Unattend 3rd party raid drivers dell perc?

J

Julian

Hi
Having real problems getting a dell perc3 DI raid
controller to be seen by a partial unattended install.
I am creating a bootable CD with a Service pack 3
slipstreamed intall of windows 2000 and the unattend.txt
file copied to I386 etc.
It never picks up the files that should be copied across
and it can never see any storage device.
I have installed by pressing F6 at initial start inserted
the driver disk and sees the disk so the files are the
correct ones.
I've created the $OEM$ folder and Textmode folders and
copied the files from the driver disk to them as per
Q288344. I have tried with a \ and a . at the end of the
second line of txtsetup.oem none work.
The txtsetup.oem file is the one that came with th dell
driver disk.
Is there any reason this should not work from the TXTsetup
and Unatend.txt file below. I have done these on other
servers before though a while back and was working fine




TXTSETUP.OEM
------------

[Disks]
d1 = "Dell PERC 2, 2/Si, 3/Si, 3/Di Windows 2000 Device
Drivers", \Raidisk1,\

[Defaults]
scsi = perc2

[Scsi]
perc2 = "Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers",
perc2

[Files.Scsi.perc2]
driver = d1, perc2.sys, perc2
driver = d1, perc2hib.sys, perc2hib
catalog = d1, perc2.cat
inf = d1, perc2.inf
inf = d1, perc2mgt.inf
dll = d1, perc2cin.dll
dll = d1, perc2evt.exe

[Config.perc2]
value = "", Type, REG_DWORD, 1
value = "", Start, REG_DWORD, 0
value = "", Group, REG_SZ, "SCSI miniport"
value = "", ErrorControl, REG_DWORD, 1
value = Parameters\Device, NumberOfRequests, REG_DWORD, 0fe

[Config.perc2hib]
value = "", Type, REG_DWORD, 1
value = "", Start, REG_DWORD, 4
value = "", Group, REG_SZ, "SCSI miniport"
value = "", ErrorControl, REG_DWORD, 1

[HardwareIds.scsi.perc2]
id = "PCI\VEN_1011&DEV_0046&SUBSYS_13649005", "perc2"
id = "PCI\VEN_1011&DEV_0046&SUBSYS_13659005", "perc2"
id = "PCI\VEN_1028&DEV_0001&SUBSYS_00011028", "perc2"
id = "PCI\VEN_1028&DEV_0002&SUBSYS_00021028", "perc2"
id = "PCI\VEN_1028&DEV_0003&SUBSYS_00031028", "perc2"
id = "PCI\VEN_1028&DEV_0002&SUBSYS_00D11028", "perc2"
id = "PCI\VEN_1028&DEV_0002&SUBSYS_00D91028", "perc2"
id = "PCI\VEN_1028&DEV_000A&SUBSYS_01061028", "perc2"
id = "PCI\VEN_1028&DEV_000A&SUBSYS_011B1028", "perc2"
id = "PCI\VEN_1028&DEV_000A&SUBSYS_01211028", "perc2"
id = "PCI\VEN_9006&DEV_2140&SUBSYS_21409006", "perc2"
id = "PCI\VEN_9005&DEV_00C5&SUBSYS_00C51028", "perc2"




UNATTEND.TXT
--------------

;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=DefaultHide
OemPreinstall=Yes
TargetPath=\Windows

[MassStorageDrivers]
"Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers"="OEM"

[OEMBootFiles]
perc2.sys
perc2hib.sys
perc2.cat
perc2.inf
perc2mgt.inf
perc2cin.dll
perc2evt.exe
txtsetup.oem

[GuiUnattended]
OEMSkipRegional=1
TimeZone=85
 
P

Patrick J. LoPresti

I have done unattended installs of Windows 2000 Server on a Dell with
perc3 hardware, but they were network-based installs, not CD-based
installs. I would expect the principles to be similar, but I do not
know for sure.

Where are you putting the the $OEM$ folder? On a CD-ROM, $OEM$ goes
at the root of the CD; on a network, it goes under i386.

What error are you seeing, if any?

The "dll = ..." lines in txtsetup.oem will cause you trouble. See
<http://support.microsoft.com/?id=275334>. I followed these
instructions to create $OEM$\$$\OemDir and populate it, and it worked.

I am skeptical that "\Raidisk1" is what you want for a tag file in the
"Disks" section. See
<http://www.mail-archive.com/[email protected]/msg00107.html>
for what I did to get this stuff working on XP. I used a similar
txtsetup.oem worked for 2000, but as I said, that was a network-based
and not CD-based installation.

If you want to try a network-based install, which I can definitely
help get working, see <http://unattended.sourceforge.net/>.

- Pat

