Path: utzoo!utgpu!ugw.utcs.utoronto.ca!CUNYVM!IBMTCP-L Date: Mon, 5 Feb 90 17:59:34 EST Reply-To: IBM TCP/IP For VM List Sender: IBM TCP/IP For VM List From: Design is the negotiation of constraints Subject: RE: VT100 Terminals X-To: SAVAX!CUNYVM.CUNY.EDU!IBMTCP-L@"decvax@decvax.dec.com" To: UofToronto LAN redistribution Message-ID: <90Feb5.190330est.58631@ugw.utcs.utoronto.ca> Newsgroups: list.ibmtcp-l Distribution: ut Approved: devnull@gpu.utcs.toronto.edu >>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