Chrismax: I've read with envy your 29/2/04 post. I have the same problem, with slightly different versions: XP Pro, DBT-120 B3 ver 3.30, 1.41.6a on the installation disk. I tried your recommendations (clean up registry, install 1.41.10a as upgrade, make sure all inner loop software is disabled (anti-virus, firewall etc), switch USB slots), but it hasn't worked.
(When you say you cleaned up the registry using tools, which tools do you have? I don't have special tools, I started regedit and erased a couple of keys containing "WIDCOMM").
By now D-Link should've had their act together; do you have any suggestions for help? TIA
TuneUp Utilities and Ace Utilities. I like both of these applications and both have recovery functionality so that I can restore any changes made to the registry.
I NEVER use regedit.
Be careful with any registry utilities. They are powerful tools and can easily wreck your registry as fix it!! Review all entries identified as a problem to ensure accuracy. Always create a restore point or make a backup of your registry before making any changes.
For those of you trying to get this to work with XP and SP2 (this was done on a clean install), in the device manager under "Bluetooth Devices" Microsoft puts in a generic Bluetooth radio driver. If you've already installed the 1.4.2.10a driver, it doesn't override this Microsoft driver because the Dlink one is unsigned. You need update this driver, choose from a list or specified location, choose the driver to install and then it should come up with a list that has both the "Gerneric Bluetooth Radio" and the "D-Link DBT-120...". Once this is done, the Dlink drivers seem to finallize the install and it takes a few minutes while it sets everything up. I had the same problem other people had with the dlink bluetooth adapter not being recognized and always getting the red icon in the system tray until I got to thise thread which gave me a few ideas. Hope this helps.
Scott884, thanks for that tip about upgrading the driver in Device Manager. As soon as I explicitly selected the DLink driver, my device was detected.
Now my only problem is that I can't connect to it because of an incorrect securihttps://cdn.geekzone.co.nz/images/ico6.gif
https://cdn.geekzone.co.nz/images/ico6.gifty code!
Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly
to your computer or smartphone by using a feed reader.
