copy 3 quotes by PeZ from Dec 20

<I always ran bitcoin-qt and Armory separately, and I don't mess with the Armory settings by using a shortcut...
"D:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir="D:\ArmoryData" --satoshi-datadir="D:\BitcoinData"
I renamed the database folder in ArmoryData to database.old to save it.
Substitute Qt with DB if you are following the instructions.
You don't want Bitcoind running if you are following the first page instructions.>

<This is what I do/did. I had previously emptied my BTC from my main wallet. Some BCH got stuck as change when I transferred it away, so I installed Bitcoin ABC in a separate directory.Uncheck the box that lets Armory run bitcoin core. It will find it, if it is running - as long as your firewall is not blocking it.
Keep separate directories for Bitcoin ABC data and Bitcoin Core data and copy the Armory wallet to another directory, but remove the database directory for when you use it with Bitcoin ABC.
If you want to run Bitcoin, do it with a shortcut e.g.
"D:\Program Files\Bitcoin\bitcoin-qt.exe" -datadir="D:\BitcoinData" -disablewallet
When synced, run Armory with the shortcut that I mention in the previous post.
Follow the directions on the first page.
Not sure if this is the easiest method, but it worked. I am using Windoze, but other OS's should have something similar.>

<With both Bitcoin Core and Bitcoin ABC, I unchecked RBF, used 1 S/B fee and copied the Hex data and used http://blockdozer.com/insight/tx/send to submit the transaction. I don't know if it is required, but I would empty the wallet of BTC before messing with the BCH contents.

Yes, when you use Bitcoin ABC you would see the BCH contents, but my wallet was completely empty of BTC.?>

---

Then quote from JoJo69 from January 19

<OK, my report, as promised.

The ABC rollback to 0.16.1 did the trick!

I did have to rebuild the Armory DB.

I have added the lines to the bitcoin.conf file since, but that was not the issue in this case.   So, to summarize for the benefit of others.

>move all BTC out of any wallets you wish to claim BCH from

