Did you pay a fee on these transactions?
If the default transaction fee was selected could the network deny the transaction somehow and make things look weird? The BTC address I sent the coins to indicates a 0 balance, but the wallet I sent the coins to still has the coins in them. I may have selected the default transaction fee. If that may make things look a little odd that would explain "some" of the issues.
Still not sure why Armory isn't letting me know there is an updated Core.
I can directly send you my log if that may make it easier to check? Little hard to decipher the log if not a developer. I can re-generate the URL issue at will by hitting check update button. I don't want to blindly just reinstall/update. I'd rather try to see why these things are happening, to avoid them later.
Thank you.
2016-01-18 20:06 (INFO) -- announcefetch.pyc:271 - Fetching:
https://bitcoinarmory.com/announce.txt2016-01-18 20:06 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-01-18 20:06 (ERROR) -- announcefetch.pyc:284 - Tried:
https://bitcoinarmory.com/announce.txt2016-01-18 20:06 (INFO) -- announcefetch.pyc:271 - Fetching:
https://s3.amazonaws.com/bitcoinarmory-media/announce.txt2016-01-18 20:15 (INFO) -- announcefetch.pyc:389 - Forcing announce data fetch
2016-01-18 20:15 (INFO) -- announcefetch.pyc:271 - Fetching:
https://bitcoinarmory.com/announce.txt2016-01-18 20:15 (ERROR) -- announcefetch.pyc:283 - Specified URL was inaccessible
2016-01-18 20:15 (ERROR) -- announcefetch.pyc:284 - Tried:
https://bitcoinarmory.com/announce.txt2016-01-18 20:15 (INFO) -- announcefetch.pyc:271 - Fetching:
https://s3.amazonaws.com/bitcoinarmory-media/announce.txt2016-01-18 20:15 (INFO) -- ArmoryQt.py:6763 - BDM is safe for clean shutdown
2016-01-18 20:15 (INFO) -- SDM.pyc:683 - Called stopBitcoind
2016-01-18 20:15 (ERROR) -- Networking.pyc:359 - ***Connection to Satoshi client LOST! Attempting to reconnect...
2016-01-18 20:15 (INFO) -- ArmoryQt.py:6805 - Attempting to close the main window!