Ancestral Sources Data Entry

Post by **tatewise** » 17 Dec 2013 15:11

I have been working on a new version of this Plugin to automatically extract the AS Version and AS Installation Path from the Windows Registry.
Previously it used other devious methods, and sometimes had to prompt the user for the AS Installation Path.
Unfortunately, different versions of Windows store the data in different places in the Registry.
I have checked my versions of Windows XP, Vista, and 7 but it would help if others were checked before the Plugin is published.

Please download and install the Plugin from my SkyDrive Ancestral Sources Data Entry.
It is version 3.3 with a brand new user interface, and will overwrite your current version.
Version 3.2 can easily be restored from the Plugin Store if necessary.

I am particularly interested in other versions of Windows and non-standard installations that do NOT use C:\Program Files\Ancestral Sources\.

johnmorrisoniom · Post by **johnmorrisoniom** » 17 Dec 2013 23:18

Hi Mike,
The new version worked alright on my XP desktop, but I got an error message on my W7 Laptop.

: AS3,3 Error.JPG (22.74 KiB) Viewed 13316 times

I re-installed ver 3.2 and it ran OK, then re-installed 3.3 and got same error.

Post by **tatewise** » 18 Dec 2013 00:26

That was not the sort of error I expected as it runs OK on my Windows 7 Home Premium Service Pack 1 64-bit OS desktop with the 64-bit version of AS installed in C:\Program Files\Ancestral Sources\.

How does your Win 7 laptop differ from that configuration?

I have made a small change and added some extra trace error message details to the Plugin via the same SkyDrive link above that might give some more clues if you could please run it again and post the error message if it still occurs.

johnmorrisoniom · Post by **johnmorrisoniom** » 18 Dec 2013 07:53

Hi Mike,
I still get exactly the same error. My laptop is a standard pre-installed W7 version same as yours. I have also tried on my other desktop, which is W7 Pro 64 bit SP1. I get the same error.
My desktop W7 machine has had "Documents" moved to Drive D:

YouTube · Post by **Jane** » 18 Dec 2013 08:54

I get the same error.

It gets through to 1636 but
That returns nil, calling the reg key outside of the pcall results in
COM exception:(.\src\library\tLuaCOM.cpp,394):Invalid root in registry key "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ancestral Sources_is1\InstallLocation".

How ever my registry contains:

Code: Select all

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ancestral Sources_is1]
"Inno Setup: Setup Version"="5.4.2 (a)"
"Inno Setup: App Path"="C:\\Program Files\\Ancestral Sources"
"InstallLocation"="C:\\Program Files\\Ancestral Sources\\"
"Inno Setup: Icon Group"="Family History\\Ancestral Sources"
"Inno Setup: User"="JANE"
"Inno Setup: Selected Tasks"=""
"Inno Setup: Deselected Tasks"="desktopicon"
"Inno Setup: Language"="en"
"DisplayName"="Ancestral Sources"
"DisplayIcon"="C:\\Program Files\\Ancestral Sources\\Ancestral Sources.exe"
"UninstallString"="\"C:\\Program Files\\Ancestral Sources\\unins000.exe\""
"QuietUninstallString"="\"C:\\Program Files\\Ancestral Sources\\unins000.exe\" /SILENT"
"DisplayVersion"="3.2.3.0"
"Publisher"="Nick Walker"
"URLInfoAbout"="http://www.ancestralsources.com"
"HelpLink"="http://www.ancestralsources.com"
"URLUpdateInfo"="http://www.ancestralsources.com"
"NoModify"=dword:00000001
"NoRepair"=dword:00000001
"InstallDate"="20130327"
"MajorVersion"=dword:00000003
"MinorVersion"=dword:00000002
"EstimatedSize"=dword:000018fa

I tried running FH in Admin mode, but that did not help.

Post by **tatewise** » 18 Dec 2013 11:24

Yes, the Windows Registry keys are weirdly inconsistent.
I have updated the Plugin via same SkyDrive link above, please try it out.

On my Windows 7 PC I have found:
"HKEY_CLASSES_ROOT\\Applications\\Ancestral Sources.exe\\shell\\open\\command\\" now used by the Plugin Line 1637, but does it work for you?
"HKEY_CURRENT_USER\\Software\\Classes\\Applications\\Ancestral Sources.exe\\shell\\open\\command\\" used by previous version but failed on your PC.
"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Ancestral Sources_is1\\InstallLocation" exists when viewed via regedit but Plugin getRegKey() returns nil.

On my Windows Vista & XP PC I have found:
"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Ancestral Sources_is1\\InstallLocation" exactly as for Windows 7 but works in Plugin Line 1643 via getRegKey() OK.
The other keys do not exist at all.

YouTube · Post by **Jane** » 18 Dec 2013 11:57

