gm@romeo.cs.duke.edu (Greg McGary) (01/10/89)
I am using an HP LJ-II connected via a parallel port to a PC-AT clone
(Hyundai 286c) for printing TeX using Beebe's DVIJEP driver. I have
nothing but praise for the print quality and speed, but I have a major
gripe with the PC/printer's behavior in the face of (infrequent)
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'm used to working with Apple LW & Imagens on big UNIX boxes that
place a job in suspended animation indefinitely until such problems are
cleared, then resume where they had left off.
I normally use the MKS-toolkit cp(1) command like so:
cp <jobname>.jep /dev/lpt1
I've tried DOS's print spooler with no luck, and find that
cat <jobname>.jep >/dev/lpt1
opens one or both of the files in ascii-mode so that the top-bit
is stripped. (Boo!)
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.
Any ideas? Thanks!
-- Greg McGary
-- 4201 University Drive #102, Durham, NC 27707 (919) 490-6037
-- {decvax,hplabs,seismo,mcnc}!duke!gm
-- gm@cs.duke.edujwright@atanasoff.cs.iastate.edu (Jim Wright) (01/11/89)
In article <13017@duke.cs.duke.edu> gm@romeo.cs.duke.edu (Greg McGary) writes: }I normally use the MKS-toolkit cp(1) command like so: } } cp <jobname>.jep /dev/lpt1 } }I've tried DOS's print spooler with no luck, and find that } } cat <jobname>.jep >/dev/lpt1 } }opens one or both of the files in ascii-mode so that the top-bit }is stripped. (Boo!) } }Any ideas? Thanks! I use a batch file called TEXPRINT.BAT with the single line: copy /B %1.hp prn: For your DVI files, change .hp to .jep. This works exactly like you want it to. The switch /B tells DOS to use binary mode.
wnp@dcs.UUCP (Wolf N. Paul) (01/11/89)
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
cww@ndmath.UUCP (Clarence W. Wilkerson) (01/12/89)
The syntax is something like "mode lpt1: ,,P "