We operate from network server drive, and have experienced the very same
problems while using Win 7 FM 11.
It isn't really a problem with FM, it's a server problem involving latency on
If you look at the resulting files after a crash you may see son with stable,
apparently random extensions. These are the open temporary files that FM
creates while working in an open file.
The crash occurs when the serve cannot keep up withe file writes.
Thank both Microsoft and your IT Department. Your infrastructure cannot keep up
with your companies demand.
On Aug 13, 2013, at 10:57, Craig Ede <craig...@hotmail.com> wrote:
> 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).
> You are currently subscribed to framers as qui...@airmail.net.
> Send list messages to email@example.com.
> To unsubscribe send a blank email to
> or visit
> Send administrative questions to listad...@frameusers.com. Visit
> http://www.frameusers.com/ for more resources and info.
You are currently subscribed to framers as arch...@mail-archive.com.
Send list messages to firstname.lastname@example.org.
To unsubscribe send a blank email to
Send administrative questions to listad...@frameusers.com. Visit
http://www.frameusers.com/ for more resources and info.