-
@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.