Search options (Page 7 of 11)

anyone able to fix this? its my main bugbear at the moment - even manually trying to install the driver I end up with a yellow exclam.

actually even though it says it worked and to reboot , it doesn't work still (only just realised as it doesnt moan on restart its got a problem)

I have had this issue with a D dir being kept, I (think) it relates to how it 'finishes'... prompting for a driver with hardware wizard, or telling you new devices are installed and it needs a reboot, or just installing everything. I say this because I seem to recall using the same image on different systems, some kept D and others didnt, all other things being equal this indicated it was relating to their hardware differences. At the time I was trying to fix other problems so unfortunately didn't really look into it.

In regards to your other question, if the .exe is terminated it will have moved D (it cant move anything if its not running). I think it moves D last too (the setupapilog shows it looking at the drivers in c:\D not in the KTD location)
Where is the finisher running from and where is your script running from?

Hi Helmi,
that isnt an option I am afraid, feel free to delete everything in this thread from me

i only seem to have options 'report', 'edit' and 'quote' unless I am being blind (which is quite possible)

Mr Smartpants,
My test rig (vmware) is up to date with everything, patched with latest Autopatcher and also windows updates.
If anyone else can see if they get e001 rankings and dont have issues at least I know the issue lies with me?

Also I was mislead about my 'patched' sfc_os.dll file in above post, I had downloaded, it turned out to be same as original, from
http://www3.sympatico.ca/lazimute/patches.htm
link title  'An already patched and compressed SFC_OS.DLL is available for download.'

I have just now patched an original winxp SP2 .dll myself, copied it to system32 and system32\dllcache and changed the SFC reg entry.  I shall test it on Monday at work.

all the packs download links end pag=
...and appears to be missing value of the 'pag' variable

This was using the Fragbert modified driverpack for modem (DP_Modem_wnt5_x86-32_702mod.7z) and worked silently

[2007/07/30 09:52:56 472.111 Driver Install]
#-019 Searching for hardware ID(s): hdaudio\func_02&ven_14f1&dev_2bfa&subsys_14f100c3&rev_0900,hdaudio\func_02&ven_14f1&dev_2bfa&subsys_14f100c3
#-018 Searching for compatible ID(s): hdaudio\func_02&ven_14f1&dev_2bfa&rev_0900,hdaudio\func_02&ven_14f1&dev_2bfa,hdaudio\func_02&ven_14f1,hdaudio\func_02
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA&SUBSYS_14F100C3" in C:\WINDOWS\Inf\oem1492.inf; Device: "Conexant HDA D110 MDC V.92 Modem"; Driver: "Conexant HDA D110 MDC V.92 Modem"; Provider: "Conexant"; Mfg: "Conexant"; Section name: "ModemX".
#I023 Actual install section: [ModemX.NT]. Rank: 0x00000001. Effective driver date: 12/02/2005.
#I022 Found "HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA" in C:\WINDOWS\Inf\oem1489.inf; Device: "HDAUDIO Soft Data Fax Modem with SmartCP"; Driver: "HDAUDIO Soft Data Fax Modem with SmartCP"; Provider: "CXT"; Mfg: "CXT"; Section name: "ModemX".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001.
#I023 Actual install section: [ModemX.NT]. Rank: 0x0000a001. Effective driver date: 02/10/2006.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ModemX] in "c:\windows\inf\oem1492.inf".
#I320 Class GUID of device remains: {4D36E96D-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA&SUBSYS_14F100C3&REV_0900\4&277104FA&0&0102".
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [ModemX.NT.Interfaces] from "c:\windows\inf\oem1492.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA&SUBSYS_14F100C3&REV_0900\4&277104FA&0&0102".
#I121 Device install of "HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA&SUBSYS_14F100C3&REV_0900\4&277104FA&0&0102" finished successfully.

Note this driver got ranked 0x0001, perfect.
[Matched a device's hardware ID with the hardware ID in an INF Models section. A rank N match means that the device's N+1 hardware ID matched the INF hardware ID]

-----------------------------------------------------

However below was next day using latest modem pack....

