Jump to content
The simFlight Network Forums

FSX - FSUIPC/Windows7 Pro 64


HarryZ
 Share

Recommended Posts

Peter,

I have spent hours trying to get my full sized simulator working with Windows 7 Pro 64, FSUIPC and Wideserver (both registered) and Project Magenta loaded on a local network with 3 other XP computers.

I have a triple bootable system and while using XP 64, everything works fine. ( XP 64 is loaded on the D partition and FS X is loaded on the C parition) But I recently loaded Windows Pro 64 on the E partition of the HD and have loaded FS X (again, making two installations under different operating systems) on the E partition as well. I have the latest FSUIC and Wideserver/Wideclient versions.

I have read Enrico S's Windows 7 guide to setting up a network with PM software on other non Windows 7 computers. All of the suggestions with permissions, etc have been followed for 7's network settings. The main 7 computer can see all the local network XP computers and data can be transferred between them. But after starting FS X in 7, the XP computers try to connect to the 7 computer, without success. In looking at the Wideclient log files with all 3 XP computers, they open port 8002, and search from the main 7 computer's local network IP address 192.168.1.101. But after several attempts, they give up. These logs do excactly the same searching when running FS X under XP 64 and they connect every time!

I did notice when I installed FSUIPC, one comment in the DOS screen showed that it could not find the FSX.CGF file and that is the folder where the DLL.XML file must be copied. I did a search for this file and the system did find and open it. I noticed that one bit of code showed that FS X was located in the C:\FSX folder but the FS X loaded under Windows 7 is loaded in the E:\FSX folder. Whether this is causing the problem or is totally irrelevant I don't know.

I have tried everything I know including running Enrico's PM file check (everything was OK except it couldn't find the CDU FMC working because those XP computers could not connect to the main 7 computer) I am at a total loss as to why Wideclient on all the XP local network computers can't connect with the Windows 7 main FS X computer.

Any help you can give me at this time would be greatly appreciated.

Thanks.

Harry

Link to comment
Share on other sites

I have read Enrico S's Windows 7 guide to setting up a network with PM software on other non Windows 7 computers. All of the suggestions with permissions, etc have been followed for 7's network settings. The main 7 computer can see all the local network XP computers and data can be transferred between them. But after starting FS X in 7, the XP computers try to connect to the 7 computer, without success. In looking at the Wideclient log files with all 3 XP computers, they open port 8002, and search from the main 7 computer's local network IP address 192.168.1.101. But after several attempts, they give up. These logs do excactly the same searching when running FS X under XP 64 and they connect every time!

Please show me the WideServer log and one instance of the Client log with this problem. Please close both FS and WideClient down first. You can paste the logs into a message here.

I did notice when I installed FSUIPC, one comment in the DOS screen showed that it could not find the FSX.CGF file and that is the folder where the DLL.XML file must be copied. I did a search for this file and the system did find and open it. I noticed that one bit of code showed that FS X was located in the C:\FSX folder but the FS X loaded under Windows 7 is loaded in the E:\FSX folder. Whether this is causing the problem or is totally irrelevant I don't know.

It isn't relevant to WideFS, but it does indicate something wrong with how FSX has been installed. The installation path is obtained from the Registry entries made by the FSX installer and should be correct or you could be in for other problems. You didn't "roll back" to a previous Windows restore point after installing FSX, did you? And you did actually install FSX rather than make a copy of the C installation in the E drive? (You CAN do such copying, but only after installing properly first).

I have tried everything I know including running Enrico's PM file check (everything was OK except it couldn't find the CDU FMC working because those XP computers could not connect to the main 7 computer) I am at a total loss as to why Wideclient on all the XP local network computers can't connect with the Windows 7 main FS X computer.

I know of no possible reasons other than firewall or incorrect settings. How are the Clients knowing the IP address is 192.168.1.101? Have you given them the explicit IP address and protocol? And are you sure that is correct? Generally it is much better to just make sure all the PCs are in the same WorkGroup (which they won't be by default), and leave the connection to occur automatically -- i.e. no Procol or Server parameters in the Client.INI files.

Regards

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.