Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Since I had to erase and rebuild my system HDD I am not able to have FSUIPC working. It loads only fos FS2004. Here is the installation log:

 

Installer for FSUIPC4.DLL version 4.939n

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:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\

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"
Not there, so looking in:
     HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3D v2
     Parameter"AppPath"
... NOT found! ...
===========================================================

INSTALLATION FOR FSX:
SetupPath="C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"
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:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL
... Version 4.939n found.
FSX Modules folder already exists.
Okay -- installed FSUIPC4 into "C:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"
Looking for the current user's Application Data path:
... found as "C:\Users\Rodrigo\AppData\Roaming"
Now finding \Microsoft\FSX\FSX.CFG for all users, including this one
Looking in "C:\Users\Rodrigo\.android\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Ambiente de impressão\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Ambiente de rede\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\AppData\Roaming"
Found FSX.CFG in "C:\Users\Rodrigo\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 ...
... There is a SimConnect.XML, checking for "local" section.
... "local" section already exists, file not modified.
Looking in "C:\Users\Rodrigo\Configurações locais\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Contacts\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Cookies\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Dados de aplicativos\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Desktop\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Documents\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Downloads\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Dropbox\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Favorites\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Intel\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\IntelGraphicsProfiles\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Links\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Menu Iniciar\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Meus documentos\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Modelos\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Music\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Pictures\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Recent\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Saved Games\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Searches\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\SendTo\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\SupTab\Roaming"
 ... No FSX.CFG there
Looking in "C:\Users\Rodrigo\Videos\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
===========================================================

All installer tasks completed.

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

 

Please help.

Posted

You should always install FSX on the root drive (e.g., C:\FSX). See if that helps.

Look around on Google for proper uninstall procedures. I know you have to uninstall FSX 2 or three times due to the Acceleration and SP modules. After that, follow NickN's Bible to re-install and configure. It works great.

http://www.simforums.com/Forums/my-bible-and-new-hardware_topic50239.html

Hope this helps until Pete or someone more knowing than I can help.

Keith

Posted

I think the answer may be a lot simpler

when you re-installed FSX - did you run it once before installing FSUIPC - this creates the fsx.cfg file

afterwards - you should then have re-insalled FSUIPC - in your case you don't need a re-install - just run FSx and say yes to have the FSUIPC dll trusted.

Posted

Since I had to erase and rebuild my system HDD I am not able to have FSUIPC working. It loads only fos FS2004. Here is the installation log:

 

The installation log shows that FSUIPC4 installed fine, no problems, into your FSX installation  FSUIPC4 does NOT install into FS2004 -- you need FSUIPC3 for that!

 

Perhaps you ought to describe the symptoms of your problem, rather than just assume it doesn't install!?

 

Pete

Posted

Hi Pete!

 

The symptoms were my saitek panels not working properly. And  when I lauched the manual plug in for Saitek panels for FSX  I got a icon on my task bar saying "FSUIPC FS2004" or something like that.

I hae FSx reinstalled and on my first flight it semmed to work fine. But what are your impressions?

Posted

The symptoms were my saitek panels not working properly. And  when I lauched the manual plug in for Saitek panels for FSX  I got a icon on my task bar saying "FSUIPC FS2004" or something like that.

 

No idea what is doing that. FSUIPC is a module inside FS, it has no icon for the task bar. It sounds like you ave some other program being run for your Saitek panels, and which is a wrong version in any case (FS2004 not FSX).

 

I think you need to go to the Saitek support forum if you still have some problmes.

 

Pete

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.