release.txt Driver File Contents (570249.exe)

                        R E L E A S E    N O T E S

                           Broadcom CIM Providers
               for Win98 SE, Win Me, Win2000 and Win XP, .NET
                               Version 6.0.4

                   Copyright (c) 2003 Broadcom Corporation
                            All rights reserved.
                               Feb. 11, 2003

CHANGES in v6.0.4
- Previous version used stale adapter state to determine redundancy status.

CHANGES in v6.0.3
- Reported redundancy status now accounts for standby adapters (CQ7011).

CHANGES in v6.0.2
- Fixed NULL pointer dereference (CQ6910) in BCMUninstall
  (when run without WMI core installed).

- Link up/down events are now treated the same as active/inactive events 
  (fix for no instance modification events for offline adapters on link status change).

CHANGES in v6.0.1
- Fixed problem in v6.0.0 version of BCIMMofComp.exe (can't include both
  -AUTORECOVER and -class:forceupdate on the mofcomp command-line).

- Fixed syntax error (extra comma) in BRCMGroup.mof (CQ6859).

CHANGES in v6.0.0
- BRCMGroup.mof: Moved __EventProviderRegistration instance definition to end
  of file (after class definitions) to fix CQ6821: "target class does not
  exist" error events in Application Log during install (BCIMMofComp).

- BRCMGroup.mof: Removed references to BRCM_NetworkVirtualAdapter.

- BCIMUninstall: Now removes __EventProviderRegistration instance from
  CIM repository. Fix for CQ6821: "target class does not exist" error events
  in Application Log when uninstalling).

- BCIMUninstall: Removed references to BRCM_NetworkVirtualAdapter.

- BCIMUninstall: Doesn't attempt to remove classes that don't exist.

