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

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.

It is possible to open multiple sessions over a single serial connection. It requires software such as mscreen or FacetTerm on the host system. Without that, only one session can run on a serial connection.

You also need to set the screen pages. That’s handled differently by different versions of TERM and TinyTERM:

• TERM: Use the TERM Script Language command PAGES:
  

  pages 4

• TinyTERM (up to 3.3) or TERM for Windows: Go to the Configure menu and select Emulation. Change the Screen Pages line.
• TinyTERM for DOS: From the main menu, select Emulation. Change the Screen Pages line.
• TinyTERM 4.00-4.20: Edit the .tpx file in Notepad or another text editor. Search for the “pages=” line. Edit the number there.
• TinyTERM 4.21 and higher: Go to the Edit menu and select Preferences. Change the Screen Pages drop-down.

Regardless of which product you’re using, accepted values for the screen pages are 1-6.

CR 26, added to user interface in TinyTERM 4.21

When replacing a dedicated (dumb) terminal with a PC, TinyTERM version may not connect over the known good serial connection. This usually means you need a null modem adapter on one end of the cable.

On a terminal, the pins line up 2-2 and 3-3. A PC uses the same hardware as the server, rather than the reversed version common to terminals. Thus, the pins need to line up 3-2 and 2-3. A null modem adapter corrects this without requiring a new data cable.

If running a transparent print job causes TinyTERM to disconnect the modem, try printing to a file instead. This bypasses the Windows printer manager, which may be interfering.

If that does not help, TinyTERM has gotten corrupted. Uninstall it, then delete the directory. Reboot and reinstall TinyTERM.