[cups.development] OS/2 port of CUPS

[Nick Bartolotti]

Do you know how far into the PS file the conversion got?  It's been a while since I put on my PS thinking cap but as I remember it %! is the start of a PS file.  If this was encountered within the file at an unexpected spot, my first thought is binary data is being mis-interpreted and causing the job loop to get confused and abort additional interpretation.
 
>From the log it looks like you might also have been in the middle of a font file or processing a font.  As I remember it Fonts also start with %!.
 
Lastly, not DSC means the PS file does not conform to the Document Structuring Convention so it's possible the PS program breaks some of the rules set forth by DSC.  This is not uncommon for hand-cranked PS or PS from older programs that don't use a driver per-se.
 
Maybe this will lend a clue.
 
 

________________________________

From: cups-dev-bounces at easysw.com on behalf of Paul Smedley
Sent: Sun 11/12/2006 4:42 AM
To: cups-dev at easysw.com
Subject: Re: [cups.development] OS/2 port of CUPS



Paul Smedley wrote:
> Paul Smedley wrote:
>> Michael Sweet wrote:
>>> Paul Smedley wrote:
>>>> ...
>>>> 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?
>>>
>>> No clue.  ESP Ghostscript has only been tested on UNIX/Linux.
>>>
>> OK I'm sure I'll work it out eventually.  Can you help with syntax for
>> the various programs in order to test from the command line? ie
>> rastertohp & lpd?  Some of the options are straightforward, others not
>> so.  ie how to tell lpd which printer to print to?
>
> OK I worked out how to drive rastertohp from the command line - and
> checked the pcl output with a PCL viewer and it's OK.
>
> What about lpd?
>
> I know to set the environment variable: DEVICE_URi=lpd://192.168.1.253
> but when I call:
> lpd 127 psmedley dilbert 1 options=any output.pcl
> I get:
> ERROR: Unable to reserve port: Invalid argument
>
> So obviously I'm missing something...

OK I found the missing link in lpd.exe and printing images (ie lpr -P
ljet image.jpg -o fitplot) works perfectly.... now to diagnose my
pstoraster problems!

Cheers,

Paul.
_______________________________________________
cups-dev mailing list
cups-dev at easysw.com
http://lists.easysw.com/mailman/listinfo/cups-dev


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.cups.org/pipermail/cups/attachments/20061112/e73711d8/attachment.html>