dslreports logo
 
    All Forums Hot Topics Gallery
spc
Search similar:


uniqs
23112

Maxxi
@cooper.edu

Maxxi

Anon

Broadcom WLAN Utility & Driver 3.100.56.0 9X/2K/XP

Strange why people haven't replied to my previous posts? These drivers come directly (more or less) from Broadcom - the company responsible for most of the chipsets (aside from Atheros) behind our WLAN NICs and Routers. Instead of installing and using horrible Linksys drivers (which even if recently updated and released, usually lag behind these "older" Broadcom releases as they are most often based on previous Broadcom builds and released with a Linksys-badge months later)... why don't you try these instead and see if they solve your problems? One thing is for sure - they've worked wonders for my 802.11g network hardware. Best of all they should work under 9X/2K/XP and with almost all Linksys WLAN NICs (802.11a/b/g/pre-h). Make sure to remove both the Linksys driver and utility as well as disable XP's WZC service. Remove all registry entries pointing to these Linksys files and reboot the PC. Download the EXE from HP's server, change the file extension from EXE to RAR/ZIP, extract to a TEMP folder, using the INFs (more on this later), update the NIC driver to a Broadcom-based 802.11x... install the utlity (same TEMP folder) and reboot the PC. Play with the settings and enjoy.

For future, current and past Broadcom drivers:
»h20000.www2.hp.com/bizsu ··· broadcom

For the Broadcom WLAN Network Adapters User Interface - Windows 9X/XP version 4.00 A (18 Feb 05) UPDATE: Utility & Driver / Ignore the prerequisites:
»h18007.www1.hp.com/suppo ··· 469.html

For the Broadcom WLAN Network Adapters User Interface for Windows 9X/2K version 4.00 A (21 Feb 05) UPDATE: Utility & Driver / Ignore the prerequisites:
»h18007.www1.hp.com/suppo ··· 490.html

These packages contain the Broadcom WLAN Utility, Version 3.100.56.0, for Microsoft Windows XP for the following network adapters in the listed notebook models:
- Broadcom 54g MaxPerformance 802.11g Adapter (most Linksys Speed-booster NICs)
- Broadcom 802.11b Adapter (most Linksys Wireless-B NICs)
- Broadcom 802.11b/g Adapter (most Linksys Wireless B&G NICs)
- Broadcom 802.11a/b/g Adapter (most Linksys Wireless A&G NICs)
- HP Wireless LAN 54g WL450 Adapter

Enhancements
* Provides Broadcom WLAN utility user interface, version 3.100.56.0, for use with Broadcom WLAN Networks Adapter Driver (includes build 3.100.46.0 (WHQL) and 3.100.56.0 (non-WHQL).

The INF files point to two different driver revisions: 3.100.46.0 (WHQL) and 3.100.56.0 (non-WHQL). Once installed the NIC properties tabs under device manager will show two new settings 1. WME Enabled/Disabled 2. WZC Managed Ethernet Enabled/Disabled

To install the newer build you'll need to modify the second INF file otherwise an error message will stop the installation and you'll have to stick with the 3.100.46.0 certified driver). The INF modification is rather simple - I will post it as an update to this thread.

I've modified my INF files to allow for channels 12-14 as well as to enable some hidden settings. I can upload these INFs or the whole modified driver/utility set if anyone can provide me with required space and hosting.

* Adds new user interface.
* Adds support for Cisco Compatible Extensions V3.0 features.
* Provides support for both pre-logon connections and persistent connections.

