Jump to content
The simFlight Network Forums

Registered Version of FSUIPC 3.999w not working


Recommended Posts

Hello Peter

I have purchased FSUIPC 3.999w from simmarket unfortunately once I entered my reg details and sn FSUIPC stopped working. Ithen removed the product and the key, re- installed without registering and the product functioned perfectly. I have tried to re-register but with the same problem

Advise Please as to any further information you require to fix this problem

Thanks

Link to comment
Share on other sites

Pete is away on holiday still, but the usual cause of problems like this are;

1. Incorrectly spelt name or email address compared to what you stated at the time of purchase.

2. PC clock wrong i.e. date and time on the PC you are trying to register FSUIPC on is set to a date before the time when you purchased the key.

3. You didn't copy and paste the key from the Simmarket website correctly, I.e. an extra space at the end or beginning of the code.

4. You purchased a key for FSUIPC3 and are trying to use it with version 4 or vice versa. i.e. Keys are not interchangeable between major versions.

5. Finally the key perhaps is no longer valid due to it being blocked due to piracy reasons, unlikely if you just purchased yesterday.

Link to comment
Share on other sites

Hello,

I have EXACTLY the same issue.

I installed: FSUIPC 3.999w

Purchased & Registered License for FSUIPC3

Installed on Windows 7 Ultimate / 64bit

Fs9 updated to v9.1

If I Launch fs9.1, FSUIP displays my registration information.

Plan-G unable to connect.

FSInn/Copilot/SquawkBox unable to connect.

If I uninstall FSUIP & reinstall without registering, I am able to connect to Vatsim and Plan-G works without problems.

I've have also tried:

1. Uninstalling the Plan-G, FSInn/Copilot/SquawkBox

2. Installing FSUIP & Registering

3. Reinstalling Plan-G, FSInn/Copilot/SquawkBox

This does not fix the issue.

Things only work when FSUIP is unregistered.

Link to comment
Share on other sites

Here are my FSUIPC Install.log

Installer for FSUIPC.DLL version 3.999w

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

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

INSTALLATION FOR FS9:

EXE Path="C:\Program Files\Microsoft Games\Flight Simulator 9"

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

C:\Program Files\Microsoft Games\Flight Simulator 9\Modules\FSUIPC.DLL

... Version 3.999w found.

Okay -- installed FSUIPC into "C:\Program Files\Microsoft Games\Flight Simulator 9\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 "LuaFileSystem.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

I think SimFlight had some server glitch a week or so ago and this might have affected their key generation program -- probably a date error on their server -- but they said it was fixed. I've no idea how much damage that did, but if you can't get it resolved via a problem ticket to SimMarket, please ZIP up your FSUIPC.KEY or FSUIPC4.KEY file and send it to me at petedowson@btconnect.com. I can check it easily here and refer to SimMarket for you.

[EDIT]

Okay. Not SimMarket after all, but yours truly. Seems I never expected FSUIPC3 still be be selling after over 8 years, and it ran afoul of a check at the end of 2012. I've extended the registration date limit now. Please download 3.999y5 from Download Links subforum and put it into your FS Modules folder.

I'll make a full new release with Installer later this month.

Regards

Pete

Link to comment
Share on other sites

Good Afternoon Pete,

Perhaps a slightly related problem, though being well over 70 years young I admit that a lot of this technical stuff is well over my head.

Yesterday [16th January] I purchased via Simflight the WideFS; my plan is to run FS2004 on my main PC with windows XP [sP3] and run Plan G on my Laptop with Windows 7.

I purchased WideFS okay and obtained the ‘key’, I registered it by downloading FSUIPC 3.999w and using the installer, everything works fine. WideFS works and connects from the laptop to FS9 on the PC.

I have set up Plan G on the laptop and have ‘pointed it’ at FS 9 on the PC and built the database, Plan G also connects to the internet though not linking with FS 9.

The problem I have now with FSUIPC is when I start FS9 it loads and after it loads it displays an error message:

The SquawkBox module was unable to start because FSUIPC could not be initialized. Ensure FSUIPC is properly installed and re-start Flight Simulator to try again.

I also notice for some reason the Squawkbox module is now missing from ‘Modules’ in FS 9.

The problem I have is to problem solve why Plan G is not linking with FS 9 and I am wondering if it is somehow related to this error message on start up of FS 9 claiming that FUSIPC is not properly installed /initialized ?

I have tried downloading and re-installing FSUIPC 3.999w I have tried downloading and installing 3.999y5, I have double checked that WideFS is registered and the key has been accepted, it has and WideFS work fine.

A thought that does occur to me is I suppose Plan G does work with the free version of FSUIPC.

Any help for this aged flier gratefully received, as I say the problem is to problem solve why Plan G does not link with FS9 and the first step I wonder if it is somehow related to a perceived problem [error message on start up] that FSUIPC is not correctly installed or initialized and somehow my Squawkbox module has now gone absent.

Regards

Peter

Link to comment
Share on other sites

Perhaps a slightly related problem, though being well over 70 years young I admit that a lot of this technical stuff is well over my head.

Well I am 70 this year, so I'm joining you!

Yesterday [16th January] I purchased via Simflight the WideFS; my plan is to run FS2004 on my main PC with windows XP [sP3] and run Plan G on my Laptop with Windows 7.

I purchased WideFS okay and obtained the ‘key’, I registered it by downloading FSUIPC 3.999w and using the installer, everything works fine. WideFS works and connects from the laptop to FS9 on the PC.

Sorry, you need to update to 3.999y5 too. Same problem. there's only one check for both FSUIPC and WideFS registration.

I also notice for some reason the Squawkbox module is now missing from ‘Modules’ in FS 9.

Neither FSUIPC nor WideFS can be held responsibnle for that. Neither know anything about any other product DLLs and certainly never delete anything there.

I have tried downloading and re-installing FSUIPC 3.999w I have tried downloading and installing 3.999y5, I have double checked that WideFS is registered and the key has been accepted, it has and WideFS work fine.

So you are sure that you are now using 3.999y5? In that case, please show me the FSUIPC.LOG file. You can paste it into a message here. Make sure FS is closed first.

Regards

Pete

Link to comment
Share on other sites

Many thanks for the reply Pete.

This has turned out to be sincerely one of those ‘Senior Moments’, I am glad my daughter is not here otherwise she would have started browsing catalogues for ‘those homes’.

I again downloaded 3.999y5 and then moved the Dll into modules and I allowed it to overwrite the file in there.

I started FS9 and it loaded okay no warning messages and the Squawkbox module is showing again.

As a test I opened the copy of Plan G direct from my PC and it opened, connected and linked to FS9 without any problems. I then closed it down and started the laptop and opened WideFS and it connected with FS9.

I then started Plan G on the laptop and low and behold it connected with FS9 on the PC.

So in short what the problem has been all day is beyond me; perhaps I have got more than a little mixed up with versions of FSUIPC and which one I have installed or thought I had installed, anyway all is well again in this household.

So no ‘home’ for this aged flier just yet, a friend who is in such a place told me the other day that he thought Matron not allowing sharp objects was bad enough until news broke that the tunnel had been discovered.

Thanks again for your timely help.

Regards

Peter.

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.