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.

If fonts aren’t scaling properly in TinyTERM version 3.x, first verify you have the “Scale to window” option checked. If that’s set, but the font is still too small, duplicate TERM fonts are causing the problem.

To fix that, go the Windows fonts folder. Look for the fonts named term*.fon; i.e., term480.fon, term600.fon, etc. Delete all but the highest-numbered one. The next time you start TinyTERM, the fonts should scale properly.

TinyTERM Plus or TERM Professional 3.3 installed in Windows 3.x. After the install, when Windows starts you may get two errors:

Cannot find syslog.dll
Cannot find file winsock.dll

Both of these files should be in the C:\Windows and C:\Windows\System directories. Copy them from their current location to both directories.

To get the winsock.dll file, you may need uninstall and reinstall TinyTERM. When you get to the screen that allows you to select which components you want to install, select the Century TCP/IP. You may be asked about installing a secondary network. This is what you want to select.

Before you start the install check your System.ini file. Search or Find the word “network” and take note of what is there. You will want to put these settings back in after the install if they change in any way.

If TinyTERM gives errors when trying to use the dialer or on boot, it usually means the PC does not have networking installed. To fix the errors, uninstall TinyTERM and reboot the PC. When you reinstall TinyTERM, uncheck Network Utilities and any other network option.

This error means that either TCP/IP is not installed, or there is a problem with the Winsock.dll file. It may be corrupted, or missing.

You may also have too many Winsock.dll files on the PC. This occurs when TCP/IP has been reinstalled multiple times. Remove it entirely in this case, then delete all copies of Winsock.dll. Restart Windows and reinstall TCP/IP at that point.

Using TERM or TinyTERM over a serial connection, with the emulation set to ANSI, the display is OK, but the arrow keys don’t work. With the emulation set to VT100, the arrow keys work, but instead of lines, it displays the letter d repeatedly.

To solve both the arrow key and line draw problems, check to see if the UNIX tty port is set to a word length of 7. If it is, set the port for a word lengthy of 8, 1 stop bit and no parity. The host application is sending 8-bit sequences for the line draw characters. With these changes, VT100 emulation will work.

Using TERM for UNIX to communicate from the SCO console to another SCO system, neither ANSI or SCOANSI emulations reproduce the remote host colors. In this case, use the TTY emulation for console-to-console communications. This is strictly a pass-through emulation and will reproduce the colors properly.

Using TinyTERM on Windows 95 on a Packard Bell PC, it won’t disconnect or let go of the phone line. Instead it gives an error that fmedia and faxworks are active.When this happens, edit the file win.ini. Locate the run= line and delete everything after the equals sign. Reboot the PC to finish the fix.

Running TinyTERM on Windows 3.1, you may get a bind error 10049 when telnetting to a host. This usually happens when you have more than one TCP stack, such as Novell Client 32, running at the same time. In this case, do not use the TCP/IP stack that Century provides. Use the one installed before TinyTERM instead.

The VT220 and VT320 emulations have two different function key modes, 7-bit and 8-bit. TinyTERM version 4 defaults to 8-bit handling of the function keys. But many host applications will only accept 7-bit function keys.

The VT220-7 and VT320-7 emulations in TinyTERM are strictly 7-bit emulations. Function keys in those emulations send the sequences required by applications requesting 7-bit key sequences.

Complicating the matter, some host systems do not recognize VT220-7 or VT320-7 as valid terminal types. For those cases, set the telnet terminal type to “vt220” or “vt320” as appropriate.

Century Software, Inc., also provides a replacement keyboard.dat with 7-bit definitions for VT function keys. To use the file, download it to your C:\Program Files\Century\TinyTERM directory. In that same directory, locate the existing keyboard.dat and rename it as a backup. Then rename the downloaded file to keyboard.dat.

The next time you start TinyTERM, open the Session Properties and go to the Keyboard tab. In the “Keyboard schemes” drop-down a new scheme will be available: VT220. Select that, then OK and save the changes. The same scheme will work for both VT220 and VT320 emulations.

CR 40, arrow keys
CR 500