This error is a protection error. It means the user doesn’t have permission to access the file default.tpx or the directory it’s in.

At a minimum, all users must be able to read the TinyTERM install directory, normally C:\Program Files\Century\TinyTERM. To make changes to default.tpx or any other file in that directory, they will also need write permissions.

On Windows Vista and Windows 7, it may not be possible to change the directory permissions, even after setting the User Account Control (UAC) setting to its minimum security level. In that case, the user will need to save settings to a different directory, one with write permissions. The user’s desktop or Documents folder are common choices.

CR 1027

When you see this error, go to Start | Programs | Startup. If there is a “Century repair” item there, delete it.

Next, open a command prompt. At that prompt go to the C:\Program Files\Century\TinyTERM directory. Run these two commands, one at a time:

tt /unregister
tt /register

If that does not solve the error, uninstall TinyTERM. Delete the C:\Program Files\Century folder, then reboot your PC and reinstall TinyTERM .

Reports that should go to your local printer may scroll across your emulator screen instead. There are several possible causes for this.

Your host application may not be configured for the correct printer. Make sure it is set for transparent printing, also called terminal, slave, local or remote printing.

If that is set correctly, check your printer settings in TERM or TinyTERM next. If no printer is selected, if the selected printer does not exist, or if the selected printer is off-line, correct that. Note that on older versions of TinyTERM or TERM for Windows, the PRINTMNGR option always uses the Windows default printer.

Test your printer with other applications also. If no application can print to the correct printer, check the printer manual for troubleshooting information.

Once the correct printer is selected and verified operational, test it with the “print screen” option in the emulator. In Windows products, this is on the File menu. In other operating systems, it’s mapped to the F6 function key by default. When this works, TERM/TinyTERM is communicating properly with the printer.

The remaining piece of the configuration is the emulation type. Each terminal emulation has a specific set of printing codes it uses. If the wrong codes are sent by the host application, then the job isn’t sent to the printer. The TERM/TinyTERM documentation includes a list of terminal emulations and their print codes.

Together the above items represent all the things that might go wrong for transparent printing. When it’s all verified correct, then printing through the emulator should work.

There is a known problem with multiple transparent print jobs. If you print a large number documents at once, somewhere after 50 print, the rest will start coming to the screen.

CR 609

This error usually indicates a corrupt configuration file. It may be accompanied by the error: “The CSL Run Engine ActiveX Doc Object Server has encountered a problem and needs to close.”

To fix the problem, locate the .tpx file you’re using, and rename or delete it. The next time TinyTERM starts, you’ll see a “file not found” error. Click OK to continue with the defaults. You will need to configure your connection again when doing this.

Terminal emulators running in a window do not work well with text-to-speech software such as Jaws or Dragon NaturallySpeaking. Because the screen information is not stored in a file format, it will often be ignored entirely.

To read a portion of the screen, select the text in the window. Be careful to select from upper left to lower right. Otherwise the text-to-speech program may read the selected area backwards.

CR 423

Sometimes the connection will work and allow the user to login normally. But after login, the keyboard stops responding. And it may not happen to all users.

This is most common with SSH connections, but can happen with any connection type. When this happens, edit the user’s .profile or equivalent on the UNIX or Linux host. Add one line to the end of the file:

stty sane

The next time the user logs in, the connection will work normally.

TinyTERM and TERM for Windows do not create desktop shortcuts as part of installation. However, you can create one manually.

The easiest way to do this is to click on Start | Programs | TinyTERM. Using your right mouse button from there, drag the “TinyTERM Emulator” icon out to the desktop. You’ll get a popup menu. Select “Copy here” from that menu, and the shortcut will automatically be created.

You can also create the shortcut step by step. Right-click on the desktop and select “New” from the popup menu, then “Shortcut”. In the box labeled, “Type the location of the item:” enter the following for TinyTERM version 4:

“C:\Program Files\Century\TinyTERM\tt.exe” -PL3 default

Replace PL3 with the first three letters of your serial number. Replace default with the name of the .tpx configuration file you’re using. The quotation marks and dash are required.

Click Next to enter a name for the shortcut. Click Finish, and the shortcut will appear on your desktop.

There are, of course, other ways to create a desktop shortcut in Windows. These methods are convenient for most PCs.

This error always refers to the TT.int file. It means TT.int is missing or corrupted.

To fix the error, copy TT.int from a PC with a working install of the same TinyTERM version. If one is not available, uninstall TinyTERM and delete the C:\Program Files\Century directory. Then reboot the PC and reinstall TinyTERM. Once the error is corrected, back up TT.int so you have a replacement copy if the error happens again.

A common cause of TT.int corruption is antivirus software. It’s just a collection of messages, but sometimes it gets incorrectly flagged as a virus and quarantined. Where possible, exempt TT.int from your virus scanner to prevent that.

CR 570

This error during a TinyTERM Plus install means that one or more files could not be overwritten. If you don’t need the NetUtils portion of TinyTERM, you can safely ignore the message.

If you do need NetUtils, copy the TinyTERM install directory to your local hard drive. Then reboot the PC in safe mode before running the install from the local copy. That will bypass any application preventing a file overwrite.

This error was resolved in TinyTERM Plus 4.60 by switching to an MSI installation.

CR 528

TinyTERM’s keyboard mapper allows you to remap the NumLock key. Version 4 also has a Force Num Lock on setting that will keep NumLock on for the TinyTERM window.

Doing both of these on a Windows NT, 2000, XP, 2003 or Vista system causes a particular issue. When you hit the remapped NumLock key, it repeats the mapped action three times.

Those operating systems read both the key press and the key release as separate events. TinyTERM also reads the key press as an event. So what actually happens is that the mapped action is triggered once for each event.

If the NumLock key is not mapped in TinyTERM, there is no problem with the Numlock signal being processed more than once. But altering TinyTERM’s behavior for this would damage other keyboard mapping functions.

CR 231