Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!decwrl!pa.dec.com!shodha.enet.dec.com!elvira!ridder
From: ridder@elvira.enet.dec.com (Hans Ridder)
Newsgroups: comp.sys.amiga.datacomm
Subject: Re: Handshake 2.20c questions
Message-ID: <3339@shodha.enet.dec.com>
Date: 10 Jun 91 17:14:23 GMT
References: <1991Jun6.030522.3061@ecsvax.uncecs.edu> <2969@public.BTR.COM> <1991Jun8.212156.1663@dayton.saic.com> <2996@public.BTR.COM>
Sender: news@shodha.enet.dec.com
Organization: Digital Equipment Corporation, Customer Support Center
Lines: 58

In article <2996@public.BTR.COM> thad@public.BTR.COM (Thaddeus P. Floryan) writes:
>The REAL problem is NOT how DEC VT2?? and VT3?? terminals and clones (both
>hardware and software) operate.  Handshake mimics a real DEC VT2?? properly.

Never run Handshake, but I don't think so.... (see below)

>I have "real" DEC VT100, DEC VT102, DEC VT220, and DEC VT340 terminals at my
>office and can see how they are definitely braindamaged.
>
>A REAL DEC VT220, operated in DEC VT100 mode, will shift to VT2?? mode after
>a "SET TERM/INQUIRE" under VMS 4.3, 4.4, 4.7, and all 5.*.

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.

>The situation got to be so frustrating that I fixed everyone's LOGIN.COM files
>on my systems (yeah, multiple VAXen running VMS (ugh)) to simply set the term
>mode to VT100 upon login.

Looks to me like you didn't need to....

>The "problem" is that the DEC terminals, upon receipt of the inquiry
>code, indicate they're a (for example) DEC VT220 in VT100 mode and then
>setup to VT200 mode; though it's been a while since I've connected DLM
>test equipment to check this, it's my recollection that VMS itself
>instructs the terminal to enter VT200 mode even though the user had the
>terminal set in VT100 mode.

The terminals send back whatever ID you tell them to.  If you want to be
a VT100, then set the ID to VT100.  Yes, I agree that it doesn't make
much sense for them to say they're a VT220 when set to VT100 mode...so
change the ID.

>IN ANY EVENT, it is NOT a problem with Handshake (in this regards); Handshake 
>does exactly what DEC's own terminals do in this respect.  Not only that, 
>EVERY VT200 clone terminal I've tested over the years (e.g. Liberty, Falco, 
>et al) does the same annoying thing ONLY on a VMS system.  

Well, if Handshake doesn't allow you to set the ID, then it should be
sending a VT100 ID when in VT100 mode.  In that case VMS doesn't mess
with the terminal.  So, if Handshake is sending a VT220 ID when in VT100
mode, and there's no way to change it, I say it's broken.

>Why do you think VMS is colloquially known as the Vomit Making System?  :-) 

Dunno, never heard that one before.  And we usually know most of those
*clever* sayings.  Heck, we usually make them up!

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

-hans
------------------------------------------------------------------------
  Hans-Gabriel Ridder			Digital Equipment Corporation
  ridder@elvira.enet.dec.com		Customer Support Center
  ...decwrl!elvira.enet!ridder		Colorado Springs, CO