>back up your BTC blockchain, ABC uses the same default install paths (borderline malicious behavior IMO but there it is.

>back up your Armory DB

>install Bitcoin ABC v0.16.1, NOT v0.16.2 !  Allow it to fully sync.  Without an old pre-fork blockchain backup or some kind of pruned backup this will take a couple days at least.

>install Armory 0.96.3.922    RC3

>deal with your pathing to point your Armory bookmark to your new BCash blockchain

>Armory file  settings  uncheck "let Armory run Bitcoin Core/bitcoind in the background"

>close armory

>delete armory\databases

>verify Bitcoin ABC is running and fully synced

>launch Armory and let it build your new DB.  This will take some hours, be patient.  It may seem hung on 99% 2 seconds remaining or something like that for a loooong time, just let it run.

>when it is finally done it should show your expected BCH balances (you moved your BTC already right?) and report "connected" in purple in the lower right corner

>set Armory to "expert" mode   user   expert

>click "send bitcoins" and make up your transaction as usual remember to uncheck "enable RBF" in the lower right

>click through and SELECT THE BCH SIGNER AS DETAILED IN THE OP OF THIS THREAD!!!

>click to broadcast, that's it...worked for me

If I screwed any of this writeup let me know guys and I will edit

Thank you all so much for the help!!>



Then from January 21:

<I found the binaries at https://download.bitcoinabc.org/0.16.1/
will link in above post>

---



I recognize that much of my questions have been addressed in the prior discussions of this thread.
I have copied many of them above to hopefully have a relatively complete listing for my questions:


____

Thank you to all the developers for all your collective efforts over the past 6 months, and the continued development of this thread.

I continue wrapping my head through the various posts of this thread and continue to remain unclear.


One Win 10 x  64 desktop computer (with two hard drives) dedicated to Armory wallets
0.96.3992 with BC Core 0.15.1 all fully sync'd to the default locations on the C drive.

--- Based on the various questions and comments through this thread,
Is it necessary to install and sync an added 0.15.1 to the Data Drive?
or does one install and sync Bitcoin Unlimited or other database to the Data Drive?

Does it remain necessary to manually delete the database blocks
immediately below block 478559 from the newly installed database (on the 2nd Data Drive)?

Does one then redirect the Path of the existing 0.96.3992 (already on the C drive)
to address the the newly installed database on the data drive. Or, does one install
a new 0.96.3992 directly to the Data Drive (if so how does one distinguish between
each of their respective icons on the monitor screen)?   

----

signers will always be an off line laptop. 


Thank you all for the development of these work around procedures
and for your suggestions re my inquiries, as I desire to correctly and securely
effect this separation of BCH from the legacy BTC.

TY for the suggestions to delete the Armory Log and the db Log.  

Deleted the Armory Datebase folder.  Opened 0.15.1 and let it sync. Closed 0.15.1
performed a new load of 0.96.3992  

0.96.3992 with 0.15.1 is now loaded and sync'd.  

Experiment re Logout was successful, though somewhat slow.  
New open of 0.96.3992 was somewhat slow, but it did successfully open, sync (and remains open)

These are the respective logs at this standing.

Ar = https://pastebin.com/yR7GDgAa
db = https://pastebin.com/XSwkuT8c

Thank you for confirming all is fine, also any ideas on why this is now rather slow loading into the computer
(Are there any ideas re interference after the recent Windows forced update)

Thank you for your kind attention.  

These are the conditions:

Using a shared Win 10 x 64 computer dedicated to Armory with the local area friend.
Originally configured successfully June, July 2017 with 0.96.0.4 and Core 0.14.2
(to be prepared for Seg-Wit, and the August 1 hard fork).  

Over the past weekend an upgrade to 0.96.3992 with Core 0.15.1 had been successful after a number of attempts
(with TY to all in the forum for the excellent suggestions)  

Further experiments to open Armory and close Armory seemed successful, Armory remained open overnight.

It had been thought that Window's updates had been disabled, but there was a forced reboot of the computer
for a Windows upgrade.  Following the reboot, 0.96.3992 didn't open correctly and had to be forced into shutdown.  

Following the prior recommendations for install the Armory folder was deleted.  
0.15.1 database properly sync'd and then properly closed.  

Subsequent attempts to load 0.96.3992 now hang at the opening rounded rectangle.
Observation of "process manager" insdicates that bitcoind.exe and ArmoryQT.exe are engaged.
ArmorydB.exe appears, but is not active

These folders are the successive Armory logs.  The dBlog file has become circa 4.4 Gbyte and not practical to copy.

Four pastebin files in succession for the Armory Log
https://pastebin.com/rVK6bS8g
https://pastebin.com/v6hCEWJz
https://pastebin.com/TN8NGuZ0
https://pastebin.com/03c4Afff

Thank you for your advice and suggestions.  
I have a guess it may be necesssary to fully reload 0.15.1 from scratch on the dedicated Armory computer.

This is the computer intended for install of the added databases
and to separate BCH from the legacy BTC positions.  

There are two other computers used each of us - for our regular internet connections.  
Each of those computers has 0.96.3992 and 0.15.1 fully operational and non contaminated
Each respective On Line computer has a dedicated off line computer for signing transactions.

Thank you again for your help.

Thank you for the excellent information and sequences re updating the Win 7 x 64 computer.

BC Core 0.15.1 updated the prior Core 0.13.xx database to the most recent format.
(I appreciated the time savings of Not reloading it).  0.15.1 sync'd perfectly. 

Per your suggestion I did delete the prior Armory database folder before installing Armory 0.96.3992.
Next closed the core 0.15.1 database program.  Then installed 0.96.3992 

Armory 0.96.3992 fully sync'd to 0.15.1 on the Win 7 x 64 computer. 

Thank you for the excellent suggestions. 

---

Now doing the same processes as above with the computer on which Armory 0.96.0.4 and Core Database 0.14.2 had been installed in July 2017.   

Armory 0.96.3992 is presently sync'ing to the updated 0.15.1 Core database on the 3rd computer. 

TY to all for the assistance. 

Now have Successful install and sync re 0.96.3992 with BC core 0.15.1


Wednesday afternoon I made a further experiment on the friend's computer. 

Uninstalled BC core 0.15.1 db management program.
Uninstalled my earlier attempt to install Armory 0.96.3992

Reinstalled Bitcoin core 0.15.1 and let it fully sync. 
Closed the 0.15.1 program after completion of the db sync. 

Reinstalled Armory 0.96.3992. 
0.96.3992 correctly completed the install and commenced the Armory sync to BC core 0.15.1
let it continue through the night. 

---

Returned to the friend location on Thurs
Armory 0.96.3992 is fully sync'd.
Each respective watching wallet indicates the correct balance. 

Confirmed that 0.96.3992 will generate a receiving code for one of the wallets.
Confirmed that 0.96.3992 can initiate an off-line spend transaction (requiring off line confirmation).

---------

For the subsequent part of this mutual project with the friend's computer:
To separate out BCH from each of the respective legacy BTC positions
(last transaction mid July 2017 successfully tested consolidation of two wallets with Armory 0.96.0.4), 
should one follow the sequences within the prior thread re Armory 0.96.3?:

Install Bitcoin ABC database on a different machine, etc? 
Will one also use Armory 0.96.3992 to sync the Bitcoin ABC database on the separate computer?
Follow the remaining sequences on the earlier thread for the separation of BCH from the legacy BTC? 

----

Independent question:
Should Bitcoin Core 0.15.1 and Armory 0.96.3992 install with equal facility on a
Win 7 x 64 computer  (2TB HDD & 8GB Ram) as on this Win 10 x 64 computer (same size HDD and Ram)? 
I presume it will be necessary to first uninstall all the prior Armory 0.93.3 and respective bitcoin core files.

TY all for your assistance and continued suggestions.   

TY for confirming that bitcoin core 0.15.1 should be OK

Following a non successful attempt to install Armory 0.96.3992 these are the two most current Log files

https://pastebin.com/eA1zP2gr  and   https://pastebin.com/D77ejppq 

Copy of the install pop up messages are as follows:

 

"Error opening file for writing"

C:\Program Files (x86)\Armory\PyQt4.QtCore.pyd

Click Abort to stop the installation
Retry to try again, or
Ignore to skip this file

<Clicked the Retry button on the Win Pop up >

Hangs at Extract: MSVCP.90dll... 100%

<Following is indicated on the installation progress pop up: >

Output folder:C:\ProgramFiles(x86)\Armory
Delete file:C:\ProgramFiles(x86)\Armory\ArmoryDB.exe
Delete file:C:\ProgramFiles(x86)\Armory\MSVCP90.dll
Extract:ArmoryDB.exe... 100%
Extract:MSVCP90.dll... 100%       

<Clicked Abort - Pop up now indicates >

Installation Aborted
Setup was not completed successfully.

Can't write C:\ProgramFiles(x86)\Armory\PyQt4.QtCore.pyd

<With the install progress indication as >

Output folder:C:\ProgramFiles(x86)\Armory
Delete file:C:\ProgramFiles(x86)\Armory\ArmoryDB.exe
Delete file:C:\ProgramFiles(x86)\Armory\MSVCP90.dll
Extract:ArmoryDB.exe... 100%
Extract:MSVCP90.dll... 100%
Can't write C:\ProgramFiles(x86)\Armory\PyQt4.QtCore.pyd

TY for the continued assistance.

TY droark

Is there a remedy regarding the "hangs" for Win 10.  My friend's ISP mandates a windows computer,
as does my personal ISP for my own net connection (my ISP different from that of the friend). 

Do we need to do a forced shut down of Armory 0.96.3991 when it is in the "Hangs" mode? 

<Holding off on other computer upgrades until the Win 10 x 64 friend's Armory is operating> 


Does the above error require a complete reload of the Bitcoin core 0.15.1 database? 
If so, does one need to delete the C:....AppData\Roaming\Bitcoin.... folder? and reload from scratch?
Or is there a shorter duration remedy?

Thank you for your continued assistance. 

TY for the assistance (& encouragement) replies.

These have been your suggestions

primary reply to my inquiry after receiving my ArmoryLog and dbLog files:

<From the looks of your dbLog, it seems ok. To be on the safe side, once the Bitcoin node issue is fixed, delete your databases folder for the good measure before running Armory again (C:\Users\Owner\AppData\Roaming\Armory\databases)>

reply to my action confirmation inquiry:


<1) Delete the databases folder as instructed

