Good news. I have figured it out.

old:

[MassStorageDrivers]
"SYMMPI_XP32" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

new:

[MassStorageDrivers]
"LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

I am experiencing the same issue.

Do you have a copy of the txtsetup.oem and ristndrd.sif file that you got to work, that you might be able to send me?

In your cd based image,

1.) On the same folder level as the i386 directory, Create a "$OEM$\Textmode\" path. This is for the textbased install. (Required)

2.) Place the SCSI drivers in the Textmode folder.(Required)

symmpi.sys
symmpi.inf
mpixp32.cat
txtsetup.oem

3.) Create "$OEM$\Drivers\P650\SCSI". This is for the GUI install (Required)

4.) Copy the drivers there as well. (Required)

5.) In your ristndrd.sif file, make these changes or additions

[Unattended]
OemPreinstall = Yes
OemPnpDriversPath = "\Drivers\P650\SCSI"

[MassStorageDrivers]
"LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OEMBootFiles]
symmpi.sys
symmpi.inf
mpixp32.cat
txtsetup.oem

6.) Restart the BINL Service on the server and load the image as you would regularly.

Note: The "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)"  line in the ristndrd.sif file MUST match the description on the

SYMMPI_XP32 = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)",symmpi

in the txtsetup.oem file. Otherwise this won't work. If you have issues, try also copying the listed files above into the i386 directory.

~Alex. 

Trial and error trying to figure this one out. There is no one resource that led me to this configuration.  Dell tech support didn't even know how to assist me in this issue. 

I used a combination of articles, the one that got me closest was Microsoft Article - 241827.

http://support.microsoft.com/default.aspx?scid=kb;en-us;241827

For the driver, I simply used the non-raid driver for the SCSI storage device. If using RAID hardware, you must use the files in that driver package.

Hope this helps.

~Alex V.

Do you have the URL for which LSI Logic driver (RAID or non-RAID) you used for this method?

I am not using a RIS server for this, but rather, using an unattended install and the WinXP CD.  I have the $OEM$ (& ..\Textmode) directories on a seperate CD and during the text setup portion of the XP install, I get the infamous error message:

"File txtsetup.oem caused an unexpected error (18) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c"

I have also tried putting these files in other locations (on the XP CD in an $OEM$ directory, etc., etc.). I only get the error message when things are in the right spots and the pathing is correct (otherwise I get "can't file txtseutp.oem").

Here are the pertinent lines from my winnt.sif file:

[Unattended]
OemFilesPath = "E:\$OEM$"
OEMPreinstall = Yes

[MassStorageDrivers]
"LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)" = "OEM"

[OEMBootFiles]
symmpi.sys
symmpi.inf
mpixp32.cat
txtsetup.oem

This is the same setup as you have. The KB article you posted the link to is close, but still doesn't "fix" my problem.

Any ideas? I'm at my wit's end on this one..

Thanks,
Michael

Found my answer (the hard way).

Basically, I had to edit the WinXP CD (will also work for Win2000). This is much the same as how you would edit the .\cmdcons directory for the recovery console (to get it to work w/o using a driver disk too).

References:

http://patrick.naoise.com/articles/windows/bootablecd/

http://www.jsiinc.com/subn/tip6500/rh6575.htm

http://groups.google.com/groups?threadm=OdrWK38%24DHA.2292%40TK2MSFTNGP12.phx.gbl

http://groups.google.com/groups?threadm=eGuzBoSBEHA.2800%40tk2msftngp13.phx.gbl

Michael

Hey

This is a really useful thread for me because we've got quite a few Precision 650 Workstations and I'd like to roll out XP in the same way as I do for other workstations that don't need the third party controller drivers.

I'm using the network boot to contact the RIS server (F12) but it seemed to be exhibiting the same error as a CD based installation when modifying the ristndrd.sif file for the LSI Logic XP32 bit drivers (you know the one - error at line 1742 on d:\xpclient\base\boot\setup\oemdisk.c ...)

