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.

If your PC has more than one LPT (parallel) port, you can select any of them in TinyTERM. However, TinyTERM version 4.10 will not recognize the change until you save the session, then exit and restart TinyTERM.

There is no patch to fix this behavior. The only solution is to use a newer version of TinyTERM.

On Windows 95, 98 or Me, the currently active window can lose focus when the LPD server receives a print request. The server has to have focus briefly to initiate the print job, especially if it’s the first LPD request received since Windows was started, but it doesn’t always return focus properly.

When this happens, create a new icon in the Startup group of your Start menu. Link the to C:\Program Files\Century\TinyTERM\NetUtils\marlpd32.exe. Change the directory as appropriate, but make sure marlpd32.exe is loaded from your Startup group. That’s the application taking focus, so if it’s started with Windows, you shouldn’t see your main window lose focus again.

The LPD Server in Century Internet Services will sometimes hang when you add a printer. There is no patch for this. But you can just kill the process from Task Manager. The printer will still be added.

Century Internet Services includes an LPD (line printer daemon) server. However, it only runs on Windows 3.1 or higher. In TinyTERM 4.x, it only runs on Windows 95, 98 and Me.

To put a Century LPD Server on Windows NT 4, 2000, XP or Vista, you will need TinyTERM Plus 4.30 or higher. No prior release includes an LPD server.

CR 293

If you need to print to a Windows network printer from TinyTERM, but for whatever reason can’t select the printer, you can print directly to the device instead. Configure TinyTERM to print “Direct to device” or select DEVICE from the drop-down list. For the file or device name, enter:

\server\printer

Replace “server” with the name of the Windows print server. Replace “printer” with the share name for the desired printer. You may need to contact your system administrator to get those names. Most Windows network printers will accept this configuration.

For printers that will not, you may be able to capture the printer to an LPT port. Instructions for this are on Microsoft’s website. By operating system, the links are:

• Windows 95, 98 and Me
• Windows NT and 2000
• Windows XP, 2003 and Vista
  

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

TinyTERM version 4.x will sometimes bring up the Page Setup dialog when a data capture is started. If you OK the dialog, the capture goes to the printer instead of the specified file. If you Cancel the dialog, nothing is captured.

This is a bug in TinyTERM. It most often happens if you’re using a .tpx file that was opened after you started TinyTERM.

The only workaround is to exit TinyTERM, then double-click the .tpx file you want to use. While it is the only file open, try the data capture again. You may need to do this more than once. Changing the version of TinyTERM you have installed may also help.

CR 81, improved in TinyTERM 4.11
CR 501, fixed in TinyTERM 4.7.0

When printing a screen in TinyTERM 4.03, lines will sometimes print as odd characters instead. This is corrected with this patch, through the implementation of multiple code pages for printing. Installation instructions and documentation are in this document. TinyTERM versions 4.04-4.12 incorporate the patch.

The problem was reintroduced in TinyTERM 4.13 with the Use printer fonts option in the new Printer Setup dialog. The same thing happened printing direct to device. This was fixed in TinyTERM 4.21.

CR 318, fixed in TinyTERM 4.21
CR 429, not fixed in VT100
CR 584

When printing from TinyTERM 4.02 or higher to a Windows printer, you may need to save the settings for lines and columns so it will print correctly. On some versions, every time you exit TinyTERM it loses those settings.

To save those settings, place the attached script into your .tpx file with these steps:

1. Copy this script to the C:\Program Files\Century\TinyTERM directory.
2. Open the Session Properties and go to the Session tab.
3. Click the “Post Session Start” radio button.
4. Click the Browse button
5. Locate and select the st.cs script
6. Click OK and close the Session Properties.
7. From TinyTERM’s File menu select Printer Setup.
8. Configure printing to the desired Windows printer.
9. Click the Setup button to get the Page Setup dialog.
10. Set the lines and columns.
11. OK all settings, then save the .tpx file and exit TinyTERM.
12. Restart TinyTERM.

It should have the lines and columns settings saved. You may need to set them one more time, now that the script is running.

Lines and Columns options were permanently added to the Page Setup dialog in TinyTERM 4.30. From that version on, the st.cs script is never necessary.

CR 400