Linked by Thom Holwerda on Tue 1st Dec 2009 23:53 UTC
Windows There was a bit of a stink today about an antivirus vendor claiming that Microsoft's November security patches caused computers to show a 'black screen of death'. Microsoft has investigated the issue, and states that the antivirus vendor, Prevx, is wrong.
Thread beginning with comment 397463
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Not an issue?
by msundman on Wed 2nd Dec 2009 13:08 UTC in reply to "RE: Not an issue?"
msundman
Member since:
2005-07-06

It's already well-known that this problem is not an issue caused by Microsoft, but rather the crapware people choose to run or malware they blindly let install.

Of course it's Microsoft's fault, even though MS isn't it's cause. Nothing that normal, non-admin users can run should be able to completely destroy your OS to the point not even the normal recovery tools work. In my case there was nothing blindly installed by any action of the user. Heck, installing malware should never be so easy that users that are utterly clueless should be able to do it. (In ubuntu, which I recommend to all clueless users, it's much easier and safer. If the user can't edit his/her own apt sources then he/she shouldn't be installing, and therefore can't install, anything not already provided by the current apt sources. (One just has to make sure the clickety-click deb-installer isn't provided.))

Edited 2009-12-02 13:10 UTC

Reply Parent Score: -2

RE[3]: Not an issue?
by strcpy on Wed 2nd Dec 2009 13:09 in reply to "RE[2]: Not an issue?"
strcpy Member since:
2009-05-20


If the user can't edit his/her own apt sources then he/she shouldn't be installing anything not already provided by the current apt sources.)


And there is nothing that can cause the system to crap out in apt sources? The same fallacy that Fedora made.

Edited 2009-12-02 13:12 UTC

Reply Parent Score: 2

RE[4]: Not an issue?
by msundman on Wed 2nd Dec 2009 13:27 in reply to "RE[3]: Not an issue?"
msundman Member since:
2005-07-06

And there is nothing that can cause the system to crap out in apt sources? The same fallacy that Fedora made.

I'm not sure what you mean, but there's nothing even remotely similar, no. And if something would cause the OSes of thousands of users to completely lock up then obviously the people making the OS would provide some means to fix it. But not MS.

[The comment preview here on OSnews is seriously b0rken. Usually in such a way that things look good in preview but not in the final version. E.g. nested quotes.]

Edited 2009-12-02 13:31 UTC

Reply Parent Score: 2

RE[3]: Not an issue?
by rockwell on Fri 4th Dec 2009 15:21 in reply to "RE[2]: Not an issue?"
rockwell Member since:
2005-09-13

so if a user operates an object incorrectly and the object malfunctions, it's the object's fault?

Apparently you've never known anyone killed by a drunk driver. Douchebag.

Reply Parent Score: 2

RE[4]: Not an issue?
by msundman on Sat 5th Dec 2009 00:02 in reply to "RE[3]: Not an issue?"
msundman Member since:
2005-07-06

so if a user operates an object incorrectly and the object malfunctions, it's the object's fault?

No. If a manufacturer makes a product such that it's particularly easy for users to render it useless by mistake then it's the manufacturer's fault that so many such products get rendered useless. (Of course the primary responsibility still lies with the one operating the product, but that's irrelevant since this obviously is a case with more than one fault.)

Apparently you've never known anyone killed by a drunk driver. Douchebag.

Nobody drives drunk by mistake.
Along similar lines, it's not MS's fault if the OS fries as a result of the user switching non-hotswap RAMs on-the-fly. That'd be against the specs and not something one would do by mistake.
And there's no reason for name-calling. Try to be civil.

Reply Parent Score: 2