Windows 7 + FrameMaker 11 = BOOM!

[rebecca officer]

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.
 
(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!)
 
Cheers
Rebecca

>>> Craig Ede <craigede at hotmail.com> 14/08/13 03:57 >>>

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).
Craig
 

NOTICE: This message contains privileged and confidential
information intended only for the use of the addressee
named above. If you are not the intended recipient of
this message you are hereby notified that you must not
disseminate, copy or take any action in reliance on it.
If you have received this message in error please
notify Allied Telesis Labs Ltd immediately.
Any views expressed in this message are those of the
individual sender, except where the sender has the
authority to issue and specifically states them to
be the views of Allied Telesis Labs.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.frameusers.com/pipermail/framers-frameusers.com/attachments/20130814/0bfa78d1/attachment.htm>