880139h@aucs.AcadiaU.ca (Rob Hutten) (05/30/91)
Hi. I'm running SCO UNIX SysV/386 v2.0 release 3.2 and I'm having terminal emulation problems on the console. The problem only arises when I telnet to other machines- setting term=vt100 *almost* works properly, but I encounter some problems when using a full-screen editor- it seems to have trouble keeping up with the scrolling and I'm forced to use ^L fairly often to refresh the screen. We have another machine here using an old version of Open Desktop and we encounter the same problem there. Has anyone else encountered the same problem? I can't find anything about terminal emulation for the console in TFM, but I've been thinking that maybe it isn't an emulation problem seeing as how the problem only occurs while telneting to another machine. Sorry if this is a frequently asked or otherwise stupid question, but I've run out of ideas. Please respond via email- if there is suitable response I will post a summary. Thanks. -- \-----------------------------------------------------------------------------/ | Rob Hutten 880139h@acadiau.ca 880139h@ace.acadiau.ca hutten@agcrr.bio.ns.ca | | CS student, geek, and g'dar player for MC FTP and the Zydeco Funkmasters. | /-----------------------------------------------------------------------------\
sef@kithrup.COM (Sean Eric Fagan) (05/31/91)
In article <1991May30.114452.13328@aucs.AcadiaU.ca> 880139h@aucs.acadiau.ca (Rob Hutten) writes: >The problem >only arises when I telnet to other machines- setting term=vt100 >*almost* works properly, but I encounter some problems when using >a full-screen editor- it seems to have trouble keeping up with >the scrolling and I'm forced to use ^L fairly often to >refresh the screen. The console is not a VT100; it's an (almost) ANSI. Actually, as far as I know, it's a superset of an ANSI terminal, including 25 lines (instead of 24), color, and a few other things. I would suggest you snag the termcap and terminfo (if appropriate) entries from the SCO system, and install them on the target system (possibly as 'scoansi' instead of ansi). -- Sean Eric Fagan | "I made the universe, but please don't blame me for it; sef@kithrup.COM | I had a bellyache at the time." -----------------+ -- The Turtle (Stephen King, _It_) Any opinions expressed are my own, and generally unpopular with others.
rbraun@spdcc.COM (Rich Braun) (05/31/91)
880139h@aucs.acadiau.ca (Rob Hutten) writes: >Hi. I'm running SCO UNIX SysV/386 v2.0 release 3.2 and I'm >having terminal emulation problems on the console. The problem >only arises when I telnet to other machines- setting term=vt100 >*almost* works properly... I have this same problem: if I 'cu' to a remote system and tell it my terminal type is vt100, the ANSI interpreter under SCO 3.2.2 really messes a lot of escape sequences up (especially those having to do with insert/delete line--try hitting ^O in Emacs). Do I need to ship my terminfo description over to all potential remote systems, or is there some terminal type which I can use? Since I suspect a number of people have run into this problem, please post the solution if you have one. -rich