2) Turn off auto bitcoind in Armory, under File -> Settings.

3) Start BitcoinQt manually, then Armory.>

------

My actions:

databases folder deleted from the ...AppData\Roaming\Armory folder
within Armory 0.96.3991 File -> Settings "auto bitcoind" has been turned "off" (unchecked from that option choice)

Bitcoin core 0.15.1 has been started and sync'd (and presently remains active).
Armory 0.96.3991 was started

The initial "Armory Loading" (rounded corner rectangle) green progress bar indicates 100% loaded
It then hangs there with zero further action into the opening page of actual Armory

The opening page of Armory remains absent.
(preparing databases progress bar, Loading Database Headers, Scanning Transaction History, nor wallet consistency check progress bars). 

All is stuck on the opening rounded rectangle with the Armory logo. 

------

If further experiments are necessary, is there a best means to close the Armory rounded rectangle (absent a close button)? 

At present it will be necessary to use Glary Utilities Process Manager, or Windows Task Manager to close Armory QT. 

------

Once Bitcoin core 0.15.1 has been sync'd, should it be closed first before engaging Armory 0.96.3991 ? 
as stated, it remains active when I activated Armory 0.96.3991 and now stuck in this "hanging" mode
(opening logo page stuck with 100% loaded displayed for the initial progress bar at the top of the rounded corner rectangle).

