FSX FSUIPC4 WIDEFS 2 PCs on home network

[wlix261]

Hello

As orther simmers, I want to install on a SECOND PC (Laptop Win7-64k) as many of the external apps I have been using on my MAIN desktop (Win7-64k), where I have been using FSUIPC4 (registerd) successfully. One of those apps is FSCommander.

(Others are IvAp 2.0, Teamspeak, and Active Sky 2012 (although I believe those do not use FSUIPC))

Having read the FSUIPC4 and WIDEFS install instructions, it appears I succeeded installing and registering WIDEFS in the SECOND PC as well as making the change in the MAIN PC (running Install again, entering the 2 keys, etc. I also disabled the Win7 firewall on the 2 PC's, and I set the 2 clocks on sync on the 2 PC's and set the home network so that both C:\ drives of the PC's are shared (read write etc) and mapped for access from each other PC.

My issue is that I am not sure my installation is working OK. Please tell me if my symptoms are normal before I continue with the FSCommander installation in the SECOND PC, which having read the instructions seems rather complicated.

My installation does the following: I first launch FSX on the MAIN PC, then I launch WideClient.exe from the desktop shortcut in the SECOND PC. The indications I see are the message on the frame of the window of WideClient FS98 Eliminator - Waiting for a connection on the SECOND PC, and the message WideServer: waiting for clients on the FSX window on the MAIN PC. And nothing else happens. I expected to see some indication that FSX and WideServer are talking.....

Thanks in advance..

[Pete Dowson]

and I set the 2 clocks on sync on the 2 PC's and set the home network so that both C:\ drives of the PC's are shared (read write etc) and mapped for access from each other PC.

No need for any of that for WideFS. Files aren't involved. Though you probably need to share some folders for FS commander.

My installation does the following: I first launch FSX on the MAIN PC, then I launch WideClient.exe from the desktop shortcut in the SECOND PC. The indications I see are the message on the frame of the window of WideClient FS98 Eliminator - Waiting for a connection on the SECOND PC, and the message WideServer: waiting for clients on the FSX window on the MAIN PC. And nothing else happens. I expected to see some indication that FSX and WideServer are talking.....

They are not talking to each other. To see why I need to see the Log files -- WideServer.log from the FS Modules folder on the server, and WideClient.log from the folder in which you are running WideClient. You can paste the text from files into a message here.

Pete

[wlix261]

Thanks for the prompt reply. For some reason I found 3 candidate files for that criteria:

(1) Content of WideClient.log on SECOND PC

********* WideClient Log [version 6.995] Class=FS98MAIN *********

Date (dmy): 22/06/13, Time 11:51:54.454: Client name is AE-LENOVO

124 LUA: "C:\Users\alvaro\Documents\WideClient\WideFS\Initial.LUA": not found

171 Attempting to connect now

171 Trying to locate server: Need details from Server Broadcast

171 Failed to connect: waiting to try again

2230 Attempting to connect now

45474 Trying to locate server: Need details from Server Broadcast

Content of Wideclient0.log also on SECOND PC

********* WideClient Log [version 6.995] Class=FS98MAIN *********

Date (dmy): 22/06/13, Time 08:49:53.691: Client name is AE-LENOVO

124 LUA: "C:\Users\alvaro\Documents\WideClient\WideFS\Initial.LUA": not found

187 Attempting to connect now

187 Trying to locate server: Need details from Server Broadcast

187 Failed to connect: waiting to try again

2246 Attempting to connect now

45490 Trying to locate server: Need details from Server Broadcast

10888745 ****** End of session performance summary ******

10888745 Total time connected = 0 seconds

10888745 Reception maximum: 0 frames/sec, 0 bytes/sec

10888745 Transmission maximum: 0 frames/sec, 0 bytes/sec

10888745 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

10888745 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

Content of WideServer0.log on MAIN PC

********* WideServer.DLL Log [version 7.90] *********

Blocksize guide = 8192 (double allowed)

Date (dmy): 22/06/13, Time 09:14:09.124: Server name is AE-ABAJO-PC

15975 Initialising TCP/IP server

15975 Initialising UDP/IP server

16115 Broadcasting service every 1000 mSecs

9443146 Closing down now ...

Memory managed: Offset records: 4439 alloc, 4438 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec

********* Log file closed *********

[Pete Dowson]

Thanks for the prompt reply. For some reason I found 3 candidate files for that criteria:

Wideclient was still running. The current log is WideClient.log, the previous one Wideclient0.log. It saves the previous one so that when needed it can be restarted without loss of information.

45474 Trying to locate server: Need details from Server Broadcast

This shows that Broadcasts from the Server are not reaching the Client. This only usually occurs if you have different Workgroups. Did you check that your Workgroup name was the same on both PCs?

You could also actually try specifying the Server name and the Protocol, as suggested in the documentation. Please do refer to the User Guide, the section marked

Configure your Network

IT IS IMPORTANT FOR ALL USERS TO READ AT LEAST PART OF THIS!

There's a reason it is so highlighted! ;-)

Pete

[wlix261]

Thanks a lot for the prompt reply.

The WORK-GROUP name in the MAIN PC had a hypen that was not included in the WORKGROUP name in the SECOND PC. So I edited that one.

Also I went ahead and followed the recomendation in the instructions and edited the [Config] section of the WideClient.ini file (SECOND PC) with:

ServerName=AE-ABAJO-PC (Name of my MAIN PC)

Protocol=TCP

This fixed my problem.

Lesson learnt: Pay attention to hypens

Also, interestingly, as far as moving files, mapping drives, etc, I did not notice anything wrong with the workgropu setting. maybe for those tasks windows is less strict when the difference is a hypen. Who knows...