Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!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: <3326@shodha.enet.dec.com> Date: 9 Jun 91 01:34:22 GMT References: <1991Jun6.030522.3061@ecsvax.uncecs.edu> <1991Jun6.101336.1659@dayton.saic.com> <1991Jun8.194853.22312@newserve.cc.binghamton.edu> Sender: news@shodha.enet.dec.com Organization: Digital Equipment Corporation, Customer Support Center Lines: 42 In article <1991Jun8.194853.22312@newserve.cc.binghamton.edu> consp03@bingsuns.cc.binghamton.edu (Kriston J. Rehberg) writes: >In article <1991Jun6.101336.1659@dayton.saic.com>, ake@dayton.saic.com >(Earle Ake) writes: >|> 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 > ^^^^^^^^^^^ > nope, it's not a bug! > >Most VT220's and VT320's, while in a mode other than VT220, will >automatically switch themselves into VT220 mode when they receive a >TERMINAL/INQUIRE message. Well, this isn't a feature of the VTxxx terminals. It's been a while since I looked at what VMS sends during a SET TERMINAL/INQUIRE, so it's possible that VMS thinks it knows better, and changes you to the terminal's "native" mode, but I've never heard of it. I'll check it when I'm in the office. >I'm not sure it is a bug, but it could be that only VT220 mode HAS the >inquire message, so it automatically switches to that mode when it sees >the message. It seems to be a hack to do the inquire properly, or just >a firmware bug. Again, I'm not sure but it's definitely not a problem >with Handshake. All VT terminals (from VT52 to VT1300) have an inquire ability, none of them change modes when asked what they are (unless they're broken.) If anything is going on, it's either a bug in Handshake, or VMS is slamming on the terminal. In any case, Handshake should do what a real VTxxx does, since that's what it's supposed to be emulating, right? If a real VTxxx doesn't exhibit the behavior, then Handshake is broken. >|>Earle >Kris -hans ------------------------------------------------------------------------ Hans-Gabriel Ridder Digital Equipment Corporation ridder@elvira.enet.dec.com Customer Support Center ...decwrl!elvira.enet!ridder Colorado Springs, CO