FSUIPC4 4.20 Install problem in Vista

[smithrb23]

Peter:

When I install Version 4.20 of FSUPC4, SimConnect now fails to load (Note: everything worked with Version 4.16).

I had this same problem when I tried to replace FSUIPC4.DLL with the interim updates prior to the full release of 4.20

Do not run a third party Firewall, just Windows Firewall and use the freeware version of AVG 7.5 virus software. They have not given me problem to date.

Below are my FSUIPC4 log and Install log.

Regards

Rick

********* FSUIPC4, Version 4.20 by Pete Dowson *********

User Name="Richard Smith"

User Addr="smithrb@unitz.ca"

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07)

Module base=61000000

DebugStatus=255

78 System time = 22:14:41

78 FLT UNC path = "C:\Users\richard\Documents\Flight Simulator X Files\"

78 FS UNC path = "D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\"

4212 LogOptions=00000001

4212 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!

19251 **** Retrying SimConnect connection****

19251 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!

34289 **** Retrying SimConnect connection****

34289 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!

49328 **** Retrying SimConnect connection****

49328 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!

64366 **** Retrying SimConnect connection****

64366 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!

79405 **** Retrying SimConnect connection****

79405 Failed on SimConnect_Open, return = 0x80070057: FSUIPC4 cannot operate!

93960 System time = 22:16:15

93960 *** FSUIPC log file being closed

Memory managed: 2 Allocs, 2 Freed

********* FSUIPC Log file closed ***********

Installer for FSUIPC4.DLL version 4.20

Looking in registry for FSX install path:

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

Parameter"SetupPath"

SetupPath="D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X"

Checking version of FSX.EXE:

... Version 10.0.61355.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

... Okay, Probe Manifest matches installed SimConnect 60905 (Original)

Found later build SimConnect 61242 (SP1 May07)

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

D:\Program Files (x86)\Microsoft Games\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.200 found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "D:\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\richard\AppData\Roaming"

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

Looking in "C:\Users\richard\AppData\Roaming"

Found FSX.CFG in "C:\Users\richard\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.

... 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\richard\Application Data\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Contacts\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Cookies\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Desktop\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Documents\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Downloads\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Favorites\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Links\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Local Settings\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Music\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\My Documents\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\NetHood\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Pictures\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\PrintHood\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Recent\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Saved Games\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Searches\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\SendTo\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Start Menu\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Templates\Roaming"

No FSX.CFG there

Looking in "C:\Users\richard\Videos\Roaming"

No FSX.CFG there

Now installing additional files into the Modules 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

All installer tasks completed okay!

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

[Pete Dowson]

When I install Version 4.20 of FSUPC4, SimConnect now fails to load (Note: everything worked with Version 4.16).

I had this same problem when I tried to replace FSUIPC4.DLL with the interim updates prior to the full release of 4.20

In that case, I wish you'd told me before I made the full release. The main reason for interim releases is to shake such problems out! :-(

Do not run a third party Firewall, just Windows Firewall and use the freeware version of AVG 7.5 virus software. They have not given me problem to date.

It isn't a firewall problem. For some odd reason, though the installer knows you don't have Acceleration of SP2 installed in FSX, FSUIPC4 seems to think you do:

Running inside FSX on Windows Vista (SimConnect Acc/SP2 Oct07)

I'm not sure why that is happening. I'll need to do some more tests on Vista here.

Regards

Pete

[Pete Dowson]

When I install Version 4.20 of FSUPC4, SimConnect now fails to load (Note: everything worked with Version 4.16).

Okay, I've tested all combinations of FSX base, FSX+SP1 on both WinXP and Vista, and I cannot reproduce anything like the problem you have.

The really odd thing is that the code for detecting the version of SimConnect is identical in both the Installer and FSUIPC4 itself, yet the Installer shows you have the base version (60905) and SP1 (61242) whilst FSUIPC4 gets an initial response as if there's SP2 or Accelerator installed.

I cannot begin to guess how that may arise. The Windows "side-by-side" library system is very complex. I can only assume either your Registry or WinSxS folders are is some sort of disarray.

Can you offer any details of your FSX install history? Have you had problems, uninstalled, reinstalled, repaired, or anything at all? You've not been involved in Beta testing have you? I'm struggling to find something which may help explain these extraordinary results.

Do you recall exactly which of the post 4.16 interim versions gave you this problem in the first place? Why didn't you tell me then? There were so many, over a period of more than two months.

At present I've really no way of knowing how to help, I'm afraid.

Regards

Pete

[Thomas Richter]

Okay, I've tested all combinations of FSX base, FSX+SP1 on both WinXP and Vista, and I cannot reproduce anything like the problem you have.

...

At present I've really no way of knowing how to help, I'm afraid.

Regards

