Armory is excellent, but not a great pick for newbies especially given that the steps here aren't "programming" .
If you haven't sent coins to your Armory wallet yet, you'll probably want to try a different wallet. Electrum is pretty easy to get going with.
If you have sent coins to an Armory address, start your own thread and explain the problems you're having there. You'll most likely be asked for Armory logs (log files) so that devs or others here can identify the problem. Posting the full version number of Armory and Bitcoin Core you are using also helps a lot too.

As for your specific questions, 64bit/32bit shouldn't make a difference, but I can't say I've ever tested that. There is no reason not to use the 64bit versions of both if you have a 64bit PC & OS. Bitcoin Core will take a long while to sync and require ~155GB of storage space (and growing). Armory isn't going to do much for you until that is complete.
Again, start a thread of your own if you still need help and/or have coins to recover.

As per the post, give that one a whirl. If you've already installed the psutil dependency from a previous offline package this should work.

Ooof, yeah. Armory needs a full ~145GB node, not a pruned one
Will you have enough space available for this once you turn off pruning?

As for why core is failing... not sure. I'd have thought if Armory was starting core itself too (there is a setting for this by default), then you'd be able to find bitcoin process it spawns.
Hate to fall back to this, but restart system?


To answer another question:
This is the current amount of transactions that are pending and waiting to be mined into a block. Not something to worry about as a user, except for figuring out transaction fees

Hey there,

Lets try to narrow down your issues.

Armory 0.96.2 and lower don't play nice with Bitcoin Core 0.15.0.1, as you seem to have found out in your last two posts.
This was fixed with the next release: 0.96.3 and 0.15.0.1 will work together.

It looks like you're running 0.96.2 and Core 0.15(.0.0) in your last post, which should work but might need a nudge:
Try shutting Armory down (including ArmoryDB) and then deleting the databases folder (/home/henry/.armory/databases) in case anything broken has been carried over.
Additionally is your Core node configured with "server=1" ?
If not, then (re)start Core. Make sure it is synced fully then start Armory. See how that goes!

If you're struggling to get Electrum working, Armory is probably not going to be a good fit. It is also the opposite of lightweight, requiring a full ~145GB bitcoin core node.
You seem to have some permissions issues, which I imagine are inhibiting electrum too.

Again, up to you but the rpi readme on the armory repo covers it. Literally just need to clone or grab a zip of the repo to extract it then follow step 2 to set up the path and so on as usual. gcc-linaro-arm-linux-gnueabihf-raspbian-x64 for x64 host and gcc-linaro-arm-linux-gnueabihf-raspbian if not.
No worries if you're not going to use it, but just wanted an answer to at least appear in search.

Seconded. DigitalCrypto, you need to follow all the instructions

As far as I know, that official cross compiler supports all rpi models - so it might work with your current 1B. Something you could try while waiting for the new model? Up to you, of course.

It means you need to use bitcoin core 0.15 and not 0.15.0.1 until this is patched in Armory and released.

You'll need to start bitcoin core (bitcoin-qt.exe) itself which will let you know how far behind the local data is.
Reading through the bitcoin full node guide might help explain a bit https://bitcoin.org/en/full-node
How long it'll take will vary depending on bandwidth available and your CPU and potentially HDD performance. If you have RAM to spare, increasing the dbcache size can help there.

Strange. Can you create a normal electrum wallet successfully?

Armory requires a fully synced (~145GB of data) Bitcoin Core node to operate.

Any reason you're not using the official rpi cross compiler?

May not magically solve all your Armory problems, but you should be using Armory 0.96.2. Some bug fixes in the changelog that could be relevant.

Regarding Electrum, importing works for me, though it was a little picky about the data.
Some things that may help:

• When exporting your private keys from Armory
  • Check "Omit spaces in key data"
  • Uncheck all other boxes except for "Private Key (Plain Base58)"
• When inputting in Electrum:
  • Do not include any other lines i.e. Remove "created, wallet ID and wallet name"
  • Make sure that each private key is on a new line and importantly make sure you are using return/enter and not space or tab. Using space/tab (at the default window size) will wrap the key onto the next line, but will not count as a new line and will stop you hitting next.
  • Alternatively copy the just PrivBase58 lines directly from Armory in one chunk and then delete "   PrivBase58: " from each line.

Nearly there. If you haven't downloaded a copy of the Armory git repo (the code), you'll need to do that. Can either grab the zip and extract it or git clone if you're familiar with that.

Either way, once you have a copy of the code, cd to wherever the Armory code is.
Then run step 7 again:

Compiling may take a little while
Fingers crossed!

You could help yourself out here by following HCP's instructions to create a bitcoin.conf in the right location with the config options he suggested.
https://bitcointalk.org/index.php?topic=2133694.msg21912062#msg21912062
Unless something very strange is going on, that should get you to a green connected state that will update as new blocks are mined on the network.

Okay, crash course to help you understand a bit:
As the message says, typing in "help" lists all commands.
"help commandgoeshere" will explain the command of your choice.
Try "help importprivkey" and it should explain that it adds a private key to your core wallet (and the arguments for the command)
This interface is very powerful, and people can be very malicious, hence the warning. A certain level of paranoia is a good thing here - and don't just take my word for it on this info.

Oh and you won't need the "bitcoin-cli" part at the start when you're in this debug console.

Since you're using 16.04, I think you're probably going to run into the same issue as Rothbart did here: https://bitcointalk.org/index.php?topic=2133694.msg21677920#msg21677920

Short answer is you'll still be missing dependencies on 16.04, but these are included as part of the base distro for 14.04.

For me, the blockchain itself is about 140GB, not including chainstate. Back of a napkin math says it grows about 4GB a month (and this may increase) You may want to run something like windirstat to help identify what is using your disk space.

Armory requires a full, up to date, node (Bitcoin Core) to be running in order to use any networking functions.
If you do not have the disk space available for a full node, this may not be the wallet for you.
Armory will need to scan the new blocks, yes. How long depends on how out of date and your hardware specs.