Bug 690359 - no output, only an error message for a certain test case
Summary: no output, only an error message for a certain test case
Status: NOTIFIED FIXED
Alias: None
Product: GhostPCL
Classification: Unclassified
Component: PCL interpreter (show other bugs)
Version: 1.53
Hardware: PC Windows XP
: P2 normal
Assignee: Default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-26 08:14 UTC by Horiana Costea
Modified: 2009-04-30 05:51 UTC (History)
0 users

See Also:
Customer: 460
Word Size: ---


Attachments
pcl6.zip (1.27 MB, application/octet-stream)
2009-04-13 07:02 UTC, Ray Johnston
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Horiana Costea 2009-03-26 08:14:08 UTC
Hello,

We have a customer test case which gives no output, only an error message 
when we try to transform it using GhostPCL 1.53.

Here is the way we call pcl6 executable:
pcl6.exe -dNOPAUSE -sDEVICE=pcxmono -r300 -J"@PJL SET PAPER=2550x3300" -
sOutputFile=%iout.pcx testcase.pcl

And here are the error messages we obtain:

"system does not support requested paper setting
system does not support requested paper setting
Warning interpreter exited with error code -1
Flushing to end of job"

We also tested using the bmpmono device but the same behavior occurred.

When printing the testcase on a HP9000 Printer it prints correctly.

Thank you
Comment 1 Horiana Costea 2009-03-26 08:18:26 UTC
Created attachment 4868 [details]
testcase.pcl
Comment 2 Henry Stiles 2009-03-26 13:19:40 UTC
2550x3300 is not a pjl paper size name, use letter.  I am sure this command will
not select letter, it may be ignored and letter paper is the default.  If it
does select letter please reopen the bug, I am closing it because the behavior
is implementation dependent and we prefer an error.
Comment 3 Ray Johnston 2009-03-27 09:22:55 UTC
Just for reference, the set of 'known' paper sizes (and the sizes in 300 dpi
units) from pcl/pcpage.c is:

    "executive", 2175, 3150
    "letter",    2550, 3300
    "legal",     2550, 4200
    "ledger",    3300, 5100
    "a4",        2480, 3507
    "a3",        3507, 4960
    "monarch",   1162, 2250
    "com_10",    1237, 2850
    "dl",        1299, 2598
    "c5",        1913, 2704
    "b5",        2078, 2952
Comment 4 Horiana Costea 2009-03-31 02:36:42 UTC
We tried your suggestion with GhostPCL 1.53 and we used   -J"@PJL SET PAPER 
=letter" instead of  -J"@PJL SET PAPER =2550x3300" 
and there are no more messages regarding of not supported paper, but still we 
don't get any output, this is in fact the problem.
the following message occurs:

"Warning interpreter exited with error code -1
Flushing to end of job"

Since the document prints ok on an HP laserjet 9000 printer we think that the 
problem might be in Ghost PCL 1.53

Also we tested with a previous version of Ghost PCL (1.40) and the behavior is 
different:  With Ghost PCL 1.40 we get the output with a problem on it (some 
text is shifted  down).
Comment 5 Henry Stiles 2009-03-31 05:41:18 UTC
It produces output without error in the current code, I am traveling and don't
have access to an HP printer to check correctness.  Reassigning to support.
Comment 6 Ray Johnston 2009-04-02 09:43:04 UTC
Marcos will test on his HP printer (I don't have one)
Comment 7 Marcos H. Woehrmann 2009-04-06 12:29:34 UTC
I printed the file on an HP LaserJet 4100dn and an HP Color LaserJet CP3505dn and both produced ~26 
pages of output.  Both printers were loaded with US letter sized paper.
Comment 8 Marcos H. Woehrmann 2009-04-06 12:46:30 UTC
Output from the current GhostPCL head (r9614) is identical to the HP printer output, except for the page 
size.  The HP printers print onto letter size paper and cutoff the bottom of each page; GhostPCL output is 8.27 x 11.69 (inches) (with and without -J"@PJL SET PAPER=LETTER").

Comment 9 Horiana Costea 2009-04-07 04:21:36 UTC
We are approaching the CVT (component verification test) start date
for our component calling Artifex GhostPCL 1.53, so if this problem 
is fixed already in 1.54, we would need a patch for 1.53. 

Thank you.
Comment 10 Marcos H. Woehrmann 2009-04-07 11:35:20 UTC
I'm not able to reproduce this with 1.53.  The command line:

ghostpdl-1.53/main/obj/pcl6 -dNOPAUSE -sDEVICE=pcxmono -r300 -J"@PJL SET PAPER=LETTER" -
sOutputFile=%iout.pcx testcase.pcl

produces 27 pcx files and no error messages.
Comment 11 Horiana Costea 2009-04-13 02:20:15 UTC
We are having some difficulties in trying to transform the testcase using Ghost 
PCL. 
Since we tried both  GhostPCL 1.53 and 1.54 and we've got the same error 
message we suspect that it could be an issue related with the compiler we are 
using: Intel Compiler 10.1.021 .
Could you please let us know what is the compiler that Artifex team uses when 
they build on Windows?
Comment 12 Horiana Costea 2009-04-13 02:21:23 UTC
And also could you please send us output you obtained for the first two pages? 

Thanks.
Comment 13 Ray Johnston 2009-04-13 07:00:18 UTC
Created attachment 4924 [details]
out1-2.zip

Output of first two pages
Comment 14 Ray Johnston 2009-04-13 07:02:11 UTC
Created attachment 4925 [details]
pcl6.zip

pcl6.exe for Windows created with Microsoft Visual Studio 8.

Note that the "Express Edition" can be downloaded free of charge from
Microsoft.
Comment 15 Horiana Costea 2009-04-13 08:07:46 UTC
Could you please tell me how can I download the private file?
When I am trying to see the attachment I am getting:
"Access to this attachment is restricted." message.

Thanks
Comment 16 Henry Stiles 2009-04-15 20:58:42 UTC
Ahh, I was just about to work on this and realized Ray already did it. 
testcase.pcl and out1-2.zip are private (restricted) but pcl6.zip is not as far
as I can tell.  It sounds to me like you should download the free microsoft
express edition, like Ray said, then you could do a bit compare of all output
files, if you think there are compiler problems.

I am reassigning to support if an actual pcl bug unfolds please assign it back
to me.
Comment 17 Horiana Costea 2009-04-16 08:00:42 UTC
We eventually succeeded to perform the transformation.
And the output looks ok on both versions 1.53 and 1.54.
You can change the resolution of this bug to FIXED. Thanks.