BEC@ALBNYVM1.BITNET (Ben Chi) (02/06/90)
Has anyone run into a situation telneting to a remote host only to find that it insists on you being a VT100 terminal? (That is, it sends you all sorts of screen formatting codes such as ESC [ 3.) And, if so, is there anything that can be done about it to make the dis- play useable? (I searched the IBM-TCP archives for "VT100" but got no hits at all.)
fleischmann@DECVAX.DEC.COM (Design is the negotiation of constraints) (02/06/90)
>>Has anyone run into a situation telneting to a remote host only to find >>that it insists on you being a VT100 terminal? (That is, it sends you >>all sorts of screen formatting codes such as ESC [ 3.) >> >>And, if so, is there anything that can be done about it to make the dis- >>play useable? (I searched the IBM-TCP archives for "VT100" but got no >>hits at all.) If it is a VAX/VMS system you want to tell it that you are a "glass" scope and have to be treated as if you were a hardcopy terminal. I use the command: $set term/la3 /marc ==== Marc Fleischmann - Manager, Enterprise Automation Sanders Associates, Inc. Nashua, NH 03061-0868 (603) 885-5050 UUCP: ...decvax!savax!nhqvax!fleischmann