Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!rice!bcm!dimacs.rutgers.edu!rutgers!faatcrl!jprad From: jprad@faatcrl.UUCP (Jack Radigan) Newsgroups: comp.sys.amiga.datacomm Subject: Re: Features I'd like to see in JRCOMM Message-ID: <955@faatcrl.UUCP> Date: 8 Feb 91 23:48:41 GMT References: <1991Feb3.075026.1923@ckctpa.UUCP> <910203.083436@lerami.lonestar.org> <26681@uflorida.cis.ufl.EDU> <52363@sequent.UUCP> <19962@shlump.nac.dec.com> Organization: FAA Technical Center, Atlantic City NJ Lines: 14 guineau@wjg.enet.dec.com (W. John Guineau) writes: >Also, Why does JRCOMM not provide a proper terminal identification string >as a result of SET TERM/INQUIRE on VMS? I get "unrecognized terminal type" >and have to type SET TERM/DEV=VT100 manually. I have VT100 selected in the >setup menu. This is JRCOMM V1.01 I'm sending the standard terminal response string as per a DEC VT-340 manual, namely: VT-100: [?1;2c VT-102: [?6c -jack-