Trying to send BTC I had the fee set to automatically calculate that. I changed that and the transaction failed, the error message said the fee may be too low. I adjusted a few times and it continued to fail.
From the looks of it, you're using 0.96. If you're trying to send BTC, you should upgrade to 0.96.5, fixes the bugs you're running into:
https://github.com/goatpig/BitcoinArmory/releasesIf you're looking to spend BCH, you will have to go through a more convoluted process:
1. You want to try 0.96.2 as the target release.
2.a. Find dedicated BCH wallet software (I dont have recommendations, sorry), create a wallet with that, back it up, test the backup. Then grab a legacy BCH address from said wallet (starts with a '2').
2.b. Make a backup of your Armory wallet if you don't already have one. Test the backup to be safe.
The hard part (you do not run Core for the entirety of these steps)3. you will need to setup a dedicated "environment" for your BCH signature process:
a. Create a copy of your blockchain data, cull blkXXXXX.data files away to be around 450~500k blocks. Aim for 30GB, you can add files as you go. You do not need the revXXXXX.dat files.
b. Run a 0.96.2 version of ArmoryDB against this copy of the chain. You can get a standalone (no install) binary through the win64.zip release.
c. Make a copy of your wallet in a dedicated datadir and run ArmoryQt 0.96.2 against it while the target ArmoryDB instance is running. You will require some path magic for this to work unfortunately. A "solution" to avoid the path-fu is to do this on a second PC. When this is finally running, you will have ArmoryQt running, showing the top block to be in that 450~500k range.
d. You can now create an unsigned transaction moving your BCH to the freshly made BCH address from Armory. To do this, check the "create unsigned" checkbox in the Send dialog. You will be served with a blob. You can choose to sign it. Pick the BCH signer and sign it. Once the blob is signed, choose to export it as "raw hex".
e.With the raw hex blob, you can now broadcast your tx via any online BCH broadcast tool, at your own leisure.
This is the leanest setup I can think of, as you would have to run some old version of the BCH node to get to broadcast from Armory, which is probably impossible these days, due to various backwards incompatible changes on the BCH side.
4. Bonus round:
If you're paranoid, you can choose to create the signed BCH tx, then move your actual BTC to a new wallet via regular Armory, then broadcast the BCH tx last. At any rate, my recommendation is to move your BTC off that wallet if you're gonna split the BCH out.
