> ...don´t let windows kill you...it´s not worth a life ;-)
>
> i have a working system which comes as follows:
>
> ...\os\somewindows\i386\$oem$\$1\drivers\raid\...
>
> ...\os\somewindows\i386\$oem$\$1\TEXTMODE\...
I guess you meant $OEM$\TEXTMODE instead of $oem$\$1\TEXTMODE\ ...
>
> i include the "normal" driver as well as the "TEXTMODE" driver during
> unattended setup menu selections and it works very well for me.
I've done it ...
>
> do you have subdirectories for every driver ?
I've got only one driver, the RAID one
I've done what you said, but setup complains about a file it can't find :
File \$WIN_NT$.~BT\$OEM$\Win32\a320raid.sys could not be loader. The error
code is 18
You must know my driver "contains" a Win32 directory that contains .sys .cat
and .inf files, whereas the txtsetup.oem is above :
4628333 -rwxr-xr-x 1 root root 3611 Jan 9 17:14 darreng.id
4628334 -rwxr-xr-x 1 root root 37 Jan 9 17:14 hraidsk1
4628035 -rwxr-xr-x 1 root root 8064 Jan 12 09:09 txtsetup.oem
4742385 drwxr-xr-x 2 root root 4096 Jan 12 09:19 win32
Must I modify the txtsetup.oem (attached in this mail) to remove the Win32
directory ? Has you "working RAID drivers" contain a subdirectory ?
>
>
>
>
> -----Original Message-----
> From: Hervé VOISIN [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, January 10, 2006 9:13 AM
> To: Dorn, Andreas (Frankfurt)
> Cc: [email protected]
> Subject: Re: [Unattended] Win2k3 and a320 raid drivers
>
> This method is working for the 1st part of the windows installation : the
> setup can see my drive and copies files on it, but it doesn't work anymore
> at the second stage : the setup asks me for the a320raid.inf file, though I
> made a directory called $1 which contains the same thing as the TEXTMODE
> one ... Windows is killing me : no logs, no clear infos about the setup,
> etc...
>
> Le Lundi 9 Janvier 2006 16:25, [EMAIL PROTECTED] a écrit :
> > i think you maybe need some directory like this in your path:
> >
> > \\unattendedserver\installshare\os\w2k3\I386\$oem$\TEXTMODE
> >
> > put the same hostraid drivers you would use for a manual setup in this
> > directory and take care that the TXTSETUP.OEM file is included.
> >
> > once this is done the unattended boot process will ask you to include the
> > driver at some point before starting the installation for example.
> >
> > hope this helps
> > cheers
> > andy
> >
> > -----Original Message-----
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Hervé
> > VOISIN Sent: Friday, January 06, 2006 10:42 AM
> > To: [email protected]
> > Subject: [Unattended] Win2k3 and a320 raid drivers
> >
> > hi all
> > I'v decided to write to this list as I've been trying to integrate a320
> > raid drivers to Win2k3 without success, though I tried during the last 3
> > weeks ! I've read so much mails, documentation, howtos and tutorials I
> > feel totally lost now :P
> > The hardware : IBM xSeries X346 : HostRaid (ServeRaid) -> Adaptec a320
> > drivers.
> > The OS : Win2k3 Standard
> >
> > I've tried I think every method : txtsetup.sif, unattended, nLite, etc
> > ... The best thing I've managed to do is an unattended Win2k3 _CD_ with
> > this driver thanks to nLite. But when I copy this CD in the unattended
> > tree, it stops at the second stage of windows installation, saying it
> > cant find a320raid.sys, though windows installer managed to format and
> > copy files on the drive !!! (ScreenShot attached)
> >
> > You're all of you my last hope ! :D Thank you
--
Hervé VOISIN
Poste 3201
#-----------------------------------------------------------------------------
# Copyright (c) Adaptec Inc. 2003
#-----------------------------------------------------------------------------
#
# General format:
#
# [section]
# key = value1,value2,...
#
#
# The hash ('#') introduces a comment.
# Strings with embedded spaces, commas, or hashes should be double-quoted
#
#------------------------------------------------------------------------------
# [Disks]
# diskN = "description",tagfile,directory
#
# The Disks section identifies the disks in the device installation kit.
#
# diskN
# Specifies a key that can be used in subsequent sections to identify
# the disk.
#
# description
# Specifies a string containing the name of the disk.
# Setup uses the description to prompt the user to insert the disk.
#
# tagfile
# Specifies the name of a verification file on the disk. The filename must
# be specified as a full path from the root and must not specify a drive.
# Setup checks for this file to ensure that the user inserted the correct
# disk.
#
# directory
# Specifies the directory on the disk where the installation files are
# located. The directory must be specified as a full path from the root and
# must not specify a drive.
#-------------------------------------------------------------------------------
[Disks]
d1 = "Adaptec HostRAID U320 Driver Ver 3.00 For Windows 2000/XP/2003",
\hraidsk1, \Win32
#-------------------------------------------------------------------------------
# [Defaults]
# component = ID
#
# The Defaults section lists the default driver(s) for each hardware component
# supported by this file. Setup highlights the default selection when it
# presents a list of drivers to the user.
#
# component
# Specifies a hardware component supported by this file. The component must
# be one of the following system-defined values: computer or scsi.
#
# ID
# Specifies a string that identifies the default option. This string matches
# an ID specified in the corresponding HwComponent section.
#
# If a txtsetup.oem file fails to define a default driver for a supported
# component, Setup uses the first entry in the HwComponent section.
#-------------------------------------------------------------------------------
[Defaults]
scsi = ADAPTEC_U320RAID_W2K
#-------------------------------------------------------------------------------
# [HwComponent]
# ID = description
#
# A HwComponent section lists the drivers available for a particular component.
# There is a HwComponent section for each type of component supported by the
# file.
#
# HwComponent
# The name of the section must be one of the following system-defined values:
# computer or scsi.
#
# ID
# Specifies a string, unique within this section, that identifies the
option.
# For each entry in this section, there must be a corresponding
# Files.HwComponent.ID section in the file.
#
# description
# Specifies a string that Setup presents to the user in the menu of driver
# choices.
#-------------------------------------------------------------------------------
[scsi]
ADAPTEC_U320RAID_W2K = "Adaptec HostRAID U320 Driver Ver 3.00 For Windows
2000/XP/2003"
#-------------------------------------------------------------------------------
# [Files.HwComponent.ID]
# filetype = diskN,filename[,DriverKey]
#
# A Files.HwComponent.ID section lists the files to be copied if the user
# selects a particular component option. One of these sections must be present
# for each option listed in each HwComponent section.
#
# HwComponent corresponds to the name of a HwComponent section in the file.
# ID corresponds to an ID entry in that HwComponent section.
#
# filetype
# Identifies the type of the file to be copied. One of these entries is
# present for each file to be copied for this HwComponent.ID. The filetype is
# one of the following system-defined values:
# driver, dll, hal, inf, catalog, detect
#
# driver - Valid for all components. Setup copies the file to
# %systemroot%\system32\drivers.
# inf - Valid for all components. Specifies the regular INF file for the
# device. This file is used during GUI-mode setup and for other device
# maintenance operations. The file is copied to %systemroot%\system32.
# catalog - Valid for drivers. Specifies a catalog file for the device.
# For example, catalog = d1, mydriver.cat.
# diskN
# Identifies the disk from which to copy the file.
# This value must match an entry in the Disks section.
#
# filename
# Specifies the name of the file, not including the directory path or drive.
# To form the full file name, Setup appends the filename to the directory
# specified for the disk in the Disks section.
#
# DriverKey
# Specifies the name of the key to be created in the registry services tree
# for this file, if the file is of type driver. This value is used to form
# Config.DriverKey section names. This value is required for components of
# type scsi.
#-------------------------------------------------------------------------------
[Files.scsi.ADAPTEC_U320RAID_W2K]
driver = d1,a320raid.sys, a320raid
inf = d1,a320raid.inf
inf = d1,adhraid.inf
catalog = d1,a320raid.cat
catalog = d1,adhraid.cat
#-------------------------------------------------------------------------------
# [Config.DriverKey]
# value = subkey_name,value_name,value_type,value
#
# A Config.DriverKey section specifies values to be set in the registry for
# particular component options. Setup automatically creates the required values
# in the Services\DriverKey key. Use this section to specify additional keys to
# be created under Services\DriverKey and values under Services\DriverKey and
# Services\DriverKey\subkey_name.
#
# subkey_name
# Specifies the name of a key under the Services\DriverKey tree where Setup
# places the specified value. Setup creates the key if it does not exist.
# If subkey_name is the empty string (""), the value is placed under the
# Services\DriverKey. The subkey_name can specify more than one level of
# subkey, such as "subkey1\subkey2\subkey3".
#
# value_name
# Specifies the name of the value to be set.
#
# value_type
# Specifes the type of the registry entry.
# The value_type can be one of the following:
# REG_DWORD, REG_SZ or REG_EXPAND_SZ, REG_BINARY, REG_MULTI_SZ
#
# value
# Specifies the value; its format depends on value_type.
#
# The following example shows a Config.DriverKey section:
# [Config.OEMSCSI]
# value = "",tag,REG_DWORD,5
# value = parameters\PnpInterface,5,REG_DWORD,1
#-------------------------------------------------------------------------------
[Config.a320raid]
value = "", Group, REG_SZ, "SCSI Miniport"
value = "", Start, REG_DWORD, 0
value = "", Tag, REG_DWORD, 1
value = "", Type, REG_DWORD, 1
# [HardwareIds.scsi.Service]
# id = "deviceID","service"
#
# A HardwareIds.scsi.Service section specifies the hardware IDs of the devices
# that a particular mass-storage driver supports.
#
# HardwareIds.scsi.Service
# Service specifies the service to be installed.
# deviceId
# Specifies the device ID for a mass-storage device.
# service
# Specifies the service to be installed for the device.
# The following example excerpt shows a HardwareIds.scsi.Service section for
# a disk device:
#
# [HardwareIds.scsi.oemscsi]
# id = "PCI\VEN_9005&DEV_8011","oemscsi"
#-------------------------------------------------------------------------------
#[HardwareIds.scsi.ADAPTEC_U320RAID_W2K]
#id = "PCI\VEN_9005&DEV_00c4","ADAPTEC_U320RAID_W2K"
#id = "PCI\VEN_9005&DEV_8011","ADAPTEC_U320RAID_W2K"
