<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v = "urn:schemas-microsoft-com:vml" xmlns:o = "urn:schemas-microsoft-com:office:office" xmlns:w = "urn:schemas-microsoft-com:office:word" xmlns:m = "http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 9.00.8112.16496">
<STYLE><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle19
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.EmailStyle20
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></STYLE>
</HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Segoe UI" lang=EN-US vLink=purple link=blue>
<DIV>We get crashes on FM10 pretty often when manipulating conditional text dialog boxes. Sometimes they crash "cleanly", but sometimes we don't get a crash message etc, FM just freezes. I left one overnight a while ago and it was still frozen the next morning.</DIV>
<DIV> </DIV>
<DIV>(We've tested FM11 and it looks like this bug is fixed. We'll be upgrading soon - hopefully we won't see a whole bunch of new bugs to work around!)</DIV>
<DIV> </DIV>
<DIV>Cheers</DIV>
<DIV>Rebecca</DIV>
<DIV><BR>>>> Craig Ede <craigede@hotmail.com> 14/08/13 03:57 >>><BR></DIV>
<DIV class=WordSection1>
<DIV>
<DIV id=yiv1545870390>
<DIV>
<DIV>
<DIV id=yiv1545870390yui_3_7_2_63_1375964420720_143>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Framemaker can take quite a while to do some things, so it's important to know the difference between a crash and a "FrameMaker is not responding" message. The latter means "Wait until I complete this task." The former is accompanied by a crash message and exiting from FrameMaker. Very seldom do I see crashes that don't have the crash window message (which contains the opportunity of send the logs to Adobe for analysis to improve the product).<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt">Craig<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: 'Calibri','sans-serif'; COLOR: #1f497d; FONT-SIZE: 11pt"><o:p> </o:p></SPAN></P></DIV></DIV></DIV></DIV></DIV></DIV>
<P><BR>NOTICE: This message contains privileged and confidential<BR>information
intended only for the use of the addressee<BR>named above. If you are not the
intended recipient of<BR>this message you are hereby notified that you must
not<BR>disseminate, copy or take any action in reliance on it.<BR>If you have
received this message in error please<BR>notify Allied Telesis Labs Ltd
immediately.<BR>Any views expressed in this message are those of
the<BR>individual sender, except where the sender has the<BR>authority to issue
and specifically states them to<BR>be the views of Allied Telesis Labs.</P>
<P> </P>
</BODY></HTML>