At 13:37 6/20/2002 -0500, FireBrick wrote: >What apparently then happens is the MSoft code keeps trying to make contact. > When the Msoft telnet code goes into its paralysis trying to >reestablish communication, it grabs all the cpu cycles and Seti eventually >shuts down and times out.
The MS code may go into paralysis on disconnect but why then do the other telnet clients (HyperTerm, and the MS Telnet Client) not slam the CPU to 100% when the disconnect occurs? Here they don't. Seems it's the DXB Internet cluster window telnet wrapper that's grabbling all the CPU resource. Perhaps the DXB internet cluster window code is not handling the results of the MS telnet connection drop outs the same as the other telnet clients? If a telnet connection drops the client application should not suck up all the CPU resource as a result. 73 Phil NA4M -. .- ....- -- -. .- ....- -- -. .- ....- -- -. .- ....- -- -. .- ....- -- Phil Duff NA4M [EMAIL PROTECTED] Georgetown, Texas
