At 08:26 PM 2/5/00 -0700, John Starkey wrote [in part]:
>> > WinPrinter???
>>
>> pbm2ppa isn't a device driver in the sense that it operates the IO
>> interface for the device. It simply takes the pbm format data from gs
>> and rearranges it to a ppa form that we hope the printer will like.
>
>Ok. But does it have to be anywhere special to work???
The script or command line that is calling it needs to be able to find it.
You are piping to it, right? (Yes, I confirmed that by looking at the script
example quoted below.) So as long as it is in the exceutables PATH, you are
OK. If it isn't, specify the full path to it in the command-line call. In
the script version that one of us (Richard? this thread is getting tangled
...) suggested, you probablt need to put the full path to pbm2ppa on the line.
>> cat >/usr/local/bin/printest
>> #!/bin/sh
>> cat $1 | gs -sDEVICE=pbmraw -q -dNOPAUSE -r600 -sOutputFile=- | \
>> pbm2ppa - - > dev/lp1
>> echo "high their" >/dev/lp1
>>
>> I doubt it'll print right, but at least if we don't get "no such
>> device" we are making progress.
>
>Still didn't work but there was no response from the "high their" command.
>So we've made progress???
Alas, no. If I recall correctly, part of what makes ppa the true technology
from hell for Linux users is these junky printers will not accept plain
ascii -- they ONLY speak ppa -- so an "echo" test won't work. N
The introduction of ppp was not HP's proudest moment. Read up at the picante
printer site I'm sure I mentioned in an earlier posting.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
Palo Alto, CA [EMAIL PROTECTED]
----------------------------------------------------------------
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.linux-learn.org/faqs
