microsuck's telnet client shell

  • Thread starter Thread starter Newbie JrSysAdmin
  • Start date Start date
N

Newbie JrSysAdmin

to understand how pathetic microsuck's telnet client shell in windows
2000 is, and to understandin general how pathetic windows is, consider
the following experiment i stumbled upon in my work:

i work on a remote solaris server by first telnet-ing to the box,
setting te display to my client's IP address, then running "xterm" in
the background, the output being captured by hummingbird's exceed on
my pc. i set the telent window to run the "top" command, to avoid
hangup, then i minimize the telent window and work in the xwindow.
when i am away from the xwindow for any period of time, i also run the
"top" command there, to keep it from hanging up as well.

here's what is interesting. i fell asleep the other day with "top"
running in the telnet window and the exceed xwindow. when i woke up,
the timestamp in the telnet window was for several hours ago, and the
window (and connection) was dead. but, the xwindow's top command was
current and running.

anyway, i've played around with this a bit, and i believe i have
determined that microsuck tries to "think for me" when a window is
minimized, in terms of caching of the display, etc in the minimized
window. i don't understand how anyone productive works with microsuck
software- it is simply not designed to reliably do a job.
 
Well now we all now why your only a "JrSysAdmin".
A professionnal in any field knows how to use his tools.
 
I actually like Microsoft's telnet client, but if you
require another do a google search, there are ample free
ones about.

Paul Devine
 
Yawn, another supposedly learned user attempts to speak to
the ignoring masses.

If you have a question, post away, opinions are ignored!
 
Back
Top