TERM for Linux 6.27 and later versions include an RPM install file. TERM 6.2.5b for Linux did not.

The RPM install does not work on every version of Linux. For those that don’t accept such files, Century Software, Inc., has created kernel-specific installs.

CR 470, RPM
CR 706, non-RPM

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

Generate a disk image with Symantec Ghost. TinyTERM always gives an “invalid license” error when recreated from the images, but never on the first run. It generally fails the second or third time it’s run on an imaged PC.

The cause has not yet been determined. The workaround is to edit the registry to remove the existing licenses, then use License Manager to add them back in.

CR 367

The TERM for UnixWare install fails with a segmentation fault on UnixWare 7.1.1. This is caused by the brand program that licenses TERM. The fault prevents /usr/bin/term from being serialized, making it unusable.

CR 300

When you use the file tttc.exe from the zipse directory on the TinyTERM 4.20 CD, it does start to run. Shortly after that you get the message, “Setup has detected some old dll files on your system. You must restart to continue installation.” After rebooting you get a “missing shortcut” error. The install never starts back up. If you manually restart the install, it does the same thing.

CR 197, fixed in TinyTERM Thin Client 4.21

TinyTERM Thin Client and TinyTERM Plus (thin client install, version 4.40 or higher) are licensed for install on a single terminal server. They are not licensed to be installed on multiple nodes in a load-balancing environment.

If you have terminal servers set up in such an environment, each server must have its own TinyTERM license. To balance the load, you’ll need to purchase a fraction of the licenses you need for each. For example, if you need 30 users spread over three servers, you must have three ten-user TinyTERM Thin Client or TinyTERM Plus licenses. One is then installed on each server.

CR 161

This problem was first noticed on SCO OpenServer 5.0.6 with dual Pentium III processors. When installing TERM through an xterm window, an error message came up: “Memory fault – core dumped.” The workaround is to install TERM at the console instead of through an xterm.

CR 136

Installing from the TinyTERM 4.50 MSI package on some Windows systems gives the following message:

Error 1722.
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.

On uninstall, a different error comes up:

Error 1721
There is a problem with this Windows Installer package. A program run as part of the setup did not finish as expected. Contact your support personnel or package vendor.

Both problems are fixed in TinyTERM 4.53.

CR 785, error 1722
CR 801, error 1721

TinyTERM 4.50 allows you to connect to a server multiple times, while only showing as a single server user. The server must be configured to allow this behavior, and each TinyTERM connection from a single PC must use the same host username and password.

CR 582

Installing TinyTERM 4.30 on Windows 95 or 98 may produce this error. There is no workaround.

CR 512, fixed in TinyTERM 4.31