Contents: ========= Dell PowerEdge RAID Controller 3/QC, 3/DC, 3/DCL, 3/SC, 4/DI, and CERC ATA100/4CH Device Driver for Windows 2000 Version 5.35.2 Compatibility: ============== 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.62 CERC IDE RAID 4 Channel 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, PERC 4/DI and 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)Driver is allocating enough continuous memory for the FLASH_WRITE_BLOCK(0x2c) command. 2) 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 criticalDataBase section of the registry through changes in the oemsetup.inf file. 3) 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. 4) New commmand has been introduced to enhance the performance for SCSI I/O on non-raid SCSI channel. 5) 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. 6) 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. 7) 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. This problem is fixed in the Driver.Download Driver Pack
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.