1. PERC2-W2K3-6.35-A02.exe Driver
2. Readme.txt File Contents

Readme.txt Driver File Contents (PERC2-W2K3-6.35-A02.exe)

Title:

Dell PowerEdge RAID Controller 2/SC, 2/DC, 4/DC, 4/SC, 3/QC, 3/DC, 3/DCL, 3/SC, 
PERC 4/Di, and CERC ATA100/4CH, Device Driver for Windows 2003.

Version 6.35.2.32

Date: 6/05/03



TABLE OF CONTENTS

1.0 Introduction

2.0 Compatibility / Minimum Requirements

3.0 Fixes or Enhancements in this Release

4.0 Additional Information

5.0 Revision History


1.0   Introduction

This is the driver for following PowerEdge Expandable RAID Controllers:
 PERC 4/SC,   
 PERC 4/DC,
 PERC 3/QC,
 PERC 3/DC,
 PERC 3/DCL,
 PERC 3/SC, 
 PERC 2/SC,
 PERC 2/DC,
 PERC 4/Di,
 CERC ATA100/4CH.


2.0 Compatibility / Minimum Requirements

This Device Driver is compatible with the following firmware versions:

PERC 4/DC			(PERC 4 Dual Channel) 		3.28,
PERC 4/SC 			(PERC 4 Single Channel)		3.28,
PERC 3/QC			(PERC 3 Quad Channel) 		1.92,
PERC 3/DC			(PERC 3 Dual Channel) 		1.92,
PERC 3/DCL			(PERC 3 Dual Channel Lite) 	1.92,
PERC 3/SC			(PERC 3 Single Channel) 	1.92,
PERC 4/Di			(PERC 4/Di - PE 2600)		2.37,
PERC 4/Di			(PERC 4/Di - PE 1750)		4.10,
CERC ATA100/4CH	 	(RAID IDE) 				6.62,
PERC 2/SC			(PERC 2 Single Channel) 	3.13,			
PERC 2/DC			(PERC 2 Dual Channel) 		1.06.			


This package is a self-extracting package of the Windows 2003 device driver 
installation diskette for PERC 4/DC, 4/SC, 3/QC, 3/DC, 3/DCL, 3/SC, 2/DC, 2/SC, 
CERC ATA100/4CH and PERC 4/Di. 

XXXX.EXE	Self-extracting package to create Windows 2003 device driver 
installation diskette

To build the installation diskette, execute the package, directing it's output 
to an empty formatted diskette.



3.0 Fixes or Enhancements in this Release 

Enhancements:
1) None

Fixes:
1) Minor change to Oemsetup.txt file.

2) Driver no longer filters out all other commands except SCSI READ and SCSI 
WRITE


4.0 Additional Information

1. When installing a PERC 3/DCL controlller in a system, Windows will 
automatically load a different PERC driver. This driver will show the PERC 3/DCL 
as a PERC 3/DC. You must upgrade the driver to the latest shipping level and 
after this upgrade the PERC 3/DCL will be displayed correctly. 

2. When installing Windows Server 2003 in a system and have a PERC 3/QC, PERC 
3/DC, PERC 3/DCL, PERC 3/SC, PERC 4/DC or PERC 4/SC together in a system you 
will see the following selection when choosing a logical drive to configure.

		(xxxxx)mb Disk 0 at Id <y> on bus <z> on mraid35x [MBR]
		
		Where (xxxxx) is the size of the logical  drive.
		Where (y) is the logical drive id per controller.
 		Where (z) is the bus number.
			z=2	PERC 3/SC or PERC 4/SC
			z=3	PERC 3/DC,PERC 3/DCL or PERC 4/DC
			z=5	PERC 3/QC

If there is more than 1 logical drive per controller then ld number will be 
incremented. 

If there is more than 1 type of controller in a system then multiple selections 
will be displayed per controller.

 		(xxxxx)mb Disk 0 at Id (y) on bus (z) on mraid35x [MBR]

		(xxxxx)mb Disk 0 at Id (y) on bus (z) on mraid35x [MBR]

The user must be careful to select the appropriate ld when installing Windows 
Server 2003. 

		


5.0 Revision History 

Changes from 6.25 to 6.32.2.32

 
1)  Changes in the setup files, so that Scsiport driver should give the correct 
device number and function number to the miniport driver.

2)  A timeout is implemented in the driver so that driver shouldn't wait 
infinitely for the firmware to acknowledge the interrupt.

3)  The driver will return an error status for all the offline logical drives.

4)  Utilities are issuing 0xc3 calls for getting the logical drive statistics. 
This is causing the system to crash. This bug has been fixed in the driver.

5)  The driver is using Hal functions to program hierarchy bridges and SCSI 
chips when system goes to D3 standby state.  

The use of Hal functions were not allowing the driver to pass the HCT 
test. So we have to disable the Hal calls in the previous releases. A workaround 
has been done in the driver whereby all the Hal calls have been replaced by its 
assembly equivalent.

6)  During reset, the driver was not clearing all the pending commands whenever 
the firmware is not able to complete it.

7)  Driver is allocating enough continuous memory for the 
FLASH_WRITE_BLOCK(0x2c) command.

8)  The system gives a blue screen when one swaps the boot controller. This bug 
has been fixed by adding entries of all the supported controllers in the 
critical data base section of the registry through changes in the oemsetup.inf 
file.

9)  The system was not waking up after a hibernation/standby operation. This bug 
was caused by the driver. The driver was trying to access PCI_CONFIG space from 
the ScsiRestartAdapter in the driver. This bug has been fixed by accessing the 
PCI_CONFIG space from the ScsiSetRunningConfig entry point.

10) A new command has been introduced to enhance the performance for SCSI I/O on 
non-raid SCSI channel.

11) In case of standby, the driver was not waiting for the firmware to get 
initialized. This resulted in the driver sending commands to the firmware even 
when the firmware is not initialized. The fix has been put in the driver. The 
driver is polling for the Firmware to get initialized before sending any 
commands to the firmware.

12) The PERC 3 Firmware was not able to handle multiple reserve commands for a 
logical drive. This was leading to reservation failures on some of the logical 
drives. A fix has been done in the driver where the driver would accept only one 
reservation call at a time and would allow it to complete before issuing any 
more commands to the firmware.