After scouring the internet to find a way to get my no-name bluetooth dongle to work with my Vista laptop, I finally resorted to using what appeared to be the most closely related driver from the list, and fortunately, that seemed to work well enough.
When Windows Plug and Play detects my dongle, it identifies the device as BCM92035DGROM. Now I had previously had success on XP SP2 by modifying bth.inf in C:\Windows\inf, and merely adding a line with the device ID reported by the device manager. (This information was provided by a blog post that I managed to find by searching on the device name).
After trying numerous times to get Windows to recognize my device, I decided, in sheer desparation, to simply go for the closest match listed in the Broadcom section of the bth.inf file, when looking through all devices in the driver database.
This option came up only when right-clicking on the device in the device manager and choosing Update Driver Software… and choosing â€œBrowse my computer for driver softwareâ€.
On the following dialog, I chose the â€œLet me pick from a list of device drivers on my computerâ€ option, which didn’t appear in the usual Plug and Play wizard.
After that, I chose All Devices and clicked â€œNextâ€, from where I could select Broadcom as the manufacturer, and BCM2033 as the device.
Although not the same device, I was able to send files from my laptop to my phone, which is all that I really wanted. I subsequently ended up with a whole lot of unrecognized hardware in my device manager, but that’s not my worry for now.
The moral of the story is, if I had to guess, that one should be careful of these no-name brand devices, and at least make sure that you get an install disc with it, or don’t misplace it if you do have one.