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.

Before installing TinyTERM Plus Edition 4.04.0553 (released July 1999) onto Windows 95, Windows 98, or NT 4.0, you must uninstall any previous version of TinyTERM. Use Control Panel’s Add/Remove Program utility to do this. After uninstalling, you must reboot the PC before installing version 4.04.0553.

If you do not reboot after the uninstall, or if you do not remove previous versions, you may see “unknown hardware” errors when you reboot the PC. It will then try to add this unknown hardware to your system. When this happens, do the following:

1. Close all application.
2. Go to Control Panel and run Add/Remove Programs
3. Uninstall all TinyTERM and NetUtils items.
4. Reboot the PC.
5. Reinstall TinyTERM 4.04.0553.
6. Reboot the PC when the install completes.

Using TinyTERM Plus Edition 4.04, how do you connect through a telnet firewall to an IBM host with TN5250 or TN3270 terminal emulation?

Configure a sessions using the TTY terminal type and a telnet connection to connect to the firewall as follows:

• Connection host: firewall name or IP address
• Connection Type: telnet
• Terminal Emulation: TTY
• Telnet Terminal Type: (depends on IBM emulation required)
  • 3270
    • IBM-3278-2
    • IBM-3278-3
    • IBM-3278-4
    • IBM-3278-5
  • 5250
    • IBM-3179-2
    • IBM3477-FC
• Save the session.
• Telnet to the firewall using this configuration. When the firewall prompts for the host, enter the hostname or IP address of the destination host.
• Depending on your firewall, you may have to hit the Enter key once to display the initial host screen.

NOTE 1: TinyTERM senses telnet binary mode to know when to switch emulations from TTY to one of the IBM emulations. The IBM terminal emulation desired is specified by the Telnet Terminal Type configuration.

NOTE 2: To preserve the initial firewall connection configuration do not save the session after the IBM host connection is made. TinyTERM changes your session properties when the IBM connection is made.

Using TinyTERM on Windows 98 with Internet Explorer version 4, and a TinyTERM session as the home page, starting IE causes numerous errors and eventually locks up the PC. To get rid of these errors, do the following:

1. Open Control Panel.
2. Double-click the Internet icon.
3. Reset the start or home page to default, or specify a URL.

You will now be able to launch Internet Explorer normally. You will have to launch TinyTERM separately after opening the browser.

If you have applied the printing patch to TinyTERM 4.03 and now get a “TinyTERM mismatch” error, you probably have older versions of Tiny Term installed on the PC. To get rid of the error, do the following:

1. Manually uninstall TinyTERM.
2. Reboot your PC.
3. Reinstall TinyTERM 4.03.
4. Apply the printing patch again.

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.

After entering the serial number and activation key, the TinyTERM 4.03 install sometimes disappears. When this happens, make sure there are no other versions of TinyTERM on the PC. If there is an older version installed, use Add/Remove Programs from Control Panel to remove it.

Before attempting to install TinyTERM 4.03 again, press Ctrl-Alt-Delete and end every task except Systra and Explorer. Once that’s done, run the install again. It should complete without a problem.

Starting TinyTERM Plus Edition 4.03 on Windows 98 or NT , you may receive the error “Get Capture Failed,” followed by DLL errors. This usually indicates you do not have TCP/IP installed. To correct the problem, you will need to do the following:

1. Add TCP/IP to Windows.
2. Reboot your PC.
3. Uninstall TinyTERM, then reboot.
4. Reinstall TinyTERM. When the install completes, reboot your PC, whether or not you are prompted to do so.

Using TinyTERM Plus Edition 4.03, if you have multiple sessions open and close the second or third, you may get this error. There is no patch. The only solution is to use a different version of TinyTERM.

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.