Cannot register FSUICP4...

[birdguy]

I'm trying to register FSUICP into FSX_SE which I recently installed.  It installs bit I can't register it.  When I try to register it it says it regoistered OK.  Then I press confirm.  But when I brng up the simulator it tells me it's an unregistered copy.

You will not the last section of the install log confirms the registration.

Installer for FSUIPC4.DLL version 4.972

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX\

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX

************ BUT this is the same path as for FSX! Will only install for FSX-SE ************

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX-SE:
SetupPath="D:\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 62615 (Steam)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... Version 4.972 found.
FSX-SE Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
Found FSX_SE.CFG in "C:\Users\birdg\AppData\Roaming\Microsoft\FSX-SE\FSX_SE.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "The 2016 List of FSX and P3D Controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC REGISTER
Providing FSUIPC registration dialogue ...
Registration for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************

 

Noel Sivertson

[Pete Dowson]

Please update to a supported version of FSUIPC, 4.974 or later.

Pete

 

[birdguy]

I did that Pete.  Same problem.  Here's the log:

Installer for FSUIPC4.DLL version 4.974

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX\

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX

************ BUT this is the same path as for FSX! Will only install for FSX-SE ************

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX-SE:
SetupPath="D:\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 62615 (Steam)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... No previous valid version found.
FSX-SE Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
Found FSX_SE.CFG in "C:\Users\birdg\AppData\Roaming\Microsoft\FSX-SE\FSX_SE.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "The 2016 List of FSX and P3D Controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC REGISTER
Providing FSUIPC registration dialogue ...
Registration for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************

 

[Thomas Richter]

Hi,

did you run the FSUIPC Installer with Administrator privilegs, right click on it and select 'Run As Administrator'?

Thomas

[birdguy]

I thought I had Thomas.  But just in case I deleted all the FSUIPC stiff from the module and installed it again as administrator.  Still no go.  While the nstallation log say's I'm registered and it seems to take when I register it when I'm the simulator it tells me it's an unregistered version.  Here's the last installation log.

Installer for FSUIPC4.DLL version 4.974

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX\

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX

************ BUT this is the same path as for FSX! Will only install for FSX-SE ************

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX-SE:
SetupPath="D:\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 62615 (Steam)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... No previous valid version found.
FSX-SE Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
Found FSX_SE.CFG in "C:\Users\birdg\AppData\Roaming\Microsoft\FSX-SE\FSX_SE.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
"Modules\FSUIPC Documents" folder created okay!
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "The 2016 List of FSX and P3D Controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC REGISTER
Providing FSUIPC registration dialogue ...
Registration for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************

 

Noel

[Pete Dowson]

Also, please show me the FSUIPC5.LOG file from the sim's Modules folder, if there is one. That'll be D:\Steam\steamapps\common\FSX\Modules. After all, that log would show what happened when you actually ran P3D --the Install Log merely shows a normal perfect install (and so far you have shown us what amounts to three identical copies except two for the current version and one for an out of date one).

In fact, please tell me what files, if any, you see in that Modules folder.

Finally, can we assume that you ARE actually running the FSX.EXE file which is in the D:\Steam\steamapps\common\FSX folder? Please check what you are actually executing. Because the install log shows nothing wrong, the Steam folders are certainly not protected in any way, unlike the "Program Files" folders, the Install log shows everything is perfect, and in fact nothing like this has ever been reported with and FSX-SE installation, so it simply isn't making sense. 

Pete

 

 

[birdguy]

Pete, I don't have a FSUIPC5.LOG.  And I no longer have P3D installed on my system.  Only FSX_se in the cam folder you mention in your reply.

My Modules Folder contains the following:

FSUIPC Documents Folder

AeroCore.dll

FSUIPC4 Install Log

FSUIPC4.DLL

FSUIPC4.key

FSUIPC4.Kodiak.ini

FSUIPC4.Kodiak.log

I started up with the Quest Kodiak.

Here is the installation log from the Modules Folder followed by the Kodiak log

Installer for FSUIPC4.DLL version 4.974

Looking in registry for FSX install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0
     Parameter"SetupPath"
