Widcomm.Bluetooth.Software.Drivers.5.1.0.1100

[HackerBabe]

Originally Posted by WIFI

You two guys quit fighting. Be grateful of each others help! Keep on Downloading!

That's the point !
That's the way we're here !
That's the way we need !

[gsmBTjoco]

Great work guys, I just wish widcomm/broadcomm will finally release something working flowlessly. After installing this version my nokia 6680 keeps disconnecting, the sound on my stereo headset started breaking and I don't know what else I am going to find not working properly.... What is your experience ?

[JimmyZ]

hehe, great forum, when i use bluetooth for the first time, the widcomm with the dongle didn't support Windows Server 2003, i have to switch to WinXP... until months later i find some cracks here

even later i bought a new machine and started using Server 2003 x64 edition, then finally the x64 widcomm was uncovered here, great, great phantasm for his/her awesome License Patcher~

[mek15]

Hello, guys. I wonder what is new in this version of the Widcomm/Broadcom driver for BT. Anybody knows? Thanks in advance.

[JimmyZ]

well i dunno, this driver is originally provide for cell-network's 2.0edr usb dongle, but i don't actually have a 2.0edr dongle

[gsmBTjoco]

Originally Posted by gsmBTjoco

Great work guys, I just wish widcomm/broadcomm will finally release something working flowlessly. After installing this version my nokia 6680 keeps disconnecting, the sound on my stereo headset started breaking and I don't know what else I am going to find not working properly.... What is your experience ?

I would like to correct my self for the information above. It was wrong and the story goes like this. The same day I installed v 5.1.0.1100 we moved offices and as I said earlier I had problems with this version, but after reverting back to v 5.0.1.2500, which I new it was working properly for the things I am using it, for my surprise I discovered that 5.0.1.2500 behaves the same way as 5.1.0.1100. Then I installed again 5.1.0.1100 but at home where I knew 5.0.1.2500 worked correctly and voiala it all worked as expected. So it looks like in my new offices there must be some interference in the BT signal from somewhere.... So apology...

[astrics]

So Problems Problems Problems....
Installed this new version, but a2dp does not work with my Bluetake i-phono. Also seems to give me problems with my Deluo BT GPS

Installed Bluesoleil VOIP version, patched fine and works, but not with my GPS and my Sony DCR-IP220 video camera. So it is back to 4.0.21 for me which has worked all along. This has just been a waste of time for now. Ooh well....

Or if someone has workarounds, please let me know by posting here.

[randomjohn]

Stupid question, but when exactly should the patcher be run (and what exactly does it do)?

Here's what I've been doing, that hasn't worked out yet:
Using a DBT-120

1- uninstall the old Widcomms
2- unplug the dongle
3- reboot
4- install widcomm
5- reboot
6- plug in dongle
7- windows xp SP2 does its annoying thing
8- go into control panel, change the CSR driver so it's using the widcomm driver instead of the Microsoft driver
9- watch in frustration as no bluetooth radio is found

Any idea where I'm going wrong?

Thanks in advance

[boto]

A mirror for file:

http://files.filefront.com/WidcommBl.../fileinfo.html

just repack by me without password...all credits to illusion.



PS: this version work fine..


1- Uninstall all previews version
2- Reboot
3- Install widcomm 5.1.0.1100 version (dont need to unplug dongles)
4- if dongle not detect..click in cancel to continue.
5- Open control panel and change microsft bluetooth driver for CSR driver using the "Use Disk" option on driver detction (Sorry for bad english)
6- Click Starting using bluetooth and enjoy.


Works fine here.

[roma0803]

Originally Posted by boto

A mirror for file:

http://files.filefront.com/WidcommBl.../fileinfo.html

just repack by me without password...all credits to illusion.



PS: this version work fine..


1- Uninstall all previews version
2- Reboot
3- Install widcomm 5.1.0.1100 version (dont need to unplug dongles)
4- if dongle not detect..click in cancel to continue.
5- Open control panel and change microsft bluetooth driver for CSR driver using the "Use Disk" option on driver detction (Sorry for bad english)
6- Click Starting using bluetooth and enjoy.


Works fine here.

Does this work for A2DP too?

Thanx.

[boto]

probably yes...try follow all steeps

[i3laze]

lol.. i've got PCMCIA Billiton Bluetooth.. it has native drivers based on Widcomm ~3.0.

Though, license patcher for 1100 doesnt see it, cause it's not usb

Widcomm installs correctly, even detect device, during setup.
But when i click BtTray, it asks for license file.

What's next?)
-----
P.S. i've used licensePatcher from 5.0.2500 in SafeMode, after that widcomm just hang, bttray = white , nothing loads.

[Yolly Zubrick]

You should get the VID and PID and manually enter it in the License Patcher. Then generate a new license file (.dat and.reg). Install as usual.

[i3laze]

Hmm should the PCMCIA have VID & PID ?
In DeviceManager it doesnt display IDs, as it does for USB devices.

[Yolly Zubrick]

Originally Posted by i3laze

Hmm should the PCMCIA have VID & PID ?
In DeviceManager it doesnt display IDs, as it does for USB devices.

I don't have a laptop so I can't verify your claim. But in my Windows XP SP2 system, all detected devices are displaying ID's, so I don't see why a PCMCIA device can't have ID's displayed too. AFAIK, WIDCOMM rely on VID and PID to lock the license to its software. Since your PCMCIA bluetooth came with WIDCOMM, it should have these IDs.

Does Windows XP install the default Windows Bluetooth drivers for your PCMCIA device? What version of Windows are you on by the way? You should at least have Windows XP SP2.