release.txt Driver File Contents (9528154.exe)


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

	                          
              Broadcom 440x 10/100 Integrated Controller Ethernet Driver
                                       for
                                 DOS NDIS2 driver

                   Copyright (c) 2002-2003 Broadcom Corporation
		               All rights reserved.



Version 2.45 June 16, 2003
----------------------------

   Fixes:
   ========

   1. Problem: 
               (CQ #7760) 4401 NDIS2 Intermittently loses network connection
               when using NETBEUI.
      Cause:
               Unknown.
   
      Change:
               Driver's ISR handles Receive Overflow condition separately from
               Receive and Transmit interrupts.

      Impact:
               None.


Version 2.44 May 06, 2003
----------------------------

   Fixes:
   ========

   1. Problem: 
               (CQ #7695) system locks up after multiple cable
                disconnect/reconnect with link speed forced on AUT and switch.
      Cause:
               Driver polls the link status every 1 second, when its detects no
               link it will continue to check again for 20 more times in 
               55ms interval before determines the link is lost. During this
               time the cable might be reconnected and reset the counter. So
               the system appears to be lock up.
   
      Change:
               Driver maintains the 1 second interval through out.

      Impact:
               When the cable is reconnected, it would takes about 7 seconds to
               re-establish the network connectivity.


   2. Problem: 
               Using NETBEUI protocol with link speed forced, while running
               ReadRite test disconnect/reconnect the cable will cause the test
               to fail in a few hours.
      Cause:
               Driver issues chip reset when its detects Receive Overflow which
               causes by DMA engine lock-up. Because link speed was forced so
               driver setup the PHY accordingly during the reset. This causes
               link lost momentarily and was detected by the link status poll.
               When link is re-established, a PHY reset is issued and the PHY is
               getting setup again.
   
      Change:
               Driver chip reset will not setup the PHY after its initialized.

      Impact:
               None.


Version 2.43 May 01, 2003
----------------------------

   Fixes:
   ========

   1. Problem: 
               (CQ #7663) Load driver with LineSpeed forced in protocol.ini
                with the far-end is set to AutoNeg. After driver initialized,
                LineSpeed shown as forced but Link LED fluctuates and is not
                stable. Switch shows line speeds continuously alternating
                between speeds.
      Cause:
               Driver do PHY reset but never waits for the link to be stable
               before forcing the desired speed.
   
      Change:
               Driver waits for AutoNegComplete bit to set before forcing the
               speed. Also, use the SuperIsolate bit to simulate line drop
               that allows the far-end to adjust to the forced speed and duplex.

      Impact:
               None.


Version 2.42 April 28, 2003
----------------------------

   Fixes:
   ========

   1. Problem: 
               (CQ #7346) Force to any speed, device always connects
               at 100 Full.

      Cause:
               Write PHY routine using incorrect bit size as input.
   
      Change:
               Write PHY routine use TypeCast to correct size.

      Impact:
               None.

   2. Problem: 
               (CQ #7623) loss connectivity when cable was disconnect
               then reconnect.

      Cause:
               Driver does not detect link change condition.
   
      Change:
               Driver detects link change condition and reset the PHY
               when regain connection.

      Impact:
               None.


04/09/03 - v2.41-
        Support Multicast addresses.
        Fixed transmit low performance with TCP/IP.

03/19/03 - v2.40-
	Merged to current NDIS2 Upper Module.
        Utilized ODI v1.07's Lower Module.
        Reduced memory footprint to 39KB.
        No release for v1.01-v2.39.

05/17/02 - v1.00-
	First Engineering Release.
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: web1, load: 0.65