PS - For Speed-booster NIC owners, Don't be alarmed when you won't seem to be able to install these drivers using a device ID of "Broadcom 54g MaxPerformance 802.11g Adapter" as it is no longer specified in the INF files... Broadcom (for one reason or another) chose to remove this device ID from all recent builds but at the same time when using the device ID of "Broadcom 802.11b/g Adapter" for both my WMP54GS and WPC54GS NICs, the cards function properly (far better than with ANY Linksys driver & utility set, not to mention XP's WZC) and still negotiate at speed-booster speeds.

Other than that - all good, flawless encryption (all types and more) support, no connection loss, good performance, better signal and lower noise levels, etc. The new Utility 3.100.56.0 is much different from the previous (3.00D/3.00E) release however upon extracting this 4.00A HP archive (just change the EXE file extension to RAR or ZIP and extract the files manually into some TEMP folder to prevent automatic installation and allow for INF editing) (17.3MB) I realized that the archive includes BOTH the Utility and new Broadcom drivers (HP typos strike again)!

JoeR2
Dude?
join:2001-06-01
Norfolk, VA

JoeR2

Member

I saw one of your other posts, but after some reading (way too much!), it seems that the WPC54G v2 is a TI ACX111 chipset, not Broadcom. Correct?

I'd love to find something to keep mine locked onto my router reliably. I could give a damn about MS WZC's hunting features with about 5 other AP's in my vicinity.

Any ideas?

Maxxi
@cooper.edu

Maxxi

Anon

I am not sure - check on the chipset using the likes of "PCI Latency Tool 2.3" or "Unknown Device Identifier 4.00" or possibly ".. they should identify your NIC by chipset/hardware manufacturer "device ID" and not the specific driver "device ID". Hope it helps. If you're dealing with TI ACX111 - I currently have no idea how to help. WZC is horrible - I've got around 10 APs which go up and down during the day in my area and all of them (although the signal was always weak or border-line) caused the "hunting features" you've mentioned.

Sorry for the long posts - I simply hate writing single-sentence threads that need to be replied to for days-on-end with more... single-sentence posts. When it comes to drivers and directions - I guess I see no other way.
elvisk
join:2003-08-17
Boston, MA

elvisk to Maxxi

Member

to Maxxi

Re: Broadcom WLAN Utility & Driver 3.100.56.0 9X/2

Maxxi - Thanks for the info but I have one question. Have you been able to figure out how to get pre-logon connections to work? I don't see it anywhere. I am using the 3.100.56 utils, but the slightly older 3.100.46 drivers. Thanks.

soganta
Premium Member
join:2003-10-15

soganta to Maxxi

Premium Member

to Maxxi
Maxxi, these drivers don't work for Windows 98 I can't install the Utility (gives me an error) and the drivers won't start. Using WMP54Gv2 OS Windows 98SE.

Maxxi
@rr.com

Maxxi

Anon

Strange - I assumed they did based on the text within the INF files - here is a sample:

[version]
Signature = "$Windows 95$" ; Combined Win9x/Win2k inf
Class=Net
ClassGUID = {4d36e972-e325-11ce-bfc1-08002be10318}
Provider = %V_BCM%
Compatible = 1
DriverVer=01/24/2005, 3.100.56.0
CatalogFile=BCM43XX.CAT

[Manufacturer]
%V_BCM% = BROADCOM

[ControlFlags]
ExcludeFromSelect = *

[BROADCOM]
%BCM430B_DeviceDesc% = BCM43XX, PCI\VEN_14E4&DEV_4301&SUBSYS_12F3103C
%BCM430G_DeviceDesc% = BCM43XG, PCI\VEN_14E4&DEV_4320&SUBSYS_00E70E11
%BCM430G_DeviceDesc% = BCM43XGT, PCI\VEN_14E4&DEV_4320&SUBSYS_12F4103C
%BCM430G_DeviceDesc% = BCM43XG1, PCI\VEN_14E4&DEV_4320&SUBSYS_12F8103C
%BCM430G_DeviceDesc% = BCM43XG2, PCI\VEN_14E4&DEV_4320&SUBSYS_12FA103C
%BCM430G_DeviceDesc% = BCM43XG3, PCI\VEN_14E4&DEV_4320&SUBSYS_12FB103C
%BCM430M_DeviceDesc% = BCM43XM1, PCI\VEN_14E4&DEV_4324&SUBSYS_12F9103C
%BCM430M_DeviceDesc% = BCM43XM2, PCI\VEN_14E4&DEV_4324&SUBSYS_12FC103C
%BCM430M_DeviceDesc% = BCM43XM3, PCI\VEN_14E4&DEV_4324&SUBSYS_12FD103C

%BCM430G_DeviceDesc% = BCM43XG1, PCI\VEN_14E4&DEV_4318&SUBSYS_1355103C
%BCM430G_DeviceDesc% = BCM43XG2, PCI\VEN_14E4&DEV_4318&SUBSYS_1356103C
%BCM430G_DeviceDesc% = BCM43XG3, PCI\VEN_14E4&DEV_4318&SUBSYS_1357103C
%BCM430M_DeviceDesc% = BCM43XM1, PCI\VEN_14E4&DEV_4319&SUBSYS_1358103C
%BCM430M_DeviceDesc% = BCM43XM2, PCI\VEN_14E4&DEV_4319&SUBSYS_1359103C
%BCM430M_DeviceDesc% = BCM43XM3, PCI\VEN_14E4&DEV_4319&SUBSYS_135A103C

;-----------------------------------------------------------------
; Win9x specific
;
[BCM43XX]
AddReg = BCM43XX.win.reg, BCM43XX.hlp.reg, common.reg, bg0.reg, bg.loc.reg, b.reg, cc.reg, cc_fixed.reg
DelReg = common.delreg, rate.delreg
CopyFiles = BCM43XX.sys.files
DriverVer=01/24/2005, 3.100.56.0

[BCM43XG]
AddReg = BCM43XX.win.reg, BCM43XX.hlp.reg, common.reg, bg0.reg, bg.loc.reg, g.reg, cc.reg, cc_fixed.reg
DelReg = common.delreg, rate.delreg
CopyFiles = BCM43XX.sys.files
DriverVer=01/24/2005, 3.100.56.0

[BCM43XGT]
AddReg = BCM43XX.win.reg, BCM43XX.hlp.reg, common.reg, bg0.reg, bg.loc.reg, g.reg, gt.reg, cc.reg, cc_fixed.reg
DelReg = common.delreg
CopyFiles = BCM43XX.sys.files
DriverVer=01/24/2005, 3.100.56.0

[BCM43XG1]
AddReg = BCM43XX.win.reg, BCM43XX.hlp.reg, common.reg, bg0.reg, bg1.reg, g.reg, us.reg
DelReg = common.delreg
CopyFiles = BCM43XX.sys.files
DriverVer=01/24/2005, 3.100.56.0

[BCM43XG2]
AddReg = BCM43XX.win.reg, BCM43XX.hlp.reg, common.reg, bg0.reg, bg.loc.reg, g.reg, cc.reg, cc_row.reg
DelReg = common.delreg
CopyFiles = BCM43XX.sys.files
DriverVer=01/24/2005, 3.100.56.0

[BCM43XG3]
AddReg = BCM43XX.win.reg, BCM43XX.hlp.reg, common.reg, bg0.reg, bg3.reg, g.reg, jp.reg
DelReg = common.delreg
CopyFiles = BCM43XX.sys.files
DriverVer=01/24/2005, 3.100.56.0

[BCM43XM1]
AddReg = BCM43XX.win.reg, BCM43XX.hlp.reg, common.reg, bag.reg, hiband.reg, chans.thru64.reg, enabled.11h.reg, us.reg
DelReg = common.delreg
CopyFiles = BCM43XX.sys.files
DriverVer=01/24/2005, 3.100.56.0

[BCM43XM2]
AddReg = BCM43XX.win.reg, BCM43XX.hlp.reg, common.reg, bag.reg, hiband.reg, chans.thru64.reg, chans.a.row.reg, chans.thru13.reg, enabled.11h.reg, cc.reg, cc_row.reg
DelReg = common.delreg
CopyFiles = BCM43XX.sys.files
DriverVer=01/24/2005, 3.100.56.0

[BCM43XM3]
AddReg = BCM43XX.win.reg, BCM43XX.hlp.reg, common.reg, bag.reg, chans.a.jp.reg, chans.thru14.reg, disabled.11h.reg, jp.reg
DelReg = common.delreg
CopyFiles = BCM43XX.sys.files
DriverVer=01/24/2005, 3.100.56.0

[BCM43XX.win.reg]
HKR, Ndi, DeviceID, , "PCI\VEN_14E4&DEV_4307"
; Ndis Info
HKR, , EnumPropPages, 0, "netdi.dll,EnumPropPages"
HKR, NDIS, MajorNdisVersion, 1, 03
HKR, NDIS, MinorNdisVersion, 1, 0A
HKR, NDIS, LogDriverName, , "BCM43XX"
HKR, NDIS, MajorDriverVersion, 1, 1
HKR, NDIS, MinorDriverVersion, 1, 0
;Install sections
HKR, Ndi\Install, , , "BCM43XX.ndi.install"
; Interfaces
HKR, Ndi\Interfaces, DefUpper, 0, "ndis3"
HKR, Ndi\Interfaces, DefLower, 0, "ethernet"
HKR, Ndi\Interfaces, UpperRange, 0, "ndis3"
HKR, Ndi\Interfaces, LowerRange, 0, "ethernet"

[BCM43XX.hlp.reg]
HKR, Ndi, HelpText, , %BCM43XX_HELP%

[BCM43XX.ndi.install]
AddReg = BCM43XX.ndi.reg

[BCM43XX.ndi.reg]
HKR, , DevLoader, 0, "*ndis"
HKR, , DeviceVxDs, 0, "BCMWL5.SYS"

; Flag = 2 is COPYFLG_NOSKIP (2)
; Flag = 33 is COPYFLG_WARN_IF_SKIP (1) | COPYFLG_NO_VERSION_DIALOG (32)
[BCM43XX.sys.files]
BCMWL5.SYS,,,2

; Both Win9x & Win2k
;

[common.delreg]
HKR, Ndi\params\Locale
HKR,,Locale
HKR, Ndi\params\Country
HKR,,Country
HKR, Ndi\params\Channel
HKR, Ndi\params\AssocPref
HKR, Ndi\params\RoamPref
HKR,,Channel
HKR,,MPC

[rate.delreg]
HKR, Ndi\params\Rate
HKR, Ndi\params\RateA

[common.reg]
HKLM, Software\Broadcom\802.11, SupportedApps, 0, "3.30.15.0,3.40.25.3,3.40.25.6,3.70.22.0,3.100.56.0"

soganta
Premium Member
join:2003-10-15

soganta

Premium Member

Yes I was under the same impression, it does recognize my WMP54G as a "Broadcom 802.11g/b" and it installs the drivers but when my PC reboots I get this ! saying "The device cannot start". Also the setup for the utility extracts fine but when it starts to install I get a warning that the setup was aborted.

Maxxi
@rr.com

Maxxi

Anon

Weird - have you tried installing the older (3.100.46.0) build? Regardless, if you can't get these to properly install (and enable your device upon reboot) the Utility WILL NOT INSTALL and will always give you that or another error. Only once the drivers are in place and working/properly loaded, will the Broadcom Utility install correctly. Good luck.
watt50
join:2005-04-12

watt50 to Maxxi

Member

to Maxxi
said by Maxxi:

To install the newer build you'll need to modify the second INF file otherwise an error message will stop the installation and you'll have to stick with the 3.100.46.0 certified driver). The INF modification is rather simple - I will post it as an update to this thread.
could you describe what you modified in which inf file, so that the 3.100.56.0 drivers are installable?

