Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ucla-cs!ucivax!orion.oac.uci.edu!ucsd!mvb.saic.com!dayton.saic.com!ake
From: ake@dayton.saic.com (Earle Ake)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: Handshake 2.20c questions
Message-ID: <1991Jun6.101336.1659@dayton.saic.com>
Date: 6 Jun 91 14:13:36 GMT
References: <1991Jun6.030522.3061@ecsvax.uncecs.edu>
Organization: Science Applications Intl. Corp., Dayton, Ohio
Lines: 25

In article <1991Jun6.030522.3061@ecsvax.uncecs.edu>, kms@ecsvax.uncecs.edu (Ken Steele) writes:
> If you don't know the answer to the first question, then how 
> about this one.  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 :-)

	If you use the command 'set terminal/inquire' on the VAX, the VAX sends
out an escape sequence and the terminal reports back what type it is with an
escape sequence.  The problem is Handshake also sets itself to VT220 mode
'for you'.  It shouldn't do this and it is a bug.  Send a message to Eric and
have him look at it.  I sent a message to him about it a year ago.  I didn't
get a response and it hasn't been fixed.  I am now using JR-Comm.


Earle
_____________________________________________________________________________
             ____ ____    ___
Earle Ake   /___ /___/ / /     Science Applications International Corporation
           ____//   / / /__                 Dayton, Ohio
-----------------------------------------------------------------------------
Internet: ake@dayton.saic.com        uucp: dayvb!ake         SPAN: 28284::ake