This error happens installing TinyTERM 3.x to Windows 3.1. It means there is a 32-bit driver loading somewhere in Windows.

To bypass the error, you will need to locate the 32-bit driver causing the problem, then disable it until TinyTERM is installed. Unfortunately, there is no easy way to do this. Check the documentation on other installed software to see which program might be causing this.

When you see this message in TERM for UNIX, it means there’s a problem in the .termsys file. Edit the file and look for the line that starts:

setv _turnchar

It will have extraneous information after that. Change the line to read:

setv _turnchar “\r”

Save the file. That will get rid of the error.

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.

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.

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.

If you cannot get the FTP server to work on Windows 98, disable the Internet services. Then locate the file inetd.exe in the Century directory and run it. That will allow you to access and configure the FTP server manually.

Installing TinyTERM 3.3 on Windows 95 may produce an error message that the product is only for DOS. When this happens, copy the contents of the TinyTERM CD to a temporary directory on the hard drive. Reboot the PC in safe mode, then install TinyTERM from the hard drive copy.

Multiple file transfers in a TERM for UNIX script can cause error 1204. It usually happens after using the OK button to acknowledge that a file has been sent. The OK button sends a ^C, causing a script abort.

The workaround is to turn off the transfer status window before the transfer. The command to do that is:

set xferstat off

It can be put in the script anywhere, as long as it executes before any file transfers.

Using TinyTERM 3.2, you may get “Error #110 No Strings File,” followed by “Error #114 No Strings File.” This is a language error. Edit the .tap file you’re using; e.g., us.tap, using any text editor. Locate the line:

lang=HU

Change it to read:

lang=US

That will switch the base language from Hungarian to US English, fixing the errors.