OS/2 port of CUPS
Paul Smedley
paul at smedley.info
Fri Nov 10 14:46:12 PST 2006
Hi Mike,
Michael Sweet wrote:
> Paul Smedley wrote:
>> ...
>>> Binary vs. text mode on the stdin/stdout pipes?
>>
>> That was my first guess too - however it doesn't seem to make any
>> difference. What mode should the stdin/out pipes be? OS/2 will
>> default to ascii.
>
> They *must* be binary.
OK made the necessary changes - unfortunately doesn't help my problem.
>
>> Is there a way I can check the output of imagetoraster to see that
>> the raster generated is valid?
>
> Yes, you can run imagetoraster to produce a raster image and use my
> RasterView program (http://www.easysw.com/~mike/rasterview/) to look
> at the results.
OK the .ras is also correct coming out of imagetoraster.
I'm been mucking around some more with pstoraster. TO grab to debug
output, I appended 2>debug to the command line run.
The log is at http://smedley.info/debug - it dies with:
Unexpected interpreter error -12.
Error object: (f80)op(0)0x221cb3
Operand stack at 0x8f23d0:
0x8e69b4: 0x03 file --S-rx--- 0x0001 0x008d6fb0
0x8e69bc: 0x03 file --S-rx--- 0x0001 0x008d6fb0
0x8e69c4: 0x12 str --Gwrx--- 0x0004 0x009acc9d = %!
Any ideas?
Of course if I run 'pstops 1 2 3 4 5 testprint.ps | pstoraster 1 2 3 4 5
- >output.ras' from a command line I get good raster output :/
Thanks for your help,
Paul.
More information about the cups
mailing list