Topic: Various issues, please help (lengthy post, but please read)

Using latest DriverPacks (6.12) with a RIS image.

1. Trying to install a HP NC8430. The client installs ok, but several devices are incorrectly detected or installed (exclamation mark in Device Manager):

* Audio Device on High Definition Audio Bus (integrated ADI SoundMax HD audio card. Found in sp32593.exe from support.hp.com)
* HP Integrated Module (Bluetooth, found in sp32315 from support.hp.com)
* Mass Storage Controller (Texas Instruments SD reader, found in sp33416.exe from support.hp.com)
* PCI Simple Communications Controller (Agere modem, found in sp32644.exe from support.hp.com)
* 3 Unknown devices (no idea what these are, but dev-ids are ACPI\HPQ0004\3&B1BFB68&0, ACPI\HPQ0006\2&DABA3FF&0 and ACPI\IFX0102\4&28738126&0)

Below are contents of DpFnshr.log:

2006-12-22 13:20:37 : <INIT> DriverPacks Finisher 6.10 initialized.
2006-12-22 13:20:37 : <INIT> Splash screen disabled.
2006-12-22 13:20:37 : <INIT> Detected platform wnt5_x86-32.
2006-12-22 13:20:37 : <INIT> Start logging of the HWIDs for relevant devices present in this system.
2006-12-22 13:20:37 : <INIT> 1. ACPI devices

ACPI\ACPI0003\2&DABA3FF&0                                   : Microsoft AC Adapter
ACPI\FIXEDBUTTON\2&DABA3FF&0                                : ACPI Fixed Feature Button
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_14\_0                : Genuine Intel(R) CPU           T2500  @ 2.00GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_14\_1                : Genuine Intel(R) CPU           T2500  @ 2.00GHz
ACPI\HPQ0004\3&B1BFB68&0
ACPI\HPQ0006\2&DABA3FF&0
ACPI\IFX0102\4&28738126&0
ACPI\PNP0000\4&28738126&0                                   : Programmable interrupt controller
ACPI\PNP0100\4&28738126&0                                   : System timer
ACPI\PNP0200\4&28738126&0                                   : Direct memory access controller
ACPI\PNP0303\4&28738126&0                                   : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0401\5&1E8DC1E5&0                                   : ECP Printer Port (LPT1)
ACPI\PNP0501\5&1E8DC1E5&0                                   : Communications Port (COM1)
ACPI\PNP0800\4&28738126&0                                   : System speaker
ACPI\PNP0A06\4&28738126&0                                   : Extended IO Bus
ACPI\PNP0A08\2&DABA3FF&0                                    : PCI bus
ACPI\PNP0B00\4&28738126&0                                   : System CMOS/real time clock
ACPI\PNP0C01\2&DABA3FF&0                                    : System board
ACPI\PNP0C02\0                                              : Motherboard resources
ACPI\PNP0C02\1                                              : Motherboard resources
ACPI\PNP0C02\2                                              : Motherboard resources
ACPI\PNP0C04\4&28738126&0                                   : Numeric data processor
ACPI\PNP0C09\4&28738126&0                                   : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0A\2                                              : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0B\0                                              : ACPI Fan
ACPI\PNP0C0B\1                                              : ACPI Fan
ACPI\PNP0C0B\2                                              : ACPI Fan
ACPI\PNP0C0B\3                                              : ACPI Fan
ACPI\PNP0C0B\4                                              : ACPI Fan
ACPI\PNP0C0B\5                                              : ACPI Fan
ACPI\PNP0C0B\6                                              : ACPI Fan
ACPI\PNP0C0D\2&DABA3FF&0                                    : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0                                    : ACPI Sleep Button
ACPI\PNP0C14\0                                              : Microsoft Windows Management Interface for ACPI
ACPI\SYN010E\4&28738126&0                                   : PS/2 Compatible Mouse
ACPI\THERMALZONE\TZ0_                                       : ACPI Thermal Zone
ACPI\THERMALZONE\TZ1_                                       : ACPI Thermal Zone
ACPI\THERMALZONE\TZ2_                                       : ACPI Thermal Zone
ACPI\THERMALZONE\TZ3_                                       : ACPI Thermal Zone
ACPI\THERMALZONE\TZ4_                                       : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0                                          : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000                                          : ACPI Multiprocessor PC
43 matching device(s) found.

