Over a telnet session, everything works fine. With SSH, opening a file in vi puts the first line halfway down the screen. Paging forward and back with ^B and ^F produce similar results.

This is not a TinyTERM error. Running vi with the -w24 command-line parameter fixes the problem.

CR 564

Set up an SSH connection on a Web server, then click the link from a PC using TinyTERM Web Server Client. The fingerprint dialog may or may not come up. That appears to be OS-dependent. Either way, it never completes the connection.

It does write the fingerprint to the registry, though. You can make the connection happen after a failure by editing the registry. In HKEY_CURRENT_USER\Software\Century Software\HostKeys, rename “last_key” to the hostname or IP address of the target system.

CR 450, fixed in TinyTERM Web Server Client 4.31

Open TinyTERM’s Session Properties and click on the Port Forwarding tab. It comes to the front, but no other changes happen. Click it again and you get the correct tab. This happens the first time you click Port Forwarding, regardless of which other tab you come from. After you do this, you can move around the tabs normally.

CR 446, fixed in TinyTERM Plus 4.30

In TinyTERM Plus, set up an SSH connection and connect. The fingerprint dialog comes up and asks if you want to continue. If you click Yes, the original session doesn’t connect. Instead, a second session opens and brings up the username/password dialog. Enter your username and password, and this session connects. The first session does not connect initially, but will connect normally if you go back to it.

CR 428, fixed in TinyTERM 4.30

Connecting to a host running sshd version 3.2, TinyTERM Plus returns the error, “Error verifying key.” It works properly with older sshd daemons. This is fixed in TinyTERM Plus 4.30.

CR 411

The SSH connection type allows you to choose from four encryption methods: None, DES, Blowfish and Triple DES. Only the latter two work in TinyTERM Plus versions prior to 4.30.

CR 356

Fingerprint for SSH connections was added in TinyTERM Plus 4.21. TinyTERM 4.21 also includes the addition of proxy services for connecting through firewalls.

CR 305

When TinyTERM Plus is connected via SSH, the Status Bar reads, “Connected = Telnet.” There is no patch for this. It was fixed in TinyTERM Plus 4.20.

CR 183

In this situation TinyTERM works with telnet, but SSH sessions connect and immediately disconnect. This only happens if you have “Login at connect” checked in the Login tab of TinyTERM’s Session Properties.

Early versions of SSH in TinyTERM require a username and password on the Login tab, but the “Login at connect” caused connection problems. Without that set, TinyTERM connects and logs in properly. In later versions of TinyTERM, that option is grayed out when SSH is set.

If that option is not checked, check the version of sshd running on the host. TinyTERM versions 4.10-4.13 use SSH version 1.5. SSH 2.0 daemons must be configured to allow pre-2.0 connections when using those versions of TinyTERM.

TinyTERM and TERM for Windows can store multiple IP addresses and telephone numbers in a single configuration file. If you want to clean the list out, so it only shows one address or phone number, close TinyTERM. Open the .tap or .tpx file you’re using, such as default.tpx, in any text editor. Notepad or Wordpad will work.

Search for the line that starts “node=”. Delete everything after the equals sign =. Save the file and exit.

If there is one host address or phone number you want to save, make it the only entry after the =. Either way, the changes you made will take effect the next time you start TinyTERM.