Tracy writes:
> If that were the case, I would also expect my dial
> up networking to also disconnect, but it does not.
Not necessarily. Your base connection to your ISP is merely a TCP/IP
simulation, either PPP or SLIP. For most of the time, no packets are going
back and forth under these protocols, so the world seems kosher at both ends
of the phone line, no matter how ratty it may occasionally get.
Telnet is a protocol that works on top of the TCP/IP emulation -- and in
contrast, it is constantly is checking the connection to see if it's still
up. Hiccups of any sort offer the possibility to disconnect the telnet
connection and leave the basic SLIP/PPP connection alone.
> Also, it didn't seem to do this before 95a.
Nothing has changed at all in QCTerm for quite some time in regards to its
telnet client. However, there can be a million other things that may have
changed some contemporaneously with your loading Version 0.95a, including the
weather (I'm not kidding. It's one of the biggest affectors of ordinary
home-phone line quality, but then are new neighbors with new phone lines,
modems aging, a change in software somewhere, etc.). It's just hard to guess.
Nonetheless, all indications that we get are that using telnet with QCTerm is
extremely robust and is hard to kill. As I said earlier, I'm wildly impressed
with its reliability. A proper diagnosis of your problem will require
equipment that you're not likely to have: a network packet sniffer and a POTS
line quality monitor.
Wirt Atmar
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|