RE: What does this Frame 5.5.6 error message mean?

[Ed Treijs <etreijs@xxxxxxxxxxxxxxxx>]

> I agree that this could be caused by network error, but check in 
> the directory and see if you have a .lck file for the FM file in 
> question.  If so, delete the .lck file.  Also, try saving the file
> to a new name and then renaming it directly.  Is the file listed
> in a book file?  You can rename the file from there too.  I can't 
> remember where it is, but there is a "Network File Locking" setting
> in Frame.  Turn that setting off.
Sender: owner-framers@omsys.com
Precedence: bulk
X-Mail-Loop: 1

We have tried deleting the .lck file.  Usually this lets you save the file
once.  The next time you try to save, the lock file is back and so are the
"changed on disk....save anyway....file has an odd suffix" messages.  In a
pinch, doing this or saving as another file keeps you from losing your work.
However, once the problem appears, then it persists and you must reset the
lock file and/or "save as" every time you save your work.  (I guess that
argues against a temporary network glitch.)

Unfortunately one person lost a few files when it happened on a book she was
regenerating.  The regeneration opens and closes files, and in this case
nuked a couple of files before it gave up with an error message.  No chance
to reset locks or save as.  (I don't know what effect automatic save would
have.)

Yes, we have Network File Locking set to on.  Can turn it off and see.  It
is quite unlikely that someone else can fiddle with our files, since we use
RCS on UNIX and only the owner has read access.

Anyone have comments on any possible side-effects of turning off the file
locking?

Thanks
Ed


** To unsubscribe, send a message to majordomo@omsys.com **
** with "unsubscribe framers" (no quotes) in the body.   **