Path: utzoo!attcan!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!ames!sgi!shinobu!odin!warp.esd.sgi.com!kipp
From: kipp@warp.esd.sgi.com (Kipp Hickman)
Newsgroups: comp.sys.sgi
Subject: Re: iris-ansi or vt100
Message-ID: <1990Dec17.175105.26724@odin.corp.sgi.com>
Date: 17 Dec 90 17:51:05 GMT
References: <9012122159.AA09221@poly1.nist.gov>
Sender: news@odin.corp.sgi.com (Net News)
Reply-To: kipp@warp.esd.sgi.com (Kipp Hickman)
Organization: Silicon Graphics, Entry Systems Division
Lines: 17

In article <9012122159.AA09221@poly1.nist.gov>, rbriber@POLY1.NIST.GOV writes:
|> 
|> We have users on our Iris 4D80GT running 3.2.0 that want to telnet to
|> a cdc cyber 855 running either NOS and NOS-VE.  The problem is that the
|> cyber 855 doesn't know about Iris-ansi terminals.  Now we could write
|> a term def for the cyber so it would understand Iris-ansi terminals but
|> no one really wants to take the time to figure out how to do this (or 
|> where to look for the necessary information).  Much more convenient would
|> be to have the Iris look like something simple such as a vt100 or vt102 for
|> the telnet session.  Does anyone know a way to do this.  Email directly or
|> post to the net.
|> 
|> Thanks in advance.
wsh emulates an ansi terminal, not a vt100 terminal (sorry).  In a forth-coming  software release, wsh will also emulate vt100 terminals as well...

					kipp hickman
					silicon graphics inc.