Txtsetup.sif, 2003, and a PERC 5 D/I

[sled]

All,

I have trying to integrate the drivers for a PERC 5/I into my unattended installation, specifically using the txtsetup.sif and dosnet.inf files. I do not want to use the [MassStorageDrivers] method, because I want to use this installation on many different kinds of hardware. Here are the changes I added to the end of the txtsetup.sif file (without the dashes of course):

--------------

[sCSI]

PERC_32 = "DELL PERC5 and PERC6/CERC6 RAID Controller Driver (Server 2003 32 bit)",percsas

[sCSI.Load]

PERC_32 = percsas.sys, 4

[sourceDisksFiles]

percsas.sys = 1,,,,,,3_,4,1

[HardwareIDsDatabase]

PCI\VEN_1028&DEV_0015&SUBSYS_1F011028 = "PERC_32"

PCI\VEN_1028&DEV_0015&SUBSYS_1F021028 = "PERC_32"

PCI\VEN_1028&DEV_0015&SUBSYS_1F031028 = "PERC_32"

PCI\VEN_1000&DEV_0060&SUBSYS_1F0A1028 = "PERC_32"

PCI\VEN_1000&DEV_0060&SUBSYS_1F0B1028 = "PERC_32"

PCI\VEN_1000&DEV_0060&SUBSYS_1F0C1028 = "PERC_32"

PCI\VEN_1000&DEV_0060&SUBSYS_1F0D1028 = "PERC_32"

PCI\VEN_1000&DEV_0060&SUBSYS_1F111028 = "PERC_32"

--------------

And to the dosnet.inf:

--------------

[Files]

d1,percsas.sys

[FloppyFiles.2]

d1,percsas.sys

---------------

Finally I compressed the Percsas.sys file to PERCSAS.SY_ using makecab and copied it to the i386 folder of the installation point. No errors are given, but the machine blue screens after the first text mode reboot. To ensure the driver was good, I ran a clean install, pushed F6 at the proper time and fed the diskette. No problems. I plan to use this automated install on many 2950 servers in the future. If anyone else has encountered and hopefully overcame such an issue, please help.

Thanks,

Sled

[InTheWayBoy]

Whenever I integrate SATA/SCSI drivers I edit txtsetup.inf and hivesft.inf. I found this process by checking out Dell's XP installs that had the Intel SATA drivers installed and it works with 2K3 too.

I copy the driver files to the I386 folder uncompressed.

Then I edit hivesft.inf:

Replace

HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SystemRoot%\inf"

With

HKLM,"SOFTWARE\Microsoft\Windows\CurrentVersion","DevicePath",0x00020002,"%SystemRoot%\inf;%SystemRoot%\SATA"

%SystemRoot%\SATA is the folder that will eventually contain the SATA drivers...looks like it just adds another source for looking for drivers, but honestly I don't know really what good it's for.

The I edit txtsetup.inf:

[WinntDirectories]

304 = SATA

[sourceDisksFiles]

PERCSAS.SYS = 1,,,,,,4_,4,1,,,1,4

PERCSAS.SYS = 1,,,,,,,304,0,0

NODEV.INF = 1,,,,,,,304,0,0

OEMSETUP.INF = 1,,,,,,,304,0,0

PERCSAS.CAT = 1,,,,,,,304,0,0

[HardwareIdsDatabase]

PCI\VEN_1028&DEV_0015&SUBSYS_1F011028 = "percsas"

PCI\VEN_1028&DEV_0015&SUBSYS_1F021028 = "percsas"

PCI\VEN_1028&DEV_0015&SUBSYS_1F031028 = "percsas"

[sCSI.Load]

percsas = PERCSAS.SYS,4

[sCSI]

percsas = "PERC 5i RAID"

Those are all added, nothing has to be changed in the file.

And that's pretty much it, don't need to mess with your unattended file or anything. I got the HardwareIdsDatabase info from the driver's INF files. Here is what the Intel SATA drivers look like:

[WinntDirectories]

304 = SATA

[sourceDisksFiles]

IASTOR.SYS = 1,,,,,,4_,4,1,,,1,4

IASTOR.SYS = 1,,,,,,,304,0,0

IASTOR.INF = 1,,,,,,,304,0,0

IASTOR.CAT = 1,,,,,,,304,0,0

IASTOR.CAT = 1,,,,,,,304,0,0

IASTOR.INF = 1,,,,,,,304,0,0

[HardwareIdsDatabase]

PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor"

PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor"

PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor"

[sCSI.Load]

iastor = IASTOR.SYS,4

[sCSI]

iastor = "Intel Matrix Storage Manager"

I recall seeing issues like what you said before I came to this process, I wonder if it has to do with compressing the driver? BTW, this worked on my 2900.