<?xml version="1.0" encoding="UTF-16" ?>
	<SoftwareComponent  releaseID="R71755" releaseDate="February 23, 2004" vendorVersion="3.41" dellVersion="A04" packageType="LWXP" xmlGenVersion ="1.1.1">
		<Name>
			<Display lang="en" >
				<![CDATA[LSI Logic PERC 4/SC, PERC 4/DC, v.3.41, A04]]>
			</Display>
		</Name>
		<ComponentType value="FRMW">
			<Display lang="en" >
				<![CDATA[Firmware]]>
			</Display>
		</ComponentType>
		<Description>
			<Display lang="en" >
				<![CDATA[Dell PowerEdge Expandable RAID Controller 4/DC and 4/SC Firmware Update 

Version: 3.41]]>
			</Display>
		</Description>
		<LUCategory value="PERC">
			<Display lang="en" >
				<![CDATA[Disk Controller]]>
			</Display>
		</LUCategory>
		<Category value="SR">
			<Display lang="en" >
				<![CDATA[SCSI Raid]]>
			</Display>
		</Category>
		<SupportedDevices>
			<Device componentID="3428" embedded="0">
				<PCIInfo deviceID="1960" vendorID="1000" subDeviceID="0520" subVendorID="1028"/>
				<Display lang="en" >
					<![CDATA[PERC 4/SC]]>
				</Display>
			</Device>
			<Device componentID="3429" embedded="0">
				<PCIInfo deviceID="1960" vendorID="1000" subDeviceID="0518" subVendorID="1028"/>
				<Display lang="en" >
					<![CDATA[PERC 4/DC]]>
				</Display>
			</Device>
		</SupportedDevices>
		<SupportedOperatingSystems>
			<OperatingSystem osCode="WNET" osVendor="Microsoft" majorVersion="5" minorVersion="2" spMajorVersion="0" spMinorVersion="0">
				<Display lang="en" >
					<![CDATA[Windows Server 2003]]>
				</Display>
			</OperatingSystem>
			<OperatingSystem osCode="WNT5" osVendor="Microsoft" majorVersion="5" minorVersion="0" spMajorVersion="1" spMinorVersion="0">
				<Display lang="en" >
					<![CDATA[Windows 2000 SP1+]]>
				</Display>
			</OperatingSystem>
		</SupportedOperatingSystems>
				<InstallInstruction fileName="perc4-dc-sc-341-a04.exe" typeCode="WP  ">			<Display lang="en" >
				<![CDATA[Custom Instructions for perc4-dc-sc-341-a04.exe: 

This program creates a bootable diskette to upgrade the firmware of the 
controllers. You will need a formatted 3 1/2 inch floppy diskette for the 
following procedure.

1) Download the file to a directory on your hard drive. The file downloaded is a 
self extracting executable.
2) Insert a blank diskette into the system's diskette drive.
3) Double click on the file that you downloaded and follow the instructions on 
the screen to extract the files to the diskette.
4) Insert the diskette into the system with the RAID controller for which you 
want to update the firmware and reboot the system.
5) Follow the instructions on the screen to update the firmware.

NOTICE: pflash.exe will be executed automatically and will report existing code 
level and prompt you to reconfirm before starting the firmware upgrade 
process.

To perform this process in non-interactive mode please execute,
pflash /?
and read about possible command line switches.

6) Remove the diskette and reboot the system.

<HR COLOR=blue>]]>
			</Display>
		</InstallInstruction>
				<InstallInstruction fileName="perc4-dc-sc-341-a04.txt" typeCode="RC  ">			<Display lang="en" >
				<![CDATA[Custom Instructions for perc4-dc-sc-341-a04.txt:

Please see read me file.
<HR COLOR=blue>]]>
			</Display>
		</InstallInstruction>
				<InstallInstruction fileName="perc4-dc-sc-341-a04.tar.gz" typeCode="TAR ">			<Display lang="en" >
				<![CDATA[Custom Instructions for perc4-dc-sc-341-a04.tar.gz: 

To install, enter the following on the command line:

  rpm -Uvh linflash-3.01-0.i386.rpm

You must copy the firmware image to the same directory for the linux 
flash utility to work. Create a diskette image of the firmware and copy 
the .rom file to the same directory as linflash.

Usage : linflash [-r] [-p] [-s] [-i [file] [file] [...]] [-f [file] 
        [file] [...]]

-r : Flash without asking for user input to flash adapter(s).
-p : Prompt user for filename. Flash without checking for signatures.
-s : Silent flash. First matching image file will be taken for each 
     adapter.
-i : Ignore the following files. These files will not be considered for
     flashing the matching controllers.
-f : Force the following files To be flashed for the matching controller.
     In case more than one matching files are specified, the first one 
     would be taken.

To uninstall the rpm, enter the following command:

  rpm -e linflash

<HR COLOR=blue>]]>
			</Display>
		</InstallInstruction>
		<RevisionHistory>
			<Display lang="en" >
				<![CDATA[Current Firmware - 3.41
(Previous - 3.28)

Current BIOS - 1.06
(Previous - 1.05)

Current Ctrl-M - U812
(Previous - 5.62)

Current BootBlock - 1.7.1Dell
(Previous - 1.6.7Dell)

Current MPT SCSI firmware - 01.03.11.05-IT
(Previous - 01.03.06.00-IT)


Firmware Enhancements 

1. Improved I/O performance. 

2. Improved hard drive status logic when virtual disks are spanned across channels.

3. Firmware will automatically change cache settings to WriteThru when a battery 
problem is detected to preserve data.  If WriteBack was originally selected, 
firmware will switch back once battery problem has been corrected.

4. In the Rebuild function of CRTL-M, a new status called “INCON” will be displayed 
after a rebuild operation completes if any unrecoverable errors are found in any 
of the hard disk drives. To identify the location of the error and if any data was 
present, run a check disk from the O/S (e.g. chkdsk in windows). 

Note: Dell recommends that a check disk or consistency check should be run after 
any RAID rebuild operation is completed by the controller. 


Firmware Bug Fixes

1. When multiple hard drive media errors are encountered, array rebuild operation 
will complete.

2. Consistency checks are aborted after reboot in cluster or stand alone mode.  
User must restart consistency check manually if needed.  

3. Manual initialization calls will be rejected if a background initialization or 
consistency check is in progress on the logical drive.

4. Address potential controller lock-ups that could occur during either degraded, 
rebuilding or multiple drive pull and reinsert scenarios.

5. Addressed potential controller freezing during driver failure on possible 
Raid configurations.not zero, then we make size as zero and log it.]]>
			</Display>
		</RevisionHistory>
		<ImportantInfo>
			<Display lang="en" >
				<![CDATA[]]>
			</Display>
		</ImportantInfo>
</SoftwareComponent>
