David W. Fenton wrote:
in this kind of situation, a program
that manages the deleted files on your hard drive would allow you to
revert to any version you chose.
and if one doesn't have, or doesn't want to buy or write such a program
it is easily simulated. When I start a large project, I create a new
directory, and create the template file (including loading all necessary
libraries, if necessart), which I save with a name of "0000.mus". After
this point, my first step in any editing session is to pull up the last
file saved, and immediately renaming it with the next number, so before
I enter a single note, I save the file as "0001.mus" and while autosave
is turned on, I still back-up manually to two separate directories, on
separate drives, on a regular basis.
Always when starting a new session with an existing file, the first item
of business is to save the file with a new name, to which the results of
that days edits will be saved. Doing it this way prevents the new work
on today from overwriting the work from yesterday. On a regular basis,
I visist the folder, select all of the files except the last one, and
change their attribute to "read only".
There has been a side benfit to this technique. On more than one
occasion, I was able to avoid spending a great deal of time and effort
removing items in a file when a client changed his mind about how he
wanted an item, simply by going back to an earlier version of the file.
Yes, the folder containing a major project may have a hundred or more
files in it, but given hardware and media costs, storage is incredibly
cheap these days, certainly far less than a dollar a gigabyte.
ns.
_______________________________________________
Finale mailing list
[email protected]
http://lists.shsu.edu/mailman/listinfo/finale
