From what I know, the "BDM not ready..." means Armory's backend hangs while processing blockchain data. - It's a known, previously reported bug.

The bad news: I think you'll need to wait for the next release - hopefully next week.

The good news: Your coins are still safe, diametrically opposed to having them stored on an online computer, not to mention an online wallet.

The ugly: If you need to spend urgently, you can go to the offline computer, pick an address with enough funds, copy its private key manually and import it to bitcoin-qt on the online computer and broadcast from there. Ugly workaround, I know, but it'll keep your coins offline.

I'm a plankton miner compared to some of the whales in this pool - however:

My miners ALWAYS report effective hash rate that is always higher than my 12hr average Eligius stat:

Shown below are my 5 overclocked BEs reporting total of  2.55GH/s (all time effective):


While my 12hr average stat reports 2.44GH/s:


Now this ~1% difference is consistent. It's never seen the numbers the other way around (higher stats).

What am I missing? Am I seeing a 1% fee on eligius?

OK, that's progress - so Armory worked on a small wallet, and when you tried to import a larger one it hanged.

Here are a few things that I'd try:

• Go to the offline computer and redo the export wallet and retry to import it to the online computer. That will exclude the possibility that the wallet file was corrupt in a way that Armory can't handle gracefully.
• Sometimes application hangs (ID 1002) are caused by an antivirus program. Could you disable for this test and try again?
• If above doesn't make a difference, post (or at least examine yourself) the Armory log file. In Armory choose File-Export log file. That can hint with more specifics what internally happened.

OK. At what stage does windows kill armory?
Is bitcoin-qt running in background, fully synced?
Did armory complete building the database? You can tell if that's so by looking at the leveldb-blkdata directory and checking the properties. As of now it should contain 9,968 files. So upwards of that number.

Also could you report with what event viewer is logging? For that, click start-Administrative tools-event viewer. When it comes up, under windows logs-applications there should be an error entry complaining about the fault.
F

Difference may be the VM. Have you tried all that on a freshly installed windows on a dedicated machine?

I'm running Armory on a 2GB windows 64bit machine, and it does plenty besides running armory.

Here's my step by step suggestions:

• Delete Bitcoin-qt from the control panel
• Delete Armory
• Install latest bitcoin-qt. 0.9.0 rc3 can be found on sourceforge
• Run bitcoin-qt, wait till it completely syncs. Do not continue until you get the green checkbox at bottom right
• Install latest version of Armory 0.9 beta, for win64.
• In File-settings clear 'let armory run bitcoin-qt' checkbox
• Under Help click 'rebuild and rescan databases'
• Restart Armory
• Let it run - it might take two days to build its database from scratch

Next step would be to remove the 4RL inductor and connect a DC-DC converter to the low voltage input of the miner chip.
In addition, you could change the oscillator to about 1.5 times current oscillator.
This would offload the heat generated by the power supply (no need for huge heatsink) and also disengage the usb hub (usb hub used only for data, not power)

I've done this to the block erupter and got it to go 55% faster, with no HW errors.

Full documentation:
http%3A%2F%2Fwww.idobartana.com%2Ffiles%2Fbitcoin%2520miners%2520overclocking%2520tutorial.pdf

http://www.idobartana.com/files/bitcoin%20miners%20overclocking%20tutorial.pdf

Detailed instructions, step by step using the Block Erupter as an example.

Feedback most welcome.

Ido

Found the following (minor) polishing issues, running on win7 x64:

•    ‘Create Backup Fragments’ dialog: has an http link ‘click here to read more about fragmented backups’ – however, this dialog box is shown only on the offline computer, and therefore this link needs to either point to a local file or not exist at all as newbies might be misled to connect online at the worst possible situation opsec wise.
•   “Bad Backup!” Dialog box (fragmented backups) syntax error: - should be “…then the one you just made” instead of “…then the on you just made”
•   Failed unlock wallet dialog box syntax error: - should be “wallet could not be unlocked” instead of “wallet was not be unlocked”
•   Restore Backup (testing paper backup) dialog box: the ID and Fx fields are prefilled with spaces and they’re not deleted when typing. Need to select all and delete each field actively.

Posting this here because bitcointalk newbie policy.

Rattling armory 0.89.99.14-beta on Windows 7 x64 I found the following (minor) polishing issues:

•    ‘Create Backup Fragments’ dialog: has an http link ‘click here to read more about fragmented backups’ – however, this dialog box is shown only on the offline computer, and therefore this link needs to either point to a local file or not exist at all as newbies might be misled to connect online at the worst possible situation opsec wise.
•   “Bad Backup!” Dialog box (fragmented backups) syntax error: - should be “…then the one you just made” instead of “…then the on you just made”
•   Failed unlock wallet dialog box syntax error: - should be “wallet could not be unlocked” instead of “wallet was not be unlocked”
•   Restore Backup (testing paper backup) dialog box: the ID and Fx fields are prefilled with spaces and they’re not deleted when typing. Need to select all and delete each field actively.

This is directed at Armory core dev Alan.