And by newest version of Armory, you mean 0.96.4 RC3? If not, upgrade.
We'll probably want to see your logs files too. File > Export Log File, add to pastebin (or a site of your choice) and post the links here, please.

Thanks.
Well on your offline, I'd create a copy of the Armory folder in C:\Users\YourNameHere\AppData\Roaming and rename C:\Program Files\Armory\ ArmoryOld, then as a worst case scenario you could just roll back.
32bit... yeah that does matter, thinking about it. 32bit should work, but there aren't any official windows 32bit builds available for 0.96.4 at the moment. 0.96.2 is available for 32bit windows, though.
Posting your logs will still help give info, but without that and in your case, I'd recommend upgrading to 0.96.2 on your online and offline pc and see how that goes.
Could need a rebuild of the Armory database too, but try the less time consuming suggestions first.

Sorry, was mobile before so my response was a bit brief.
We need full logs, not just the last snippets. Add dblog.txt and armorylog.txt to pastebin (or a site of your choice) and post the links here, please. And privacy issues are your username and some debug info about your hardware.
Which version of Bitcoin Core are you using? I vaguely remember older versions of Armory choking on newer versions of Core, but not completely sure.
Are you dead set on not upgrading your offline setup? That offline signer is really old now - 2 years ish?

Might be a compatibility issue then... might not. Post your Armory logs please.
Fees vary, but this is a decent resource for seeing what the going rate is https://dedi.jochen-hoenicke.de/queue/more/#24h

No to the first paragraph, yes to the second:

make uninstall  (sudo if it fails)
make clean
make
make install (sudo if it fails)

Are you running Armory RC3? Upgrade if not.
We'll likely need full Armory logs. Could you add your armorylog.txt and dbLog.txt to pastebin and post the links here please? Split if too large.


Please go back to using Core 0.15.1, otherwise you'll need to reindex your chainstate.

There isn't a one fits all solution for problems, Artur2000. However, it will make it a heck of a lot more difficult for us to help you if you change your setup a bunch while asking for help.

That advice is about 10 months old.
Get yourself on Core 0.15.1 and Armory 0.96.4 RC3

Yeah, no sign of the above error since you upgraded from 0.96.
Let it scan for a while. If it doesn't play nice, you can try deleting the Armory databases folder and letting it rebuild. That will take a while though.
If you still have no luck, start a new thread with fresh logs (as you have done already) and we'll see what needs to be done to get you running.

RC3 is available now and you should use it, but I expect it won't fix this problem.
How old is your mac? Not an expert on mac crashes, but usually illegal instruction errors are down to old CPUs. Tends to require compiling Armory yourself rather than using a general purpose build. droark will know better than I do

No.
https://bitcointalk.org/index.php?topic=2754632.0

Ninja'd by Holliday but posting anyway:

Generally an offline wallet is used as part of a cold storage setup.
You have the full wallet on an offline pc and a stripped down "watch-only" wallet on the online pc that can see your balance on the various addresses. You create unsigned transactions on the online pc, sign them on the offline pc, then broadcast on the online pc.
Helps keep your private keys secure, as well as the coins they control.

The old website has a decent blurb on it that still applies: https://www.bitcoinarmory.com/cold-storage/

No problems so far. Thanks, goatpig!

"Send Bitcoins", right below the Armory logo.
You need a receive address from your exchange too.

Glad you're up and running.
Are you talking about on the same pc here? Or having a separate offline & online computer?
The wallet itself should be there, but the balance won't display unless it is online.

Since it won't appear in the logs, are you running Windows 10?

Since you're using Windows, please grab 0.96.4 RC1.
0.96.4 RC2 has more fixes than RC1, but has a bit of a quirk that can cause issues - RC3 will fix this.
Heads up: bitcoinarmory.com is the old site. Please use btcarmory.com and/or this forum/github in the future for up to date builds.

Try again after updating. Thanks for providing logs!

Oh and the blockchain looks like it is in C:\Users\MrPc\AppData\Roaming\Bitcoin\blocks for you. That folder (and its contents) should be about 160GB.

So, that setting I had you uncheck? That means you need to manage Bitcoin Core yourself, rather than just launching Armory and having it sort things out. One extra step, but I've found it a lot more robust and is my go to when things aren't working automatically for people - but you need Bitcoin Core to be running for Armory to go online.

So, usual process for me:
Start Bitcoin Core from the shortcut (which loads up the Graphical User Interface [GUI]). Wait for the splash screen to finish verifying blocks.
Start Armory.
Wait for everything to catch up and then, usually, Armory will pop up and say everything is in sync and online.

To shutdown:
Quit Armory. Optionally check if ArmoryDB has closed too (It doesn't seem to shut down if it is busy)
Quit Bitcoin Core.

Does that help?

I don't understand this part? Would you mind trying to explain again?
I don't know what you are trying nor whether you have done anything wrong in the process
Slight language barrier here - Your English fluency is a lot better than my German, though!

Was that 2 BTC in your hot wallet in August, when the split happened? If not, it won't be there on the BCH chain.
You can check balances for your cold wallet addresses on various blockchain websites - Blockchair supports BCH.

There is also a big thread about splitting BCH pinned in this forum.

Whatever your BTC balance was at the time of the fork (August), you'll have an equivalent balance in BCH.