Jump to content
The simFlight Network Forums

Recommended Posts

Posted

Hello,

I have a registered version of FSUIPC4 and wide server for FSX. All has been fine up to now. Recently the machine running FSX failed and I transfered the hard drive containing FSX to another machine and called it F: Eventually I got FSX to run no problem but the FSUIPC module was not present. Below are the contents of the FSUIPC4 Install and FSUIPC log files after running FSX. Is there any information you can see in them that may suggest why the module does not appear in FSX?

Regards

Phillip

Installer for FSUIPC4.DLL version 4.60a

Looking in registry for FSX install path:

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

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"AppPath"

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

Looking in registry for ESP install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"AppPath"

... NOT found! ...

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

INSTALLATION FOR FSX:

AppPath="F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

Checking version of 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)

Checking if there's already a version of FSUIPC4 installed in:

F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.600 found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Documents and Settings\Phillip Lloyd\Application Data"

Now finding \Microsoft\FSX\FSX.CFG for all users, including this one

Looking in "C:\Documents and Settings\Administrator\Application Data"

... No FSX.CFG there

Looking in "C:\Documents and Settings\Administrator.PHILLIP-NETWORK\Application Data"

... No FSX.CFG there

Looking in "C:\Documents and Settings\All Users\Application Data"

... No FSX.CFG there

Looking in "C:\Documents and Settings\Default User\Application Data"

... No FSX.CFG there

Looking in "C:\Documents and Settings\LocalService\Application Data"

... No FSX.CFG there

Looking in "C:\Documents and Settings\NetworkService\Application Data"

... No FSX.CFG there

Looking in "C:\Documents and Settings\Phillip Lloyd\Application Data"

Found FSX.CFG in "C:\Documents and Settings\Phillip Lloyd\Application Data\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.

... 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.

"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 controls.pdf" okay

Installed "GlobalSign Root.exe" 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 "Example LUA plugins.zip" okay

FSUIPC4.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

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

All installer tasks completed okay!

Registration check for FSUIPC4 and WideFS was successful! (result code 00)

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

********* FSUIPC4, Version 4.60a by Pete Dowson *********

Reading options from "F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.ini"

NOTE: SimConnect Acc/SP2 Oct07 is supported, but it isn't installed.

Trying to connect to SimConnect SP1 May07 ...

User Name="Phillip Lloyd"

User Addr="phillip.lloyd@virgin.net"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX (using SimConnect SP1 May07)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=255

281 System time = 16/04/2012 17:54:43

297 FLT UNC path = "\\PHILLIP-NETWORK\My Documents\Flight Simulator X Files\"

297 FS UNC path = "F:\Program Files\Microsoft Games\Microsoft Flight Simulator X\"

1641 LogOptions=00000000 00000001

22781 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

22781 ... Now trying to connect to another version of SimConnect ...

22797 Trying to connect to SimConnect Original ...

22828 Now running with SimConnect Original

44016 Failed on SimConnect_Open, return = 0x80004005: FSUIPC4 cannot operate!

44016 ... Now trying to connect to another version of SimConnect ...

Posted

Is there any information you can see in them that may suggest why the module does not appear in FSX?

...

Installer for FSUIPC4.DLL version 4.60a

That's the first problem. i cannot possibly support such an old version. the current version for FSX is 4.823.

The other serious problem is that your FSX is up to SP2/ACC level but your SimConnect installation is not, so they are incompatible. you need to install SP2 or Acceleratioin (again, if you tried already).

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.