Configure TinyTERM to show the vertical scrollbar. Then use the bottom right corner to resize the TinyTERM window. The scrollbar changes its width and leaves visual artifacts behind.

CR 969, fixed in TinyTERM 4.7.2, 15 March 2012

Every time a session is saved, TinyTERM stores the current hostname or IP address in the .tpx file. If the hostname is changed, both the previous and current address are stored. These can be accessed from a drop-down list on the Sessiontab of TinyTERM’s settings.

To remove this history list, open the .tpx file in a text editor. Search it for the line that starts:

node=

Delete all the addresses that should no longer be stored.

Century Software has received a request for a user interface option that will remove those extra addresses.

Cr 962

On some Windows 7 systems, TinyTERM version 4.65.4985 (August 2011 release) will fail to run. Instead, the following error comes up:

Error (4547) Method Redraw Called With Invalid Object Instance

This is due to User Access Control (UAC) settings interfering with the TinyTERM install process. It’s caused by a bug in the install routines. This was fixed in TinyTERM version 4.65.5012.

Many host applications display shaded boxes by drawing some of the character cells around the box in black. At certain screen resolutions, TinyTERM will display light-colored lines between these cells.

This is a draw bug allowing a TinyTERM default background color through. It happens on Windows, Mac and Linux platforms.

CR 939

On 64-bit Windows 7, TinyTERM Plus may fail to connect automatically when the connection type is set to SSH. This can be cleared up by running TinyTERM in a 32-bit compatibility mode. To do that, follow these steps:

1. Go to the Start menu and right-click on the TinyTERM Emulator icon.
2. Select Properties from the pop-up menu.
3. In the resulting dialog, go to the Compatibility tab.
4. Check the box marked Run this program in compatibility mode for:
5. Select Windows XP (Service Pack 3) from the drop-down list.
6. OK the changes.

SSH will connect normally after that.

When running TinyTERM version 4.63 or higher, you may get an error message that reads, “This copy of TinyTERM is not licensed to run on Microsoft server operating systems.” It is most common on Windows Vista and later Windows versions.

This message indicates that the product is not licensed to run in a terminal server environment. TinyTERM uses concurrent licensing in Microsoft terminal server environments such as Windows 2008 Server.

If you believe you have received this message in error, please contact Century Software technical support at support@centurysoftware.com or 801-268-3088. Please have your activation key and your Windows version available. We will work with you to get this issue resolved.

When running TinyTERM version 4.63 or higher, you may see a “License Count Exceeded” error dialog. This happens when you open more windows than your product is licensed for. For example, a three-user TinyTERM Plus license will only allow three windows to open. The fourth will see this error.

This is by design. In terminal server environments such as Microsoft Windows 2008 Server, TinyTERM Plus is licensed concurrently. Only the licensed number of TinyTERM instances may be run at one time.

You may get this message in error on standalone PCs. If this is happening, and you believe it should not be, please contact technical support at support@centurysoftware.com or 801-268-3088. Please have your 25-character activation key available, and let us know which version of Windows you are using. We will resolve this issue for you.

On Windows Vista and Windows 7, attempting to delete a .tpx file as described here appears to work. But when TinyTERM starts again, the deleted connection settings are still there.

Those versions of Windows back up important files in case of accidental deletion. This includes TinyTERM’s .tpx files. The backup copies are kept in a special directory:

C:\Users\<username>\AppData\Local\VirtualStore\Program Files\Century\TinyTERM

where <username> is the login name of the user who deleted the files.

To delete the files, delete both the main and backup copies. The next time TinyTERM starts, the connection settings will be back at default.

Century Software, Inc., has received a report in reference to Windows Vista Business Edition running in VMware, with an Agere OCM Serial Modem installed. Any attempt to configure a TAPI connection in that environment causes TinyTERM to crash with:

CSL Run Engine has encountered a problem and needs to close.

The same configuration works fine when using Windows XP in the same environment. Century Software has not been able to duplicate this error.

CR 881

On a widescreen monitor, if TinyTERM is maximized to fill the screen, the letters will probably be spaced far enough apart to be distracting and hard to read. Widescreen monitors use a 16:9 or similar aspect ratio intended to be like a movie screen. The dedicated terminals TinyTERM emulates all used a 4:3 aspect ratio, similar to a standard television. That makes a widescreen monitor about 1/3 wider than an equivalent terminal, so the letters are spaced that much farther apart. There are two ways to compensate for this in TinyTERM.

The preferred method is to run TinyTERM in a window, rather than full screen. You can resize the window to use the full height of the screen, widening it until it looks correct to the user.

The alternate method is to change the number of columns TinyTERM displays. To do that, open the Session Properties. In the lower right of the Session tab, check the “Use custom emulation size” box. Change the number of columns to 132. Leave the number of lines as-is. This will cause TinyTERM to display the maximum number of letters it can support in each line. However, it will cause display oddities for text longer than the terminal standard of 80 characters.

Once you have either resized TinyTERM to match your preference or increased the number of columns, go to the File menu and select Save Session to save your settings. This will ensure that the spacing does not automatically reset.