SCO Unix, Xenix and ODT General FAQ
This article is from a FAQ concerning SCO operating systems. While some of the information may be applicable to any OS, or any Unix or Linux OS, it may be specific to SCO Xenix, Open This is an old article about SCO Unix and is only left here for historical purposes. There is lots of Linux, Mac OS X and general Unix info elsewhere on this site: Search this site is the best way to find anything.
Unfortunately, everyone has a different definition of the behaviour of an ANSI terminal. The exact definition may also vary between versions of products (SCO has had more than one version of SCO ANSI, and even the rudimentary ANSI support in the ANSI.SYS driver in DOS varies between versions).
If your terminal emulation program doesn't specifically mention that it emulates a SCO ANSI terminal, chances are that it's designed to work like ANSI.SYS, and that's not sufficient for SCO ANSI. Many terminal emulation programs have a specific SCO ANSI setting; check with your documentation or contact the vendor.
In some cases (particularly via telnet or rlogin), the terminal type you're using is transmitted as part of the connection sequence. Make sure that the terminal type your communications software is reporting is the same as what SCO expects. For example, many programs call their SCO ANSI emulation "SCOANSI", but SCO calls it "ansi", and if your software sends "SCOANSI" as its terminal type, your SCO system will not understand. Many terminal emulation packages allow you to define what terminal type it will say it's using; set this to "ansi".
Got something to add? Send me email.
(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version
Increase ad revenue 50-250% with Ezoic