Jump to content
The simFlight Network Forums

error 372


Recommended Posts

Hello,

 

I've a problem to install FSUIPC4 (newest version) correctly.

First it shows the following message: "Your FSX installation is not suitable for this version of FSUIPC. You may need to install an update from Microsoft."

I have P3D v 2.5 and I have the newest version of FSUIPC4 (registered one).

At the end of the installing of FSUIPC it says: "Installed into Prepar3D v2 okay!"

 

I need FSUIPC for FDC Live Cockpit (an add-on made for FSX). If I use FSUIPC4 and FSX and FDC it works fine. If I use the same version of FSUIPC4 and P3D and FDC it doesn't work. I install all older FSX add-ons with a payware migration tool and that works fine with all add-ons. During installation I deactivated Norton Antivirus.

 

I would like to upload FSUIPC4.log if you need it but the uploader says: "You aren't permitted to upload this kind of file."

 

Could you please help me?

 

Thanks a lot!

 

Mathew "kelle8806"

Link to comment
Share on other sites

I've a problem to install FSUIPC4 (newest version) correctly.

 

And what was your previous install version?

 

First it shows the following message: "Your FSX installation is not suitable for this version of FSUIPC. You may need to install an update from Microsoft."

 

I need to see the Install log to determine why that occurs. What version of FSX do you have installed?

 

I have P3D v 2.5 and I have the newest version of FSUIPC4 (registered one).

 

Sorry, what are you trying to install, then? I'm now confused. Do you ONLY have P3D, no FSX? Because the error you mention says that your registry points to an FSX installation.

 

At the end of the installing of FSUIPC it says: "Installed into Prepar3D v2 okay!"

 

So, what is the problem? Please explain! don't you believe it?

 

I need FSUIPC for FDC Live Cockpit (an add-on made for FSX). If I use FSUIPC4 and FSX and FDC it works fine. If I use the same version of FSUIPC4 and P3D and FDC it doesn't work. I install all older FSX add-ons with a payware migration tool and that works fine with all add-ons. 

 

Oh, no! Not one of those horrible migration programs which renames the progeam so that FSUIPC and other programs can't even tell what is going on?

 

When you say "it doesn't work" can you expand on that. What "doesn't work" about it? If FSUIPC running?

 

I would like to upload FSUIPC4.log if you need it but the uploader says: "You aren't permitted to upload this kind of file."

 

Just paste contents of text files into your messages. Use the <> button above the edit area to enclose them. And the main file, for installation problems, is the install FSUIPC log file.

 

I also suspect FDC can't work with a renamed P3D installation. You need to undo whatever your horrible migration tool is doing to mess everything up!

 

Pete

Link to comment
Share on other sites

Hello Pete,

 

I use FSX and P3D.

FSX version is: 10.0.61472.0

P3D version is: 2.5.12944.0

 

I use a payware migration tool because for me it is the only way to keep my old add-ons and use them in P3D. I don't understand to do it manually because i do it only in my leasure time. All add-ons work but FDC Live Cockpit doesn't work with P3D.

My FSX and FSUIPC4 and FDC work fine. My P3D and FSUIPC4 and FDC don't work.

 

The migration tool installs FDC without any error and as I said with my FSX FSUIPC works but not with my P3D. The only error message I get during installation is the one of FSUIPC. I deactivated Norton Antivirus to avoid problems.

 

Install-log of FSUIPC:

 

Installer for FSUIPC4.DLL version 4.939g


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

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... NOT found! ...

Looking in registry for Prepar3D v1 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\LockheedMartin\Prepar3D
     Parameter"SetupPath"
... >>>  OK! FOUND Prepar3D v1!  <<< ...
     SetupPath=C:\P3D\

Looking in registry for Prepar3D v2 install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"SetupPath"
... >>>  OK! FOUND Prepar3D v2!  <<< ...
     SetupPath=C:\P3D\

************ BUT this is the same path as for Prepar3D v1! Will only install for Prepar3D v2 ************

===========================================================

INSTALLATION FOR FSX:
SetupPath="C:\P3D\"
Checking version of the FSX EXE:
... Version 2.5.12944.0  (Need at least 10.0.60905.0)
!! WARNING !! This version of FSX is later than any known by this FSUIPC4.
   There may be problems. Please check for a later version of FSUIPC4!
===========================================================