The plugin did not work.

Code: Select all

require "luacom"
function getRegKey(key)
    local sh = luacom.CreateObject "WScript.Shell"
    local ans 
    if pcall(function () ans = sh:RegRead(key) end) then
      return ans
    else
      return nil,true
    end
end

local list = {
"HKEY_CLASSES_ROOT\\Applications\\Ancestral Sources.exe\\shell\\open\\command\\",
"HKEY_CURRENT_USER\\Software\\Classes\\Applications\\Ancestral Sources.exe\\shell\\open\\command",
"HKEY_LOCAL_MACHINE\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Ancestral Sources_is1\\InstallLocation"
}

for k,v in ipairs(list) do
print(k,v)
print(getRegKey(v))
end

Returned

Code: Select all

1	HKEY_CLASSES_ROOT\Applications\Ancestral Sources.exe\shell\open\command\
nil	true
2	HKEY_CURRENT_USER\Software\Classes\Applications\Ancestral Sources.exe\shell\open\command
nil	true
3	HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ancestral Sources_is1\InstallLocation
nil	true
Plugin has completed

Post by **tatewise** » 18 Dec 2013 12:23

It still might not work but the HKEY_CURRENT_USER key needs a double backslash at the end i.e \\command\\"

The first two keys work OK on my Win 7 PC and the third one is OK on my XP & Vista PC - I said it was weird.

If you could do a full search of the Registry for Ancestral Sources\Ancestral Sources.exe or wherever you have AS installed that might reveal some more keys for the installation path.

YouTube · Post by **Jane** » 18 Dec 2013 14:10

The only place the path exists in my registry is the Uninstall Directory in HKLM. I can't seem to read any values from that directory using RegRead, but I can view and edit them with RegEdit.

I think the problem is

By default, if your process is running as a 32 bit process you will end up accessing the 32 bit "reflection" of
the remote system. Therefore, registry keys like HKLM\Software will actually be mapped to HKLM\Software\Wow6432Node
which gets very frustrating! You can access the 64 bit "reflection" via WMI, but personally I find that quite painful.

source: http://gallery.technet.microsoft.com/sc ... n-615fa73a

So if you have an x64 install of AS you won't find it looking from the 32bit FH.

Post by **tatewise** » 18 Dec 2013 14:38

I suspected it might be something to do with that 64/32-bit scenario.
I have tried the suggested HKLM\\SOFTWARE\\Wow6432Node\\Microsoft\\... path without success.

All I am trying to do is find the full installation path of AS so the Plugin can use fhShellExecute() without having to ask the user where AS is installed when it is NOT in the default C:\Program Files\ or C:\Program Files (x86)\ folders.

Any suggestions would be welcome.

If Nick Walker sees this, maybe it is possible that the next version of AS can save its installation path somewhere in HKCU\\Software\\Ancestral Sources\\00\\... which seems be accessible on all PC.

Could other users check that this is true by seeing what happens at Line 1642 where HKEY_CURRENT_USER\\Software\\Ancestral Sources\\00\\Version is read.

YouTube · Post by **Jane** » 18 Dec 2013 14:57

I did look at the vb scripts for using the method mentioned in the link, but I have not tried to reverse them so they could be done in Lua, personally I would try the default locations, then the registry and finally prompt the user, I suspect 99% of users will have AS installed in the default directory so only a very few would need to search for it.

Don't forget you can get the actual Program Files directories from the Environment variables.

Post by **tatewise** » 18 Dec 2013 15:31

Yes, that is what the current Plugin Store version does, but I had hoped it could be automated by reading the Registry keys.

Post by **tatewise** » 18 Dec 2013 17:19

I have found the AS installation path in various keys that the Plugin can obtain.
Does your PC have Ancestral Sources listed in any of these Registry keys:
"HKCR\\Local Settings\\Software\\Microsoft\\Windows\\Shell\\MuiCache"
"HKCU\\Software\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\Shell\\MuiCache"
"HKEY_USERS\\S-1-5-21-4109675573-1409003035-2569323029-1002\\Software\\Classes\\Applications\\Ancestral Sources.exe\\shell\\open\\command"
"HKEY_USERS\\S-1-5-21-4109675573-1409003035-2569323029-1002_Classes\\Applications\\Ancestral Sources.exe\\shell\\open\\command"
"HKEY_USERS\\S-1-5-21-4109675573-1409003035-2569323029-1002\\Software\\Classes\\Local Settings\\Software\\Microsoft\\Windows\\Shell\\MuiCache"
"HKEY_USERS\\S-1-5-21-4109675573-1409003035-2569323029-1002_Classes\\Local Settings\\Software\\Microsoft\\Windows\\Shell\\MuiCache"

For some of these there is a long list of installation paths and applications, but AS is in there along with FH.

