Hey,

this has been asked before, but I had troubles finding a recent answer: can I use Armory and the standard bitcoind wallet in parallel? I still  use bitcoind via rpc for some scripts, and even though I would use Armory for my personal wallet, I would need to keep the script functionality. I imagine that the two wallets do not clash at all, ie, are completely separate?

yes you can, bitcoin{d,-qt} is only needed to communicate with the network and get/validate the blockchain.

Alan is working on it as we speak, hang in there =)

The first issue is on our list of bug fixes for the immediate future.

The second one is more complicated.  We switched from using MSI files to use NSIS .exe files for the installers.  This has proven to be more difficult in terms of signing.  I can sign the .exe, and the user can right-click the properties of the .exe and see it, but I believe it then unpacks the proper installer and runs that, which isn't signed.  As such, I haven't been able to figure out how to make this work with our new NSIS installer system.

Perhaps I'll add it as a task in our SW tracking system.

More specifically, you can go into the settings for Armory, and disable "Let Armory manage Bitcoin-Qt/bitcoind in the background".  Then Armory will expect you to run Bitcoin-Qt or bitcoind manually, and that it will be open and synchronized when you start Armory.

This will give you greater flexibility for managing both apps.

By the way, we will have a mostly-complete armoryd.py soon.  You might consider looking at that (in a week or two), as it should have most of the same functionality as bitcoind, but with Armory wallets (including watching-only wallets, etc).  Also we recently added a page about Python Scripting with Armory

I had to downgrade to 0.88 last night because the UI had become slow and unresponse to the point at which I could create a transaction and click "send" and nothing would happen.

Log file?  

Also, did you recently add a lot of addresses, wallets, etc?  There's a known problem if you have tons of addresses, it can be slow when new blocks are coming in.  That's going to be fixed in 0.91.

Also, try "Help"-> "Rebuild and Rescan Databases"

Bitcoind is in a completely separate directory.  Armory just starts it without the GUI.

If you close Armory, you can start bitcoind, and it will work as normal.  The two sets of wallets are completely separate (except that Armory assumes blocks that have been verified by bitcoind are valid).

Oops. Forgot about this.

bitcoind's been throttled to .5kB/s since I last posted. Hovering over "Connected (275122 blocks)" shows "Last block received is 19 hours ago." Upon unthrottling bitcoind, Armory ran fine for a while (no updates to block count), then froze up for a few minutes. the next update is "Connected (275179 blocks)" and hover text shows "Last block received is 12 seconds ago." As of this post, current block is 275307. Unlike QT, Armory isn't telling me how far behind bitcoind is. Armory also kept occasionally freezing up for ~10-20 seconds while sync'ing. Emailed you the log just in case the freezing's an unknown issue and there's anything helpful in there.