Re: [Dorset] CUPS same printer multiple drivers
Hi Ralph On 31/10/15 00:44, Ralph Corderoy wrote: Hi Tim, Setting up a raw queue overcomes this. Another option I've seen is uncommenting "application/octet-stream" in CUPS's mime.types and mime.convs. This apparently lets the raw data from Windows through to the printer? Yes that's true, but Windows won't see that as a raw printer but as a cups PS printer as defined by the PPD file in /etc/cups/ppd. "application/octet-stream" seems to be enabled by default in recent CUPS releases. So the question is, can I have a raw and a non-raw version of the same printer? I've found quote a few independent pages on the Internet suggesting doing just that; multiple queues for the same printer. Found only one, very old, post that suggests jobs on different queues, same device, crash into one another. I don't think just setting up separate printer queues cuts it, as I would think that has the potential for jobs getting garbled at the backend. I guess CUPS multiplexes whole print jobs onto the backends per device? https://wiki.debian.org/PrintQueuesCUPS Several queues can point to the same physical device, the printer, #cups on freenode thought the job in process on one queue would make the device appear locked from use on the other. I don't know what method of locking that is, could well vary per type of device, e.g. locking the device file for a parallel printer. I think the way to do this is set up queue-1 for the printer in the standard way, and then queue-2 as a raw printer, but printing to cups printer on queue-1. The "application/octet-stream" on queue-1 will let the raw data straight through, and queue-2 hides the ppd from Windows. For the moment I've gone back to cupsaddsmb and Samba. Much of the issues appear to be permissions differences between different versions of Windows. Cheers Tim -- Next meeting: Bournemouth, Tuesday, 2015-11-03 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
Re: [Dorset] CUPS same printer multiple drivers
Hi Tim, > Setting up a raw queue overcomes this. Another option I've seen is uncommenting "application/octet-stream" in CUPS's mime.types and mime.convs. This apparently lets the raw data from Windows through to the printer? > So the question is, can I have a raw and a non-raw version of the same > printer? I've found quote a few independent pages on the Internet suggesting doing just that; multiple queues for the same printer. Found only one, very old, post that suggests jobs on different queues, same device, crash into one another. > I don't think just setting up separate printer queues cuts it, as I > would think that has the potential for jobs getting garbled at the > backend. I guess CUPS multiplexes whole print jobs onto the backends per device? https://wiki.debian.org/PrintQueuesCUPS Several queues can point to the same physical device, the printer, #cups on freenode thought the job in process on one queue would make the device appear locked from use on the other. I don't know what method of locking that is, could well vary per type of device, e.g. locking the device file for a parallel printer. Cheers, Ralph. -- Next meeting: Bournemouth, Tuesday, 2015-11-03 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
[Dorset] CUPS same printer multiple drivers
Hi I have a CUPS server in a mixed Linux/Windows environment. In the past I have used Samba and cupsaddsmb to have the CUPS/Samba server provide drivers to Windows clients. In recent years all sorts of weirdness has crept into this setup (peculiar page sizes in Windows, unable to change page size preferences etc) so decided to move to IPP (http://cupsserver:631/printers/printername). However, it looks like I need to set up raw queues for the Windows machines to use, otherwise for some printers there appears to be a mismatch in what CUPS advertises as printer characteristics and what Windows thinks they should be (this occurs for older printers where Windows has its own drivers - it simply refuses to connect to the IPP printer at the Add Printer stage). Setting up a raw queue overcomes this. So the question is, can I have a raw and a non-raw version of the same printer? I don't think just setting up separate printer queues cuts it, as I would think that has the potential for jobs getting garbled at the backend. Cheers Tim -- Next meeting: Bournemouth, Tuesday, 2015-11-03 20:00 Meets, Mailing list, IRC, LinkedIn, ... http://dorset.lug.org.uk/ New thread: mailto:dorset@mailman.lug.org.uk / CHECK IF YOU'RE REPLYING Reporting bugs well: http://goo.gl/4Xue / TO THE LIST OR THE AUTHOR