TY for your continued assistance.

(and TY for the warning re the computer shop - and from your push I did find the correct info to view the "Hidden Files")
2 computer implementation and full paper (encrypted print) backups have been the modus operandi for myself going back to my initial load of Armory in late 2013 - same implementations with my local area friend. 

TY for examining the conditions of the log files.  

Bitcoind 0.15.1 is loaded to the default location, as is Armory 0.96.3991
Bitcoind 0.15.1 always self-syncs when opened, again confirmed as I was typing this reply.  

Let me know if there is any other information you need.  

TY again for your kind and quick response.  

------

FYI, This evening (and Saturday, Sunday) schedules will keep me fully away from the friend's computer until sometime on Monday.

----  

added info re my experiences over the years, is the observation of how the database fragments the files on the hard drive, and for
which I regularly run the Glary Utilities program routine to defrag and re-optimize the file locations (typically with a defrag once or
twice per week; plus the defrag and optimize routine circa every week to 10 days).  

We have an additional computer set operating Armory 0.96.0.4 along with bitcoin core 0.14.2 (from mid July 2017, pre fork).
This is the initial step toward upgrading all of our Armory wallets and databases to the most current versions.

TY for the warning.  I have a personal Armory Wallet going back to late 2013 with the On Line/Off Line configuration - updated through 0.93.3 - late 2017 updated to a higher speed net connection, appropriate speed for an upgrade with the latest Armory & BC core. 

Early 2017 I introduced the local area friend to Bitcoins and we have a mutual project through his fast cable modem and Win 10. 

A decade back I knew how to find the hidden files but hadn't the need to do so over the subsequent duration.  I did re-find the info about opening the View options for the hidden files and got the txt files you desire this morning from the friend's computer. 

https://pastebin.com/7UEH61N2 and https://pastebin.com/UkHnaMsE

- yes, yours is a valid criticism re one who continues to prefer analog, yet with some coin positions going back to early 2014.  Thus the "non geek" ID

TY for the assistance.

TY for the specifics of the log files needed. 

At present I don't have admin access to any folders deeper than C:\users\owner\  and the customary windows folders

Cheating (using a paused defrag from Glary Utilities) I can see that the files are stored within
  C:\users\owner\AppData\Roaming\Bitcoin\chainstate\  then the unique respective files

We have a plan to visit the computer shop Friday morning (show them this thread) ask for the keys to admin access,
and also have them assist us to get both the most recent (complete) armorylog.txt and dbLog.txt files & get them into
pastebin - where we can enter them here. 

