The following versions of TinyTERM and TERM are certified Year 2000 (Y2K) compliant:

• TinyTERM 3.3, April 1997 or later
• TinyTERM 4.05 or higher, September 1999 or later
• TERM for UNIX 6.2.5 or higher, 1997 or later
• All versions of TinyTERM or TERM for DOS.

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

Any version of TinyTERM or TERM for Windows can use a Windows-only printer, provided the driver is installed. As with USB printers, the specifics depend on which version of TinyTERM you have.

TinyTERM 3.x and earlier, also
Any version of TERM for Windows
The specified printer must be the Windows default printer. Set TinyTERM to use PRINTMNGR as its printing device. TinyTERM will then send all printer output to that printer.

TinyTERM 4.00 – 4.12
Select the “To Windows Printer” option in TinyTERM’s Printer Setup dialog. Then click the Setup button to choose the Windows printer.

TinyTERM 4.13 and newer
Select the “To Windows Printer” option in TinyTERM’s Printer Setup dialog. Use the drop-down list to select the desired printer. Do not set the “Use printer fonts” or “Bypass printer driver” option.

Unlike USB printers, there may be a hardware port such as LPT1: associated with a Windows-only printer. However, Windows-only printers require a Windows printer driver to function at all. Bypassing the printer driver will usually cause all print jobs to be lost.

Using TinyTERM 4.x, if you do not have web access, you can still use TinyTERM Web Emulator. “Web Emulator” is just the name for the terminal emulator in that version. It can be launched and used without any network access at all.

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.

Using Term for UNIX , one customer had everything running through a Visual Basic application. When the information from TERM started displaying to the screen, it forced the Visual Basic application to shut down. To bypass the problem, the TERM command line was changed to term -q. This put TERM into a quiet mode, preventing screen display.

When upgrading to a newer version of TERM or TinyTERM, you can still use the older configuration files, provided they have the same extension. For example, any version of TinyTERM for Windows that uses a .tap file can use them interchangeably with earlier or later versions of TinyTERM.

If the extension for the connection file has changed, such as from .con to .tap, you will need to recreate the file, or convert the older file. TinyTERM 3.x and TERM 7.x include a utility CONVTAP.EXE. This will convert a .con file to .tap format. TinyTERM 4.x includes a CScript named TAPtoTPX.cs that will convert a .tap file to .tpx format. But there is no utility to go from .con format to .tpx.

You may see this error installing TERM on SCO UNIX. It means there’s a SCO file missing. You can download the missing file from SCO.

Select “Sco OpenServer” as your operating system and “OpenServer” as your family, then select “Binary Compatibility Module 7.1.1 for Sco OpenServer(for UDK compatibility)” as the download. You’ll have to go through a couple more pages before you can download the module. Then install it using the instructions provided.

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.