This was reported in Wyse60-25 emulation. The arrow keys worked properly until the user opened Session Properties. After clicking OK there, the arrow keys failed. This has not been duplicated.

CR 587

TERM for Linux 6.28 gives either a segmentation fault or “unknown service family” when connecting via telnet. This is corrected with separate builds for the different Linux distros. Here are the download links:

Debian
SUSE
Red Hat Enterprise

One of these should work for any current Linux distro.

CR 585, segmentation fault
CR 606, unknown service family

The TERM for UNIX documentation states that in 132-column mode, you can use the Ctrl-Right Arrow key combination to scroll sideways. But the display text wraps at 80 columns regardless of whether 132-column mode is on or off. The TSL SET WRAP OFF command is also ignored.

CR 579

In Wyse60 emulation, the code \033`F switches text from normal mode to reverse. But the text still displays normally in TinyTERM. If you open Session Properties and click OK,  reverse text then displays properly.

CR 576

Neither TERM nor TinyTERM supports the Send key for IBM3101 and IBM3151 emulations.

CR 567

Run the following script command in TERM for Linux:

setkey sf1 “text”

No matter how it’s actually mapped, Shift-F1 does nothing. The same is true all the way through Shift-F12. Ctrl-function keys also fail, as do Ctrl+Shift and Alt keys. You can see this by running:

term -z ktest.cmd

In fact, Shift-F5 displays as “sf1” using that script. Shift-F8 is “sf4” and nothing past that works at all.

This also affects TERM for SCO UNIX versions 6.2.5b and 6.28 running on SCO 5.0.6 or higher. SCO maintenance pack 2 for SCO OpenServer 6 restores the system console to ANSI, instead of the default AT386. This fixes the problem on that particular OS.

CR 565

When the user’s password has expired, SSH disconnects with a “login refused” message. The SSH protocol allows for the opportunity to change the password, but this is not implemented in TinyTERM Plus.

CR 562

There is no convenient way to determine the connection settings for TERM or TinyTERM. You have to know in advance what they should be. Without that information, it’s nearly impossible to guess at how the connection should be configured.

In some environments, Cyrillic characters aren’t correct for Russian language display. In other environments, they work perfectly. There are no common factors identified to date.

CR 556

IBM publishes a product called UniVerse which supports “device licensing”; that is, when multiple sessions are opened it only uses one server license. This is not currently supported in TinyTERM.

CR 553