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.

The duplex mode in TinyTERM has several settings. Each is useful for different servers and devices, as well as troubleshooting. The different modes are:

FULL
Everything on the screen comes from the server. Even what you type is sent to the server, then displayed back to TinyTERM. This is the default setting because it’s usually required.

HALF
What you type displays on the screen locally. If every character you type displays twice, this option is probably set. Some older servers require this, but it’s generally not used any more.

MNEMONIC
Non-printable characters are replaced by text describing them, such as <CR> for a carriage return. Useful for troubleshooting display issues.

CONTROL
Similar to mnemonic, but instead of text, control characters are shown with the caret-character combination. For example, a carriage return will display as ^M.

DUMP
All characters display as two-digit hexadecimal numbers, separated by spaces. So the word hello will display as
68 65 6c 6c 6f

This error means the serial port you’ve selected in TinyTERM isn’t usable on your PC. There are a few possible causes:

1. The serial port doesn’t exist. Older versions of TinyTERM offer ports COM1 through COM6, whether or not the ports are actually installed on the PC. Verify that the port number you’ve selected in TinyTERM has a matching physical port on the PC.
2. Another program is using the serial port you’ve chosen. This is common for software such as fax programs. The other program will monitor the COM port, even if it’s not currently in use. This prevents TinyTERM from connecting to it. Shut down or reconfigure any other software that uses serial ports to bypass this problem.
3. The serial port selected has a driver or hardware problem. Check with a trusted computer technician if this is the case.

If TinyTERM 4.6 is installed it on a PC that had an older version of TinyTERM, adding the license may cause the program to close with no errors. This happens when the previous license file, CenLic32.dll, was not removed before installing the new version.

To fix the problem, uninstall TinyTERM, then delete the directory C:\Program Files\Century. Restart the PC, then reinstall TinyTERM 4.6. It will accept the license after that.

In TinyTERM 4.63, select rlogin as the connection type. Add a username to the Login tab, then connect. TinyTERM closes with no errors. The debug monitor shows a disconnect, then nothing.

This is due to a bug in TinyTERM’s communications file cencom.dll. A replacement file is available for download.

CR 892

If TinyTERM Plus 4.60 or higher is installed on a Windows terminal server, every user has to license it to run it. This is due to the nature of licensing in TinyTERM 4.6, which uses a license certificate file license.crt, rather than a registry entry as in prior versions of TinyTERM.

When this happens, the license.crt file was written to the administrator’s My Documents folder. This is one of two locations where the file can be written, and is normal for domain systems.

As a local PC administrator, copy license.crt to C:\Program Files\Century\TinyTERM. Make sure all users have read access to the file. (On some systems, it’s also necessary to give all users write access.) That should resolve the issue.

TinyTERM does support 28800 baud as a connection speed. You can set that with this script command:

te.baud = 28800;

But this option is not available in the user interface. Century Software has received a request to add it.

CR 887

Change the default background color in TinyTERM to anything other than the default blue. Then read the background color in CScript:

var test = te.GetBGColor(0);

test will always equal 0, regardless of the current background color.

CR 888

Set a background image in TinyTERM using CScript:

te.SetBackgroundImage("file.jpg",0);

The display does not change, though the command reports as running successfully.

CR 889

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