Disabling Quit On Telnet

[John Esak]

>
> 1) The handling of the "X" button event is only really possible to do at
> the client level.  That isn't anything Scott will be able to do
> without the
> vendor changing the client.  However, I know for a fact that you can tell
> the Windows wm not to draw those three buttons -at all-.  If that were
> done, there's no way to click on them, obviously.  A feature you might
> consider from even an aesthetic standpoint--why have decorations
> there that
> are rendered unusable anyway?
>

As you know... Alt-F4 closes any active window... you and I both use this,
preferring keystrokes to mouse clicking...  Would getting rid of the 3
controls at the top right of the window *also* obviate the Alt-F4?  That
*world* be kind of cool.... just curious.

This is probably out of the scope of this discussion, but when we set up our
thin  client Wyse Winterm screens... we always take away all decoration,
menu pads, status bars, etc.  This makes them look just like a Wyse 50 for
example... and the user can not do anything to leave the application other
than through tthe provided means.

If they lose the telnet connection.... doesn't happen often, but
sometimes..the telnet session does not die... this creates havoc when they
log back in again with the same user name.  So, we use a little script in
their login dot file (in our case .profile) that kills all the old telnets
with that particular user name.  In our situation, there are *never* *ever*
two logins with the same name as those used to login on these WinTerms.
This was the *only* solution we could think of to keep things from getting
scrambled up.

Not sure if any of this helps this discussion like I said... but this stuff
was critically important for us, since we direct the printing from these
particular logins to particular network printers... and there are lots of
them all around the country.

John