Printfil allows printing to Windows printers, from Dos, Windows programs or Unix, Linux, legacy applications running on a Windows PC via telnet or other terminal emulator software.
You can set your application to print to an ascii file, or you can let
Printfil automatically Capture one or more Parallel port (even from LPT1: to LPT9: simultaneously), and redirect your DOS print jobs to any Windows printer, including USB, GDI, IP network printers, fax printers and PDF writers, even if a printer is physically connected to the captured port or no LPT ports are physically installed, on any machine running Windows 95, 98, ME, NT, 2000, XP, 2003, Vista, Windows 7, 2008, including Terminal Server environments and Linux via Wine.
What's new:
* On Windows Terminal Servers now you can choose to ignore the user's session contained in the printer's name, making the printer's list consistent Between different sessions. For example, instead of selecting "HP LaserJet (from REMOTE-PC) in session 1" as Default printer for
Printfil, you can simply select "HP LaserJet (from REMOTE-PC)" and avoid using the "Choose printer" option that requires an additional click for each captured print job. Please find out more in the article How to make DOS programs on Terminal Server printing to local or remote Windows printers
* Added SSL authentication when emailing print jobs as PDF files (and support requests) via SMTP directly (without using Outlook or a MAPI mail client). This feature requires Windows 2000 or higher (it's not available in Windows 9x)
*
Printfil now detects if it's running on a 64 bit Windows system, and, if it's setup to capture an LPT port, it points the user to the FAQ suggesting which is the best
Printfil configuration on 64 bit systems
* If a source program does Create its print jobs without closing the printing device at the end of the process,
Printfil was used to show a "Error 5 - File locked by an external program" alert on screen.
