Jump to content
The simFlight Network Forums

Registration problem


Recommended Posts

Hi

I just bought FSUIPC For FS2004 from simmarket (Order number 753656) and I found that it can registration successfully.

However, when I start to play FS2004 and call FSUIPC, it shows me that "This copy is unregistered". How can I fix it ?

My system is Window 7 x64 and the location of FS2004 is C:\Flight Simulator\Microsoft Flight Simulator 2004

Version of FS2004 is 9.1

Installation 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="C:\Flight Simulator\Microsoft Flight Simulator 2004"

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

C:\Flight Simulator\Microsoft Flight Simulator 2004\Modules\FSUIPC.DLL

... No previous valid version found.

Okay -- installed FSUIPC into "C:\Flight Simulator\Microsoft Flight Simulator 2004\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 ***************

Link to comment
Share on other sites

However, when I start to play FS2004 and call FSUIPC, it shows me that "This copy is unregistered". How can I fix it ?

My system is Window 7 x64 ...

Assuming the PC's date is set correctly (check please), it is probably the result of a recent Win7 update which tightens security even further on the Registry. There are two things which may overcome this:

1. Re-run the Installer but by right-clicking on it and selecting "Run as administrator", or

2. Download the latest interim update (currently up to 3.997b) from the Download Links subforum and copy it into the FS Modules folder.

If neither action helps, please paste the FSUIPC log file (not the Install log) here, after closing FS down.

Regards

Pete

Link to comment
Share on other sites

Hi Pete

Assuming the PC's date is set correctly

I don't understand what it's mean?

Because I never change a time and date in my PC. It's still up to date. Is it OK?

Thank you for you reply.

Regards,

Link to comment
Share on other sites

Hi

I would like to thank you all and say "The problem was solved already". I can solved it by solution no.2

Thank you so much. But it has something I like to know, if FSUIPC module has upgrade again, What should I do?

I have to buy a new license or use the same license with a new version.

Regards,

Link to comment
Share on other sites

Thank you so much. But it has something I like to know, if FSUIPC module has upgrade again, What should I do?

I have to buy a new license or use the same license with a new version.

You purchased a license for FSUIPC3. That covers you for ALL FSUIPC3 versions, forever. You'd only need to purchase again if you changed to FSX and therefore needed FSUIPC4.

I prefer all users to keep up to date in any case, as I cannot support old versions!

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.