RIS Deploy, Added drivers (SATA HD)

Hi!


I'm doing some tests on RIS tp deplay Windows XP at a customer site.
I've got it all working fine from my two lab PCs.
One image for laptops and one for workstations.
I know that the customer have all kinds of hardware and I know that I will
have to add drivers for all kinds of stuff to my images.
I found some information about this in TechNET but it's not all I need.
To test my own stuff I'm using a computer with Serial ATA disk (SATA).
As far as I can understand I have to create $OEM$ folder and the do some
editing in the .SIF file to enable it to search for drivers there.
Create a folderstructure below this with \Drivers\"Hardwaretype" and just
add the drivers there.
The problem is this... I can only find information about add another modem
or printer and what not, but how do I get it to load the driver for the SATA
disk, I just cant have the user pressing F6 and isert a driver disk.
They'll never figure that one out, and if they do, they'll probably get the
wrong disk or something....
Is there a document (that I've failed to find) that contains the FULL
folderstructure that needs to be created below $OEM$ folder?
Or is it as simple as RIS does not support SATA or SCSI?


On another related note.
We have WinPE (we are solution provider).
I haven't had the time to read that documentation yet.
If someone just can give me some short pointers of what the benefit of it is
I'd be a happy camper for the rest of the day : )


Regards,
Fredrik Landin
--

Fredrik.Landin@SYSteam.se

Fredrik,

I cannot quote the source, but this would be handled the same way SCSI
would. There are some articles that describe installing OEM SCSI drivers
that would apply. Try searching there.

For PE to recognize it, you can press F6 or you will need to create a new PE
CD by adding the infs to inf, sys to drivers, and the rest of the files to
system32. The PE docs cover some of it.

"Fredrik Landin" <landin@home.se> wrote in message
news:%23j%23y6fcfDHA.3700@TK2MSFTNGP11.phx.gbl...
> Hi!
>
>
> I'm doing some tests on RIS tp deplay Windows XP at a customer site.
> I've got it all working fine from my two lab PCs.
> One image for laptops and one for workstations.
> I know that the customer have all kinds of hardware and I know that I will
> have to add drivers for all kinds of stuff to my images.
> I found some information about this in TechNET but it's not all I need.
> To test my own stuff I'm using a computer with Serial ATA disk (SATA).
> As far as I can understand I have to create $OEM$ folder and the do some
> editing in the .SIF file to enable it to search for drivers there.
> Create a folderstructure below this with \Drivers\"Hardwaretype" and just
> add the drivers there.
> The problem is this... I can only find information about add another modem
> or printer and what not, but how do I get it to load the driver for the
SATA
> disk, I just cant have the user pressing F6 and isert a driver disk.
> They'll never figure that one out, and if they do, they'll probably get
the
> wrong disk or something....
> Is there a document (that I've failed to find) that contains the FULL
> folderstructure that needs to be created below $OEM$ folder?
> Or is it as simple as RIS does not support SATA or SCSI?
>
>
> On another related note.
> We have WinPE (we are solution provider).
> I haven't had the time to read that documentation yet.
> If someone just can give me some short pointers of what the benefit of it
is
> I'd be a happy camper for the rest of the day : )
>
>
> Regards,
> Fredrik Landin
> --
>
> Fredrik.Landin@SYSteam.se
>
>

As I am reading this, you do not want a specific build for that SATA
machine, but would rather it install as needed, right? If so, read on.

OK, I found my old notes on this. Microsoft PSS gets credit for this, but
not officially as it is unsupported. ;-) This applied to W2K, but should
carry over. Adjust accordingly ;-)


Here goes:

Copy the i386 folder and its contents from the 2000 Cd-rom to the root of a
folder (ex. named "FLAT")

Now we are going to "trick" windows into thinking the 3rd party drivers are
"in-the-box" by modifying the following files:

Winnt.sif

Hivesys.inf

Txtsetup.sif



File structure on the folder should look like this:

c:\flat\i386\$oem$\$1\drivers\scsi

You will need the following 3rd party drivers:

txtsetup.oem

3rdparty.cat

3rdparty.inf

3rdparty.sys



----------------------- FILE ADDITIONS TO FLAT -----------------------------

