"FrameMaker has detected a problem and must quit" Really?!

[Robert Lauriston]

I haven't worked anywhere without source control in years, but before
that, I encountered so many problems editing FrameMaker files on
network shared drives that I eventually decided it was easier to work
on a local copy.

On Wed, Feb 13, 2013 at 11:27 AM, Ken Poshedly <poshedly at bellsouth.net> wrote:
> 1. Copied the entire folder with all book and chapter files from the network
> drive to his own C-drive.
> 2. Once more did steps 2, 3 and 4 using only the files on his own C-drive,
> but this time with no FM crashes -- at least so far.
>
> So it APPEARS this has solved the problem. More info if / as it develops.