On the corrupted project file - get VB3 back where it belongs (and/or delete it entirely) and with any luck you might find the project now loads.

Very helpful thanks... So as I am reading your explanation, there is no need to remove the other 32 bit dll's in the 32 bit folder, even though I use the 64 bit version of Sonar X2 and all of my plug ins (other than this one) are 64 bit. What you are saying is that Sonar will load both the 64 and the 32 bit versions of the same plug ins and run fine...? Thanks for taking the time to respond R

Your 32 bit VST's will be fine.
Sonar "ignores" the duplicates, I think that's right.

Tom

RMCALL:

Keep 64 bit stuff under "program files" and 32 bit stuff under "program files(x86)" and you should be fine.

If you load a 32 bit plugin into 64 bit Sonar you get a little jack plug graphic in the top left of the vst window indicating the plugin is bitbridges to 64 bit if I remember rightly. There may well be other ways to tell them apart as well, but I haven't any 32 bit plugs installed myself so can't check.

One other way outside Sonar (assuming you're running 64 bit Sonar) would be to load the plugins you are using in the project then run Windows task manager and see if bitbridge.exe is running. If it is, then at least one loaded plugin is 32 bit.

Thanks you everyone for the help this has been very useful

Since the subject has come up...
 
I got Chromaphone (after having talked myself out of getting yet another synth when I haven't really learned the ones I already have - but arrgh!, that $20 off coupon snagged me in a vulnerable moment).  I downloaded and installed it, and it turned out that Sonar would only add the 32-bit version in the plugin manager list.  I thought I had pointed it to all the right folders so it would find both the 32- and 64-bit versions.  Anyway, I finally resorted to renaming the 32-bit dll with a bogus extension so it wouldn't load at all, and only then would Sonar use the 64-bit version.  Weird...

This is very interesting.  For a long time, I had 32-bit v 64-bit confusion (meaning that it was tricky to make sure Sonar found the right dlls).  I also theorized that using a mix of 32 and 64 bit plugs-ins was affecting memory utilization, although some have told me that cannot be so.  I also attributed some crashes to this same cause.

Recently, Sweetwater upgraded all my remaining 32-bit plugs to 64-bit and I no longer need bit bridge, so this possible cause is now eliminated.

I am obviously not helping you solve the problem.  I am just saying that I think there is an issue deep in Cakewalk code.