Oh, Sia-UI-v0.4.2-beta-win32.zip includes x64 version of siad and dosent work on x32 systems

Okay, should be fixed now. Thanks.
Somebody will answer where Sia a wallet keeps the downloaded blocks?
Sia/consensus/set.db
Stuff like this...
Will limit this (very promising) project to super-geeks that unlimited time to f*ck around with crypto wallets.
That said, the GUI wallet is what counts and it's making progress:

OK, the blockchain is updated and I've transferred a little test coin from Polo...
But, of course, I'm LOCKED OUT... even after I've been given a 29 word passphrase (where NXT uses only 12 words).

Oh, the Dev wants me to run another 2 separate command line utilities...
And muck around with more passphrases with little known copy/paste techniques via consoles.
Let's add 17 more "locks", baby = very poor design.
Sorry, but you HAVE TO make GUI wallet standalone to attract normal people. Please make standalone GUI wallet a priority.
It's called 'beta' for a reason

We're still working through the kinks, each version we try to make it more user friendly.
Are those nodes that only offer space, or all nodes connected? I don't appear on that list. Is that because I'm not done syncing the blockchain yet?
You won't appear until you finish syncing. That list should be ~a full list.
I've been syncing for 10 hours now. I'm at block height 1976 (connected to 8 peers). Is it normally this slow?
Also, I cannot Announce my storage. I get the error message:
"Error 400 Bad request host address not reachable; ensure you have forwarded port 9982"
I have forwarded port 9982 on my router. Still doesn't work.
Sounds like you froze the client by unlocking the wallet before the syncing finished. This is a bug, but avoidable by waiting to unlock the wallet. Hope to have a fix in the next 2 weeks.
You'll have to do a 'force announce' if it doesn't think you've forwarded your port, but you know that you have forwarded your port.
Also, I cannot Announce my storage. I get the error message:
"Error 400 Bad request host address not reachable; ensure you have forwarded port 9982"
I have forwarded port 9982 on my router. Still doesn't work.
I think you have to forward 9981 as well
Let me know if that works, I don't think it will help but on the off chance that it does... good to know for all other users.
I'm splitting my response into 2 posts since there's a lot to say. Sorry if I missed anyone, tried not to forget anything.