RE: [hpoj-devel] Re: ptal-mlcd debug message dump

[PASCHAL,DAVID (HP-Roseville,ex1) <dav...@hp...>]

Hi, Joe.  What happens if you start ptal-printd with the "-nouel" switch?  I
changed the UEL format recently (since 0.7) to fix PostScript printing on
the LaserJet 3200m, and maybe this change confuses your printer (and causes
it to bitbucket the job and/or freak out).  If this doesn't work, you could
also just try the 0.7 version of ptal-printd.c and see if that works any
better, but of course it lacks the robustness "fixes" I put in that now
could be suspect.

David

Joe Piolunek wrote:
> The ptal-printd queue really doesn't like to accept text as 
> the first print 
> job. Sometimes postscript isn't accepted either. Printing a 
> web page from 
> netscape sometimes won't create a first entry in the queue, 
> even after 
> reloading the page. It appears that once there is a first 
> entry, subsequent 
> jobs can be more reliably added.
> 
> This is just a guess, but could one of the daemons be 
> bit-bucketing the job 
> inappropriately at times?
> 
> When attempting to print to the ptal-printd queue from 
> netscape, this error 
> message often appears. When it does, it repeats every 30 
> seconds, until 
> ptal-printd is killed.
>  
> ]# ptalChannelOpen(chan=0x0804AF60): provider failed open!
> ptal-printd(mlc:par:0): ptalChannelOpen failed!  Will delay and retry.
> ptalChannelOpen(chan=0x0804AF60): provider failed open!
...
> I just noticed that when attempting to print with ptal-mlcd, 
> instead of 
> totally ignoring the print request, the 600's LCD screen 
> shows the message "0 
> pages printed". So far, that's the only response I've seen 
> from the printer. 
> It appears a few seconds after attempting to print a 
> postscript file from the 
> command line. The message doesn't seem to appear again until 
> the daemons are 
> restarted.