The “print on” code for Wyse50 emulation is ^X. That’s the same code used to end a file transfer in the ZMODEM and WTERMCRC protocols.

To avoid problems, use a different file transfer protocol with Wyse50. Or use a different emulation with ZMODEM and WTERMCRC. Either solution will work.

Reports that should go to your local printer may scroll across your emulator screen instead. There are several possible causes for this.

Your host application may not be configured for the correct printer. Make sure it is set for transparent printing, also called terminal, slave, local or remote printing.

If that is set correctly, check your printer settings in TERM or TinyTERM next. If no printer is selected, if the selected printer does not exist, or if the selected printer is off-line, correct that. Note that on older versions of TinyTERM or TERM for Windows, the PRINTMNGR option always uses the Windows default printer.

Test your printer with other applications also. If no application can print to the correct printer, check the printer manual for troubleshooting information.

Once the correct printer is selected and verified operational, test it with the “print screen” option in the emulator. In Windows products, this is on the File menu. In other operating systems, it’s mapped to the F6 function key by default. When this works, TERM/TinyTERM is communicating properly with the printer.

The remaining piece of the configuration is the emulation type. Each terminal emulation has a specific set of printing codes it uses. If the wrong codes are sent by the host application, then the job isn’t sent to the printer. The TERM/TinyTERM documentation includes a list of terminal emulations and their print codes.

Together the above items represent all the things that might go wrong for transparent printing. When it’s all verified correct, then printing through the emulator should work.

There is a known problem with multiple transparent print jobs. If you print a large number documents at once, somewhere after 50 print, the rest will start coming to the screen.

CR 609

Print jobs from the server may print one line, feed a page, then print the next line, and so on. This usually happens when the host application turns transparent printing on at the beginning of each line, then off at the end. TinyTERM versions 4.00 and higher include a workaround to stop this problem.

TinyTERM 4.00-4.12
In TinyTERM’s Printer Setup, check the Manually stop print jobs box. This will make the Stop on key press box available. Check it, too. The next time you print, TinyTERM will hold the print job in memory until you press a key. Then the print job will go to the printer with the correct pagination.

TinyTERM 4.13 and higher
In TinyTERM’s Printer Setup, check the Spool print jobs box. This will make two options available: Print on key press and Print on timeout. Print on key press works the same way Stop on key press does in earlier versions of TinyTERM.

Print on timeout (not available in TinyTERM 4.13) includes a timeout setting, which defaults to five seconds. If you have this option selected, TinyTERM will hold the job until the specified number of seconds go by with no new print data. Then it will release the job all at once. You can adjust the timeout based on how the print job behaves.

CR 21, spool option
CR 145, spool timeout