Article View: comp.lang.postscript
Article #9289Postscript printer stopped duplexing
From: Paul Clayton
Date: Mon, 08 Sep 1997 00:00
Date: Mon, 08 Sep 1997 00:00
41 lines
2901 bytes
2901 bytes
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).
Thanks,
Paul
==============================================================
Paul Clayton Tel: +61-8-8303-8408
Urrbrae Fax: +61-8-8303-8550
South Australia
==============================================================
Technical Details
Message-ID:
<5uvtae$3bg_001@adl.soils.csiro.au>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 10d683,55bd29f0d3b55e5,start X-Google-Attributes: gid10d683,public X-Google-Thread: f62f2,55bd29f0d3b55e5,start X-Google-Attributes: gidf62f2,public X-Google-Thread: 104d8a,55bd29f0d3b55e5,start X-Google-Attributes: gid104d8a,public X-Google-Thread: 1020c6,55bd29f0d3b55e5,start X-Google-Attributes: gid1020c6,public X-Google-Thread: 10d053,55bd29f0d3b55e5,start X-Google-Attributes: gid10d053,public From: Pau.Clayton@adl.clw.CSIRO.AU (Paul Clayton) Subject: Postscript printer stopped duplexing Date: 1997/09/08 Message-ID: <5uvtae$3bg_001@adl.soils.csiro.au> X-Deja-AN: 271893746 Distribution: inet Organization: CSIRO Newsgroups: comp.lang.postscript,comp.unix.admin,comp.periphs.printers,aus.computers.sun,aus.computers.ibm-pc