Wii Motion Plus-toshiba drivers not finding remote

[MusicNomad]

So I imagine this is rather redundant, but I am at a loss.

I Have an ASUS laptop with atheros built in (internal) bluetooth. I have a black wii remote plus. Through following the provided tutorials, I was able to connect it to toshiba drivers, play zelda SS for a couple of hours, though when i came back to turn my wii mote on again after quitting dolphin, I could no longer sync it. It seems that even after uninstalling every single bluetooth driver (the original atheros drivers for ASUS on windows, and the toshiba drivers) and reinstalling, the bluetooth still won't recognize it. It perplexes me that it WAS working for awhile, but even after trying things like "wiipair.exe" (which doesn't recognize the wii-mote either), I still can't figure out why it won't even show up. im wondering if it is the wii mote itself, or if my bluetooth stopped working for some random reason. I will try once more going through all the steps, but if anyone has a clue as to why this may be happening, it would be greatly appreciated for some input on the matter.

Thanks in advance.

[skid]

If the bluetooth stack thinks that the device is still connected, it won't pick up the wiimote a second time. From the bt stack software, check if devices are listed as found/detected/connected and remove the device if it has.

[MusicNomad]

If the bluetooth stack thinks that the device is still connected, it won't pick up the wiimote a second time. From the bt stack software, check if devices are listed as found/detected/connected and remove the device if it has.

Understood. The moment I noticed that it wasn't picking it up, I removed it from the list. After that, it refused to pick it up at all. I'm still at that point after uninstalling/re-installing Atheros BT stack, Windows BT stack, and toshiba BT stack. I've tried coupling them, installing them alone and individually. Not sure where to go from here unless I need to "pair" the wii-mote with another dongle separately in order to "clear" it in a sense? I ordered that $2 mini dongle from amazon. perhaps that will work...any other thoughts would be appreciated!

[MusicNomad]

so after much retrying, I re-installed the atheros drivers and turned the "allow bluetooth devices to find this computer" on. Thus, Windows BT stack found the wii remote. Thats a good sign for now. now all i have to do is figure out how to configure this BT stack or switch back to toshiba. i'm guessing toshiba was "piggybacking" off of the Windows BT S? thats why it got the signal in the first place, maybe a fluke. Will update as I trudge on...

---

So I suppose that is the reason why it wasn't working in the first place...it seems that toshiba "piggybacks" off of the atheros or rather windows BT stack. I had to uninstall EVERY bluetooth stack and then reinstall the original built in stack (atheros). From there I clicked "allow bluetooth devices to find this computer" under settings, ran wiipair, paired it up (without any pair code entering, etc.) and then proceeded to install the toshiba stack. After configuring it in toshiba, I successfully paired it to dolphin and am now playing again. I need to test if this sort of thing will happen again, though wiipair should have fixed that...anyway, will update once more if all goes well...





EDIT: Tested again, works perfectly.

[MayImilae]

There is no "piggybacking". However, bluetooth stacks can interfere with one another. Installing multiple bluetooth stacks is generally a bad idea.

Also, wiipair is not necessary for -TR wiimotes. Or any wiimotes for that matter.

[MusicNomad]

There is no "piggybacking". However, bluetooth stacks can interfere with one another. Installing multiple bluetooth stacks is generally a bad idea.

Also, wiipair is not necessary for -TR wiimotes. Or any wiimotes for that matter.

Understood. However, I have recently been playing and after putting my laptop to "sleep" or restart, the toshiba stacks again do not recognize the wiimote, therefore i must uninstall/reinstall the drivers for it to work again. I've even tried disconnecting and deleting the device from toshiba, though with no success. Not sure why this is happening...