2006-12-22 13:20:37 : <INIT> 2. PCI devices

PCI\VEN_1002&DEV_71C5&SUBSYS_30A3103C&REV_00\4&31B7BFB9&0&0008: ATI Mobility Radeon X1600
PCI\VEN_104C&DEV_8039&SUBSYS_30A3103C&REV_00\4&2EC23395&0&30F0: Generic CardBus Controller
PCI\VEN_104C&DEV_803A&SUBSYS_30A3103C&REV_00\4&2EC23395&0&31F0: Texas Instruments OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_104C&DEV_803B&SUBSYS_30A3103C&REV_00\4&2EC23395&0&32F0: Texas Instruments PCIxx12 Integrated FlashMedia Controller
PCI\VEN_104C&DEV_803C&SUBSYS_30A3103C&REV_00\4&2EC23395&0&33F0: SDA Standard Compliant SD Host Controller
PCI\VEN_104C&DEV_803D&SUBSYS_30A3103C&REV_00\4&2EC23395&0&34F0: Texas Instruments PCI GemCore based SmartCard controller
PCI\VEN_14E4&DEV_16FD&SUBSYS_30A3103C&REV_21\4&BF41672&0&00E0: Broadcom NetXtreme Gigabit Ethernet
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_E1\3&B1BFB68&0&F0 : Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_27A0&SUBSYS_00000000&REV_03\3&B1BFB68&0&00 : PCI standard host CPU bridge
PCI\VEN_8086&DEV_27A1&SUBSYS_00000000&REV_03\3&B1BFB68&0&08 : PCI standard PCI-to-PCI bridge
PCI\VEN_8086&DEV_27B9&SUBSYS_00000000&REV_01\3&B1BFB68&0&F8 : PCI standard ISA bridge
PCI\VEN_8086&DEV_27C4&SUBSYS_30A3103C&REV_01\3&B1BFB68&0&FA : Standard Dual Channel PCI IDE Controller
PCI\VEN_8086&DEV_27C8&SUBSYS_30A3103C&REV_01\3&B1BFB68&0&E8 : Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_27C9&SUBSYS_30A3103C&REV_01\3&B1BFB68&0&E9 : Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_27CA&SUBSYS_30A3103C&REV_01\3&B1BFB68&0&EA : Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_27CB&SUBSYS_30A3103C&REV_01\3&B1BFB68&0&EB : Standard Universal PCI to USB Host Controller
PCI\VEN_8086&DEV_27CC&SUBSYS_30A3103C&REV_01\3&B1BFB68&0&EF : Standard Enhanced PCI to USB Host Controller
PCI\VEN_8086&DEV_27D0&SUBSYS_00000000&REV_01\3&B1BFB68&0&E0 : PCI standard PCI-to-PCI bridge
PCI\VEN_8086&DEV_27D2&SUBSYS_00000000&REV_01\3&B1BFB68&0&E1 : PCI standard PCI-to-PCI bridge
PCI\VEN_8086&DEV_27D6&SUBSYS_00000000&REV_01\3&B1BFB68&0&E3 : PCI standard PCI-to-PCI bridge
PCI\VEN_8086&DEV_27D8&SUBSYS_30A3103C&REV_01\3&B1BFB68&0&D8 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_4222&SUBSYS_135C103C&REV_02\4&4878531&0&00E1: Intel(R) PRO/Wireless 3945ABG Network Connection
22 matching device(s) found.

2006-12-22 13:20:37 : <INIT> 3. HDAUDIO devices

HDAUDIO\FUNC_01&VEN_11D4&DEV_1981&SUBSYS_103C30A3&REV_1002\4&1B4B6C16&0&0001: SoundMAX Integrated Digital HD Audio
HDAUDIO\FUNC_02&VEN_11C1&DEV_3026&SUBSYS_103C30A3&REV_1007\4&1B4B6C16&0&0101: Agere Systems HDA Modem
2 matching device(s) found.

