PC Review Forums Newsgroups Windows 2000 Microsoft Windows 2000 Deployment Need help with Unattended Setup Dell Precision 350

Reply

Need help with Unattended Setup Dell Precision 350

 
Thread Tools Rate Thread
Old 10-07-2003, 06:12 PM   #1
El Duderino
Guest
 
Posts: n/a
Default Need help with Unattended Setup Dell Precision 350



Hi!

I´m trying to create an unattended setup for Windows 2000 on a Dell
Precision 350 Workstation. However, I have massive problems integrating the
SCSI driver for "LSI Logic 1020/1030" adapters.

Here´s what I´ve done up to now:

- copied the i386 files to the local hard drive (under DOS, first created
partition/formatted, then copied i386 to C
- created the Unattended.txt file.
- copied the driver files for W2k to i386\$OEM$\Textmode
- edited the txtsetup.oem file so it points to the current folder. (removed
sub folders)

I start setup using winnt.exe /s:c:\i386 /unattend:C:\unattend.txt

Setup runs until after the first reboot. After "Windows 2000 is starting"
the PC locks up with a BSOD STOP error. (07B) - this basically means that
for some reason the driver was not found. (according to MS KB)

I´ve tried this procedure with another adapter/driver on another machine and
it works. So I don´t understand what I´ve done wrong with this one.

Here´s the unattended file (only the sections that count here..)

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

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
TargetPath=\WINNT
Repartition = Yes
KeyboardLayout = "German"
; OemPnPDriversPath = "lsi\scsi"
DriverSigningPolicy = Ignore
; UseWholeDisk = Yes

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

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



And here´s the txtsetup.oem file I´ve modified to fit the paths:



#
# 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.
#
# <description> is a descriptive name for a disk, used when
# prompting for the disk
# <tagfile> is a file whose presence allows setup to recognize
# that the disk is inserted.
# <directory> is where the files are located on the disk.
#

d1 = "LSI Logic Ultra320 1020/1030 Driver",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 [<component_name>]
# section (see below).
#
# <component_name> is one of computer, display, keyboard, mouse, scsi
# <id> is a unique <within the component> string to be associated
# with an option.

scsi = SYMMPI_2k



[scsi]

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

SYMMPI_NT = "LSI Logic Ultra320 1020/1030 Driver (Windows NT)",symmpi
SYMMPI_2K = "LSI Logic Ultra320 1020/1030 Driver (Windows 2000)",symmpi
SYMMPI_XP32 = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)",symmpi



[HardwareIds.scsi.SYMMPI_2K]

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"

