Operating System - HP-UX
1820260 Members
2841 Online
109622 Solutions
New Discussion

Problem printing a postscript file if it is big

 
Marko_3
Contributor

Problem printing a postscript file if it is big

Dear all

I have problem printing out a postscript file if it is too big, say 80KB. I have no problem printing a file which is say 60KB.

The postscript file was converted using html2ps perl program.

The error message of the file when opened with Ghostviewer:

Loading NimbusSanL-BoldItal font from d:\gs\fonts\n019024l.pfb... 2519520 1122076 1670480 344053 2 done.
Loading StandardSymL font from d:\gs\fonts\s050000l.pfb... 2559712 1161366 1670480 346019 2 done.
%GSVIEW_PDF_MARK: /DOCINFO /Title (Invoice: _INVOICENUM_) /Subject () /Keywords () /Author () /Creator (html2ps version 1.0 beta3)
Unrecoverable error: rangecheck in put
Operand stack:
0 31 --nostringval-- 9.16667 --nostringval--

--- Begin offending input ---

--- End offending input ---
file offset = 73728
gsdll_execute_cont returns -15

Please help.

Thanks
1 REPLY 1
Alex Glennie
Honored Contributor

Re: Problem printing a postscript file if it is big

sounds like the file may have been corrupted :

Rangecheck

According to the Adobe PostScript Language Reference Manual, a "Rangecheck" message
is produced when "A numeric operand's value is outside the range expected by an
operator--for example, an array or string index is out of bounds, or a negative number appears
where a non-negative number is required. Rangecheck can also occur if a matrix operand
does not contain exactly six elements."

Referring to the PostScript Error Types table above, you will find Rangecheck to be
associated with "unintelligible PostScript code." What this means is that information was
received by the PostScript interpreter which was unexpected in the situation where it was
presented.

Since this error is not related to memory, the steps for troubleshooting are not a duplicate of
those for a Limitcheck; however, they do have similarities.

Look for clues in the error itself.

Here, the type would be Rangecheck, and the offending command would be our clue. The
offending command is the last command that the PostScript interpreter attempted to process.
Look up the offending command in the table above to see into which category it falls. This will
help to give us a starting point. Since Rangecheck does not specifically point to memory or
complexity in a file, use the starting point identified by the offending command and begin to
isolate the cause.

Are you using the correct printer driver and PPD? Using a level 2 driver with a
level 1 printer or program can cause this error to occur. Using an incorrect PPD
can also cause this error to occur.
Are the Page setup and Print dialog boxes configured correctly?
Try a different driver or reinstall the existing driver (be sure to discard the original
driver and associated Preferences file before reinstalling).
Try printing from a different application.
Try to isolate the element in the file (look at the offending command for clues).

Since this error type is in the "Unintelligible PostScript code" category, the offending
command will often be some random character. This makes the value of the offending
command less than it otherwise could be. In these situations, use the steps in the general
troubleshooting guidelines below to identify where the problem occurs, and follow the
recommendations listed.