Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ames!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: <1991Jun8.212156.1663@dayton.saic.com> Date: 9 Jun 91 01:21:56 GMT References: <1991Jun6.030522.3061@ecsvax.uncecs.edu> <2969@public.BTR.COM> Organization: Science Applications Intl. Corp., Dayton, Ohio Lines: 31 In article <2969@public.BTR.COM>, thad@public.BTR.COM (Thaddeus P. Floryan) writes: > You say "Vax" but I suspect you mean a Vax running VMS. > > What's doing-you-in is a "SET TERM/INQUIRE". > > Check your LOGIN.COM for that (^^^^^^^^^^) and remove it. > > If you're unfortunate enough to have a system where the SET TERM/INQUIRE is > in the system-wide LOGIN.COM, then either ask your site admin to remove that > from that file OR to alter your UAF entry to NOT execute the system-wide > LOGIN.COM and to just execute your personal LOGIN.COM instead. The systems that have 'SET TERM/INQUIRE' have it there for a reason. If you remove it and then try to use an application that uses the SMG (Screen ManaGement) service, it might fail. Anymore by default the terminal lines are set 'unknown' and the 'set term/inquire' is used to determine what type of terminal you have and set the terminal settings properly. The REAL problem is REAL vt100 emulators should know how to handle that escape sequence properly. Handshake is returning the correct string but in the process is resetting itself to a VT220 ALL the time! The solution is to have Eric fix the code not remove the 'set term/inquire' from the login.com! Earle _____________________________________________________________________________ ____ ____ ___ Earle Ake /___ /___/ / / Science Applications International Corporation ____// / / /__ Dayton, Ohio ----------------------------------------------------------------------------- Internet: ake@dayton.saic.com uucp: dayvb!ake SPAN: 28284::ake