WideFS Client Locks up on Connect

[cbaye]

Peter,

I'm running WideServer (Machine name: BOEING) and two WideClinets (Machine names: MINCO_22254 and WHOOMAH) . One of the clients, MINCO_22254, connects and operates normally while the other, WHOOMAH, does not. When I start WideClient on WHOOMAH the window opens and indicates "Connected" but then the window cannot be moved, resized or closed (without using Task Manager) and CPU time for WideClient.exe fluxuates between 80 and 90%. The server status line in the MSFS Frame on BOEING indicates that 2 clients are connected. I have followed the network instructions in the manual and have not observed any changes in behavior. One more little tid-bit to keep this interesting (When WHOOMAH is the Server and BOEING is a client... Everything works just fine)

The logs for both clients and the server are listed below.

Server

********* WideServer.DLL Log [version 6.70] *********
Blocksize guide = 4096 (double allowed)
Date (dmy): 19/11/06, Time 19:36:34.989: Server name is BOEING
   116627 Initialising TCP/IP server
   116637 Initialising IPX/SPX server
   116637 ServerNode=0.0.2816.1243.50302
   116647 Initialising UDP/IP server
   118280 Broadcasting service every 1000 mSecs
   127313 Incoming connection Accepted ok (skt=2128) TCP
   127613 Connected to computer "MINCO_22254" running WideClient version 6.710 (skt=2128) TCP
   180539 Incoming connection Accepted ok (skt=2148) TCP
   180689 Connected to computer "WHOOMAH" running WideClient version 6.710 (skt=2148) TCP
   473270 Error 10054: client socket disconnected at Client: removing (skt=2128) TCP
   566404 Error 10053: client socket disconnected at Client: removing (skt=2148) TCP
   746303 Close signalled to clients
   747414 Closing down now ...
Memory managed:  Offset records: 136 alloc, 136 free
Read buffer usage:  846 alloc, 846 free, max in session: 1
Write buffer usage: 38690 alloc, 38690 free, max in session: 1
Throughput maximum achieved:  41 frames/sec, 1150 bytes/sec
Throughput average achieved for complete session:  8 frames/sec, 194 bytes/sec
Average receive rate from "MINCO_22254":  1 frames/sec, 36 bytes/sec
Average receive rate from "WHOOMAH":  0 frames/sec, 13 bytes/sec
********* Log file closed *********

Functioning Client

********* WideClient Log [version 6.71] Class=FS98MAIN *********
Date (dmy): 19/11/06, Time 19:38:45.740: Client name is MINCO_22254
      400 Attempting to connect now
      420 Trying TCP/IP host "Boeing" port 8002 ...
      420Okay, IP Address = 192.168.0.66
      430 Connection made okay!
    16684 New Client Application: "CDUDemo" (Id=1012)

   346388 ****** End of session performance summary ******
   346388 Total time connected = 346 seconds
   346388 Reception maximum:  40 frames/sec, 1054 bytes/sec
   346388 Reception average whilst connected:  35 frames/sec, 790 bytes/sec
   346388 Transmission maximum:  4 frames/sec, 430 bytes/sec
   346388 Transmission average whilst connected:  2 frames/sec, 65 bytes/sec
   346388 Max receive buffer = 518, Max send depth = 4, Send frames lost = 0

   346388 **************** Individual client application activity ****************
   346388 Client 1012 requests: 1627 (Ave 4/sec), Data: 3025919 bytes (8745/sec), Average 1859 bytes/Process

   346388 ********* Log file closed (Buffers: MaxUsed 5, Alloc 13856 Freed 13856 Refused 0) *********

Non-functioning Client

********* WideClient Log [version 6.71] Class=FS98MAIN *********
Date (dmy): 19/11/06, Time 19:39:33.765: Client name is WHOOMAH
      500 Attempting to connect now
      516 Trying TCP/IP host "Boeing" port 8002 ...
      516Okay, IP Address = 192.168.0.66
      531 Connection made okay!

   385938 ****** End of session performance summary ******
   385938 Total time connected = 385 seconds
   385938 Reception maximum:  2 frames/sec, 198 bytes/sec
   385938 Reception average whilst connected:  1 frames/sec, 43 bytes/sec
   385938 Transmission maximum:  0 frames/sec, 100 bytes/sec
   385938 Transmission average whilst connected:  0 frames/sec, 19 bytes/sec
   385938 Max receive buffer = 374, Max send depth = 1, Send frames lost = 0

   385938 ********* Log file closed (Buffers: MaxUsed 2, Alloc 740 Freed 740 Refused 0) *********

Thanks for the help.

- Chris

[Pete Dowson]

When I start WideClient on WHOOMAH the window opens and indicates "Connected" but then the window cannot be moved, resized or closed (without using Task Manager) and CPU time for WideClient.exe fluxuates between 80 and 90%. The server status line in the MSFS Frame on BOEING indicates that 2 clients are connected.

Something is bad in the drivers or network hardware on that Client. There a no loops or places in WideClient which can use all that processor time -- it is getting stuck deeper down, inside the drivers somewhere. All WideFS operations are aynchronous, based on reacting to Windows messages sent when data is ready to be read or the line is ready to accept data to be written.

One possibility is interrupts clashing. This is usually sorted out well by Windows XP, but it used to be a big problem on Win98 and so on. You don't say what operating system you are using, but that is somethnig to check. If the Network hardware on that Client is on a PCI card then moving the card to a different socket might help.

Otherwise all I can suggest is uninstalling the Network hardware and letting Windows find it again so it re-installs the drivers.

If you continue to make no headway, you can set "Log=DebugAll" in the Client's INI file, and this will put everything that the Client is doing into the Log (it may get very large), but based on past experience of this sort of problem I suspect it will only indicate that same as above. If you do produce a large log, ZIP it up and send it to me at petedowson@btconnect.com.

Regards

Pete

[cbaye]

Hello Peter,

I found the culpret. It was a program called QuickCare that was installed when I changed to a new DSL router from Qwest, my local telephone company. I usually shut down all extrainious programs in my system tray before flying but I guess I missed a few...

Thanks for you assistance.

- Chris

[Pete Dowson]

I found the culpret. It was a program called QuickCare that was installed when I changed to a new DSL router from Qwest, my local telephone company. I usually shut down all extrainious programs in my system tray before flying but I guess I missed a few...

Glad you found it. What does it actually do? I guess it hooks into stuff on the Network? I wonder why it affected an outgoing connection (WideClient connects TO WideServer) but not incoming ones, like when you tried the Server on that PC?

Regards

Pete