Quote from: bob123 on June 12, 2019, 06:48:44 AM

It would help us a lot if you could post your armoy logs.

Upload them to https://pastebin.com/ or any similar site and provide us the URL.

My guess would be that some configuration is wrong. Without the logs we can't say whether it is the directory or anything else.

Here's the Armory log> https://pastebin.com/aaSmUqSc

Also:
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
You will also need a "bitcoin.conf" file in your Bitcoin "datadir" that has the following line in it:
Code:

server=1

That will enable the RPC component in Bitcoin Core and allow Armory to communicate with your Bitcoin Core instance correctly... In the Bitcoin Core GUI "network" settings (Settings -> Options -> Network), you need to check the "Allowing Incoming Connections" option
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
I have the bitcoin.conf file but there's nothing in there. Not sure how to put the "server=1" in it.

Bitcoin core has the box checked to "Allowing Incoming Connections"
In fact those settings look exactly like yours.

I did change Armory to find the Bitcoin Core directory in the "D" drive, but something is still off.

I get the feeling when I make a change in some way, the entire configuration is still off. Everything needs to be properly configured. I' just not sure if I'm leaving something simple unchanged or i'm making changes in the wrong place.
The fact that I'm running dual drives is complicating things.

If I don't get this solved by tonight I'm taking this thing back to exchange for a single drive laptop. Unless you folks feel otherwise.........