Connecting via modem, when TERM tries to XMIT a string the connection dies. This was tracked to the parity not being sent. There was no option to set parity in the modem initialization string.

The workaround was to use the TERM Script Language command SET MASKPAR ON. This masks the parity being sent.

CR 176

When running TERM as a background process with term &, you will get the error:

selrdr: eof error on console

repeated multiple times. To fix it, add -q to the TERM command line:

 term -q &

This puts TERM into quiet mode, so it does not try to display messages to the console.

This error means a serial number and activation key have already been applied to TERM. If it will not start, uninstall TERM, then reinstall it.

If that does not get rid of the error, you probably have the wrong serial number for your version of TERM. Contact Technical Support to verify your license information.

Using TERM on a DEC ALPHA system, the arrow key definitions changed. The TERM the emulation was set to TTY because the connection was UNIX to UNIX, no conversion at all.

After some digging, the end user discovered that the cursor keys were switching to application mode. Closing TERM resets the keys to normal cursor mode. The solution was:

1. Copy /etc/termcap to /usr/term/termcap.mod.
2. Change the following in /usr/term/termcap.mod for the console emulation type:
   

   ks=\E=ke=\E>ku=\E[Akl=\E[Dkr=\E[Ckd=\E[B3

3. Set the TERMCAP environment variable to /usr/term/termcap.mod and export it:
   

   TERMCAP=/usr/term/termcap.mod;export TERMCAP

On starting TERM the keypad is turned on, but the arrow keys stay unaltered. TERM is looking at the keypad arrow keys, which now reflect the standard arrow keys.

Using Term for UNIX , one customer had everything running through a Visual Basic application. When the information from TERM started displaying to the screen, it forced the Visual Basic application to shut down. To bypass the problem, the TERM command line was changed to term -q. This put TERM into a quiet mode, preventing screen display.

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.

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.

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.

This was seen using TERM 6.2.5 on an AIX 4.2 system, which had been upgraded from AIX 3. TERM randomly locked three different ports, requiring a system shutdown to clear them.

It turned out that TERM 6.2.4 was still on the system when TERM 6.2.5 was installed. Removing all versions of TERM and reinstalling only version 6.2.5 fixed the problem.