On 8 Jun 2004 at 21:31, Christopher BJ Smith wrote:
At 8:13 PM -0400 6/08/04, Darcy James Argue wrote: > >The other thing to watch out for is Finale changing the name of your >file, causing it to overwrite an existing file, without telling you. >This bug is relatively rare, but three people on the list have >already fallen prey to it, and boy does it suck when it happens to >you. Make sure you turn on "Make Backups When Saving Files." You'll >need it.
I'm not convinced that this will help. After all, if the wrong file is overwritten when it is saved, the backup will be overwritten, too, won't it? I don't use this feature for that reason. The only thing it seems to save ME from is hard-drive failure in the middle of a session, if I set the backup to occur on another drive. I drag my documents folder over to my other drive daily.
It won't save the new version, but at least you won't lose the *old* version, just the changes since your last save.
Think of it this way (using Windows file naming conventions, of course):
You are working on GrandSymphony.MUS.
You work on it for a while, and then you save it.
The previous version is renamed GrandSymphony.BAK and the new version is saved as GrandSymphony.MUS.
GrandSymphony.BAK will still be the version that you opened (or the last time you saved it after opening it), so if GrandSymphony.MUS ends up having the contents of some other file you had open, you have lost only the changes since the last time GrandSymphony.BAK was saved.
But doesn't Autosave save a .bak file, too? That means that if you don't notice that things have gone wrong for five minutes or more, then GrandSymphony.BAK will ALSO have the wrong contents.
Christopher _______________________________________________ Finale mailing list [EMAIL PROTECTED] http://lists.shsu.edu/mailman/listinfo/finale
