udiagrel.txt Driver File Contents (9528154.exe)

		     Release Note for B44UDIAG USER Diagnostics.
		    ==================================================

Version 1.33
   New Addition:
    =============
    1. Request: (ClearQuest #7467)
           Added new Error Level when diag detect invalid command line options and list proper command line
       Fix: 
           Added Error Code 141 to report invalid command line options.
version 1.32

    New Addition:
    =============
    1. Request: (ClearQuest #7679)
           Test for CAM matching capabilities. The CAM in 4401 can be programmed with 
           up to 64 MAC entries.  Each MAC entry is 48 bits, or 6 bytes.  Once CAM 
           matching is enabled, the purpose of the CAM is to filter out those packets 
           that don't match any of the entries inside the CAM.  The CAM is doing this 
           by comparing/matching the 'destination MAC' address of the incoming packet 
           with any of the 64 MAC entries in the CAM.  If at least one of the entries
           in the CAM matches the 'destination MAC' of the incoming packet, the packet 
           will be passed on by the CAM for further processing.  If no match occurs,
           the packet is silently discarded.

           This test will ensure that MAC addresses written to the CAM actually 'stick'
           (see CQ #7629). In addition to that, the test will be added in order to detect
           any matching capability problems within the CAM.

       Fix:
           Cam matching capabilities test has been added to b44diag.  
           Diag will program current MAC address to an cam entry then loopback 40 packets 
           with matching destination mac address.  If CAM is functioning, diag will receive
           all packets.   
           In addition, 3 negative tests had also been added.  The 1st -ive test is disabling CAm and no 
           packet should be received.  The 2nd -ive test is sending packets w/ unmatching 
           destination mac address and no packet should be received.  The 3rd test is setting
           unmatching CAM entry and no packet should be received either.  

version 1.31

    New Addition:
    =============
    1. Request: (ClearQuest #7629)
           We need a utility in the field to validate that we can WRITE 
           and READ validate the 64 CAM (Content Addressable Memory) entries.
	   It is recommended to W/R some specific 'pattern' that tests for 
           bits stuck to high/low.

       Fix:
           Cam test has been added to b44diag.  This test will run the CAM Read/Write Test.  
           48 Bit patterns will be written to 64 entries of the CAM space.  Test will read back 
           the 64 entries and check.  It will be tested against 5 patterns such  as FFFF, 0000, 
           5555, AAAA, 55AA, AA55.

           
version 1.30

    New Addition:
    =============
    1. Request: (ClearQuest #7439)
           When external loopback test D3 and D4 test fail provide different
           error codes for failures at 10/100/1000 Mbit/s.
       Fix: 
           Added code to achieve the above and documented new error codes.
	   Error Code: 117 */ "No good link! Check Loopback plug (10BT)",
           Error Code: 118 */ "No good link! Check Loopback plug (100BT)",
           Error Code: 119 */ "No good link! (PHY)",
	   Error Code: 33 */ "No good link! (MAC)",
           Error Code: 120 */ "Packets received with CRC error (10BT)",
           Error Code: 121 */ "Packets received with CRC error (100BT)",
           Error Code: 122 */ "Packets received with CRC error (PHY)",
           Error Code: 72 */ "Packets received with CRC error (MAC)",
	   Error Code: 123 */ "Tx DMA failed (10BT)",
           Error Code: 124 */ "Tx DMA failed (100BT)",
           Error Code: 125 */ "Tx DMA failed (PHY)",
           Error Code: 13 */ "Tx DMA failed (MAC)",
           Error Code: 127 */ "Rx DMA failed (10BT)",
           Error Code: 128 */ "Rx DMA failed (100BT)",
           Error Code: 129 */ "Rx DMA failed (PHY)",
           Error Code: 14 */ "Rx DMA failed (MAC)",

    2. Request: (ClearQuest #7155)
           User requested that an error log file is generated when an error
           occurs. Only error information is logged (NOT pass information).
       Fix: 
           Added DOS command line option "-elog <file>" to provide the feature.

Version 1.29
    1.  This is identical to v1.28
Version 1.28
    1.  This is identical to v1.28
version 1.27
    1.  Added -info switch from cmd line to display Dev ID Ven ID SVen ID SSystem ID
Version 1.26
    1.  This is identical to v1.25
Version 1.25
    1.  This is identical to v1.24
Version 1.24
    1.  Software will return error level 254 instead of 256 when there is no card found.
Version 1.23 
    1.  This is identical to v1.22
Version 1.22 
    1.  This is identical to v1.21
Version 1.21 
    1.  This is identical to v1.20
Version 1.20 
    1.  This is identical to v1.18
Version 1.18
    1.  This is identical to v1.17.
Version 1.17
    1.  TX and RX buffer memory is allocated only once during software initialization.
    2.  TX and RX buffer memory is deallocated only before software exit.
    3.  Fixed bug in all loopback tests and blast -t.  The content of the packet is corrupted.
        Instead of selected pattern being sent out, all zeros pattern is acctrually being sent out.
        This bug is found in V1.15 and V1.16.
    
Version 1.16
    1. It is identical to v1.15
Version 1.15
    1.  Added "-lbm", -lbp, -lph, -lbt command line options to specify number of packets in loopback tests.
    2.  Using the same code base as b44diag.
Version 1.14
    1.  It is identical to v1.13.
Version 1.13
    1.  Fixed Phy loopback CRC bug.
Version 1.12
    1. It is identical to v1.11
Version 1.11
    1. It is identical to v1.10
Version 1.10
    1. No longer use DOS4GW.exe, instead,DOS extended memory will be used.
    2. Reduced wait time in link_test.
    3. Reduced number of trail in led_test.
    4. Removed unused code.
    5. Reduce total tests time to 22s.(loaded from hard drive) 
Version 1.09
    1. Reduced total tests (ABC) time to less than 30s.
    2. Packet counts in loop back test has been increase from 200 to 2000
Version 1.08:
    1. Version format has been changed to x.xx.
    2. Added Error codes.
    3. External loopback test has been separated to 2 tests, C3 and C4.  C3 is 100BT and C4 is 10BT. 
    4. loopback test packet size increase to 1514 bytes (cl4xsb.c)

Version 1.07:
    1. Rename to  b44udiag.exe


Version 1.00:
    1. Initial 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: ftp, load: 2.39