Structure of RIS/SYSPREP additional drivers folders

[Hasse E]

Hi!

I'm trying to use the $OEM$/$1/drivers folder structure to add drivers for
NIC, Chipset, Audio and Video for a bunch of computers on my network. As far
as all descriptions about this go the structure under the $OEM$/$1/ foldet
should be Drivers/NIC, Drivers/Audio, Drivers/Video, Drivers/Chipset as an
example, and stated in the [OEMPnPDriversPath] section semicolon separated.
But What if I have subfolders under the drivers\nic for instance to support
different models of NICs? Say drivers\NIC\model1 Drivers\NIC\Model2. Would
the minisetup be able to find the drivers then? Or do they have to be
directly uinder the NIC subdirectory? I think I have read that the setup
automaticaly appends %SYSTEMROOT% before and subfolders after the specified
path but I'm not entirely sure. Anyway, using subfolders doesn't seem to
work. The Drivers folderstructure is copied but the drivers aren't
installed.

Any help much appreciated!

Rgds,
Hasse

 

[Rob]

You have to put all the drivers and support files in the root drivers\nic or
whatever subdirectory, and edit the TXTSETUP.SIF to remove all references to
the subfolders so it looks for the support files in the root folder.

For example:
Edit txtsetup.oem
[disks]
d1 = "driver disk set description", tagfile, \WinXP
(this section may contain folder names like \WinXP - those have to be
changed to "\")It will look like this when edited:d1 = "Adaptec HostRAID
U320 Driver Ver 1.02 For Windows 2000/XP/2003", \txtsetup.oem,\

 

[Gui]

You can put multiple drivers in the image on the ris server for example:
$oem\$1\Drivers\Nic\3com
$oem\$1\Drivers\Nic\Broadcom
$oem\$1\Drivers\Nic\intel

but you will need to specify the correct path in the .sif file associated
with that image like this

[Unattended]
OemPreinstall = YES
OemPnpDriversPath = "Drivers\Nic\Broadcom"

It will not just find it unless you specify the exact path.

hope this helps
Brian

 

[Hasse E]

Thanks Brian! I think this was the answer I wanted... Very easy to maintain
this way...

BR,

Hasse

You can put multiple drivers in the image on the ris server for example:
$oem\$1\Drivers\Nic\3com
$oem\$1\Drivers\Nic\Broadcom
$oem\$1\Drivers\Nic\intel

but you will need to specify the correct path in the .sif file associated
with that image like this

[Unattended]
OemPreinstall = YES
OemPnpDriversPath = "Drivers\Nic\Broadcom"

It will not just find it unless you specify the exact path.

hope this helps
Brian

Hi!

I'm trying to use the $OEM$/$1/drivers folder structure to add drivers for
NIC, Chipset, Audio and Video for a bunch of computers on my network. As far
as all descriptions about this go the structure under the $OEM$/$1/ foldet
should be Drivers/NIC, Drivers/Audio, Drivers/Video, Drivers/Chipset as an
example, and stated in the [OEMPnPDriversPath] section semicolon separated.
But What if I have subfolders under the drivers\nic for instance to support
different models of NICs? Say drivers\NIC\model1 Drivers\NIC\Model2. Would
the minisetup be able to find the drivers then? Or do they have to be
directly uinder the NIC subdirectory? I think I have read that the setup
automaticaly appends %SYSTEMROOT% before and subfolders after the specified
path but I'm not entirely sure. Anyway, using subfolders doesn't seem to
work. The Drivers folderstructure is copied but the drivers aren't
installed.

Any help much appreciated!

Rgds,
Hasse

 

[Matt]

Just as a side note, one thing I always do is add the driver paths into the
registry right before I use riprep to create a new image.

1). Create all the drivers you need in C:\drivers\, each driver should have
its own folder.

2) .Edit the following registry key:

HKLM\Software\Microsoft\Windows\CurrentVersion\DevicePath

It by default only has the following path: %SystemRoot%\inf , but you can
modify it and add more paths.

For example:
%SystemRoot%\inf;%SystemDrive\Drivers\3com;%SystemDrive\Drivers\Nvidia

%SystemDrive% = C:\
%SystemRoot% = C:\Winnt or C:\Windows depending on 2000/XP

Hope that helps you out in the future if you ever need to add more drivers
into your images
Matt

Thanks Brian! I think this was the answer I wanted... Very easy to maintain
this way...

BR,

Hasse

You can put multiple drivers in the image on the ris server for example:
$oem\$1\Drivers\Nic\3com
$oem\$1\Drivers\Nic\Broadcom
$oem\$1\Drivers\Nic\intel

but you will need to specify the correct path in the .sif file associated
with that image like this

[Unattended]
OemPreinstall = YES
OemPnpDriversPath = "Drivers\Nic\Broadcom"

It will not just find it unless you specify the exact path.

hope this helps
Brian

Hi!

I'm trying to use the $OEM$/$1/drivers folder structure to add drivers for
NIC, Chipset, Audio and Video for a bunch of computers on my network.

As
far

as all descriptions about this go the structure under the $OEM$/$1/ foldet
should be Drivers/NIC, Drivers/Audio, Drivers/Video, Drivers/Chipset

as

an

example, and stated in the [OEMPnPDriversPath] section semicolon separated.
But What if I have subfolders under the drivers\nic for instance to support
different models of NICs? Say drivers\NIC\model1 Drivers\NIC\Model2. Would
the minisetup be able to find the drivers then? Or do they have to be
directly uinder the NIC subdirectory? I think I have read that the setup
automaticaly appends %SYSTEMROOT% before and subfolders after the specified
path but I'm not entirely sure. Anyway, using subfolders doesn't seem to
work. The Drivers folderstructure is copied but the drivers aren't
installed.

Any help much appreciated!

Rgds,
Hasse