If you select a 25-line emulation in TERM, such as SCOANSI or Wyse60-25, but there are not 25 lines available on screen, TERM falls back to VT100 emulation. There’s no warning when this happens. TERM just starts behaving differently than expected.

CR 523

TERM for UNIX/Linux won’t make an rlogin connection unless the user is logged in as root. Any other username returns the following errors:

Attempting connection to rlogin:ip.address (rlogin:ip.address)…
Can’t get reserved socket, must run setuid root
Can’t connect to ip.address
Can’t connect to rlogin:ip.address (rlogin:ip.address)…

CR 519

When running TERM as a background process with the -q command-line option for quiet mode, the Linux log fills with “EOF error on console” messages. This does not happen consistently across releases of TERM or distros of Linux.

CR 498

TERM for UnixWare does not properly enable or disable tty ports on OpenUnix 8. The devices apparently aren’t listed in the /etc/inittab where TERM expects to find them.

CR 495

TERM for Sun Solaris includes two cd commands in the install script, in the middle of the following if statement:

if [ $OSmajor = 5 ]
then
LASTMOD="28 Apr 95"
BIN_FILES="$BRANDIT"
cd Solaris
else
cd SunOS
fi

On the CD distribution of TERM for UNIX, neither “Solaris” nor “SunOS” exists during the install process. This makes the install script fail with the listed error. The workaround is to install TERM manually.

CR 469

Century Software, Inc., has had a request to add IBM3151 terminal emulation to TERM for UNIX/Linux. That has not been done thus far.

CR 358

The TERM for UNIX manual does not describe how to use the TERM CD. It’s also out of date on supported UNIX flavors, and does not mention Linux, or the demo versions available for SCO UNIX and Linux.

The May 2007 release of the TERM for UNIX CD includes a PDF copy of the TERM for UNIX/Linux manual. It also includes a Quick Start Guide, similar to that available for TinyTERM. The hardcopy manual will no longer be available.

CR 333

On SCO UnixWare 7.1, if you enable uucp in the devices file, you can still use TERM. It will dial and connect normally, but the display is scrambled. No more than half a screen comes through visibly. If uucp is disabled, TERM works fine.

CR 291

If you use TERM for SCO UNIX to transfer a file to a directory that does not exist, TERM drops the connection.

CR 280

On a UNIX system, disable getty on a modem port. Then run a TERM script that does an answer wait on the modem. The script should continue to execute when someone dials into that modem.

When you run this script in the background using the ampersand character:

term modemscript.cmd &

the script never answers the modem, even if the script works properly run without the & switch. The TERM process runs, but it does not answer the modem.

CR 224
CR 228, all background scripts fail on Sun