2006-12-22 13:20:37 : <INIT> 4. USB devices

USB\ROOT_HUB\4&193F3BB0&0                                   : USB Root Hub
USB\ROOT_HUB\4&30CC89FB&0                                   : USB Root Hub
USB\ROOT_HUB\4&33E5B70E&0                                   : USB Root Hub
USB\ROOT_HUB\4&AD8EF39&0                                    : USB Root Hub
USB\ROOT_HUB20\4&2A3AF5A3&0                                 : USB Root Hub
USB\VID_03F0&PID_171D\5&343AC587&0&1                        : HP Integrated Module with Bluetooth 2.0 Wireless Technology
USB\VID_046D&PID_C01D\6&EAAA50F&0&3                         : USB Human Interface Device
USB\VID_04B4&PID_6560\5&2E1C9B8C&0&8                        : Generic USB Hub
8 matching device(s) found.

2006-12-22 13:20:37 : <INIT> Logging of HWIDs complete.
2006-12-22 13:20:38 : <INIT> Processed settings.
2006-12-22 13:20:38 : <INIT> Detected a method 2 driver installation, the DevicePath value in the registry has been reset.
2006-12-22 13:20:38 : <FLTR> Collected the HWIDs for this system.
2006-12-22 13:20:38 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0002__D-G-A-1] (1 of 20 exceptions).
2006-12-22 13:20:38 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:38 : <FLTR> 		Found tagfile "C:\ATICCC.ins" (1/2).
2006-12-22 13:20:38 : <FLTR> 		Found tagfile "C:\D\G\A\1\ATICCC.exe" (2/2).
2006-12-22 13:20:38 : <FLTR> 	4. +infFiles (ANY +infFiles must be matched)
2006-12-22 13:20:38 : <FLTR> 		Wildcard specified for +infFiles requirement: scan for .inf files (1 of 1 +infFiles).
2006-12-22 13:20:38 : <FLTR> 		Checking .inf file "C:\D\G\A\1\C2_38463.inf".
2006-12-22 13:20:41 : <FLTR> 		Checking .inf file "C:\D\G\A\1\CX_38463.inf".
2006-12-22 13:20:44 : <FLTR> 		Checking .inf file "C:\D\G\A\1\CX_38465.inf".
2006-12-22 13:20:44 : <FLTR> 		Matched +infFile"C:\D\G\A\1\CX_38465.inf" through the HWID "PCI\VEN_1002&DEV_71C5" (original HWID: "PCI\VEN_1002&DEV_71C5&SUBSYS_30A3103C&REV_00").
2006-12-22 13:20:44 : <FLTR> 	=> All requirements for exception [wnt5_x86-32__0002__D-G-A-1] have been met!
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0003__D-G-A-1] (2 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\ATICCP.ins" (1 of 2 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0004__D-G-A-2] (3 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		Found tagfile "C:\D\G\A\2\CPanel.exe" (1/1).
2006-12-22 13:20:44 : <FLTR> 	4. +infFiles (ANY +infFiles must be matched)
2006-12-22 13:20:44 : <FLTR> 		! Could not match any of the +infFiles.
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0005__D-G-A-5] (4 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\ATICCP.ins" (1 of 2 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0006__D-G-A-5] (5 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		Found tagfile "C:\ATICCC.ins" (1/2).
2006-12-22 13:20:44 : <FLTR> 		Found tagfile "C:\D\G\A\1\ATICCC.exe" (2/2).
2006-12-22 13:20:44 : <FLTR> 	4. +infFiles (ANY +infFiles must be matched)
2006-12-22 13:20:44 : <FLTR> 		! Could not match any of the +infFiles.
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0007__D-G-3-1] (6 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\3dfxV2ps.dll" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0009__D-S-CR-1] (7 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\ha20x2k.sys" (1 of 2 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0010__D-S-CR-2] (8 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\ha10kx2k.sys" (1 of 3 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0011__D-S-CR-3] (9 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\P17.sys" (1 of 2 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0012__D-S-H-2] (10 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	4. +infFiles (ANY +infFiles must be matched)
2006-12-22 13:20:44 : <FLTR> 		! Could not match any of the +infFiles.
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0013__D-S-N] (11 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\nvapu.sys" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0014__D-S-S-U] (12 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\sthda.sys" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0015__D-S-SI-1] (13 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\sis7012.sys" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0016__D-S-SI-2] (14 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\sis7018.sys" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0017__D-S-T-2] (15 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\FM801.sys" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0018__D-S-T-3] (16 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\cmaudio.sys" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0019__D-S-T-4] (17 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\TT1724ht.sys" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0020__D-S-T-5] (18 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\dmxsens.sys" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0021__D-S-V-1] (19 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\envysens.sys" (1 of 1 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Verifying requirements for exception [wnt5_x86-32__0022__D-S-V-2] (20 of 20 exceptions).
2006-12-22 13:20:44 : <FLTR> 	1. tagFiles (ALL tagFiles must be found)
2006-12-22 13:20:44 : <FLTR> 		! Could not find tagfile "C:\WINDOWS\system32\drivers\vinyl97.sys" (1 of 2 tagfiles).
2006-12-22 13:20:44 : <FLTR> 	=> This exception will not be applied.
2006-12-22 13:20:44 : <FLTR> Finished filtering exceptions.
2006-12-22 13:20:44 : <EXEC> Executing all commands (6) for exception [wnt5_x86-32__0002__D-G-A-1].
2006-12-22 13:20:44 : <EXEC> 	Executing command 1 of 6: "%DPSROOT%\D\G\A\1\ATICCC.exe -y -o%DPSTMP%"
2006-12-22 13:20:54 : <EXEC> 		No STDOUT output occurred.
2006-12-22 13:20:54 : <EXEC> 	Executing command 2 of 6: "msiexec /i %DPSTMP%\ISScript9.Msi /qn /norestart"
2006-12-22 13:21:14 : <EXEC> 		No STDOUT output occurred.
2006-12-22 13:21:14 : <EXEC> 	Executing command 3 of 6: "?processWaitClose:ISScript9.Msi"
2006-12-22 13:21:15 : <EXEC> 		Custom DriverPacks Finisher command "?processWaitClose" waited 0.3 seconds for the process "ISScript9.Msi".
2006-12-22 13:21:15 : <EXEC> 	Executing command 4 of 6: "msiexec /i %DPSTMP%\ATICCC.msi /qn /norestart"
2006-12-22 13:21:37 : <EXEC> 		No STDOUT output occurred.
2006-12-22 13:21:37 : <EXEC> 	Executing command 5 of 6: "?processWaitClose:ATICCC.msi"
2006-12-22 13:21:37 : <EXEC> 		Custom DriverPacks Finisher command "?processWaitClose" waited 0.3 seconds for the process "ATICCC.msi".
2006-12-22 13:21:37 : <EXEC> 	Executing command 6 of 6: "rd /s /q %DPSTMP%"
2006-12-22 13:21:37 : <EXEC> 		No STDOUT output occurred.
2006-12-22 13:21:37 : <KTD>  KTD cache location set: "C:\D".
2006-12-22 13:21:37 : <KTD>  KTD is enabled, in PATHS mode.
2006-12-22 13:21:37 : <KTD>  Move drivers inside "C:\D" to "C:\D\D".
2006-12-22 13:21:37 : <KTD>  Successfully created the "%KTD%" environment variable, it has been set to "C:\D". It will be available after the next reboot.
2006-12-22 13:21:41 : <KTD>  Successfully updated the DevicePath registry value!
2006-12-22 13:26:24 : <KTD>  Successfully created the .pnf files. KTD has been applied! It will be available after the next reboot.
2006-12-22 13:28:48 : <CLNP> Deleted the DriverPacks, which were located in "C:\D".
2006-12-22 13:28:48 : <CLNP> Deleted "C:\hwids.dat"!
2006-12-22 13:28:48 : <CLNP> Deleted "C:\DPsFnshr.ini"!
2006-12-22 13:28:48 : <CLNP> Deleted "C:\devcon.exe"!
2006-12-22 13:28:48 : <CLNP> Deleted "C:\makePNF.exe"!
2006-12-22 13:28:48 : <CLNP> Deleted "C:\pmtimer.exe"!
2006-12-22 13:28:48 : <CLNP> Deleted "C:\ATICCC.ins"!
2006-12-22 13:28:48 : <CLNP> Deleted "C:\DSPdsblr.exe"!
2006-12-22 13:28:48 : <CLNP> Added new value to the RunOnce key in the registry: the DriverPacks Finisher itself will get deleted after the next reboot.
2006-12-22 13:28:48 : Program terminated.

2. After first login, a notepad pops up with a text file named "desktop", containing [.ShellClassInfo] LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787. Also, an error message saying "CLI.EXE - application error - the application failed to initialize properly (0xc0000135)." This seems to have something to do with the graphics card?

3. Is it possible to also suppress the "Driver Signing Policy Disabler" splash screen / status image, not just the generic splash screen?

4. Is the source code for DevPath.exe, DpFnshr.exe as well as any other compiled customizations or utilities (i.e driver signing policy disabler) available?

5. KTD is not enabled, even though properly set in settings (see log file, C:\D does not exist).

Last edited by rumour (2006-12-23 00:28:12)

Re: Various issues, please help (lengthy post, but please read)

rumour wrote:

Using latest DriverPacks (6.12) with a RIS image.

1. Trying to install a HP NC8430. The client installs ok, but several devices are incorrectly detected or installed (exclamation mark in Device Manager):

* Audio Device on High Definition Audio Bus (integrated ADI SoundMax HD audio card. Found in sp32593.exe from support.hp.com)
* HP Integrated Module (Bluetooth, found in sp32315 from support.hp.com)
* Mass Storage Controller (Texas Instruments SD reader, found in sp33416.exe from support.hp.com)
* PCI Simple Communications Controller (Agere modem, found in sp32644.exe from support.hp.com)
* 3 Unknown devices (no idea what these are, but dev-ids are ACPI\HPQ0004\3&B1BFB68&0, ACPI\HPQ0006\2&DABA3FF&0 and ACPI\IFX0102\4&28738126&0)

Please check whether these devices are actually supported by the DriverPacks.
If not, I suggest you post a [REQUEST] thread about each of them in the approriate subforum with a link to the driver file so that it can be included in the next version.

2. After first login, a notepad pops up with a text file named "desktop", containing [.ShellClassInfo] LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787.

I got that once myself but never found out the cause.
It is still a mystery for us.
Hasn't happened again on me for some time, though.

Also, an error message saying "CLI.EXE - application error - the application failed to initialize properly (0xc0000135)." This seems to have something to do with the graphics card?

Quite correct that is ATi's CCC trying to launch.
Do you have .NET FW slipstreamed?
If not, it is a requirement for CCC to run.
Either rely on the CP or slipstream it into your CD/DVD.

5. KTD is not enabled, even though properly set in settings (see log file, C:\D does not exist).

The default path for KTD is %Systemdir%/DriverPacks, which is ususally C:/Windows/DriverPacks on a default path.
Have a look for them there, I'm sure you will find them wink

Re: Various issues, please help (lengthy post, but please read)

hi

did you run DPs_base while there was a winnt.sif of your own in 386 folder?

The answer was 42?
Kind regards, Jaak.

Re: Various issues, please help (lengthy post, but please read)

the other question
donators, testers, translators and coders have been able to look at source files since this went open source.
I think devpath is by M$, so you would not find the source for that.

are you an AUTOIT user?

The answer was 42?
Kind regards, Jaak.

Re: Various issues, please help (lengthy post, but please read)

Isnt microsoft open source tongue

Re: Various issues, please help (lengthy post, but please read)

Helmi wrote:
rumour wrote:

Using latest DriverPacks (6.12) with a RIS image.

1. Trying to install a HP NC8430. The client installs ok, but several devices are incorrectly detected or installed (exclamation mark in Device Manager):

* Audio Device on High Definition Audio Bus (integrated ADI SoundMax HD audio card. Found in sp32593.exe from support.hp.com)
* HP Integrated Module (Bluetooth, found in sp32315 from support.hp.com)
* Mass Storage Controller (Texas Instruments SD reader, found in sp33416.exe from support.hp.com)
* PCI Simple Communications Controller (Agere modem, found in sp32644.exe from support.hp.com)
* 3 Unknown devices (no idea what these are, but dev-ids are ACPI\HPQ0004\3&B1BFB68&0, ACPI\HPQ0006\2&DABA3FF&0 and ACPI\IFX0102\4&28738126&0)

Please check whether these devices are actually supported by the DriverPacks.
If not, I suggest you post a [REQUEST] thread about each of them in the approriate subforum with a link to the driver file so that it can be included in the next version.

Found these after some searching. One is the TPM encryption chip driver, another is HP Quick Launch Buttons. I will post a request later. What I found strange though, was that all devices (except the three listed as "Unknown") seemed to be properly identified and matched judging by DPFnshr.log, yet they were incorrectly installed.

2. After first login, a notepad pops up with a text file named "desktop", containing [.ShellClassInfo] LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787.

I got that once myself but never found out the cause.
It is still a mystery for us.
Hasn't happened again on me for some time, though.

Strangely, it only seems to pop up when I log on as a local administrator. Logging on to a domain does not produce this error.

Also, an error message saying "CLI.EXE - application error - the application failed to initialize properly (0xc0000135)." This seems to have something to do with the graphics card?

Quite correct that is ATi's CCC trying to launch.
Do you have .NET FW slipstreamed?
If not, it is a requirement for CCC to run.
Either rely on the CP or slipstream it into your CD/DVD.

Did not know about the .Net FW requirement. Works pretty now, thanks. smile

5. KTD is not enabled, even though properly set in settings (see log file, C:\D does not exist).

The default path for KTD is %Systemdir%/DriverPacks, which is ususally C:/Windows/DriverPacks on a default path.
Have a look for them there, I'm sure you will find them wink

Actually, no. As per posted log file:

2006-12-22 13:21:37 : <KTD>  KTD cache location set: "C:\D".
2006-12-22 13:21:37 : <KTD>  KTD is enabled, in PATHS mode.
2006-12-22 13:21:37 : <KTD>  Move drivers inside "C:\D" to "C:\D\D".

The C:\D folder does noe exist. Neither are the DriverPacks located in %SystemDir%DriverPacks.

One question I'm still wondering about is whether or not the Driver Signing Policy Disabler splash screen can be suppressed/disabled.

Re: Various issues, please help (lengthy post, but please read)

jtdoom wrote:

the other question
donators, testers, translators and coders have been able to look at source files since this went open source.
I think devpath is by M$, so you would not find the source for that.

are you an AUTOIT user?

Yes, I am an AutoIT user. No, there wasn't a custom .sif in the folder. smile

Googling for devpath.exe only produces hits from these (and similar) forums, som I'm not sure if it is an MS util.

Re: Various issues, please help (lengthy post, but please read)

rumour wrote:

Actually, no. As per posted log file:

2006-12-22 13:21:37 : <KTD>  KTD cache location set: "C:\D".
2006-12-22 13:21:37 : <KTD>  KTD is enabled, in PATHS mode.
2006-12-22 13:21:37 : <KTD>  Move drivers inside "C:\D" to "C:\D\D".

The C:\D folder does noe exist. Neither are the DriverPacks located in %SystemDir%DriverPacks.

The C:\D\ is merely the temporary directory for the first extraction.
If you have KTD enabled, they will be moved out of this dir to their final destination.
If it's disabled it will get deleted.

Please check your KTD settings again, the default is disabled.
If you enable it, also check the path.
Default is %SystemDir%\DriverPacks, and it has always worked for me.