CakeAlexS
Sonar patches call C++ updates. I wouldn't load another update till X2B whereby another C++ update may be installed.
+1000 for this one.
Just to add a little "why" to this: Say Cakewalk is using version 1.3.0231 of the C++ libraries to develop Sonar and distribute that version's redistributable with Sonar. Next you install VSampler (just a name I picked out of thin air) which hasn't been updated in a while and was written to version 1.2.812 of the C++ libraries and installs that version of the redistributable with VSampler, could potentially cause a problem. Also, say you install SlickerThanSlicedBread Compressor which uses version 1.3.4821 of the C++ libs and redistributes that with their product, it will overwrite the versions used to create sonar and potentially create a problem. This is not Cake's fault, VSampler's fault or STSB Compressor's fault.
This is Microsoft's fault. This problem has been plaguing windows systems since Windows95 with MSVCP versions being downgraded by installing older software or upgraded by installing newer software to the point that it sometimes breaks Windows as well as some previously installed application.
They have sort of resolved this, somewhat, by at least providing different libraries for their major releases (i.e. MSVCP5 for version 5, MSVCP6 for 6,etc) but unfortunately with bug fixes and windows updates, even a supposed sideways move from MSVCP7.231 to MSVCP7.243 could potentially break software if either a bug that was counted on is now "fixed" or a new bug was introduced.
And to the doubters that say "it is not possible that installing sonar (or any other application which updates system-wide libraries for that matter) broke windows", think again. This particular scenario makes it completely possible if a driver manufacturer wrote their driver software with MSVCP7.231 and now after sonar, it is MSVCP7.243 or any other possible disparity between the lib used to develop vs the currently installed runtime lib version, could potentially break their driver and/or service which could potentially end up in a BSOD and prevent booting.
Again, not Cake's fault, not the hardware or manufacturer's fault, but good ole Microsoft. But don't believe me. Just do a quick google search for "msvcrt version resolved" or "msvcp version resolved" and read through some of the 1.2 million results regarding this particular issue. I've been complaining about this for quite a while that sandboxing apps to have their required libs in their own space and leave the \windows\system32 versions alone, would probably resolve at least 25% of the BSOD's of the Windows world. As would differentiating between drivers required for windows to boot (a la safe-mode) and drivers for other pieces of hardware which should loaded in a separate memory space and not be allowed to crash the entire operating system. If I need my files, I don't care if the bluetooth driver has a problem, just get me to my files. Unfortunately, instead of concentrating on these difficult to solve problems, MS presents us with Metro.
Sorry for another rant in the same thread. Just a real hot button issue for me. Hopefully somebody appreciated the little bit of enlightenment.
Best,
guitardood
P.S. My apologies to JamesYoYo for kind of hijacking your post.