XP doesn't see Mobile Mouse 3000

[xqqqqme]

Just yesterday I received my MSI Wind U100420US (this version does not have
Bluetooth) with Windows XP SP3...and today I went out and purchased a MS
Wireless Mobile Mouse 3000 for it. As soon as the receiver went into the USB
port, XP announced that it had found the new hardware. But the mouse won't
work (yes, I installed the battery)...the cursor won't move and clicks do not
register.

According to the info in Control Panel>Mouse (including troubleshooting), XP
says the device is there and working properly. Only, it ain't. I tried
moving the receiver to the other USB ports and got the same results.

Why/How could everything look so "positive" and produce no sign of a
functioning mouse?

 

[smlunatick]

Just yesterday I received my MSI Wind U100420US (this version does not have
Bluetooth) with Windows XP SP3...and today I went out and purchased a MS
Wireless Mobile Mouse 3000 for it.  As soon as the receiver went into the USB
port, XP announced that it had found the new hardware.  But the mouse won't
work (yes, I installed the battery)...the cursor won't move and clicks donot
register.

According to the info in Control Panel>Mouse (including troubleshooting),XP
says the device is there and working properly.  Only, it ain't.  I tried
moving the receiver to the other USB ports and got the same results.

Why/How could everything look so "positive" and produce no sign of a
functioning mouse?

Did you try on a different PC?

Did you try to "re-sync" the signals, by pressing the small "Connect"
button on the mouse?

 

[xqqqqme]

Did you try on a different PC?

Did you try to "re-sync" the signals, by pressing the small "Connect"
button on the mouse?

I didn't try it on another PC, but what I did do was plug in a wired mouse
to the same USB port to make sure there was no problem there (it worked).
Ultimately, even though I had no idea that a "re-syncing" was necessary (note
that was passes for docs with this product makes no mention of this and
describes installation as literally a plug-and-play proposition), I started
fooling around with both the button on the receiver and the button on the
mouse. All I knew was that these buttons pushed against each other when the
receiver was stored in the mouse and turned off the power. But, as I can
tell you know, after a couple of presses of each button, the pointer jumped
to life on the screen. At the time, I had no idea what, exactly, I had done.
But from your reply, I now know. Is this something that needs to be done
regularly?

 

[smlunatick]

I didn't try it on another PC, but what I did do was plug in a wired mouse
to the same USB port to make sure there was no problem there (it worked). 
Ultimately, even though I had no idea that a "re-syncing" was necessary (note
that was passes for docs with this product makes no mention of this and
describes installation as literally a plug-and-play proposition), I started
fooling around with both the button on the receiver and the button on the
mouse.  All I knew was that these buttons pushed against each other when the
receiver was stored in the mouse and turned off the power.  But, as I can
tell you know, after a couple of presses of each button, the pointer jumped
to life on the screen.  At the time, I had no idea what, exactly, I haddone.
 But from your reply, I now know.  Is this something that needs to bedone
regularly?

Yes and No. You need to only re-sync when the mouse does not
respond. It has been noticed that the signals can get mixed up in a
"noisy" environment (quiet for human ears, noisy for computer wireless
devices.)