Using any dot-matrix printers connected directly to an LPT port, in TinyTERM 4.x the print job is slow and loses data. The problem is in flow control between the PC and printer.

This was resolved in TinyTERM 4.13. There is no patch for earlier versions.

Sometimes a screen will display with double spaces when it shouldn’t. If you minimizes the TinyTERM window or obscure it in any way that causes it to repaint, then the lines appear normally.

This was fixed in TinyTERM 4.20. It is a known problem in all versions of TinyTERM for Windows prior to that. There is no patch for any prior version.

CR 167

If you configure TinyTERM to print direct to device and the printer is offline, printing will cause TinyTERM to freeze. If you leave the printer online TinyTERM will function properly.

CR 6, fixed in TinyTERM 4.13

This error comes from running a TinyTERM version prior to 4.10 on Windows Me. Only TinyTERM versions 4.10 and higher are supported in that environment.

In TinyTERM version 4’s Printer Setup, when you chose a Windows printer, you can use the Setup button to set the paper size, margins, etc. But the settings aren’t saved, so when you restart TinyTERM, every change you made is lost.

This feature was added in TinyTERM 4.13. Prior versions require making the Page Setup changes every time.

CR 154
CR 177, margin settings

When printing direct to device, there may not be a form feed at the end of the print job. This causes the last page of the printout to get “stuck” in the printer, waiting for someone to hit the page advance button.

An Add Form Feed (FF) option was added to the Printer Setup dialog in TinyTERM 4.13. It’s available when printing direct to device, or when bypassing the Windows printer driver. There is no patch for earlier versions.

CR 128

When transparent printing, if the printer runs out of paper during the print job, it will lose pages. For example, if you are printing a 100-page document and run out of paper on page 30, after loading more paper it will print a few more pages in sequence — maybe up to 34 or so — then skip several pages and resume printing around page 40.

This was corrected in TinyTERM 4.13. There is no patch for earlier versions.

CR 31

Connecting to the server via modem, when you disconnect TinyTERM it may lock up. Even though it’s a modem connection, this is most likely a corrupted installation of Winsock2. You will need to reinstall Winsock2 to fix the problem.

When running TERM as a background process with term &, you will get the error:

selrdr: eof error on console

repeated multiple times. To fix it, add -q to the TERM command line:

 term -q &

This puts TERM into quiet mode, so it does not try to display messages to the console.

This error comes up after setting the connection type to Modem. It indicates a general problem in Windows.

Delete your modem from the system, then reboot and reinstall the drivers. If that fails, Windows itself may need to be reinstalled.