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: "Dr Douglas J. Chappell" <d.chappell@mmb.usyd.edu.au> Date: Thu, 28 Mar 2002 10:49:10 +1100 Subject: Re: PPR: ppr 1.44 not collating Windows2000 + procsets Brian, You wrote: > We are using a redhat 6.2 box with samba 2.2.3a for windows >printing. we >cannot print collated copies from Windows 2000. We are also having >difficulties printing PDF's from Windows 2000 as well. For the PDFs that >don't print ppr states that the procset resource CIDINIT is not found, but it >appears to be there when looking at the ps file. any help would be greatly >appreciated. Something like this? # ppop log sc2-1234 : : +Job turned away from printer "sc2p2" for the following reason(s): +Resource "ProcSet CIDInit" not available. We are having similar problems here, however, the procset is not present. Are you sure you have the CIDInit procedure set? The postscript in the job files I have looked at defines only that CIDInit is needed. %%DocumentNeededResources: procset CIDInit %%IncludeResource: procset CIDInit If it was included we would expect something like: %%BeginResource: procset CIDInit : : %%EndResource The adobe CIDFont_Spec states. *** Immediately after the header information and before the definition of the CIDFont proper, a findresource is done on the procset CIDInit, which is one of the system support files installed on the host or printer hard disk. This ensures that the routines necessary to process CIDFont files are first read into VM. An end operator corresponding to this begin appears near the end of the file. *** What I'd like to be do is to install these procsets in the cache (/usr/share/ppr/cache/procset) and have ppr add them on the fly. I note that the latest ghostscript seems to have CID font support. Actually ppr often complains that other resources are not present when they are but these jobs print possibly because there is no DocumentNeededResources comment referring to them??? $ ppop log mackay-7298 WARNING: Resource "procset Pscript_WinNT_ErrorHandler 5 0" declared Supplied but isn't included WARNING: Resource "procset Pscript_FatalError 5 0" declared Supplied but isn't included WARNING: Resource "procset Pscript_Win_Basic 5 0" declared Supplied but isn't included WARNING: Resource "procset Pscript_Win_Utils_L2 5 0" declared Supplied but isn't included WARNING: Resource "procset Pscript_WinNT_Compat 5 0" declared Supplied but isn't included I used the extractres utility (from psutils) to pull out these resources and moved them to /usr/share/ppr/cache/procset to test out resource inclusion. I haven't got it to work yet. I thought I might trap an infile (switchset -H keepinfile), pull out the resources and then send the stripped file to see if they are included. I renamed the resources according to the style set by the other files in the directory (eg Pscript_WinNT_Min-5-0). Incidently if you trap an infile with the CIDInit problem and rewrite it with ps2ps (ghostscript) it will print. Doug |--------------------------------| | Dr Doug Chappell | | School of Molecular and | | Microbial Biosciences | | The University of Sydney, 2006 | | NSW AUSTRALIA | | d.chappell@mmb.usyd.edu.au | |--------------------------------| | Phone: 61 2 9351 2511 | | Fax: 61 2 9351 4726 | |--------------------------------|