Hi;
Firstly, let me say I am eager to install your Armory client on my new computer, and I have read through the instructions a few times already. I have a few issues I would like to resolve before I launch into using it in earnest tho...
RAM; You state that I need 4 GB of RAM to operate the online wallet. My comp comes with 4 GB installed RAM (says 3.6 available) does Armory itself use all 4 GB? that seems like a hell of a lot, and would leave me short 0.4 GB to operate it. plus my comp would only be good to use as a wallet and I could forget about running any of the other software I use on a daily basis. Am I missing the point here? do you mean I need a 4 GB RAM comp, or I need the whole 4 GB to run armory? please elaborate.
New version coming soon; how soon, and will the new 9.0 version use less RAM?
This is a bit of a stickler for me as I am very attracted to armory's unique features, but buying a new, and frankly, at over 4 GB much more costly computer is kinda hard for me to swallow. sorry, i'm such a n00b but if you could just lay out the basic must haves in simpleton language for me it would be much appreciated. I really want me some armory protection
The combined RAM usage of Windows and Armory together is approaching 4 GB. It's based on an old, not-really-intended-to-be-scalable blockchain engine from 12+ months ago, built before I realized I even wanted to make a full client. It's needed to be upgraded for a while, and I just wasn't quick enough before it went over the 4 GB cliff. So that's why there's the scary message.
I am in the process of not only fixing the RAM issues, but solving a ton of other, persistent issues users have been having. Most of them are just usability issues. But I'll definitely be a lot further ahead than I started. Just, for the next couple weeks i have to leave the scary message up there. I'm pretty sure the next version will be 0.9 and will use about 1/10th the RAM (and not grow with the size of the blockchain), and will start up very quickly. But it's not even close to ready yet...