Xref: utzoo comp.sys.ibm.pc:23064 comp.text:3045
Path: utzoo!attcan!utgpu!watmath!clyde!att!osu-cis!killer!dcs!wnp
From: wnp@dcs.UUCP (Wolf N. Paul)
Newsgroups: comp.sys.ibm.pc,comp.text
Subject: Re: HP LJ-II printjob bombs from DOS after paper-out or paper-jam
Message-ID: <295@dcs.UUCP>
Date: 11 Jan 89 05:49:17 GMT
References: <13017@duke.cs.duke.edu>
Reply-To: wnp@dcs.UUCP (Wolf N. Paul)
Organization: DCS, Dallas, Texas
Lines: 28

In article <13017@duke.cs.duke.edu> gm@romeo.cs.duke.edu (Greg McGary) writes:
 >I am using an HP LJ-II connected via a parallel port to a PC-AT clone
 > ...
 >paper-jams and out-of-paper conditions: if new paper isn't added, or
 >the jam cleared within about 20 seconds, the job aborts in the middle!
 >
 >I normally use the MKS-toolkit cp(1) command like so:
 > ...
 >I've tried DOS's print spooler with no luck, and find that
 > ...
 >When cp(1) bombs after paper-out or paper-jam, I get a message on my 
 >console indicating that DOS knows what's going on with the printer.
 >It will say something like: `write failed: no paper' which leads me
 >to believe that a command written specifically for printing could be
 >smart enough to retry writes that fail on `repairable' conditions.
 
You need to tell DOS to retry writing on the printer port. The command
is something like,

  mode lpt1:,,P

(see under the "MODE" command description in your DOS manual. The two
commas are placeholders for line length and line spacing values used only
from BASIC and only if you have an IBM printer.
-- 
Wolf N. Paul * 3387 Sam Rayburn Run * Carrollton TX 75007 * (214) 306-9101
UUCP:     killer!dcs!wnp                 ESL: 62832882
DOMAIN:   dcs!wnp@killer.dallas.tx.us    TLX: 910-380-0585 EES PLANO UD