<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman,new york,times,serif;font-size:14pt"><div>Yes, an .lck file is created but perhaps it no longer does what it used to do before. Capisce?<br><br>-- Ken in Atlanta<br><br></div><div style="font-family:times new roman, new york, times, serif;font-size:14pt"><br><div style="font-family:arial, helvetica, sans-serif;font-size:10pt"><font face="Tahoma" size="2"><hr size="1"><b><span style="font-weight: bold;">From:</span></b> Robert Lauriston <robert@lauriston.com><br><b><span style="font-weight: bold;">To:</span></b> Ken Poshedly <poshedly@bellsouth.net>; framers@lists.frameusers.com; TECHWR-L <techwr-l@techwr-l.com><br><b><span style="font-weight: bold;">Sent:</span></b> Wed, February 13, 2013 12:11:02 PM<br><b><span style="font-weight: bold;">Subject:</span></b> Re: "FrameMaker has detected a problem and must quit"
Really?!<br></font><br>
That's a pretty radical change. Does FM11 not create .lck files when<br>you open an .fm file?<br><br>On Wed, Feb 13, 2013 at 8:55 AM, Ken Poshedly <<a ymailto="mailto:poshedly@bellsouth.net" href="mailto:poshedly@bellsouth.net">poshedly@bellsouth.net</a>> wrote:<br>> I just learned from Adobe tech support (via phone call) that the permissions in<br>> FrameMaker 11.0 have been modified so that the data files should also be on the<br>> same hard drive where FM 11.0 is installed. Working across drives (FM here, data<br>> files there) is no longer an accepted practice -- at least not with FM11.<br>><br>> I guess this explains the flaky, intermittent nature of my coworker's FM crashes<br>> because that (the "wrong" way is just how we've been doing things here.<br></div></div>
</div></body></html>