This release note and the software that accompanies it are copyright (c) 2006, Intel Corporation, and may only be installed and used in accordance with the license that accompanies the software.

This Software is furnished under license and may only be used or copied in accordance with the terms of that license. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. The Software is subject to change without notice, and should not be construed as a commitment by Intel Corporation to market, license, sell or support any product or technology. Unless otherwise provided for in the license under which this Software is provided, the Software is provided AS IS, with no warranties of any kind, express or implied. Except as expressly permitted by the Software license, neither Intel Corporation nor its suppliers assumes any responsibility or liability for any errors or inaccuracies that may appear herein. Except as expressly permitted by the Software license, no part of the Software may be reproduced, stored in a retrieval system, transmitted in any form, or distributed by any means without the express written consent of Intel Corporation.

This download supports Intel(R) RAID controllers using SAS software stack (SRCSAS18E), please verify that this driver has been tested with the RAID card you have chosen to use by checking the drivers web page for your controller at http://support.intel.com.

================
Package Information
================
Driver Version = 1.17.0.32
OS supported = Windows* 2003, Windows* 2000

====================
Attention!
====================
This package contains the signed Microsoft Windows* 2003 (1.17.0.32) storport driver and the Microsoft Windows* 2000 (1.17.0.32) MiniPort driver. 

Extract package contents to a user specified location such as = a:\

================
Known Restrictions
================
This utility is not compatible with those RAID controllers using software stack 1 (SRCU21, SRCU31, SRCU31L, SRCMR, SRCZCR, SRCU32, SRCU42L, or SRCS14L) or software stack 2 (SROMBU42E, SRCU42X, SRCU42E, SRCU41L, SRCS16, SRCS28X, & SRCZCRX).

====================
Contents on the package
====================
The following files are included in this package:

Name							Description
megasas.SYS						Win2K Driver
msas2k3.sys						Win2K3 Driver
Web License.rtf						License file
NODEV.INF						Inf file
OEMSETUP.INF						Inf file
TXTSETUP.OEM						Install support	
megasas.cat						Install support	
ir3_Win2K3_Win2K_DRV_v1.17.0.32_readme.txt		This file

==================
Installation Instructions
==================
This updated driver can be applied using the normal OS installation options.
Extract package contents to a user specified location such as = a:\

This procedure installs the Intel RAID device driver on a new Windows* 2003 system. Windows 2003 automatically adds the driver to the registry and copies the driver to the appropriate directory.

1. Start the Windows installation by booting from the Windows CD-ROM.
The system BIOS must support booting from a CD-ROM. BIOS settings might require changes to allow CD-ROM booting. See your system documentation.

2. Press <F6> when the screen displays: "Press F6 if you need..."

Note: You must press <F6> for the system to recognize the new driver.

3. Choose <S> to specify an additional device when the screen displays: "Setup could not determine the type of one or more mass storage devices..."
Note: If this screen is not displayed as the first user input, then pressing <F6> was not seen by the setup program. Reboot the system, and return to step 2.

4. The system prompts for the manufacturer-supplied hardware support disk. Insert the driver diskette containing the Windows 2003 device driver, and press <Enter>.

5. Select the Windows device driver from the menu by highlighting it and press <Enter>.

6. Press <Enter> again to proceed.

7. Return to the Windows Setup screen.

8. Windows displays a "Welcome to Setup" window. 

9. Press <Enter> to proceed.

10. Follow the Microsoft Windows installation procedure to continue the OS installation.


Existing Windows System Driver Installation:
This procedure installs or updates the Intel RAID device driver on an existing Windows 2003 system.

1. Boot Windows.  The Found New Hardware Wizard begins. 

2. Click the Next button.

3. Insert the driver diskette into the A:\ drive.

4. Click the Search for a Suitable Driver... button and click Next.

5. Click the Next button.

6. Check the Specify Location box, uncheck all other boxes, and click the Next button.

7. Type A:\ and click the OK button.

8. Click the Next button on the Driver Files Search Results window.

9. Click the Finish button to complete the driver installation.

10. Repeat this process for all the controllers on your system.


