PhreeZ

@the_doc735: OemPnPDriversPath works with [OemInfFiles].

Try [OemInfFiles]

try [OemInfFiles]...

try [OemInfFiles]

try [OemInfFiles]

@cyberloner: check out the [OemInfFiles] method.

perhaps your drivers are being extracted after GUI-mode setup detects and installs your devices.

@THXTEX: if your drivers come with a .CAT file they should be WHQL. check setupapi.log in your WINDOWS folder see if you can find the device or the .INF you are trying to install.

@Jackrip5: if you are using this method to install on your NVRAID, it should not interfere with any existing OemPnPDriversPath entries.

@Mengha: it doesn't really matter what folder you put the drivers in. organize it as you see fit. just make sure the OemPnPDriversPath in your WINNT.SIF matches where you put the drivers.

@THXTEX: try removing %SYSTEMDRIVE% from the OemPnPDriversPath entry. i believe it should look as follows: [Unattended] OemPnPDriversPath="Drivers\Chipset;Drivers\Lan" are those drivers WHQL certified?

@n00b: try adding the [OemInfFiles] entries to your unattend.txt. let me know if you get it to work.

@Levster: try using the nForce 7.13 PATARAID IDE drivers and the method i described HERE.

i tried appending the OemDriverPathName entry with no success. the following two formats failed: OemPnPDriversPath="PATH1","PATH2" OemPnPDriversPath="PATH1;PATH2" it seems this method is limited to a single source path.

@Dynaletik: try installing your monitor using the method i described HERE. let us know if you get it to work.

@oioldman: try installing your monitor using the method i described [url="http://www.msfn.org/board/index.php?showtopic=49374"]HERE[/url]. let us know if you get it to work.

give [OemInfFiles] a try. add the following lines to WINNT.SIF [Data] OemDrivers=OemInfFiles [OemInfFiles] OemDriverFlags=1 OemDriverPathName="%SystemRoot%\OemDir" OemInfName="driver0.inf" edit OemDriverPathName to match the path to the drivers and modify OemInfName to correspond with the correct .INF. let us know if you get it to work.

@dale5605: what symptoms are you experiencing that leads you to believe it didn't work? you can always use the OemInfFiles entries. i know those work with 7.13.

thanks to Silentman for verifying this method works with a device other than a mass storage controller. i had originally thought this method would be useful for only nonWHQL drivers. apparently, setup still prioritizes its own drivers although newer WHQL drivers are supplied.

it is interesting that setup prioritized its own driver then. i figured drivers were prioritized by date. i guess it's the version number matters.

@bilemke: i am curious as to why you want to skip TEXTMODE setup. @hp38guser: how did the monitor installation experiment go?

@Silentman: thanks for reporting back. excellent stuff. was that AMD driver WHQL'd? did it come with a .CAT file?

@Silentman: the [OemInfFiles] entry shouldn't be the cause of the problem. try checking setupapi.log in the WINDOWS root folder. find the line where windows skips the installation of that driver. why not try installing that AMD K8 driver using OemInfFiles. let us know if it works.

@bilemke: i have no experience with PE, but the method you are describing sounds very similar install method i was using before i found out about the OemInfFiles entries. with the $WIN_NT$.~BT folder, ntldr, $LDR$, TXTSETUP.SIF, and minor changes to boot.ini all placed in the root i could boot up the computer for an installation. i believe this method loads the same files as using the floppy-boot install. i just had to throw in my WINNT.SIF into the $WIN_NT$.~BT folder to have a cd-based source. i was hoping to try PE, until i found the method above. is this method similar to your process? i would think making changes to WINNT.SIF is easier than altering $WINNT$.INF. after all, $WINNT$.INF is based off the .SIF file.

@dale5605: it should be good for both.