[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.
#
# <file_type> is one of driver, port, class, dll, hal, inf, or detect.
# See below.
# <source_disk> identifies where the file is to be copied from, and must
# match en entry in the [Disks] section.
# <filename> 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_NT]
driver = d1,symmpi.sys,SYMMPI
inf = d1,symmpi.inf
[Files.scsi.SYMMPI_2K]
driver = d2,symmpi.sys,SYMMPI
inf = d2,symmpi.inf
catalog = d2,symmpi2k.cat
[Files.scsi.SYMMPI_XP32]
driver = d3,symmpi.sys,SYMMPI
inf = d3,symmpi.inf
catalog = d3,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.
#
# <key_name> 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.
# <value_name> specifies the value to be set within the key
# <value_type> is a string like REG_DWORD. See below.
# <value> specifies the actual value; its format depends on <value_type>
value = Parameters,dummy,REG_DWORD,0
value = Parameters\PnpInterface,5,REG_DWORD,1



Anyone have a clue why Windows doesn´t find the driver?

Thanks for any input!

Jack


  Reply With Quote
Old 10-07-2003, 08:54 PM   #2
Patrick J. LoPresti
Guest
 
Posts: n/a
Default Re: Need help with Unattended Setup Dell Precision 350

What you describe should work. Perhaps there is something wrong with
your TXTSETUP.OEM file; send it along if you want someone to look at
it.

I cannot help but mention that my installation system automatically
scans $OEM$\TEXTMODE, parses TXTSETUP.OEM, and generates the
appropriate unattend.txt file automatically. If you would like to
give it a try, see <http://unattended.sourceforge.net/>.

You also might find my rant helpful, even though it mostly applies to
Windows XP:

http://www.mail-archive.com/unatten...t/msg00107.html

In particular, you might look around under $WINNT$.~BT and $WINNT$.~LS
after the failed installation to make sure the driver files and
txtsetup.oem file got copied properly.

- Pat


"El Duderino" <nomail@please.com> writes:

> Hi!
>
> I´m trying to create an unattended setup for Windows 2000 on a Dell
> Precision 350 Workstation. However, I have massive problems integrating the
> SCSI driver for "LSI Logic 1020/1030" adapters.
>
> Here´s what I´ve done up to now:
>
> - copied the i386 files to the local hard drive (under DOS, first created
> partition/formatted, then copied i386 to C
> - created the Unattended.txt file.
> - copied the driver files for W2k to i386\$OEM$\Textmode
> - edited the txtsetup.oem file so it points to the current folder. (removed
> sub folders)
>
> I start setup using winnt.exe /s:c:\i386 /unattend:C:\unattend.txt
>
> Setup runs until after the first reboot. After "Windows 2000 is starting"
> the PC locks up with a BSOD STOP error. (07B) - this basically means that
> for some reason the driver was not found. (according to MS KB)
>
> I´ve tried this procedure with another adapter/driver on another machine and
> it works. So I don´t understand what I´ve done wrong with this one.
>
> Here´s the unattended file (only the sections that count here..)
>
> ;SetupMgrTag
> [Data]
> AutoPartition=1
> MsDosInitiated="0"
> UnattendedInstall="Yes"
>
> [Unattended]
> UnattendMode=FullUnattended
> OemSkipEula=Yes
> OemPreinstall=Yes
> TargetPath=\WINNT
> Repartition = Yes
> KeyboardLayout = "German"
> ; OemPnPDriversPath = "lsi\scsi"
> DriverSigningPolicy = Ignore
> ; UseWholeDisk = Yes
>
> [MassStorageDrivers]
> "LSI Logic Ultra320 1020/1030 Driver (Windows 2000)" = "OEM"
> "IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
>
> [OEMBootFiles]
> symmpi.sys
> symmpi2k.cat
> symmpi.inf
> txtsetup.oem
>
>
>
> And here´s the txtsetup.oem file I´ve modified to fit the paths:
>
>
>
> #
> # 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.
> #
> # <description> is a descriptive name for a disk, used when
> # prompting for the disk
> # <tagfile> is a file whose presence allows setup to recognize
> # that the disk is inserted.
> # <directory> is where the files are located on the disk.
> #
>
> d1 = "LSI Logic Ultra320 1020/1030 Driver",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 [<component_name>]
> # section (see below).
> #
> # <component_name> is one of computer, display, keyboard, mouse, scsi
> # <id> is a unique <within the component> string to be associated
> # with an option.
>
> scsi = SYMMPI_2k
>
>
>
> [scsi]
>
> # This section lists the options available for a particular component.
> #
> # <id> is the unique string for the option
> # <description> is a text string, presented to the user in a menu
> # <key_name> gives the name of the key to be created for the component in
> # HKEY_LOCAL_MACHINE\ControlSet001\Services
>
> SYMMPI_NT = "LSI Logic Ultra320 1020/1030 Driver (Windows NT)",symmpi
> SYMMPI_2K = "LSI Logic Ultra320 1020/1030 Driver (Windows 2000)",symmpi
> SYMMPI_XP32 = "LSI Logic Ultra320 1020/1030 Driver (XP 32-bit)",symmpi
>
>
>
> [HardwareIds.scsi.SYMMPI_2K]
>
> 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"
>
> [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.
> #
> # <file_type> is one of driver, port, class, dll, hal, inf, or detect.
> # See below.
> # <source_disk> identifies where the file is to be copied from, and must
> # match en entry in the [Disks] section.
> # <filename> 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_NT]
> driver = d1,symmpi.sys,SYMMPI
> inf = d1,symmpi.inf
> [Files.scsi.SYMMPI_2K]
> driver = d2,symmpi.sys,SYMMPI
> inf = d2,symmpi.inf
> catalog = d2,symmpi2k.cat
> [Files.scsi.SYMMPI_XP32]
> driver = d3,symmpi.sys,SYMMPI
> inf = d3,symmpi.inf
> catalog = d3,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.
> #
> # <key_name> 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.
> # <value_name> specifies the value to be set within the key
> # <value_type> is a string like REG_DWORD. See below.
> # <value> specifies the actual value; its format depends on <value_type>
> value = Parameters,dummy,REG_DWORD,0
> value = Parameters\PnpInterface,5,REG_DWORD,1
>
>
>
> Anyone have a clue why Windows doesn´t find the driver?
>
> Thanks for any input!
>
> Jack

  Reply With Quote
Reply



Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off