==============================================
USING THE NETXTREME II MONOLITHIC "RIS" DRIVER
==============================================

Due to limitations in Microsoft's operating systems not supporting the Virtual Bus Device architecture of the NetXtreme II adapter under certain circumstances, separate drivers were created to address these limitations. The NetXtreme II monolithic driver allows the adapter to behave similarly to standard network adapters and only provides network connectivity without the advanced offerings of the device. The monolithic driver should be used for connectivity during the text mode portion of a RIS installation (by placing in the I386 or AMD64 platform directory),  in a Windows Preinstallation Environment (Windows PE), and for the agent used for Microsoft's Automated Deployment Services (ADS).  

When using to deploy a RIS image from a Windows 2000 Server, you may experience an error indicating that the driver for the NetXtreme II device cannot be found.  This is despite having the monolithic driver in the platform directory.  This is due to a parsing error that occurs in Windows 2000 only.  To work around this issue, the following modification is required to the b06nd.inf file located in the platform directory:

- Locate [Manufacturer] within the file. 
- Review the line below which reads: %brcm% = broadcom, ntx86, ntamd64, ntia64 
- Modify that line to read: %brcm% = broadcom.ntx86, ntamd64, ntia64 (The change made replaces the comma and space after "Broadcom" with a period). 
- Save the file. 
- You must restart the "Boot Information Negotiation Layer" service in order for the change made to take effect.