 [OemInfFiles] |
  |
 Jun 26 2005, 01:32 PM
Post
#1
|
|
|
Newbie Group: Members Posts: 38 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 |
 |
 
|
|
Jun 26 2005, 01:48 PM
Post
#2
|
|
|
Newbie Group: Members Posts: 38 Joined: 21-May 05 Member No.: 57044
|
i've tried using this method to install the nvidia 77.72 x64 display driver, which is nonWHQL, but it failed. i'm trying to figure out how to resolve Cannot create a stable subkey under a volatile parent key as i believe it to be the cause of the driver installation failure.
EDIT: Same errors happen using the 71.84 WHQL driver, but it successfully installs.  here is an excerpt from setupapi.log for reference: CODE [2005/06/25 22:16:41 280.1793 Driver Install] #-019 Searching for hardware ID(s): pci\ven_10de&dev_0161&subsys_81ae1043&rev_a1,pci\ven_10de&dev_0161&subsys_81ae1043,pci\ven_10de&dev_0161&cc_030000,pci\ven_10de&dev_0161&cc_0300 #-018 Searching for compatible ID(s): pci\ven_10de&dev_0161&rev_a1,pci\ven_10de&dev_0161,pci\ven_10de&cc_030000,pci\ven_10de&cc_0300,pci\ven_10de,pci\cc_030000,pci\cc_0300 #-199 Executing "C:\WINDOWS\system32\setup.exe" with command line: setup -newsetup #I022 Found "PCI\CC_0300" in C:\WINDOWS\inf\display.inf; Device: "Standard VGA Graphics Adapter"; Driver: "Standard VGA Graphics Adapter"; Provider: "Microsoft"; Mfg: "(Standard display types)"; Section name: "vga". #I023 Actual install section: [vga]. Rank: 0x00002006. Driver date: 10/01/2002. Version: 5.2.3790.1830. #I022 Found "PCI\VEN_10DE&DEV_0161" in C:\WINDOWS\inf\oem1.inf; Device: "NVIDIA GeForce 6200 TurboCache(TM)"; Driver: "NVIDIA GeForce 6200 TurboCache(TM)"; Provider: "NVIDIA"; Mfg: "NVIDIA"; Section name: "nv4_NV3x". #I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001. #I023 Actual install section: [nv4_NV3x]. Rank: 0x0000a001. Driver date: 06/15/2005. Version: 7.7.7.2. #I022 Found "PCI\VEN_10DE&DEV_0161" in C:\Drivers\002_GRAPHICS\x64_ForceWare\nv4_disp.inf; Device: "NVIDIA GeForce 6200 TurboCache(TM)"; Driver: "NVIDIA GeForce 6200 TurboCache(TM)"; Provider: "NVIDIA"; Mfg: "NVIDIA"; Section name: "nv4_NV3x". #I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001. #I023 Actual install section: [nv4_NV3x]. Rank: 0x0000a001. Driver date: 06/15/2005. Version: 7.7.7.2. #-148 Loading coinstaller modules for "Video Controller (VGA Compatible)". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\WINDOWS\system32\nvcod.dll" for driver "Video Controller (VGA Compatible)" will be installed (Policy=Ignore). Error 87: The parameter is incorrect. #-166 Device install function: DIF_SELECTBESTCOMPATDRV. #I319 Driver "Standard VGA Graphics Adapter" in "c:\windows\inf\display.inf" section [vga] skipped (DNF_BAD_DRIVER). #I063 Selected driver installs from section [nv4_NV3x] in "c:\windows\inf\oem1.inf". #I320 Class GUID of device remains: {4D36E968-E325-11CE-BFC1-08002BE10318}. #I060 Set selected driver. #I058 Selected best compatible driver. #-124 Doing copy-only install of "PCI\VEN_10DE&DEV_0161&SUBSYS_81AE1043&REV_A1\4&243D7BD0&0&0070". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "c:\windows\inf\oem1.inf" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nv4_mini.sy_" to "C:\WINDOWS\system32\DRIVERS\nv4_mini.sys" via temporary file "C:\WINDOWS\system32\DRIVERS\SET1BE.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nv4_mini.sy_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvcod.dl_" to "C:\WINDOWS\system32\nvcod.dll" via temporary file "C:\WINDOWS\system32\SET1BF.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvcod.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvcod.dl_" to "C:\WINDOWS\system32\nvcodins.dll" via temporary file "C:\WINDOWS\system32\SET1C0.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvcod.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nv4_disp.dl_" to "C:\WINDOWS\system32\nv4_disp.dll" via temporary file "C:\WINDOWS\system32\SET1C1.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nv4_disp.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvoglnt.dl_" to "C:\WINDOWS\system32\nvoglnt.dll" via temporary file "C:\WINDOWS\system32\SET1C2.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvoglnt.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvogl32.dl_" to "C:\WINDOWS\SysWow64\nvogl32.dll" via temporary file "C:\WINDOWS\SysWow64\SET1C3.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvogl32.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvcpl.dl_" to "C:\WINDOWS\system32\nvcpl.dll" via temporary file "C:\WINDOWS\system32\SET1C4.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvcpl.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvcpl.dl_" to "C:\WINDOWS\system32\nvcplins.dll" via temporary file "C:\WINDOWS\system32\SET1C5.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvcpl.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvcpl32.ex_" to "C:\WINDOWS\system32\nvcpl32.exe" via temporary file "C:\WINDOWS\system32\SET1C6.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvcpl32.ex_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvmctray.dl_" to "C:\WINDOWS\system32\nvmctray.dll" via temporary file "C:\WINDOWS\system32\SET1C7.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvmctray.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvwddi64.dl_" to "C:\WINDOWS\system32\nvwddi64.dll" via temporary file "C:\WINDOWS\system32\SET1C8.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvwddi64.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvnt4cpl.dl_" to "C:\WINDOWS\system32\nvnt4cpl.dll" via temporary file "C:\WINDOWS\system32\SET1C9.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvnt4cpl.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvwddi.dl_" to "C:\WINDOWS\SysWow64\nvwddi.dll" via temporary file "C:\WINDOWS\SysWow64\SET1CA.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvwddi.dl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvcpl.hl_" to "C:\WINDOWS\help\nvcpl.hlp" via temporary file "C:\WINDOWS\help\SET1CB.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvcpl.hl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 1168: Element not found. #-336 Copying file "C:\OEM\nvwcplen.hl_" to "C:\WINDOWS\help\nvwcplen.hlp" via temporary file "C:\WINDOWS\help\SET1CC.tmp". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\OEM\nvwcplen.hl_" for driver "NVIDIA GeForce 6200 TurboCache(TM)" 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 GeForce 6200 TurboCache(TM)". #W360 An unsigned, incorrectly signed, or Authenticode(tm) signed file "C:\WINDOWS\system32\nvcodins.dll" for driver "NVIDIA GeForce 6200 TurboCache(TM)" will be installed (Policy=Ignore). Error 87: The parameter is incorrect. #-166 Device install function: DIF_INSTALLINTERFACES. #-011 Installing section [nv4_NV3x.Interfaces] from "c:\windows\inf\oem1.inf". #I054 Interfaces installed. #-166 Device install function: DIF_INSTALLDEVICE. #E008 Setting registry value HKLM\Software\NVIDIA Corporation\Global\NvSvc\OemConfigurations\LoadLimitedSID #E033 Error 1021: Cannot create a stable subkey under a volatile parent key. #E065 Parsing AddReg section [nv_SoftwareDeviceSettings] in "c:\windows\inf\oem1.inf" failed. Error 1021: Cannot create a stable subkey under a volatile parent key. #E064 Parsing install section [nv4_NV3x.SoftwareSettings] in "c:\windows\inf\oem1.inf" failed. Error 1021: Cannot create a stable subkey under a volatile parent key. #E154 Class installer failed. Error 87: The parameter is incorrect. #I060 Set selected driver. #-166 Device install function: DIF_INSTALLDEVICE. #E154 Class installer failed. Error 0xe0000203: There is no driver selected for the device information set or element. #-166 Device install function: DIF_INSTALLDEVICE. #E154 Class installer failed. Error 0xe0000203: There is no driver selected for the device information set or element. i am still unsure whether [OemInfFiles] is suitable for anything other than mass storage controllers. if anybody is successfully able to use this method to install nonWHQL drivers for other devices, please let me know. 
This post has been edited by PhreeZ: Jun 29 2005, 02:12 PM |
|
|
|
|
Jul 18 2005, 01:37 AM
Post
#3
|
|
|
... but not really  Group: Patrons Posts: 5719 Joined: 29-October 03 From: Hasselt, Belgium Member No.: 8748 OS: none 
|
Do you also know whether this forces the specified .inf file to be installed either there is a compatible HWID or not?
If it just gets installed when it's necessary, then this might be a great solution! P.S.: where did you find the information about this method??? 
|
|
|
|
|
Jul 19 2005, 02:28 PM
Post
#4
|
|
|
Member  Group: Members Posts: 228 Joined: 8-December 03 Member No.: 10619 |
QUOTE (Bâshrat the Sneaky @ Jul 18 2005, 01:37 AM) P.S.: where did you find the information about this method???  Indeed. Searching this on google finds only MSFN and two german boards (one being Winfuture).. May I also ask where you found this? Was it one of the two german forums/boards I see in google? |
|
|
|
|
Jul 19 2005, 02:43 PM
Post
#5
|
|
|
Newbie Group: Members Posts: 38 Joined: 21-May 05 Member No.: 57044
|
@Bâshrat the Sneaky:
i believe the driver installation is only forced only if there is a compatible HWID. looking at the first few lines of setupapi.log, setup seems to first identify the device HWID, then searches available .INFs for a match. line #I319 is the point in setup where the windows drivers are ignored and the drivers in OEMDIR are installed. i haven't verified it, but i assume that if the OEMDIR drivers are older than the windows drivers, OEMDIR drivers won't be installed. i came across this method while i was trying to get NF4 x64 RAID drivers integrated into an unattended x64 installation. i always inspected the logs (especially setupapi) in the windows root after installations, to try and figure out why it would fail. i started off trying METHOD1 then METHOD2. METHOD1 always blue screened and i could never get METHOD2 to work from a cd-boot installation. there would always be the OEMDISK.C/ERROR (18).  eventually, i gave a network installation using METHOD2 a try and it worked. i later modified the installation with an HDD-boot and source files from CD. i stayed with this method for a while. one day, i decided to figure out why METHOD2 would work and METHOD1 wouldn't. setupapi.log gave the answer. with M1, the NVIDIA NForce Storage Controller was not being installed during GUIMODE. since the driver was not WHQL certified, setup prioritized the installation of its own Standard Dual Channel PCI IDE Controller. however, M2 seemed to be forcing the installation somehow, evident in line #I319. i did more snooping and noticed $WINNT$.INF in the SYSTEM32 folder. it seemed to be a copy of my WINNT.SIF with some modifications. after an M2 installtion, i noticed it had the OemInfFiles entries added to it, while an M1 installation didn't. i decided to add these entries into WINNT.SIF myself and give M1 another try since it was the only working cd-boot installation method. so i proceeded with the install, and it went through without a problem. SUCCESS! 
|
|
|
|
|
Jul 19 2005, 10:37 PM
Post
#6
|
|
|
Member Group: Members Posts: 228 Joined: 8-December 03 Member No.: 10619 |
QUOTE (PhreeZ @ Jul 19 2005, 02:43 PM) @Bâshrat the Sneaky: i believe the driver installation is only forced only if there is a compatible HWID. looking at the first few lines of setupapi.log, setup seems to first identify the device HWID, then searches available .INFs for a match. line #I319 is the point in setup where the windows drivers are ignored and the drivers in OEMDIR are installed. i haven't verified it, but i assume that if the OEMDIR drivers are older than the windows drivers, OEMDIR drivers won't be installed. i came across this method while i was trying to get NF4 x64 RAID drivers integrated into an unattended x64 installation. i always inspected the logs (especially setupapi) in the windows root after installations, to try and figure out why it would fail. i started off trying METHOD1 then METHOD2. METHOD1 always blue screened and i could never get METHOD2 to work from a cd-boot installation. there would always be the OEMDISK.C/ERROR (18). eventually, i gave a network installation using METHOD2 a try and it worked. i later modified the installation with an HDD-boot and source files from CD. i stayed with this method for a while. one day, i decided to figure out why METHOD2 would work and METHOD1 wouldn't. setupapi.log gave the answer. with M1, the NVIDIA NForce Storage Controller was not being installed during GUIMODE. since the driver was not WHQL certified, setup prioritized the installation of its own Standard Dual Channel PCI IDE Controller. however, M2 seemed to be forcing the installation somehow, evident in line #I319. i did more snooping and noticed $WINNT$.INF in the SYSTEM32 folder. it seemed to be a copy of my WINNT.SIF with some modifications. after an M2 installtion, i noticed it had the OemInfFiles entries added to it, while an M1 installation didn't. i decided to add these entries into WINNT.SIF myself and give M1 another try since it was the only working cd-boot installation method. so i proceeded with the install, and it went through without a problem. SUCCESS! Dont meen to interupt.. But very interesting the change to $WINNT$.INF in one method and not the other. I knew$WINNT$.INF was created for quite some time now.. When you do a normal (not unattended) install this is where some other settings normally seen in winnt.sif for an unattended install. I have actually had hopes of trying to make a program to directly alter $WINNT$.INF instead of winnt.sif so that I could use the folders created during the dos (blue) portion of setup on a PE cd instead of having to run the dos style portion of setup to get them on the drive. So, I could copy these folders to a cd with a copy of PE. . Boot PE and use it to make changes to $WINNT$.INF and copy to target harddrive of windows install. (Would also need to copy boot loader and use some tool to modify boot sector if it was a brand new drive) Restart and pull PE cd out and let it start/continue setup from the GUI portion. I have read about some of the first Longhrn alphas and I think this is pretty much how they installed. The disk image (if you want to call it that) that setup copied contained similair files to what are on your hd after the dos style portion of setup in XP. |
|
|
|
|
Jul 20 2005, 09:16 PM
Post
#7
|
|
|
Newbie Group: Members Posts: 38 Joined: 21-May 05 Member No.: 57044
|
@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. This post has been edited by PhreeZ: Jul 20 2005, 09:17 PM |
|
|
|
|
Jul 21 2005, 12:46 AM
Post
#8
|
|
|
Member Group: Members Posts: 228 Joined: 8-December 03 Member No.: 10619 |
My intention was to find a way to skip seeing the "floppy-boot install" or the blue/white low graphics section of the install all together. I have not stopeed and taken the time to work on this yet but hopefully will sometime soon.
|
|
|
|
|
Jul 21 2005, 03:36 PM
Post
#9
|
|
|
MSFN Expert Group: Members Posts: 1118 Joined: 28-June 04 From: Eerbeek Member No.: 23554 OS: XP Home 
|
This might just work for custom monitor drivers for example.
Using the SetupCopyOEMINf utility the setup inf's are passed to the Windows\Inf directory in alphabetical order. So I install my custom Acer monitor driver so: Thanks to the A it comes first, so Windows will copy the inf to oem0.inf Now I could use CODE [OemInfFiles] OemDriverFlags=1 OemInfName="oem0.inf" To force installation of the monitor inf Let's find out. |
|
|
|
|
Jul 25 2005, 04:57 PM
Post
#10
|
|
|
Newbie Group: Members Posts: 38 Joined: 21-May 05 Member No.: 57044
|
@bilemke:
i am curious as to why you want to skip TEXTMODE setup.  @hp38guser: how did the monitor installation experiment go? |
|
|
|
|
Jul 25 2005, 06:14 PM
Post
#11
|
|
|
Newbie Group: Members Posts: 38 Joined: 21-May 05 Member No.: 57044
|
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. 
|
|
|
|
|
Aug 23 2005, 11:06 AM
Post
#12
|
|
|
Newbie Group: Members Posts: 38 Joined: 21-May 05 Member No.: 57044
|
i tried appending the OemDriverPathName entry with no success. the following two formats failed:
CODE OemPnPDriversPath="PATH1","PATH2" OemPnPDriversPath="PATH1;PATH2" it seems this method is limited to a single source path.
|
|
|
|
|
Aug 23 2005, 01:11 PM
Post
#13
|
|
|
Member Group: Members Posts: 228 Joined: 8-December 03 Member No.: 10619 |
QUOTE (PhreeZ @ Jul 25 2005, 04:57 PM) @bilemke: i am curious as to why you want to skip TEXTMODE setup. Sorry about the slow response.. Been busy for a while and almost foregot this thread.. Why you may ask? cause it is very slow. I can ghost the files it puts on to my hd from a ghost image on cd to my hd faster then it can do it. I tried this from PE once and it is much faster for me. This post has been edited by bilemke: Aug 23 2005, 01:12 PM |
|
|
|
|
Aug 21 2006, 08:43 AM
Post
#14
|
|
|
OCMania.com Group: Members Posts: 542 Joined: 19-July 05 From: Penang Malaysia Member No.: 65099 OS: XP Pro x86 
|