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

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

Windows has a “standard keyboard buffer” feature which can be accessed programmatically. For example, the Visual Basic SendKeys function uses the buffer to pass information to other programs.

TinyTERM does not respond to input from the standard keyboard buffer. It has been reported that with a strict 16-bit implementation, TinyTERM will accept such input. However, that puts significant restrictions on the applications written to that standard.

CR 64

Century Software, Inc., has received a report that the TN3270 emulation hangs when you hit Return while in a protected field. This has not been duplicated. The actual problem may be caused by the next screen received from the host, not the protected field itself.

CR 639

The Wyse50 terminal includes a host message capability. To send the message, the command is \033F. This puts the message at the top of the display area, rather than in a reserved screen area. This is not implemented in TinyTERM as yet.

CR 635

With TERM for HP-UX, if you specify a .con file on the command line:

term connection.con

it does not successfully connect via modem. You get the error, “Modem not responding” instead. The modem responds normally if the .con file is not specified.

CR 633