Signalman7500 Posted August 1, 2018 Report Posted August 1, 2018 (edited) Having no problems with fsuipc. Just a technical question. I recently re-installed fsupic v. 4.955c (registered) and was looking at the FSUIPC4 Install.log and found the following: "Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=E:\Flight Simulator X\" Just out of curiosity, I opened up the registry editor and clicked the path as listed in the log above. I got as far as "HKEY_LOCAL_MACHINE_SOFTWARE. But "'Microsoft\Microsoft Games\Flight Simulator\10.0" was not listed. Eventually, I did locate "HKEY_CURRENT_USER\Software\Microsoft\Microsoft Games\Flight Simulator\10.0". So my question relates to the apparent discrepancy of what was reported in the FSUIPC log and what I found when I checked the registry on my computer. That is, the FSUIPC installer, according to the log, found the reference to Flight Simulator X in "HKEY_Local Machine but when I checked the Registry on my computer, the Flight Simulator X entry was located in HKEY_Current_User. Thanks Bob Edited August 1, 2018 by Signalman7500
Pete Dowson Posted August 1, 2018 Report Posted August 1, 2018 1 hour ago, Signalman7500 said: "Looking in registry for FSX install path: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0 Parameter"SetupPath" ... >>> OK! FOUND FSX! <<< ... SetupPath=E:\Flight Simulator X\" Just out of curiosity, I opened up the registry editor and clicked the path as listed in the log above. I got as far as "HKEY_LOCAL_MACHINE_SOFTWARE. But "'Microsoft\Microsoft Games\Flight Simulator\10.0" was not listed. 64-bit Windows re-maps the registry entries for 32-bit programs to "Wow6432Node", so the actual path seen in the Registry Editor is: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft Games\Flight Simulator\10.0 This mapping is invisible to the programs accessing the registry, though they can be explicit if they want (I think! Never tried, as I like to keep it compatible with32-bit Windows versions). If the Installer doesn't find it there it will look in the Current User place. But I think the parameter is different there (InstallPath)? Pete
Signalman7500 Posted August 2, 2018 Author Report Posted August 2, 2018 OK thanks Pete, for the information.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now