ReleaseNotes.txt Driver File Contents (nforce3_Win2K-XP.zip)

                                    RELEASE NOTES
                                    -------------

This file needs to be updated each time a change is made to the mcp3 folder.
This file describes in detail the code/INF/makefile changes made, perforce check-in number, testing done by the 
programmer and testing expected out of QA. You can copy and paste from Perforce history the perforce change number and 
comments if they are detailed.

All new additions in this file appear at the top - Always append to the begining of the file, below this block, betweem
the lines.
---------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------
---------------------------------------------------------------------------------------------------------------

Change 877174 by nbhat@NBHAT-DT2 on 2003/09/25 18:48:32

CK8S segmentation code added.
CK8S has 3 models NF3-250 and NF3-250-1000 (Both CK8 Non Pro), NF3-250-PRO (CK8 Pro).
Only Pro model has ASF, WOLS5 and Vlan enabled. Non pro models do not have these.
Testing efforts:
  Test all models of CK8S and make sure that features are enabled/disabled for a particular model.
  MCP2S - Make sure ASF, WOL from S3/S4/S5, Vlan is not broken.
  CK8 and MCP2 - Use monolithic driver and make sure that ASF, WOL from S3/S4/S5, Vlan is not broken.
  MCP2 - Use monolithic driver and make sure that WOL from S3/S4/S5 is not broken.
Things to keep an eye on:
   ASF timer function - make sure it functions properly on CK8 (Pro and NonPro), MCP2S and CK8S


---------------------------------------------------------------------------------------------------------------

Change 801298 by nbhat@NBHAT-DT2 on 2003/07/25 16:19:49

Changes added as per the rquest of NetMgmt team.
Checksum offload is being broken into two variables now, from the original bitmask that was exposed in the 
Advanced tab.
bChecksumOffloadEnable    : Boolean - Enable or Disable. Exposed in Adv tab.
ulChecksumOffloadBM       : Bitmask value. Not exposed in Adv tab. Exposed in Net mgmt app.
Format is the same as earlier.This value is applied only if the bChecksumOffloadEnable is 1. This should be 
made 0 if bChecksumOffloadEnable is 0.

JumboFrameSize is mapped to the ulMaxPacketSize directly, but is changed to enumarator now.
Mappings are as follows:
Enum value     Max Payload Size    ulMaxPacketSize (incl FCS)
  0 (deafult)      1500             1518   
  1                2500             2518
  2                4500             4518
  3                9000             9018

INF file cleaned up, all variables localized, unnecessary sections deleted.

//sw/main/drivers/network/mcp3/common/include/adapter.h#18
//sw/main/drivers/network/mcp3/windows/ethernet/cfgmgr.c#13
//sw/main/drivers/network/mcp3/windows/ethernet/myndis.h#35
//sw/main/drivers/network/mcp3/windows/ethernet/nvenetfd.inf#15
//sw/main/drivers/network/mcp3/windows/ethernet/parse.c#22

Testing done:
------------
Installation, uninstallation testing. Debug build: Checksum offload variables set to right value

QA testing:
-----------
Run WHQL Checksum offload test for following combinations:
   - Disabled in Adv tab
   - Enabled in Adv tab - Change different values of Checksum offload using Netmanagement
Test with different values of jumbo frames.

---------------------------------------------------------------------------------------------------------------
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: web3, load: 3.76