Seems like I'm getting somewhere with finding out why I lost the project in the first place.

I recently bought the "Filmscore" expansion patch for Rapture. I have found out that this seems to be causing all kinds of problems. When Rapture is open with a filmscore patch loaded, Sonar tends to either crash, freeze or give me the message that the disk is full and it cannot save the file.

This happens nine times out of ten. I only looked at this when I saw that some other users are complaining of similar problems with the filmscore patches.

Has anyone else experienced this too?

Cheers,

Peter.

I'm assuming everyone uses Per Project folders yes?

 
I'm not a fan of per-project folders.  I like to keep my project files in one location (usually my C: drive) and ALL audio data (and only audio data) on my dedicated D: drive.  I find this a much cleaner system, and less prone to trouble.  The idea is to keep the audio stream totally free from interruption by the system.  Sonar knows which files go where, so I don't have to, and the audio files are titled sensibly enough you can find them if you really need to.  For moving a project elsewhere, I can always save it as a bundle. 
 
I've written batch files using xcopy for backups, and they work beautifully.  ALL my audio data is backed up in a single place, going back over a decade.  When I want to fetch one of my old projects from the archive, I just open up the file.  Sonar will prompt me to locate the missing audio, so I select "copy" and browse to the audio backup directory, and it pulls the files it needs.  Then if I want to save it and keep working with it, I just "save as" to my current project folder and Sonar does the rest.   No need to micromanage. 
 
I'm not really making a case for doing it this way, it's just the way I prefer.  But it works rather well for me. 
 
You know, I just realized, there's a vague sliver of a possibility I might be just a tad nerdy.   :)