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.39
Important Information:
==============
This Device Driver is compatible with the following firmware versions:
Controller Minimum firmware level Description
---------- ---------------------- -----------
PERC 3/QC 1.74 PERC 3 Quad Channel
PERC 3/DC 1.74 PERC 3 Dual Channel
PERC 3/DCL 1.74 PERC 3 Dual Channel Lite
PERC 3/SC 1.74 PERC 3 Single Channel
PERC 4/DI 2.01 PERC 4/DI
CERC ATA100/4CH 6.62 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 and PERC 4/DI.
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.
Fixes or Enhancements From Prior releases
===================================
Changes from 5.35.2 to 5.39
======================
1. Utilities are issuing driver calls for getting the logical drive
statistics. We have seen some utilities are requesting 40LD
statistics but send buffer less than the required statistics size.
This is causing the system to crash. This bug has been fixed in the
driver by returning all the calls with lesser buffer size
without copying any data successfully.
2. Change in the setup files, so that Scsiport driver should give
correct Device Number and Function Number to the Miniport driver.
3. A timeout is implemented in the driver so that driver shouldn’t wait
infinitely for the Firmware to acknowledge the interrupt.
4. During Reset, Driver was not clearing all the Pending Commands
whenever the Firmware is not able to complete it.
5. System was hanging after it wakes up from Hibernation/Standby on
PERC 3/QC and PERC 3/DC controllers. Driver needs to reprogram these
SCSI chips before waiting for the firmware to initialize.
6. During the Cluster HCT phase 5 test the driver and firmware used
to wait for each other for a command completion. This led to dead
lock condition and the HCT test fails with an IO timeout error.
In order to avoid this dead lock condition the driver will poll the
firmware for completion of a command before the OS times out the
command.
7. When running heavy I/O's the miniport driver would often get a mailbox
busy condition that would lead to an I/O hang. The fix is made in
the driver to improve delay optimization for the mailbox busy
condition.
8. The logical drive status checking was failing for Dummy Device inquiry.
This logic was removed since there is no need to check status of this
device.
9. The capability pointer was changed in firmware for Fast READ/WRITE
calls for hard drives connected to the SCSI Channels.
10. Initial release of PERC 4/DI support on PE2755MC
========================================================================
Version 5.35.2 Release
Changes from 5.32 to 5.35.2
=======================
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 command 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 period of time for the outstanding
commands to complete. If the commands are not completed in certain period 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
up to 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.
=======================================================================
Version 5.32.0.0
Changes from 5.22.2 to 5.32
======================
1. During Logical drives creation/deletion through Open Manage Array Manager,
Open Manage 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 Power State. 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 achieve higher performance.
12. Initial release of PERC 4/DI on PE2600.
Changes from 5.29 to 5.32 - CERC ATA100/4ch
======================================
1) During Logical drives creation/deletion through Open Manage Array Manager , sometimes
Open Manage 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 CERC ATA100/4ch controller.
This problem was causing the driver to scan for the Qlogic chips during
boot up or during hibernation, which was resulting in the system hang.
This problem has been fixed by disabling scan of Qlogic chips for the CERC ATA100/4ch controller.
===================================================================
Version 5.22.2
Changes from 5.22.1 to 5.22.2
======================
1. In case of reset, driver was not able to complete all outstanding commands to OS, results in
lockup in system. This is fixed by purging all the outstanding commands with driver; so OS will retry
those commands and system will not lockup.
===================================================================
Version 5.22.1
Changes from 5.22. to 5.22.1
=======================
Modified oemsetup.inf and txtsetup.oem to add support for the PERC 3/SC.
Version 5.22 - Original release
=======================
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.