Topic: Armory - Discussion Thread - page 202. (Read 521749 times)

Using .73 and .74 I get an error when trying to run saying only one instance can be ran at once even though that was the first time I have ever used this program. I tried the installer and standalone archive. I am using Windows 7 x64. .70 works fine though.

that is awesome. 

i don't have the time or the background to do it the way it is currently required.

Sweet!  I got an official-looking installer created for Windows 64-bit systems (in the form of a *.msi file).  It is a massive improvement over the previous distribution method.

• Creates a single downloadable .msi file that can be double-clicked to install Armory
• Makes you agree to the Armory license
• Automatically adds an "Armory Bitcoin Client" section to your start menu
• Menu includes an uninstallation option
• Each new version will just overwrite the old one

Try it out and give me feedback!  Also, please let me know if you have any problems running 0.74 and provide me with system specs if you do.  I've had a report of some issues on some systems.

Next up is creating a Debian package for nearly the same simplicity in Ubuntu/Debian (you will still have to install the dependencies the first time, but then every update should be a double-click).

Thanks, i'm going to build it and post my results (I'm using VS2010)

This sounds fantastic!  Admittedly, my windows MMAP/MVOF skills are below par.  I couldn't understand why declaring sequential scanning didn't improve the load time at all, and why it still seems "finnicky."  Please PM me with the information and I can put the improvements directly into my branch, rather than dealing with getting the build environment setup. 

If it's more involved than just changing flags... well the Windows build instructions on my website are really good!  (it's not pleasant, but I've documented it thoroughly enough that it worked for a lot of people building it).  Just be aware, that it didn't go smoothly last time I tried to build it in MSVS 2005.  I use 2008 and I've heard 2010 works, too.

I was going to improve your Windows mmap implementation, but i just read the README and i'm too lazy to set-up the build enviroment on Windows right now (3 am). So i'm going to sleep a bit and then help!

istar,

It has supported them since version 0.70.  Windows systems with 1.5 GB+  and Linux with 0.5 GB or more.  Windows didn't react so nicely to my RAM-reduction upgrades, but it does work, and it shouldn't kill the system (it looks like it's using a lot of RAM, but it's mostly virtual which means that it can/will give up some when other programs are loaded).

The only restriction is that it won't work on 32-bit Windows.  32-bit Linux is fine.

As soon as Armory support comps with less than 4 gig ram. I will start using it.

Using Armory 0.7 (and Bitcoin 0.6.0) for Linux on a daily basis... Thanks!!

Just posted version 0.74 which fixes a few bugs in 0.73:

-- Multiple-instance prevention didn't work in offline mode.  It does now.
-- Importing addresses and removing imported addresses now updates address list immediately and correctly.  If you don't feel like upgrade, be sure to close the wallet props window and reopen after an import.  The import works, but it doesn't update the table.

This wasn't a big enough issue to be worth updating the announcements thread.  But the import/remove thing was bugging me, so maybe it was bugging you, too.

No, I said it right.  In Windows, my memory-mapping was locking out all other processes from the blockchain file.  This meant that the Satoshi client couldn't read or write the blockchain file at all -- no validation no block updates.  Whatever block you were on when you started Armory, is where you were stuck (though incoming or outgoing 0-conf tx worked fine, they were just stuck 0-conf).  But I figured out the correct flags for the mapping in Windows, and it should all work now!

Did you mean "The memory mapping wasn't preventing the Satoshi client from accessing the blockchain file at all!"

This is worthy of an announcement update (so I will post one soon) -- the Windows issues are completely fixed! 

The memory mapping was preventing the Satoshi client from accessing the blockchain file at all!  I hate Windows.  But I'm relieved.  Fwhew!

I also got sick of the -beta-alpha version which made more sense if I was like 2 days from beta.  But I promised a new wallet format for beta, and that might still be a couple weeks off.


Find the new Win64 binary in (version 0.73-alpha):   https://github.com/etotheipi/BitcoinArmory/downloads

