Printable Version of Topic

Posted by: cssw@voicenet.com Jul 10 2001, 10:50 AM

I'm getting the message

pmprint spooler queue processor

job id 5 on hp 8550n color net

invalid spool file format. check your printer destination

configurate printer specific format setting and resubmit

your job (PMV6019)

processing will continue.

This only happens on a large image file
even if I only request to print out a very small area.

What is wrong, I can print other images
to the printer from the same computer.

Posted by: Peter Jul 10 2001, 12:51 PM

This sure sounds like a printer driver bug!

How big is the file?

A workaround would of course be to first use transform->size in PMView to downscale the image before printing it...



------------------
Peter Nielsen (peter@pmview.com) "If you can dream it, you can do it" JFK.

Posted by: cssw@voicenet.com Jul 10 2001, 01:33 PM

Because I was getting the error first on trying to print "fit pixels" which
fit on one page, and was getting the above error, I then started to print
The image (which is 4700 x 6412), however I'm only requesting to fit it into a 2.00inch x 2.62inch part of it.

I've also been seeing after requesting pmview to print
"jobs printed directly - spooler disabled"

Posted by: Peter Jul 11 2001, 09:29 PM

I just downloaded the latest HP 8550 printer driver from http://service5.boulder.ibm.com/2bcprod.nsf and installed in on Warp4/FP12 (=standard Warp 4 with older fixpak, i.e no high memory support) and Warp3/FP43 (=Warp 4 advanced server SMP with both HMS and SMP support).

I put the printer on "Hold". Printing a 4700x6412 24 bit full color image works flawlessly here. The printed file correctly appears in the printer object. Everything seems to work correctly in both Warp installations.

Obviously something is not right with your OS/2 setup since it works fine here in two very different OS/2 setups...


------------------
Peter Nielsen (peter@pmview.com) "If you can dream it, you can do it" JFK.

Posted by: Peter Jul 11 2001, 09:31 PM

BTW, I remember hearing about an odd problem like this occuring when there are no local (=non-network) printers installed. Try installing a "dummy" local printer object and see if that helps...

------------------
Peter Nielsen (peter@pmview.com) "If you can dream it, you can do it" JFK.

[This message has been edited by Peter (edited July 13, 2001).]