When transparent printing on Windows 2000 direct to LPT1:, the last page of the printout doesn’t print until you close TinyTERM. There is no patch or workaround for this.

On Windows 2000 we recommend you print to the Windows printer with the Bypass Printer Drivers option set. However, if you must print direct to device instead, this was fixed in TinyTERM 4.20.

CR 193

When printing to the Windows printer in TinyTERM 4.x, the Page Setup dialog comes up for every print job. In TinyTERM 4.13 this was changed so that the Page Setup dialog only came up once, the first time you used a given printer in TinyTERM. To make changes between print jobs, you must go to the File menu and select Page setup.

TinyTERM 4.30 added a check box labeled Page Setup Every Print. If that is not checked, then the Page Setup dialog comes up only the first time a print job is sent to the selected printer. With that option checked, every print job produces a Page Setup dialog. This is helpful when each printout has separate requirements.

However, if you have Bypass Printer Drivers set, you can’t turn off Page Setup Every Print. The check box is checked, and the option is grayed out. This was fixed in TinyTERM 4.40.

If you have TinyTERM configured to print directly to a COM port, you will also get the Page Setup dialog regardless of other settings. The workaround for this is to configure a Windows printer on that COM port, then print to that Windows printer and bypass the printer drivers.

CR 19, Page Setup one time only
CR 325, check box added
CR 560, Bypass fixed
CR 692, adjustments made in TinyTERM 4.43
CR 703, COM port
CR 804, Page Setup on every Print Screen

When the Printer Setup dialog box was revamped for TinyTERM 4.13, the Flush Output option was removed. It was re-added in the Transparent Print Only section of Printer Setup in TinyTERM 4.20.

Cr 189

TERM Script Language includes a TERMINAL command. It returns control of TERM to the user until a match string is received. That capability was added to CScript in TinyTERM 4.21 with the te.Terminal() method.

CR 188

When TinyTERM Plus is connected via SSH, the Status Bar reads, “Connected = Telnet.” There is no patch for this. It was fixed in TinyTERM Plus 4.20.

CR 183

Then NFS server and client included with TinyTERM Plus 4.12 give errors that the license is invalid. The same thing happens in TERM Professional 3.3 for Medical Manager. There is no patch for this.

CR 178, 4.12 fixed in TinyTERM Plus 4.20
CR 362, TERM Professional

Installing TinyTERM Plus on Windows 2000 may produce the error, “Files that are required for Windows to run properly have been replaced by unrecognized versions. To maintain system stability, Windows must restore the original versions of these files. Insert your Windows 2000 Professional CDROM now.” This is a warning that the file C:\Windows\System32\Msvcrt40.dll was replaced during the TinyTERM install.

You can safely ignore this error. Clicking the Ignore button on the message does not have any negative repercussions

CR 173, fixed in TinyTERM Plus 4.20 .

TN5250 emulation allows binary data capture for troubleshooting purposes. However, turning on data capture often opens the Page Setup dialog instead. If you click OK, the data is captured to the printer. This is fixed in TinyTERM Plus 4.40.

CR 172

In TinyTERM versions prior to 4.21, if there is a Winsock problem, you have to wait for TinyTERM to time out before you can do anything. TinyTERM 4.21 allows for an instant disconnect, regardless of the state of Winsock.

CR 170

Some versions of TinyTERM Thin Client give the error, “Serial number does not match activation key” on install. This also happens with TinyTERM Web Server and TinyTERM Web Server Client in the same releases. It’s fixed in version 4.20.

CR 169, TinyTERM Thin Client
CR 571, TinyTERM Web Server