Release.TXT Driver File Contents (Perc3_W2K5352a.exe)

Dell PowerEdge RAID Controller 3/QC, 3/DC, 3/DCL, 3/SC, PERC 4/DI, and CERC ATA100/4CH, 
Device Driver for Windows 2000

Version 5.35.2

This Device Driver is compatible with the following firmware versions:

Controller		Minimum firmware level	Description
----------		----------------------	-----------
PERC 3/QC		1.72				PERC 3 Quad Channel
PERC 3/DC		1.72				PERC 3 Dual Channel
PERC 3/DCL		1.72				PERC 3 Dual Channel Lite
PERC 3/SC		1.72				PERC 3 Single Channel
PERC 4/DI		2.01				PERC 4/DI
CERC ATA100/4CH		6.6.2				RAID IDE	

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

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

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

Changes from 5.32

1) System was not waking up after a hibernation/standby operation. This bug was caused by the driver. 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.

2) New commmand has been introduced to enhance the performance for SCSI I/O on non-raid SCSI channel.

3) In case of cluster reset, Driver was waiting infinitely for all the commands to complete, resulting in the system crash/hang. This problem has been fixed by waiting for certain peroid of time for the outstanding commands to complete.If the commands are not completed in certain peroid of time, Driver completes all the outstanding with error and returns.

4) In case of Standby, driver was not waiting for the Firmware to get initialized, resulting in the driver sending commands to the firmware even when the Firmware is not initialized. The fix has been put in the driver. Driver is polling for the Firmware to get initialized before sending any commands to the Firmware.

5) A single Tape drive was seen at TargetID 0 and TargetID 16 on the physical channel.  One can attach upto a maximum of 15 devices on a single physical channel. All the requests coming for a physical channel with TargetID greater than 15 should be returned as Illegal request.

Changes from 5.29
1) During Logical drives creation/deletion through Marble, sometimes Marble used to hang as it keeps on waiting for the notification of the drive created/removed. This issue has been resolved in the driver by sending notification to the system Manager about the arrival/removal of a logical drive.

2) Bug fixed in the Read/Write path,in case of SCSI Channel, with PAE support enabled.

3)Miniport driver was scanning Qlogic Chips for 511 controller.
This problem was causing the driver to scan for the Qlogic chips during
bootup or during hibernation, which was resulting in the system hang.
This problem has been fixed by disabling scan of Qlogic chips for the 511 controller.

1) Raid on MotherBoard(ROMBI) support added to the driver.
2) 494/503 refernces has been removed from the inf file.

Changes from 5.22.2

1. During Logical drives creation/deletion through OpenManage Array Manager, 
   OpenManage Array Manager, used to hang as it keeps on waiting for the 
   notification of the drive created/removed. This issue has been resolved in 
   the driver by sending notification to the system manager about the 
   arrival/removal of a logical drives.

2. A bug fixed in the Read/Write path with PAE support enabled.

3. In case of a reset, the driver was not able to complete all outstanding commands
   to the OS, resulting in a lockup of the system. This is fixed by purging all the 
   outstanding commands with the driver. The OS will retry those commands  
   and system will not lockup

4. Ghost drive seen when installing Windows 2000 cluster environment. There was a   
   mismatch while calculating the logical drive number.

5. When the PERC Controller is being used as a secondary controller, the system hung   
   for the first time whenever it tries to load the driver. This has been 
   taken care by checking the Scsi chip PowerState. If the Scsi chip is in the D3  
   state, the driver will detect that the firmware is hung. In this condition, the
   system will not hang. The driver cannot expose any logical drive or any other device  
   connected to the controller during a firmware hang.

6. Support for Random Deletion of logical Drives.

7. Support for legacy functions has been added. The new driver will return success
   if it supports Random Delete operation. This has been done so that the driver
   does not hang if the Firmware does not support Random Delete.

8. Support for CERC ATA IDE controller added.

9. Implemented time outs during the driver initialization phase to detect a firmware   
   hang condition.

10. While read and write commands are merging, sometime this merged command was 
    exceeding the number of physical pages supported by the firmware. In this
    situation, the driver split these commands to fit the number of pages. 

11. Number of concurrent commands is increased to achive higher performance. 
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: 0.79