Julian said:
Hi
Having real problems getting a dell perc3 DI raid
controller to be seen by a partial unattended install.
I am creating a bootable CD with a Service pack 3
slipstreamed intall of windows 2000 and the unattend.txt
file copied to I386 etc.
It never picks up the files that should be copied across
and it can never see any storage device.
I have installed by pressing F6 at initial start inserted
the driver disk and sees the disk so the files are the
correct ones.
I've created the $OEM$ folder and Textmode folders and
copied the files from the driver disk to them as per
Q288344. I have tried with a \ and a . at the end of the
second line of txtsetup.oem none work.
The txtsetup.oem file is the one that came with th dell
driver disk.
Is there any reason this should not work from the TXTsetup
and Unatend.txt file below. I have done these on other
servers before though a while back and was working fine




TXTSETUP.OEM
------------

[Disks]
d1 = "Dell PERC 2, 2/Si, 3/Si, 3/Di Windows 2000 Device
Drivers", \Raidisk1,\

[Defaults]
scsi = perc2

[Scsi]
perc2 = "Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers",
perc2

[Files.Scsi.perc2]
driver = d1, perc2.sys, perc2
driver = d1, perc2hib.sys, perc2hib
catalog = d1, perc2.cat
inf = d1, perc2.inf
inf = d1, perc2mgt.inf
dll = d1, perc2cin.dll
dll = d1, perc2evt.exe

[Config.perc2]
value = "", Type, REG_DWORD, 1
value = "", Start, REG_DWORD, 0
value = "", Group, REG_SZ, "SCSI miniport"
value = "", ErrorControl, REG_DWORD, 1
value = Parameters\Device, NumberOfRequests, REG_DWORD, 0fe

[Config.perc2hib]
value = "", Type, REG_DWORD, 1
value = "", Start, REG_DWORD, 4
value = "", Group, REG_SZ, "SCSI miniport"
value = "", ErrorControl, REG_DWORD, 1

[HardwareIds.scsi.perc2]
id = "PCI\VEN_1011&DEV_0046&SUBSYS_13649005", "perc2"
id = "PCI\VEN_1011&DEV_0046&SUBSYS_13659005", "perc2"
id = "PCI\VEN_1028&DEV_0001&SUBSYS_00011028", "perc2"
id = "PCI\VEN_1028&DEV_0002&SUBSYS_00021028", "perc2"
id = "PCI\VEN_1028&DEV_0003&SUBSYS_00031028", "perc2"
id = "PCI\VEN_1028&DEV_0002&SUBSYS_00D11028", "perc2"
id = "PCI\VEN_1028&DEV_0002&SUBSYS_00D91028", "perc2"
id = "PCI\VEN_1028&DEV_000A&SUBSYS_01061028", "perc2"
id = "PCI\VEN_1028&DEV_000A&SUBSYS_011B1028", "perc2"
id = "PCI\VEN_1028&DEV_000A&SUBSYS_01211028", "perc2"
id = "PCI\VEN_9006&DEV_2140&SUBSYS_21409006", "perc2"
id = "PCI\VEN_9005&DEV_00C5&SUBSYS_00C51028", "perc2"




UNATTEND.TXT
--------------

;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=DefaultHide
OemPreinstall=Yes
TargetPath=\Windows

[MassStorageDrivers]
"Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers"="OEM"

[OEMBootFiles]
perc2.sys
perc2hib.sys
perc2.cat
perc2.inf
perc2mgt.inf
perc2cin.dll
perc2evt.exe
txtsetup.oem

[GuiUnattended]
OEMSkipRegional=1
TimeZone=85
Click to expand...
 
J

Julian

Thanks for that
Yes the $OEM$ was in the I386 directory and not the cd
root.
Also with a Boot CD i realised after reading a few web
links that you do not use a unattend.txt file but you
rename it to winnt.sif for the instalation to see it.
Hence why it was not even picking up the file / drivers
It was i while since i did one of these

I'll just go away and slap my self now

Cheers

other useful link that was on sourceforge was
http://www.willowhayes.co.uk/

-----Original Message-----
I have done unattended installs of Windows 2000 Server on a Dell with
perc3 hardware, but they were network-based installs, not CD-based
installs. I would expect the principles to be similar, but I do not
know for sure.

Where are you putting the the $OEM$ folder? On a CD-ROM, $OEM$ goes
at the root of the CD; on a network, it goes under i386.

What error are you seeing, if any?

The "dll = ..." lines in txtsetup.oem will cause you trouble. See
<http://support.microsoft.com/?id=275334>. I followed these
instructions to create $OEM$\$$\OemDir and populate it, and it worked.

