[cups.general] Win2K printing (yes I RTFMed :)

[Jeff Hardy]

On Mon, 2005-02-21 at 16:05 -0500, Robert Brockway wrote:
> On Mon, 21 Feb 2005, Robert Brockway wrote:
> 
> > Hi all.  I've RTFMed on this topic and tried various suggestions but still
> > have a problem.
> 
> After some more digging (and the light of day) I think I may have it:
> 
> d [20/Feb/2005:23:52:51 -0500] print_job(0x40200008[3],
> http://cups.local.domain.com:631/printers/MFC210C)
> D [20/Feb/2005:23:52:51 -0500] print_job: auto-typing file...
> E [20/Feb/2005:23:52:51 -0500] print_job: Unsupported format
> 'application/octet-stream'!

This looks like you do not have raw printing enabled.  At the bottom of
your mime.types and mime.convs files in your cups config directory
(usually /etc/cups) you'll find some more info.  Named, uncomment the
lines:

application/octet-stream


application/octet-stream        application/vnd.cups-raw        0
-

in mime.types and mime.convs respectively.  Basically your windows
clients are sending raw data that the cups filter chain is not set to
understand and this tells it to pass it on.


> d [20/Feb/2005:23:52:51 -0500] send_ipp_error(0x40200008[3], 40a)
> D [20/Feb/2005:23:52:51 -0500] Sending error:
> client-error-document-format-not-supported
> d [20/Feb/2005:23:52:51 -0500] WriteClient: Removing fd 3 from
> OutputSet...
> d [20/Feb/2005:23:52:51 -0500] WriteClient: 3 Removing temp file
> /var/spool/cups/00000000
> 
> no, local.domain.com is not really the local domain ;)
> 
> So it is making it into the spool directory and then failing with
> "unsupported format".
> 
> This was a Win2K test page.
> 
> So It's looking like the 22K client driver to me.  I'll try with a
> postscript driver I saw mentioned.
> 
> Rob
> 
-- 
Jeff Hardy
Systems Analyst
hardyjm at potsdam dot edu