\i386\3rdparty.sys

\$oem$\$1\drivers\scsi\<entire contents of scsi driver package:
txtsetup.oem,
3rdparty.cat, 3rdparty.inf, 3rdparty.sys>

(SO, THE DRIVER (.SYS) FILE SHOULD BE LOCATED IN BOTH THE I386 AND THE
$OEM$\$1\DRIVERS\SCSI DIRECTORIES)


------------------------ WINNT.SIF CHANGES
-----------------------------------



Verify the following:

[Unattended]

OemPreinstall = Yes

OemPnPDriversPath = "DRIVERS\SCSI"

NT Upgrade = No

Win9xUpgrade = No

DriverSigningPolicy = Ignore



[MassStorageDrivers]

; Rem out all (cdrom should be detected during install process)



[OEMBootFiles]

; Rem out all



[UserData]

ProductID = xxxxx-xxxxx-xxxxx-xxxxx-xxxxx



[GuiUnattended]

OEMSkipRegional=1

OemSkipWelcome=1



------------------------ HIVESYS.INF CHANGES-----------------------------

search HIVESYS.INF for reference to "aic78xx" and copy and paste the aic78xx
lines directly below it to revise with our driver name instead, such as:



Copy these:

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","ErrorControl",0x00010003,1

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","Group",0x00000002,"SCSI
miniport"

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","Start",0x00010003,4

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","Tag",0x00010003,30

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx","Type",0x00010003,1

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx\Parameters",,0x00000012

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx\Parameters\PnpInterface","5"
,0x
00010003,1



and paste and revise as necessary (where "3rdparty" is the correct
drivername):

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","ErrorControl",0x00010003,
1

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","Group",0x00000002,"SCSI
miniport"

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","Start",0x00010003,4

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","Tag",0x00010003,30

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty","Type",0x00010003,1

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty\Parameters",,0x00000012

(**See Below**)

HKLM,"SYSTEM\CurrentControlSet\Services\aic78xx\Parameters\PnpInterface","5"
,0x
00010003,1



**ALERT:

HKLM,"SYSTEM\CurrentControlSet\Services\3rdparty\Parameters\PnpInterface","5
",0
x00010003,1

PLEASE confirm that the value at the end of this line "0x00010003,1" is the
same as the REG_DWORD value at the bottom of your 3rdparty.inf file



Search again for aic78xx and you will hit in a different section where you
will
see:



Copy these lines:

HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\aic78xx","EventMessa
geF
ile",0x00020002,"%SystemRoot%\System32\IoLogMsg.dll"

HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\aic78xx","TypesSuppo
rte
d",0x00010003,7



And paste and revise:

HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\3rdparty","EventMess
age
File",0x00020002,"%SystemRoot%\System32\IoLogMsg.dll"

**ALERT:

0x00020002 - confirm this number from the value listed in the 3rdparty.inf
file
under: REG_EXPAND_SZ value



HKLM,"SYSTEM\CurrentControlSet\Services\EventLog\System\3rdparty","TypesSupp
ort
ed",0x00010003,7

**ALERT:

0x00010003 - confirm this number from the value listed in the 3rdparty.inf
file
under: REG_DWORD value



--------------- TXTSETUP. SIF MODIFICATIONS
(ADDITIONS)----------------------

;The specific values for this driver were taken from the driver's
OEMSETUP.INF
(or 3rdparty.inf) file

[SourceDisksFiles]

search for aic78xx.sys and paste the driver name with the same value:

3rdparty.sys = 1,,,,,,3_,4,1 (this value was copied from the aix78xx.sys
entry)



[HardwareIdsDatabase]

example:

PCI\VEN_1044&DEV_A501 = "drivername" -

PLEASE NOTE: the PCI\VEN value will vary depending on the driver.

This value can be found from the 3rdparty.sys file, under the manufacturer
section with a DeviceDesc% value in the string.



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



[SCSI]
drivername = "Driver Description - SCSI Adapters for Windows 2000 and
greater x86"

Burn these files as outlined and you should have a cdrom unattended install
that includes 3rd party scsi drivers.

