🚀 go-pugleaf

Re <9204110408.AA09971@raisin-nut> <19542@chopin.udel.edu>:

Boris Chang reports problems displaying PostScript files:

>    The (B) 8 bit color ps file could not displayed was
> 
>    %!PS-Abode-3.0 EPSF-3.0
>    %%BoundingBox 0 0 
>    %%LanaguageLevel: 2
>    %%EndProlog
>    320 200 scale 
>    [/Indexed /Device RGB 255
>    < .... (some color map data I guess) ...>
>    ] setcolorspace
>    <<
>    /ImageType 1
>    /Width 320 /Height 200
>    /BitsPerComponent 8
>    /Decode [0 1 0 1 0 1]
>    /ImageMatrix [320 0 0 -200 0 200] 
>    /DataSource Currentfile /ASCIIHexDecode filter
>    >>
>    image

setcolorspace, <<, >>, and the dictionary form of `image' are Level 2
PostScript features that Ghostscript does not currently implement.

> 3. The (A) file 24 bit color image also wouldn't work: (ps file)
>    
>    ......
>    320 200 scale
>    /picstr 960 string def
>    320 200 24
>    [320 0 0 -200 0 200] {currentfile ... pop}
>    false 3
>    colorimage
>    .... (color image data) ...
>    %%EOF
> 
>    The error message was:
>    ----------------------------------------------
>    Initializing... done.
>    Error: /rangecheck in --colorimage--
>    Operand stack:
>        320  200  24  [320 0 0 -200 0 200]  
>    {currentfile picstr readhexstring pop}  
>    false  3
>    Execution stack:
>        %interp_exit    --nostringval--  --nostringval--  false  
>    --nostringval--  --nostringval--  false  --nostringval--   
>    --nostringval--  --nostringval--
>    Dictionary stack:
>        426/449  6/200
>    Ghostscript 2.4 (3/25/92)
>    --------------------------------------------	
>    I do not know how to make it works!

This file is not valid, according to the specification of colorimage
on p. 376 of the PostScript Language Reference Manual, Second
Edition.  The value 24 is not legal as the bits/comp argument for
colorimage: this value must be the number of bits for each component,
not the total number of bits in each pixel.  In other words, this is
caused by a bug in the Alchemy program that produced the PostScript
file.

> 4. The gs386.exe (plus dos4gw.exe) was not functioned at all.  
>    The error message was: (after I execute gs386 myfile.ps)
> 
>    DOS/4GW Protected Mode Run-Time Version 1.3
>    Copyright ....
>    DOS/4GW Fatal error: Loader failed --LINEXE_LOADER
> 

Several other people have reported this error.  I do not know what it
means.  I cannot find it in the Watcom documentation.  I will report
it to Watcom Technical Support and post the reply here.

L. Peter Deutsch :: Aladdin Enterprises :: P.O. box 60264, Palo Alto, CA 94306
ghost@aladdin.com, ...decwrl!aladdin!ghost ; 415-322-0103 8-9 AM M-F/msg
	    "Implementation is the sincerest form of flattery."