same driver /monitor problems; see here...

http://www.msfn.org/board/index.php?s=&amp...st&p=568387

Edited October 4, 200619 yr by the_doc735

[OemInfFiles]

i thought it would be best to continue discussion of this method in this forum instead of the x64 forum since it probably applies to more than that version of windows. i have not been able to find this method documented anywhere, so i will document it here.

EDIT: verified to work with 32-bit Windows.

by adding the following lines to WINNT.SIF, you can force GUIMODE setup to install a nonWHQL certified driver placed in X:\$OEM$\$$\OEMDIR on your unattended cd.

[Data]
	OemDrivers=OemInfFiles

[OemInfFiles]
	OemDriverFlags=1
	OemDriverPathName="%SystemRoot%\OemDir"
	OemInfName="driver0.inf"

OemInfName can be appended:

OemInfName="driver0.inf","driver1.inf","driver2.inf", ...

at some point during setup, the .INF files are copied to C:\Windows\inf as oem0.inf, oem1.inf, oem2.inf, ...

the source disk for the .INFs is defined by OemDriverPathName. during device detection in GUIMODE setup, these drivers are prioritized over the default ones included with windows. i am assuming that OemDriverFlags=1 is what allows this to happen.

@PhreeZ

can you still use 'oempnpdriverspath' as well? I have a promise (fasttx2k/ulsata) RAID and intel (875p)chipset driver collection in that folder you see?

thanks in advance?

Edited October 8, 200619 yr by the_doc735

@the_doc735:

OemPnPDriversPath works with [OemInfFiles].

@the_doc735:

OemPnPDriversPath works with [OemInfFiles].

the big question has to be:

does this [OemInfFiles] work for monitor drivers? (monitors don't seem to be detected by setup? - yes?)

many thanks in advance