Post a Comment
I may not be a Microsoft lover but I don't see why MS should be held liable for making an update that would break older apps. (older than the update) Didn't something similar happened with Firefox on a smaller scale?
From the article
"In regards to Sophos, we have only received one support request and we cannot reproduce the issue in our labs. If we can, we will produce a hotfix as soon as possible," said Peter Houston, senior director of servicing strategy at Microsoft.
From linked full article at the link provided
http://www.microsoft-watch.com/article2/0,2180,1839634,00.asp
According to a posting on the SANS Internet Storm Center forums, "a reader reported that "...After applying the patches, some components (either the firewall or protection against unknown threats) on Panda Platinum 2005 Internet Security (9.02.01) stopped working. This happened on my Win2000 laptop (fully patched) and on several WinXP Pro boxes. The solution was to completely uninstall Panda & then re-install it."
So maybe that's the workaround
I may not be a Microsoft lover but I don't see why MS should be held liable for making an update that would break older apps. (older than the update) Didn't something similar happened with Firefox on a smaller scale?
I'm neither an MS-lover nor a basher, but unless there is an unavoidable reason (ie. fundamental security flaw) then I think MS should jump through hoops to make sure they don't break older apps with an update. Doesn't make for a very stable platform if patches and updates break existing applications.
In fairness to MS, often times broken apps are a result of those third-party companies using un-documented or un-published API's which may change with a patch or service pack release. ZoneAlarm got stung with this on a Win2K service pack release a while back, and had to revise their code. So in cases like that, it may not be fair to hold MS responsible.
You're right too, this did happen to Firefox with 1.05 breaking certain third-party extentions. And their response was to politely apologize for the inconvenience and quickly release 1.06 to address this. Ideally of course, 1.05 wouldn't have broken compatibility in the first place but one has to respect that they chose to admit and address the problem rather than expecting the third-party extension makers and their users to deal with it.
On the windows front, I run Windows2000, and after the most recent batch of security updates, I've noticed that my Digital Camera software (which ships with my Canon camera) ArcSoft Image whatever takes forever to start. Probably calling home using or whatever. So who do I blame?
Luckily, with Zeta I dont have these issues.
So the companies running Windows 2000 have two options:
1) Upgrade to XP (until the next XP update comes out which breaks third-party AV products) - Microsoft wins.
2) Dump third party AVs and only use Microsoft AV - Microsoft wins.
Actually, you'll need XP to use the AntiVirus service when it's fully released, similar to their anti-spyware apps. So this will actually be an opportunity for the third-party vendors that are willing to make sure they keep their support of Win2K strong.
"I may not be a Microsoft lover but I don't see why MS should be held liable for making an update that would break older apps. (older than the update) Didn't something similar happened with Firefox on a smaller scale?"
Yes, but Firefox and Linux are free software, with open source code. Binary incompatibility can be resolved with simple recompilation of source code or free (zero cost) updates to the last version.
This is a situation EXTREMELY DIFERENT than those of poor windows 2000 and other windows users.
It was security software that broke, most of it was nothing more than fuzzy feelgood WORTHLESS security software I might add.
Think about it. What does a software firewall on windows really do to work ?
It hacks system DLLs and does some totally off the wall shit to integrate itself with the TCP/IP stack on the system. Yes updates might break an application like that.
The applications listed that broke are close to malware anyway.
I applied the rollup on a Windows 2000 server and it broke printing. I removed it and still broken. Other people on the net are having the same problem.
So finally after wanting to thorow the computer out the Window, I moved the printer to the new MAC, and it works great, no problems.
I think I am finally done with Windows at home. Guess I will just have to put up with it at work. The MAC gives me no problems and just works.




