🚀 go-pugleaf

Pau.Clayton@adl.clw.CSIRO.AU (Paul Clayton) wrote:

>For several months I have been printing in duplex mode to a HP LJ5M 
>postscript printer.  Recently it stopped and I'm unable to get duplex mode 
>back - all printout is standard single-sided.  The problem is common to 
>several PCs (Wkgrps 3.11 and Win95) and a Mac which share the networked 
>printer.  There are no error messages or other indications of abnormality.
>
>The story so far:
>1.  Duplexing stopped, but initially I thought that I'd just disabled the     
>    setting in the printer configuration.  Actually I hadn't.
>2.  I reinstalled the printer under Win 95 and Wkgrps 3.11 (I have 2 PCs), but 
>    the problem persisted.
>3.  I then thought that the duplexing unit could be faulty.  It tests OK     
>    and duplexing works if pre-selected via control panel of printer.  I can't 
>    leave the printer in that mode as not all printout is wanted as double 
>    sided.
>4.  If the printer is set to PCL or auto-recognise and the PCL driver         
>    installed on both the Win95 and Win3.1 PCs, duplexing works.  This is not 
>    really a fix as auto-detect sometimes fails tp properly detect postscript 
>    jobs and prints, rather than interprets the print stream.  Other   
>    applications expect Postscript.
>5.  By printing a test job for both duplex and simplex to files and comparing 
>    them, the select duplex/simplex Postscript commands can be identified -   
>    the printer just ignores the duplex instruction.
>6.  Under heavy use by several users there doesn't seem to be any other     
>    feature which is not working properly on the printer - just the ignoring 
>    of the software selected duplex option.
>
>Can any HP or Postscript wizzes cast some light on this and suggest a fix.  
>(the support call to HP is still "open" - no help there).
>

Just a guess, but most all postscript drivers require a "UNIDRIVER".
That is, a Driver that is common among all Postscript devices. 

I would suspect that this has been recently replaced/updated by a
printer driver installation, and has broken your duplexing. Track down
the "POSTSCRIPT" drivers, remove them and re-install the original
ones. If you know where they came from that is.
  __   __   _______________________________
 //)) //)) | Richard RUDEK. MicroDek.      | 
//\\ //\\  | Chatswood, Sydney. Australia. | 
           `-------------------------------'