HP3000-L Archives

October 1995, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Jeff Kell <[log in to unmask]>
Reply To:
Jeff Kell <[log in to unmask]>
Date:
Wed, 25 Oct 1995 23:38:29 EDT
Content-Type:
text/plain
Parts/Attachments:
text/plain (31 lines)
On Thu, 26 Oct 1995 07:50:26 +1000 Jim Wowchuk said:
>At 04:56 PM 25/10/95 +0200, SoftLink wrote:
>>FILE t;dev=lp;rec=128,1,b
>                         ^ you've specified a byte stream, not binary
>:file t;dev=lp;rec=128,1,f,binary
 
In this, and in another suggestion or two, we're missing the point.  He has
a raw binary PCL file to send to a printer.  Every HP utility that I know
of (print/fcopy/etc) will do a record-oriented transfer.  In such cases,
even with binary designations, each record will be written followed by at
least a carriage return/linefeed - and this <cr><lf> will interrupt the PCL
data stream.
 
The only solution I know of is either third party, or else write your own
program which reads the input file on a record-by-record basis and then
writes it to the output device with a no-space (%320) carriage control.
 
I've never tried it, but one *possibility* might be to send the file to the
output device as if it were an environment file (which I think does indeed
do a binary transfer); so if you have file 'rawpcl' perhaps (just guessing)
you might be able to:
 
   :file out;dev=xx;env=rawpcl
   :fcopy from=;to=*out
   <either hit ctl-y or type :eod>
 
If this works, you owe me first round at SIGBAR at IPROF'96 :-)  If not,
you get what you pay for :-)
 
[\] Jeff Kell <[log in to unmask]>

ATOM RSS1 RSS2