TY for both your assistance and your patience, while my friend and I get the txt logs you need (entered here via pastebin). 

This is copied from an assistance inquiry incorrectly entered to the development thread re 0.96.4 RC2

actions report re the update to the friend's computer:

I found the link for Armory 0.96.3.991 and installed to the friend's Win 10 x 64 computer.

The load in of 0.96.3991 successfully interfaced and upgraded the 0.96.3 already installed, retaining the watcing only "offline" security status of the wallets already installed (with non correct zero balance indicated for each of the watching only copies of those on line wallets).  

Bitcoin core 0.15.1 had already been installed and synced to itself.

Once Armory 0.96.3991 was loaded various experiments were attempted:

1) close BC core 0.15.1, and then start 0.96.3991 - result 0.96.3991 continued to not sync to BCcore 0.15.1

2) open core 0.15.1 first and then start 0.96.3991 - same result of 0.96.3991 not syncing to Core 0.15.1

3) open 0.96.3991 first and then attempt to open CoredB 0.15.1 - result 0.15.1 opened and self synced but absent any correlation to 0.96.3991 - also missing any conflict error messages about 0.96.3991 already accessing the CoreDb (ie to the effect that only one copy of CoredB can be open at one time).

----

Throughout all the above experiments with 0.96.3 and now with 0.96.3991 the watching only wallets are not synced to the CoreDb 0.15.1 and all indicate a zero balance.  

Thank you for your assistance. Is there a different version of Armory which should be installed beyond 0.96.3991 in order to sync Bitcoin core 0.15.1
(after the Bitcoin core 0.15.1 has self synced to itself)?

Or is there a necessary different procedure of install (as in the older versions 0.93.3 and earlier - where Armory was first installed and then Armory needed to complete the full self sync of the BCcore database) so the wallets will sync and indicate their balances?

----

There are requests by the admins here to post the log files, and droark suggested using PasteBin, 0Bin, CryptBin, etc, for the transmission of those log files.  

----

Non geek here, with left brain training in fields outside of IT.  


Do I look for the log files from the "Open Program" commands used by Win 10? Or do you need the copy of the code entry which input into Win 10 when I downloaded the "exe" file?  

As a non geek, what commands does one enter/activate from Win 10 to observe and copy these log files.  

TY for your help - where I'm happy to send you the Log files which you need (once I learn how to find them).

Done

I very much appreciate the assistance.

TY droark,

Do I upload from the open Armory command, or upload it from the win 64 exe file (linked at the top of this thread)?  

As a non geek, left brain trained in other fields, I appreciate the help along - so I can assist you folks.

Apologies for entering my questions to what seemed the most appropriate place thread.
where does one find the log files to post?

I will be pleased to copy them and enter them here.    

TY kindly

actions report re the update to the friend's computer:

I found the link for Armory 0.96.3.991 at the top of this thread and installed to the friend's Win 10 x 64 computer. 

The load in of 0.96.3991 successfully interfaced and upgraded the 0.96.3 already installed, retaining the watcing only "offline" security status of the wallets already installed (with non correct zero balance indicated for each of the watching only copies of those on line wallets).   

Bitcoin core 0.15.1 had already been installed and synced to itself. 

Once Armory 0.96.3991 was loaded various experiments were attempted:

1) close BC core 0.15.1, and then start 0.96.3991 - result 0.96.3991 continued to not sync to BCcore 0.15.1

2) open core 0.15.1 first and then start 0.96.3991 - same result of 0.96.3991 not syncing to Core 0.15.1

3) open 0.96.3991 first and then attempt to open CoredB 0.15.1 - result 0.15.1 opened and self synced but absent any correlation to 0.96.3991 - also missing any conflict error messages about 0.96.3991 already accessing the CoreDb (ie to the effect that only one copy of CoredB can be open at one time). 

----

Throughout all the above experiments with 0.96.3 and now with 0.96.3991 the watching only wallets are not synced to the CoreDb 0.15.1 and all indicate a zero balance.   

