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

This may happen on Windows NT when the Century NFS client is installed. If you are not using NFS, you can fix the problem by uninstalling TinyTERM Plus and NetUtils. Reboot, then reinstall TinyTERM Plus without the NFS component.

No version of TinyTERM Plus designed for Windows 2000 or XP installs NFS by default. The NFS client is not supported in those environments, so those systems should never see this error.

On a fresh install of TinyTERM version 4.0x, starting the emulator may give you one or more “Get Property” errors. That may mean some of the important files didn’t properly register in Windows. To fix that, open a command prompt and go to the C:\Program Files\Century\TinyTERM directory. Then run these four commands:

regsvr32.exe cenbrows.ocx
regsvr32.exe cencom.dll
regsvr32.exe cenft.dll
regsvr32.exe cente.ocx

Sometimes when starting TinyTERM, the splash screen displays upside-down. This is not a bug in the graphic; rather, it’s a bug in the way the video driver displays it. Updating the video driver will usually fix the problem.

This happens because the height value of a bitmap image determines how it’s drawn. If the height value is negative, the bitmap is stored in reverse order. TinyTERM makes a system call to the Windows graphics API and passes the bitmap information off to it. TinyTERM does not draw the bitmap; the video driver and Windows GDI do it. If the video driver does not accept the negative height value, it draws the bitmap upside down.

The video software subsystem should be able to handle both positive and negative height values, as both are defined in the Win32 API library. If it doesn’t handle correctly, it doesn’t draw correctly. That’s why we recommend updating the video driver.

You can also prevent the splash screen from displaying. Add the -nosplash option to the TinyTERM command line. That will cause the TinyTERM window to display immediately.