============================ R E L E A S E N O T E S ============================ Broadcom 440x 10/100 Integrated Controller Driver For Microsoft Windows Operating Systems Copyright (c)

2000-2006 Broadcom Corporation All Rights Reserved.

Version 4.47 May 17, 2006 -------------------------------------------------------1. Problem (CQ#24836) 4401 B0: MAC and PHY loopback test hang in BACS Diagnostic when Driver version 4.44 to 4.46 is installed. Cause: The 4401 NDIS Driver v4.44 to 4.46 correction for CQ#24514 ADSL PPPOE Intermediate driver sending packets with LAN Link disconnected conditio n; causes Diagnostic hang of MAC and PHY Looback Tests since Loopback tests may be requested to run when there is no LAN Link cable and the Diagnostic Loopback Packets should have been processed. Change: Added Driver code to handle LAN Link Down condition for both normal and diagnostic modes of operation. Impact: Correct CQ#24836 issue.

Version 4.46 May 15, 2006 -------------------------------------------------------1. Enhancement Request CQ#24750 4401: Add multiple 4401 OEM Device IDs to support new OEM projects.. Cause: New Device IDs support request. Change: Added the requested Device IDs to be supported. Impact: Complete CQ#24750 enhancement request.

Version 4.45 May 05, 2006 -------------------------------------------------------1. Problem (CQ#24556) 4401B0 Windows Vista HCT Test 2c_LinkCheck test script failed with expected Link Down notification after driver is initialized and LAN cable not attached. Cause: New test script expects Link Down Event to be reported to NDIS just after the driver finishes initialization and no LAN cable c onnected. Prior OS and NDIS versions did not have this new requirement. Change: Changed 4401 NDIS driver code to report Link Down Event to

NDIS if running in Windows Vista OS and NDIS, when its initialization is finished and no LAN Cable connected. Impact: Correct CQ#24556 issue.

Version 4.44 April 28, 2006 -------------------------------------------------------1. Enhancement Request 4401: Perform TX and RX buffer reclaims outside of IRQL restricted Chip Reset function. Cause: NDIS Driver IRQL guidelines require that NDIS Allocate and Deallocate Buffer functions called by 4401 Driver to run at IRQL less than or equal to Dispatch Level. Change: Moved 4401 Driver TX and RX reclaim functions out of the IRQL restricted Driver ResetChip function. Impact: Complete enhancement request. 2. Enhancement Requests CQ#24185, CQ#24188, CQ24191 4401: Add 4401 OEM Device IDs to support new OEM projects. Cause: New Device IDs support request. Change: Added the requested Device IDs to be supported. Impact: Complete CQ#24185 , CQ#24188, and CQ24191 enhancement request. 3. Problem (CQ#22672) 4401B0-E in OEM Laptop System with ATI Chipset exhibits TCP Connection error when Network Chariot Stress is applied. Cause: PCI Bus interface memory reads and writes in this chipset are not very efficient and result in 4401 Receive FIFO overflows under Network Chariot Stress condition. The 4401 NDIS Driver has to recover the RX FIFO overflows by doing 4401 chip reset and reinitialize. The very frequent 4401 chip reset and reinitializations in this specific system results in the 4401 hardware to become unresponsive. This problem has not been observed in other 4401 designs. Change: Added a 2 millisecond wait to 4401 Driver reinitialization DMA Reset function to avoid the 4401 getting unresponsive in this system and avoid the TCP connection error under Chariot stress condition. Impact: Correct CQ#22672 issue. 4. Problem (CQ#24412) 4401B0 Shows lower 10 Mb Link Speed when monitored using Windows XP x64 OS Task Manager Networking Tab; and when LAN cable is disconnected. The 4401 NDIS Link Up and Link Down status reporting is not a problem and not addressed with this CQ24412.

Cause: The Task Manager Networking Tab of Windows x64 keeps sending OID_GEN_LINK_SPEED even when LAN Link is Down. The 4401 NDIS Driver versions 4.43 and earlier did not save the last known speed at Link Up state; so at time of Link Down (upon LAN cable removal) the default lower speed of 10 Mb was reported to the OS. Change: Added code to the 4401 NDIS Driver to save the last Link Up Speed for reporting during handling of OID_GEN_LINK_SPEED even when LAN cable is removed. The 4401 NDIS Link Up and Link Down status reporting was not a problem and Windows OS Task Manager Networking Tab showed proper "Operational" and "Non Operational" status conditions. Impact: Correct CQ#24412 issue. 5. Problem (CQ#24514) 4401 B0: Pulling out ADSL LAN cable from PC halts BCM4401 desktop after ADSL PPPOE connection has been installed and started. Cause: The 4401 NDIS Driver has already reported Link Status as Disconnected; however the ADSL PPPOE intermediate driver still tries to send some packets on the LAN. The 4401 NDIS Driver code for reporting Link Status as Disconnected and its Send_Packets function try to acquire a software spinlock two ti mes which leads to system OS lockup. This problem only occurs with ADSL PPPOE intermediate driver installation and removal of the LAN cable. Change: Changed 4401 NDIS driver code to avoid the deadlock condition and not try to send packets while the LAN connection is disconnected. Impact: Correct CQ#24514 issue.

Version 4.43 February 08, 2006 -------------------------------------------------------1. Enhancement Requests CQ#22360 and CQ#22361 4401: Turn Off 4401 Timer and Interrupts before transition to S1/S3/S4 sleep states. Cause: To achieve functional parity with BCM57xx NDIS Driver that also turns off its timers and interrupts prior to transition to sleep state. Change: Added driver code to turn off the 4401 Timer and Interrupt before transition to S1/S3/S4 states. Impact: Complete CQ#22360 and CQ#22361 enhancement request. 2. Problem (CQ#23018) 4401 Windows S5 Shutdown WOL capability was determined by the Windows "Allow this device to bring the computer out of standby" checkbox of Power Management Tab.

Cause: 4401 Driver code implementation from v4.17 to 4.42 would turn Off the PHY and Disable S5 WOL when "Allow this device to bring the computer out of standby" was not set. And was enabling S5 WOL when it was set. Change: Changed v4.43 and greater 4401 Driver to look up new NDIS configuration word in the 4401 SPROM NVRAM that has S5 WOL Option as Default ON for all present 4401 NICs and LOMs; and save that setting for Enable or Disabling of S5 WOL during transition to actual S5 Shutdown state. Impact: Correct CQ#23018 issue. 3. Enhancement Request CQ#22371 4401: Add 4401 OEM Device IDs to support new OEM projects in OEM installation INF only. Cause: New Device ID support request. Change: Added the requested Device ID to be supported. Impact: Complete CQ#22371 enhancement request.

Version 4.42 December 06, 2005 -------------------------------------------------------1. Enhancement Request CQ#14654 4401: Add two 4401 OEM Device IDs to support new OEM projects in OEM installation INF only. Cause: New Device ID support request. Change: Added the requested Device IDs to be supported. Impact: Complete CQ#14654 enhancement request. 2. Problem (CQ#22185) 4401B0-E locks System Under Test running new NDIS6 test script 1c_ChimneyReqCov Cause: New test script covers NDIS Chimney query operations. Change: Changed 4401 NDIS driver code to return proper data size for all input parameter conditions. Impact: Correct CQ#22185 issue. 3. Problem (CQ#22187) 4401B0-E Locks System Under Test running new NDIS6 Tester script 1c_NdisRequestCov Cause: New test script version checks for returned data size with various input parameters. Change: Changed 4401 NDIS driver code to return proper data size for all input parameter conditions. Impact: Correct CQ#22187 issue.

4. Problem (CQ#22233) 4401B0-E fails 1c_WMICoverage NDIS6 WHQL test script Cause: New test script version checks for returned data size with various input parameters. Change: Changed 4401 NDIS driver code to return proper data size for all input parameter conditions. Impact: Correct CQ#22233 issue. 5. Problem (CQ#22234) 4401B0-E fails 1c_OidsWMI NDIS6 WHQL test script Cause: New test script version checks for returned data size with various input parameters. Change: Changed 4401 NDIS driver code to return proper data size for all input parameter conditions. Impact: Correct CQ#22234 issue.

Version 4.41 November 15, 2005 -------------------------------------------------------1. Enhancement Request 4401: Use newer DDK from Microsoft with default -GS compile option for OS inclusion submission. Cause: Use new Microsoft DDK released driver kit. Change: Modified build directive file to use newer Microsoft DDK. Impact: Complete enhancement request.

Version 4.40 November 09, 2005 --------------------------------------------------------1. Enhancement Request: Improve handling of statistic OIDs while device is in Low Power Mode. Cause: New WHQL test case putting device into Low Power mode and then issue statistics query OIDs. Change: Added check and reject of statistic OIDs while device is in Low Power Mode. Impact: Resolve handling of statistic OIDs Enhancement Request. Version 4.39 November 05, 2005 --------------------------------------------------------1. Problem (CQ#14582) 4401: v4.38 Fails running test 2c_OidsNdisRequest

in Windows Vista Cause: New test script version checks for returned data size and non implemented OIDs. Change: Changed 4401 NDIS driver code to return proper data size and reject unimplemented OIDs as unsupported. Impact: Correct CQ#14582 issue. 2. Problem (CQ#14503) 4401: v4.38 Fails running NDIS tester scripts 1c_64BitOids in Windows Vista. Cause: New test script version checks for returned data size with various input parameters. Change: Changed 4401 NDIS driver code to return proper data size for all input parameter conditions. Impact: Correct CQ#14503 issue.

Version 4.38 November 02, 2005 --------------------------------------------------------1. Enhancement Request 4401: Use newer DDK from Microsoft with default -gs compile option for OS inclusion submission. Cause: Newer Microsoft DDK available. Change: Modified build directive file to use newer Microsoft DDK. Impact: Complete enhancement request.

Version 4.37G *** INF Update *** December 12, 2005 Same driver binary files as prior v4.37 Driver Release --------------------------------------------------------1. Enhancement Request CQ#22371 4401: Add two 4401 OEM Device IDs to support new OEM projects in OEM install INF file only. Cause: New Device ID support request. Change: Added the requested Device IDs to be supported. Impact: Complete CQ#22371 enhancement requests.

Version 4.37F *** INF Update *** November 16, 2005 Same driver binary files as prior v4.37 Driver Release --------------------------------------------------------1. Enhancement Request CQ#14654 4401: Add two 4401 OEM Device IDs to support new

OEM projects in OEM install INF file only. Cause: New Device ID support request. Change: Added the requested Device IDs to be supported. Impact: Complete CQ#14654 enhancement requests.

Version 4.37E *** INF Update *** September 15, 2005 Same driver binary files as prior v4.37 Driver Release --------------------------------------------------------1. Enhancement Request CQ#14026 4401: Add two 4401 OEM Device IDs to support new OEM projects. Cause: New Device ID support request. Change: Added the requested Device IDs to be supported. Impact: Complete CQ#14026 enhancement requests.

Version 4.37D *** INF Update *** September 15, 2005 Same driver binary files as prior v4.37 Driver Release --------------------------------------------------------1. Enhancement Request CQ13695 4401: Remove 4401 OEM Device ID as a result of OEM switch to 57xx device. Cause: OEM request. Change: Removed the requested 4 part PCI Device ID. Impact: Complete CQ13695 enhancement request.

Version 4.37C *** INF Update *** August 24, 2005 Same driver binary files as prior v4.37 Driver Release --------------------------------------------------------1. Enhancement Request (CQ#13778) 4401: Add 4401 OEM Device ID to support new OEM project. Cause: New Device ID support request. Change: Added the requested Device ID to be supported. Impact: Complete CQ#13778 enhancement requests.

Version 4.37B *** INF Update *** August 12, 2005 Same driver binary files as prior v4.37 Driver Release

--------------------------------------------------------1. Enhancement Request (CQ#13694 and CQ13695) 4401: Add two 4401 OEM Device IDs to support new OEM projects. Cause: New Device ID support request. Change: Added the requested Device IDs to be supported. Impact: Complete CQ#13694 and CQ13695 enhancement requests.

Version 4.37 (August 05, 2005) ------------------------------------1. Problem (CQ#13192) 4401: TX/RX packet counters during big file transfer was not as expected . Cause: The 4401 NDIS driver did not refresh its statistics often enough and the hardware counters rolled over. Change: Changed 4401 NDIS driver code to refresh driver statistics much more often and therefore not let the hardware packet counters roll over to ze ro. Impact: Correct CQ#13192 issue.

Version 4.36 (August 02, 2005) ------------------------------------1. Problem (CQ#13564) 4401: 4401 Cannot gain DHCP address with 2GB or more RAM in Microsoft Windows Longhorn Operating System. Cause: As a result of 4401 Hardware addressing limitation of maximum thirty bits on PCI bus; when OS gives valid PCI addresses that have bits 30 and or 31 set (starting from address bit 0) the 4401 encounters PCI bus Read errors and can not recover. All prior 4401 NDIS drivers did not do a range check of PCI physical bus addresses that were supplied by the OS; and would encounter same errors in a system that has 2 or more GB of memory with Windows Longhorn that takes advantage of this large RAM size. This problem is limited to 4401 v4.35 and earlier drivers; installed on Windows Longhorn x32 and x64 versions. Change: Modified the 4401 NDIS5 and NDIS5.1 driver source code to call and use Microsoft DDK Memory Manager API functions: MmAllocateContiguousMemorySpecifyCache() and MmGetPhysicalAddress() instead of DDK NDIS function: NdisMAllocateSharedMemory(). The DDK Memory Manager API function MmAllocateContiguousMemorySpecifyCache() allows 4401 driver to specify maximum memory physical address range so that the memory resource supplied by the OS will not have either bits 30 and or 31 s et; therefore eliminating the 4401 Hardware PCI addressing limitation

problem as a result of this driver workaround. Impact: Correct CQ#13564 issue.

Version 4.35 (July 07, 2005) ------------------------------------1. Enhancement Request (CQ#13333) 4401: Add 4401 OEM Device ID to support new OEM project. Cause: New device ID support request. Change: Added the new device ID support. Impact: Correct CQ#13333 issue.

Version 4.34 (June 29, 2005) ------------------------------------1. Problem (CQ#13292) 4401: Win2K installation of v4.33 does not show proper event log mes sages. 4401 Driver v4.25 to 4.33 installations for Windows 2000 had a probl em in proper Windows Event Log message logging. This resulted in common Network Device logging messages for 4401 (i.e. Link Up or Link Down) to be showing: [The description for Even t ID 4 in source bcm4sbe5 cannot be found. The local computer may not have the necessary Registry information to display messages.] This problem was only a driver Windows 2000 Event Logging issue and overall 4401 NDIS 5 or NDIS 5.1 driver operation was not affected. Cause: During merge of NDIS 5 and NDIS 5.1 Installation INF files into one common version (v4.24 to v4.25); an INF file error was introduced such that NDIS 5 installations did not get the proper Windows Regist ry link to the driver bcm4sbe5.sys file for driver messages. This problem does not exist for any of the v4.25 to v4.33 4401 XP Drivers since the Windows Registry link to bcm4sbxp.sys was setup correctly. Change: Modified the common NDIS 5 and NDIS 5.1 b44win.inf installation INF file to properly link the driver bcm4sbe5.sys in the Windows Registr y so that Event Log messages are correctly displayed. Impact: Correct CQ#13292 issue.

Version 4.33 (June 16, 2005) ------------------------------------1. Problem (CQ#13162) 4401: Add new 4401 OEM device ID to support new OEM project.

Cause: New device ID support request. Change: Added the new device ID support. Impact: Correct CQ#13162 issue.

Version 4.32 (June 15, 2005) ------------------------------------1. Problem (CQ#13133) 4401 AMD64 driver 4.31 fails 1c_KernelCalls for HCT12.1.1 Cause: New AMD64 Driver had a printf defined as DbgPrint() causing an unwanted Operating System Kernel DbgPrint() function call. Change: Modified the 4401 driver printf define to be an empty define. Impact: Correct CQ#13133 issue.

Version 4.31 (June 10, 2005) ------------------------------------1. Problem (CQ#13106) 4401 AMD64 driver "bcm44amd64.sys" does not follow the 8.3 naming standard specification. Cause: New AMD64 Driver name was not same as requirements. Change: Renamed the AMD64 Driver to b44amd64.sys and updated AMD64 applicable INF installer files. Impact: Correct CQ#13106 issue. 2. Enhancement Request (CQ#13111) 4401: OEM would like to disable FlowControl by default on their device which has 4 part PCI ID matching. Cause: New OEM request for device already supported. Change: Modified OEM specific device support to disable FlowControl as default. Impact: Correct CQ#13111 issue.

Version 4.30 (May 26, 2005) ------------------------------------1. Problem (CQ#12636) 4401: Add new 4401 OEM device IDs to support new OEM projects. Cause: New device ID support request. Change: Added the new device ID support.

Impact: Correct CQ#12636 issue. Version 4.29 (May 05, 2005) ------------------------------------1. Enhancement Request (CQ#12117) 4401: Request to have ability not to strip the 802.1Q tagging information from the packets. Cause: Original driver implementation. Change: Added read of Windows Registry for new "PreserveVlanInfoInRxPacket" Boolean that can be set to 1 to tell 4401 driver not to strip 802.1Q VLAN tags on the Received incoming packets. Default 4401 Driver behavior is retained (802.1Q VLAN tags removed) when this new Registry key is not present or if it set to 0. This parameter is intended to be used only when advanced users want to use the 4401 device in a network monitor type of application, and that setting this parameter in other scenarios could actually lead to network level application failures if VLAN is enabled, because the 802.1Q VLAN tags would not be stripped, even though the OS expected them to be stripped. Please do not add or set this new Registry parameter unless you are developing or demonstrating IP Network sniffers. Impact: Resolve CQ#12117 Enhancement Request. 2. Problem (CQ#12635) 4401: Driver doesn't retain forced 10 Mbps setting after system wakeup from S3 Standby mode. This occurs only if Speed & Duplex option is set to 10 Mbps and "Allow this device to bring the system out of Standby/Hibernate" in the Windows power management tab is unchecked. Cause: Version 4.28 and earlier 4401 Drivers did retain the forced 10 Mbps option when transition to S3 Standby was made. Change: Added 4401 driver code to retain the forced 10 Mbps option when going to Standby mode and when waken up from Standby or Hibernate. Impact: Correct CQ#12635 issue. 3. Enhancement Request 4401: Add x64 Operating System Support for EM64T and AMD64 Systems. Cause: Original driver implementation did not support EM64T and AMD64 x64 S ystems. Change: Migrated the 4401 Driver sources and builds to have 32 bit and 64 bi t Operating System support capability for versions 4.29 and greater. Impact: No impact is anticipated for current 32 bit Operating Systems. Known Problems: Some AMD64 Systems with Chip Sets other than Intel have exhibited PCI Bus interface problems when Broadcom Evaluation 4401 NIC has bee

n installed in their 32 bit and 64 bit PCI Slots. Please contact Broadcom Support for further information.

Version 4.28 (February 02, 2005) *** INF Update Only *** ---------------1. Problem (CQ#11972) 4401: Add new 4401 OEM device ID's to support OEM. Cause: New device ID support request. Change: Added the new device ID support. Impact: Correct CQ#11972 issue. Version 4.28 (November 23, 2004) *** INF Update Only *** ---------------1. Problem (CQ#11417) 4401: Add 6 new 4401 OEM device ID's to support OEM. Cause: New device ID support request. Change: Added the new device ID support. Impact: Correct CQ#11417 issue.

Version 4.28 (November 01, 2004) *** INF Update Only *** ---------------1. Problem (CQ#11166) 4401: Add 4401 OEM device ID's to support OEM mobile project. Cause: New device ID support request. Change: Added the new device ID support. Impact: Correct CQ#11166 issue. 2. Problem (CQ#11207) 4401: Add 4401 OEM device ID with custom Error and Information logging. Cause: New device ID support request. Change: Added the new device ID support with custom logging. Impact: Correct CQ#11207 issue. 3. Problem (CQ#11188) 4401: Add 4401 OEM device ID with custom Error and Information logging. Cause: New OEM device ID support request. Change: Added the new OEM device ID support with custom logging. Impact:

Correct CQ#11188 issue.

Version 4.28 (October 11, 2004) ---------------1. Problem (CQ#10990) 4401: PSCHED error logged for OEM laptop when cable is removed and the system is put into stand-by and then resumed. Cause: 4401 driver in general uses Windows Kernel mode support function NdisMSetTimer to get 10 ticks per second or 100 millisecond interval s. Driver 4.27 and earlier versions requested 100 millisecond interval from Windows kernel support services. But since this is an inaccurat e timer, it resulted in actual 109 milliseconds or 9 ticks per second. This caused the v4.27 4401 driver to be late in responding to query of OID_GEN_LINK_SPEED and get a PSCHED Error logged. Change: Modified 4401 driver to now request a 91 milliseconds timer from Windows Kernel mode support function NdisMSetTimer, which now results in proper ten ticks per second needed for driver timeout calculations. Impact: Correct CQ#10990 issue. Version 4.27 (September 20, 2004) ---------------1. Problem (CQ#10971) 4401 fails WHQL Certification 2c_ReceiveStats NDIS Test Cause: 4401 driver reported zero for OID_GEN_RCV_NO_BUFFER Change: Modified 4401 driver to add and report the following RX missed packets, and no receive buffer condition; for OID_GEN_RCV_NO_BUFFER query operation. Impact: Correct CQ#10971 issue. Version 4.26 (September 17, 2004) ---------------1. Problem (CQ#10886) 4401 B0 fails Diagnostic in BACS2 after system wake up from S3 stand by. 4401 A1 does not have this problem, since eeprom enable control bit is only applicable to B1 devices. Cause: 4401 B0 eeprom access enable control bit was cleared in 4401 B0 chip , when system changed to full power after S3 state. Change: Added setting of 4401 eeprom access enable control bit to driver co de responsible for initialization of device after S3. Impact: Correct CQ#10886 issue for 4401 B0 devices.

Version 4.25 (August 19, 2004) **** inf Update Only **** ---------------1. Enhancement Request (CQ#10597) 4401-B0: Add new PCI 4 ID match OEM support for A1 and B0 devices. Cause: Request for new support. Change: Added new support. Impact: Correct CQ#10597 issue. 2. Enhancement Request (CQ#10682) 4401-A1: OEM DT 4401A1 Displays Locally Administered Address in Adv anced Property Page. Cause: Original version. Change: Removed Locally Administered Address from OEM 4 PCI ID match in ins tall inf file. Impact: Correct CQ#10682 issue. 3. Enhancement Request (CQ#10720) 4401-B0: Add new PCI 4 ID match OEM support. Cause: Request for new OEM Device support. Change: Added new OEM device support. Impact: Correct CQ#10720 issue.

Version 4.25 (June 18, 2004) **** inf Update Only **** ---------------1. Enhancement Request (CQ#10247) 4401-B0: Merge all inf files into a single inf file to support XP, Win2K, WinMe. Cause: Request for improvement. Change: Merged XP and Win2K and WinMe install inf files into new b44win.inf file. Win98SE and Win98 however still have to use separate install inf fi le b44win98.inf since they cannot use unified inf with XP install section. Prior driver binary 4.25 is used for quick WHQL inf update procedur e and driver signing. Impact: Correct CQ#10247 issue. 2. Enhancement Request (CQ#10418) 4401-B0: Add new PCI ID Support for OEM. Cause: Request for new OEM product.

Change: Added new PCI ID Suppport. Impact: Correct CQ#10418 issue.

Version 4.25 (May 26, 2004) ---------------1. Enhancement Request (CQ#10191) 4401-B0: Advance properties option "Locally Administered Address" v isible with OEM PCI IDs. Cause: OEM Request for custom settings. Change: Modified XP32 and NDIS5 driver install files to honor OEM request. Impact: Correct CQ#10191 issue. 2. Enhancement Request -- Correct Windows 2000 install inf file for OEM 4401: Windows 2000 custom Information and Warning Driver logging f or OEM; did not work as expected. Change: Modified 4401 Windows 2000 install inf to perform the requested cus tom logging. Impact: New event logging behavior for 4401 Windows 2000 OEM installations.

Version 4.24 (May 13, 2004) -------------1. Problem (CQ#8807) 4401: Adjust error accounting to be in line w/ 5705 Cause: Driver included Undersized Packet count in RX Error count statistic OID_GEN_RCV_ERROR. Change: Driver changed to exclude Undersized Packets for RX Error statistic OID_GEN_RCV_ERROR. Impact: Correct CQ#8807 issue. 2. Problem (CQ#9374) 4401: Drivers force setting of BUS MASTER control bit Cause: Older system BIOS may not set PCI Bus Master Enable in PCI Common C onfiguration Command. Change: Driver changed to read and set PCI Bus Master in PCI Common Configu ration Command. Impact: Correct CQ#9374 issue. 3. Problem (CQ#9875) 4401-B0: wake-up from S3 shows link even when LAN cable is removed Cause: Old connection status left in the PHY when it was powered down.

Change: Driver changed to implement a Reset PHY prior to power down of PHY. Impact: Correct CQ#9875 issue. 4. Problem (CQ#9990 part 1) 4401: When "Allow this device to bring the computer out of standby " was unchecked; the mapped network drive would be missing after wakeup from Hibernate. Cause: The 4401 PHY was turned off for power savings and would not keep pr oper connection status when it was turned back on. Change: Added PHY Reset prior to turning off the PHY; for proper connection status once it has been turned back on Impact: Correct CQ#9990 first issue. 5. Problem (CQ#9990 part 2) 4401: Very large TX and RX statistics after resume from S3/S4 slee p. Cause: The chip statistics counters needed to be cleared whenever the 4401 is transitioned from low power to full power state. Change: Added clearing of 4401 chip statistics counters upon getting comman d from Operating System to go to full power. Impact: Correct CQ#9990 second issue. 6. Problem (CQ#9990 part 3) 4401: Slow file transfers when system is woken up from Hibernate sleep. Cause: The 4401 was doing partial chip reset upon power up from Hibernate sleep; which resulted in Receive FIFO getting overrun. This condition need ed to be handled and cleared by the 4401 driver; which resulted in slow tran sfers. Change: Modified 4401 wakeup initialization procedure to perform full chip reset, and verified that the the Receive FIFO overruns do not occur. Impact: Correct CQ#9990 third issue. 7. Enhancement Request 4401: Implement custom Information and Warning Driver logging for OEM. Change: Modified 4401 XP install inf and Driver to perform the requested cu stom logging. Impact:

New event logging behavior for 4401 XP OEM installations.

Version 4.23 (September 26, 2003) -------------1. Problem (CQ#8525) 4401: OID_GEN_RCV_ERROR - remove fragmented packets Cause: Driver included Packet fragment count in RX Error count statistic O ID_GEN_RCV_ERROR. Change: Driver changed to exclude Packet fragment count for RX Error statis tic OID_GEN_RCV_ERROR. Impact: Correct CQ#8525 issue.

Version 4.22 (September 23, 2003) -------------1. Problem (CQ#8479) 4401-B0: HP INF file references to project names Cause: Driver installation inf file had project names. Change: Removed project names from driver installation inf file. Impact: Correct CQ#8479 issue.

Version 4.21 (September 22, 2003) -------------1. Problem (CQ#8499) 4401: Rx Symbol Error when connected to Fujitsu LH 1108C HUB durin g file transfers resulting into low performance throughput. Cause: The 4401 PHY hardware reports RX Symbol Errors due to collisions. These RX Symbol Errors can be ignored because the CRC Check is the ultimate decision maker if a packet should be dropped or not. This can be considered a software workaround to remedy operations w ith particular HUBs that are not compliant to IEEE Specifications. Change: A Registry key has been created for accepting packets that have bee n flagged by PHY hardware with RX Symbol Error condition. The default behavio r is to implement this Software workaround. Impact: Correct CQ#8499 issue. 2. Problem (CQ#8502) 4401: Rx Symbol Error Accounting Cause: Due to CQ 8499 we had to modify driver error accounting.

Change: Modified Driver to account for RX fragmented packets for RX total e rror statistics. Impact: Correct CQ#8502 issue.

Version 4.20 (September 19, 2003) -------------1. Problem (CQ#8392) 4401: PME Enable setting in conjunction with WOL Cause: Request to reduce power consumption during low power to zero amps. Change: Driver enables PowerManagementEnable (PME) when WOL is not "None" in the Advanced Properties of 4401; and Windows "Allow this device to Wake up..." is also set. Impact: Correct CQ#8392 issue.

Version 4.19 (September 18, 2003) -------------1. Problem (CQ#8482) 4401-B0: WinXP - 'Allow only management stations ...' doesn't stic k when Advanced option was set to Magic Packet Cause: For 4401-B0 Driver was not reporting Magic Packet support during se rvice of OID_PNP_CAPABILITIES. Change: Corrected Driver handling of OID_PNP_CAPABILITIES for B0 chip. Impact: Correct CQ#8482 issue.

Version 4.18 (September 18, 2003) -------------1. Problem (CQ#8472) 4401 B0 does not show 'Both' in Wakeup capabilities in Win 98/Me Cause: Driver installation inf file did not specify correct options for WO L for 4401 B0. Change: Corrected Driver installation inf file for proper 4401 B0 WOL suppo rt. Impact: Correct CQ#8472 issue. 2. Problem (CQ#8479) 4401-B0: HP INF file references to project names Cause: Driver installation inf file had project name. Change: Driver installation inf file project name was removed.

Impact: Correct CQ#8479 issue. 3. Problem (CQ#8482) 4401-B0: WinXP - 'Allow only management stations ...' doesn't stic k Cause: For 4401-B0 Driver was not reporting Magic Packet support during se rvice of OID_PNP_CAPABILITIES. Change: Corrected Driver handling of OID_PNP_CAPABILITIES for B0 chip. Impact: Correct CQ#8482 issue.

Version 4.17 (September 15, 2003) -------------1. Problem (CQ#8392) 4401: PME Enable setting in conjunction with WOL Cause: Request to reduce power consumption during low power to zero amps. Change: Driver enables PowerManagementEnable (PME) when WOL is not "None" in the Advanced Properties of 4401; and Windows "Allow this device to Wake up..." is also set. Impact: Correct CQ#8392 issue.

Version 4.16 (September 15, 2003) -------------1. Problem (CQ#8463) 4401 B0 failed to wake up with MagicPacket when local administered address advanced option was set to a custom value. Cause: 4401 Driver was always using permanent address to setup MagicPacket WOL instead of the optional local administered address. Change: 4401 Driver was modified to use local administered address if set; or use permanent address if local administered is not specified. Impact: Correct CQ#8463 issue.

Version 4.15 (September 10, 2003) -------------1. Problem 4401: Installation .inf file update to support OEM. Cause: New 4401 PCI Device Identification. Change: 4401 Driver installation .inf file was updated.

Impact: None.

Version 4.14 (September 9, 2003) -------------1. Problem (CQ#8441) 4401: Failed WHQL HCT 11.2 ChkInf test procedure. Cause: 4401 Driver installation .inf file was missing a string definition for DriverOEMVersion Change: 4401 Driver installation .inf file was updated to have this string definition. Impact: Correct CQ#8441 issue.

Version 4.13 (September 3, 2003) -------------1. Problem (CQ#8325) 4401: Rpt2.0SI- Windows XP Event Viewer error: PSched: The netcard driver failed the query: OID_GEN_LINK_SPEED. This error occured when cable was di sconnected. Cause: 4401 Driver was waiting seven seconds for Link up prior to handling of the above OID. Change: Modified 4401 Driver to wait maximum of 3.9 seconds and then comple te the above OID when cable has been disconnected and link was not established. Impact: Correct CQ#8325 issue. 2. Problem (CQ#8358) 4401-B0, NDIS5.1 Intermittently Fails to Wake Up from The Standby S leep State Cause: 4401 Driver setup for case of Both Magic Packet & WakeUp Frame WOL was not correct. Change: Corrected 4401 Driver setup for case of Both Magic Packet & WakeUp Frame WOL. Impact: Correct CQ#8358 issue. 3. Problem (CQ#8393) 4401 B0 halts NDIS tester during 2m_WOLMagicPacket script in Win2k WHQL Tests. Cause: 4401 Driver setup for case of Magic Packet WOL was not correct. Change: Corrected 4401 Driver setup for Magic Packet WOL. Impact: Correct CQ#8393 issue.

4. Problem (CQ#8412) 4401-B0 Drops Network Connection Once Awaken from Standby, via Mag ic Packet. Cause: 4401 Driver setup for case of Magic Packet WOL was not correct. Change: Corrected 4401 Driver setup for Magic Packet WOL. Impact: Correct CQ#8412 issue.

Version 4.12 (August 29, 2003) -------------1. Problem (CQ#8392) 4401: PME Enable setting in conjunction with WOL Cause: Request to reduce power consumption during low power to zero amps. Change: Driver would only enable PowerManagementEnable (PME) when WOL is no t "None" in the Advanced Properties of 4401. Impact: Correct CQ#8392 issue. 2. Problem (CQ#8391) 4401 fails WHQL 2m_wolPattern test with Windows XP NDIS tester Cause: Driver setup of WOL Patterns when WOL Both option was selected. Change: Corrected Driver setup of WOL Patterns when WOL Both option is sele cted. Impact: Correct CQ#8391 issue.

Version 4.11 (August 22, 2003) -------------1. Problem (CQ#8358) BCM4401-B0: Intermittently Fails to Wake Up from Standby/Hibernate/ Shutdown. Cause: Incorrect driver setup of Magic Packet WOL operation for 4401 B0. Change: Corrected driver setup of 4401 B0 chip for Magic Packet WOL operati on. Impact: Correct CQ#8358 for proper WakeOnLan operation of Magic Packets and Interesting Packets.

Version 4.10 (August 18, 2003) -------------1. Problem (CQ#8306) CQ#8306 4401: Locally administered MAC Network Address.

Cause: Not implemented in prior 4401 Drivers. Change: Add Locally administered MAC Network Address to 4401 Driver. Impact: Correct CQ#8306 issue.

Version 4.00 (August 13, 2003) -------------Added support for 4401 B0 Hardware and increased driver version to 4.00

Version 3.64 (August 6, 2003) -------------Fixes: ========= 1. Problem (CQ#8224) CQ#8224 4401: function. Cause: 4401 Driver had ow power mode. Change: 4401 Driver was er mode setup. Impact: Correct CQ#8224 Magic Packet wake-up with multicast packet did not not enabled Multicast during its process to go to l modified to enable Multicast as part of its low pow issue.

2. Problem (CQ#8178) CQ#8178 4401: CRC RX Error Statistics reported was not as expecte d. 4401: Private Statistics reported during OID: T3_OID_GET_STATISTICS_COUNTERS not accum ulative. Cause: 4401 Driver reported sum of two CRC error counters with same value, resulting in CRC count that was twice as actual errors. 4401 Driver during handling of OID: T3_OID_GET_STATISTICS_COUNTERS did not use the "accumulative" method of keeping and reporting of s tatistics. Change: 4401 Driver was modified to gather and send the proper statistics. Impact: Correct CQ#8178 issue.

Version 3.63 (June 30, 2003) -------------Fixes: ========= 1. Problem (CQ#8101) CQ#8101 BCM4401-A1 NIC/LOM Intermittently fails to retain correct

line speed when Advanced Option is set to 10Half Mbps; and running BACS Diagno stics. Cause: 4401 Driver did not reinitialize the PHY options after going in and out of Diagnostic mode; as a result of driver change for CQ#8027. Change: 4401 Driver was modified to reinitialize the PHY options when Diagn ostic mode is done. Impact: Correct CQ#8101 issue.

Version 3.62 (June 24, 2003) -------------Fixes: ========= 1. Problem (CQ#8085) CQ#8085 4401: 802.1p Priority Tagging not as expected. Cause: 4401 always generated 802.1p Priority marked packets, when its Adva nced Option was set to Enable 802.1p. Change: Modified driver to generate 802.1p Priority marked packets only whe n packet priority is non zero; per Windows XP Device Driver Kit documentation. Impact: Same 8021.p Priority Tagging as Broadcom 570x Adapters.

Version 3.61 (June 18, -------------Fixes: ========= 1. Problem (CQ#8027, CQ#8027 lex with 802.1p option

2003)

CQ#7976, CQ#7806) 4401: WinXP - connectivity issue when changing speed/dup set and QoS Packet Sheduler enabled. CQ#7976 - 4401: Intermittently Loses Network Connection upon Change in Line Speed/Duplex CQ#7806 - 4401: IP address gets lost after changing from 10HDX->AUT O->100HDX Cause: 4401 Driver was taking longer than 3 seconds to respond to OID_GEN_ MEDIA_CONNECT_STATUS; which caused Microsoft NDIS component "QoS Packet Scheduler" to dis able IP address of 4401. Change: Modified driver to respond to OID_GEN_MEDIA_CONNECT_STATUS quicker, by increasing the frequency of Phy Link status check. Impact: Resolve connectivity issues CQ#8027, CQ#7976, CQ#7806 2. Problem (CQ#7842)

4401: Link activity reported by driver included Broadcast and Multi cast Packets Cause: Original implementation. Change: Modify driver to report only Unicast Packets when polled for Link a ctivity. Impact: None. 3. Problem (CQ#7788) 4401: The Power Management Tab for 4401 disappears intermittently Cause: Operating System Suspected. Change: Modified driver to wait 50 milliseconds before returning the result of PlugNPlay Power Management Query OIDs. Impact: None.

Version 3.60 (May 15, 2003) -------------Fixes: ========= 1. Problem (CQ#7796) 4401: BACS Diagnostics does not finish MAC- LoopBack test at 10 Hal f Duplex. Cause: Reported Link Down to NDIS while running this test. Change: Keep Link Status Up while running this MAC LoopBack test. Impact: Resolve the problem of the MAC LoopBack diagnostic not finishing.

Version 3.59 (May 9, 2003) -------------Fixes: ========= 1. Problem (CQ#7699) 4401: Slow boot time when network cable unplugged Cause: 4401 Initial report for OID_GEN_MEDIA_CONNECT_STATUS was Link Up when Network Cable was disconnected. Part of Microsoft Workaround for Pushing Policy issue. Change: 4401 driver pends this request and determines link connection statu s first and then indicates results to caller of OID_GEN_MEDIA_CONNECT_STATU S.

Impact: Improve boot time and resolve this issue. 2. Problem (CQ#7700) 4401: NDIS Tester 3.91 failure in function 1c_ginfo.leth Cause: 4401 Initial report for OID_GEN_MEDIA_CONNECT_STATUS was Link Up when Network Cable was disconnected. Part of Microsoft Workaround for Pushing Policy issue. Change: 4401 driver pends this request and determines link connection statu s first and then indicates results to caller of OID_GEN_MEDIA_CONNECT_STATU S. Impact: Resolve NDIS Tester 3.91 failure in function 1c_ginfo.leth 3. Problem (CQ#7669) 4401: BACS LoopBack PHY diagnostic runs indefinitely when testing at 10Half Duplex. Cause: Reported Link Down to NDIS while running this test. Change: Keep Link Status Up while running this PHY LoopBack test. Impact: Resolve the problem of the LoopBack PHY diagnostic not finishing.

Version 3.58 (April 26, 2003) -------------Fixes: ========= 1. Problem (CQ#7095) 4401: Spurious connection drops when connected at 100Half with Dell 5224 Switch and DHCP mode. Cause: 4401 driver did PHY isolate prior to setting forced 100Half Duplex mode. Change: 4401 driver no longer doing PHY isolate prior to setting 100Half Du plex mode. Impact: Proper operation with Dell 5224 switch at 100Half and DHCP mode.

2. Problem (CQ#7606) Operating System crash while running BACS diagnostics and pinging o ut in Windows NT 4. Cause: 4401 driver did NdisMSendComplete for discarded and or modified pac kets during diagnostics. Change: 4401 driver updated to flush modified packets.

Impact: No Operating System crash during BACS Diagnostics while pinging out .

Version 3.57 (April 24, 2003) -------------Fixes: ========= 1. Problem (CQ#7324) 4401 equipped systems had link issues with Dell 5224 Switch in DHCP mode at 100 Half Duplex. Cause: 4401 driver handling of 100 Half Duplex setting. Change: 4401 driver proper setting of 100 Half Duplex. Impact: Correct link issues with Dell 5224 Switch in DHCP mode at 100 Half Duplex. 4. Problem (CQ#7596) 4401 Not doing WOL from S5 Shutdown when 'wake up frame' is selecte d. Cause: Original design. Change: Modified 4401 driver to do WOL with Magic Packet when 'wake up fram e' is selected for Dell SubVendor programmed device ID. Impact: 4401 Dell SubVendor device will now do WOL from S5 Shutdown when ma gic packet is sent to it.

Version 3.56 (April 21, 2003) -------------Fixes: ========= 1. Problem (CQ#7537) 4401 equipped systems in Win98 cannot connect using only NetBeui pr otocol. Cause: 4401 driver initialization and first link indication Change: 4401 device reports Link down until finished initialization and neg otiations. Impact: Correct problem of running only NetBeui protocol. 2. Problem (CQ#7451) 4401 equipped systems in Win2k switching from TCP/IP to Netbeui res ulted in losing connection. Change: 4401 device reports Link down until finished initialization and neg

otiations. Impact: Correct problem of losing mapped drive when only Netbeui protocol i s running. 3. Problem (CQ#7473) BACS 6.10 does not display Bus / Device Number correctly in WinNT 4 .0 for 4401 device Cause: Driver was not setting this information. Change: 4401 driver was modified to get and set this information. Impact: Correct display of Bus / Device in BACS. 4. Problem (CQ#7596) 4401 Not doing WOL from S5 Shutdown when 'wake up frame' is selecte d. Cause: Original Marketing Requirements for this product specified this. Change: Modified 4401 driver to do WOL with Magic Packet when 'wake up fram e' is selected. Impact: 4401 device will now do WOL from S5 Shutdown when magic packet is s ent to it.

---------------------------------------------------------------------------------------------------------------Version Release Date ======= ============ 3.55 03/25/03 a. Corrected SQA Bug# 7327: Wrong spelling for Broadcom name shown duri ng driver installation in Windows NT.

3.54

03/18/03

a. Corrected SQA Bug#7095: 4401: Intermittent connection down when con nected at 100Half with Dell PowerConnect switch models 5224 and 5012.

3.53 k Bar

03/18/03 a. Corrected SQA Bug#7229: BCM4401 Reported wrong line speed in the Tas upon Disabling/Enabling of device.

b. Corrected SQA Bug#4794: Broadcom Advanced Control Suite (BACS) NT 4 did not show Vital Sign information for 4401 adapters.

3.52

03/10/03

a. Corrected SQA Bug#6963: 4401 did not pad small packets with zeros. b. Corrected issue of Group Policy "Windows Startup Script" and "Logon S cript" not being applied to 4401 equipped user station. c. Corrected SQA Bug#6095: 4401 BACS does not retain network speed set ting after "Diagnostic Test". d. Corrected SQA Bug#7151: PHY Mode On/Off OID support for 4401 APIs. 3.51 12/17/02 Shared Interrupt with Audio device and runn

a. Corrected SQA Bug#6424: ing 4401 Diagnostics caused system lock up. 3.50 12/04/02

a. Corrected SQA Bug#6236: 4401 Did Wake On LAN with Interesting Packe t (ping) when OS check box "Allow this device" was not checked. b. Corrected wrong LED operation after Wake On LAN from S3 Standby state on laptops using battery.

3.49 uplex to

11/04/02 a. Corrected SQA Bug#5802: 4401 Win2K/XP speed change from 10Mb Half D

100Mb Half Duplex failed to work b. Corrected SQA Bug#5860: ustek P4GE MotherBoard 3.48 09/10/02 4401 WinME Shutdown - System Rebooted on As

a. Corrected driver issue of not logging Link Speed during Windows XP WH QL test: WHQLCheckConfig

3.47

08/30/02

a. Corrected LED display initialization in driver after wake from Standb y or Hibernate.

3.46

08/22/02 a. Submit 4401 NDIS Drivers to SQA for Microsoft WHQL HCT Testing.

3.45

08/19/02

a. Corrected Windows XP and Windows 2000 Link Indications after wake fro m Standby/Hibernate.

3.44

08/19/02

a. Corrected SQA logged bug#4512 No cable attached, 4401 shows a link i n Windows at 10mb, after going into sleep mode and waking. b. Corrected SQA logged bug#4162 4401 Cable disconnect, put in Standby, connect cable, wake, connection to network lost. 3.43 or 4401. b. Corrected SQA logged bug#4511 st in BACS, the statitics displays wrong c. Corrected SQA logged bug#4799 ibernation at 100HD d. Corrected SQA logged bug#4987 "0" and does not increment. After running "Internal Memory" diag te statistic counters. 4401 version 3 board locks up during h 4401 Received packet counter displays 08/06/02 a. Corrected SQA logged bug#4830 BACS reports wrong statistic counters f

3.42

07/18/02

a. Corrected SQA logged bug#4814 NDIS5.1 driver v3.41 fails 2c_LoadUnloa d in XP32 Pro

3.41

07/18/02

a. Corrected SQA logged bug#4811: Win2k Infchecker test fails with 4401 Ndis5 driver v3.40 3.40 07/17/02 a. Added support for Broadcom 440x OEM device and subsystem IDs. 3.39 07/16/02

a. Changed Driver to correct reporting of CRC and CRC_Align errors with OID_GEN_RCV_CRC_ERROR

and general RX errors with OID_GEN_RCV_ERROR.

3.38

07/11/02 a. Added Windows XP 32 and Windows NT 4 Driver support.

3.37

07/02/02

a. Resolved SQA Logged Bug#4652 Win2K WHQL Signability test reports erro r with 4401 Ndis5 driver.

3.36

06/17/02 a. Resolved SQA Logged Bug#4413 Netmon statistics support added. b. Resolved SQA Logged Bug#4303 802.3 and BACS statistics added. c. Resolved SQA Logged Bug#4412 directed and broadcast packets statistic

s added. d. Resolved SQA Logged Bug#4411 Frames RXed with alignment error statist ics added. e. Resolved SQA Logged Bug#3881 System locks up with 4401 during NDIS Te sting in Win2K. f. Resolved SQA Logged Bug#3910 System stop during Win2K Certification. g. Resolved SQA Logged Bug#4066 System hangs during Win2k certs with 440 1.

3.35

06/06/02 Mapped Drive not available after wake up Cable disconnect in sleep state/connecti No cable attached, 4401 shows a link in mode CRC error count not supported using Netm Power management option "Allow this devi is grayed out when D

a. Resolved SQA Logged Bug#4160 from Standby/Hibernate. b. Resolved SQA Logged Bug#4151 on lost. c. Resolved SQA Logged Bug#4186 Windows at 10mb, after going into sleep d. Resolved SQA Logged Bug#4382 on. e. Resolved SQA Logged Bug#4395 ce to come out of standby" ell Magic Packet is set. 3.34 05/30/02

a. Resolved SQA Logged Bug#4324 wrong version in BACS displayed for NDIS Driver. b. Updated WOL Advanced Options.

3.33

05/17/02

a. Resolved SQA Logged Bug#4154 WOL at S5 sleep state did not work on al l ACPI compliant systems.

3.32 ents.

05/16/02 a. Set FlowControl Default Option to Enabled per Dell Software Requirem

b. Set Default WakeOnLan Advanced Option to "Wake Up Frame" for WHQL C ertification. c. Corrected SQA Bug#4183 Win2K Certification test 1c_ginfo failure. 3.31 05/08/02 a. Set WakeOnLan Default Option to Both (Magic Packet and Wake Pattern) 3.30 Suite. b. Resolved SQA Logged Bug#4078 Driver Statistics Display in BACS Cont rol Suite. c. Resolved SQA Logged Bug#4053 System Wake on Ping When only Magic pa cket enabled. 3.29 05/03/02 a. Modified driver for performance and submit to Broadcom SQA. 05/08/02 a. Resolved SQA Logged Bug#4077 Driver Version Display in BACS Control

3.27

04/30/02 a. Corrected Windows System Shutdown issue noted as prior errata. b. Corrected Win2K WHQL Test 1c_ginfo.tst failures.

3.26

04/24/02

a. Added Flow Control advanced option. b. Corrected failing WHQL 2m_WOLPattern test. Errata 1: Some systems may experience power shutdown problems when "Shutdown" requested from the Windows Start button. In this situation please press the Reset button of th e system first and then press the system Power button.

3.25

04/22/02

a. Resolved warnings encountered during 1c_64BitOids Windows XP Certifi cation Tests. b. Added Advanced Adapter Options Key for Wake On LAN choices. c. Added Dell/Broadcom DTWOL Magic Packet Wake On LAN support. Errata 1: Some systems may experience power shutdown problems when "Shutdown" requested from the Windows Start button. In this situation please press the Reset button of th e system first and then press the system Power button. 3.24 04/12/02 a. Updated driver settings for duplex performance. 3.23 04/11/02 a. Submit to Broadcom SQA for XP and Win2K Certification. 3.22 ers. 3.21 03/27/02 04/03/02 a. Resolve Bug#3774 - Wrong Driver version in BACS for 4401 NIC Adapt

a. Resolve Bug#3525 - The NIC option 802.1P "Priority Handling" disab le/enable for WHQL HCT test 2m_prior. 3.20 02/27/02 a. Resolve Bug#3281 - Control Suite Failure while testing MAC and PHY Loopback tests. 3.19 sting; missing Catalog file entry added. b. Resolve Bug#3426 - Inchecker test in Windows 2000; BASEDRIVERFILEVERSION entry added. 3.18 02/22/02 a. Resolve Bug#3326 - Device name under Event Viewer corrected. b. Resolve Bug#3336 - Logging of Link Status and Speed for Windows XP and Windows 2000 Pro and Server. 3.17 02/19/02 02/27/02 a. Resolve Bug#3427 - Signability test in Windows ME Certification te

a. Change Adapter name to "Broadcom 440X Fast Ethernet Controller" 3.16 02/19/02 a. Resolve Bug#3291 - Device Name to 4401 b. Resolve Bug#3286 - InfChecker issue with unreferenced name c. Resolve Bug#3282 - Forced and Auto Speed Setting Correction 3.15 02/14/02 a. Change Advanced Options display text to match other Broadcom driver. 3.14 02/14/02 a. Initial Release of 4401 Driver