Failure converting doc/ps to pdf - offending command: setcmykoverprint

[Don_Parda@adobeforums.com]

Any ideas on this one?

For some doc files, PDFMaker hangs up during "printing" when converting doc to pdf.

For ps (prn) files from these doc files, Distiller hangs up with page 1 Error: undefined; OffendingCommand: setcmykoverprint.

Acrobat 5.5.5.2001101100
Acrobat Distiller 5.0.5.2001101100
Word 2002 (10.5522.4219) SP-2
Windows 2000 Ver 5.0 Build 2195 Service Pack 3

Thanks.

[Aandi_Inston@adobeforums.com]

An unusual one, but could possibly be from either
- embedded EPS files that aren't portable
- using the wrong PostScript driver

Aandi Inston

[Don_Parda@adobeforums.com]

Pursuing the possibility of the wrong PostScript driver.

Looking at a prn file generated for an HP5si, I find the following two lines

....
%!PS-Adobe-3.0
....
%%Creator: PScript5.dll Version 5.2
....

Does this tell me whether I have the right/wrong PostScript driver?

Incidentally, on an equivalent prn file generated on a different computer I use daily for printing, I find

....
%!PS-Adobe-3.0
....
%%Creator: Pscript.dll Version 5.0
....

Pursing the possibility of problems with EPS (thanks for the opportunity to be introduced to Encapsulated PostScript) files.

Looking at the prn file, I find multiple instances of

....%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 158 195 252 217
....
/setcmykoverprint
....

which I think means I have multiple embedded EPS files with the suspect command "setcmykoverprint".

Any clues on how to isolate (what marks the end of the file?) and view/print an EPS file?

Thanks.

Don Parda

[Aandi_Inston@adobeforums.com]

It's certainly the wrong driver. Use the Distiller driver (in Acrobat
6.0, called "Adobe PDF").

All these drivers use the same underlying program (PScript5.dll) but
produce different results.

Finding the end of an EPS can be tricky, but see if the
%!PS-Adobe ... EPSF...
line is preceded (perhaps separated by a few lines) by a line like
%%BeginDocument. If it is, look for a matched %%EndDocument.

Aandi Inston

[Don_Parda@adobeforums.com]

Thank you very much. The problem is solved. Changing the graphics implementation in the Word document page headers eliminated the suspect embedded EPS files. I did not have to change my existing PostScript driver (PScript5.dll Version 5.2?).

Don Parda