[log in to unmask] wrote:

> No, no, no. It's only a problem when using VT. For some reason, more luck
> than not probably, when you use telnet, this kind of thing simply doesn't
> happen, no matter how ugly your exit. Because QCTerm only uses telnet, it
> doesn't belong in the list above. In fact, I've always prided myself that the
> easiest way to kill a QCTerm session is simply to press ALT+F4 or the window
> kill box and everything goes away very gracefully, including the HP3000
> session (actually it works identically as well in Reflection when the
> connection was made using telnet, but I won't mention that).

OK, I may have overstepped my bounds.  If you indeed close the
connection gracefully then my sincere apologies.  The typical response
to a close (by most emulators) is either nothing (causing a timeout) or
or a reset (the error 42).  The only way to avoid any console logging
in either VT or Telnet is to :BYE before you close, and even if you
enhance your emulator to generate a :BYE when closed, that won't work
if the user is in an application rather than the CI.  Perhaps an :EOF/:BYE
would be a bit more universal.

But Wirt is correct, you will not get the VT error as you are in telnet
mode.  You will, however, get the corresponding network transport error
with the same error code.

Jeff (a happy QCTerm user, no offense intended) :-)

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *