RIS: How to use OEM mass-storage drivers?

[Marksham]

This is a follow-up question to a posting with the same subject as
above from Jul 25th 2004.

I am faced with the same problem. Specifically:
W2K RIS Server
XP client with SCSI disk.

I have been able to push the OS image up to RIS, but now cannot pull it
back down. F6 is no longer available in XP and all Microsofts articles
point to adding PNP drivers to RIS; Mass storage drivers to unattended
set-ups (as distinct from RIS);etc.... but nothing specifically on
Adding XP Mass-storage drivers to RIS images

The article from July 25th has a deadlink pointing to
http://www.wug-nordic.net/articles/ris-add-storage.htm
This is no longer active.

Please Please can someone give me the content of this link, it appears
to have cured everyones ills but I cannot find it

From what I've read, part of the process involves the modification the

textsetup.sif file adding four specific sections like this example:

BEGIN EXAMPLE
[SourceDisksFiles]
viasraid.sys = 1,,,,,,_x,4,1


[HardwareIdsDatabase]
PCI\VEN_1106&DEV_3149 = "viasraid"


[SCSI.Load]
viasraid = viasraid.sys,4


[SCSI]
viasraid = "VIA Serial ATA RAID Controller"

END EXAMPLE

My problem is I have no idea how to compile this information for my
particular SCSI driver (Adaptec U320). This I put down to my own
stupidity, so can someone please put me out of my misery.

Somewhere out there there's got to be a definitive, step-by-step guide
to Adding Mass Storage drivers to RIS images.

Hope someone can help.

Mark

 

[Marksham]

I managed to figure this out with some help from a site at MIT.
http://web.mit.edu/ist/topics/windows/server/winmitedu/whatsRIS.htm
My sincere thanks to the author(s)

Here's my set-up:
W2K Server running RIS
Windows XP image created and uploaded to RIS on a Dell Precision 380
with an Adaptec U320 SCSI controller managing a single SCSI disk.

"ImageName" is the RIS folder I copied the XP image from the Dell
Precision workstation into.
"BaseImage" is the initial folder created by RIS during RISETUP that is
created using the standard WinXP CD

1). In the \BaseImage folder, at the same level as the i386 folder,
create the following folder structure:

\$OEM$\$1\Drivers\SCSI\
\$OEM$\TEXTMODE

2). Copy the SCSI driver files into the Textmode folder.

3). Copy the SCSI driver files to \$OEM$\1\Drivers\SCSI

4). In the \ImageName folder, at the same level as the i386 folder,
create the following folder structure:

\$OEM$\$1\Drivers\SCSI\
\$OEM$\TEXTMODE

5). Copy the SCSI driver files into the Textmode folder.

6). Copy the SCSI driver files to \$OEM$\1\Drivers\SCSI

7). In the beginning of the riprep.sif file stored in the
ImageName\i386\Templates, add a new section that reads like this

[OEMBootFiles]
oemsetup.inf
driver.sys [substitute the name of the driver]
txtsetup.oem

NOTE: oemsetup.inf & txtsetup.oem should be files you copied in steps 1
through 6 above. You'll just need to change "driver.sys" to reflect the
..sys file that applies to the specific driver you're working on. This
was the case for my driver but may vary for yours. Use the file
extensions as your guide.

8). Add a [MassStorageDrivers] section to the .sif file and determine
the device name from the txtsetup.oem. For example for the LSI Logic
Ultra 320 you will find this line:
SYMMPI = "LSI Logic PCI SCSI/FC MPI Miniport Driver",symmpi
The name you would use here will be "LSI Logic PCI SCSI/FC MPI Miniport
Driver"
So the syntax you will use in the sif file under [MassStorageDrivers]
will look like:

[MassStorageDrivers]
"LSI Logic PCI SCSI/FC MPI Miniport Driver" = "OEM"

9). In the [Unattended] section of the .sif file, make sure the
DriverSigningPolicy = Ignore entry exists; verify that the
OemPnpDriversPath includes \Drivers\SCSI; and verify that OemPreinstall
= Yes

10). Stop and restart the Boot Information Negotiation Layer (BINL)
service on the RIS server. This step is required for these changes to
take effect.

That should be it. I'm not sure why you need to copy the driver files
to the BaseImage and the ImageName folders but my solution wouldn't
work without them. I also think you can get away with just copying the
oemsetup.inf; driver.sys ; and txtsetup.oem files in steps 1 - 6 but I
just copied the entire driver set as I spent too long just trying to
get this thing to work, never mind tweaking it.

That's about it, I can't guarantee it'll work for you, but this is what
resolved this issue for me. If anyone can improve on this, please do,
others will benefit.

Now lets all give Microsoft a big hand for removing a nice handy way of
loading SCSI drivers during a RIS installation and replacing it with a
process with no documentation.

Longfort Abu