Ch, ch, ch, Changes . . . tracking for APP embed code

I ran ProcessMonitor on the BO Tpl 9.1 installer, the screen capture is below. It shows it finds 9.1 by reading GUID Registry key to get the InstallLocation

10:02:09.1874616 AM	BoTpl44SU.exe	26264	RegQueryValue	
HKLM\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall\{5FBB5960-7EDC-11E3-3D6C-05B078044AE1}\InstallLocation	
SUCCESS	Type: REG_SZ, Length: 26, Data: D:\Clarion91

That GUID matches what I see in the 9.1 Uninstall log. Other RegMon RegQueryValue entries match to 9.0 and 8.0 GUID’s from my logs. I did not install them on this machine but I have the folders and logs, so the BoTpl setup did not find 8 and 9.0.

So it would be easy to make a 8,9,9.1 Fake Installer to create those keys (PUTREG) and the empty folders (MkDir). The remaining question is what is being read from ClarionProperties.xml and does it matter? I’m sure Fred would tell us. I would guess it is the BoTpl product looking for its own info.