UNSOLVED

ericmt

updated

19 years ago

Closed

E

ericmt

10 Posts

0

6283

April 17th, 2007 10:00

usb wireless mouse help

I have a new e1505 (two months old) and bought a new Microsoft wireless mouse 3000 for it and it was working fine until yesterday. I plugged in the USB receiver and the mouse wouldn’t work or would just skip and freeze and then totally stop when I tried to use it. When I plug it in the computer it makes the little jingle that its connected and it also shows up in the device manager that its there. I tried a different USB port with the same results. I reset the receiver and mouse buttons but it still didn’t work. One thing I noticed is that the USB receiver was getting hot after being plugged in for only 30 sec to a minute. Then after an hour I plugged it in again and now it works fine. Does this seem like it would be a bad USB mouse receiver or do you think a bad board would cause this?

  • DieCast61

    52 Posts

    654

    0

    Posted April 17th, 2007 15:00

    Try changing the battery.
  • ericmt

    10 Posts

    654

    0

    Posted April 17th, 2007 16:00

    How would the battery effect it? This is a brand new computer.
  • DieCast61

    52 Posts

    654

    0

    Posted April 17th, 2007 16:00

    Battery in the wireless mouse!
  • ericmt

    10 Posts

    654

    0

    Posted April 17th, 2007 18:00

    I did change the battery in the mouse. No diff.  I just exchanged the mouse for a new one. I think the receiver went bad or funky.
  • ericmt

    10 Posts

    654

    0

    Posted April 17th, 2007 18:00

    Do you have any idea what would cause the mouse receiver to heat up so quick when I plugged it in. I tried all the usb ports with the same results. When I tried it an hour later and the mouse worked it did not heat up at all. Would this be a sign of a bad receiver? What controlls the usb ports. Would I have a bad motherboard?
  • ericmt

    10 Posts

    654

    0

    Posted April 18th, 2007 10:00

    I exchanged the mouse for a new one and it works fine. Must have been a bad usb receiver. Thanks for the help.