I did that, now the ArmoryDB.exe started again and showing these command lines:
<../DatabaseBuilder.cpp:268> parsed block file #38
<../DatabaseBuilder.cpp:268> parsed block file #40
<../DatabaseBuilder.cpp:268> parsed block file #42
and so on..
It stopped at
<../DatabaseBuilder.cpp:268> parsed block file #48
That's supposed to happen, but it should continue with some other stuff and with more block files.
Is Bitcoin Core running? Is it synced? What does ArmoryQt show?
Just to get it right: If I use an RaPi as a coldwallet to sign tx, that are made with a watch-only hot-wallet on my online pc, just the online-version has to be up-to-date, right? The RaPi can stay 0.93 forever, correct? I guess i cant use the advantages of segwit transactions then, but thats not so important for long-term holdings.
So long as the unsigned transaction format does not change and you don't use any of the new script types and signing requirements don't change, then yes, that is fine.