View Full Version : Broadcom Software Update (5.1.0.2300)
Go to:
http://update.broadcom.com/BTWUpdate/iedownload.asp
Download and run:
http://update.broadcom.com/BTWUpdate/downloads/btwinitialupdate.exe
You will have something like that in %temp% directory folder
ce2a5341-a490-4d79-8d9c-af903dd97aae.exe - 18,1 MB
It updates you drivers to 5.1.0.2300
You can grab it here:
http://rapidshare.com/files/782916/BTW_5.1.0.2300.zip.html
Ready to install v5.1.0.2300
adisor19
10-26-2006, 23:19
Whoa, this is an interesting development coming from Broadcom! :eek: But it looks like that little update program actually CHECKS to see what dongle you have and updates the software ONLY if the dongle manufacturer has paid them $ for the licence.. oh well, as long as we can still extract the executable installation thanks to the IE installation like pointed by miro68 above, it's allll gooooood ;)
Thanks for a GREAT post miro68 !
Adi
adisor19
10-27-2006, 03:19
So, has anybody tried it to see if it works with CSR based dongles ? :D
Adi
I have tried it. I have two ISSC dongle. and one can install, and the other can't. license patcher 1.8 & widcomm patcher V2 can't work with this version. I think phantasm or bbsc should be some busy now &_&
Hmmm, even this version doesn't work well with my microsoft keyboard, logitech mx900 mouse, and logitech bt stereo headphones. If my headphones are connected and playing, weird things happen to my keyboard and mouse. They go in and out of connectivity.
The bluesoleil stack works much better.
I downloaded the software. But it does not recognize my Bluetooth device. Is the software restricted to Broadcom devices only ? Any work around ? After installation the icon in task bar is red. Please help.
Yolly Zubrick
10-28-2006, 01:56
So, has anybody tried it to see if it works with CSR based dongles ? :D
Adi
It will install after the "magic ingredient" of Phantasm. The dongle (CSR) can be recognized. BUT, it WILL NOT pair. So I guess it still doesn't work. Using the shortcuts in Windows Explorer, it has trouble displaying the dongle's services. The PC will get stuck, and after a while it will give a license error.
So my conclusion: Yes I think this version has CSR support, but we need a new formula for the "magic ingredient" to make it work. I hope Phantasm can look into the new version.
:D
I just installed it over the .1700 version for my Dell Truemobile 355 Broadcomm based internal bluetooth device, it's inside my laptop. Installation went flawlessly, no need to re-run the license patcher or anything. My stereo headset still works so I'm happy.
Are there release notes to say what it fixes etc?
I think phantasm or bbsc should be some busy now &_&
My patcher works OK with this distro.
But from the other side, the driver doesn't work with SiW chipsets (I have two Cellink BTA3120) :(
So, the result is the same as for 1700 and 2100.
romeo_dolorosa
11-01-2006, 01:05
It will install after the "magic ingredient" of Phantasm. The dongle (CSR) can be recognized. BUT, it WILL NOT pair. So I guess it still doesn't work. Using the shortcuts in Windows Explorer, it has trouble displaying the dongle's services. The PC will get stuck, and after a while it will give a license error.
So my conclusion: Yes I think this version has CSR support, but we need a new formula for the "magic ingredient" to make it work. I hope Phantasm can look into the new version.
:D
I have a Dell with Truemobile 350 and I get the same license errors, when I am searching for other BT devices. Any solution till yet?
adisor19
11-03-2006, 20:50
My patcher works OK with this distro.
But from the other side, the driver doesn't work with SiW chipsets (I have two Cellink BTA3120) :(
So, the result is the same as for 1700 and 2100.
I'm afraid your patcher v 2.0 and phantasm's licence pather v1.8 don't work with versions 2100 and above even with Broadcom based chipsets. It installs fine but when you try to find a device it detects that the licence is no good. Looks like they implemented a new way to detect whether the licence is valid or not. :(
Adi
have same problems with msi Btoes 2 - but without patching work ok
It installs fine but when you try to find a device it detects that the licence is no good.
Sounds strange, I tried to install and patch 1700, 2100, 2300 but they said me nothing about license :)
The other thing is that they did not work :(.
Well, I'll try to have a look at the problem....
adisor19
11-06-2006, 07:35
Sounds strange, I tried to install and patch 1700, 2100, 2300 but they said me nothing about license :)
The other thing is that they did not work :(.
Well, I'll try to have a look at the problem....
Well they do install fine and appear to work ok until you try and search for other devices. At this point it complains about an invalid licence. I tried this with .2300 and .2100. Didn't test .1700 yet..
The dongle is a Broadcom based Dell/Logitech device..
Adi
adisor19, you're right, there was a problem with device search.
But, AFAIR, the patcher_v2 and Phantasm's license patcher gave the same result, so I decided that the problem is in the chipset.
BTW, I don't remember anything about license...
Well, it seems a more deep look became necessary :).
adisor19
11-06-2006, 08:54
adisor19, you're right, there was a problem with device search.
But, AFAIR, the patcher_v2 and Phantasm's license patcher gave the same result, so I decided that the problem is in the chipset.
BTW, I don't remember anything about license...
Well, it seems a more deep look became necessary :).
Yep, initially i thought the same but then i verified it with 2 differenct Broadcom based dongles (each having a different revision firmware) and the same thing happened. So indeed Broadcom must be using a new trick to mess with us ;)
I'm gonna test .1700 tomorrow and i'll post my results. I clearly remember pple with Broadcom chipsets working fine with the .1700 version...
Good luck with your work :)
Adi
Yolly Zubrick
11-07-2006, 04:18
Or is it not .1100? Last time I remembered .1700 also didn't work. :(
Now I see. There really is a problem.
I'll try to solve it, but it will take some time.
Well, the problem seems to be found.
Still not working with my dongles (cannot search). I'm not sure if it's license or driver problem.
Is there anybody whose dongle works with this Widcomm?
I'd like to test the patch.
adisor19
11-07-2006, 23:21
Go to:
http://update.broadcom.com/BTWUpdate/iedownload.asp
Download and run:
http://update.broadcom.com/BTWUpdate/downloads/btwinitialupdate.exe
You will have something like that in %temp% directory folder
ce2a5341-a490-4d79-8d9c-af903dd97aae.exe - 18,1 MB
It updates you drivers to 5.1.0.2300
miro68, can you tell us what dongle you used in order for the updater to download the latest version ? It refused in my case with all my dongles :
Belkin CSR based BT 1.1 FT008 100m
Microsoft CSR based BT 1.1 10m
Dell Broadcom based BT 2.0 10m
I fact, can everybody who managed to use this program to download and install an update tell us what dongle they have ?
Regards,
Adi
Hi, adisor19
My dongle is here:
http://www.trust.com/products/product.aspx?artnr=14693
Aqualung
11-08-2006, 13:03
Now I see. There really is a problem.
I'll try to solve it, but it will take some time.
Well, the problem seems to be found.
Still not working with my dongles (cannot search). I'm not sure if it's license or driver problem.
Is there anybody whose dongle works with this Widcomm?
I'd like to test the patch.Folks, I don't get it. Am I supposed to experience problems with the latest Widcomm stack (5.1.0.2300)? Licensing issues? My Broadcom-based dongles (Belkin F8T20 and Jabra A320s) work fine with this release--or, at least, to the extent to which I am using them. Could it be that there is some feature that I haven't tested yet, that could cause trouble? What feature would that be?
adisor19
11-08-2006, 15:01
Folks, I don't get it. Am I supposed to experience problems with the latest Widcomm stack (5.1.0.2300)? Licensing issues? My Broadcom-based dongles (Belkin F8T20 and Jabra A320s) work fine with this release--or, at least, to the extent to which I am using them. Could it be that there is some feature that I haven't tested yet, that could cause trouble? What feature would that be?
How did you install it ? Did you have to use the Licence Patcher or the Widcomm Patcher 2.0 or did it work without it ?
Also, can you post the firmware version of both your Broadcom based dongles ?
Adi
Aqualung
11-08-2006, 15:16
How did you install it ? Did you have to use the Licence Patcher or the Widcomm Patcher 2.0 or did it work without it ?No patcher, nothing. Works right out of the box. I've never used no license patchers with any of the Widcomm stacks discussed here on the forums. That's what's amazing, and what makes me suspicious: why did I not need any license patching? Or is it that I do need license patching, only I just don't realize it yet?Also, can you post the firmware version of both your Broadcom based dongles?I think they're both 2.1.92.0 (that's at least my Jabra's firmware).
I have been able to install this version for my CSR dongle (modded the inf before) and the BT device has been recognized thanks to License patcher 1.7
By the way, the software has been installed in English (setup was partially in French) though I have a French Windows version. Maybe the files miro68 made available to us are English only as he might have an English OS and btwinitialupdate.exe only downloads the language file one actually needs.
When I run btwinitialupdate.exe myself, it says "no Bluetooth device detected"...
But now the sad part of the story:
Unfortunately, when rebooting the computer I get a BSOD:
STOP - c000021a
The Windows Logon Process terminated unexpectedly with a status of 0xc0000139 (00000000 00000000). The system has been shut down.
This is not the first time I have to encounter that error as a cause of a new Widcomm installation...maybe somebody knows what this is due to....?!
In the meanwhile I'll reinstall Windows :mad:
I am using ANYCOM USB-250 adapter. I confirm that license patch is not needed for making the driver work with the adapter. Actually when the driver is installed, the caption just showed ANYCOM USB-200/250 5.1.0.2300. And in Add/Rmove Programs, ANYCOM USB-200/250 Bluetooth Software is listed. I cannot tell if it is downloaded from Broadcom or from ANYCOM directly. 2300 driver is not mentioned at ANYCOM website yet.
adisor19
11-09-2006, 18:27
I am using ANYCOM USB-250 adapter. I confirm that license patch is not needed for making the driver work with the adapter. Actually when the driver is installed, the caption just showed ANYCOM USB-200/250 5.1.0.2300. And in Add/Rmove Programs, ANYCOM USB-200/250 Bluetooth Software is listed. I cannot tell if it is downloaded from Broadcom or from ANYCOM directly. 2300 driver is not mentioned at ANYCOM website yet.
This is a bit weird.. did you do an upgrade or did you first completly uninstall the previous version of the Widcomm driver ? And what version did you previously have installed ?
I have a feeling you did an upgrade...
Adi
adisor19
11-09-2006, 18:43
This is a bit weird.. did you do an upgrade or did you first completly uninstall the previous version of the Widcomm driver ? And what version did you previously have installed ?
I have a feeling you did an upgrade...
Adi
I did a bit more experimenting on my side : I did an upgrade from 5.1.1100 (patched) to 5.1.2300 withought uninstalling .1100 in the first place and initially everything seemed to be working fine. However as soon as i searched for devices in range, it complained about the licence being invalid..
We still need help with this one..
P.S. I'm using a Broadcom dongle with Firmware 2.1.164.0.
Hope Phantasm can take a looke at theses newer versions..
Regards,
Adi
Yolly Zubrick
11-10-2006, 02:46
But now the sad part of the story:
Unfortunately, when rebooting the computer I get a BSOD:
STOP - c000021a
The Windows Logon Process terminated unexpectedly with a status of 0xc0000139 (00000000 00000000). The system has been shut down.
This is not the first time I have to encounter that error as a cause of a new Widcomm installation...maybe somebody knows what this is due to....?!
In the meanwhile I'll reinstall Windows :mad:
Here's an article I found about your problem:
0xC000021A: STATUS_SYSTEM_PROCESS_TERMINATED
(Click to consult the online Win XP Resource Kit article, or see Windows 2000 Professional Resource Kit, p. 1561.)
This occurs when Windows switches into kernel mode and a user-mode subsystem, such as Winlogon or the Client Server Runtime Subsystem (CSRSS), is compromised and security can no longer be guaranteed. Because Win XP can’t run without Winlogon or CSRSS, this is one of the few situations where the failure of a user-mode service can cause the system to stop responding. This Stop message also can occur when the computer is restarted after a system administrator has modified permissions so that the SYSTEM account no longer has adequate permissions to access system files and folders.
Doesn't look like it has something to do with WIDCOMM. Too bad though. I have never encountered this STOP error before. Just be careful next time I guess. For the complete list of STOP errors go HERE (http://www.aumha.org/win5/kbestop.php)
I just did an upgrade. I downloaded the small program and run it. And it did the rest of things. No need to uninstall previous version (2100). I guess it is no problem because ANYCOM is sort of "paid" company to Broadcom since it releases new driver from time to time.
This is a bit weird.. did you do an upgrade or did you first completly uninstall the previous version of the Widcomm driver ? And what version did you previously have installed ?
I have a feeling you did an upgrade...
Adi
adisor19
11-10-2006, 03:06
I just did an upgrade. I downloaded the small program and run it. And it did the rest of things. No need to uninstall previous version (2100).
And now, are you able to search for new devices and pair them ? What dongle and firmware version do you have ? Was the previous version using a patched licence ? (the .2100 one)
Adi
ladude626
11-10-2006, 04:04
If your bluetooth dongle is not supported by Widcomm, it's most like that it's not license. Use this program to patch the "license.dat" file to support your device. It can also patch the registry to let it support your device.
adisor19
11-10-2006, 04:08
If your bluetooth dongle is not supported by Widcomm, it's most like that it's not license. Use this program to patch the "license.dat" file to support your device. It can also patch the registry to let it support your device.
ladude626, i'm well aware of that program as i used it to patch my licence.dat file as mentioned previously, however even with that, it still complains about a licence error one you try to do a search for a device or to pair a device with version 5.1.0.2300 even though i have a Broadcom based dongle.
Adi
And now, are you able to search for new devices and pair them ? What dongle and firmware version do you have ? Was the previous version using a patched licence ? (the .2100 one)
Adi
Adi, I said in the previous post, I use ANYCOM USB 250 adapter (firmware 2.1.128.250). The patch is never needed. :) Everything works naturally after update.
Yolly Zubrick
11-10-2006, 06:44
I think if your BT dongle has a Broadcom Chip, like Anycom products. you will not have problems with updates. Too bad for CSR and ISCC and other users.
Aqualung
11-10-2006, 10:30
(firmware 2.1.128.250).Gosh, where do you get all these fancy new firmware updates from? I myself am looking for a firmware update for my Broadcom-based MSI dongle (if not also for the other two dongles with newer firmware).
adisor19
11-10-2006, 14:24
I think if your BT dongle has a Broadcom Chip, like Anycom products. you will not have problems with updates. Too bad for CSR and ISCC and other users.
Yolly, once again, i have a Broadcom based dongle and it still doesn't work with the latest version of Widcomm, wich leads me to believe our current pachers need updating.
Adi
adisor19
11-10-2006, 14:26
Gosh, where do you get all these fancy new firmware updates from? I myself am looking for a firmware update for my Broadcom-based MSI dongle (if not also for the other two dongles with newer firmware).
For now, the only ones who offer regular firmware and software updates for their products has been Anycom.
Adi
@Yolly Zubrick
Thanks for your answer, I found that article on my side too.
The BSOD STOP issue must have to do with Widcomm, as it occurs when I upgrade Widcomm from an older version and then reboot. I already experienced that in the past (and only when upgrading Widcomm).
I now reinstalled Windows and Widcomm 5.1.0.2300 directly with patched license.dat.
My BT device is recognized, but unfortuantely I still get license prompts and error message when searching a device to pair.
By the way, does anybody know what these special sections in the INF mean and how I can figure out if I do have a selectively suspendable dongle?
-Special sections for the Broadcom dongle and others with both selective suspend & remote wakeup disabled
-Special sections for Broadcom/Widcomm Smart Dongle
-Special sections for the Dell and other "selectively suspendable" dongles
Thanks,
ulysse
adisor19
11-16-2006, 05:47
Aii, here is an update from me. I bought the Trust dongle mentioned previously and it came with Widcomm 4.0.1.2900. I had already installed on my PC Widcomm 5.1.0.1100 and when i plugged the dongle in, it was recognised and was working properly. So then i ran the broadcom updater and it told me that it can not update my Evaluation version of widcomm ! :0
It seems that the 5.1.0.1100 or the way the licence patcher 1.8 works, is that it makes the widcomm software look like an evaluation verion.
I then uninstalled 5.1.0.1100 and installed the version 4 that came on the cd. Once the dongle was recognised and working properly, i ran the updater and it immediatly downloaded the updated to 5.1.0.2300. Sweet ! :)
The only problem with this dongle is that it has a relatively OLD firmware on it :(
Firmware version 2.1.33.161.
If only there was an update for it.
The good news is that the dongle is a GENERIC(VID and PID) broadcom dongle. In other words it will always be updated to the latest version of the Widcomm software :)
Adi
Folks - installed 2300 but the BT try icon remains red - if I say start BT device - it says - BT license check failed
If I use the license patcher - BT tray icon trun white on connecting the device but if I want to use the "explore my BT places" is again pops the license question
Yolly Zubrick
11-19-2006, 13:15
Exactly the same problem as everyone else not using compatible BT dongles.
I thought I will reply rather than edit -
I uninstalled 2300 & installed 2500 - its working now
adisor19
11-19-2006, 19:20
I thought I will reply rather than edit -
I uninstalled 2300 & installed 2500 - its working now
What chipset is your dongle based on ? Is it a CSR based dongle ?
Adi
Yolly Zubrick
11-20-2006, 10:38
What chipset is your dongle based on ? Is it a CSR based dongle ?
Adi
I think she meant 5.0.1.2500, which should work with most dongles. If you're dongle cannot benefit from the advance features of the new stack, I think switching to an older, but compatible version is the way to go.
solnyshok
11-20-2006, 15:19
I used 5.0.1.2500 (with Thinkpad's IBM Integrated Bluetooth III - CSR based) for some half a year, but it doesn't work correctly with my newly purchased stereo headset (Soneric DS970) and I upgraded to the latest 5.1.0.2300 and now I have same problems as others reported. I am eagerly awaiting a patch.
Is there a version between 5012500 and 5102300 that has some improvements over 5012500 but is still patchable?
adisor19
11-20-2006, 17:43
I used 5.0.1.2500 (with Thinkpad's IBM Integrated Bluetooth III - CSR based) for some half a year, but it doesn't work correctly with my newly purchased stereo headset (Soneric DS970) and I upgraded to the latest 5.1.0.2300 and now I have same problems as others reported. I am eagerly awaiting a patch.
Is there a version between 5012500 and 5102300 that has some improvements over 5012500 but is still patchable?
Yes, use 5.1.0.1100.
Adi
luckyknight
11-21-2006, 15:47
I've recently switched over to Vista x64. Is there a 64-bit version and is WIDCOMM now compatible with Vista?
I've tried WIDCOMM 5.1.0.1100 but Vista refuses to load the driver for the Bluetooth dongle (it has an exclamation mark on it on device manager). I've also tried 5.1.0.1700 but Vista refused to load the driver this time because it was not digitally signed.
I have setup the appropiate inf options. My device is a Air2U USB dongle (manufactured by Silicon Wave apparently). Is that a CSR?
solnyshok
11-22-2006, 23:03
5101100 works fine with everything except Sony Ericsson DS970 A2DP
dreamramon
11-22-2006, 23:29
seemed our patches makes the A2DP non-working...
Since my moto ht820 worked fine on the original 5.1.0.2500
These two do not seem to work together in A2DP. Anyone have any ideas?
The only version I have had it work with is 4.1.0.1700, I think