INSTALLATION FOR Prepar3D v2:
SetupPath="C:\P3D\"
Checking version of the Prepar3D v2 EXE:
... Version 2.5.12944.0  (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
Checking if there's already a version of FSUIPC4 installed in:
       C:\P3D\Modules\FSUIPC4.DLL
... Version 4.939g found.
Prepar3D v2 Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\P3D\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\MPOS\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\DefaultAppPool\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\dub_cm_auto\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\MPOS\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\MPOS\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.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\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D2.dll" 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 "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 "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
===========================================================

All installer tasks completed.
Registration for FSUIPC4 was successful! (result code 00)

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

Could you please help me?

 

Thanks a lot!

 

Mathew

Link to comment
Share on other sites

Hello Pete,

 

you were right. Now I deactivated the migration tool and installed FSUIPC again - without any error. Now i try to get FDC to work.

 

Thanks!

 

Mathew

 

new install-log:

 

Installer for FSUIPC4.DLL version 4.939g


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

Looking in registry for FSX-SE install path:
     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"SetupPath"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator - Steam Edition\10.0
     Parameter"AppPath"
... NOT found! ...

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"
... >>>  OK! FOUND Prepar3D v2!  <<< ...
     SetupPath=C:\P3D\
===========================================================

INSTALLATION FOR FSX:
SetupPath="C:\FSX\"
Checking version of the FSX EXE:
... Version 10.0.61472.0  (Need at least 10.0.60905.0)
Checking compatibility with installed SimConnect:
    Found SimConnect build 60905 (Original)
    Found SimConnect build 61242 (SP1 May07)
    Found SimConnect build 61259 (Acc/SP2 Oct07)
Checking if there's already a version of FSUIPC4 installed in:
       C:\FSX\Modules\FSUIPC4.DLL
... Version 4.939e found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\FSX\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\MPOS\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\Default\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\DefaultAppPool\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\dub_cm_auto\AppData\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\MPOS\AppData\Roaming"
Found FSX.CFG in "C:\Users\MPOS\AppData\Roaming\Microsoft\FSX\FSX.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\Public\AppData\Roaming"
 ... No FSX.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 "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 "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
===========================================================

INSTALLATION FOR Prepar3D v2:
SetupPath="C:\P3D\"
Checking version of the Prepar3D v2 EXE:
... Version 2.5.12944.0  (Need at least 1.0.677.0)
Checking compatibility with installed SimConnect:
Checking if there's already a version of FSUIPC4 installed in:
       C:\P3D\Modules\FSUIPC4.DLL
... Version 4.939g found.
Prepar3D v2 Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\P3D\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\MPOS\AppData\Roaming"
Now finding \Lockheed Martin\Prepar3D v2\Prepar3D.CFG for all users, including this one
Looking in "C:\Users\All Users\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\Default User\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\DefaultAppPool\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\dub_cm_auto\AppData\Roaming"
 ... No Prepar3D.CFG there
Looking in "C:\Users\MPOS\AppData\Roaming"
Found Prepar3D.CFG in "C:\Users\MPOS\AppData\Roaming\Lockheed Martin\Prepar3D v2\Prepar3D.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\Public\AppData\Roaming"
 ... No Prepar3D.CFG there
"Modules\FSUIPC Documents" folder already exists.
Now installing the Prepar3D SimConnect interface for FSUIPC4 into the "Modules" folder:
   Installed "SimConnectP3D2.dll" 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 "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 "FSUIPC4 Offsets Status.pdf" okay
   Installed "Profiles in Separate Files.pdf" okay
===========================================================

All installer tasks completed.
Registration for FSUIPC4 was successful! (result code 00)

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

Link to comment
Share on other sites

Looking in registry for FSX install path:

     HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

     Parameter"SetupPath"

... >>>  OK! FOUND FSX!  <<< ...

     SetupPath=C:\P3D\

 

That's a bad migration tool! It should at least clean up its mess when it has finished. It makes the Registry point to your P3D installation for FSX, and also seems to put an FSX.EXE there (or renamed Prepar3D.exe), which makes the confusion even worse!

 

The end result is:

 

************ BUT this is the same path as for Prepar3D v1! Will only install for Prepar3D v2 ************

 

There is really no way a decent installer can untangle the sort of mess this is in! Your so-called "migration tool" should only do its fiddle temporarily, whilst you are using stupid installers which can't work things out correctly. Then the "migration tool" should put things back correctly so that normal well-written installers can find the right things in the right place!

 

you were right. Now I deactivated the migration tool and installed FSUIPC again - without any error. Now i try to get FDC to work

 

Okay. I think you should only "activate" the tool when installing things which don't understand what they are doing, then deactivate it afterwards for normal use.

 

Pete

Link to comment
Share on other sites

I found the problem with FDC and I wrote it in their forum:

 

FDC starts with a version of 2006 and not the newest one. That's why it doesn't work.

FSUIPC works fine now.

Thanks a lot. I'll really use this migration tool only to install the old add-ons and then I deactivate it forever.

 

Greetings!

 

Mathew

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.