In this situation, TinyTERM connects to a host via serial cable successfully. Another application on the PC then makes a modem connection. This causes the system to lock up completely.

Check the IRQs used by the serial port and modem. If both are trying to use one IRQ — or worse, one COM port — that will cause the lockup. Assign the modem its own IRQ.

TinyTERM and TERM for DOS can both connect via IPX/SPX. They do not require TCP/IP as TinyTERM and TERM for Windows do.

You cannot copy the TinyTERM install directory to a new PC. You’ll get license errors if you do. You must install TinyTERM on the new PC from CD or download. Delete the files you copied over before running the install.

While trying to manually uninstall TinyTERM, you may find there are some files you cannot delete, such as CenLic32.dll. It’s caused when the file is in use by Windows.

When this happens, finish as much of the uninstall process as possible, then reboot the PC in safe mode. You will be able to delete the files then. Reboot again after deleting the files to return to normal mode.

This error does not come from TERM or TinyTERM. It’s a host error, indicating that all available user licenses have been taken. The only solution is to purchase more licenses for the server, not TinyTERM.

In TinyTERM 4.00-4.13, there is no flow control setting in the user interface. To set flow control for those versions, go through Windows Device Manager and set it directly on the serial port.

A user interface for this was added in TinyTERM 4.20.

CR 25

When you start TinyTERM in a browser, you may want to hide the Ribbon Bar to increase the available screen space. To prevent the Ribbon Bar from displaying, do the following:

1. Open TinyTERM outside the browser.
2. From the Edit menu, select Preferences.
3. Go to the OLE Settings tab.
4. Remove the check from Display ribbon bar.

If you want even more available screen space, you can also disable the Session Bar in the same dialog.

Closing TinyTERM version 4.x, if you get “An error occurred in CenTE.ocx” when the last connection closes, it indicates a corrupt file. To fix the problem, uninstall TinyTERM. When that completes, reboot the PC and reinstall TinyTERM.

The SNA protocol is a native IBM network protocol. TinyTERM does not support it for TN3270 or TN5250 emulations. Only TCP/IP connections are supported.

With TinyTERM Plus Edition 4.05 installed, you can’t capture a network printer to LPT1:. The problem goes away when TinyTERM is uninstalled. To fix the problem, reinstall TinyTERM Plus Edition without the NFS component.