To me, it sounds as if you're running out of memory/resources at the
end of the string of operations, but you didn't provide your system
specifics. And I wouldn't be at all surprised if there was some memory
leakage going on. Also whether you're running other memory-hungry aps
at the same time. I
Thanks.
The files are on the network. But they are
relatively small (66 pages) compared to other
books (1200 pages) that work fine.
I will wash and see what happens.
Can I get any info on network timeout and using
FM files - any documentation out there?
Thx again.
At 11:00 AM 07/05/2009,
Jim: The offending text field is probably a text frame that is marked as
PostScript code in the text frame's object properties. The first word in the
text frame is KVH, and since PostScript is space-delimited, PostScript throws
an error at the first word (KVH not being a proper PostScript or
Great catch, William! Whoever thinks about PS text frames anymore?
Regards,
Peter
___
Peter Gold
KnowHow ProServices
___
You are currently subscribed to Framers as [EMAIL PROTECTED]
Send list messages to [EMAIL PROTECTED]
Hi, Jim
Make sure all your files are consistent in the book in page layouts, sizes,
pagination, etc. Is the printer time out set to low?
Brenda
Brenda L. Waltermeyer
Lead Desktop Publisher
The Johns Hopkins University Applied Physics Laboratory
National Security
Thanks for all of your help. I just figured out a workaround. I noticed
the first file in the book was the only one that I couldn't save as a
PDF. The culprit was the last page of the first file. There was a text
field that existed in duplicate in both the left master page and body
page. I tried
Hi, James:
Usually an offending command statement displays the name of a
PostScript command that is somehow incorrect at that location in the
PostScript code, for some reason or other.
If your company initials are identified as the offending command, it's
possible that one or more of your files
