We have a old Perl program that has been around for a decade or so. It originally lived on a Solaris 8 Unix system. In 2008 it was ported to run on a Windows 2003 server.
One function of this program automatically prints a text file to a network printer. The challenge being that the output to the printer needs to be landscape, duplex, edge-to-edge, and scaled to fit 11x8.5 paper. It took quite a bit of work, but in 2008 we got it done.
Here is the code in the Perl program.
use Win32::Printer::Direct; ... $v_error = Printfile("\\\\hardcopy\\pur", $printfile);
This year a new printer is being brought online. Changing the above line to the new printer loses all the print configuration. Nothing we do to configure the printer has an affect on the output produced by the new printer. $v_error = Printfile("\\\\hardcopy\\pml_pur_1", $printfile);
What we can not figure out is how the first printer is working. Looking at the print driver on the win 2003 server, the print server or the printer itself and none of them are setup to produce output in landscape, duplexed, edge-to-edge and scaled to fit.
How could the Perl code possibly be connecting to the //hadcopy/pur printer through the Win32::Printer module? Where could that configuration information be hidden?
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |