In the Century FTP Client, if the Set_FACL command has been used to restrict access to files via a File Access Control List, the FTP Client cannot see these files on the server. To resolve this problem you will need to replace the ftp32.exe file. You can download a patch for this here.

To use the patch, locate the existing ftp32.exe file in C:\Program Files\Century\TinyTERM\NetUtils. Rename it as a backup. Copy the patch file Ftp32_FACL.exe into that same directory. Then rename the patch as ftp32.exe. The next time you start the Century FTP Client, the patch will be in effect.

This patch applies to TinyTERM Plus versions 4.10 and earlier. Later versions of TinyTERM Plus incorporate the patch.

Turning on data capture in TinyTERM 4.04 will cause it to crash and close, unless the Status Bar is turned off. To do that, go to the View menu and uncheck the “Status Bar” option.

The crash is caused by a bug in the butterfly net graphic that normally displays in the status bar. Other versions of TinyTERM do not have this problem. There is no patch available.

If you have multiple sessions open in a single TinyTERM window, you may see information from a hidden session “bleed” into the active session. There are two causes for this.

1. Your Windows video driver needs to be updated. Contact the video card or PC manufacturer for an updated video driver.
2. One of the background sessions updates the screen regularly. When this happens you can see the updates in any active session, not just the correct one. This was corrected in TinyTERM 4.10.

CR 71

When you start TinyTERM right after install, the screen can be completely blank. This most often happens when an earlier version of TinyTERM was installed on the PC, but not completely uninstalled. The existing fonts interfere with the install of the new fonts, causing the display problem. Restarting the PC will fix it.

CR 312

This error happens when running TinyTERM 4.10 on Windows NT 4.0 or 2000. It’s not actually trying to update the registry, but it does check to see if it can.

You can resolve the error by downloading and applying this patch. It is a replacement for the existing tt.exe program.

To use the patch, save it into the C:\Program Files\Century\TinyTERM directory. In that same directory, locate the file tt.exe and rename it as a backup. Then rename this patch as “tt.exe”. The next time you start TinyTERM, it will be in effect.

WARNING: This patch only applies to TinyTERM version 4.10. If used with earlier versions of TinyTERM, or on operating systems newer than Windows NT 4.0 or 2000, TinyTERM licensing problems and system instability could result.

The patch is not needed for Windows 95, 98 or Me. The patch is incorporated into later versions of TinyTERM already.

TinyTERM 3.2 and older versions have a “network install” option, which allows a set number of concurrent users to run it at the same time. If it’s not allowing the correct number of users, the license control file may be corrupt.

Search the TinyTERM install directory for the file tt.ser or term.ser. Rename that file as a backup, then replace it with the blank file you can download here. Rename the file to term.ser if needed.

This error comes from using an older version of TinyTERM on Windows Me, 2000, XP or Vista. Windows TAPI changed considerably in those operating systems, so older versions of TinyTERM won’t understand it. The best solution is to upgrade. Or you can dial the modem manually.

You can configure TinyTERM Application Developer 3.3 to dial the modem. To do that, locate the file wtermus.cmd and open it in a text editor such as WordPad. Search it for the line:

setvar t_tapi true

For every instance of that line, change “true” to “false”. Save the changes, and TinyTERM will use its internal dialer instead of TAPI. This workaround is only available on TinyTERM Application Developer 3.3.

Windows 95 introduced TAPI for modem handling. TERM for Windows 7.2 and TinyTERM 3.3 can use TAPI, but will sometimes give errors instead of connecting normally. In those cases, it’s possible to turn off TAPI handling, allowing TinyTERM to use the modem as though it were on Windows 3.1 instead.

Locate the file WTERMUS.CMD in the TinyTERM directory. Open it in Notepad or another text editor. Search it for every instance of the line:

setvar t_tapi true

Change “true” to “false” for every instance. TinyTERM will no longer recognize TAPI, which will allow it to handle the modem directly instead.

When TinyTERM is configured to print to DEVICE or “Direct to device,” it can lock the printer port so that other Windows applications can’t use the printer. That’s because TinyTERM directly accesses the printer port in this configuration.

To bypass this, configure TinyTERM to print to PRINTMNGR or “To Windows printer.” This allows Windows to manage the print job and the printer port. Other applications will then be able to print without problem.

This is a license error that prevents TinyTERM from opening. Check your system date when this happens. It’s usually off by several years.

If the system date is correct, you will need to uninstall TinyTERM, then reboot and reinstall.