I just tested this now under WindowsME, and find that EasyTerm (a free telnet client) does not have the problem, whereas DXBase2003 does everytime I have tried. I think one will have to look at DXB for cause of this one, I agree with Phil.
Ron ----- Original Message ----- From: "Phil Duff" <[EMAIL PROTECTED]> To: "FireBrick" <[EMAIL PROTECTED]>; "Ron Stordahl" <[EMAIL PROTECTED]>; <dxbase@mailman.qth.net> Sent: Thursday, June 20, 2002 1:58 PM Subject: Re: [DXBase] Internet cluster window > 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 > > >
