Some versions of TinyTERM have a bug in the Wyse50 emulation that cause it to leave reverse text on the screen, even when it should be cleared. For example, a menu highlight that should move when you press an arrow key instead stays behind, and highlights the new selection also.

This problem will also cause some text that should be displayed in reverse to be displayed as bold instead. Some text may not display at all, unless you minimize and restore the TinyTERM window. These Wyse50 issues were fixed in TinyTERM 4.31.

CR 490, bold
CR 507, refresh

If you enter a string in the WRU Answerback field, it may change to 0 or 255. This is a bug in some versions of TinyTERM. You should be able to enter any text in that field.

CR 487, fixed in TinyTERM 4.40

It is sometimes necessary to connect to a host via serial cable, then change the baud rate, word length or other connection information while connected. TinyTERM versions prior to 4.31 require you to disconnect before settings changes take effect. TinyTERM 4.31 and higher allow you to make the change on the fly.

CR 460

Support for device naming on AS/400 systems was added in TinyTERM Plus 4.40, for both TN3270 and TN5250 emulations.

CR 46, AS400

Open a reasonable-size file in vi, one that has more than a couple screens of information. Move partway through, then put the cursor in the middle of the screen. Type “dd” or Shift-J to delete a line. You get a Dr. Watson in tt.exe, stack overflow error.

If the file doesn’t take up a full screen of emulation, you won’t get a Dr. Watson error. However, the entire screen will scroll deleting a single line.

If you don’t delete lines, but just scroll down through the file, you can’t scroll back up. And the status line scrolls with the file text as well.

This affects all VT-series emulations. The scrolling problem affects the Linux emulation as well.

CR 458, Dr. Watson
CR 459, scrolling
both fixed in TinyTERM 4.31

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

The ANSI emulation is loosely defined at best. The screen display sequences are fairly well fixed, but the function key definitions vary from system to system.

If you are using ANSI emulation, but the function keys aren’t working, try another emulation instead. SCOANSI, AT386 and VT100 are all common options.

CR 449

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

Connect four or more sessions in TinyTERM. Disconnect two or three of the sessions. The remaining sessions no longer reflect the keys in the interface nor send the keys to the server.

However, TinyTERM is not locked. You can open and close any number of sessions, and get response from the new sessions. In the bad sessions, the display is OK, and the cursor still flashes.

If the second or subsequent session uses TN3270 or TN5250 emulation, you don’t have to close the session to cause the problem. Clicking OK on the Session Properties is enough to cause the keyboard errors.

CR 441, fixed in TinyTERM 4.31
CR 445, duplicate

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