- BCIMMofComp: Added command-line parameters to "mofcomp.exe BRCMGroup.mof"
  command-line (replaces Microsoft-specific #pragmas in the .mof file).

CHANGES in v3.0.7
- Bugfix, the redundancy status value was not being reported correctly when
  adapters were manually taken offline (rather than unplugged).

- Increased BMAPI initialization retry count from 60 to 120 (seconds).

- EnableASF method now supports SNMPCommunityName property (fix for CQ 5243).
  Allows basfrcfg.vbs user to specify both the enableasf and snmpcom params
  on the same command-line. BRCMGroup.mof updated.

CHANGES in v3.0.6
- CBRCMFtmiData::InitInstances() no longer returns failure (1) if it's 
  already been initialized. This caused intialization retries which
  appeared as lock-ups or delays during operation.

CHANGES in v3.0.5
- GetAdapterStatus() return value is now based on link status instead of
  online/offline status.

CHANGES in v3.0.4
- The status of adapters manually set to offline (disabled) state is now
  correctly reported.
- The status of stand-by adapters (in a Team) is now correctly reported
  when primary adapters are offline/disabled.

CHANGES in v3.0.3
- Stand-by adapters (in a Team) are now reported as offline (inactive).
- CBRCMFtmiData::InitInstances() now retries (for up to 60 seconds)
  if BmapiInitialize() call fails.
- ProviderBase::AddInstancesRef() no longer increments reference counter 
  if CBRCMFtmiData::InitInstances() call fails.
- Reduced maximum retry time in CBRCMFtmiData::RefreshInstances() from 
  60 minutes to 60 seconds.
- Requires bmapi.dll v3.0.16 or later (for shutdown exception fix).

CHANGES in v3.0.2
- All Broadcom made network adapter will be in 'BRCM_NetworkAdapter'
  class. All non-Broadcom made network adapters will be in
- Support TT events.
- Support for .NET.

CHANGES in v3.0.1
- Require bmapi.dll v3.0.2 or later.
- Change ASF community name to at most 20 characters including NULL
  termination character.

CHANGES in v3.0.0
- Require cabw32.dll v0.22 or later.
- Require bmapi.dll v3.0.1 or later.
- Add support for 5704 and 5705.
- Modify MBA configuration methods.
- Support ASFCFG version 5.
- Modify 'ValueMap' in mof files so that it will not use value 0 or
  1 to represent other than 'Unknown' and 'Others'.

CHANGES in v1.0.12
- Add 'LocalRxStatus', 'RemoteRxStatus', 'AutoNegotiationMode' and
  'RequestedMediaType' properties for 'BRCM_NetworkAdapter' class.
- Modify 'GetLinkStatus()' method to return more link status related
- Fix incorrect 'BootAgentVersion' string.

CHANGES in v1.0.11
- Require BMAPI v2.2.19 or later.
- Support BASP in W2k profrssional and XP professional version.

CHANGES in v1.0.10
- Require BMAPI v2.2.18 or later.
- Fix ClearQuest:
  3722: Broadcom CIM provider diagnostic doesn't work with 5703S.

CHANGES in v1.0.9
- Require BMAPI v2.2.13 or later.
- Modify StartService() and EnableASF() in BRCM_ASFOOBAlertService class so
  that they will always enable the ASF frature regardless the service has
  been started or not.
- Manual installation is no longer supported. Users should always use
  installation program to install.

CHANGES in v1.0.8
- Require BMAPI v2.2.13 or later.
- Add one more method EnableASF() in BRCM_ASFOOBAlertService class.

CHANGES in v1.0.7
- Require BMAPI v2.2.13 or later.
- Support Windows 98 SE, Windows Me, Windows 2000 and Windows XP.
- Require Cable Analysis module 0.16 or later.

CHANGES in v1.0.6
- Require BMAPI v2.2.10 or later.
- Fix PXE version string.
- Allow users to enable and disable ASF feature on network adapter.

CHANGES in v1.0.5
- Add multiple boot agent support.
- Add alerting service support for ASF.

CHANGES in v1.0.4
- Add Cim Diagnostics Model support.
- Fix lock up problem with using ControlSuite to modify team.

CHANGES in v1.0.3
- Fix incorrect team status in case of a team with standby adapter.
- Fix incorrect team configuration after offline an adapter and hot remove
- Fix dead lock in refreshing team configuration.

CHANGES in v1.0.2
- Incorporate the changes in FTMI 5.0 beta SDK 2.2c.
- Add version control to the BRCMGroup.Dll.

CHANGES in v1.0.1
- The development is based on IBM FTMI 5.0 beta SDK 2.1. The implementation is
  subject to change in the future for final release.
- Users can manually upgrade the module by (the use must have administrative
  1. Open a 'Command Prompt'.
  2. For FTMI users, type in 'net stop twgipc' and press Enter.
  3. Type in 'Winmgmt /kill'  and press Enter.
  4. Copy BMAPI.dll to %systemroot%\system32.
  5. Copy BRCMGroup.dll to %systemroot%\system32.
  6. Copy BRCMGroup.mof to %systemroot%\system32.
  7. Open a command prompt. Goto %systemroot%\system32. Type in
     'regsvr32 BRCMGroup.dll and press Enter.
  8. Type in 'mofcomp BRCMGroup.mof' and press Enter.
  9. For FTMI users, type in 'net start twgipc' or reboot machine.
- In order to have event provider work properly, users should reboot machine
  after create first team. Or, users can manually restart software by (the use
  must have administrative rights):
  1. Open a 'Command Prompt'.
  2. For FTMI users, type in 'net stop twgipc' and press Enter.
  3. Type in 'Winmgmt /kill'  and press Enter.
  4. Type in 'Winmgmt'  and press Enter.
  5. For FTMI users, type in 'net start twgipc' or reboot machine.
- This release will support FTMI required classes such as BRCM_NetworkAdapter
  and BRCM_ExtraCapacityGroup. This release also support two new classes  not
  used by FTMI, BRCM_VirtualNetworkAdapter and BRCM_BASPEvents.
  BRCM_VirtualNetworkAdapter class represents virtual NICs created for teams.
  BRCM_BASPEvents class is for events generated from BASP software.
  Applications could use query such as 'SELECT * FROM BRCM_BASPEvents' to
  listen to events.
- CIM requires event consumer registered to CIM before event provider will
- all Broadcom CIM providers are loctaed under 'root\CIMV2' name space.
- users can use wbemtest.exe to verify installation and test Broadcom CIM
  providers. For example:
  1. After configured a team, users can launch wbemtest.exe, connect to
  'root\CIMV2' name space, open class like BRCM_NetworkAdapter and click
  'Instances' to browse all adapters that joined a team.
  2. Users can open class BRCM_ExtraCapacityGroup and browse all teams's

CHANGES in v1.0.0
- The development is based on IBM FTMI beta SDK. The implementation is subject
  to change in the future.
- Current implementation support Windows 2000 only.
- Users can manually install the module by:
  1. Make sure BMAPI.dll is under %systemroot%\system32.
  2. Copy BRCMGroup.dll to %systemroot%\system32.
  3. Copy BRCMGroup.mof to %systemroot%\system32.
  4. Open a command prompt. Goto %systemroot%\system32. Type in
     "regsvr32 BRCMGroup.dll". Type in "mofcomp BRCMGroup.mof".
- For FTMI, users need to install IBM Netfinity Directory 2.12 or higher and
  FTMI Version 5.0 on Windows 2000 Server (or Advance Server) machine.
  Currently, we only have FMTI 5.0 SDK and it requires Microsoft WMI SDK which
  is included in Microsoft Platform SDK.
  For more information, please refer to FMTI 5.0 SDK documentation.
- To install Netfinity Directory, run 'ibmsetup.exe' under '\Win32\INSTALL'
  directory on Netfinity Director CD. For installation options, please refer to
  installation instruction in FTMI 5.0 SDK and Netfinity Director
  To install FTMI 5.0 SDK, run 'setup.exe' under 'sdk\FTMI_setup' directory.
  For installation instruction, please refer to FTMI 5.0 SDK documentation.


The Common Information Model (CIM) is an industrial standard defined
by the Distributed Management Task Force (DMTF). Microsoft implements CIM on
Windows platforms such as Windows 2000. Broadcom will support CIM on the
Windows 2000 platform.

Broadcom's implementation of CIM will provide various classes to provide
information to users through CIM client applications. Please note that
Broadcom CIM data provider will provide data only, and users can choose their
prefered CIM client software to browse the information exposed by Broadcom CIM
provider. The current implementation of CIM is based on IBM FTMI beta SDK, and
is subject to change in the future.

Broadcom CIM provider provides information through BRCM_NetworkAdapter and
BRCM_ExtraCapacityGroup classes. BRCM_NetworkAdapter class provides network
adapter information pertaining to a group of adapters including Broadcom and
other vendors' controllers. BRCM_ExtraCapacityGroup class provides team
configuration for the Broadcom Advanced Server Program. Current implementation
will provide team information and information of physical network adapters in
the team.

Broadcom Advanced Server Program provides events through event logs. Users can
use the "Event Viewer" provided by Windows 2000, or use CIM to inspect or
monitor these events. Broadcom CIM provider will also provide event
information through CIM's generic event model. These events are
__InstanceCreationEvent, __InstanceDeletionEvent and
__InstanceModificationEvent, and are defined by CIM. For detail information
about these events, please refer to CIM documentation. CIM requires the client
application to register the events from the client application, using queries
as examples shown in following in order to receive events properly.

SELECT * FROM __InstanceModificationEvent where TargetInstance ISA "BRCM_NetworkAdapter"
SELECT * FROM __InstanceModificationEvent where TargetInstance ISA "BRCM_ExtraCapacityGroup"
SELECT * FROM __InstanceCreationEvent where TargetInstance ISA "BRCM_NetworkAdapter"
SELECT * FROM __InstanceDeletionEvent where TargetInstance ISA "BRCM_NetworkAdapter"
SELECT * FROM __InstanceCreationEvent where TargetInstance ISA "BRCM_ActsAsSpare"
SELECT * FROM __InstanceDeletionEvent where TargetInstance ISA "BRCM_ActsAsSpare"

For latest classes provided by Broadcom network controller card CIM provider,
please refer to the BRCMGroup.mof.
Download Driver Pack

How To Update Drivers Manually

After your driver has been downloaded, follow these simple steps to install it.

  • Expand the archive file (if the download file is in zip or rar format).

  • If the expanded file has an .exe extension, double click it and follow the installation instructions.

  • Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.

  • Find the device and model you want to update in the device list.

  • Double-click on it to open the Properties dialog box.

  • From the Properties dialog box, select the Driver tab.

  • Click the Update Driver button, then follow the instructions.

Very important: You must reboot your system to ensure that any driver updates have taken effect.

For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.

server: ftp, load: 2.85