[2007/07/31 10:45:06 892.9 Driver Install]
#-019 Searching for hardware ID(s): hdaudio\func_02&ven_14f1&dev_2bfa&subsys_14f100c3&rev_0900,hdaudio\func_02&ven_14f1&dev_2bfa&subsys_14f100c3
#-018 Searching for compatible ID(s): hdaudio\func_02&ven_14f1&dev_2bfa&rev_0900,hdaudio\func_02&ven_14f1&dev_2bfa,hdaudio\func_02&ven_14f1,hdaudio\func_02
#-198 Command line processed: C:\WINDOWS\system32\services.exe
#I022 Found "HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA" in C:\WINDOWS\Inf\oem1487.inf; Device: "HDAUDIO Soft Data Fax Modem with SmartCP"; Driver: "HDAUDIO Soft Data Fax Modem with SmartCP"; Provider: "CXT"; Mfg: "CXT"; Section name: "ModemX".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001.
#I023 Actual install section: [ModemX.NT]. Rank: 0x0000a001. Effective driver date: 02/10/2006.
#I022 Found "HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA" in C:\WINDOWS\DriverPacks\D\3\M\C\12\pdazlcmpk.inf; Device: "HDAUDIO Soft Data Fax Modem with SmartCP"; Driver: "HDAUDIO Soft Data Fax Modem with SmartCP"; Provider: "CXT"; Mfg: "CXT"; Section name: "ModemX".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000a001.
#I023 Actual install section: [ModemX.NT]. Rank: 0x0000a001. Effective driver date: 02/10/2006.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [ModemX] in "c:\windows\inf\oem1487.inf".
#I320 Class GUID of device remains: {4D36E96D-E325-11CE-BFC1-08002BE10318}.
#I060 Set selected driver.
#I058 Selected best compatible driver.
#-166 Device install function: DIF_INSTALLDEVICEFILES.
#I124 Doing copy-only install of "HDAUDIO\FUNC_02&VEN_14F1&DEV_2BFA&SUBSYS_14F100C3&REV_0900\4&277104FA&0&0102".
#-011 Installing section [ModemX.NT] from "c:\windows\inf\oem1487.inf".
#E358 An unsigned or incorrectly signed file "c:\windows\inf\oem1487.inf" for driver "HDAUDIO Soft Data Fax Modem with SmartCP" blocked (server install). Error 1168: Element not found.
#E122 Device install failed. Error 1168: Element not found.
#E157 Default installer failed. Error 1168: Element not found.

Now because the precise driver is missing, and the other driver is getting bumped down into the untrusted range rank 0xa001, its not automatically installing and I get a 'new HW wizard' thing up at the end of it all.
However manually clicking search and so forth, it does install it fine using this driver....(this appears to be same issue with graphics drivers I am having a nightmare with at present, if anyone has looked in graphics pack thread)

It appears when rank gets bumped down to  0xE001, default windows behaviour is that it won't automatically install [and gives the 'Element not found' errors]. Then as a result of this, get the HW Wizard popups after its all done.
Seems to becoming more and more of a problem with newer and newer Driverpacks? I seem to be basically having this issue with almost all graphics drivers on any machine(All Dell, laptops and pcs)...to the point where I am wondering if its something inherantly wrong with something or somehting I am doing?
Does anyone have things install ok even with a ranking below 0x3FFF ??

rigid: same issue with D820's too, ive posted lots of logs of failing-to-detect- devices
Tiger: they do, see here http://www1.euro.dell.com/content/produ … &s=bsd

[in vmware workstation v6, created on acpi uniprocessor HAL and dropped to Standard HAL]
devpath  > makepnf > roe > sysprep -bmsd > sysprep > ghost to image
ghost from image > finisher on RunOnceEx with KTD of everything

(1) immediately prior to finsher running in RunOnceEx I clean the devicepath key [as finisher doesnt remove entries from initial devpath]
(2)KTD paths to each pack specified so dont get the double 'D' bug on KTD

It is pretty much the method as posted by skinlayers, only difference is way I clean the devicepath (I run devpath on an empty dir) and I add some extra drivers o nthe fly to the SysprepMassStorage section of sysprep.inf

I think that would be a good idea, however as the finisher is running in the same fashion, and all other things being equal, I cannot see how the problems are connected to sysprep?
Most everything seems to boil down to drivers not installing because their ranking is too low?  [I am summising this because with the HW wizard they are found and installed ok]