this is NOT easy if you have thousands of keys.
Define "easy" then? 
Also, with the Electrum forks you should only need to do the import once. From that point on, you should be able to get away with simply copying the the wallet files and opening the copy in the appropriate fork of Electrum and it should just work.
- Import keys into BTC Electrum (ensure all empty)
- Copy wallet file
- Open in Electron Cash (get BCH)
- Copy original wallet file
- Open in ElectrumG (get BTG)
- Rinse and repeat.
Of course, not all forks have released Electrum forks... but if you want your "free money" you're going to have to work for it
would you be willing to share the entire contents of your bitcoin.conf? like i said, i tried listing both server=1 and listen=1 as well as dummy rpcuser and rpcpassword parameters without success.
Code:
walletrbf=1
dbcache=750
server=1
Note that without listen=1, I get the issue (using BitcoinQT) where it will say "node offline" or it will say "connected", but it won't update blocks... If I just use bitcoind, it seems to work OK.dbcache=750
server=1
However, for me, having listen=1 will ramp up the bandwidth usage quite dramatically though.
You can read about the various issues I've had with Armory and Win10 here: https://bitcointalk.org/index.php?topic=2783764.msg28460485#msg28460485
and an older (and quite possibly outdated) here: https://bitcointalk.org/index.php?topic=2200306.msg22126330#msg22126330)
i'm now able to get an active connection when i downgrade ABC to 0.16.1. it will even connect from the VM when the host has an active BTC client connected! so much for port conflicts. turns out it probably is the network magic goatpig was talking about and how Armory won't connect to any ABC client newer than 0.16.1. makes me worry about what will happen after the May 15 ABC hard fork when and if 0.16.1 won't be compatible...