TinyTERM Plus 3.2 comes with a Marathon TCP/IP stack for Windows 3.1. If you want to install without it, edit the PC’s AUTOEXEC.BAT and CONFIG.SYS files.

In the AUTOEXEC.BAT, REM out everything except ECHO, PROMPT and PATH commands. In the CONFIG.SYS, REM out everything except FILES, BUFFER, HIMEM.SYS and EMM386.EXE.

Restart your PC after this. When you install TinyTERM, you will be able to bypass the Marathon portion.

This happens on Windows 95 when there is insufficient space on the C: drive. You will need to free up about 20 Mb of space before attempting the install again.NOTE: If you have already started an install, you need to remove any Century folders, Marathon or Marsetup files before trying to install again.

This error comes up when installing TinyTERM 3.2 on Windows 3.1. It’s caused by one of two things:

1. Multiple Winsocks are installed on the PC. Remove them and reinstall only one.
2. No Winsock is installed on the PC. Install one before installing TinyTERM.

Installing TinyTERM on Windows 3.1, it may ask for an IP address, even if you plan a serial connection. When this happens, click the Back button and deselect the network installation.

This error indicates a damaged .tap or .tpx file. To fix it, exit TinyTERM. Delete the file, then start TinyTERM again. Recreate the configuration and save it.

Error 502 means that TinyTERM has no network driver selected. To select a network driver, do the following:

1. Open the ICONect or .tap file.
2. Go to the Configure menu and select Communications.
3. Select Network Login for the port.
4. Click the Network button and choose Generic Winsock as the network type.

TERM and TinyTERM for DOS can both be loaded into high memory with the LOADHIGH or LH command.

To shell out to DOS in TERM, type Alt-F4. In TinyTERM, the hotkey is Alt-H. Either can be remapped through the included utilities.

Using TinyTERM 3.3 on Windows 95 or 98, printing the screen may require you to press the reset button on your printer before other applications can use it. To fix this, configure TinyTERM to print to PRINTMNGR instead of DEVICE. This will allow Windows to manage the printer, eliminating the need for you to reset it.

Using TinyTERM 3.3 and PCTERM emulation on Windows 3.1, some keys give extra characters, such as:

pressing a key gives ad
x gives xx
l gives l_

To fix this, change the primary code page to “STD 437 MS-DOS Latin US.”

If your display is correct, but the application doesn’t respond to the function keys, try a different terminal emulation. Function keys send escape or control sequences that are emulation-specific. If the sequence doesn’t match what the application expects, the function key will fail.

If no emulation seems to work, check with the application software publisher. Find out what the application expects to see from each function key. You can then program the function keys in TinyTERM’s keyboard mapper.