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.

Using TinyTERM on an IBM Warp OS/2 2.21 running in Windows 3.11 enhanced mode, TinyTERM crashes. It’s not supported in that environment, but you may be able to get it to run. For this situation, install TinyTERM to a standard 16-bit FAT file system, instead of HPFS.

Using TERM for UNIX to communicate from the SCO console to another SCO system, neither ANSI or SCOANSI emulations reproduce the remote host colors. In this case, use the TTY emulation for console-to-console communications. This is strictly a pass-through emulation and will reproduce the colors properly.

Using TinyTERM for Windows, the session tab at the bottom of the screen is normally labeled, “default.” It reflects the name of the .tap or .tpx configuration file.

To change the name, save the session or ICONect with a different name. When you open that file again, the tab will display the file name you entered.

After installing TinyTERM Plus Edition version 4.02 or 4.03, you may find there are no network utilities installed. You may also have noticed a CenLic32.dll error during install.

This is generally caused by installing TinyTERM Plus Edition over an older version of TinyTERM. To resolve this, do the following:

1. Uninstall all versions of TinyTERM.
2. Reboot the PC.
3. Search drive C:\ for CenLic32.dll. Delete any copies you find.
4. Install TinyTERM Plus Edition.

If you experience any other install issues after this, run one of the following install patches, whichever is appropriate to your version:

TinyTERM Plus Edition 4.02
TinyTERM Plus Edition 4.03

We also suggest you install Winsock2 on Windows 95 machine. You can download that here.

After upgrading from TERM for DOS 7.0 to version 7.2, trying to transfer a file using ZMODEM will give the error, “Can’t find FTZMOD.DLL.” You will need to go to the Century directory and rename the file FTZMODEM.DLL to FTZMOD.DLL.

Using TinyTERM on Windows 95 on a Packard Bell PC, it won’t disconnect or let go of the phone line. Instead it gives an error that fmedia and faxworks are active.When this happens, edit the file win.ini. Locate the run= line and delete everything after the equals sign. Reboot the PC to finish the fix.

If you have a multi-user license of TinyTERM version 3.x, and an additional multi-user license of TinyTERM version 4.x, all users should be able to connect to the host, provided the host itself is licensed to accept them all. If you get a message that all licenses are in use, and the host can still accept logins, this may be a TinyTERM version issue.

If TinyTERM version 3 was installed using the isetup option, this could be causing your problem. The isetup routine tracks the number of TinyTERM licenses being used. TinyTERM version 4 does not use isetup, so its license is not recognized. To resolve the problem, you will need to do the following:

1. Check the network for isetup or TinyTERM. Remove any that you find.
2. Uninstall TinyTERM version 3 from the PCs that have it installed.
3. Re-install TinyTERM version 3 directly to the same PCs.

You should now be able to use all your TinyTERM licenses.

When you try to install NFS on Windows 98, you may get an error message stating that on the specific location there is no data about the hardware. To fix this, when the install asks if you want to restart your computer, click No. Next, type Alt-Tab until you get to a registry question. Click OK to add to the registry. You should now be able to set up the NFS Client.

If Term is installed to a directory other than the default /usr/term, you may get this error. In that case, set the TERMDIR environment variable to point to the TERM install directory. For example, if TERM is installed to /var/term, add the following two lines to your .profile:

TERMDIR=/var/term
export TERMDIR