... >>>  OK! FOUND FSX!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX\

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\DovetailGames\FSX
     Parameter"Install_Path"
... >>>  OK! FOUND FSX-SE!  <<< ...
     SetupPath=D:\Steam\steamapps\common\FSX

************ BUT this is the same path as for FSX! Will only install for FSX-SE ************

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v3 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v3
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX-SE:
SetupPath="D:\Steam\steamapps\common\FSX\"
Checking version of the FSX-SE EXE:
... Version 10.0.62615.0  (Need at least 10.0.62607.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 62615 (Steam)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL
... No previous valid version found.
FSX-SE Modules folder already exists.
Okay -- installed FSUIPC4 into "D:\Steam\steamapps\common\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX-SE\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
Found FSX_SE.CFG in "C:\Users\birdg\AppData\Roaming\Microsoft\FSX-SE\FSX_SE.CFG"
Now checking DLL.XML ...
... There is a previous DLL.XML, checking for FSUIPC4 section.
... FSUIPC4 section already exists but will be replaced.
     (for FSUIPC4, without Loader)
... FSUIPC4 section of DLL.XML written okay
Now checking for a SimConnect.XML file ...
... No SimConnect.XML file found. This is okay.
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX.CFG there
Looking for the current user's Application Data path:
... found as "C:\Users\birdg\AppData\Roaming"
Now finding \Microsoft\FSX\FSX_SE.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\birdg\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX_SE.CFG there
Looking in "C:\Users\Public\AppData\Roaming"
 ... No FSX_SE.CFG there
"Modules\FSUIPC Documents" folder created okay!
Now installing additional files into the "Modules\FSUIPC Documents" folder:
   Installed "FSUIPC4 User Guide.pdf" okay
   Installed "FSUIPC4 for Advanced Users.pdf" okay
   Installed "FSUIPC4 History.pdf" okay
   Installed "The 2016 List of FSX and P3D Controls.pdf" okay
   Installed "FSUIPC Lua Library.pdf" okay
   Installed "FSUIPC Lua Plug-Ins.pdf" okay
   Installed "Lua License.pdf" okay
   Installed "Lua Plugins for VRInsight Devices.pdf" okay
   Installed "LuaFileSystem.pdf" okay
   Installed "Example LUA plugins.zip" okay
   Installed "ASN WX Radar facilities in FSUIPC4.pdf" okay
   Installed "Offset Mapping for PMDG 737NGX.pdf" okay
   Installed "Offset Mapping for PMDG 777X.pdf" okay
   Installed "Offset Mapping for PMDG 747QOTSII.pdf" okay
   Installed "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
   Installed "FSUIPC4_Loader.dll" okay
===========================================================

All installer tasks completed.
Registration dialog exit: selected  FSUIPC REGISTER
Providing FSUIPC registration dialogue ...
Registration for FSUIPC4 was successful! (result code 00)

*************** End of Install Log ***************

FSUIPC4.Kodiak.log

********* FSUIPC4, Version 4.974 (24th February 2018) by Pete Dowson *********
Windows 10 Pro 64 Bit reported as Build 16299, Release ID: 1709 (OS 10.0)
Kodiak.exe version = 10.0.62615.0
Running inside FSX Steam Edition on Windows 10
... ESP has been renamed as "Kodiak"
Module base=52760000
User Name=""
User Addr=""
FSUIPC4 not user registered
WIDEFS7 not user registered, or expired
        0 System time = 07/04/2018 16:08:00
        0 FLT path = "C:\Users\birdg\Documents\Flight Simulator X - Steam Edition Files\"
        0 ------ Module Version Check ------
        0        acontain.dll: 10.0.62615.0
        0             api.dll: 10.0.62615.0
        0        controls.dll: 10.0.62615.0
        0      fs-traffic.dll: 10.0.62615.0
        0             G3D.dll: 10.0.62615.0
       16        language.dll: 10.0.62615.0
       16            sim1.dll: 10.0.62615.0
       16        visualfx.dll: 10.0.62615.0
       16         weather.dll: 10.0.62615.0
       16          window.dll: 10.0.62615.0
       16 ----------------------------------
       32 Trying to connect to SimConnect Steam ...
       47 FS path = "D:\Steam\steamapps\common\FSX\"
      141 LogOptions=00000000 00000001
      141 -------------------------------------------------------------------
      141 ------ Setting the hooks and direct calls into the simulator ------
      141 --- CONTROLS timer memory location obtained ok
      141 --- SIM1 Frictions access gained
      141 --- FS Controls Table located ok
      141 --- Installed Mouse Macro hooks ok.
      141 --- Wind smoothing fix is fully installed
      141 --- SimConnect intercept for texts and menus option is off
      141 --- All links checked okay
      141 -------------------------------------------------------------------
      141 SimConnect_Open succeeded: waiting to check version okay
      141 Trying to use SimConnect Steam
      141 Opened separate AI Traffic client okay
     8235 Running in "Microsoft Flight Simulator X", Version: 10.0.62615.0 (SimConnect: 10.0.62615.0)
     8235 Initialising SimConnect data requests now
     8235 FSUIPC Menu entry added
     8250 C:\Users\birdg\Documents\Flight Simulator X - Steam Edition Files\ZZZ_Kodiak.FLT
     8250 D:\Steam\steamapps\common\FSX\SimObjects\Airplanes\Kodiak\Kodiak.air
    12641 User Aircraft ID 1 supplied, now being used
    12641 Aircraft loaded: running normally now ...
   209719 System time = 07/04/2018 16:11:29, Simulator time = 10:02:44 (17:02Z)
   212657 Starting everything now ...
   213813 Advanced Weather Interface Enabled
   238938 Sim stopped: average frame rate for last 28 secs = 40.9 fps
   238938    Max AI traffic was 1000 aircraft (Deleted 0)
   253172 === Closing session: waiting for DLLStop to be called ...
   263407 === DLLStop called ...
   263407 === Closing external processes we started ...
   264422 === About to kill any Lua plug-ins still running ...
   265594 === About to kill my timers ...
   265594 === Restoring window procs ...
   265594 === Unloading libraries ...
   265594 === stopping other threads ...
   265594 === ... Memory checking ...
   265594 === ... Button scanning ...
   265703 === ... Axis scanning ...
   265813 === Releasing joystick devices ...
   265813 === Freeing macro memory
   265813 === Removing any offset overrides
   265813 === Clearing any displays left
   265813 === NOTE: not calling SimConnect_Close ...
   265813 === AI slots deleted!
   265813 === Freeing button memory ...
   265813 === Closing my Windows ...
   265813 === Freeing FS libraries ...
   266828 === Closing devices ...
   266828 === Closing the Log ... Bye Bye! ...
   266828 System time = 07/04/2018 16:12:26, Simulator time = 10:03:17 (17:03Z)
   266828 *** FSUIPC log file being closed
Minimum frame rate was 37.8 fps, Maximum was 42.3 fps
Minimum available memory recorded was 1853Mb
Average frame rate for running time of 33 secs = 40.4 fps
Maximum AI traffic for session was 1000 aircraft
Memory managed: 18 Allocs, 18 Freed
********* FSUIPC Log file closed ***********

[Pete Dowson]

8 hours ago, birdguy said:

Pete, I don't have a FSUIPC5.LOG.  And I no longer have P3D installed on my system.  Only FSX_se in the cam folder you mention in your reply.

Sorry, I'm so used to typic FSUIPC5 these days it came out automatically. I of course meant FSUIPC5.LOG.

8 hours ago, birdguy said:

FSUIPC4.DLL
FSUIPC4.key
FSUIPC4.Kodiak.ini
FSUIPC4.Kodiak.log

I started up with the Quest Kodiak.

Aha! There's the reason:

"Running inside FSX Steam Edition on Windows 10
... ESP has been renamed as "Kodiak"

This is why I asked you 
"Finally, can we assume that you ARE actually running the FSX.EXE file which is in the D:\Steam\steamapps\common\FSX folder? Please check what you are actually executing."

You are NOT running "FSX.EXE"!

FSUIPC registration has worked and produced the FSUIPC4.KEY file, but because you aren't running "FSX.EXE", but something named Kodiak, all sorts of odd things happen.  Why have you done it? It should never be needed these days.

It does allow a different FSX CFG  -- using a renamed CFG file, and a different FSUIPC setup (renamed INI, renamed LOG, and, importantly here, renamed KEY!)

The KEY file is produced by the installer when you install. It doesn't know and doesn't deal with anything other than FSX.  (The INI and LOG are run-time). To make an alternative install work, with a different renamed FSX.EXE, you must copy and rename your settings (INI) and KEY file. It seems you've never even run FSX.EXE normally so there was no original INI file, only the one saved with the Kodiak part.

If you had run FSX.EXE you would have seen that your registration was successful.

In order to make FSUIPC run in its registered form with a renamed FSX you need the KEY file named like the INI and LOG files, i.e. FSUIPC5.Kodiak.key.

Incidentally, there is a chapter about this in the FSUIPC4 Advanced Users Guide, in the chapter entitled "Multiple INI files", where the reason for this renaming is described as being for different settings. I don't know your reasons, but these facilities have been dropped in FSUIPC5 because they are simply not necessary these days and renaming is seldom if ever used.

Pete

 

 

 

[birdguy]

OK Pete, I understand.

I start my simulator in an unconventional manner.  I bypass the opening screen.  I have several favorite planes in startup scenarios at different airports in parking spaces with a desktop icon for each scenario.  I make a copy FSX.exe and rename it with the scenario name, hence I have a Kodiak scenario for when I want to fly the Kodiak.  I've been using this method since the days of FS2002.

I guess I would rather retain my regular method of starting flights and forego having FSUIPC4 registered.  But thanks for the help.

Noel

 

[Luke Kolin]

1 hour ago, birdguy said:

I guess I would rather retain my regular method of starting flights and forego having FSUIPC4 registered.  But thanks for the help.

 

Then do what Pete suggested and rename the key file.

Cheers!

Luke

[birdguy]

I tried that Luke but it doesn't work.

The first time I just made a copy of the key file and named it FSUIPC4.Kodiak.Key and started it up.  The Kodiak still said it was unregistered.  I shut it down and looked at the Modules folder and the Kodiak key had been deleted.

Then I tried a different tack.  I again made a copy of the key file and renamed it FSUIPC4.Kodiak.key.  Then I deleted the Kodiak ini and log files hoping that when  started it again it would rewrite the ini and log files.  It did rewrite the ini and log files but again remained unregistered and deleted the Kodiak key file.

But thanks for trying to help.

One of the problems is that I have about 50 such startups on my desktop.  Not all different aircraft but some are the same aircraft with different starting locations, times, and weather.  And I plan to add more as time goes on.  I can live with an unregistered version of FSUICP4.

Noel

 

[Pete Dowson]

2 hours ago, birdguy said:

I guess I would rather retain my regular method of starting flights and forego having FSUIPC4 registered.

please yourself, but all you need to do is make a copy of the KEY file renamed appropriately, as I said (and as I see Luke reminded you).

Note that if you have a lot of renamed FSX.EXE files you'll need a renamed KEY file for each. If you actually use FSUIPC for anything, and therefore have settings saved, you'll need a renamed INI file for each too.

Your system is really very unusual and would probably throw a number of installers and add-ons. It's probably unique. I've heard of doing this for different FS settings (because, at least at one time, each would have a different CFG file too, I think), and once upon a time for different FSUIPC assignments and calibrations, but since Aircraft-Specific settings, and then Profiles were introduced this hasn't been needed for FSUIPC.

Pete

 

 

[Pete Dowson]

8 minutes ago, birdguy said:

The first time I just made a copy of the key file and named it FSUIPC4.Kodiak.Key and started it up.  The Kodiak still said it was unregistered.  I shut it down and looked at the Modules folder and the Kodiak key had been deleted.

That must be wrong. There is nothing anywhere in FSUIPC that can or will delete a KEY file. Nor in the Installer, come to that. It will of course re-write one if you re-register, that's all.

Are you sure it isn't a virus checker doing it? because KEY files are also used to change your Registry, and many virus checkers will remove them or put them in their "safe place".

Pete

 

[birdguy]

I solved the problem.

I was in error about the Kodiak key beng deleted.  It had been moved to the top of the Modules folder but changed to FSUIPC4,Kodiak.key (a comma after FSUIPC4).

What I did next was change the comma to a period so I had FSUIPC4.Kodiak.key.

Then I ran it again and the same thing happened and I had an unregistered version on my Kodiak installation.

This time I commented out FSUIPC4.key and restored FSUIPC4.Kodiak.key so it was the only entry in the Modules folder with a key.

That worked.  Now my Kodiak has a registered version.

Next I uncommented FSUIPC4.key and ran the start-up screen version.  I selected a free flight flight and when it came up it had a registered version.

I reran Kodiak and it still had a registered version.

Now that I know how to do it I can get all my stand alone aircraft registered.

Thanks for you help  Luke and Pete.  I wish I knew more bout how this stuff worked but at 84 year old my learning curve has gotten steeper.

Noel

 

[Pete Dowson]

13 hours ago, birdguy said:

It had been moved to the top of the Modules folder but changed to FSUIPC4,Kodiak.key (a comma after FSUIPC4).

Was that an error when you changed the name?

13 hours ago, birdguy said:

Then I ran it again and the same thing happened and I had an unregistered version on my Kodiak installation.

This time I commented out FSUIPC4.key and restored FSUIPC4.Kodiak.key so it was the only entry in the Modules folder with a key.

That worked.  Now my Kodiak has a registered version.

Next I uncommented FSUIPC4.key and ran the start-up screen version.  I selected a free flight flight and when it came up it had a registered version.

I reran Kodiak and it still had a registered version.

That's a lot of palavah! I don't know what is going on with your system, but FSUIPC will be doing absolutely nothing differently the second time from the first. It wouldn't be looking at FSUIPC4.KEY at all if the FSX was renamed as you have it. There's no way it will work in the one case and not in the other!

13 hours ago, birdguy said:

I wish I knew more bout how this stuff worked but at 84 year old my learning curve has gotten steeper.

Well, I hope I'm as good when I'm 84. I am 75 this year and I'm sure my little grey cells are disappearing fast already!

Pete

 

[birdguy]

Mr. Dowson, I am only telling you what happened.

You can call it palavah if you want.  I do not lie.  Why would I went I am only trying to get help?

Both attempts were NOT the same.

On the first attempt BOTH FSUIPC4 and Kodiak KEYs were active.  Kodiak would not register.

On the second attempt I disabled the FSUIPC4  KEY and that time Kodiak did register.

On the third time, after I re-enabled the FSUIPC key, they were both registered.  Probably because  the FSUIPC4 log was already registered.

I do not take kindly to the inference I lied.  I came here for assistance and I appreciate your help.  I understand how it works a bit better now.

But if I have more problems I hesitate to come back here and get berated because my system might work differently.

Noel 

 

[Pete Dowson]

2 hours ago, birdguy said:

Mr. Dowson, I am only telling you what happened.

I understand that. That is why I said "I don't know what is going on with your system" -- because I don't. I can only tell you what FSUIPC can and cannot do. When strange things are happening on a users system I simply do not have enough information about everything else on that system to explain strange happenings.

2 hours ago, birdguy said:

You can call it palavah if you want. 

Well, it is a complicated sequence which should not be necessary and which I don't understand. Perhaps you understand something different from that word as you seem to be taking it as an insult! :-(

2 hours ago, birdguy said:

I do not lie.

Where on Earth is this coming from? Where did I ever say you were lying???

2 hours ago, birdguy said:

But if I have more problems I hesitate to come back here and get berated because my system might work differently.

NO ONE IS BERATING YOU OR YOUR SYSTEM!!

Please do read my replies a little more carefully, as you plainly are reading things which are just not there!  I try my best to help, but I do not understand everything that may happen on everyone's systems. All I can say it what my own program does.

Pete