Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!decwrl!public!thad
From: thad@public.BTR.COM (Thaddeus P. Floryan)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: Handshake 2.20c questions
Message-ID: <3024@public.BTR.COM>
Date: 11 Jun 91 11:11:44 GMT
References: <1991Jun6.030522.3061@ecsvax.uncecs.edu> <2969@public.BTR.COM> <1991Jun8.212156.1663@dayton.saic.com> <2996@public.BTR.COM> <3339@shodha.enet.dec.com>
Organization: BTR Public Access UNIX, Mountain View CA
Lines: 26

In article <3339@shodha.enet.dec.com> ridder@elvira.enet.dec.com (Hans Ridder) writes:
>[...]
>I just tested this on a *real* VT220, VT320, and a VT330.  When set to
>VT100 mode, they *stay* in VT100 mode after a SET TERM/INQUIRE.  Note
>that you have to select "VT100 ID" when in VT100 mode.  If you leave it
>at VT220 then yes, VMS, for whatever reason, changes the terminal into
>its native mode.
>[...]

Now THAT (selection of a "VT100 ID") is news to me and some 300 other people
(over the years) at my company.  We've been using DEC computers and terminals
for a long time (just celebrated our company's 19th anniversary last week
(June 3, 1972)) and NONE of us noticed that.

OK, I'm taking in DLM (Data Line Monitor) test equipment to my office tomorrow
and will check this out (besides re-reading the VT2?? and VT3?? manuals and
perusing their SETUP screens).  Sheesh, with 3 DEC-20, four VAXen, and umpteen
DEC terminals one would've thought this would have been noticed before; perhaps
the EPROM code in our terminals is o-l-d.  OOPS, correct that to be two DEC-20;
just remember one 2060 was let-go last week along with Cisco's and Stanford's
(though I did keep the nameplate).  Sigh, approaching the end of another era.

'Sfunny, though, I never had problems with the SAME terminals operated on UNIX
systems (with their equivalent of a SET TERM/INQUIRE (on some systems)). Hmmmm.

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