================
Component Features
================
N/A

================
Known Issues
================
N/A

================
Fixes/Updates
================
1) Changing the driver not to expose any PDs when there is no logical drive information present. Functionality has been
added to turn ON/OFF this feature through the Windows debugger.
2) Driver would specify to the Firmware if there is a hotplug situation so that Firmware will spinup one drive at a time otherwise it firmware will use Vendor supplied drive spinup count.
3) Driver would support the maximum 80SGE count supported by the firmware. Previously, driver was only supporting 56 SGE count for 32bit systems and 37 SGEs count for the 64 bit systems.
4) Driver is not handling the AEN masks properly. Driver needs to ORed all the masks sends by the applicaiton and send it to Firmware. This would allow multiple application with different mask information to work properly.
5) Driver would use DeviceNumber/FunctionNumber/BusNumber to uniquely identify the controller to avoid issues with the ControllerId when Dell and LSI controllers are on the same system.
6) Driver was not handling the Shutdown call gracefully. Driver was not building the Shutdown command properly leading to the system hang. This issue has been fixed by building the shutdown command and issuing it to the firmware.
7) Hibernation/Standby issue resolved. Driver needs to send Controller/Disk flush command before sending the Hibernation/Standby command. This would allow firmware to flush all the cache.
8) Driver was not sending the WaitforEvent(AEN Frame) with the correct sequence number. This would make firmware send AENs for the incorrect sequence number.
9) Storport driver fails to load when the dataTransferLength is set to 512K. Driver was not handling the Scatter gather list properly.
10) WMI, AEN and DPC initliazation is disabled during hibernation/Standby.
11) Interrupt Vector is returned by the driver to Storelib application when the application request for PCI information.
12) Ability to detect hibernation/crashdump has been added in the driver.
13) After importing a Foreign LD the OS drive name mapping is incomplete until a "scan fo hardware changes" is performed in device manager. Driver has been fixed with the change that would allow PnP to scan the bus whenever there is a change in the logical drive configuration during the import foreign config.
14) S3 standby was not resuming. Driver would examine the contents of the STATE register and look at the time 
between changes in the register. If the register is changing, then firmware is probably initializing drives and updating the state. However, if the state register freezes for too long, then that would indicate a FW hang condition. So, during your timeout poll, if the state register changes, driver would simply restart your 60 second timeout.
15) MFI_STAT_LD_LBA_OUT_OF_RANGE was not mapped correctly to the OS status. This fix has been made and driver is returning invalid request for the mfi status MFI_STAT_LD_LBA_OUT_OF_RANGE.
16) First attempt at drive format in Win2k3 fails each time, fixed
17) After Hibernation, Deleting/Adding Logical Drives will Cause System to Crash, fixed
18) Failed during the upgrade install from W2K SP4 o W2K3 SE, fixed
19) OS takes long time to boot or format of a logical drive takes longer time to complete:
Driver is not handling the Sequence number correctly which is results in the driver sending incorrect sequence number to the firmware which causes firmware to post older AENs to the driver. This results in the endless loop of AENs getting issued to the driver and hence it slows down the performance.
20) When the driver and the FW times out, driver logs the message in the Windows event log :"The driver has detected a device with old or out-of-date firmware. The device will not be used". This message has been replaced by Driver timeout message.
21) OS or I/O hangs while running I/O on 8 LDs and script create/delete LD 9th:
For any timeouts happening for a target attached to the physical channel driver is still processing the commands from the OS and sending it to the Firmware during reset. This is leading to timer routine never able to make the PendCmds=0 and hence eventually we set the adpater to Dead.This fix has been done by blocking the commands from the OS when the driver is busy processing the outstanding commands in the resetBus on the physical channel as well.
Verion 1.16.0.xx
XP 64 inf file fails WHQL 
1) Fixed Very low performance with slow init of the logical 
2) Fixed Dirty cache LED re-illuminates during clean OS shutdown 
3) Fixed Very low performance accessing Logical Drive 
4) Fixed Unsigned drivers for adapter in WXP64 Download 


*Third-party trademarks are the property of their respective owners.