YouTube · Post by **Jane** » 18 Dec 2013 19:27

No none of those. As I said I did a full search of my Registry and only found the one section with the folder name in.

Code: Select all

1	HKEY_CLASSES_ROOT\Applications\Ancestral Sources.exe\shell\open\command\
COM exception:(.\src\library\tLuaCOM.cpp,394):Invalid root in registry key "HKEY_CLASSES_ROOT\Applications\Ancestral Sources.exe\shell\open\command\".
nil	true
2	HKEY_CURRENT_USER\Software\Classes\Applications\Ancestral Sources.exe\shell\open\command\
COM exception:(.\src\library\tLuaCOM.cpp,394):Invalid root in registry key "HKEY_CURRENT_USER\Software\Classes\Applications\Ancestral Sources.exe\shell\open\command\".
nil	true
3	HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ancestral Sources_is1\Publisher\
COM exception:(.\src\library\tLuaCOM.cpp,394):Invalid root in registry key "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ancestral Sources_is1\Publisher\".
nil	true
4	HKCR\Local Settings\Software\Microsoft\Windows\Shell\MuiCache
COM exception:(.\src\library\tLuaCOM.cpp,394):Unable to open registry key "HKCR\Local Settings\Software\Microsoft\Windows\Shell\MuiCache" for reading.
nil	true
5	HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache
COM exception:(.\src\library\tLuaCOM.cpp,394):Unable to open registry key "HKCU\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache" for reading.
nil	true
6	HKEY_USERS\S-1-5-21-4109675573-1409003035-2569323029-1002\Software\Classes\Applications\Ancestral Sources.exe\shell\open\command
COM exception:(.\src\library\tLuaCOM.cpp,394):Invalid root in registry key "HKEY_USERS\S-1-5-21-4109675573-1409003035-2569323029-1002\Software\Classes\Applications\Ancestral Sources.exe\shell\open\command".
nil	true
7	HKEY_USERS\S-1-5-21-4109675573-1409003035-2569323029-1002_Classes\Applications\Ancestral Sources.exe\shell\open\command
COM exception:(.\src\library\tLuaCOM.cpp,394):Invalid root in registry key "HKEY_USERS\S-1-5-21-4109675573-1409003035-2569323029-1002_Classes\Applications\Ancestral Sources.exe\shell\open\command".
nil	true
8	HKEY_USERS\S-1-5-21-4109675573-1409003035-2569323029-1002\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache
COM exception:(.\src\library\tLuaCOM.cpp,394):Invalid root in registry key "HKEY_USERS\S-1-5-21-4109675573-1409003035-2569323029-1002\Software\Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache".
nil	true
9	HKEY_USERS\S-1-5-21-4109675573-1409003035-2569323029-1002_Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache
COM exception:(.\src\library\tLuaCOM.cpp,394):Invalid root in registry key "HKEY_USERS\S-1-5-21-4109675573-1409003035-2569323029-1002_Classes\Local Settings\Software\Microsoft\Windows\Shell\MuiCache".
nil	true
Plugin has completed

Post by **tatewise** » 18 Dec 2013 20:09

OK, so it's back to the drawing board.

BTW as you demonstrated, I know those Registry keys don't work with getRegKey(), so I was hoping to use a different technique with a Batch Command file running REG QUERY similar to my Backup and Restore Family Historian Settings Plugin (but only when all else fails).

But if those Registry keys don't even exist in your PC Registry then that technique won't work either.

I tried that REG QUERY technique on the HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall entire key, but that refused to include the 64-bit applications too.

Post by **tatewise** » 18 Dec 2013 21:09

I believe I have found a solution after much Google searching.

This Plugin code works on 32-bit PC and probably where AS 32-bit is installed on 64-bit PC.
getRegKey("HKLM\\SOFTWARE\\Microsoft\\Windows\\CurrentVersion\\Uninstall\\Ancestral Sources_is1\\InstallLocation")

This batch command works on 64-bit PC where AS 64-bit is installed - the /REG:64 qualifier does the trick.
REG QUERY "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Ancestral Sources_is1" /REG:64
I can use that with my Batch Command technique and read the file of keys to get the InstallLocation value.

I shall build those methods into the Ancestral Sources Data Entry Plugin tomorrow and let you all try it out.

[EDIT] New version is available ahead of schedule via SkyDrive link above.

YouTube · Post by **Jane** » 19 Dec 2013 09:00

That's now working fine, I am not a huge fan of the dialogue layout, but it works.

Post by **tatewise** » 19 Dec 2013 11:07

That Plugin version only checks that I've correctly reintroduced the tests for AS installed in the default C:\Program Files\ or C:\Program Files (x86)\ locations.

Please change Line 1703 so that the file path is incorrect, to test the Windows Registry code,
e.g.
local strPath = "\\AncestralSources\\AncestralSources.exe"

