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

This entry was posted on Thursday, March 15th, 2007 at 2:02 pm and is filed under Transparent. You can follow any responses to this entry through the RSS 2.0 feed. Both comments and pings are currently closed.