Highpoint 1640 (HPT374) Driver Integration RIS

[Jon-G]

Hi All,

I am trying to configure a Windows 2003 Remote Installation Server to deploy our XP workstation Image. I’ve worked through most of the procedures I have found on this site to include the driver for the Highpoint 1640 RAID card that all our systems boot from into the Image but keep drawing a blank. There are currently 2 images on the RIS server and each one works fine when using a standard disk controller on the target system, however it makes a massive ball ache for me having to image each workstation, install the RAID card, then build the array so am looking for advice as to what I need to do to allow the text mode portion of the setup to see the hard disk when connected directly through the 1640 card.

I think my confusion lies with which files within which image I should be altering, as there is the XPSP2 ‘flat’ image ripped straight from the XP CD to the RIS server, then there is the XP workstation desktop imaged I have configured with all the relevant apps etc and imaged back to the RIS server.

I have created a $OEM$ at the same level as the I386 dir within the folder which holds this image. Within the $OEM$ folder I have created a Drivers folder, and this has one sub directory called NIC which has the drivers for the Marvell Yukon card I’m booting from.

I added another sub directory to the $OEM$\Driver directory called RAID and copied the following driver files to there:

Hpt374.sys

Hpt374.inf

Hpt374.cat

TXTSETUP.OEM

DISK1

I have edited the riprep.sif file found in the \\Server\reminst\Setup\English\Images\ImacXpSp2Rev103\i386\Templates folder to add the following:

[MassStorageDrivers]

"RocketRAID 154x/1640 Controller for WinXP/2003" = "OEM"

"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OEMBootFiles]

hpt374.inf

hpt374.cat

hpt374.sys

[unnatttended]

OemPnpDriversPath = "\Drivers\Nic;\Drivers\RAID"

DriverSigningPolicy = Ignore

OemPreinstall = yes

I stopped and restarted the binlsvc service and attempted install the image to a PXE boot enabled workstation. I get the error:

“File txtsetup.oem caused an unexpected error (21) at line 1747 in D:\xpsprtm\base\boot\setup\oemdisk.c”

If I choose to continue setup still cannot find the hard disk through the 1640 controlled.

Digging around on the net I found reference to someone saying you have to copy the driver files into the I386 folder.I tried this for the I386 folder in the ImacXpSp2Rev103 folder (Where I Riprepped the workstation to originally) but this had no efect. I then tried copying them to the I386 dir of the ‘flat’ image that I took from the XP cd (XPSP2OEM) still to no avail.

I found reference to someone saying the the changed made to the riprep.sif file had to be mirrored to the ristndrd.sif found in the \i386\templates of the ‘flat’ image file. I have tried this too.

The last thing I tried with all the above in place was editing the TXTSETUP.SIF file found in the

\\Server\reminst\Setup\English\Images\ImacXpSp2Rev103\i386\Mirror1\UserData\I386

To add the following content the relevant sections:

[sourceDisksFiles]

hpt374.sys = 1,,,,,,_3,4,1

[sCSI.Load]

hpt374=hpt374.sys,4

[sCSI]

hpt374 = "RocketRAID 154x/1640 Controller"

[HardwareIdsDatabase]

PCI\VEN_1103&DEV_0008 = "hpt374"

And still I get the txtsetup.oem error as before and if I OK the HDD cannot be seen through the 1640 Controller. Sure its me that is doing something wrong as this isnt rocket science.

Could someone please give me a gigantic slap in the right direction????

Cheers,

Jon.

[Jon-G]

Ok, so I played and played and just referenced everything in the ristnd and riprep.sif files duplicated the files all over and now the txtmode portion of the setup and see the card and access the connected disks. The problem Im faced with now is that setup tries to copy the hpt374 inf cat and sys files at the very end but gives a cannot copy file error. I have tried skipping the file copy, setup then reboots and will start into windows, however when I try and install the drivers for the Raid card that is hsowing up in Device Manger with a ? I get an access denied error.

The TXTSetup.oem and DISK1 files currently reside in the $OEM$\Driver\RAID folder and the sys,cat and inf files in the Win_XP sub directory. The content of the TXTSetup.oem file is as follows:

#

# TXTSETUP.OEM for RocketRAID 154x/1640 Controller

#

[Disks]

d1 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \

d2 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \win_nt

d3 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \win_2000

d4 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \win_xp

d5 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \AMD64

[Defaults]

scsi = hpt374XP

[scsi]

hpt374NT = "RocketRAID 154x/1640 Controller for WinNT 4.0", hpt374

hpt3742K = "RocketRAID 154x/1640 Controller for Win2000", hpt374

hpt374XP = "RocketRAID 154x/1640 Controller", hpt374

hpt374amd64 = "RocketRAID 154x/1640 Controller for Windows AMD64", hpt374

[Files.scsi.hpt374NT]

driver = d2, hpt374.sys, hpt374

inf = d2, hpt374.inf

[Files.scsi.hpt3742K]

driver = d3, hpt374.sys, hpt374

inf = d3, hpt374.inf

catalog= d3, hpt374.cat

[HardwareIds.scsi.hpt3742K]

id = "PCI\VEN_1103&DEV_0008","hpt374"

[Files.scsi.hpt374XP]

driver = d4, hpt374.sys, hpt374

inf = d4, hpt374.inf

catalog= d4, hpt374.cat

[HardwareIds.scsi.hpt374XP]

id = "PCI\VEN_1103&DEV_0008","hpt374"

[Files.scsi.hpt374amd64]

driver = d5, hpt374.sys, hpt37464

inf = d5, hpt374.inf

catalog= d5, hpt374.cat

[HardwareIds.scsi.hpt374amd64]

id = "PCI\VEN_1103&DEV_0008","hpt374"

[Config.hpt37464]

value = "", Tag, REG_DWORD, 1

value = "Parameters\PnpInterface", 5, REG_DWORD, 1

Any help would be greatly appreciated gys.

Jon

[jweather]

I know it's a bit late to be much use, but I thought I'd save other people the hassle if they come across this post... Textmode drivers must all be in the directory $oem$\textmode. Using subfolders under textmode is NOT supported -- the driver will load for textmode setup, but fail to be copied, as the parent poster indicated. Collapsing drivers to a single directory may require some editing of the [disks] section of txtsetup.oem (correct directory path should be "\", meaning $oem$\textmode.) Hope this helps...

[cluberti]

I was going to point you to the MS article on integrating Mass Storage drivers in unattended setup, but it looks like you figured it out.