Fred is correct. I also did that and it stopped the problem. (I knew I was forgetting something - Thanks Fred!)
Thank you, Gillian Flato Technical Writer (Software) nanometrics 1550 Buckeye Dr. Milpitas, CA. 95035 *408.545.6316 7 408.232.5911 * gflato at nanometrics.com<mailto:gflato at nanometrics.com> "Well Done is better than Well Said" - Benjamin Franklin From: Fred Ridder [mailto:docu...@hotmail.com] Sent: Thursday, August 05, 2010 10:45 AM To: Flato, Gillian; orlyz at marvell.com; framers at lists.frameusers.com Cc: igork at marvell.com Subject: RE: FM8 crashing upon showing all conditions. Gillian Flato wrote: > I had that problem a few months ago. Check the directory where the files are > kept. Delete all of the lock files. > Before viewing all of the conditions, update your book. Delete any lock > (*.lck) files, than view the conditions. That worked for me. And unless the files are in a network directory (a situation that has its own set of gotchas) so that other users can potentially be using some of the same files at the same time as you are, you can safely set FrameMaker to stop generating all thoise *.lck files in the first place. Go to File>Preferences>General and de-select the Network File Locking option. The primitive lock file mechanism provides such minimal protection in a shared directory working environment that IMO it isn't worth the hassle of having to clean up the left-over lock files if/when FrameMaker "unexpectedly exits" or "has to quit", which seemingly happens fairly frequently when you are working on files that reside on a network drive. -Fred Ridder
