This error happens installing TinyTERM 3.x to Windows 3.1. It means there is a 32-bit driver loading somewhere in Windows.

To bypass the error, you will need to locate the 32-bit driver causing the problem, then disable it until TinyTERM is installed. Unfortunately, there is no easy way to do this. Check the documentation on other installed software to see which program might be causing this.

This happens on Windows 95 when there is insufficient space on the C: drive. You will need to free up about 20 Mb of space before attempting the install again.NOTE: If you have already started an install, you need to remove any Century folders, Marathon or Marsetup files before trying to install again.

This error comes up when installing TinyTERM 3.2 on Windows 3.1. It’s caused by one of two things:

1. Multiple Winsocks are installed on the PC. Remove them and reinstall only one.
2. No Winsock is installed on the PC. Install one before installing TinyTERM.

If you cannot get the FTP server to work on Windows 98, disable the Internet services. Then locate the file inetd.exe in the Century directory and run it. That will allow you to access and configure the FTP server manually.

Installing TinyTERM 3.3 on Windows 95 may produce an error message that the product is only for DOS. When this happens, copy the contents of the TinyTERM CD to a temporary directory on the hard drive. Reboot the PC in safe mode, then install TinyTERM from the hard drive copy.

Using TinyTERM 3.3, you may get the error, “CTL3D32.DLL is not the correct version.” This most often happens after using TinyTERM successfully for a while.

If you have installed any new software, changed any configurations, or removed software, CTL3D32.DLL may have been replaced with an older version. In that case, do the following:

1. Open Windows Explorer or My Computer.
2. Open the Century folder.
3. Open the TERM Professional folder.
4. Open the wtt folder.
5. Locate the file CTL3D32.XXX in that directory.
6. Copy this file to C:\Windows\System.
7. If there is already a copy of CTL3D32.DLL in the C:\Windows\System folder, rename it as a backup.
8. Rename CTL3D32.XXX to CTL3D32.DLL.

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 TinyTERM version 4.04 on Windows NT 4, it may lock up while working in the emulation. It may also hang if you make changes to Session Properties. To troubleshoot this issue, go to TinyTERM’s Edit menu and select Preferences. Click on the “OLE Settings” tab next. Does this cause TinyTERM to lock up?

If it does lock up, the file comctl32.dll has been replaced with an earlier version. Some software installs automatically replace this DLL, regardless of the currently installed version. Running the updated comctl32.dll from the 401com subdirectory of Tiny Term will fix this problem. This will require system a reboot, so plan accordingly on Windows server.

If looking at the OLE settings does not cause TinyTERM to lock up, you have file corruption instead. Uninstall TinyTERM, then delete the Century directory out of Program files. Reboot the NT system, then reinstall TinyTERM.

After installing third-party software that uses TCP/IP, TinyTERM may fail to connect on Windows 95. This happens when the new software replaces Winsock2 with an older version. This is not an issue on newer versions of Windows.

To fix this, reinstall Winsock2 on Windows 95. You can download the install here.

This error may come up after installing TinyTERM Thin Client Edition 4.02 on Windows NT Server 4.0. To fix it, uninstall TinyTERM. Next, search for the file MFC42.DLL. Rename any copies found as backups. You may have to boot to safe mode to rename MFC42.DLL.

Once you have renamed all copies, install TinyTERM Thin Client Edition again. It will complete normally, and and TinyTERM will start without errors.