Derice Posted March 20, 2007 Report Share Posted March 20, 2007 I have just installed a who new fresh system. Vista, FS9, all my addons, etc. When I start FS and select the PMDG 747, it gives me the error message that FSUIPC.DLL is too old. I checked and I have version 3.73. Tried to reinstall the 747, but that didn't work. Any suggestions to what might be the issue? The 737 also has some issues, like the panels aren't showing any infromation, can't use the overhead panel, fmc, etc. UAC on or off didn't make any change. Any idea what could be the issue? Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 20, 2007 Report Share Posted March 20, 2007 I have just installed a who new fresh system.Vista, FS9, all my addons, etc. When I start FS and select the PMDG 747, it gives me the error message that FSUIPC.DLL is too old. I checked and I have version 3.73. Please look at the FSUIPC.LOG file, in the FS Modules folder. Does it show any errors? Run FS again, close it down, show me the Log, all of it. Regards Pete Link to comment Share on other sites More sharing options...
Derice Posted March 21, 2007 Author Report Share Posted March 21, 2007 Thanks, but i fixed it. Cost me a whole reinstall of FS before I discoverd it. Entered a wrong widefs key, very annoying that the whole FS then gets mixed up, instead of just reporting an error. Link to comment Share on other sites More sharing options...
Pete Dowson Posted March 21, 2007 Report Share Posted March 21, 2007 Thanks, but i fixed it.Cost me a whole reinstall of FS before I discoverd it. Entered a wrong widefs key, very annoying that the whole FS then gets mixed up, instead of just reporting an error. Well, it doesn't! That's for certain. To start with, a really wrong Key would be rejected in the first place -- you wouldn't have been able to enter it! It would fail the basic checks. Since version 3.53 of FSUIPC, the only type of key which can cause things to go wrong later are those which have been made by one of the Pirate Key generators around. These look like valid keys to the entry-checker's processing, but are wrong enough to corrupt the decoding of the interface data. The fix is simple: just delete the FSUIPC.KEY file and re-register, entering only legitimate, non-pirated, keys. There is no re-installation of anything at all ever needed, as no permanent changes are made. The only result of the bad key is bad data supplied to FSUIPC client applications. Regards Pete Link to comment Share on other sites More sharing options...
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now