Jump to content
The simFlight Network Forums

FSUIPC4 4.60


Recommended Posts

Hi Guys,

I read the post by dimatrixxx on the Help with FSUIPC4 code signature problem topic.

Im not having the global sign root fix problem.

I am just having the Installation error where it says check trusted content under IE.

Done all that and it still doesnt work

I have installed FSX to my C:\Games\Microsoft Games\FSX.

When I install FSUIPC it gives that error, as I am trying to get FSmetar working but it wont connect with out the FSUIPC

If I have missed something silly here please point me to right direction.

David

Link to comment
Share on other sites

I read the post by dimatrixxx on the Help with FSUIPC4 code signature problem topic.

Im not having the global sign root fix problem.

I am just having the Installation error where it says check trusted content under IE.

Done all that and it still doesnt work

Please show me the Install log and, if you've tried running FSX, the FSUIPC4 log. Both will be in the FSX Modules folder. I need to see these because they contain more information.

If I have missed something silly here please point me to right direction.

Try this thread on installation problems which I think must end successfully (though the complainant never confirmed):

viewtopic.php?f=54&t=80782&p=488851

The final fix must have been the Registry edit.

Regards

Pete

Link to comment
Share on other sites

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"

... >>> 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="C:\Games\Microsoft Games\FSX"

Checking version of FSX.EXE:

... Version 10.0.61637.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:\Games\Microsoft Games\FSX\Modules\FSUIPC4.DLL

... Version 4.600 found.

FSX Modules folder already exists.

Okay -- installed FSUIPC4 into "C:\Games\Microsoft Games\FSX\Modules\FSUIPC4.DLL"

Looking for the current user's Application Data path:

... found as "C:\Users\David Jacobs\AppData\Roaming"

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

Looking in "C:\Users\David Jacobs\AppData\Roaming"

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

... No SimConnect.XML file found. This is okay.

Looking in "C:\Users\David Jacobs\Application Data\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Contacts\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Cookies\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Desktop\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Documents\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Downloads\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Favorites\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Links\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Local Settings\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Music\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\My Documents\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\NetHood\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Pictures\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\PrintHood\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Recent\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Saved Games\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Searches\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\SendTo\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Start Menu\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Templates\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\Tracing\Roaming"

No FSX.CFG there

Looking in "C:\Users\David Jacobs\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 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

Link to comment
Share on other sites

I did yes Pete. Still no Joy

Error ref 80092026

Well that's certainly the windows system error which, according to assorted places (Google it yourself) occurs because of an ultra-safe setting in the Registry. See This for example:

http://blog.stealthpuppy.com/windows/wiion-failed

I'm afraid all I can do is follow up all the Googled references, but it would be quicker for you to do so yourself. This is only the second or third time, in nearly four years, that this particular error has occurred, and the other one or two have either fixed it or never come back to say.

Regards

Pete

Link to comment
Share on other sites

  • 1 month later...

I got Global Root problem "out of nowhere". Yesterday FSX was running totally fine, as it always has. I also haven´t experienced digital signing problems ever before. I did the checklist found in this post, expect re-installing Windows http://forums.simflight.com/viewtopic.php?f=54&t=80782&p=488851#p491302

I couldn´t find any trace of SimFlight in Control Panel | Internet Properties | Content | Certificates.

Windows seems to have updated itself recently. Maybe the problem is due to the updates. Stardock Fences also stopped working at the same time as FSX. upt.gif

Link to comment
Share on other sites

I got Global Root problem "out of nowhere".

What's "Global Root" problem?

I couldn´t find any trace of SimFlight in Control Panel | Internet Properties | Content | Certificates.

You've not confirmed you've trusted it yet, then. It would either be in the Untrusted or Trusted tab. It needs to be NOT untrusted. Else it doesn't matter.

Regards

Pete

Link to comment
Share on other sites

I got Global Root problem "out of nowhere".

What's "Global Root" problem?

Sorry, I meant Globalsign Root. Or whatever the error message said when the problem appeared (restart fsx / enable service et cetera).

I couldn´t find any trace of SimFlight in Control Panel | Internet Properties | Content | Certificates.

You've not confirmed you've trusted it yet, then. It would either be in the Untrusted or Trusted tab. It needs to be NOT untrusted. Else it doesn't matter.

Regards

Pete

No, it´s not there anywhere. I also tried manually importing the certificate by right clicking FSUIPC4.dll -> properties et cetera, but it´s no good.

It looks like something is really broken in my OS. I tried installing .NET Framework 4.0 standalone package for testing purposes, and I´m getting the

0x80092026 (The cryptographic operation failed due to a local security option setting.)

(0x800B010B), "Generic trust failure. "

error message.

Link to comment
Share on other sites

Sorry, I meant Globalsign Root. Or whatever the error message said when the problem appeared (restart fsx / enable service et cetera).

Hmmm. Shouldn't be about Globalsign except on an original XP release (where MS forgot to include that root), or Windows 98/Me. And the FSUIPC installer should rectify that by automatically running the GlobalSign root installer.

It looks like something is really broken in my OS. I tried installing .NET Framework 4.0 standalone package for testing purposes, and I´m getting the
0x80092026 (The cryptographic operation failed due to a local security option setting.)

Have you tried the Registry fixes detailed in the "Help with FSUIPC4 code signature problem" Announcement in this Forum?

Regards

Pete

Link to comment
Share on other sites

Have you tried the Registry fixes detailed in the "Help with FSUIPC4 code signature problem" Announcement in this Forum?

Regards

Pete

Yes, I tried them, without success.

However, I managed to fix the problem. :D I tried the following solutions, and somehow it worked out. 808blink.gif

http://support.microsoft.com/kb/956702 Initpki.dll was not found on my system.

http://support.microsoft.com/kb/947821 This program probably did the trick (System Update Readiness Tool).

Thanks for your help, and continuing development of FSUIPC is much appreciated. :wink:

Link to comment
Share on other sites

However, I managed to fix the problem. :D I tried the following solutions, and somehow it worked out.

http://support.microsoft.com/kb/956702 Initpki.dll was not found on my system.

http://support.microsoft.com/kb/947821 This program probably did the trick (System Update Readiness Tool).

Hmmm. Not sure I understand those, but I'm glad you got it sorted out!

Regards

Pete

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.