The Notebook Review forums were hosted by TechTarget, who shut down them down on January 31, 2022. This static read-only archive was pulled by NBR forum users between January 20 and January 31, 2022, in an effort to make sure that the valuable technical information that had been posted on the forums is preserved. For current discussions, many NBR forum users moved over to NotebookTalk.net after the shutdown.
Problems? See this thread at archive.org.

    Bluetooth Mice paring issues

    Discussion in 'Accessories' started by gintor, Nov 17, 2010.

  1. gintor

    gintor Notebook Evangelist

    Reputations:
    5
    Messages:
    478
    Likes Received:
    0
    Trophy Points:
    30
    Chaps just a little anoyance i found out with my MX17 R2 and my Orochi bluetooth gaming mouse. If you have other mice and experience the same problem i would try the fllowing:-


    My Orochi worked fine via the USB cable and blue tooth untill an OS refresh.

    All my issue started after i had done a windows reinstall after setting Raid 0 up on my MX17 R2. I updated the adapter with the latest Broadcom Widcomm drivers/software and Bluetooth stack, to try and see why i was unable to reconnect the mouse. it seems this confused the Razor Orochi as it already had my bluetooth stack MAC address within its own memory. After days of messing with it all I needed to do was pair it with something else to wipe the old pairing info and then pair it with my old adapter in my MX17 R2 one more time. Basically, the mouse will not work with the same adapter it has once before been paired with, or the same USB dongle in two different PCs because they both think that they are still paired even though only one OS is aware. . The solution was to pair it with ANOTHER Bluetooth adapter and then pair it with the original one in on my laptop. I used my my PS3.
     
  2. Pitabred

    Pitabred Linux geek con rat flail!

    Reputations:
    3,300
    Messages:
    7,115
    Likes Received:
    3
    Trophy Points:
    206
    What probably happened is the mouse recognized the adapter on your computer as being the same, so it was already authenticated, but the adapter on your computer didn't think the same thing. So they got upset at each other. Your solution is all you can really do, as it forces the mouse to basically reset all of it's saved connection info.