SCOANSI emulation allows a host program to send \033[m to return text attributes to their default values. TinyTERM versions prior to 4.20 ignore this command. There is no patch for this issue.

CR 104, fixed in TinyTERM 4.20.

The Wyse60 terminal allows the host to set the number of lines to display. For 42 lines the host sends \033e*, and for 43 lines the host sends \033e+. TinyTERM versions prior to 4.20 do not respond to these escape sequences. There is no patch. You must use a newer version of TinyTERM to fix this.

CR 102, fixed in TinyTERM 4.20.

Connecting via modem, when TERM tries to XMIT a string the connection dies. This was tracked to the parity not being sent. There was no option to set parity in the modem initialization string.

The workaround was to use the TERM Script Language command SET MASKPAR ON. This masks the parity being sent.

CR 176

Sometimes a screen will display with double spaces when it shouldn’t. If you minimizes the TinyTERM window or obscure it in any way that causes it to repaint, then the lines appear normally.

This was fixed in TinyTERM 4.20. It is a known problem in all versions of TinyTERM for Windows prior to that. There is no patch for any prior version.

CR 167

Connecting to the server via modem, when you disconnect TinyTERM it may lock up. Even though it’s a modem connection, this is most likely a corrupted installation of Winsock2. You will need to reinstall Winsock2 to fix the problem.

This error comes up after setting the connection type to Modem. It indicates a general problem in Windows.

Delete your modem from the system, then reboot and reinstall the drivers. If that fails, Windows itself may need to be reinstalled.

This happens when TinyTERM connects via telnet, but America On-Line uses a dial-up connection. It’s due to a conflict between the TCP/IP stack for AOL and the Windows stack TinyTERM uses. TinyTERM can’t differentiate between the two.

TinyTERM versions 4.10 and higher have changes that correct for this. No patch is available for earlier versions.

Using TinyTERM 4.02, the modem dials, but it gets a high pitched sound and the remote party disconnects. There are known TAPI connectivity  issues in that version. There is no patch. The only solution is to upgrade.

This error generally means the phone line used by the modem is in use or otherwise not working. Test it with another modem-using application, such as cu or HyperTerminal. If that gives the same or a similar error, check your phone lines. You may also need to reboot your PC.

Using TinyTERM 4.04 over a serial connection, the text can pause occasionally, then more text will display. It’s very slow in such cases.

In TinyTERM 4.05 there was a change made to the way TinyTERM buffers screen display. It smooths out the pauses and clumping of text. There is no patch.