then the Plugin will skip the default locations and inspect the Windows Registry keys.
On a 32-bit PC or with 32-bit AS installed then getRegKey(HKLM) is performed invisibly.
On a 64-bit PC with 64-bit AS installed a brief Command Prompt popup runs REG QUERY HKLM /REG:64.

I'm sorry you are not a fan of the new GUI layout. The reasons for this new design are:

To eliminate the 2nd GUI needed when latest AS is not installed or installed in an unusual location.
To align the 7 data entry buttons horizontally to match the associated buttons in the AS toolbar.
To present the 4 ancillary buttons on the bottom row similarly to my other Plugins.

Is there any particular features that I could improve, such as hide the download button entirely when not needed.

YouTube · Post by **Jane** » 19 Dec 2013 13:20

That seems to work OK, I get the black screen and then the plugin starts.

For me the dialogue is too busy with many equal weight buttons (the old one just had the buttons I needed to launch AS.

I don't think you need a download button or the big bold message at the top unless there is a problem with finding AS.

To be honest I find several of your dialogues over large. I know you like to use the very large fonts AND LOTS of bold as all your font choices are the same size and none of them are the current windows default.

My personal preference is to keep the amount of buttons and information to a minimum, so for example I find the new search and replace dialogue over powering, I think it might have been better to keep it simple and included an advanced button (or tab) to allow the various sub types to be selected.

Post by **tatewise** » 19 Dec 2013 13:58

Eventually, in the published version, once the installation path has been discovered, it will be saved and the Registry will not be interrogated agian.

I appreciate your feedback regarding the GUI.
You are right, I should hide the download button, and unbold the top message when not needed.
Apart from the download button and top message, there is only one extra button (Restore Defaults) compared to previous versions, and they have always been equal weight.
I would say the AS data entry buttons are now slightly bigger and more prominent.

I accept that some dialogues are too busy, and could be simplified by adding tabs.

I will also have a look at increasing the font choices.
A difficulty with a wider range of font sizes is to get the GUI to behave correctly for all cases.
A problem that I, and clearly some others, suffer is reading the small default fonts, especially on larger higher resolution monitors.

The Search and Replace debate continues at Search and Replace - New Dialogue (10976).

Post by **tatewise** » 19 Dec 2013 23:25

There is an updated Plugin via the original SkyDrive link that implements some of the above suggestions.
It only uses bold for the top message when latest AS version is not installed.
It hides the download button and top message when not needed.
The Set Window Font button supports the Windows default user font.

Once the Plugin has determined the AS installation path it is saved, so the Windows Registry is not read again.
However, using the Restore Defaults button, or a change in the AS installation path, will invoke the process to determine the AS installation path again and may read the Windows Registry.

Post by **tatewise** » 03 Jan 2014 00:19

There is a revised version of this Plugin in SkyDrive Ancestral Sources Data Entry.

This adds several new concepts.

The installation path for AS is first assumed to be in C:\Program Files or C:\Program Files (x86) but if not then the Windows Registry is interrogated with getRegKey(HKLM), or finally using a brief Command Prompt popup to run REG QUERY HKLM /REG:64. The path is saved to avoid subsequent interrogation.
The Set Window Fonts button now supports all available Fonts and Colours, with the Plugin Window automatically increasing with larger Fonts, and a Minimum Size button to shrink the Plugin Window for smaller Fonts. Users can alter the Plugin Window size, but its minimum size is set automatically by the current Fonts.
The Plugin saves the Font & Colour & Window placement settings in the per User Plugin Data. The AS Installation Path is saved in the per Machine Plugin Data whereas the Close on Save Entry setting is saved in the per Project Plugin Data. This shows how a user can configure a Plugin once and the settings are applied to all Projects or Machine wide, but still allow per Project settings..
The bulk of the features above, and some others to simplify constructing GUI using IUP, are implemented by a standard library module used by all my Plugins from now on, and potentially available to everyone.

[EDIT] I have updated the SkyDrive link above.

Post by **Valkrider** » 03 Jan 2014 07:50

Mike,

Wrong url for the new version Skydrive says it isn't there.

johnmorrisoniom · Post by **johnmorrisoniom** » 03 Jan 2014 09:21

I have installed it OK.

Post by **NickWalker** » 11 Jan 2014 13:01

tatewise wrote: If Nick Walker sees this, maybe it is possible that the next version of AS can save its installation path somewhere in HKCU\\Software\\Ancestral Sources\\00\\... which seems be accessible on all PC.

Mike

The next version of Ancestral Sources will record the application path under a string value App Path under the 00 key.

Best wishes

Nick

Family Historian User Group

* Ancestral Sources Data Entry

Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry

Re: Ancestral Sources Data Entry