Jump to content
The simFlight Network Forums

FSUIPC registering problem


Jaap
 Share

Recommended Posts

Hello,

I've got the FSUIPC version 3.99. Also I received a registration.

I had to reinstall mij FS9 and of course FSUIPC 3.99.

After installing FSUIPC, the program said it is registered but after starting FS9 it says: it is an unregistererd version.

I'have FSUIPC installed several times, after deleting the FSUIPC.DLL. but to no avail.

Please help me because I need FSUIPC for my 4-engined planes.

Geetings

Jaap Stiemsma

See install log and FSUIPC log::

Installer for FSUIPC.DLL version 3.99

Looking in registry for FS9.1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.1

Parameter"EXE Path"

... NOT found! ...

Looking in registry for FS9 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0

Parameter"EXE Path"

... >>> OK! FOUND FS9! <<< ...

Looking in registry for FS8 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\8.0

Parameter"EXE Path"

... NOT found! ...

Looking in registry for FS7 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0

Parameter"path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\7.0

Parameter"path"

... NOT found! ...

Looking in registry for FS6.1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1

Parameter"InstallDir"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\6.1

Parameter"InstallDir"

... NOT found! ...

Looking in registry for CFS2 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\2.0

Parameter"EXE Path"

... NOT found! ...

Looking in registry for CFS1 install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0

Parameter"EXE Path"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Combat Flight Simulator\1.0

Parameter"EXE Path"

... NOT found! ...

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

INSTALLATION FOR FS9:

EXE Path="D:\FS2004"

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

D:\FS2004\Modules\FSUIPC.DLL

... Version 3.990 found.

Okay -- installed FSUIPC into "D:\FS2004\Modules\FSUIPC.DLL"

"Modules\FSUIPC Documents" folder already exists.

Now installing additional files into the "Modules\FSUIPC Documents" folder:

Installed "FSUIPC User Guide.pdf" okay

Installed "FSUIPC for Advanced Users.pdf" okay

Installed "FSUIPC History.pdf" okay

Installed "List of FS2004 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

Installed "SIMSAMURAI+FSUIPC+TUTORIAL.pdf" okay

FSUIPC.DLL installed and signature checked out okay!

Deleted GlobalSign Root fix program ... no longer relevant

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

All installer tasks completed okay!

Registration for FSUIPC was successful! (result code 00)

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

********* FSUIPC, Version 3.99 by Pete Dowson *********

Running on Windows Version 5.1 Build 2600 Service Pack 2

Verifying Certificate for "D:\FS2004\MODULES\FSUIPC.DLL" now ...

SUCCESS! Signature verifies okay!

Running inside FS2004 (FS9.1 CONTROLS.DLL, FS9.1 WEATHER.DLL)

User Name="Jaap Stiemsma"

User Addr="j.stiemsma@live.nl"

FSUIPC Key is provided

FSUIPC not user registered

WIDEFS not user registered, or expired

Module base=61000000

WeatherReadInterval=4

LogOptions=00000001

DebugStatus=3

9173 System time = 09/11/2012 10:47:09

9173 D:\FS2004\

9173 System time = 09/11/2012 10:47:09, FS2004 time = 12:00:00 (00:00Z)

17769 FLIGHTS\OTHER\FLTSIM.flt

17925 AIRCRAFT\c172\Cessna172SP.air

20530 Clear All Weather requested: external weather discarded

46457 C:\Users\Stiemsma\Documents\Flight Simulator Files\UI generated flight.flt

46644 Clear All Weather requested: external weather discarded

49265 Advanced Weather Interface Enabled

67595 Traffic File #14 = "scenery\world\scenery\traffic030528"

97516 WeatherOptions set, now 0000B027 (timer=0)

318024 System time = 09/11/2012 10:52:18, FS2004 time = 10:51:01 (18:51Z)

318024 *** FSUIPC log file being closed

Memory managed: 0 Allocs, 4044 Freed

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

Link to comment
Share on other sites

I've got the FSUIPC version 3.99.

Version 3.99 is well out of date and not supported. The signature system has been changed since then. Please always check that you are using a current and supported version -- 3.999w is the earliest such version, and there is a later interim update to 3.999x available in Download Links.

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

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