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

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

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

Configure TinyTERM for Wyse60 emulation, then connect to a Linux system. Once logged in, switch to page 1 from page 0. An easy way to do this is to run vi, then exit it.

The TinyTERM screen displays in the wrong colors. Anything you type is correct, though. Clearing the screen sets the colors correctly and maintains them from then on.

CR 529

The PCTerm emulation in TinyTERM 4.x does not work properly. The host should be able to switch Wyse60 emulation to this mode. Once the escape sequence is received for PCTerm mode, all characters are wrong. And TinyTERM can’t exit that mode since the escape sequence for returning to Wyse60 is similarly scrambled, and so unrecognized.

CR 41, character display
CR 44, mode switch

Century Software, Inc., has had a request to add protected mode to the Wyse50 terminal emulation. That has not been implemented thus far.

CR 397

Under certain circumstances, the Wyse50 emulation will ignore control sequences that switch it between 80 and 132 columns. This cannot be reliably duplicated, but it has been conclusively demonstrated. At this point it’s undetermined exactly what the trigger is that causes the switch to be ignored.

CR 158

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

After using vi or other full-screen applications, the Wyse60 emulation won’t scroll back. It doesn’t matter if you use the vertical scrollbar or the keyboard commands.

This is due to the way Wyse60 terminals work. Full-screen applications such as vi often put the terminal into a different screen page, which clears all memory of the previous screen page. Exiting the application sets the terminal back to screen page 0. Essentially, there’s nothing to scroll back to at that point.

Disabling screen pages in Wyse60 will cause problems with some applications. So no option to do so has been added to TinyTERM.

CR 396
CR 505

When the Wyse50 emulation receives \033d, it incorrectly interprets that as a “print on” code. This causes TinyTERM to appear to hang, as no corresponding “print off” code is ever received. This is fixed in TinyTERM 4.20.

CR 201