Armory version (0.72-beta)-alpha-RC2   (Still Linux/OSX only)

Still on the "bulkimport" branch!  But stability is rapidly approaching, will merge into master soon.  PLEASE HELP TEST!  (See my previous post about how to run 0.72)

Great News!

• Fixed color schemes!  Looks great with dark desktop themes! (see below)
• Cleaned up address books!  Better user interaction, better information!
• Cleaned up bulk-import!  Warns you about keys already in wallet.

Terrible News!

I have become aware that the Windows version 0.70+/RAM-Reduction is preventing the Satoshi client from writing the blockchain.  This went unnoticed, because you can still send transactions and receive zero-conf transactions, but you won't see any confirmations until you restart Armory!  This is super-top-priority for fixing!

(Linux version works fine, though)

I don't actually care about offline transactions.  I just want the book keeping.  I've been doing it my way because my way was the only way I could think of.

It's not a bad idea for helping users do this without shooting themselves in the foot.  But I don't think it solves Red Emerald's problem, which is that he does want this address added to his wallet so that he can then use it for offline transactions.  Implementing your suggestion would be great for letting users simply-watch-and-nothing-else addresses on demand, but doing anything other than monitoring payments/balances would be complicated.

Right now, the only way to achieve Red Emerald's goal is to go to your offline system first, import the key, fork the watching-only wallet, then copy it to your online computer (removing the original).  It's a few extra steps for sure, and it could be improved.

However, regardless of the solution: discussing this just made me realize a very important feature I need to add (and is already kind of in queue to be added):  separate comments file.  Right now, all your address/tx comments are stored in your wallet, and there's no way to merge a new wallet in (as described above) without overwriting all of them. 

I say this is "kind of in queue already", because I will need to do the exact same thing with P2SH scripts:  they will need to be stored in a separate, low-sensitivity file that can be dropboxed or part of some kind of daily backup.  You need that stuff backed up as soon as you create it (comments, not so important, P2SH scripts:  very important), but you don't want your whole wallet file, encrypted or not, sync'd to multiple other servers on the internet. 

Unless one of the dependencies conflicts with your current version of libc6, and APT decides the best way to resolve the situation is to uninstall libc6. The fact that the following command: appears more than once in my .bash_history would seem to indicate that Synaptic does not always know what the Hell it is doing.

Well, typically you can setup the offline system while online (which takes 3 minutes), and then disconnect it permanently before creating your first offline wallet.  However, this means you may not know how to install new packages, since us Ubuntu folk are so dependent on our versatile package managers.

In Synaptic, after you select all the packages you want to install, you can go to File-->Generate Download Script.  It then creates a script (which is just a bunch of wget commands) that can be run on any linux system to download the package and all of its dependencies.  Save the script to its own directory on a USB key.  Then you just double click from an online computer and downloads everything for you into the same directory.

When you go back to the offline computer with your USB key full of packages, you go into Synaptic again, and File-->Add Downloaded Packages.  You point it to that directory, and it installs them as if it had a connection.  This is a useful feature, because Synaptic knows what dependencies and versions it needs, and will do it The Right Way for you. 

Fixed. Don't forget, order matters with the and operator. If the first operand evaluates to false, the second operand won't be evaluated at all, since the and operator is guaranteed to return false regardless of what the second operand is. This is why that line didn't cause an error when the Internet connection was detected successfully: the erroneous expression was never evaluated. The same thing happens with the or operater if the first operand is true.

Thank you.

Well I'm guessing (and this is pure speculation on my part) that you'd install it the same way you installed all the other dependencies for Armory? And Armory itself for that matter?

Perhaps you could make the "Ledger"  (Maybe turn into "Wallet Ledger"?) a drop down selection list. Have "Watching" one of the options. Then when "Watching" is selected it just lists all the addresses and the totals for each one. Add a little button "Add address to watch" and the user then inputs the Bitcoin address only. You could just enter any address. It scans the blockchain and finds the total. Something like that perhaps? That way the Ledger and Watching are never together in the same list.