[OemInfFiles]

MSFN Home·Forum Rules·Unattended Guide·Login·Register

Search ·Members·Calendar·Help·Contact Us

MSFN Forums > Unattended Windows Discussion & Support > Device Drivers

Unattended CD/DVD Guide Homepage · MSFN Forum Rules

[OemInfFiles]

Options

PhreeZ View Member Profile	Jun 26 2005, 01:32 PM Post #1
Newbie Group: Members Posts: 37 Joined: 21-May 05 Member No.: 57044	[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. CODE [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. here is an excerpt from setupapi.log: CODE [2005/06/25 22:16:41 280.1784 Driver Install] #-019 Searching for hardware ID(s): pci\ven_10de&dev_0053&subsys_cb8410de&rev_a2,pci\ven_10de&dev_0053&subsys_cb8410de,pci\ven_10de&dev_0053&cc_01018a,pci\ven_10de&dev_0053&cc_0101 #-018 Searching for compatible ID(s): pci\ven_10de&dev_0053&rev_a2,pci\ven_10de&dev_0053,pci\ven_10de&cc_01018a,pci\ven_10de&cc_0101,pci\ven_10de,pci\cc_01018a,pci\cc_0101 #-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup #I393 Modified INF cache "C:\WINDOWS\inf\INFCACHE.1". #I022 Found "PCI\VEN_10DE&DEV_0053" in C:\WINDOWS\inf\oem0.inf; Device: "NVIDIA nForce4 Parallel ATA Controller"; Driver: "NVIDIA nForce4 Parallel ATA Controller"; Provider: "NVIDIA Corporation"; Mfg: "NVIDIA Corporation"; Section name: "Crush11_Inst". #I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001. #I023 Actual install section: [Crush11_Inst.NTAMD64]. Rank: 0x0000a001. Driver date: 05/12/2005. Version: 5.10.2600.533. #I022 Found "PCI\CC_0101" in C:\WINDOWS\inf\mshdc.inf; Device: "Standard Dual Channel PCI IDE Controller"; Driver: "Standard Dual Channel PCI IDE Controller"; Provider: "Microsoft"; Mfg: "(Standard IDE ATA/ATAPI controllers)"; Section name: "pciide_Inst". #I023 Actual install section: [pciide_Inst]. Rank: 0x00003006. Driver date: 10/01/2002. Version: 5.2.3790.1830. #I022 Found "PCI\VEN_10DE&DEV_0053" in C:\Drivers\000_CHIPSET\nForce4x64_IDE\nvatax64.inf; Device: "NVIDIA nForce4 Parallel ATA Controller"; Driver: "NVIDIA nForce4 Parallel ATA Controller"; Provider: "NVIDIA Corporation"; Mfg: "NVIDIA Corporation"; Section name: "Crush11_Inst". #I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001. #I023 Actual install section: [Crush11_Inst.NTAMD64]. Rank: 0x0000a001. Driver date: 05/12/2005. Version: 5.10.2600.533. #-166 Device install function: DIF_SELECTBESTCOMPATDRV. #I319 Driver "Standard Dual Channel PCI IDE Controller" in "c:\windows\inf\mshdc.inf" section [pciide_Inst] skipped (DNF_BAD_DRIVER). #I063 Selected driver installs from section [Crush11_Inst] in "c:\windows\inf\oem0.inf". #I320 Class GUID of device remains: {4D36E96A-E325-11CE-BFC1-08002BE10318}. #I060 Set selected driver. #I058 Selected best compatible driver. #-124 Doing copy-only install of "PCI\VEN_10DE&DEV_0053&SUBSYS_CB8410DE&REV_A2\3&2411E6FE&0&30". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\windows\inf\oem0.inf" for driver "NVIDIA nForce4 Parallel ATA Controller" will be installed (Policy=Ignore). Error 1168: Element not found. #-024 Copying file "C:\WINDOWS\OemDir\nvatax64.sys" to "C:\WINDOWS\system32\DRIVERS\nvatax64.sys". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\WINDOWS\OemDir\nvatax64.sys" for driver "NVIDIA nForce4 Parallel ATA Controller" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\WINDOWS\OemDir\idecoi.dll" to "C:\WINDOWS\system32\idecoi.dll" via temporary file "C:\WINDOWS\system32\SET17D.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\WINDOWS\OemDir\idecoi.dll" for driver "NVIDIA nForce4 Parallel ATA Controller" will be installed (Policy=Ignore). Error 1168: Element not found. #-166 Device install function: DIF_REGISTER_COINSTALLERS. #I056 Coinstallers registered. #-148 Loading coinstaller modules for "NVIDIA nForce4 Parallel ATA Controller". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\WINDOWS\system32\idecoi.dll" for driver "NVIDIA nForce4 Parallel ATA Controller" will be installed (Policy=Ignore). Error 87: The parameter is incorrect. #-166 Device install function: DIF_INSTALLINTERFACES. #-011 Installing section [Crush11_Inst.NTAMD64.Interfaces] from "c:\windows\inf\oem0.inf". #I054 Interfaces installed. #-166 Device install function: DIF_INSTALLDEVICE. #I123 Doing full install of "PCI\VEN_10DE&DEV_0053&SUBSYS_CB8410DE&REV_A2\3&2411E6FE&0&30". #I121 Device install of "PCI\VEN_10DE&DEV_0053&SUBSYS_CB8410DE&REV_A2\3&2411E6FE&0&30" finished successfully. line #I319 is interesting as this is where setup skips the default windows driver. This post has been edited by PhreeZ: Jun 26 2005, 06:41 PM

Replies

PhreeZ View Member Profile	Oct 9 2006, 02:24 PM Post #2
Newbie Group: Members Posts: 37 Joined: 21-May 05 Member No.: 57044	@the_doc735: OemPnPDriversPath works with [OemInfFiles].

the_doc735 View Member Profile	Oct 11 2006, 07:55 AM Post #3
Junior Group: Members Posts: 96 Joined: 17-August 06 Member No.: 107768	QUOTE (PhreeZ @ Oct 9 2006, 09:24 PM) @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

Posts in this topic

PhreeZ [OemInfFiles] Jun 26 2005, 01:32 PM

PhreeZ i've tried using this method to install the nv... Jun 26 2005, 01:48 PM

Bâshrat the Sneaky Do you also know whether this forces the specified... Jul 18 2005, 01:37 AM

bilemke QUOTE (Bâshrat the Sneaky @ Jul 18 2005, 01:3... Jul 19 2005, 02:28 PM

PhreeZ @Bâshrat the Sneaky: i believe the driver install... Jul 19 2005, 02:43 PM

bilemke QUOTE (PhreeZ @ Jul 19 2005, 02:43 PM)@Bâshra... Jul 19 2005, 10:37 PM

PhreeZ @bilemke: i have no experience with PE, but the me... Jul 20 2005, 09:16 PM

bilemke My intention was to find a way to skip seeing the ... Jul 21 2005, 12:46 AM

hp38guser This might just work for custom monitor drivers fo... Jul 21 2005, 03:36 PM

cyberloner RE: [OemInfFiles] Aug 21 2006, 08:43 AM

PhreeZ @bilemke: i am curious as to why you want to skip ... Jul 25 2005, 04:57 PM

bilemke QUOTE (PhreeZ @ Jul 25 2005, 04:57 PM)@bilemk... Aug 23 2005, 01:11 PM

PhreeZ thanks to Silentman for verifying this method work... Jul 25 2005, 06:14 PM

PhreeZ i tried appending the OemDriverPathName entry with... Aug 23 2005, 11:06 AM

cyberloner by using old method and point the driver to harddi... Aug 22 2006, 01:53 PM

the_doc735 same driver /monitor problems; see here... http:/... Oct 4 2006, 12:47 PM

the_doc735 QUOTE (PhreeZ @ Jun 26 2005, 08:32 PM) [O... Oct 8 2006, 08:07 AM

PhreeZ @the_doc735: OemPnPDriversPath works with [OemInf... Oct 9 2006, 02:24 PM

the_doc735 QUOTE (PhreeZ @ Oct 9 2006, 09:24 PM) @th... Oct 11 2006, 07:55 AM

« Next Oldest · Device Drivers · Next Newest »

2 User(s) are reading this topic (2 Guests and 0 Anonymous Users)

0 Members:

Display Mode: Switch to: Standard · Switch to: Linear+ · Outline

Track this topic · Email this topic · Print this topic · Subscribe to this forum

Lo-Fi Version

Time is now: 22nd November 2009 - 04:44 PM