Print Job Becomes Huge

[thefourthwall]

Hello,

An end user here has a 1.69MB .png file that he opens with the Picture and Fax Viewer app in XP Pro.

When he prints that file using either pcl or postscript drivers, the resulting print job balloons to 192MB, slowing the PC down unacceptably.

Seems that its the application rendering the print job to such enormous sizes, but we're stumped as to how to resolve.

Any thoughts?

Thanks,
thefourthwall

 

[chipk]

Try disabling Advanced Printer Features and see if you get the same result:

Click Start, and then click Printers and Faxes.
Right-click the printer that you are printing to, and then click Properties.
Click the Advanced tab, clear the Enable advanced printing features check box, and then click OK.

 

[directlyconnected]

What are you printing to? Are there options in the driver to rasterize locally on the printer, and if so, do you have enough RAM in the printer? If not, it's pretty cheap on Ebay.

Tim

 

[thefourthwall]

Both good options to explore. I just got back to the office and am running a test on chipk's idea of disabling advanced printer features. Tim, the print device is a xerox MFP with 256MB of ram installed.

Wondering if, given that the spooler file balloons to 192MB regardless of where its printed to, if its a printer driver issue. We've setup a test print queue with xerox's current PS and Microsoft's certified PCL drivers. Will update with the results. Thanks again for your input.

-thefourthwall

 

[thefourthwall]

Problem Resolved, and thanks chipk and Tim for your input.

This was a case of "not knowing what I didn't know"

The user insisted that the graphics file was only 1.69MB and "gee, what could be the problem?"

Using Photoshop revealed that the file, when opened, uncompresses to 192MB and has a resolution of approximately 10000x6600 pixels and a canvas size of like 35x25 inches at 300dpi.

The user is creating this file and not using the appropriate tools to edit/manipulate the image (or he doesn't know how to properly create the output).

Anyway, thanks guys, for your help!

-thefourthwall

 

[directlyconnected]

Good thing, because I actually never ran across that---you had me worried!