Endless crashes when trying to print book to file (Unstructured)

[Bodvar Bjorgvinsson]

Hi David,

Thank you for the reply.

This is what I do. And, there are no Xrefs yet in the files. However
it is this that leads me to thing that a font may be suspicious. But
this is a format that I have used on three other books in the last
couple of years, so I am not "hopeful" of finding the solution there.

Bodvar

On 12/21/06, Shenton, David (DTRN) <david.shenton at smithsdetection.com> wrote:
>
> Try looking at the postscript program as its running and see what page
> it stops on. Check out the particular page delete any xrefs on that
> page. This has happened to me xref being the problem.
>
> -----Original Message-----
> From:
> framers-bounces+david.shenton=smithsdetection.com at lists.frameusers.com
> [mailto:framers-bounces+david.shenton=smithsdetection.com at lists.frameuse
> rs.com] On Behalf Of Bodvar Bjorgvinsson
> Sent: Thursday, December 21, 2006 4:55 AM
> To: Framers (E-mail)
> Subject: Endless crashes when trying to print book to file
> (Unstructured)
>
> I am having problems printing a certain book to file. Sometimes FM
> crashes on the first file, somtimes farther back. I have tried to start
> a new empty template and copy the contents from the old file into the
> new one, plus importing the formats into the new file. It seems to work
> at first, but then crashes working on another file in the book.
> Then when I retry, it even crashes at the first file in the book the one
> I had just rebuilt.
>
> The messages I get are:
>
> Internal Error 7204, 610980, 7778516, 0. FrameMaker has detected a
> serious problem and must quit. Etc.; and then
>
> Adobe FrameMaker: FrameMaker.exe - Application Error The instruction at
> "0x0039199f" referenced memory at "0x00000000". The memory could not be
> read. Etc.
>