While that doesnt make sense w/ resetting the mouse etc,  you as a fellow
software developer have to admit that sometimes there are bugs that are
created from things that just dont make sense.  Especialy when you start
dealing with memory corruption bugs, if you have any experience in a
langauge with pointers.

Plus microsoft isnt only responsible for the update, but they are
responsible for the operating system too so if hes having problems with his
mouse locking up and having to reboot etc, and it isnt a hardware problem,
and it isnt a 3rd party driver or software problem, thats still MS's problem
one way or another :P

----- Original Message -----
From: "Eric Peterson" <[EMAIL PROTECTED]>
To: "RBASE-L Mailing List" <[EMAIL PROTECTED]>
Sent: Friday, August 15, 2003 2:03 PM
Subject: [RBASE-L] - Re: New Worm


This is precisely what I'm talking about.  "two or three reboots
followed by resetting the mouse to another setting and then back ...."
That makes absolutely no sense.  Computers are logical devices.  They do
yes or no (1 or 0).  They don't do 'maybe'.  There aren't little
gremlins or lemmings in side your system jumpering a solder contact on
your ps2 port for which 3 reboots will cause them to drop the cables.
Something else is wrong.  You might want to start at the root of the
problem (your hardware, and it's drivers).  A logical thought process
needs to be applied to this rather than "installed Microsoft update,
mouse bad, Microsoft bad".

Again, a software developer cannot possibly account for everything and
circumstance that is out there.  If 20 people say 'works for me' and 1
says 'screwed me up' chances are high that you have a problem other than
your update.

Eric Peterson
All your Rbase are belong to MS



-----Original Message-----
From: Bernie Corrigan [mailto:[EMAIL PROTECTED]
Sent: Friday, August 15, 2003 3:04 PM
To: RBASE-L Mailing List
Subject: [RBASE-L] - Re: New Worm

> I have never had a problem with a bad update.

I sure wish I could say that.  Nearly every time I download
either a M$ or a Symantec update my mouse freezes up and I have
to do two or three reboots followed by resetting the mouse
to another setting and then back again to the original settings.
I get screen flicker on monitors running off notebooks.  That
involves the same resetting of everything.

I dread software updates from either M$ or Symantec.

Symantec has suggested several registry edits to solve this
problems.  What joy.



At 07:35 AM 8/15/2003 -0700, you wrote:
>Nicky,
>
>You hit the nail on the head.  That is why I have my computer set up to
>automatically alert me to critical updates.  If I come into the office
>and there is one pending, I take the time to let it download and
>install. After a reboot I am back in business.  I have never had a
>problem with a bad update.
>
>I also have my antivirus software set to automatically update so I
>don't have to worry about that.  It does so in the morning before I get
>to work.
>
>And I have Zone Alarm installed.
>
>Dennis McGrath
>
>
>--- Nicky Avery <[EMAIL PROTECTED]> wrote:
>
>---------------------------------
>
>
>Eric Peterson wrote:
>
>How aboutthe Microsoft Security Bulletinlist?  If you were on that
>list, you#8217;d have known about this exploitandpatch a month ago.
>
>
>
>
>Eric,
>
>Had you considered that, while keeping up with the almost dailysecurity
>hole plugs and other patches is your work and you get paid forit, for
>most of theother people on this list, all these issues prevent them
>from gettingon with their work and getting paid for it?
>
>Nicky
>
>

Reply via email to