Quote from: Octavian on March 28, 2013, 03:49:45 PM

I also have this problem on Windows 7, 64bit with both the Bitcoin-Qt and Armory-clients installed not on default locations.
Else it works, but this constant rescanning upon each start make it practically useless for me for "fast" transactions.
For offline wallets it's ok to wait for me.

It would be great if this can be fixed, maybe by checkpointing and a Merkle tree hash upon all successfully validated transactions.

Don't worry guys... I know what to do

There's been a lot of life distractions, and I'm trying to finish some other Armory upgrades that both improve usability, and security. After that (hopefully in the next couple days!) I'm going to crawl into a hole for 96 hours and not come out until the the RAM usage is reduced and the blockchain doesn't require rescanning on each load.

Right now, Armory is still an advanced tool. I haven't made it a priority, because I wanted to focus on unique features that no other program has, instead of having less features, but making it more usable. I'd rather have a program that 50% can't live without + 50% can't use... than a program that 95% of people can use, but don't see the advantage. Unfortunately, that "50% can't use" is growing quickly, so that's why my priorities have shifted.

It's coming!