<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">I think it's fair to say that
FrameMaker never crashes _for you_. However, given my (somewhat
different) experience with the stability of FrameMaker 11, I'm
sensitive about having our concerns dismissed. :-)<br>
<br>
Stability of FrameMaker seems to vary greatly depending on the
source files being edited, authoring mode, and system environment
(even on systems that meet and exceed FrameMaker requirements). If
you haven't had the privilege of working on a "crashy" project,
you're lucky.<br>
<br>
<div class="moz-signature">-Alan<br>
<br>
</div>
On 8/11/13 12:07 PM, Matt Sullivan wrote:<br>
</div>
<blockquote
cite="mid:BEEEC8D8-D047-41BC-895D-4003906D9051@mattrsullivan.com"
type="cite">I run FrameMaker so much, and crash Fm11 so
infrequently, it's pretty fair to say it never crashes. The few
times I see a crash it is the result of :
<div>
<ul class="MailOutline">
<li>a specific file which will not open (either a problematic
graphic, or a "corrupted" .fm file)</li>
<li>a missing resource (font, graphic, unresolved xref) which
presents a user interaction dialog while updating a linked
Rh project (or any other similar process)</li>
</ul>
<div><br>
</div>
<div>Once you enable all missing resource alerts in your prefs,
AND you can open and update your entire book without error
messages, then you can start narrowing down the file and or
graphic that is causing your issue. Isolate the offending
files from "good" content, and keep splitting the "bad" files
in half to narrow down the problem.</div>
<div><br>
</div>
<div>NOTE: Those that can remember 25 MHz computers will recall
that we didn't always have immediate computer processing
gratification!!! When your application becomes unresponsive,
take the opportunity to (insert your Zen activity of choice)
and allow Fm (or other app) to either complete the process, or
present an actual crash message. Failure to allow Fm to
complete a process could itself be what causes an actual
problem with the file.</div>
<div apple-content-edited="true">
<p style="font-family: arial, helvetica; ">FWIW, I'm running
Fm on a lean system: 4Gb RAM on my MacBook Air, shared
between the Mac OS and Win 7. I routinely run any and all
apps concurrently without fear of crashing. I do this for
online classes, for Adobe-sponsored webinars, and many other
situations where crashing would impact my ability to do my
job, and very seriously and negatively impact my clientele.
And I don't crash.</p>
<p style="font-family: arial, helvetica; "><br>
-Matt<br>
</p>
<br>
</div>
</div>
</blockquote>
<br>
</body>
</html>