Forced to Close Sonar To Copy Project To Alternate Drive

I'm pretty sure this is normal behavior for any program. Try and do this with any program, any file and Windows will give you this error. Consider it a protection. This way you avoid file corruption.

Thanks guys...

Yes, I understand the reasoning (closing first), but often it's a fast way for me to maintain constant backups while working.... You guys know how long it can take to open a file so if I've just recorded a lead vocal and want immediate backup, I must stop work to do that if I must close down Sonar...

When I was able to simply copy the files while open it made the procedure fast and unobtrusive...

...and it seems I was always able to until X1d's rollout...

I guess I'll have to learn to live with it as if it's "normal" for programs to do such (?), it must be a "fix" by the Bakers...

What about this one:

If I save a project then export a mix, X1d is also now marking the open file "dirty" (not saved with recent changes)... What's with that? The file hasn't been changed, only an export of it sent out.... Much like opening various "windows" to simply look at settings doesn't force a dirty state, why should the export?

I guess for the topic at hand, I may have to resort to a raid system to write to two drives simultaneously... Can anyone remind me which Raid number that is?

Thanks Again...
Keni