On Windows NT, 2000 or XP, TinyTERM 4.x will sometimes hang after a modem connection disconnects normally. There are two possible solutions:

1. Open TinyTERM’s Session Properties and go to the Login tab. Click the Logout radio button. Delete any text in the 1st Send, Wait for, Then Send and Retry fields on that same tab. Save the changes.
2. If that does not work, update the modem drivers on the PC.

There are circumstances where neither of these solutions works. In that case, the only fix is to kill TinyTERM from the Task Manager. To get to that, right-click on a blank area of your taskbar. Select Task Manager from the popup menu. Click on TinyTERM in the list of applications, then click the End Task button. That will close TinyTERM.

Please note that there is no way to get rid of the “Remote party disconnected” message. It will come up any time the remote system closes the telephone connection. This also alerts you to premature connection losses.

CR 117
CR 187

When you’ve set up an RS232 (Serial) connection, but aren’t getting a login prompt, there are several things to check:

1. Make sure you’ve chosen the right serial port. For example, TinyTERM defaults to COM2. If your PC only has one serial port, COM1, you’ll need to change the default.
2. Verify the communications settings. The baud rate, parity, word length and stop bits all need to match the port settings on the host computer, for the host port your PC is connected to. Each port on the host can have a different communication setup, though that’s uncommon.

If everything is set correctly, but you’re still not seeing a login prompt, you need to test the connection with another application. For example, there is a program included with Windows versions up to XP (but not Vista) named HyperTerminal. Regardless of the application or operating system you use, configure the connection the same as in TERM or TinyTERM.

If everything is set correctly in the other application, but you still don’t get a login prompt, then the problem isn’t in the terminal emulation software. It may be a problem in your PC’s serial port, in the cable connecting you to the host, or in the host’s serial port. You’ll need to test the hardware for failures in that case.

This error means that TinyTERM isn’t detecting a dial tone. When you get this error, first check to see if other Windows programs — HyperTerminal, a dial-up Internet connection, etc. — can use the same phone line.

If not, then check to make sure the telephone line is properly plugged into the modem and the wall. If it is, try plugging a telephone into the same line. That will tell you whether the problem is in the line or the modem itself.

If other Windows applications can use the modem, first try updating your modem driver. After updating the driver, if TinyTERM still can’t use the modem, there’s a compatibility problem. You’ll need to dial the modem manually. Instructions are in our knowledge base here.

When connecting, you may see something like this display:

^L1^T5^S

This comes from a failed automatic login. To fix it, go to the automatic login configuration in TERM or TinyTERM. Clear out everything there, so no settings are left. Saving that configuration will get rid of those characters.

This is normal behavior when “backspace sends delete” is turned on. It can also cause the last character in some text entry fields to disappear. Turning it off depends on which product you’re using:

TERM for UNIX or DOS
Execute this TERM Script Language command:

SET BSDEL OFF

TinyTERM for Windows version 3.x or earlier,
and TERM for Windows
Go to the Configure menu and select Emulation. Clear the BACKSPACE key sends DELETE check box.

TinyTERM for Windows version 4.0x
Edit the .tpx file using any text editor. Search for the line:

destbs=1

Change the 1 to a 0 (zero). Save the file. The change will take effect the next time you start TinyTERM.

TinyTERM for Windows version 4.1x or higher
In the Session Properties, go to the Keyboard tab. Clear the Destructive Back Space check box.

CR 98, default changed in TinyTERM 4.20
CR 160, .tpx files changed
CR 375, UI added

Using the keyboard mapping function, you can configure a key to send a BREAK signal. By default, this is mapped to ^B in TERM for DOS or UNIX. You can change that with the SETKEY script command. For example, to set F10 as the BREAK key, the command is:

setkey f10 break

In TinyTERM for Windows, open the keyboard mapper and click the Chart button to open the TCS Chart. Click the F button there to bring up the function list. With the mouse pointer drag the word BREAK from the chart and drop it on the key you want to use.

Some releases of TinyTERM 4.x ignore the BREAK command from the chart. When this happens, click on the key in the keyboard mapper you want to use. Change the Action drop-down to COMMAND. In the Value field, type:

te.break();

Click the Set button to finalize the mapping.

CR 415

When this happens, check the Line Turnaround Character (LTA) in the emulation setup. It should be set to 13 normally, the ASCII value of a carriage return (CR). If it’s set incorrectly, or not set at all, then the function keys will not work.

When you use TinyTERM 4.05, the emulator will reset the “Keyboard” settings in the Windows Control Panel. It forces the “Cursor blink rate” to it’s highest setting. In turn, the cursor virtually disappears while typing text.

There is no patch or workaround for this. The only solution is to use a different version of TinyTERM.

TinyTERM version 4 requires Winsock2 for TCP/IP connectivity. This is not installed by default in Windows 95. You will need to add two patches: DCOM95 and WS2Setup. We recommend you install these before installing TinyTERM.

When using SCOANSI, AT386 or other ANSI-series emulations, screens that should have lines or boxes drawn may not. Or the lines may draw as letters instead.

To fix that, open the Session Properties and go to the Code Page tab. Click the Advanced button. The top two lines of that dialog are SCOANSI alternate character sets. Set both to “STD 437 MS-DOS Latin US”. That should correct the line draw problem.

You can also go to the Attributes tab and check the “Use Non-Font Based line draw characters” option. This will use Windows graphics instead of text characters to draw the lines.

Restoring the code pages to the alternate character sets will also fix character alignment problems. For example, if the screen goes out of alignment when you minimize TinyTERM, check the SCOANSI alternate character sets.

CR 281, default.tpx
CR 360, added to all included .tpx files