This error may come up installing TERM on AIX. It happens when you install the wrong version. For example, on AIX 5.2 you should installing files from /termunix/i6/4.2, rather than the /termunix/ai files. Also, the serial number to use in that case is the one ending in I6.

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.

When connected to an HP-UX 10.20 host, it may lose data when pasting over 100 lines of information. If this happens, you will need the following patches for HP-UX 10.20:

• PHNE_13413
• PHNE_13414

One patch is for telnet. The other is a kernel patch which requires a system reboot.

Some versions of TERM for UNIX, particularly prior to version 6.2.5b, can only read and write file names up to 14 characters long. This affects scripts, file transfer, log files, etc. The solution is to upgrade your version of TERM.

At this writing, TERM for AIX still exhibits the problem. The most current versions of TERM for all other operating systems do not have this restriction.

CR 70

Both TinyTERM version 4.x and all versions of TERM for UNIX are multithreaded applications. They will take advantage of multiple processors as well.

However, multithreading and multiprocessor support are handled by the operating system. So TinyTERM and TERM for UNIX will only use multithreading and multiple processors if the OS allocates the resources accordingly.

A TCP/IP connection creates a pseudo-tty device (ptty) on the fly at the host system. The numbers assigned to them are not stored, but are lost at disconnect. The specific ptty may change with each connection.

Some configurations may require that users login through specified ptty ports. SCO UNIX has a solution for this in the recon command. Similar commands may exist for other host operating systems, but they are not as well documented.

Sometimes the connection will work and allow the user to login normally. But after login, the keyboard stops responding. And it may not happen to all users.

This is most common with SSH connections, but can happen with any connection type. When this happens, edit the user’s .profile or equivalent on the UNIX or Linux host. Add one line to the end of the file:

stty sane

The next time the user logs in, the connection will work normally.

On operating systems with a root or administrator login, always use that login or one with equivalent rights to install TinyTERM or TERM. When the install requires a reboot, login as an administrator when the reboot is complete, also.

Otherwise, TinyTERM’s and TERM’s installs can’t access the files and registry settings they need. Errors during install or when running the emulator will happen if this isn’t done.