Re: Microsoft confirms OneCare zaps Outlook, Outlook Express e-mail -- PCTECH

I disagree that the response in either hysterical or not warranted.

No, we only blame evil Microsoft, and we scream and cry like 2 year
olds who can't have another cookie.  The sky is falling, and it is all
Microsoft's fault.


Number 1: it is Microsoft's fault. 
Number 2: a 6 week old report is pretty old report
Number 3: of all of the software that should have been tested after the
product ran on the test system, all Microsoft products should have been
tested first.
Number 4: far be it from me to point out that 99% of the users don't read
the pages and pages of license agreement, nor do they read the "readme" and
backup your data first. 

They have a completely unwarranted trust of Microsoft. Why? I don't know. To
say that any reaction is an overreaction isn't giving the simple answer it's
due. 
Be prudent. Test your product. Don't allow it to hurt me. Don't make me
protect me from you.

JMHO
John Brandt
iStudio400.com


-----Original Message-----
From: pctech-bounces+pgmr=experts.tzo.com@xxxxxxxxxxxx
[mailto:pctech-bounces+pgmr=experts.tzo.com@xxxxxxxxxxxx] On Behalf Of Tom
Jedrzejewicz
Sent: Thursday, March 08, 2007 11:56 AM
To: PC Technical Discussion for iSeries Users
Subject: Re: [PCTECH] Microsoft confirms OneCare zaps Outlook,Outlook
Express e-mail

I don't disagree that it is a problem, I disagree with the hysterical
nature of the response.  Particularly from those of us who should know
better.

I keep coming back to the Chicken Little fable. There is so much
hysteria in the world today; why do we fall for it and make the
situation worse?

My presumptions are to give people credit and the benefit of the
doubt, and to assume intelligence and competance until compelled
otherwise.  There doesn't seem to be enough here for that.

On 3/8/07, Chuck Lewis <chuck.lewis@xxxxxxxxxxxxx> wrote:

You've GOT to be kidding TOM. I have NEVER introduced any bug into any

piece

of software that would cause users to get that doomed feeling like this

one

did. And early on no one knew how to recover from it.


Part of my point is the difference between FEELINGS and ACTUAL IMPACT.
 In fact the actual impact is tiny; no data is lost and the recovery
is easy.  We need to be rational about this, not ratchet up the
emotional intensity and angst.

And by the way, shouldn't the user be taking BACKUPS of their data,
particularly if it is important enough that losing it produces such
feelings of doom.

No, we only blame evil Microsoft, and we scream and cry like 2 year
olds who can't have another cookie.  The sky is falling, and it is all
Microsoft's fault.

As to the perfection of your programming .. you never introduced a
report that mis-stated sales and produced a heart flutter in the VP,
or an inquiry screen that did arithmetic improperly and showed the
wrong quantity available causing a customer to be promised something ,
or a change that locked an order so that it couldn't be shipped, or a
change that wrote incorrect GL entries and gave the accountants
heartburn?

Could you maintain such an excellent record when you have to test for
an infinite number of hardware and software combinations, and respond
instantaneously to malware and viruses on a daily basis.

And this has been an issue for 9 months and still not fixed.


Yes, but there is no data loss, and the repair and workaround are well
known, easy, and quick.  I completely understand why this has not
percolated to the top of the queue when there are new vulnerabilities
introduced daily.

Yet still the response is hysterical, as if this problem was causing
re-formats of the hard drive, sending out nasty emails, or requiring
lots of time and money to deal with.  We need to save our outrage for
a real, serious issue.

He who lives in a glass house ...

I stand by my position.