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.

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.

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

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

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

When connecting via SSH to a new system, TinyTERM asks the user to approve the host’s fingerprint. This dialog cannot be bypassed.

When using TinyTERM’s ActiveX control CenTE.ocx programatically, this dialog does not come up. If the host’s fingerprint is not already registered with TinyTERM, the connection fails silently. The only workaround is to connect to the host using TinyTERM to register the fingerprint first.

Century Software, Inc., has had a customer request that this dialog have an option to bypass it programatically. This would remove the need for manual connections to register the fingerprint.

CR 876

The TVI950 terminal includes a line lock feature which locks an 80-character line when the sequence

\033!1

is received. This is ignored in TinyTERM, producing no effect.

CR 874

Set TinyTERM’s terminal emulation to TTY. Connect to the host, then display text to the screen, more than one screenfull. When you scroll back, everything past the current screen is lost.

CR 873

In TinyTERM’s Session Properties, go to the Attributes tab and turn on the “Use non font-based line draw” option. Connect to your host system, then go to a screen that draws lines in a color other than the default. The lines will change colors, but refreshing the screen; i.e. by putting a new window in the foreground, then bringing TinyTERM back, changes the colors.

If you don’t set that option, line draw characters maintain the correct colors.

CR 871