Would you please check whether there is an entry in one of the registry keys mentioned in the source that would match your missing installation? Cause it's a bit of a heuristic that's going on there and it might not be accurate enough... And are you on Windows 32- or 64-bit? If the later are you compiling as 32- or 64-bit?
I'm 100% sure as to what you are asking there. I've just used RegEdit and can see an entry [wow6432Node] but don't see any entry under that for FPC or Lazarus.
I had said that you should look in the registry keys I had mentioned in the source, cause I couldn't look it up right now, so here is the full keys you need to look at:
- HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall
- HKEY_LOCAL_MACHINE\SOFTWARE\WoW6432Node\Microsoft\Windows\CurrentVersion\Uninstall
This is where the utility finds the installations and where Windows also retrieves them from for display in the
Uninstall control pane. The installations themselves are subkeys and values like
Publisher of these are the ones looked at.
My system is 64 bit and I normally compile for 32bit but for your program I made no changes to the [Options] -- ie. the Target platform entries are all [Default].
That is not enough information, cause I don't know what the
Default setting of your Lazarus is as this doesn't depend on your host system but on whether you have installed the 64- or 32-bit version of Lazarus.
[EDIT]
After a little more research, I've found a reference to 'Lazarus.AssocFile.lfm' (plus .inc, .lpi etc.) under [HKEY_CLASSES_ROOT] and these all point to the Laz 1.6 installation. There is also an entry for FPCPASFile etc. As suggested, when I installed Laz 2.2 as a 'secondary install', I purposly told it to NOT associate files so am wondering if that may be the reason for your program not to find FPC3.2.2
The file associations are not relevant for this, though this could indeed be used to find out whether there are
remnants of an installation (but that's not the purpose of my tool).