Anyway, I included the symmpi.sys file into the i386 directory and edited the txtsetup.sif file to include the relevant bits from the txtsetup.oem file. This got me past the text setup stage - great - it finds the disk, formats it and copies all the relevant files. It reboots starts the Windows XP splash screen and blue screens on me a few seconds later with a stop error.

I've seen lots of threads about the text setup but nothing about a crash occurring during the GUI setup. Anybody else found something similar.

Thanks

Doug

Here is the file :

 

 

# txtsetup.oem - version XP32.5 for SYMMPI Windows drivers (Windows XP)
#
# ***********************************************************************
#                                                                       *
#   Copyright 2002 LSI Logic, Corp.  All rights reserved.               *
#                                                                       *
#   This file is property of LSI Logic, Corp. and is licensed for       *
#   use as is.  The receipt of or posession of this file does not       *
#   convey any rights to modify its contents, in whole, or in part,     *
#   without the specific written consent of LSI Logic, Corp.            *
#                                                                       *
# ***********************************************************************
#
# format for txtsetup.oem.
#
# General format:
#
# [section]
# key = value1,value2,...
#
#
# The hash ('#') introduces a comment.
# Strings with embedded spaces, commas, or hashes should be double-quoted
#

[Disks]

# This section lists all disks in the disk set.
#
# is a descriptive name for a disk, used when
#   prompting for the disk
# is a file whose presence allows setup to recognize
#   that the disk is inserted.
# is where the files are located on the disk.
#

d1 = "LSI Logic Ultra320 1020/1030 Driver (XP)", \symmpi.tag, \

[Defaults]

# This section lists the default selection for each 'required'
# hardware component.  If a line is not present for a component,
# the default defaults to the first item in the [ ]
# section (see below).
#
# is one of computer, display, keyboard, mouse, scsi
# is a unique string to be associated
#   with an option.

scsi = SYMMPI_XP32

[scsi]

# This section lists the options available for a particular component.
#
# is the unique string for the option
# is a text string, presented to the user in a menu
# gives the name of the key to be created for the component in
#   HKEY_LOCAL_MACHINE\ControlSet001\Services

SYMMPI_XP32 = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)",symmpi

[HardwareIds.scsi.SYMMPI_XP32]

id = "PCI\VEN_1000&DEV_0621", "symmpi"
id = "PCI\VEN_1000&DEV_0622", "symmpi"
id = "PCI\VEN_1000&DEV_0624", "symmpi"
id = "PCI\VEN_1000&DEV_0626", "symmpi"
id = "PCI\VEN_1000&DEV_0628", "symmpi"
id = "PCI\VEN_1000&DEV_0030", "symmpi"

# This section lists the files that should be copied if the user
# selects a particular component option.
#
# is one of driver, port, class, dll, hal, inf, or detect.
#   See below.
# identifies where the file is to be copied from, and must
#   match en entry in the [Disks] section.
# is the name of the file. This will be appended to the
#   directory specified for the disk in the [Disks] section to form the
#   full path of the file on the disk.

[Files.scsi.SYMMPI_XP32]
driver = d1,symmpi.sys,SYMMPI
inf    = d1,symmpi.inf
catalog = d1,mpixp32.cat

[Config.SYMMPI]

# This section specifies values to be set in the registry for
# particular component options.  Required values in the services\xxx
# key are created automatically -- use this section to specify additional
# keys to be created in services\xxx and values in services\xxx and
# services\xxx\yyy.
#
# is relative to the services node for this device.
#   If it is empty, then it refers to the services node.
#   If specified, the key is created first.
# specifies the value to be set within the key
# is a string like REG_DWORD.  See below.
# specifies the actual value; its format depends on
value = Parameters\PnpInterface,5,REG_DWORD,1

Are you including the drivers for the GUI based installation? Text based and GUI based are 2 different setups.

For the Gui based, you want the drivers in the $OEM$/$1/Drivers/NIC path and then edit the SIF template to reflect this path.

[Unattended]
UnattendedMode = ProvideDefault
OemPreinstall = Yes
OemPnpDriversPath = "\Drivers\Nic"
DriverSigningPolicy = Ignore