All three of you read this carefully.
The original battery is ancient history and three new NIMH batteries have
dome their best to make the mouse work again.
Something in a Vista update slipped malicious code into the mouse through
it's bluetooth port. This is 'extremely' a well understood exploit - 15
minute blurb on it on the news last week. The mouse is messed up pretty bad.
No more battery talk.
Does any tech have any idea how to do a really effective (and safe)
low-level hardware reset of Microsoft Wireless Laser Mouse 8000?
Sensible answers.
Mark
Peter wrote: [boyscout battery basics]
Computer & So... wrote: [repeat of Peter's good will]
samoila_mirc... wrote: [repeat of peter's good will]
"mark" wrote:
Quote:
> Subject: Problem Laser 8000 Bluetooth Mouse
>
> Message: When the mouse is put on the charge pad its green light pulses 8
> times slowly. Then a red light flashes continuously and rapidly. The
> mouse's NIMH battery does not charge except for a few minutes of use. Even
> when the mouse is left on the pad overnight. This problem started early in
> August when a Vista update included a prompt to update the mouse driver
> software with a download from Microsoft. The Microsoft download was run
> and stopped itself with a note that the driver was not compatible. Thatt
> is when the mouse stopped charging properly.
>
> Then late August another Vista prompt to download the updated driver for
> the mouse, and this time the driver installed. However, the mouse
> continues to fail to charge except for less than a minute when it is first
> placed on the charge pad.
>
> The mouse battery charge anly lasts a very short while. If I take a half
> hour to reseat the mouse on the pad every time the rapid red blinking
> occurs, I can slowly build up the charge. The slow green pulsing lasts
> about 30 seconds, so in half an hour the mouse is reseated on the charger
> pad 60 times.
>
> Microsoft can direct me to a safe driver update, please. That would be
> greatly appreciated. It would be really appropriate if Microsoft would
> correct the error in its driver update for the Laser 8000 mouse (date of
> manufature, 2007).
>
> Mark Stewart, August, September, October 2007