Thank you for your assistance. Is there a different version of Armory which should be installed beyond 0.96.3991 in order to sync Bitcoin core 0.15.1
(after the Bitcoin core 0.15.1 has self synced to itself)? 

Or is there a necessary different procedure of install (as in the older versions 0.93.3 and earlier - where Armory was first installed and then Armory needed to complete the full self sync of the BCcore database) so the wallets will sync and indicate their balances?

Again, TY for your kind assistance. 

TY for your assistance on this question which I think I have now posted to the correct thread:

Now updating a friend's Win 10 computer, which formerly had Armory 0.93.3 and an old Bitcoin core database.  Both of them fully deleted and scrubbed.  


Installed Armory 0.96.3 to his Win 10 off line computer, and also to his on line desktop (Win 10).  Installed the new Bitcoincore 0.15.1
database to the friend's desktop.  Per a successful summer 2017 experiment (re Armory 0.96.0.4 with bitcoin core 0.14.2) I let the BC core 0.15.1 fully sync itself before attempting to sync with Armory 0.96.3.  

Armory 0.96.3 seems to recognize that the BCcore 0.15.1 database might be present, but does not sync properly to the 0.15.1 data base.  

All paperbackups successfully installed into the off line Armory 0.96.3 and watching only copies also indicate correctly to the On Line Armory 0.96.3.  The watching only On Line wallets have been identified as "This Wallet Is Mine" under Wallet Properties (and where the On Line Armory 0.96.3 now correctly indicates Offline Security for each respective "Watching Only copy").  Balance continues to indicate as zero for each of those wallets.  

Is there some other procedure needed to be performed for those wallets to indicate their balances and for Armory 0.96.3 to be fully synced to core datebase 0.15.1  

Each time Armory 0.96.3 is activated it does not update the BCcore 0.15.1 database (which only updates when Armory is closed, and BCcore is separately opened)

TY for your assistance.

Replying to the multiple topics in this thread:  (for purpose of separating BCH from legacy BTC) and upgrading to the most recent workable versions of Armory (which will address and separate out BCH from legacy BTC).  

The last Armory transaction occurred on July 19, 2017 (pre fork) moving some pre-fork BTC between two different Armory 0.96.0.4 wallets (for the confirmation where that version of Armory had been successfully installed - with Bitcoin Core 0.14.2).  

The early summer 2017 successful install of BCCore 0.14.2 and Armory 0.96.0.4 seemed to have opposite sequence for successful sync (than the former 0.93.3) where the BC core 0.14.2 was synced first to itself; then Armory 0.96 (and subsequent 0.96.0.4) all easily synced to the full 0.14.2 bitcoin core database.

---

Present questions:

Now updating a friend's computer, which formerly had Armory 0.93.3 and an old Bitcoin core database.  Both of them fully deleted and scrubbed.  

Installed Armory 0.96.3 to his former off line computer, and also to his on line desktop (Win 10).  Installed the new Bitcoincore 0.15.1
database to the friend's desktop.  Per early summer 2017 experience I let the BC core 0.15.1 fully sync itself.  Armory 0.96.3 seems to
recognize that the database might be present, but does not sync properly to the 0.15.1 data base.  

All wallets successfully installed into the off line Armory 0.96.3 and watching only copies also indicate to the On Line Armory 0.96.3.  The 5 watching only On Line wallets have identified as "This Wallet Is Mine" (and where the on line Armory now correctly indicates Offline for Security).  Balance continues to indicate as zero for each of those wallets.  

Is there some other procedure needed to be performed for those wallets to indicate their balances and for Armory 0.96.3 to be fully synced to core datebase 0.15.1?  

---

2nd task regards separating the BCH in each of those wallets into a separate system.  Once the above Armory 0.96.3 is fully synced for all wallets, is it necessary to use an external hard drive (or other computer) and install the Bitcoin ABC database also with Armory 0.96.3 as the driver for that database? and from which one can separate out the BCH from each respective legacy BTC wallet?  (per some of the forum comments above).  

Thank you for your assistance.  

We're now into just square one of the separation process (installing the most recent versions of Armory with the most recent BC core databases).