* Crossover Test Reg Access

[tatewise]

This thread is aimed at Crossover users of FH.

Please run the ATTACHMENT TestRegAccess Plugin Version 1.1 Date 02 Apr 2016.
[EDIT: ATTACHMENT now deleted.]

It should try and perform a multi-line REG QUERY similar to the Backup and Restore FH Settings plugin.
But will probably fail with a ~ Registry Query Error ~ message box saying not saved and no bytes...
There will also be a ~ Backup & Restore multi-line REG QUERY ~ message box giving File Size and Family Historian Version.
But if following the failure message, those details will be blank.

Then it performs some getRegKey workarounds similar to the Backup and Restore FH Settings plugin.
If it works, there will be a ~ Backup & Restore alternative getRegKey ~ message box giving Build number and Family Historian Version.
If it fails, then those details will be blank.

[Valkrider]

Mike

I have combined the 4 output screens in one image below. I hope that it helps. (Still on v6.1.4 on the laptop).

errors.jpg (54.51 KiB) Viewed 10326 times

[tatewise]

Colin,
I think you have run the old TEST REG ACCESS plugin dated 04 Jan 2015 (note spaces in ALL CAPS title), instead of the new ATTACHMENT TestRegAccess plugin dated 02 Apr 2016 (note no spaces in Title-case title).

[Valkrider]

Mike

As usual you are right. I have deleted the old plugin. New results below

Screen Shot 2016-04-04 at 5.38.58 PM.png (19.49 KiB) Viewed 10321 times

Screen Shot 2016-04-04 at 5.39.12 PM.png (19.47 KiB) Viewed 10321 times

[tatewise]

Thank you Colin, that seems to confirm what I expected, so could you please try the ATTACHMENT Backup and Restore Family Historian Settings Plugin Version 2.4.1 Date 03 Apr 2016, which should now work for the ProgramData and other files, but not for the Windows Registry just yet.
[EDIT: ATTACHMENT now deleted.]

[Valkrider]

Mike

That seems to work with v6.2.

Screen Shot 2016-04-04 at 7.43.29 PM.png (37.53 KiB) Viewed 10308 times

[tatewise]

That is an excellent step in the right direction.
If you are happy to try it, then Restore should also work, just for Program Data Files, and not Windows Registry.
You can Skip Operation rather than restore Program Data Files if you prefer.
The Tutorial Files and Registry Data Keys buttons should be greyed out.

However, that just proves the Plugin can tell when to use the RegRead method instead of Reg Query.
It is only reading a few specific Registry keys to determine the FH Version.

The next step is to check that the RegWrite method also works so that Registry keys can be restored.
Then there must a way of running a batch script full of RegWrite commands after closing the Plugin and FH.

When I have written a test Plugin to check those features, I will post another ATTACHMENT again.

[tatewise]

This thread is aimed at Crossover users of FH and checks writing to the Registry, but it only modifies the Tools > Preferences > Maximum Undoable Actions.

Please run the ATTACHMENT TestRegAccess Plugin Version 1.3 Date 05 Apr 2016.
[EDIT: ATTACHMENT now deleted.]

It performs some getRegKey commands similar to the Backup and Restore FH Settings plugin.
If OK, there will be a ~ Backup & Restore alternative getRegKey ~ message box giving Build number and Family Historian Version.
If it fails, then those details will be blank.

It then performs one putRegKey command using RegWrite method.
If OK, there will be a ~ Backup & Restore alternative putRegKey ~ message box saying RegWrite: Max Undos 33.

It then performs a VBScript with one putRegKey command using RegWrite method.
There should be a popup prompt asking Continue with VBS? so click Yes button.
If OK, there will be a ~ Backup & Restore alternative vbsRegKey ~ message box saying RegWrite: "Max Undos"=30.

[Valkrider]

Mike

All OK to start with then no popup for VBS was shown then the following error messages shown.

Screen Shot 2016-04-06 at 2.24.52 PM.png (19.88 KiB) Viewed 10216 times

Screen Shot 2016-04-06 at 2.25.47 PM.png (18.29 KiB) Viewed 10216 times

[tatewise]

Colin,
That is disappointing as it looks like Visual Basic Scripts (VBS) do not work in Crossover.
I cannot delve deeper just now as the Codeweavers website appears to be off-line.

If that won't work, then I am struggling to think of how to restore Window Registry settings.

I can save the Window Registry settings using the RegWrite method within the Plugin.
But to restore them needs something to run outside FH after it has closed (such as a Batch or VBS script).
The only other alternative is a manual use of RegEdit to import the saved Window Registry settings file.

[Valkrider]

Mike

I think that VBS does run under Crossover, maybe it needs to be specified in the Bottle. I will check that out. If the manual edit of the registry maybe what is required I don't think that is the end of the world, not as convenient but not a show stopper imho.

[tatewise]

