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.

While using TinyTERM 4.03, the keyboard may lock up, causing TinyTERM to stop responding to your typing. Moving the mouse frees up the keyboard.

This is a known issue with that version of TinyTERM. There is no patch. The only solution is to use a newer version of TinyTERM.

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.

This error means the IP address or hostname supplied for the connection is incorrect. Test the connection using the ping command from a system prompt. If you receive errors, verify the address or hostname you’re using.

If ping works, try to telnet to the host from a command prompt. Errors from this command indicate possible problems with the network or TC/IP configuration on your PC.

This error comes up when incorrect information is entered in the Telnet terminal type line of TinyTERM’s Session Properties. Erase that setting or the netterm setting to get rid of the error.

In this situation, TinyTERM connects to a host via serial cable successfully. Another application on the PC then makes a modem connection. This causes the system to lock up completely.

Check the IRQs used by the serial port and modem. If both are trying to use one IRQ — or worse, one COM port — that will cause the lockup. Assign the modem its own IRQ.

TinyTERM and TERM for DOS can both connect via IPX/SPX. They do not require TCP/IP as TinyTERM and TERM for Windows do.

In TinyTERM 4.00-4.13, there is no flow control setting in the user interface. To set flow control for those versions, go through Windows Device Manager and set it directly on the serial port.

A user interface for this was added in TinyTERM 4.20.

CR 25

Closing TinyTERM version 4.x, if you get “An error occurred in CenTE.ocx” when the last connection closes, it indicates a corrupt file. To fix the problem, uninstall TinyTERM. When that completes, reboot the PC and reinstall TinyTERM.