problem with pcl duplex printing
in [General Linux]
|
From: hehehe on 21 Apr 2010 05:32 Hello! I have strange problem when i print ps file in duplex by command lpr my priter works fine(print double side) but when i convert by ghostscript using ljet4d driver my document and then i print by lpr my printer inform me that printing will be duplex but its print in simplex...? what can be a problem?
From: The Natural Philosopher on 21 Apr 2010 06:18 hehehe wrote: > Hello! > > I have strange problem when i print ps file in duplex by command lpr > my priter works fine(print double side) but when i convert by > ghostscript using ljet4d driver my document and then i print by lpr my > printer inform me that printing will be duplex but its print in simplex...? > > what can be a problem? I had this. I manually edited a PPD file I think. Somewhere there is an entry for the printer that links selectable options to command codes. In my case although the printer announced itself as duplex and accepted the command, the entry for simplex and duplex was the same. Ok. Ive had a look, and on this particular printer (Ricoh 3800) teher is a file in /etc/cups/ppd that contains this *OpenUI *Duplex/Double-Sided Printing: PickOne *FoomaticRIPOption Duplex: enum CmdLine A *OrderDependency: 120 AnySetup *Duplex *DefaultDuplex: None *Duplex DuplexNoTumble/Long Edge (Standard): "%% FoomaticRIPOptionSetting: Duplex=DuplexNoTumble" *FoomaticRIPOptionSetting Duplex=DuplexNoTumble: " -dDuplex=true -dTum&& ble=false" *End *Duplex DuplexTumble/Short Edge (Flip): "%% FoomaticRIPOptionSetting: Duplex=DuplexTumble" *FoomaticRIPOptionSetting Duplex=DuplexTumble: " -dDuplex=true -dTumbl&& e=true" *End *Duplex None/Off: "%% FoomaticRIPOptionSetting: Duplex=None" *FoomaticRIPOptionSetting Duplex=None: " -dDuplex=false" *CloseUI: *Duplex ISTR that I have edited this section...to make it work
From: hehehe on 21 Apr 2010 15:56 Użytkownik "The Natural Philosopher" <tnp(a)invalid.invalid> napisał w wiadomości news:hqmjei$qlk$1(a)news.albasani.net... > hehehe wrote: >> Hello! >> >> I have strange problem when i print ps file in duplex by command lpr my >> priter works fine(print double side) but when i convert by ghostscript >> using ljet4d driver my document and then i print by lpr my printer inform >> me that printing will be duplex but its print in simplex...? >> >> what can be a problem? > > I had this. I manually edited a PPD file I think. Somewhere there is an > entry for the printer that links selectable options to command codes. In > my case although the printer announced itself as duplex and accepted the > command, the entry for simplex and duplex was the same. > > Ok. Ive had a look, and on this particular printer (Ricoh 3800) teher is a > file in /etc/cups/ppd that contains this > > *OpenUI *Duplex/Double-Sided Printing: PickOne > *FoomaticRIPOption Duplex: enum CmdLine A > *OrderDependency: 120 AnySetup *Duplex > *DefaultDuplex: None > *Duplex DuplexNoTumble/Long Edge (Standard): "%% FoomaticRIPOptionSetting: > Duplex=DuplexNoTumble" > *FoomaticRIPOptionSetting Duplex=DuplexNoTumble: " -dDuplex=true -dTum&& > ble=false" > *End > *Duplex DuplexTumble/Short Edge (Flip): "%% FoomaticRIPOptionSetting: > Duplex=DuplexTumble" > *FoomaticRIPOptionSetting Duplex=DuplexTumble: " -dDuplex=true -dTumbl&& > e=true" > *End > *Duplex None/Off: "%% FoomaticRIPOptionSetting: Duplex=None" > *FoomaticRIPOptionSetting Duplex=None: " -dDuplex=false" > *CloseUI: *Duplex > > ISTR that I have edited this section...to make it work > th
From: hehehe on 21 Apr 2010 15:57 thx for respond .. but not work. Those line you gave me from ppd this is commands for ghostscript but in my 8.15 version dDuplex i not available ....
From: The Natural Philosopher on 21 Apr 2010 19:24 hehehe wrote: > thx for respond .. but not work. Those line you gave me from ppd this is > commands for ghostscript but in my 8.15 version dDuplex i not available > .... I dont think they are commands for ghostcript..I think they are commands to apply to lp.
|
Pages: 1 Prev: problem with pcl duplex printing Next: Eight tasks, eight CPUs ... this shouldn't be hard |