pwalpwal
so are we seeing a new pattern - monthly releases with intra-monthly patches/bug-fixes? i'm not sure i could keep up with that!

It's really not that hard...    Well, at least some of us like it! 
 
Hey, since it was mentioned previously in a few other posts, isn't this sorta/kinda the methodology "R" follows? 

I've switched to the intermediate release cycle rather than install straght away so it doesn't bother me. If this becomes a regular thing and all the serious release issues get addressed by an intermediate release then then no problems whatsoever..! Happy for all you guys to do the testing!

Attempted to install the updated Splat file:
 
This program can't start because TTSlame.dll is missing from you computer.
 
Guidance, please.

YouDontHasToCallMeJohnson
Attempted to install the updated Splat file:
 
This program can't start because TTSlame.dll is missing from you computer.
 
Guidance, please.

This sounded familiar to me so I searched the forums. In at least two cases, the problem was occurring because Sonar was not be run from the directory where it is normally installed. In one case, the user thought they created a shortcut to Sonar.exe on their desktop but they actually copied Sonar.exe to their desktop. In the other, the person was applying a hotfix but did not extract it to the right location and again, was running the Sonar.exe app from a location other than its normal install location.
 
I don't know if this helps. 

stevec

pwalpwal
so are we seeing a new pattern - monthly releases with intra-monthly patches/bug-fixes? i'm not sure i could keep up with that!

It's really not that hard...

for me it's more about having the time to check stuff out, or learn new features, but then i suppose one doesn't have to install/update the moment new stuff is released

Hi guys,
 
Reading all this, I am wondering if it would be possible to;
 
install both the 32 bit an 64 bit version on my 64 bit system. Could I be updating one version to check it out let say the 32 bit version. And if I am happy I could update the 64bit version. (my production version)
 
Would this work?
 
 

Yes, no problem

pwalpwal

for me it's more about having the time to check stuff out, or learn new features, but then i suppose one doesn't have to install/update the moment new stuff is released

 
Some major positives with the new system that make it safe to update:
 
- You are not forced to update - you can update when you choose to do so and if the new fixes/features are of interest to what you are working on
- Updates are small and much easier to learn since any feature updates per release are fewer 
- If for some reason something doesn't work for you it takes a minute to roll back to the prior version
- If there is a problem we can fix it at worst within a month sometimes earlier
- we get feedback from users much quicker and can respond faster as a result. Also its much easier for us to react to feedback when a feature is just released rather than a year later which was the case in the prior model.
- users are much more likely to be heard

Thanks for your response.
 
Traditionally, I have installed ALL sonar versions into folders on the C: disk: C:\Sonar6, C:\SonarX3,...
 
I thought the CCC would obey the established paths.
 
But, I installed all CCC items as the CCC wanted.
 
The registry should be listing where Sonar2015 is.
 
So, why am I getting the error?
 
 

Noel Borthwick [Cakewalk]
- You are not forced to update - you can update when you choose to do so and if the new fixes/features are of interest to what you are working on

Seems to me a person who has critical projects underway would be best to plan their updates the last week of the month, if they are in between projects then.  It is likely that any critical issues will be settled out by that point.