TinyTERM won’t start. Instead, it gives the error, “Could not run CSL entry point: main.”

“CSL entry point: main” is another name for the TinyTERM program tt.exe. So the error only means TinyTERM can’t start. There are three probable causes for this:

1. The first is a corrupt .tpx file. Rename the .tpx file you’re using, then start TinyTERM. If you get a “file not found” error, click Yes and configure your connection again. The old file was corrupt.
2. Another program may have replaced DLL files TinyTERM uses. If the problem started right after installing other software, try uninstalling that software. If you have a “rollback” utility that can restore Windows to a previous configuration, that’s even better. Test TinyTERM to see if it works again after the uninstall or rollback.
3. If you still get the “CSL entry point” error after renaming the .tpx file, and no new software was installed, one of TinyTERM’s main files is corrupt. The only way to fix that is to uninstall TinyTERM. Delete the Century folder from Program Files after uninstalling, then reboot and reinstall.

CR 140, DLLs replaced

You may see this error when installing TinyTERM on Windows 2000 or XP. It will reference the file AUTOEXEC.NT or CONFIG.NT.

It usually happens when the specified file is missing. You can find a replacement in either C:\Windows\Repair or C:\Windows\i386. Copy the file into C:\Windows\System32, then start the install again.

If AUTOEXEC.NT already exists in C:\Windows\System32, the error means that file has a setting that’s interfering with TinyTERM’s install. To fix the error, back up AUTOEXEC.NT by copying it to another location, then edit it to have the following three lines only:

lh %SystemRoot%\system32\mscdexnt.exe
lh %SystemRoot%\system32\redir
lh %SystemRoot%\system32\dosx

You won’t need to reboot. TinyTERM will install after those changes are made.

CR 730, fixed in TinyTERM 4.50

TinyTERM version 4.x requires Winsock2 to connect via TCP/IP. This is standard in Windows 98 or higher.

Windows 95 does have the ability to use Winsock1 only. You must update to Winsock2 to use TinyTERM version 4. In fact, TinyTERM 4.0x won’t install unless Winsock2 is included, even if you plan to use a serial or modem connection.

Older versions of TinyTERM or TERM for Windows can use Winsock1 or Winsock2 interchangeably.

CR 55, Winsock2 requirement removed for non-TCP/IP connections

Any version of TinyTERM or TERM for Windows can use a Windows-only printer, provided the driver is installed. As with USB printers, the specifics depend on which version of TinyTERM you have.

TinyTERM 3.x and earlier, also
Any version of TERM for Windows
The specified printer must be the Windows default printer. Set TinyTERM to use PRINTMNGR as its printing device. TinyTERM will then send all printer output to that printer.

TinyTERM 4.00 – 4.12
Select the “To Windows Printer” option in TinyTERM’s Printer Setup dialog. Then click the Setup button to choose the Windows printer.

TinyTERM 4.13 and newer
Select the “To Windows Printer” option in TinyTERM’s Printer Setup dialog. Use the drop-down list to select the desired printer. Do not set the “Use printer fonts” or “Bypass printer driver” option.

Unlike USB printers, there may be a hardware port such as LPT1: associated with a Windows-only printer. However, Windows-only printers require a Windows printer driver to function at all. Bypassing the printer driver will usually cause all print jobs to be lost.

Using TinyTERM 3.3 on Windows 95, you may see fuzzy, unreadable fonts which also affects other applications, such as Microsoft Word. There are several possible fixes for this problem:

1. TinyTERM Graphics Settings
   1. In TinyTERM, go to the Configure menu and select Emulation.
   2. Click the Advanced button.
   3. Check the Ignore graphics/parity bit option.
   4. OK and save the changes.
2. Duplicate Term Fonts
   This is generally caused by having several installs on one PC. To get rid of the duplicates:
   1. Open the Windows Control Panel.
   2. Double-click Fonts.
   3. Scroll down to the fonts named Term*.
   4. Delete any with duplicate names
3. Video Driver
   1. Open the Windows Control Panel.
   2. Double-click Display
   3. Change the display resolution.

In extreme cases, you may need to change the video driver to generic VGA or super VGA.

Starting TinyTERM 3.3 on Windows 95 may give the error, “CTL3D32.DLL error.” Replacing the file does not fix the issue.

This happens when there are too many ctl3d32.xxx and ctl3d32.dll files on the PC. Remove all copies of both files, except the one in C:\Windows\System. Then reboot the PC.

Installing TERM Professional 3.3 on Window NT 4.0, you may see the error “Sesman.exe unable to locate rasapi32.dll.” This happens when RAS is not installed in Windows NT. To bypass the error, either uncheck the Desktop Manager option in the TERM Professional install, or install the RAS option on Windows before installing TERM Professional.

Using TinyTERM on Windows NT 4.0, installing a Windows service packmay cause registry errors. Uninstalling and reinstalling TinyTERM should fix this. If you still have problems after that, do the following:

1. Uninstall TinyTERM and NetUtils through Control Panel.
2. Click the Start button.
3. Select Run.
4. Type in regedit and click OK
5. Click the + sign next to HKEY_Current_User.
6. Click the + sign next to Software.
7. Delete any “Century Software” or “NCD Software” folders.
8. Click the + sign next to HKEY_Local_Machine
9. Click the + sign next to Software.
10. Delete any “Century Software” or “NCD Software” folders.
11. Close the Registry Editor.
12. Open Windows Explorer or My Computer.
13. Delete any Century folders from C:\ and C:\Program Files.
14. Go to the Windows folder.
15. Delete any marathon.* or marsetup.* files listed there.
16. Reboot the PC.
17. Now install TinyTERM.

Using TinyTERM 3.3 with Citrix Winframe on Windows NT 3.51, it works properly on a client until it logs out. At this point the session on the Unix server is closed, but the TinyTERM window stays open. The only way to get rid of the window is through Task Manager.

Century Software, Inc., has never supported TinyTERM 3.3 or earlier versions in a terminal services environment. However, it may help to uninstall TinyTERM and run Scandisk on the hard drive. When that’s done, reboot and reinstall Tiny Term.

Using TinyTERM or TERM for Windows, Alt keys are ignored in the emulator by default, even if you’ve remapped them. Under the keyboard configuration there is a check box labeled, “Use Alt keys in emulation.” That needs to be set; otherwise, Windows uses the Alt keys.

Note that in TinyTERM versions prior to 4.0, and by extension all versions of TERM for Windows, that Alt-F4 can be remapped, but Windows will still read it. This will of course close the emulator, no matter what mapping you may have set for it.