Xref: utzoo comp.os.vms:3801 comp.editors:46
Path: utzoo!mnetor!uunet!husc6!bloom-beacon!gatech!rutgers!iuvax!bsu-cs!cfchiesa
From: cfchiesa@bsu-cs.UUCP (Christopher F. Chiesa)
Newsgroups: comp.os.vms,comp.editors
Subject: Re: VT100 confused by TPU
Message-ID: <1718@bsu-cs.UUCP>
Date: 18 Dec 87 14:52:12 GMT
References: <2080@charon.unm.edu>
Distribution: na
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 26
Keywords: VMS TPU vt100 firmware confusion
Summary: Similar...

In article <2080@charon.unm.edu>, sdowdy@charon.unm.edu (Stephen Dowdy) writes
> If I page up and down
> several times, the vt100 gets extremely confused about what its
> scrolling region is and where to put the next line of text.  This

This sounds somewhat similar to what I experience when using a DEC GIGI
terminal ("so awful they had to name it twice...") in such things as Vax
DEBUG...  {I dial into our Cluster at 1200 baud and DEBUG does indeed "re
draw the screen for single line motions..." - several times for EACH command
executed}  - because the GIGI doesn't HAVE "scrolling regions."  What a pain.

  Well, anyway, my thought is this: write a test program (something to "echo"
each character you type right back to your terminal) to examine your
terminal's response to individual "set scrolling region" and other escape-
sequence commands - it sounds like your terminal's behavior is just plain
"at odds" with what it "should" be.  Does what you describe happen on ALL
"VT100-AA" terminals, or just YOURS?

  I've used this "echo program" idea to "de-mystify" several terminals, and
although it can be slow, it usually does work.  (A general-purpose DEC 'ter-
minal test' program would be nice, something that you run and then compare
your screen output with examples in a manual, saying "if you have THIS dis-
play, your terminal has such-and-such problem", maybe.)  Good luck - I hope
you're able to work it out.

   Chris Chiesa, BSU CS Dept. student