Using TinyTERM on Windows 95 or Windows 98 , when you print the Windows printer setup screen may come up and lock up TinyTERM. To fix that, do the following in TinyTERM:

1. From the File menu, select Printer Setup.
2. Select Direct to Device.
3. Set the device name to the printer port, usually LPT1:.
4. Check the “Flush output buffer to printer” box.
5. Click OK to close the Printer Setup window.
6. From the File menu, select Save Session.

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 on Windows 95 with an HP LaserJet printer, the fonts don’t always print correctly. However, they do print correctly in TinyTERM for DOS on the same PC.

In Windows 95, most HP LaserJet printers install a printer monitor program in the system tray, next to the clock on the task bar. If you remove this, the font problem will be solved. The program that needs to be ended is HPPROPTY.EXE.

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.

Installing TinyTERM Web Edition 4.0 on Windows 3.1, you may get an error that you are out of drive space, even if there is plenty of space available. When this happens, try installing TinyTERM to a sub-directory of an existing directory. You may not be able to create a new directory otherwise if there are more than 256 folders in the root of C:.

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.

Once a TERM Script or CScript is running, you can’t change its behavior. You can still edit the file, but TinyTERM and TERM cache scripts in memory when they’re executed. So any changes you make will not be read until the next time you execute the script.

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