This appears to be an OSX specific issue. You should submit a ticket to support@bitcoinarmory.com

New release coming up real soon. You can try out the testing builds already present on the official site to see if the this issue occurs again.

There is a coin control option in expert mode that allows you to exclude an address from the available pool of spendable outputs. Keep in mind that you'll have to exclude these addresses on every send. Don't quote me on this but I'm pretty sure there are some low priority plans to add up coin control functionalities.

The current Armory database is about 1.2x larger than the blockchain, for a total of 2.2x blockchain worth of disk space. This is currently the full implementation, aimed at supporting full and super nodes. There are plans to reduce the DB size requirements for plain "client" nodes.

Regarding Windows XP support: The code is there, and the builds have worked in my environment. I have passed this build around for users to test out, and so far the reports are positive. However this build implements some changes to the build environment and the code. We need to test these out more thoroughly before including them to the release.

Assuming there is a WinXP user base loud enough to complain about the lack support and etotheipi is ok with this, I'll build and serve the XP binaries. That will be my own build however, it won't be signed and it won't be hosted on Armory's page, only a link in the forums. Use that at your own risk or wait for the official release.

tldr: have a good build, needs more testing, may post home brew builds if you can't wait.

You lose the deterministic benefit of Armory wallets when you import private keys instead of sweeping them.

The current testing version is actually very stable and entirely better than the latest release. It has even posted on the official website. This is confusing admittedly.

Do you have a bitcoin.conf set? Do you restrict the amount of nodes that can connect to you? Armory doesn't connect to the RPC, it connects as a node through localhost. Also, which version of the bitcoin client are you running?

Your version kind of is out of date.

https://bitcointalk.org/index.php?topic=299684.0

Try this one out and let me know if the issue still occurs.

What version of Armory did this occur on?

The collision would only compromise a single private key. Wallets have several private keys. If you're talking about Armory's wallet seed collision, then it would indeed corrupt the entire wallet. In this case multiple multiple wallets would protect even more.

Keep in mind that the chance for collision is infinitesimal

By design you should save your coins on several private keys. In the abysmal chance of private key collision, you wouldn't be losing everything.

fork the git repo and code away o.o

Thanks for the testing guys =) Keep it up =P

Reinstalled bitcoind or Armory? OS?

Thanks for testing guys. Need a few more tests plz, Win7+ as well =)

Windows User, Vista and above only:

This build attempts to fix start up issues in Win Vista+. It implements some rather big changes in how the exe is produced, so please, Win7 and 8 users, try it as well.

Note: as usual, this my build (goatpig's), not etotheipi's. This is ran at your own risk. You only need to run Armory in offline mode to confirm the compatibility of the exe.

http://dfiles.eu/files/hff8gkt3b

WinXP Users:

http://dfiles.eu/files/maerajlp1

Vista or XP?

Communication with Qt is done through the RPC server, however (don't quote me on this) I think it is hardcoded to localhost. Assuming you get accross this hurdle (or that I'm wrong), you still need to give Armory the raw block chain files path. Through a network share, I assume.

Here's a new tentative build to try and get Armory running on Vista and XP.

Disclaimer: This my build (goatpig), not etotheipi's. This is only for testing purpose on older Windows platforms. A lot of optimizations have been taken out in an attempt to achieve a failsafe build, so this will be slow. Starting Armory in offline mode is enough to prove compatibility. Adventurous ones, you may wanna try and build the DB (at your own risk)

https://mega.co.nz/#!0chE2J4C!RoE8WUfmPPqU1HStumsfh3bKGtJPu-toxzRhcM7_zVY

There was explicit notes on the lack of WinXP compatibility with the code I used, but nothing about Windows Vista. Please install .NET framework 4.5 and tell me if it works. I'll investigate that matter.