Windows 8 + CUPS 1.4.4 + PostScript

[Steven Hunter]

We have a CUPS 1.4.4 server running on Ubuntu. We've had no real
problems with Windows clients (XP, Vista, and 7) until people started
showing up with Windows 8 laptops wanting to connect to our printers.

If we configure the queue using using the Windows 8 provided PCL driver,
it works fine. However if we use the postscript driver then we get the
raw postscript code printed as text. The printer I am testing with is a
LJ3800, but we have seen this behavior with both a 4650 and 8150 as
well. For now we're using the PCL driver as a work-around but there are
some printers for which the PS driver is preferred and there's no reason
I can see why it shouldn't work.

Neither I nor our Linux admin can figure why. Does anyone have any
suggestions or pointers?

Thanks in advance.

[Michael Sweet]

Steven,

Post by Steven Hunter
We have a CUPS 1.4.4 server running on Ubuntu. We've had no real
problems with Windows clients (XP, Vista, and 7) until people started
showing up with Windows 8 laptops wanting to connect to our printers.

Are you printing through Samba or ???

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair

[Steven Hunter]

Post by Michael Sweet
Steven,

Post by Steven Hunter
We have a CUPS 1.4.4 server running on Ubuntu. We've had no real
problems with Windows clients (XP, Vista, and 7) until people started
showing up with Windows 8 laptops wanting to connect to our printers.

Are you printing through Samba or ???

We're printing directly to the CUPS queue using IPP over HTTP. In turn
the queues use the JetDirect port on the printers.

[Michael Sweet]

Steven,

Post by Steven Hunter

Post by Michael Sweet
...
Are you printing through Samba or ???

We're printing directly to the CUPS queue using IPP over HTTP. In turn
the queues use the JetDirect port on the printers.

Well, more than likely the issue is that the PS output from Windows cannot be auto-detected by the current rules. Run CUPS with debug logging enabled ("cupsctl --debug-logging" on the server) and then watch the /var/log/cups/error_log file when you submit a job from Windows 8.

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair

[Steven Hunter]

On 2/1/2013 4:49 PM, Michael Sweet wrote:

<snip>

Post by Michael Sweet
Well, more than likely the issue is that the PS output from Windows
cannot be auto-detected by the current rules. Run CUPS with debug
logging enabled ("cupsctl --debug-logging" on the server) and then
watch the /var/log/cups/error_log file when you submit a job from
Windows 8.

@PJL SET STRINGCODESET=UTF8
@PJL SET RESOLUTION=600
@PJL ENTER LANGUAGE=POSTSCRIPT

Apparently the filter was looking for the "^[%-12345X" which is omitted
by Windows 8. We've added appropriate filters that detect the Win8 jobs now.

Thanks for your help!

[Paul Conklin]

You may also temporarily want to turn on the FileDevice Directive and make sure that you don't have a hodgepodge of PJL ENTER LANGUAGE = PCL and PostScript commands

another option is the personality on the printer is set to PCL and not AUTO

last but not least, make sure the printer even supports PostScript

Post by Michael Sweet
Steven,

Post by Steven Hunter

Post by Michael Sweet
...
Are you printing through Samba or ???

We're printing directly to the CUPS queue using IPP over HTTP. In turn
the queues use the JetDirect port on the printers.

Well, more than likely the issue is that the PS output from Windows cannot be auto-detected by the current rules. Run CUPS with debug logging enabled ("cupsctl --debug-logging" on the server) and then watch the /var/log/cups/error_log file when you submit a job from Windows 8.
_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair

[Benn]

Just wanted to chime in to say I've noticed the same thing on our CUPS server
when Windows 8 is configured to print using IPP with Postscript drivers. PCL
ones work.

Our CUPS server is running version 1.5.3.

[Steven Hunter]

application/postscript ai eps ps string(0,%!) string(0,<04>%!) \
contains(0,4096,<0a>%!PS-Adobe)) \
contains(0,128,<1B>%-12345X) + \
(contains(0,4096,"LANGUAGE=POSTSCRIPT") \
contains(0,4096,"LANGUAGE = Postscript") \
contains(0,4096,"LANGUAGE = PostScript") \
contains(0,4096,"LANGUAGE = POSTSCRIPT") \
(contains(0,4096,<0a>%!) + \
!contains(0,4096,"ENTER LANGUAGE")))
The second and third lines were the lines that we inserted into the original
filter that match Windows 8 Postscript jobs.