If you need to map the same function to several keys in TinyTERM for Windows, with only minor changes to each one, you can speed up the process so you don’t have to type the same thing repeatedly. Once you’ve mapped the first key, use the mouse to drag it to the Clipboard in the Keyboard Mapper. You’ll find it in the lower left-hand corner of the “Edit Keyboard Map” dialog box. This copies the entire key to the clipboard. You can then drag the Clipboard to any number of keys, making them all the same. Once that’s done, click on each of the keys you remapped to change them individually.

You can also view this information in a screencast by clicking here.

TinyTERM version 4.x requires Winsock2 to connect via TCP/IP. This is standard in Windows 98 or higher.

Windows 95 does have the ability to use Winsock1 only. You must update to Winsock2 to use TinyTERM version 4. In fact, TinyTERM 4.0x won’t install unless Winsock2 is included, even if you plan to use a serial or modem connection.

Older versions of TinyTERM or TERM for Windows can use Winsock1 or Winsock2 interchangeably.

CR 55, Winsock2 requirement removed for non-TCP/IP connections

Using TinyTERM 3.3 on Windows 95, you may see fuzzy, unreadable fonts which also affects other applications, such as Microsoft Word. There are several possible fixes for this problem:

1. TinyTERM Graphics Settings
   1. In TinyTERM, go to the Configure menu and select Emulation.
   2. Click the Advanced button.
   3. Check the Ignore graphics/parity bit option.
   4. OK and save the changes.
2. Duplicate Term Fonts
   This is generally caused by having several installs on one PC. To get rid of the duplicates:
   1. Open the Windows Control Panel.
   2. Double-click Fonts.
   3. Scroll down to the fonts named Term*.
   4. Delete any with duplicate names
3. Video Driver
   1. Open the Windows Control Panel.
   2. Double-click Display
   3. Change the display resolution.

In extreme cases, you may need to change the video driver to generic VGA or super VGA.

When TERM for UNIX displays this error, test cu or uucp against the same port. If either of those works, there may be a lockfile on the port. To bypass that, enter the command:

term -i

If that fails, list the port explicitly in the command line:

term -l/dev/ttyS0

Replace ttyS0 with the actual tty port. You can also combine this with the -i command-line parameter.

If everything above checks out, look at the number you’re dialing with the CALL command. The # character will cause the “unknown transport” error. This is problematic, particularly if your phone system requires you to dial something like #8 to get an outside line.

CR 412, CALL

This error comes up when there’s something wrong with the terminal emulation type. There are two places to check:

1. The “Telnet terminal type” or “netterm” setting in TERM or TinyTERM. (This only needs to be checked on network connections.) If it’s not set to a valid terminal type for the host system, it needs to be changed. If it’s blank, you may need to enter something, such as “vt220” when you’re using VT220-7 emulation.
2. The TERM environment variable on the host system. This will usually be stored in your .profile or equivalent. Like the telnet terminal type, this must be set to a valid emulation for the host system.

Some systems will request a terminal type when you login. You can usually hit Enter to accept the default; however, if it’s incorrect or listed as unknown, you will need to type an appropriate value.

In some cases, you may be unable to see certain fields in the emulation window. You know the fields are there, but the display of them is wrong or missing.

When this happens, verify that you are using the correct terminal emulation. Some emulations share display codes, but are not 100% compatible. Missing or otherwise scrambled display is normal in this case if the wrong emulation is chosen.

Using TERM for UNIX on a tty port, it may fail even though cu can see the port. When this happens, first verify the port permissions are 666 (-rw-rw-rw-). If that’s correct, launch TERM with the -i parameter:

term -i -l/dev/tty04

This will ignore any lockfiles on the tty port. Please be aware that if another application is using the port, it will be interrupted when you do this.

This error comes up when using TinyTERM or TERM for DOS on a PC with no networking installed. You will need to configure the connection again, as it’s been changed to try to use a network.

You may run into a situation where transparent printing works for a few pages of text, then gives a print error. After that the job may fail, or it may print one line per page.This is a flow control issue. Disable flow control on both the PC and the server port. Printing should work properly after that.

Old versions of TinyTERM will sometimes scroll the screen up one line when you switch between two or more sessions. This is a known issue. It was fixed in TinyTERM version 4.00. No patch exists for earlier versions.