Yesterday (Wednesday) morning, FM 11.0 crashed while it was opening his files. 
His process was to open the book file, then open each chapter file 
one-at-a-time. There are six chapters in the book. FM 11 crashed while opening 
the fifth chapter. We then tried another tact, that is to open one chapter, 
scroll through it, then open a second chapter and scroll through it. It then 
crashed while scrolling through the second chapter. We kept at it before I 
called the Adobe rep.

Of COURSE things work faster when all are on the same drive -- I just happen to 
mention it here.

But the problem that did NOT occur last week DID occur first thing Wednesday 
a.m. here. He couldn't even work on any files because FM 11 kept crashing.
And now it doesn't. THAT'S what I meant by the "go figure" comment.

-- Ken

From: "Combs, Richard" <>
To: Ken Poshedly <poshedly at>; "framers at" 
<framers at>
Cc: "techwr-l at" <techwr-l at>
Sent: Thu, February 14, 2013 4:39:30 PM
Subject: RE: "FrameMaker has detected a problem and must quit" Really?!

Ken Poshedly wrote:

> Fourth, my coworker has experienced no FM crashes since moving his work files
> to
> his hard drive where his FM program files are also located. Also, his files
> now
> seem to open and process far faster than before. Go figure. 

Go figure? You really find it surprising that it takes longer to read/write 
files across the network than on your local hard drive? 

As several of us have tried to point out, it's local vs. remote that's making 
the difference. Your coworker would be seeing the same increased reliability 
speed if he were storing his work on a second hard drive in his PC. 

Richard G. Combs
Senior Technical Writer
Polycom, Inc.
richardDOTcombs AT polycomDOTcom
rgcombs AT gmailDOTcom
-------------- next part --------------
An HTML attachment was scrubbed...

Reply via email to