Note: please don't spam any of the e-mail addresses which you see here. Follow this link if you want some addresses to misuse.
From: Francisco Franco <ffranco@aerocompsys.com> Date: Wed, 1 May 2002 17:57:48 -0400 (EDT) Subject: Re: PPR: missing ppr.conf? -- should be misconfigured printer? Hi David, Well, I ran into the same problem with the updated version of PPR. I must be missing something. Francisco On Wed, 1 May 2002, Francisco Franco wrote: > Hi David, > > Just an update. I went back, removed ppr and re-instated the lp that > comes with Solaris. Defined the printer using the admintool and now it > works. The print job went through on Solaris 8. Using the OS lp on HP-UX > 11, I have to do a lp -d myprinter -o postscript and it works. I was > using ppr-1.44. I've noticed that ppr-1.50a1 is now available. I'm going > to download the updated package and see if this fixes the problem. > > Any ideas as to what your experience may point to what I have done wrong > would be appreciated. > > Francisco > > On Tue, 30 Apr 2002, David Chappell wrote: > > > Francisco Franco wrote: > > > > >Hi Folks, > > > > > >When submitting a postscript print job, I get the following messages: > > > > > >+++ > > >WARNING: Procset "NTPSOct95" has no version and revision numbers > > >WARNING: Ignoring "%%Pages:" in trailer because no "%%Pages: (atend)" in header > > >WARNING: 241757 characters follow EOF mark > > >WARNING: No valid "%%Pages:" comment > > >+++ > > > > > >The printjob gets stuck at 9% and goes no further. I have tried to change > > >PPD files from the Optra 1855 to the Optra 1255 to Optra 1655 to the > > >AppleLaserWritter to the HP Laserjet 4Si Postscript. I can print output > > >from Netscape browser and from text (ie ls | pprd -d...), but I can't > > >print the file that is giving me the problem. I tried to open the > > >file that is giving me the problem in GhostView and Ghostview does not > > >complain about the file. > > > > > >Are there any parameters that I can use to force the job through or get > > >more info as to why the job is stuck where it is. Here is the output from > > >the different ppr commands: > > > > > It is difficult to know what to suggest. Chaning the PPD file is > > unlikely to help. > > > > I once had jobs that got stuck on an HP 5Si. The problem was that the > > printer would detect a fatal internal error, print an error message, and > > partialy reset itself. The network connection wouldn't be broken but > > the printer would "forget" that it was processing a job. Since PPR was > > waiting for the printer to indicate that it had finished the job, it > > would wait forever. You should use the "ppop log" command to display > > the job's log file since there might be some indication. > > > > The fact that PPR thinks there are 241757 characters after %%EOF > > definitely a bad sign. It may mean that the DSC comments in the job are > > misleading. If so, it may help to use ppr's "-H editps" option. PPR > > may have a Perl script that can fix the job in its editps/ directory. > > > > > > - -- Francisco Franco ffranco@aerocompsys.com AeroComp Consulting Inc. (416) 409-0163