Manfred Steinecke Posted December 3, 2007 Report Posted December 3, 2007 Hallo Pete, I need some help, I use Windows XP, fs9.1, FSUIPC 3.7.0.0, WideFS 6.7.5.0 I payed for keys FSUIPC 07/2006, WideFS 11/2007 with the same username and email-adress. I registered FSUIPC in 2006 and tried to register WideFS 2 weeks ago. But it doesn't happen. If I open the FSUIPC-Window in FS there is marked, that the registering of FSUIPC is correct and I have still to register WideFS. I press the button to register WideFS and the "Register"-window appears. There is entered the correct username and email-adress. But the window is "freezed". I can't write in the key. I can't press any button. The whole FS is blocked. Only I can shutdown the FS. Then I tried some ways to register WideFS. I started FS on the client-PC and there it's possible to register WideFS without a problem. When I start FS on the server-PC and WideFS on the cllient-PC the client-PC tries to connect. In the FS-windowbar of the server-PC appears "cannot serve... see log". The WideFSserver.log says, I have to register WideFS. But how I can do that on the server-PC, when the register-window always is freezed? Where is the mistake? regards Manfred
Pete Dowson Posted December 4, 2007 Report Posted December 4, 2007 I press the button to register WideFS and the "Register"-window appears. There is entered the correct username and email-adress. But the window is "freezed". I can't write in the key. I can't press any button. The whole FS is blocked. Only I can shutdown the FS. There is something external to FS interfering with its windowing facilities. Do you use "Window Blinds" or any other such window tailoring options? The only other thing I know of which can make the dialogues do such things occasionally is a rogue mouse driver, from Kensington I think. See if you can find it and uninstall it. your mouse should be fine with the normal Microsoft default mouse driver. Regards Pete
Manfred Steinecke Posted December 14, 2007 Author Report Posted December 14, 2007 Hallo Pete, I solved the problem, about I wrote. First I found out, that I can register WideFS on the clientPC. I compared the contents of the moduls-folder of the clientPC and the serverPC and then I removed all those files from the serverPC, which I didn't found in the clientPC. Then I couldt register WideFS on the severPC too and I had a succesfull connection of both PC's with WideFS. After then I moved the removed files back to the moduls-folder of the serverPC. But now I have another problem. I can't use my favorite aircraft PMDG737 NG 600-700, because the main-panel and FMC are dark. I asked the support of PMDG737 for help and find out, that the B737 is sucessfull working, if I remove the file FSUIPC.key out of the moduls-folder. But then in the register-window of FS9 (Menu - Modules - FSUIPC) are shown FSUIPC and WideFS as "unregistred" and so I can't connect the serverPC and the the clientPC. Enclosed I send you the file and ask you for help, please. [FILE DELETED] Regards Manfred
Pete Dowson Posted December 14, 2007 Report Posted December 14, 2007 the B737 is sucessfull working, if I remove the file FSUIPC.key out of the moduls-folder I need to see the FSUIPC LOG file. But the symptom you are getting only occurs if one of the following is true: 1. The FSUIPC.DLL file is corrupt, or 2. The GlobalSign signatire is not valid (both of these are logged), or 3. The PC's system date is EARLIER than your registration purchase, or 4. One or both of the Keys you are using in an illegal pirated one. Enclosed I send you the file and ask you for help, please. Never EVER post your KEY file openly like that! I have deleted it from open view and will now have to invalidate both FSUIPC and WideFS keys so that they cannot be used with your name by crooks and thieves! This is a shame because they do both appear to be legitimate. Check the first three points above. Show me the LOG file. NEVER show the KEY file -- if I ever want that I shall ask you to ZIP it and sent it to me privately. As it is your Keys will not work at all with the next FSUIPC update as I shall have to make them invalid. Write to me at petedowson@btconnect.com if you want to recover from this bad mistake. Regards Pete
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