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.

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.

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.

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.

When installing TERM for UNIX, you may see the error “Term.exe not found.” This error always happens when you have uncompressed the wrong version of TERM; for example, using the termi6.tar file on SCO UNIX, which should use termu3.tar instead. Check the readme file on the TERM CD for a list of operating systems and appropriate versions.

Using TERM on AIX 3.2.5, you may have problems using modems. In particular, you may need to power the modem off and on after starting TERM for it to connect.  Setup strings are the same (ATZ\r) for all three Motorola modems. To resolve this, apply the most recent AIX 3.2.5.5 service pack.

When TERM for UNIX returns a “device busy” error, but there are no lockfiles, there is a permission problem.  Verify the following:

• Permissions on /usr/bin/callin and /usr/bin/callout must be 4755 (-rwsr-xr-x).
• Permissions on the full structure of /usr/spool/uucp or /var/spool/uucp (Linux) must be at least 666 (-rw-rw-rw-). The directory itself, plus every directory and file within it, must have those permissions or higher. Lockfiles are placed in this directory.
• Permissions on the tty port itself must be at least 666 (-rw-rw-rw-).

When TERM for UNIX gives the error, “Non-expired lockfile lck..inittab,” make sure the permissions on the whole structure of /usr/spool/uucp are at least 666 (-rw-rw-rw-).

For TERM for Linux, the directory path is normally /var/spool/uucp. If TERM for Linux is configured for /usr/spool/uucp instead, this error will result even if permissions are correct on /var/spool/uucp.

CR 277
CR 573, Linux spool directory fixed in TERM 6.28

To install TERM for UNIX manually, login as root or a user with equivalent permissions. Then do the following:

1. Create the directory where TERM will reside:
   

   md /usr/term

2. Copy the install files into this directory.
3. Extract (untar) the files. For example:
   

   tar xvf cmdfile1.tar
tar xvf cmdfile2.tar
tar xvf cmdfile3.tar
tar xvf termi6.tar

   Replace termi6.tar with the correct install file. You may not have the separate cmdfile#.tar files either, depending on your flavor of UNIX.

4. Move the term, callin and callout files to /usr/bin:
   

   mv term callin callout /usr/bin

5. Change permissions on the moved files:
   

   chmod 555 /usr/bin/term
chmod 4755 /usr/bin/callin /usr/bin/callout

6. Brand the TERM executable with the command:
   

   ./brand /usr/bin/term

   Enter your serial number and activation key when prompted to do so. Please remember that both are case-sensitive.

The install will be complete at this point.

Multiple file transfers in a TERM for UNIX script can cause error 1204. It usually happens after using the OK button to acknowledge that a file has been sent. The OK button sends a ^C, causing a script abort.

The workaround is to turn off the transfer status window before the transfer. The command to do that is:

set xferstat off

It can be put in the script anywhere, as long as it executes before any file transfers.