"Fredrik Landin" <landin@home.se> wrote in message
news:%23j%23y6fcfDHA.3700@TK2MSFTNGP11.phx.gbl...
> Hi!
>
>
> I'm doing some tests on RIS tp deplay Windows XP at a customer site.
> I've got it all working fine from my two lab PCs.
> One image for laptops and one for workstations.
> I know that the customer have all kinds of hardware and I know that I will
> have to add drivers for all kinds of stuff to my images.
> I found some information about this in TechNET but it's not all I need.
> To test my own stuff I'm using a computer with Serial ATA disk (SATA).
> As far as I can understand I have to create $OEM$ folder and the do some
> editing in the .SIF file to enable it to search for drivers there.
> Create a folderstructure below this with \Drivers\"Hardwaretype" and just
> add the drivers there.
> The problem is this... I can only find information about add another modem
> or printer and what not, but how do I get it to load the driver for the
SATA
> disk, I just cant have the user pressing F6 and isert a driver disk.
> They'll never figure that one out, and if they do, they'll probably get
the
> wrong disk or something....
> Is there a document (that I've failed to find) that contains the FULL
> folderstructure that needs to be created below $OEM$ folder?
> Or is it as simple as RIS does not support SATA or SCSI?
>
>
> On another related note.
> We have WinPE (we are solution provider).
> I haven't had the time to read that documentation yet.
> If someone just can give me some short pointers of what the benefit of it
is
> I'd be a happy camper for the rest of the day : )
>
>
> Regards,
> Fredrik Landin
> --
>
> Fredrik.Landin@SYSteam.se
>
>

Fredrik,

The correct method to do this would be similiar to integrating a mass
storage driver into a regular network installation. See the following KB

http://support.microsoft.com/defaul...KB;EN-US;816299

The only difference is that with a RISETUP image the $oem$ goes at the same
level as I386 not below it.

Scott McArthur[MS]
Microsoft Windows Server Setup Support
This posting is provided "AS IS" with no warranties, and confers no rights
--------------------
| From: "Fredrik Landin" <landin@home.se>
| Subject: RIS Deploy, Added drivers (SATA HD)
| Date: Thu, 18 Sep 2003 11:33:52 +0200
| Lines: 38
| X-Priority: 3
| X-MSMail-Priority: Normal
| X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
| X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
| Message-ID: <#j#y6fcfDHA.3700@TK2MSFTNGP11.phx.gbl>
| Newsgroups: microsoft.public.windowsxp.setup_deployment
| NNTP-Posting-Host: fw.systeam.se 194.218.203.20
| Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
| Xref: cpmsftngxa06.phx.gbl
microsoft.public.windowsxp.setup_deployment:84633
| X-Tomcat-NG: microsoft.public.windowsxp.setup_deployment
|
| Hi!
|
|
| I'm doing some tests on RIS tp deplay Windows XP at a customer site.
| I've got it all working fine from my two lab PCs.
| One image for laptops and one for workstations.
| I know that the customer have all kinds of hardware and I know that I will
| have to add drivers for all kinds of stuff to my images.
| I found some information about this in TechNET but it's not all I need.
| To test my own stuff I'm using a computer with Serial ATA disk (SATA).
| As far as I can understand I have to create $OEM$ folder and the do some
| editing in the .SIF file to enable it to search for drivers there.
| Create a folderstructure below this with \Drivers\"Hardwaretype" and just
| add the drivers there.
| The problem is this... I can only find information about add another modem
| or printer and what not, but how do I get it to load the driver for the
SATA
| disk, I just cant have the user pressing F6 and isert a driver disk.
| They'll never figure that one out, and if they do, they'll probably get
the
| wrong disk or something....
| Is there a document (that I've failed to find) that contains the FULL
| folderstructure that needs to be created below $OEM$ folder?
| Or is it as simple as RIS does not support SATA or SCSI?
|
|
| On another related note.
| We have WinPE (we are solution provider).
| I haven't had the time to read that documentation yet.
| If someone just can give me some short pointers of what the benefit of it
is
| I'd be a happy camper for the rest of the day : )
|
|
| Regards,
| Fredrik Landin
| --
|
| Fredrik.Landin@SYSteam.se
|
|
|