🚀 go-pugleaf

In article <1992Sep5.001106.24945@newstand.syr.edu> amichiel@rodan.acs.syr.edu (Allen J Michielsen) writes:
>
>In@usenet.ucs.indiana.edu> yawei@bronze.ucs.indiana.edu (~{QG9p~}) writes:
>>...
>>PRINT.EXE via the DOS multiplex interrupt calls so that it can
>>be printed in the background. Everything worked perfectly 
>>until some bytes with values 0x0D or 0x1B sneaked into the files.
>
>>It turned out that PRINT.EXE was only equiped to handle non-binary
>>files! (This was confirmed after checking the manuals.) An 
>
>I didn't see it my manuals either, but many dos level programs intended
>for text files, have a hidden (or poorly documented) /b switch for
>use with binary files.  Try print /b file.ext
>
>al
>--
>Al. Michielsen, Crouse Hinds School of Management, Syracuse University
> InterNet: amichiel@mailbox.syr.edu  amichiel@sunrise.acs.syr.edu
> Bitnet: AMICHIEL@SUNRISE 

My problem consisted in printing output of Word for Windows in a remote
printer (a HPLJ 3).  This is a binary file.
Print will expand tabs and other annoying and not wanted conversions.

My solution:
copy /b a:myfile lpt1:

I know this is not a spooler, but I was using the other PC and nobody
was on it, so that spooler was ne necessary.
And this works!

-- 
  \_\    Denis Beauregard  *  internet:beaurega@ireq.hydro.qc.ca
 /   \   Genealogiste officiel : Beauregard/Jarret/Jarest/Vincent
J   __>  Un Quebec renouvele dans une Amerique renovee
\_.-===                                                  Opinions ? Et pis non !