1. R193682.exe Driver
2. R193682.txt File Contents

R193682.txt Driver File Contents (R193682.exe)

Dell SAS 5 and SAS 6 Controller 
Device Driver for Windows Vista 32-bit

Version 1.28.03.01


TABLE OF CONTENTS
=================

1.0  Introduction
2.0  Compatibility / Minimum Requirements
3.0  Install Instructions
     3.1  Installing the Driver curing Operating System Installation
     3.2  Installing a Windows Driver for a New SAS Controller
     3.3  Updating an Existing Windows Driver
4.0  Driver Fixes/Enhancements
5.0  Additional Information
6.0  Known Issues 


1.0 Introduction
================

This is the Device Driver for following controllers:
 
    SAS 5 Controllers
    SAS 6 Controllers


2.0 Compatibility / Minimum Requirements
========================================

This device driver requires the following minimum Operating System version:

Windows Vista 32-bit 

Minimum SAS 5 FW package version: 00.10.51.00.06.12.05.00
Minimum SAS 6 FW package version: 00.25.45.00.06.22.02.00


3.0 Install Instructions
========================

Copy the files from the package to a media device supported by the system.
Vista supports floppies, USB keys, CD & DVD drives.

3.1 Installing the Driver during Operating System Installation
--------------------------------------------------------------

1. Power up the system and boot to the Microsoft Windows Vista DVD.
2. Follow the on-screen instructions until you reach the 
   "Where do you want to install Windows?" section.
3. Select "Drive options (advanced)". 
4. Click on "New" to create a partition to install Vista, select 
   the size in MB and click on "Apply" (consult the Vista user 
   manual to select a drive size that meets the OS demands).
5. Select "Load Driver" and browse to the location where you have 
   copied the Vista driver.
6. Select the controller used for this installation.  The system 
   will automatically select one controller. Click on "Next".
7. After the driver loads you will return to the "Where do you want 
   to install Windows?" screen. (Partitions can be configured on 
   this screen). Click on "Next" again to continue with th 
   installation process.

NOTE: Dell SAS 5 and SAS 6 controllers have Vista native support.The OS 
      installation can be executed using the native driver. In such a 
      case, when the installation completes the SAS driver should be 
      updated. See Section 3.3: Updating an Existing Windows Driver, 
      for details.


3.2 Installing a Windows Driver for a New SAS Controller
--------------------------------------------------------

Perform the following steps to configure the driver when you add a new 
controller to a system that already has Windows installed.

1. Power down the system.
2. Install the new controller in the system.
   Refer to Hardware Installation for detailed instructions on installing 
   and cabling the controller in the system.
3. Power on the system.
4. Windows Vista has native support for SAS 5 and SAS 6 controllers, the 
   system will identify the new controller and use the native driver.
5. Update with the newer driver following the steps on the next section 
   3.3: Updating an Existing Windows Driver.

3.3 Updating an Existing Windows Driver
---------------------------------------

Perform the following steps to update the Windows driver for the new 
controller already installed on your system.

NOTE: It is important that you put your system on idle before you 
update the driver.

1. Press "Start" > "Control Panel" > "System and Maintenance" > "System".
   The "View basic information about your computer" screen displays.
2. Click on the "Device Manger" link on the left.
   The "Device Manger" window opens up.
4. Click on "Storage controller". 
5. Double-click on the controller for which the driver has to be updated.
6. Click on the "Driver" tab and click on the "Update Driver" button.
   The screen for the Upgrade Device Driver Wizard displays.
7. Insert the appropriate media (Driver diskette/USB key/CD/DVD).
8. Click on "Browse my computer for driver software".
9. Click on "Let me pick from a list of device drivers on my computer".
10.Click on the "Have Disk" button and browse to the appropriate location.
11.Select the controller and click "Next".
12.The new driver will be uploaded, close all windows and reboot the system
   for the changes to take effect.


4.0 Fixes or Enhancements in this Release 
=========================================

- Force OS bus rescan after any F/W fault, to detect unreported volumes 
  changes prior to the fault.
- Add functionality to detect and properly associate existing volumes with 
  new/deleted hotspares.
- Check for inactive/active volume status before presenting the volume to 
  the OS.
- Improve handshake negotiations on drive hotplug activities.
- Log system event error when the Persistency Table is full.
- Changes on the F/W download activity to reduce impact to users.
- Increased timeout for FW download.
- Add functionality to allow removing more than 64 devices in one action.
- Added support for detecting dual port SAS drives or detecting SATA drives 
  behind a port selector
- General improvements on error detection and task management functions:
	. Improve handling of bus change requests (pause/resume/detect)
	. Better error detection for SAS tape environments
	. Better handling of NULL SRB's
	. Send Diag Reset instead of Message Unit Reset if a stuck LUN or 
          Target Reset condition occurs
	. Fixed malformed bad reply messages
	. Improvements in driver reset & escalated reset handling
	. Improvements handling error returns from FW
- Algorithm changes to better work with storport and meet all new requirements
- Added reset queue to execute resets for different target/LUNs in the 
  order received.
- Added detection of Task Aborted SCSI status returned from target to force a 
  retry by the Windows port driver, MPIO, or the Disk class driver and avoid 
  potential data corruption on Write.  Problem limited to some multi-initiator 
  RBOD configurations.


5.0 Additional Information
==========================

The Driver version may be displayed in a different manner depending on the 
application because the leading zeros are often trimmed and not shown. 
(i.e.: 1.24.04.00 may be displayed as 1.24.4.0).


6.0 Known Issues
================

None.