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

[Robert Lauriston]

If Adobe has dropped support for file sharing on shared drives, they
should get rid of the locks.

Unless the data-files-must-be-local thing is working around a bug.

On Wed, Feb 13, 2013 at 9:16 AM, Ken Poshedly <poshedly at bellsouth.net> wrote:
> Yes, an .lck file is created but perhaps it no longer does what it used to
> do before. Capisce?
>
> -- Ken in Atlanta
>
>
> ________________________________
> From: Robert Lauriston <robert at lauriston.com>
> To: Ken Poshedly <poshedly at bellsouth.net>; framers at lists.frameusers.com;
> TECHWR-L <techwr-l at techwr-l.com>
> Sent: Wed, February 13, 2013 12:11:02 PM
> Subject: Re: "FrameMaker has detected a problem and must quit" Really?!
>
> That's a pretty radical change. Does FM11 not create .lck files when
> you open an .fm file?
>
> On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly <poshedly at bellsouth.net>
> wrote:
>> I just learned from Adobe tech support (via phone call) that the
>> permissions in
>> FrameMaker 11.0 have been modified so that the data files should also be
>> on the
>> same hard drive where FM 11.0 is installed. Working across drives (FM
>> here, data
>> files there) is no longer an accepted practice -- at least not with FM11.
>>
>> I guess this explains the flaky, intermittent nature of my coworker's FM
>> crashes
>> because that (the "wrong" way is just how we've been doing things here.