When connecting from one system to another, if you run TERM on both you may receive an error about duplicate copies of TERM. This is caused BY installing the same TERM license on both systems. You must have a different license for each system. You cannot use the same serial number and activation key on two systems.

When you move to a new UNIX server, you must install TERM on the new server. If you copy the files over from an older system, you will get errors running TERM instead.

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.

To uninstall TERM for UNIX, you need to remove three files and one directory:

• /usr/term (the only directory)
• /usr/bin/term
• /usr/bin/callin
• /usr/bin/callout

Each user may also have a .termsys file in his home directory. Delete those as well.

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.

When you see this message in TERM for UNIX, it means there’s a problem in the .termsys file. Edit the file and look for the line that starts:

setv _turnchar

It will have extraneous information after that. Change the line to read:

setv _turnchar “\r”

Save the file. That will get rid of the error.

Using TERM Professional 3.3 on Windows NT, after installing NFS you can’t shut down Windows. Instead, you get a Dr. Watson error, followed by a blue screen.

To correct this error, you will need to download this patch. To use it, search the C: drive for the file mar_nfs.386. Rename any copy you find as a backup. Then copy the patch file into the same directory. The next time you start Windows NT, the patch will be in effect.

Using TERM for UNIX on HP-UX, XMODEM receives files from an EDI mailbox without a problem. However, sending files fails after a few packets with a CRC error. There are two possible issues in this case:

1. TERM maybe sending data, but not receiving acknowledgements. If you abort the TERM script and immediately connect to the UNIX device file using the Unix command “cu-l /dev/cul0p7 -m dir”, you may find that the telephone connection is still open. In this case, you may be able to continue the session manually.To resolve this, disable local flow control on the modem. The Hayes command for that is AT&K0. Please be aware each modem may have different local flow control commands. Check the documentation for specifics.
2. If you are connecting to a GEIS network, you will need to convert the UNIX-formatted file to DOS format before sending it. The GEIS network expects DOS-formatted files. You can use the HP-UX utility dos2ux to convert the file.