When you map a key to a string in TinyTERM, then come back to look at it later, it shows in the Value field as a series of numbers in angle brackets. For example, the word “key” displays as:

<619><613><633>

The Value Viewer line always shows the exact text. But that line has an absolute limit to how much it can display. It can’t be scrolled like the Value field can.

CR 656

TinyTERM 4.40 does list in Control Panel as a program that can be removed. However, clicking the button to uninstall it does nothing. It must be uninstalled manually.

CR 655, fixed in TinyTERM 4.41

To improve CPU utilization, TinyTERM 4 changed the way data is cached or buffered before display. This can make screen display appear slower than it was in version 3.3.

Century Software, Inc., has had a request to make the buffer size user-controllable. This would improve apparent display speed, but would increase the demand on system resources.

CR 654

The SSH2 protocol includes the ClientAliveInterval and ClientAliveCountMax options. The sshd_config man page describes both:

ClientAliveInterval
Sets a timeout interval in seconds after which if no data has been received from the client, sshd will send a message through the encrypted channel to request a response from the client. The default is 0, indicating that these messages will not be sent to the client. This option applies to protocol version 2 only.

ClientAliveCountMax
Sets the number of client alive messages which may be sent without sshd receiving any messages back from the client. If this threshold is reached while client alive messages are being sent, sshd will disconnect the client, terminating the session. It is important to note that the use of client alive messages is very different from TCPKeepAlive. The client alive messages are sent through the encrypted channel and therefore will not be spoofable. The TCP keepalive option enabled by TCPKeepAlive is spoofable. The client alive mechanism is valuable when the client or server depend on knowing when a connection has become inactive.

TinyTERM Plus responds to the keepalive packets sent when ClientAliveInterval is non-zero. Thus, it does not automatically get disconnected when idle.

CR 653, added in version 4.8.1

In TinyTERM Plus’ Session Properties, set the terminal emulation to TN5250 and click the Apply button. Next, go to the Keyboard tab and click Edit. Click the Chart Open button. You get the 3270 keyboard chart. If you make changes and save the new mappings, it’s saved in the file keyboard.dat as a 3270 keyboard mapping.

This works properly in TinyTERM Plus 4.33 and earlier versions.

CR 650

The CScript command te.SetRGBEntry() does not change colors already on screen. It only takes effect when the screen is refreshed. For example, if you use the keyboard to scroll back and forth — Ctrl-PageUp and Ctrl-PageDown — the screen clears in the correct colors.

The colors don’t always change immediately, either. If you set up a startup script with a color change, it’s not in effect until something “pushes” it. Typing clear at a shell prompt is not enough. However, if you run Midnight Commander on Linux for example (enter mc at a shell prompt), the colors come up correctly. When you exit Midnight commander, though, the screen washes clear in a blue background before returning to the correct colors. Then you can use clear successfully at the prompt.

CR 649

On Windows XP or Vista, if a non-administrator user starts SecureFT, an error immediately displays:

The instruction at “0x77fc8fe1” referenced memory at “0x00720075”. The memory could not be “written”.

The user who installed TinyTERM Plus can always use SecureFT, even if the administrator rights required for install are later taken away.

You can work around this by enabling Windows 98 compatibility mode. To do this, login as an administrator. Right-click on the SecureFT shortcut and select Properties. Go to the Compatibility tab. Check the box labeled Run this program in compatibility mode for. Select Windows 98 / Windows Me from the drop-down list. Click OK to make the change permanent.

CR 648

On Solaris 8, TERM gives the error, “Cannot open device” when connecting to a tty port. This works properly on earlier versions of Solaris. Changing the port permissions does not help, nor does starting TERM with the -i command-line parameter.

Unlike ASCII terminals, the PF keys on an IBM 3270 or 5250 terminal send coded network signals. Since they’re not composed of ASCII sequences, there’s no way to use the te.xmit() CScript command to send the appropriate key.

CR 645

Century Software, Inc., has had a request to add an option to port forwarding that would allow the remote system to assign TCP ports dynamically. Currently port forwarding can only use assigned TCP ports.

CR 643