It should only need the Windows Script Host that is installed already.
But maybe the method of running the VBS batch file is not compatible with Crossover.
I use:
Run('cmd.exe /C "batch.vbs"', 2, true)

[tatewise]

Colin, please run the ATTACHMENT TestRegAccess Plugin Version 1.4 Date 13 Apr 2016.
[EDIT: ATTACHMENT now deleted.]

It runs much as before, but does not issue any prompts, and just reports Registry keys.

It uses a modified way of invoking the VBS script from within a BAT script.

[Valkrider]

Mike, will do and will report back tomorrow.

[Valkrider]

Mike

Same as before I think.

Screen Shot 2016-04-14 at 12.40.23 PM.png (20.96 KiB) Viewed 10090 times

Screen Shot 2016-04-14 at 12.40.35 PM.png (22.66 KiB) Viewed 10090 times

Screen Shot 2016-04-14 at 12.40.50 PM.png (23.04 KiB) Viewed 10090 times

[tatewise]

Thanks Colin, yes that shows the VBS script is not working.
If it did, the last popup would say Max Undos 29 instead of 35.

So please try this variant ATTACHMENT TestRegAccess Plugin Version 1.5 Date 14 Apr 2016.
[EDIT: ATTACHMENT now deleted.]

[Valkrider]

Mike

That seems to be working now.

Screen Shot 2016-04-14 at 4.21.21 PM.png (21.5 KiB) Viewed 10076 times

[tatewise]

BINGO ! ! !

That should let me eventually unleash a comprehensive Backup and Restore for the Crossover Windows Registry, although it involves a table driven technique where all known FH Registry Keys have to be manually compiled and updated with each new FH version.

I just need to run one more test Plugin that runs the BAT/VBS script after closing FH similar to the BaRFHS plugin.

[Valkrider]

Great, well done, looking forward to getting it for testing.

[tatewise]

Colin, please try variant ATTACHMENT TestRegAccess Plugin Version 1.6 Date 15 Apr 2016.
[EDIT: ATTACHMENT now deleted.]

The first two popup windows should be the same as before and writes Max Undos 35.

Then it mimics the BaRFHS Plugin with a Close Program WARNING popup with two buttons.
Click either button and the Plugin will close leaving a black Command Prompt window on display.

In FH check:
Tools > Preferences > General > Maximum Undoable Actions: is 30 or your preferred setting.
Tools > Preferences > File Load/Save > Exclude fields that are not valid for Gedcom 5.5 is NOT ticked.

Close FH and then enter Y to Command Prompt window and press Enter key.

Open FH and check:
Tools > Preferences > General > Maximum Undoable Actions: 29.
Tools > Preferences > File Load/Save > Exclude fields that are not valid for Gedcom 5.5 is ticked.
Reset them to Installation Settings of 30 and unticked respectively.

[Valkrider]

Works exactly as you said it would. Well done.

[tatewise]

OK Colin, one last check to see if Registry Data Keys can be exported using VBS to mimic the REG EXPORT command.

Try variant ATTACHMENT TestRegAccess Plugin Version 1.7 Date 16 Apr 2016. [EDIT: ATTACHMENT now deleted.]

The first popup window should be the same as before and report FH Build and Version.

Then it should display a black Command Prompt window that lists various HKEY_CURRENT_USER and HKEY_LOCAL_MACHINE key values such as "Hide Splash Panel"="TRUE". This mimics the Registry.keys file found in the Plugin Backup Data folder, but just for a few sample values.

Press any key to close the Command Prompt window.

[Valkrider]

Mike

Yes that works too.

Screen Shot 2016-04-16 at 1.03.02 PM.png (39.82 KiB) Viewed 10004 times

[tatewise]

OK, thank you, that should give me enough to work on for a reasonably full Registry Backup and Restore for the currently installed Family Historian version, that is compatible with the Windows PC version.

It may eventually be possible to cater for other installed versions such as Family Historian Demo 3.0 and Family Historian x.y Beta test versions, assuming they run in Crossover.

When I have a working prototype I will be back!

[tatewise]

Well I think I have a working Backup and Restore Family Historian Settings Plugin Version 2.4.3 Date 21 Apr 2016 that might run in Crossover. [EDIT: ATTACHMENT now deleted.]

It should behave exactly the same as the native Windows version, with one small exception:
Custom Named List columns will not Backup if that Named List does not exist in current Project.

It should even be possible to migrate Backup Data from Crossover to Windows and vice versa.

The first step is to perform a Backup and compare the Backup Data folders & files with the native Windows equivalents.

If that all looks good, then try a Restore at least up to the Command Prompt where you can always use N to escape.

If you decide to fully test the Registry Data Keys, then with the Command Prompt displayed, change some FH Preferences and Records Window columns before closing FH, and then enter Y to the Command Prompt.
When FH is reopened its Preferences and Records Window columns should have been restored.

If anything misbehaves, then on the Options tab there is the Enable Diagnose Mode setting that leaves behind script and data files that we can examine.

Good luck.