 |
WiiLi.org
a new revolution
|
| View previous topic :: View next topic |
| Author |
Message |
Maxious
Joined: 17 Nov 2006
Posts: 26
Location: Australia
Digg It |
 Posted: Sun Dec 17, 2006 2:03 am Post subject: |
|
|
| tadhock wrote: |
Haha, I appreciate seeing what it *should* look like anyway. If you get past this stage, is there any way to tell it's connected? Like, do the LED's stay on on the remote, or is it displayed in a list in 'My Bluetooth Places' or anything?
Also, Maxious, did you get any error when installed the DB-120 drivers with the widcomm stack (like "Internal error 2753. f84988_btins.dll")?
|
When you look at it in My Bluetooth Places, it has a box with two green pointing arrows over the Keyboard+Mouse icon. You can double click on it to get a status window and the data transfered counters go up when you press buttons.
No errors like that. Google seems to suggest that with other programs "Internal error 2753" means there's a problem overwriting a file. So maybe uninstall, clear out temp directories, C:\Program Files\D-Link\Bluetooth Software and all the bt*.dll files in System32 and reinstall? |
|
| Back to top |
|
 |
tadhock
Joined: 15 Dec 2006
Posts: 9
Location: Perth, Australia
Digg It |
| Posted: Sun Dec 17, 2006 8:10 am Post subject: |
|
|
| Maxious wrote: | | When you look at it in My Bluetooth Places, it has a box with two green pointing arrows over the Keyboard+Mouse icon. You can double click on it to get a status window and the data transfered counters go up when you press buttons. |
Damn, mine doesn't show those arrows when it finishes the connection wizard. It gets all the way through like in the video, but isn't connected still  . Seriously starting to wonder if the dongle's faulty - unfortunately, I've got no other bluetooth devices, so I can't really tell.
| Quote: | | No errors like that. Google seems to suggest that with other programs "Internal error 2753" means there's a problem overwriting a file. So maybe uninstall, clear out temp directories, C:\Program Files\D-Link\Bluetooth Software and all the bt*.dll files in System32 and reinstall? |
Yeah, I googled it too and figured it was something to do with old installs, but I've tried cleaning everything out, then re-installing those drivers. The problem is, after uninstalling the DBT-122 drivers, when you try to install the DBT-120 drivers, it gets to the 'Please Insert your USB adapter' message, and won't recognize the adapter (and a windows new hardware wizard pops up in the background). And if you skip the message, and continue, it still doesn't recognize the adapter when you put it in after the install's complete. |
|
| Back to top |
|
|
Imunalia
Joined: 17 Dec 2006
Posts: 9
Digg It |
| Posted: Sun Dec 17, 2006 8:57 am Post subject: Same Problem |
|
|
| I have the same weird issues, I can get my wiimote to connect via bluetooth, but when i fire up glove pie i get nothing. It does however tell me the current battery level but thats it. As for installing drivers for the 120 instead of the 122, the dongle wont work. |
|
| Back to top |
|
|
CarlKenner
Site Admin
Joined: 29 Nov 2006
Posts: 614
Digg It |
| Posted: Sun Dec 17, 2006 12:59 pm Post subject: |
|
|
| The battery level 255 is a bug. That is just what I initialize it to, and one of the few fields that I don't check if the Wiimote exists first. |
|
| Back to top |
|
|
Imunalia
Joined: 17 Dec 2006
Posts: 9
Digg It |
| Posted: Tue Dec 19, 2006 4:52 am Post subject: |
|
|
| Ive exhausted every avenue i can think of at the moment and put in a tech support question with BlueSoleil. I'll keep posted my progress. |
|
| Back to top |
|
|
Melchior
Joined: 16 Dec 2006
Posts: 9
Digg It |
| Posted: Tue Dec 19, 2006 6:00 am Post subject: |
|
|
| Quote: | Following these instructions (and holding 1 + 2 the whole time as CarlKenner pointed out...doesn't seem to work if you don't), I get all the way through to this screen:
There aren't any PIN-entry screens using this method.
However..it doesn't go anywhere from here. I push Finish, the lights on the wiimote eventually stop blinking and go back to all being un-lit, and it doesn't say anywhere obvious on-screen that the remote's connected. |
Then you open wiin remote or, glovepie and run a script. You certandly noticed that the bluetooth logo (bottom-right) had previously, a white storm but now, the storm color is cyan. Wich mean that the device is connected and ready to use. 
It worked perfectlyfor me this way. I didn't tried the dbt- 120 drivers, certandly brings new compatibility issues..
The only thing I don't like with this technique.. is that I have to do this every time I turn on the pc.. |
|
| Back to top |
|
|
tadhock
Joined: 15 Dec 2006
Posts: 9
Location: Perth, Australia
Digg It |
| Posted: Tue Dec 19, 2006 12:12 pm Post subject: |
|
|
| Melchior wrote: | | Then you open wiin remote or, glovepie and run a script. You certandly noticed that the bluetooth logo (bottom-right) had previously, a white storm but now, the storm color is cyan. Wich mean that the device is connected and ready to use. |
It didn't change colour - that was my problem. It went all the way through the steps...and did nothing.
...however, I've now got it working on a different machine (one I tried it on with no luck earlier), using the drivers off the dlink international site specifically for the B models. Not sure why it works now, but I'm not questioning it! Still no luck on the main machine. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
