[13718] in Athena Bugs
Frame 4.0 crash on printing
daemon@ATHENA.MIT.EDU (Dorothy Bowe)
Tue Aug 8 09:12:19 1995
To: bugs@MIT.EDU
In-Reply-To:
Date: Tue, 08 Aug 1995 09:12:15 EDT
From: Dorothy Bowe <dot@MIT.EDU>
here is the information I received from Frame regarding this bug:
------- Forwarded Message
Hello Dorothy:
Thanks again for forwarding the files. This is a strange one.
I tried to print your file to a file and I got the following
error message but no core file:
fmprintdr.ps: Internal error 11 in version 4. Please contact Technical Suppor
t and describe the actions leading up to this error. : 104
fmprintdr.ps: Cannot finish printing.
I found a technical note on this error and one of the suggestions
was to see if a custom color had been created and the name of
the custom color included a \. When I tried to look at the color
definitions by choosing View-Color-Definitions, maker crashed
without any errors and produced a core file.
I determined that the crash was not related to the imported epsi
because the crash still occured after removing the epsi. Finally
I tried saving your file to MIF, opening the MIF, and saving back
to Normal format. This resolved both the print errors and the
Color Definition crash. Note that there were no custom colors in
your doc.
Sometimes saving a file to MIF will fix corruptions and inconsistencies
in a doc. This is exactly what it did for your file. I compared
the first MIF to one that I created after saving the MIF to Normal
format. The first MIF was missing some statements related to color.
I was unable to reproduce either problem in a New Custom
doc. I used the same margins as your file and imported the
epsi by copy into the same location. No problems printing to
a file or opening the Color Definitions window.
So it seems like this doc got corrupted. Unfortunately, I don't
think we can tell how it got into this state. Perhaps this file
was created in an unusual way? Was it filtered from another
application? Any information you can give to me on the way it
was created?
I also wanted to let you know that neither problem occured
when I opened the original file in FrameMaker Release 5.
------- End of Forwarded Message
