I didn't _fix_ the problem. but I THINK I have it isolated.
If someone created a PDF from an image file using like a tiff file and LZW
compression. The file is being forwarded and causing the printjob to take
forever to print.

I wrote a script that looks for the LZWDecode in the spool file and kicks
off the printjob and replaces it with an error message if it finds it.

It acts as a samba printer so LPRng doesn't even get to see it unless it
passes the test.

Unfortunately people won't be able to print some documents until I find a
better solution.

I THINK this makes some sense as to what the problem actually is though.
If anyone else has any better suggestions I am still open to suggestions,
because i would LIKE these people to be able to print these documents, but
it has to be in a reasonable amount of time.

Sean

On Thu, 29 Jan 2004, Sean O'Malley wrote:

>
>
> On Wed, 28 Jan 2004, Matt Forrest wrote:
>
> > I'm not at a location where I can test those files right now, but I'll
> > try them when I can.
>
> That would be appreciated!
>
> > Take a look at the df* files in the queue directory.  You should have a
> > line something like this.  If it isn't version 5.2, upgrade the drivers on
> > the windows machines!  We've had similar problems with our 8150 and they
> > happen less with the 5.2 version.
> >
> > %%Creator: PScript5.dll Version 5.2
> from the dfA file
> %%Creator: PScript5.dll Version 5.2^M
>
> I don't think this is the problem. I think the problem is the _original_
> postscript driver used to create the questionable pdf's may have been <5.2
> driver.
>
> I have a feeling CUPS on OS X is doing some sort of filtering to
> straighten out the job before it goes to print. That is my only
> explanation of why the job prints faster on OS X (3 vs 30 min) because
> windows isn't printing the pdf I created on the Mac any faster then it was
> the original pdf.
>
> I just wish I knew what it was...
>
> Sean
>
>
>
> -----------------------------------------------------------------------------
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from MUST be your subscription address
>
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
> to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
> with:                           | example:
> subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]
>
> If you have major problems,  send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------
>


-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to