Help with Bluetooth on Windows 7

I recently bought a logitech mx5000 keyboard from a garage sale, however, I don't have the rf dongle that came with it so I decided to connect via bluetooth. I have a D-link DBT-120 rev A1 dongle which has worked great for me in the past, however, I can't get the drivers to install.

By default windows labels it a "generic bluetooth device" and then puts a flag next to it with an error code 43.

I tried installing the widcomm drivers for 7 from their site but the installation hangs when it says "please plug in or turn on your device now..."

I have my device plugged in and I even uninstall the useless "generic drivers" before I start the program but no luck.

I also did pick up a dongle from the sale I thought went with the keyboard (and it even comes up as RF combo device in device manager), however, I'm not sure what it goes to.

Only markings are the logo of a little guy running and the model number: TSHG-2402

Any help is appreciated, as I've already spent too much time trying to figure this one out...


Oh yea, I did enable bluetooth in services :-)

Alright, first I tried the D-Link drivers on the site but got an error message:

"Your WIDCOMM Bluetooth Software license does not include use on this operating system.[-350]"

This was even with every possible combination of compatibility mode.


Next I tried the 7 drivers I got off this site:

http://www.broadcom.com/support/bluetooth/update.php

and ran those (not in compatibility mode) and the setup starts then hangs on the first step when it can't detect the bluetooth dongle.

It says "Please plug in or turn on your Bluetooth device"... but I've tried every usb port... all the same

I think this happens because windows gives it a code 43 right when I plug it in (because it's missing drivers) and then this program which installs drivers can't find it... stupid infinite loops lol

Any other ideas are appreciated.


I think what I need to do is find a way to force drivers (64 bit windows 7 compatible) on before I plug it in... then maybe windows will not disable it right away with a code 43... but I can't find where those drivers might be...

man is this frustrating...

Thanks, I'm looking at it right now and I might bite the bullet for $15...

Aside: I read this in a review and laughed...

"Windows 7 was designed with bluetooth connectivity in mind, so it should work well with most devices."

My dongle is 2.0EDR USB 2.0 ... not that old and it will not work for anything...

Ok, I called tech support and they say the dongle is too old to support 7 so I guess that ends it :-(

I tried xp drivers, vista drivers... everything. If the drivers installed they did not see the device. if they didn't install ...well they just didnt lol


I got 64bit Toshiba drivers working but they do not see the device and device manager looks like this:

Bluetooth:
-Bluetooth RFCOMM

Bluetooth Radios:
-Generic Bluetooth Adapter


if only I could get the darn adapter to show up under "Bluetooth"...

Just to bring closure... I bought a $2.34 (with free shipping) dongle off of DealExtreme and it works great... plug and play like it should have been all along.

My advise is don't waste time with it... I tried almost every stack available and no luck. Just grab a new dongle for cheap and your good to go :-)

Actually, while I had Windows 7 RC on my machine (64-bit), I had used the Broadcom drivers from the http://www.broadcom.com/support/bluetooth/update.php site without any problems - this gave me the ability to stream audio to my Bluetooth stereo headphones.

Now that I have installed Win 7 RTM 64-bit, the Broadcom install gives me the aforementioned "Please plug in or turn on your Bluetooth device" message. Haven't yet figured it out.

I noticed on the Broadcom site that they mention it is compatible with "Windows 7 (RC), Windows Vista, Windows XP, or Windows 2000 operating system", but it does not indicate it is compatible with Windows 7 RTM. I had heard that Microsoft has their own streaming audio technology coming out, so I wonder if they have deliberately crippled the bluetooth audio. Call me paranoid, but crazier things have happened.