Pete,
Hope you had a good holiday.
I've got a problem with wideclient taking 99% of the CPU cycles, even when nothing is operating across the network.
Here's the background.
I run a registered WideFS 6.51 across two desktop computers running on WinXP SP2, both on the same home network subnet (plugged into the same router) using the same network workgroup name. The wideclient 6.5.1 system has been operating perfectly until about 2 weeks ago. Suddenly, upon starting wideclient, I noticed that the applications running via wideclient were showing no connection to FS, even though WideFS was indicating a connection.
Opening task manager, wideclient was using 99% of the CPU and choking off the other apps. What is so puzzling is that this was a sudden change and wideclient worked so well before, hardly using 1% of the CPU, if that!
I have deleted wideclient and reinstalled it, fiddled with the INI file, but nothing seems to help. I have 2 other desktop systems and a laptop, all running WinXP SP2, and wideclient works as expected on these other systems. Therefore, I think I can eliminate wideserver as the problem.
I am using FSUIPC 3.60 on the FS computer.
Here is the log from wideclient on the problem computer:
********* WideClient Log [version 6.51] Class=FS98MAIN *********
Date (dmy): 14/05/06, Time 17:41:11.604: Client name is BRUCE-DESKTOP
140 Opening GPSout port COM8, speed=4800 -- OK!
151 Attempting to connect now
151 Trying TCP/IP host "Aurora" port 8002 ...
151Okay, IP Address = 192.168.1.5
151 Connection made okay!
Here is the wideclient.ini file:
; PLEASE SEE WideFS documentation for parameter details
; =====================================================
[Config]
Port=8002
Window=250,250,160,31
Visible=Min
ServerName=Aurora
UseTCPIP=Yes
ButtonScanInterval=20
ClassInstance=0
NetworkTiming=5,1
PollInterval=2000
ResponseTime=18
ApplicationDelay=0
TCPcoalesce=No
WaitForNewData=500
MaxSendQ=100
OnMaxSendQ=Log
NewSendScanTime=50
Priority=3,1,2
Log=DebugAll
; -----------------------------------------------
[user]
Log=Errors+
; ===============================================
[GPSOut]
Port=COM8
Speed=4800
; ===============================================
Here is the wideserver log file:
********* WideServer.DLL Log [version 6.51] *********
Blocksize guide = 4096 (double allowed)
Date (dmy): 14/05/06, Time 15:11:02.953: Server name is AURORA
229000 Initialising TCP/IP server
229078 Initialising IPX/SPX server
229078 IPX/SPX socket() failed [Error=10047] Address family not supported by protocol family
229078 Failed to start IPX/SPX Server
230094 Broadcasting service every 1 mSecs
9008875 Incoming connection Accepted ok (skt=22540)
9008891 Connected to computer "BRUCE-DESKTOP" running WideClient version 6.510 (skt=22540)
9008891 Client capabilities: 04 (GPSout=Y) (skt=22540)
9039750 Error 10054: client socket disconnected at Client: removing (skt=22540)
9039750 Auto send stopped before sending all data (0 of 136 sent), Error=10038 (skt=-1)
Here is my wideclient.ini file:
; PLEASE SEE the documentation for parameter details
; ==================================================
[Config]
Port=8002
AutoRestart=0
AutoUpdateTime=13
MaximumBlock=4096
NoStoppedRestarts=Yes
RestartTime=10
SendTimeout=15
TCPcoalesce=No
AdvertiseService=Yes
; -----------------------------------------------
[user]
Log=Errors+
; ===============================================
[ClientNames]
1=BRUCE-DESKTOP
Wideclient literally sucks up every available cpu cycle. I am unable to shut the program down by closing the window. I have to terminate the process from task manager.
Reading through previous posts, someone else mentioned this problem and found that some DLLs from another program were binding to wideclient and using up CPU cycles. I downloaded the Depends21_x86 program that analyzes what wideclient loads when it runs, but I don't know enough about wideclient to tell if anything extra is getting loaded. I tried to compare the depends21 log between a computer that is operating correctly and the computer with the problem, but that didn't help either.
I've disabled all firewalls, virus protection, and anything else that could be a factor in the network transfer.
Do you have any suggestions? Are there any other logs that I can provide to help diagnose the problem? Unfortunately, I can't tell you what programs were loaded onto the computer between the time wideclient was working and stopped working correctly. It's just so odd that something is making wideclient behave so erratically.
Thanks for any assistance you can provide.
Bruce