tomc@oakhill.UUCP (02/24/87)
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-2953ell@linus.UUCP (Edward L. Lafferty) (03/08/87)
The vt100tool distributed via mod.sources was for the sun-2 and will not compile on a sun3. However as I have posted earlier, it is available via anonymous ftp in binary form from mitre-b-ed for a sun-3. I will repeat the instructions here: get the following files from the directory pub: vt100tool.Z vttest.c <if you do not already have them from the earlier posting get the following:> fonts/* README v100tool.c <for info only -- will not compile in your environment> NOTE: if you don't have decompress there is an uncompressed version in the directory but it will take a long time to transfer. I will try to get a source port sometime soon. as to the problems posted in the article using vtem, I have not used the emulator from SMI but there is a certain amount of maturity that the one I built has that the SMI version may not have yet. The vt100 does not work exactly the way it says in the manual and there are programmers who use undefined features(?) which can screw up unwary emulators. Most DEC built VMS applications are very tricky in their use of this terminal, in particular the EDT editor family.