I am skeptical that "\Raidisk1" is what you want for a tag file in the
"Disks" section. See
<http://www.mail-archive.com/unattended- (e-mail address removed)/msg00107.html>
for what I did to get this stuff working on XP. I used a similar
txtsetup.oem worked for 2000, but as I said, that was a network-based
and not CD-based installation.

If you want to try a network-based install, which I can definitely
help get working, see
Click to expand...
- Pat

Julian said:
Hi
Having real problems getting a dell perc3 DI raid
controller to be seen by a partial unattended install.
I am creating a bootable CD with a Service pack 3
slipstreamed intall of windows 2000 and the unattend.txt
file copied to I386 etc.
It never picks up the files that should be copied across
and it can never see any storage device.
I have installed by pressing F6 at initial start inserted
the driver disk and sees the disk so the files are the
correct ones.
I've created the $OEM$ folder and Textmode folders and
copied the files from the driver disk to them as per
Q288344. I have tried with a \ and a . at the end of the
second line of txtsetup.oem none work.
The txtsetup.oem file is the one that came with th dell
driver disk.
Is there any reason this should not work from the TXTsetup
and Unatend.txt file below. I have done these on other
servers before though a while back and was working fine




TXTSETUP.OEM
------------

[Disks]
d1 = "Dell PERC 2, 2/Si, 3/Si, 3/Di Windows 2000 Device
Drivers", \Raidisk1,\

[Defaults]
scsi = perc2

[Scsi]
perc2 = "Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers",
perc2

[Files.Scsi.perc2]
driver = d1, perc2.sys, perc2
driver = d1, perc2hib.sys, perc2hib
catalog = d1, perc2.cat
inf = d1, perc2.inf
inf = d1, perc2mgt.inf
dll = d1, perc2cin.dll
dll = d1, perc2evt.exe

[Config.perc2]
value = "", Type, REG_DWORD, 1
value = "", Start, REG_DWORD, 0
value = "", Group, REG_SZ, "SCSI miniport"
value = "", ErrorControl, REG_DWORD, 1
value = Parameters\Device, NumberOfRequests, REG_DWORD, 0fe

[Config.perc2hib]
value = "", Type, REG_DWORD, 1
value = "", Start, REG_DWORD, 4
value = "", Group, REG_SZ, "SCSI miniport"
value = "", ErrorControl, REG_DWORD, 1

[HardwareIds.scsi.perc2]
id = "PCI\VEN_1011&DEV_0046&SUBSYS_13649005", "perc2"
id = "PCI\VEN_1011&DEV_0046&SUBSYS_13659005", "perc2"
id = "PCI\VEN_1028&DEV_0001&SUBSYS_00011028", "perc2"
id = "PCI\VEN_1028&DEV_0002&SUBSYS_00021028", "perc2"
id = "PCI\VEN_1028&DEV_0003&SUBSYS_00031028", "perc2"
id = "PCI\VEN_1028&DEV_0002&SUBSYS_00D11028", "perc2"
id = "PCI\VEN_1028&DEV_0002&SUBSYS_00D91028", "perc2"
id = "PCI\VEN_1028&DEV_000A&SUBSYS_01061028", "perc2"
id = "PCI\VEN_1028&DEV_000A&SUBSYS_011B1028", "perc2"
id = "PCI\VEN_1028&DEV_000A&SUBSYS_01211028", "perc2"
id = "PCI\VEN_9006&DEV_2140&SUBSYS_21409006", "perc2"
id = "PCI\VEN_9005&DEV_00C5&SUBSYS_00C51028", "perc2"




UNATTEND.TXT
--------------

;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=DefaultHide
OemPreinstall=Yes
TargetPath=\Windows

[MassStorageDrivers]
"Dell PERC 2, 2/Si, 3/Si, 3/Di RAID Controllers"="OEM"

[OEMBootFiles]
perc2.sys
perc2hib.sys
perc2.cat
perc2.inf
perc2mgt.inf
perc2cin.dll
perc2evt.exe
txtsetup.oem

[GuiUnattended]
OEMSkipRegional=1
TimeZone=85
Click to expand...
.
Click to expand...
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads

TXTSetup.OEM to SysPrep.INF 0
Unattended Network Installation of Dell Poweredge 4600 with PERC 3/dc 1
Unattened install of Win2k Server with Perc 3d/c 2
Integrating SCSI Raid driver into unattended setup 1
How to add Third-Party SCSI Array controller drivers for Windows 2000 Server 1
Integrate Adatpec 29320-R SCSI int unattended setup fails 1
Installation a RipRep Image on a Dell Precision 370 2
Txtsetup.oem - Multiple OEM Mass Storage drivers (defaults section) 0

Top