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.

Some TinyTERM 3.3 and 4.0 installs had the potential to delete all printers installed in Windows NT. To restore printing functionality in this case, uninstall TinyTERM. Then apply this patch. The patch documentation can be downloaded from this link.

Once the patch is installed, you can reinstall TinyTERM. Do not install the NFS component, as that’s what causes the problem.

You may see this error running TinyTERM 3.3 on Windows NT. If you search your C: drive, you should find the file CTL3DXX.DLL. Rename that file to CTL3D32.DLL.

If you do not have that file, you can also download it from this link. In either case, the file should be in the C:\Winnt\System32 folder.

On Windows 95 and 98 systems with a dial-up ISP, starting a telnet application such as TinyTERM can cause Windows Dial-Up Networking to launch, even if TinyTERM should connect over a LAN.

To stop this from happening, create a hosts file on the PC or edit the existing one (instructions). Add the IP address and hostname of the system you are connecting to.

If this procedure does not work, locate your dial-up networking connection file and rename it. Then start TinyTERM. You’ll get a message that the connection file can’t be found. In that message window will be an option not to connect to the Internet automatically. Check that box, then change the name of your dial-up connection back to the original name. The next time you start TinyTERM, the dialer won’t automatically open.

This error happens when using the Century FTP Client that came with TinyTERM Plus versions 4.11 and earlier over a VPN. It’s fixed with the patch available here.

To use the patch, locate the existing ftpslave.exe file on your PC. Rename it as a backup, then copy this file into the same directory. The next time you start the Century FTP Client, the patch will be in effect.

This patch does not work with SecureFT.

CR 100, fixed in TinyTERM Plus 4.12 .

Support for TinyTERM versions prior to 4.0 (October 1998 release) ended in July 1999. This includes all versions of TERM For Windows. Support for TinyTERM versions prior to 4.30 ended in March 2007. The only support remaining for those products is here on our website So if you have questions about our older versions, watch this forum for answers.

This also effectively means the end of support for Windows 95 as a platform for TinyTERM. Version 4.30 requires Windows 98 or higher, and versions from 4.40 on require at least Windows 98se.

TERM for DOS and TERM for UNIX/Linux are not affected by this. We will continue to support those products in the appropriate environments.

If TinyTERM doesn’t open when you try to start it, but just puts a button on the Windows taskbar, it means the window position information has gotten corrupted. To fix that, right-click the button and select Maximize from the pop-up menu. TinyTERM will open full screen. From the File menu, select Save Session. This will usually fix the problem.

If it does not, you’ll need to edit the configuration file you’re using. Close TinyTERM and edit the .tpx file being used in Notepad. Search for the following two lines, which will be one right after the other:

xwindow=
ywindow=

They’ll both be set to very high numbers, or they’ll be negative numbers. Change each to 100:

xwindow=100
ywindow=100

Save the changes and close Notepad. The next time you start TinyTERM, it will open in a normal window. It may be too small, so resize it if you need to. Then save the session to make the changes permanent.

If your version of TinyTERM is old enough to use a configuration file with the .tap extension, the correct line to adjust in that file is:

window=

Change the first four numbers in that line     they’re separated by commas     to 100. The next time you start TinyTERM, resize the window to your needs.

Watch a screencast demonstrating this process.