When the host sets the number of columns in TinyTERM to 132, such as with the VMS command SET TERM/WID=132, the TinyTERM display changes appropriately. At some point afterward, the screen reverts to 80 columns. Neither the host nor the user needs to take any action to have this happen.

CR 917

TinyTERM for iPad 1.1 has the ability to change the text display area, based on whether or not the keyboard is visible. When the keyboard is brought back after being hidden, this sometimes causes data to scroll off the top of the screen.

This is due to the way TinyTERM deals with the changing number of lines and columns. It starts at the bottom left of the current display, then works up and to the right. Text that won’t fit in the reduced space is lost.

This is a compromise between the variable settings functionality and the amount of available space. It may not be the best way to handle the changes. Century Software welcomes suggestions on how this can be improved.

CR 916
CR 920

When connected to a Cisco router, the BREAK key does not open rmon as it should. The key is apparently not usable connected to a Cisco router at all.

CR 910

Century Software has received a request that TinyTERM for iPad automatically start the VPN when it’s launched. This would save a step in the connection setup process over VPNs.

CR 907

Century Software has received a request to add an automatic login capability to TinyTERM for iPad.

CR 906

Century Software has received a request for global color and encoding default in TinyTERM for iPad. This would allow a single set of colors, code pages, etc., to apply to all new connections after they are set.

CR 905, added in version 1.1.0

When using Wyse50 or Wyse60 emulation in TinyTERM for iPad version 1.0, reverse text displays as a solid block instead. This is an initialization error in the text draw. It was corrected in TinyTERM version 1.1.0.

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.