The Back Tab option in the keyboard mapper for TN5250 does nothing. When that is mapped to a key, it’s as if the key were mapped to nothing. There is no patch for this.

CR 114, fixed in TinyTERM Plus 4.40.

The SNA protocol is a native IBM network protocol. TinyTERM does not support it for TN3270 or TN5250 emulations. Only TCP/IP connections are supported.

The TN5250 emulation available in TERM Professional and TinyTERM Plus will not work through an IBM 5250 card. The 5250 card has its own software and cabling. TinyTERM Plus and TERM Professional use TCP/IP.

Telnet is the only option available to both. TinyTERM Plus version 4.5 also has SSL/TLS capabilities.

Using TinyTERM Plus Edition 4.04, how do you connect through a telnet firewall to an IBM host with TN5250 or TN3270 terminal emulation?

Configure a sessions using the TTY terminal type and a telnet connection to connect to the firewall as follows:

• Connection host: firewall name or IP address
• Connection Type: telnet
• Terminal Emulation: TTY
• Telnet Terminal Type: (depends on IBM emulation required)
  • 3270
    • IBM-3278-2
    • IBM-3278-3
    • IBM-3278-4
    • IBM-3278-5
  • 5250
    • IBM-3179-2
    • IBM3477-FC
• Save the session.
• Telnet to the firewall using this configuration. When the firewall prompts for the host, enter the hostname or IP address of the destination host.
• Depending on your firewall, you may have to hit the Enter key once to display the initial host screen.

NOTE 1: TinyTERM senses telnet binary mode to know when to switch emulations from TTY to one of the IBM emulations. The IBM terminal emulation desired is specified by the Telnet Terminal Type configuration.

NOTE 2: To preserve the initial firewall connection configuration do not save the session after the IBM host connection is made. TinyTERM changes your session properties when the IBM connection is made.

The TN5250 emulation included with TinyTERM Plus does not have the capability to set up print sessions. It can only print screen.

CR 34

TinyTERM Plus version 4.05 will use 100% of the CPU if a session is configured for TN3270 or TN5250 emulation. TinyTERM Plus 4.10 will do the same thing with two or more sessions open using those emulations.

TinyTERM 3.3 will sometimes use 100% of the CPU regardless of the emulation chosen. Older versions of TERM or TinyTERM for Windows will do the same thing. TinyTERM does not need to be connected for this to happen.

There is no workaround for these situations. TinyTERM must be upgraded to improve its CPU utilization.

TinyTERM Plus Edition 4.05 may use 100% of the CPU after install on Windows NT 4.0, even when the TinyTERM Emulator is not running. That’s caused by the NFS client included with TinyTERM Plus Edition. To fix that, uninstall TinyTERM and NetUtils. Reboot the PC, then reinstall without the NFS component.

TinyTERM 4.31 and higher will use 100% of the CPU on Windows 98 or Me when connected via TCP/IP or modem. This does not happen on Windows 98 Second Edition, nor does it happen with serial connections.

CR 72, improved in TinyTERM 4.12
CR 294, reported in TinyTERM 4.20
CR 647, Windows 98 and Me