I have an HP870Cse, which I'm sure you are all getting tired of hearing about. I have three queues set up for that printer, one at 300dpi greyscale (default), one at 600dpi greyscale, and one which is two up 300dpi greyscale (color cartidges are just too expensive, IMO). Each of these is set up in the GNOME Print Mangager for pre-rendering, since the postscript interpreter on that printer is S-L-O-W (like 30 minutes per page) while transferring a graphics image is acceptably fast (like 4 pages per minute).
But I find that only the first two actually honor the pre-rendering. If I print to TwoUp, then it does indeed print two pages side- by-side on the page, but it takes 30 minutes. If I use mpage, I get 4 pages per minute again.
Is anyone aware of why that would be or what I could do to correct that?
Also, I'd like to do some two-sided printing. This printer does not have a duplexer, so I've been investigating using mpage or psmandup for that. Does anyone have experience using these in this manner automatically by setting up the queue to use them directly?
Mike
On Wed, Feb 22, 2006 at 02:09:26PM -0600, Mike McCarty wrote:
I have an HP870Cse, which I'm sure you are all getting tired of hearing about. I have three queues set up for that printer, one at 300dpi greyscale (default), one at 600dpi greyscale, and one which is two up 300dpi greyscale (color cartidges are just too expensive, IMO). Each of these is set up in the GNOME Print Mangager for pre-rendering, since the postscript interpreter on that printer is S-L-O-W (like 30 minutes per page) while transferring a graphics image is acceptably fast (like 4 pages per minute).
I assume by the Gnome Print Manager you mean system-config-printer. This program just does not work properly in a CUPS environment. Set up your printer using the CUPS web interface and I think you will find the results will be more to your liking.
But I find that only the first two actually honor the pre-rendering. If I print to TwoUp, then it does indeed print two pages side- by-side on the page, but it takes 30 minutes. If I use mpage, I get 4 pages per minute again.
Is anyone aware of why that would be or what I could do to correct that?
Also, I'd like to do some two-sided printing. This printer does not have a duplexer, so I've been investigating using mpage or psmandup for that. Does anyone have experience using these in this manner automatically by setting up the queue to use them directly?
Mike
p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} This message made from 100% recycled bits. You have found the bank of Larn. I can explain it for you, but I can't understand it for you. I speak only for myself, and I am unanimous in that!
-- fedora-list mailing list fedora-list@redhat.com To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
akonstam@trinity.edu wrote:
On Wed, Feb 22, 2006 at 02:09:26PM -0600, Mike McCarty wrote:
I have an HP870Cse, which I'm sure you are all getting tired of hearing about. I have three queues set up for that printer, one at 300dpi greyscale (default), one at 600dpi greyscale, and one which is two up 300dpi greyscale (color cartidges are just too expensive, IMO). Each of these is set up in the GNOME Print Mangager for pre-rendering, since the postscript interpreter on that printer is S-L-O-W (like 30 minutes per page) while transferring a graphics image is acceptably fast (like 4 pages per minute).
I assume by the Gnome Print Manager you mean system-config-printer.
Yes, though I start it usually by clicking on the printer icon.
This program just does not work properly in a CUPS environment. Set up your printer using the CUPS web interface and I think you will find the results will be more to your liking.
Ok, thanks for the advice. Er, how do I enter the CUPS web interface?
Google turned up this...
Is this what you mean?
Mike
akonstam@trinity.edu wrote:
I assume by the Gnome Print Manager you mean system-config-printer. This program just does not work properly in a CUPS environment. Set up your printer using the CUPS web interface and I think you will find the results will be more to your liking.
Ok, I tried that, and it doesn't even have as many options as does the system-config-printer. In particular, it doesn't know anything about pre-rendering.
Mike
On Thursday 23 February 2006 15:36, Mike McCarty wrote:
akonstam@trinity.edu wrote:
I assume by the Gnome Print Manager you mean system-config-printer. This program just does not work properly in a CUPS environment. Set up your printer using the CUPS web interface and I think you will find the results will be more to your liking.
Ok, I tried that, and it doesn't even have as many options as does the system-config-printer. In particular, it doesn't know anything about pre-rendering.
Mike
It may not Mike, but what it does do, is right.
-- p="p=%c%s%c;main(){printf(p,34,p,34);}";main(){printf(p,34,p,34);} This message made from 100% recycled bits. You have found the bank of Larn. I can explain it for you, but I can't understand it for you. I speak only for myself, and I am unanimous in that!
Gene Heskett wrote:
On Thursday 23 February 2006 15:36, Mike McCarty wrote:
akonstam@trinity.edu wrote:
I assume by the Gnome Print Manager you mean system-config-printer. This program just does not work properly in a CUPS environment. Set up your printer using the CUPS web interface and I think you will find the results will be more to your liking.
Ok, I tried that, and it doesn't even have as many options as does the system-config-printer. In particular, it doesn't know anything about pre-rendering.
Mike
It may not Mike, but what it does do, is right.
Probably so. But it didn't change anything in the setup that I could find, except a few lines saying what tool did the setup. In fact, I can't find anything that "prerendering" changes in any of the files documented by CUPS, and I read every word of documentation I could find on my machine, which has the CUPS docu installed. I now know the layout of a .ppd file and could create one by hand, if I had to, not that I'd *want* to :-)
But I know it's somewhere.
The places I found it using Googls were all Red Hat related, so I guess it's a Red Hat thing, not a CUPS thing. Also, prerendering does not do what I thought (based on what I heard, that is) if the Red Hat documentation is correct. What the Red Hat docu says is the *unusual fonts* get prerendered (I guess to images) and then the postscript is massaged to make it all postscript level 1 (no 2 or 3), but the output is still postscript.
I know this: Turning "prerendering" on turned print jobs which took 30 minutes per page into jobs that took 0.25 minutes per page, but not for "two up" printing, and I still don't know why. I also know that the output from mpage does essentially the same thing, and also prints at 4 ppm when printed via my "non-two-up" 300dpi queue for that printer.
My guess is that it is behind CUPS where this is happening, in the back end. Maybe I'll have a look at the source for HPIJS and see what I can find.
Mike
On Thu, Feb 23, 2006 at 08:55:27PM -0600, Mike McCarty wrote:
The places I found it using Googls were all Red Hat related, so I guess it's a Red Hat thing, not a CUPS thing. Also, prerendering does not do what I thought (based on what I heard, that is) if the Red Hat documentation is correct.
It's actually a foomatic thing.
http://www.linuxprinting.org/execution.cgi?driver=Postscript&printer=Gen...
See 'PreFilter'.
Tim. */
Tim Waugh wrote:
On Thu, Feb 23, 2006 at 08:55:27PM -0600, Mike McCarty wrote:
The places I found it using Googls were all Red Hat related, so I guess it's a Red Hat thing, not a CUPS thing. Also, prerendering does not do what I thought (based on what I heard, that is) if the Red Hat documentation is correct.
It's actually a foomatic thing.
Ahh. (What's foomatic?)
http://www.linuxprinting.org/execution.cgi?driver=Postscript&printer=Gen...
See 'PreFilter'.
I certainly shall. And in the immortal words of Bilbo Baggins, "Thag you very buch."
Mike