Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!im4u!oakhill!tomc
From: tomc@oakhill.UUCP
Newsgroups: comp.sources.d
Subject: VT100 emulation on Sun
Message-ID: <842@oakhill.UUCP>
Date: Tue, 24-Feb-87 12:21:19 EST
Article-I.D.: oakhill.842
Posted: Tue Feb 24 12:21:19 1987
Date-Received: Fri, 27-Feb-87 01:20:47 EST
Organization: Motorola Inc. Austin, Tx
Lines: 26
Keywords: VT100 Sun

Somewhere along the way I lost my copies of both vtem and vt100tool for Sun
2s (the latter I believe out of Mitre Corp.).  I would like to get one or
both of them back if possible, although we now have Sun 3s so the vt100tool
package may be of limited usefulness (Sun also sells a VT100 emulator now;
costs $2800, but I guess does a good job of screen handling, key mapping,
etc.).

When I used vtem on the Sun, however, things did not work right.  I would
start up vtem in a shell window, then run Kermit to talk to a VAX/VMS system
out one of the serial ports.  If I tried to run any kind of full screen
application (like MicroEMACS on the VAX) or even try a TYPE/PAGE command the
VAX would choke.  It would abort the application with some kind of buffer
overflow message, then start spitting out DCL command prompts in rapid
succession.  If I got out of Kermit and back in, echo would be off on the
VAX side.  Now I realize there are many layers of software involved here and
something is bound to break, but this is very strange and repeatable
behavior.  Should I be using something like tip instead of Kermit?  Is vtem
somehow broken?  Is the VAX broken (or have I not set something properly)?
Any clues greatly appreciated (also, if you happen to have vtem lying
around...).
-- 

Tom Cunningham     "Good, fast, cheap -- select two."
USPS:  Motorola Inc.  6501 William Cannon Dr. W.  Austin, TX 78735-8598
UUCP:  {ihnp4,seismo,ctvax,gatech}!ut-sally!oakhill!tomc
Phone: 512-440-2953