Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!bsu-cs!cfchiesa
From: cfchiesa@bsu-cs.bsu.edu (Christopher Chiesa)
Newsgroups: comp.sys.atari.8bit
Subject: Re: Kermit65
Summary: Why Vax's don't recognize Kermit65 as VT100
Message-ID: <10714@bsu-cs.bsu.edu>
Date: 6 Feb 90 18:57:25 GMT
References: <21748@pasteur.Berkeley.EDU> <18455.25cd7749@merrimack.edu>
Distribution: usa
Organization: CS Dept, Ball St U, Muncie, IN, USA
Lines: 22

In article <18455.25cd7749@merrimack.edu>, ain1496e@merrimack.edu writes:
>          If your using Kermit65 with a Vax system, you may have to type
>   Set Term/VT100 at the Vax command line prompt.   I'm also using Sparta 3.2d
>   to run Kermit (on a 1050).  On VAX's, at login Kermit isn't recognized as
>   being a vt100 for some reason and thats why the Set command is necessary.
>   If your not using a VAX though I can't help you.

At login (or on issuance of the SET TERM/INQUIRE command) the Vax sends out
an escape sequence that's supposed to cause a DEC terminal to respond with
another, identifying escape sequence.  This sequence has evolved over the
years into a pretty comprehensive report of terminal capabilities, espe-
cially as the VT200 and 300 series have come along...

Anyway, KERMIT65 doesn't respond to the Vax's "inquiry" sequence, although
if it didn't intercept it at all you would see part of it on the screen...
(To John Dunning: what about it?  Fix in a new version of Kermit65?  :-) )

   C.Chiesa (usually posting as Chris_F_Chiesa@cup.portal.com -- mail
    to me HERE will go THERE, even.)
-- 
UUCP: <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!cfchiesa 
cfchiesa@bsu-cs.UUCP