Pete

Hi Pete

Running now Vista 32 with FSX, had installed 4.16 + latest.

Installed 4.20 without any problems, no Firewall or anything else on that PC.

Part of the Install.txt

Checking version of FSX.EXE:

... Version 10.0.61637.0 (Need at least 10.0.60905.0)

Checking compatibility with installed SimConnect:

... Okay, Probe Manifest matches installed SimConnect 60905 (Original)

Found later build SimConnect 61242 (SP1 May07)

Found later build SimConnect 61259 (Acc/SP2 Oct07)

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

F:\Microsoft Flight Simulator X\Modules\FSUIPC4.DLL

... Version 4.181 found.

FSX Modules folder already exists.

...

[Pete Dowson]

Hi Thomas!

Running now Vista 32 with FSX, had installed 4.16 + latest.

Installed 4.20 without any problems, no Firewall or anything else on that PC.

Ah, but you have Acceleration installed!

Checking compatibility with installed SimConnect:

... Okay, Probe Manifest matches installed SimConnect 60905 (Original)

Found later build SimConnect 61242 (SP1 May07)

Found later build SimConnect 61259 (Acc/SP2 Oct07)

Thanks for the confirmation, nonetheless!

Best Regards

Pete

[smithrb23]

Peter:

Sorry tried to reply last night but keep losing the forum server.

I was able to sort out the problem based on your response. 4.20 now loads and works as it should.

Somehow I ended up with a copy of the Microsoft.FlightSimulator.Simconnect.dll from the SDK in the Modules directory.

This is what was causing FSUIPC4 the grief. I was experimenting with the Camera views awhile ago and must have (wrongly and without good reason) copied this file to the Modules directory.

Sorry for the grief, and I will be more careful in future.

To recap, 4.16 was not affected, but 4.166 was. I have the log file from 4.166 if you care to see it.

Regards

Rick

[Pete Dowson]

Somehow I ended up with a copy of the Microsoft.FlightSimulator.Simconnect.dll from the SDK in the Modules directory. This is what was causing FSUIPC4 the grief. I was experimenting with the Camera views awhile ago and must have (wrongly and without good reason) copied this file to the Modules directory.

Ooh, ouch!

Maybe I should put in a check against that. However, I do find it rather strange that Windows would look there for a Side-by-Side manifested DLL. I shall have to ask my contacts in Microsoft about it.

To recap, 4.16 was not affected, but 4.166 was. I have the log file from 4.166 if you care to see it.

The only difference I can think of is that 4.16 was not aware of the Acc/SP2 update whilst later interim versions were. Can you tell me what the version of the SimConnect.DLL was that you put in the Modules folder?

Regards

Pete

[Pete Dowson]

Somehow I ended up with a copy of the Microsoft.FlightSimulator.Simconnect.dll from the SDK in the Modules directory. This is what was causing FSUIPC4 the grief.

Further to this, I have now added code to FSUIPC4 to check that the full pathname for the SimConnect.dll I connect to contains "WinSxS" (to show it is from the Windows side-by-side folder.

However, in trying to test it, I placed each of the versions of Microsoft.FlightSimulator.Simconnect.dll I can find (Original, SP1 and the new Accelerator version), one test at a time, into the Modules folder alongside FSUIPC4, and also even tried them with the name stripped to just Simconnect.dll, and in no case did Windows supply anything other than the correct WinSxS version. So I don't understand what happened in your case. Are you sure there was no other file in there, like the .manifest file or any SimConnect.xml or cfg file?

[LATER]

EUREKA! I managed to make it do as you did -- on Vista! It doesn't go wrong on WinXP. It is evidently a new Vista bug/deficiency!

Anyway, now I can test my "check" for this. Unfortunately I cannot make FSUIPC4 actually work with this hapening, all I can do is log the incorrect SimConnect details and say it should be removed.

Thanks,

Regards

Pete

[GHD]

EUREKA! I managed to make it do as you did -- on Vista! It doesn't go wrong on WinXP. It is evidently a new Vista bug/deficiency!

No wonder you are smiling in your avatar :D

It was quite an epic hunt :P

George

[smithrb23]

WOW... had no idea!

As for the version of Microsoft.FlightSimulator.Simconnect.dll , it was file version 10.0.60905.0 from SDK SP1A Service Pack release.

Just Note:

I just installed the new Release of FSX: Acceleration and everything works just fine with Vista.

There is a definate improvement in FPS on my system and the graphs appear to be much smoother. I like it

Regards

rick

[Pete Dowson]

As for the version of Microsoft.FlightSimulator.Simconnect.dll , it was file version 10.0.60905.0 from SDK SP1A Service Pack release.

Actually 60905 (means "5th September 2006") was the first release, last year, not SP1A.

Regards

Pete