Maxxi
@rr.com

Maxxi

Anon

You can modify the INFs all you please (they are pretty much self-explanatory) and there is PLENTY to modify (settings, additional channels, etc.) but the single mod which allows for proper installation of the newer driver (today I'm not really sure if there is a difference between the builds - I don't want to get into that) is this... open the second inf file (the "a" inf) and locate these lines:

[version]
Signature = "$Windows 95$" ; Combined Win9x/Win2k inf

modify them to read:

[version]
Signature = "$Windows NT$" ; Combined Win9x/Win2k inf

save, update driver, point the wizard to the "a" inf file, choose the 3.100.56.0 driver, install, reboot, enjoy.

jdepew
James Depew
Premium Member
join:2002-05-13
Savannah, GA

jdepew

Premium Member

Maxxi,

Would you mind if I reprinted these instructions, given proper credit, at our site? You can either PM me or reach me directly at jdepew [at] linksysinfo.org

I personally used these on the MiniPCI card I yanked out of my WRT54Gv1.0 to use in my wireless-less laptop, and they worked great. Unfortunately, not too impressed with the Broadcom client looks like a regression from earlier versions. It seems terribly missing that you cannot click on a AP in the site survey to auto add it to your list or connect to it, and are rather forced through thier awkward wizard.

Thanks for the great info! Keep it coming!

Maxxi
@rr.com

Maxxi

Anon

No problem - thanks for the heads up. It turns out I am a "somewhat-active" member of your site (my login there is maxx) and I've posted my instructions in the forum (more than once) but received no replies. Please do reprint them - maybe then someone will notice and make use (like you did) of this information.

PS - You are right to point out that the Broadcom wizard is awkward and that clicking on an AP in the site survey has no effect. Other than that - I think these drivers are the way to go - with some simple INF editing (but not only) the encryption options and settings they allow for are great.