Solved::Jamaica Plain installed it's FX with mapped drive as thier path.

I updated my 32 bit win7 dev machine to Jamaica Plain last night.
Upon first launch I got a flurry of "corrupt image" dialog boxes one after the other for each of the effects that are shipped with Sonar, Blue tube stuff etc.
 
Each of the effect paths were s:\program files.......\effect name.dll
Where S: is our home NAS server which is a mapped drive.
 
This drive map has been connected and present for each of the updates since the first one.
This is the first time this happened.
 
The install path should have been c:\....
For the effects
 
The program runs fine after that episode with 30 or so error dialogs.
 
So.... yeah.
 
 

I PM'ed you with the jpg of it as we cant upload from our computers here. only from url afaik

I updated from IPSwich to Jamaica mon.
 
We know what we're doing over here. CCC does it all for us anyway.
There is little chance we can mess it up.
 
Something went wrong with the installer. s:\... is also the wrong path.
 

You need to adjust CCC and Sonar (Edit -> Prefs -> VST Settings) to your actual file paths.
Then do some plugin housekeeping if necessary (split 32 bit folders from 64 bit folders), get Sonar to ignore 64 bit folders.
I've seen CCC reset the file paths every now and then (last time was about 4 releases ago).

Cheers..

bitman
Nope.
 
Nice avalanche of wild guesses again though.

No wild guesses here, you have a 32 bit application pointing to a 64 bit DLL and that's not going to work so you are going to need to sort it out and I've given you advise on how to do it.

I'm only trying to help, I even sorted out that image for you. If you are going to criticise me afterwards I suggest you come up with your own solution.

Cheers.

I'm only trying to help

 
Don't anymore ok Doc?
 

That's weird. The installer should be using the paths in command center to install plugins so I'm not sure how it would even know about your S: drive. Maybe those Jamaicans have a problem with you :)
We'll look into it.

Beepster
Just seems weird it would throw those errors but still work anyway.

bifilter2X64.DLL (see the image I bothered to upload for him in #4) is a 64 bit DLL and he's running in Sonar in a 32 bit app. So Sonar should not load it when scanning and just throw a warning ("not designed to work in" [32 bit] "Windows") by design. Sonar should continue to work without the 64 bit plugins loaded.

You know they do Noel. ;-)
 
@rivers88.
 
Sorry, man. It's been an ongoing battle of wits with the good Doc for a while.
 
 
 
 
 

Beepster
That doesn't explain why it's referencing his server drive. Based on his file paths and his previous experiences with CCC nothing should be going to the s drive at all.

Right, that does answer why  he is seeing "corrupt images" though (see his post #1).


As stated in post #7 I've seen CCC screw up the file paths in CCC, and not only that in Sonar itself, consequently I always double check the paths nowadays before and after upgrading (in ccc and Sonar preferences) mainly out of paranoia, but this has not happened recently. When it did happen I had to clean it up manually of course.
 
Anyways apparently I'm some sort of ahole for saying all this and trying to help. So moving on...

I was merely suggesting a possible reason for the s drive shenanigans. Never called anyone an ahole AFAICT.
 
This is one of those reasons I don't use any auto doohickeys (including CCC) at all on my DAW. Probably wasting a lot of my own time unnecessarily but at least I can control/see where everything is going/what is happening.
 
Not so coincidentally I've never had a problem with CCC as a result. lulzity

Wait no it's not fixed. I went back to relaunch Jamaica  and got the image errors again.
Bizarre.

What I would do, and remember I'm a dum dum, is go into the Sonar VST scanner's file paths to see if anything in there is pointing to your s drive.... AND I would go into the s drive itself to look for any plugin/Cakewalk/whatever files that should not be there.
 
Sonar is reaching out to the server drive for a reason. It thinks something it needs is there. Disconnecting it probably just removed the path from the scan automatically and once you hook it back up again it'll start hunting again.
 
Again I say... irdum... just making suggestions of where I would look first.
 
Edit: and of course if you do find any paths or files that should not be make them not be anymore (delete them).