Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!public!thad
From: thad@public.BTR.COM (Thaddeus P. Floryan)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: Handshake 2.20c questions
Keywords: kermit, terminal
Message-ID: <2969@public.BTR.COM>
Date: 6 Jun 91 20:51:59 GMT
References: <1991Jun6.030522.3061@ecsvax.uncecs.edu>
Organization: BTR Public Access UNIX, Mountain View CA
Lines: 23

In article <1991Jun6.030522.3061@ecsvax.uncecs.edu> kms@ecsvax.uncecs.edu (Ken Steele) writes:
>[...]
>Handshake is set for VT102 mode.  When I
>am logged into one Vax and then telnet to another Vax, upon
>connecting, Handshake flips into VT220 mode, the cursor dives
>to the bottom right of the screen and stays there until I
>manually change the term setting back to VT102.  Is there a
>way to prevent this?  Or am I doomed to an eternity of doubt
>about what was in the login message :-)
>[...]

You say "Vax" but I suspect you mean a Vax running VMS.

What's doing-you-in is a "SET TERM/INQUIRE".

Check your LOGIN.COM for that (^^^^^^^^^^) and remove it.

If you're unfortunate enough to have a system where the SET TERM/INQUIRE is
in the system-wide LOGIN.COM, then either ask your site admin to remove that
from that file OR to alter your UAF entry to NOT execute the system-wide
LOGIN.COM and to just execute your personal LOGIN.COM instead.

Thad Floryan [ thad@btr.com (OR) {decwrl, mips, fernwood}!btr!thad ]