This error comes up when there’s something wrong with the terminal emulation type. There are two places to check:

1. The “Telnet terminal type” or “netterm” setting in TERM or TinyTERM. (This only needs to be checked on network connections.) If it’s not set to a valid terminal type for the host system, it needs to be changed. If it’s blank, you may need to enter something, such as “vt220” when you’re using VT220-7 emulation.
2. The TERM environment variable on the host system. This will usually be stored in your .profile or equivalent. Like the telnet terminal type, this must be set to a valid emulation for the host system.

Some systems will request a terminal type when you login. You can usually hit Enter to accept the default; however, if it’s incorrect or listed as unknown, you will need to type an appropriate value.

You may see this error installing TERM on SCO UNIX. It means there’s a SCO file missing. You can download the missing file from SCO.

Select “Sco OpenServer” as your operating system and “OpenServer” as your family, then select “Binary Compatibility Module 7.1.1 for Sco OpenServer(for UDK compatibility)” as the download. You’ll have to go through a couple more pages before you can download the module. Then install it using the instructions provided.

In some cases, you may be unable to see certain fields in the emulation window. You know the fields are there, but the display of them is wrong or missing.

When this happens, verify that you are using the correct terminal emulation. Some emulations share display codes, but are not 100% compatible. Missing or otherwise scrambled display is normal in this case if the wrong emulation is chosen.

Using TERM for UNIX on a tty port, it may fail even though cu can see the port. When this happens, first verify the port permissions are 666 (-rw-rw-rw-). If that’s correct, launch TERM with the -i parameter:

term -i -l/dev/tty04

This will ignore any lockfiles on the tty port. Please be aware that if another application is using the port, it will be interrupted when you do this.

This error comes up when using TinyTERM or TERM for DOS on a PC with no networking installed. You will need to configure the connection again, as it’s been changed to try to use a network.

You may run into a situation where transparent printing works for a few pages of text, then gives a print error. After that the job may fail, or it may print one line per page.This is a flow control issue. Disable flow control on both the PC and the server port. Printing should work properly after that.

Starting TinyTERM 3.3 on Windows 95 may give the error, “CTL3D32.DLL error.” Replacing the file does not fix the issue.

This happens when there are too many ctl3d32.xxx and ctl3d32.dll files on the PC. Remove all copies of both files, except the one in C:\Windows\System. Then reboot the PC.

Old versions of TinyTERM will sometimes scroll the screen up one line when you switch between two or more sessions. This is a known issue. It was fixed in TinyTERM version 4.00. No patch exists for earlier versions.

TERM version 6.2.5 for AIX has a problem with the install script. The script has extraneous ^M characters that throw it off. To bypass the error, follow the manual install instructions.

TERM has several of the function keys preset for certain actions, such as opening the menu or help. You can reset those by editing the .termsys file in UNIX, or the term.sys file in DOS. Search the file for lines that start with the word setkey; for example:

setkey f1 menu

Change the word after the function key name (in this example, menu) to reset:

setkey f1 reset

This will reset the keys to their default values the next time you start TERM.