Re: Testers needed for new Graphics driverpacks
firstly the sysprep -bdsm didnt have any effect on anything so ignore that theory
Re: Testers needed for new Graphics driverpacks
secondly i decided i'd make my own driverpack B addon with other drivers from Dell, and this perhaps unsurprisingly, solved the problem.
I made extra 8,9,10,11,12 under the D\G\I with the contents of
R79733.exe R96000.exe R126541.exe R126990.exe and R126991.exe (not in that order though) - these being the graphics drivers for Dell GX260,GX270 and GX280 onboard Intel embedded graphics. Below is the outcome for the graphics detection.
[2002/09/24 00:31:28 480.223 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_8086&dev_2562&subsys_01261028&rev_01,pci\ven_8086&dev_2562&subsys_01261028,pci\ven_8086&dev_2562&cc_030000,pci\ven_8086&dev_2562&cc_0300
#-018 Searching for compatible ID(s): pci\ven_8086&dev_2562&rev_01,pci\ven_8086&dev_2562,pci\ven_8086&cc_030000,pci\ven_8086&cc_0300,pci\ven_8086,pci\cc_030000,pci\cc_0300
#-198 Command line processed: C:\WINDOWS\system32\services.exe -setup
#I393 Modified INF cache "C:\WINDOWS\Inf\INFCACHE.1".
#I022 Found "PCI\VEN_8086&DEV_2562&SUBSYS_01261028" in c:\D\G\I\10\ialmnt5.inf; Device: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Driver: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i845G".
#I023 Actual install section: [i845G]. Rank: 0x00000001. Effective driver date: 01/23/2005.
#I022 Found "PCI\VEN_8086&DEV_2562" in c:\D\G\I\12\ialmnt5.inf; Device: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Driver: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i845G".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [i845G]. Rank: 0x0000e001. Effective driver date: 03/23/2006.
#I022 Found "PCI\VEN_8086&DEV_2562&SUBSYS_01261028" in c:\D\G\I\12\ialmnt5.inf; Device: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Driver: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i845G".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x0000c001.
#I023 Actual install section: [i845G]. Rank: 0x0000c001. Effective driver date: 03/23/2006.
#I022 Found "PCI\VEN_8086&DEV_2562" in c:\D\G\I\5\ialmnt5.inf; Device: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Driver: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i845G".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [i845G]. Rank: 0x0000e001. Effective driver date: 08/20/2004.
#I022 Found "PCI\VEN_8086&DEV_2562" in c:\D\G\I\7\iegd.inf; Device: "Intel Corporation 845 Embedded Graphics Controller"; Driver: "Intel Corporation 845 Embedded Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "iegd_alm".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [iegd_alm]. Rank: 0x0000e001. Effective driver date: 06/04/2007.
#I022 Found "PCI\VEN_8086&DEV_2562&SUBSYS_01261028" in c:\D\G\I\8\ialmnt5.inf; Device: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Driver: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i845G".
#I023 Actual install section: [i845G]. Rank: 0x00000001. Effective driver date: 02/10/2004.
#I022 Found "PCI\VEN_8086&DEV_2562" in c:\D\G\I\9\ialmnt5.inf; Device: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Driver: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i845G".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [i845G]. Rank: 0x0000e001. Effective driver date: 03/23/2006.
#I022 Found "PCI\VEN_8086&DEV_2562&SUBSYS_01261028" in c:\D\G\I\9\ialmnt5.inf; Device: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Driver: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i845G".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x0000c001.
#I023 Actual install section: [i845G]. Rank: 0x0000c001. Effective driver date: 03/23/2006.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [i845G] in "c:\d\g\i\10\ialmnt5.inf".
#I320 Class GUID of device remains: {4D36E968-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 "PCI\VEN_8086&DEV_2562&SUBSYS_01261028&REV_01\2&EBB567F&0&10".
#-011 Installing section [i845G] from "c:\d\g\i\10\ialmnt5.inf".
#W313 Copy target "C:\WINDOWS\system32\igfxext.exe" is also a Delete target, forcing COPYFLG_NODECOMP.
#W313 Copy target "C:\WINDOWS\system32\igfxexps.dll" is also a Delete target, forcing COPYFLG_NODECOMP.
#-166 Device install function: DIF_REGISTER_COINSTALLERS.
#I056 Coinstallers registered.
#-166 Device install function: DIF_INSTALLINTERFACES.
#-011 Installing section [i845G.Interfaces] from "c:\d\g\i\10\ialmnt5.inf".
#I054 Interfaces installed.
#-166 Device install function: DIF_INSTALLDEVICE.
#I123 Doing full install of "PCI\VEN_8086&DEV_2562&SUBSYS_01261028&REV_01\2&EBB567F&0&10".
#I121 Device install of "PCI\VEN_8086&DEV_2562&SUBSYS_01261028&REV_01\2&EBB567F&0&10" finished successfully.
[2002/09/24 00:31:33 480.329 Driver Install]
conclusion is:
rank 0001 valid .cat and subsys
rank c001 no/invalid .cat and subsys
rank e001 no subsys and no/invalid .cat
-anything higher than 3FFFF is going to be 'Untrusted Driver Rank' and not work automatically, hence as far the Intel drivers must have original file set in them.
Last edited by chud (2007-09-05 06:10:20)
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
Did you notice if the drivers included any .cat files? My experience is 'No'. That would explain why your still getting the "Driver node not trusted" errors.
The problem with including all the Dell specific drivers is that the G_B DP would balloon in size well beyond what the average user (or the server) could handle. 
In cases like this, it's not unheard of for the user to create their own DP, as you have done, for specific (troublesome) hardware.
I myself cannot use the 3rd party Modem DP because the Motorola driver .inf overlaps my Agere modem .inf and installs the wrong driver. My solution? My own specialized modem DP.
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
Re: Testers needed for new Graphics driverpacks
Seems pointless to include Intel drivers without/invalid .cat file as they don't work?
I think 1 or 2 of the added dir's (10 and maybe 11) would pretty much cover everything Dell-wise. There are hundreds of thousands of Optiplex GX's about these would cover. I work at the NHS and as far as I know most UK hospitals use Dell (and we are third largest employer in the world) & our local council (local government) also uses them.
Alternatively is to use junction points and just have one copy of every binary identical file with links to it in the dirs? (would obviously need to be automated, maybe the DPfinisher could do it). I use a junction point quite effectively for building a BartPE cd - I have all the DP's extracted in one place and link the BartPE drivers dir to it with a hard link.
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
NHS eh? Do you work in their IT dept? I'll be retiring in two years and need a job (Adenbrookes) to keep busy. 
I'll troll the Dell website and put together a test DP of Dell drivers. Similar to what you did.
As long as the .inf points to the correct folder location, it doesn't really matter where the driver files are located.
As to the .cat files, Intel ALWAYS includes the .cat files, Dell on the other hand does so infrequently.
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
Re: Testers needed for new Graphics driverpacks
chud wrote:
I124 Doing copy-only install of "PCI\VEN_8086&DEV_2572&SUBSYS_01511028&REV_02\3&172E68DD&0&10".
#-011 Installing section [iegd_alm] from "c:\windows\inf\oem21.inf".
#E358 An unsigned or incorrectly signed file "c:\windows\inf\oem21.inf" for driver "Intel Corporation 865 Embedded Graphics Controller" blocked (server install). Error 1168: Element not found.
Cat file is missing in Intel Embedded drivers. Intel didn't include Embedded cat file.
R79733.EXE does not contain embedded drivers.
Try last test package, but remove Intel Embedded drivers.
Does graphics drivers load at Dell GX260,GX270 and GX280?
Added:
#I022 Found "PCI\VEN_8086&DEV_2562&SUBSYS_01261028" in c:\D\G\I\12\ialmnt5.inf; Device: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Driver: "Intel(R) 82845G/GL/GE/PE/GV Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i845G".
#I087 Driver node not trusted, rank changed from 0x00000001 to 0x0000c001.
Idea:
Dell edited file ialmnt5.inf, SUBSYS was added: PCI\VEN_8086&DEV_*&SUBSYS_*
However there is a old Intel default *.cat tile included. This cat file is invalid to the edited Dell ialmnt5.inf.
Therefore rank 0xc001.
However according to *.cat file date, Dell may have added a Dell *.cat file too.
How to recognice a *.cat distributer.
Last edited by cdob (2007-09-05 20:00:36)
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
cdob wrote:
Cat file is missing in Intel Embedded drivers. Intel didn't include Embedded cat file.
Try last test package, but remove Intel Embedded drivers.
Does graphics drivers load at Dell GX260,GX270 and GX280?
Good catch. I'm downloading the intel package again to look for the .cat file (it's referenced in the .inf). Odd that Intel would release the package without double checking the referenced files were included.
I agree with cdob, delete the G\I\7 folder and repackage. I think we can probably delete that folder entirely since it's meant for Linux, WinCE, and XP embedded which are not supported by the Driverpacks in general.
Hello! Intel!!! Unified driver please....please?
*Edit,
Nope, the .cat file is missing from that Intel package. I'll remove the folder and reupload a 7.09.1 nightly including some Dell drivers in a day or so.
Last edited by mr_smartepants (2007-09-05 23:17:36)
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
Re: Testers needed for new Graphics driverpacks
..
Last edited by chud (2007-09-07 22:23:02)
Re: Testers needed for new Graphics driverpacks
Hi....
Just to let you know I have tried the latest 7.09 Graphics packs and I am having a problem on Dell Optiplex GX620 and Optiplex 745 machines. I think the problem is with Graphics B 7.09. My image is XP with SP2 and RyanVM PostSP2 applied via nLite and then all the latest driverpacks applied via DPs_BASE.EXE.
During the DPSFNSHR.EXE phase, the Matrox PowerDesk SE setup/config program starts up and then half way through doing whatever it does, it complains with the following error:
Error: 1309. Error reading from file:
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\7zS17B.tmp\Program Files\Matrox Graphics Inc\PowerDesk\Services\Matrox.PowerDesk.Services.exe. Verify that the file exists and that you can access it.
......the problem is that neither of these machines have a Matrox card. Both have ATI Radeon dual head cards:
Dell Optiplex 745 has Radeon X1300/X1550 Series 256MB
Dell Optiplex GX620 has Radeon X300/X550/X1050 Series 256MB
If I click cancel, the Matrox PowerDesk program exits and DPFNSHR.EXE finishes normally. The machine then reboots and everything is fine.....the XP Device Manager correctly identifies the display adapter in both cases, the ATI Control Center icon is displayed on the tool bar near the clock and I can set any color depths, resolutions etc. I want that are supported by the display.
The DPsFNSHR.log file shows that 5 exceptions have been identified for execution and one of them is %DPSROOT%\D\G\M\1\matrox.exe. My full DPsFNSHR.log file can be viewed at http://cwbshaw.diinoweb.com/files/DPsFnshr.log. Also at the end of this post is the output from savehwids.exe.
Not sure whats causing this, but I thought I should post something on it.
HTH
Chris.
Output of savehwids.exe:
===========
PCI Devices
===========
PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00\4&FA8D773&0&0008: Radeon X1300/X1550 Series
PCI\VEN_1002&DEV_71A3&SUBSYS_0D031028&REV_00\4&FA8D773&0&0108: Radeon X1300/X1550 Series Secondary
PCI\VEN_11C1&DEV_5811&SUBSYS_80101028&REV_61\4&1B02CB0B&0&00F0: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_14E4&DEV_167A&SUBSYS_01DA1028&REV_02\4&21E4E6E0&0&00E4: Broadcom NetXtreme 57xx Gigabit Controller
PCI\VEN_8086&DEV_244E&SUBSYS_00000000&REV_F2\3&172E68DD&0&F0: Intel(R) 82801 PCI Bridge - 244E
PCI\VEN_8086&DEV_2810&SUBSYS_00000000&REV_02\3&172E68DD&0&F8: Intel(R) ICH8/ICH8R Family LPC Interface Controller - 2810
PCI\VEN_8086&DEV_2820&SUBSYS_01DA1028&REV_02\3&172E68DD&0&FA: Intel(R) ICH8 4 port Serial ATA Storage Controller - 2820
PCI\VEN_8086&DEV_2825&SUBSYS_01DA1028&REV_02\3&172E68DD&0&FD: Intel(R) ICH8 2 port Serial ATA Storage Controller - 2825
PCI\VEN_8086&DEV_2830&SUBSYS_01DA1028&REV_02\3&172E68DD&0&E8: Intel(R) ICH8 Family USB Universal Host Controller - 2830
PCI\VEN_8086&DEV_2831&SUBSYS_01DA1028&REV_02\3&172E68DD&0&E9: Intel(R) ICH8 Family USB Universal Host Controller - 2831
PCI\VEN_8086&DEV_2832&SUBSYS_01DA1028&REV_02\3&172E68DD&0&EA: Intel(R) ICH8 Family USB Universal Host Controller - 2832
PCI\VEN_8086&DEV_2834&SUBSYS_01DA1028&REV_02\3&172E68DD&0&D0: Intel(R) ICH8 Family USB Universal Host Controller - 2834
PCI\VEN_8086&DEV_2835&SUBSYS_01DA1028&REV_02\3&172E68DD&0&D1: Intel(R) ICH8 Family USB Universal Host Controller - 2835
PCI\VEN_8086&DEV_2836&SUBSYS_01DA1028&REV_02\3&172E68DD&0&EF: Intel(R) ICH8 Family USB2 Enhanced Host Controller - 2836
PCI\VEN_8086&DEV_283A&SUBSYS_01DA1028&REV_02\3&172E68DD&0&D7: Intel(R) ICH8 Family USB2 Enhanced Host Controller - 283A
PCI\VEN_8086&DEV_283E&SUBSYS_01DA1028&REV_02\3&172E68DD&0&FB: Intel(R) ICH8 Family SMBus Controller - 283E
PCI\VEN_8086&DEV_283F&SUBSYS_00000000&REV_02\3&172E68DD&0&E0: Intel(R) ICH8 Family PCI Express Root Port 1 - 283F
PCI\VEN_8086&DEV_2847&SUBSYS_00000000&REV_02\3&172E68DD&0&E4: Intel(R) ICH8 Family PCI Express Root Port 5 - 2847
PCI\VEN_8086&DEV_284B&SUBSYS_01DA1028&REV_02\3&172E68DD&0&D8: PCI Device
PCI\VEN_8086&DEV_2990&SUBSYS_00000000&REV_02\3&172E68DD&0&00: Intel(R) Q963/Q965 Processor to I/O Controller - 2990
PCI\VEN_8086&DEV_2991&SUBSYS_00000000&REV_02\3&172E68DD&0&08: Intel(R) Q963/Q965 PCI Express Root Port - 2991
21 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&1B8E453E&0 : USB Root Hub
USB\ROOT_HUB\4&2C6BE34E&0 : USB Root Hub
USB\ROOT_HUB\4&3828BED4&0 : USB Root Hub
USB\ROOT_HUB\4&61EFCCB&0 : USB Root Hub
USB\ROOT_HUB\4&64061BA&0 : USB Root Hub
USB\ROOT_HUB20\4&10671E48&0 : USB Root Hub
USB\ROOT_HUB20\4&6BA2591&0 : USB Root Hub
USB\VID_0461&PID_4D15\5&2DE04A89&0&1 : USB Human Interface Device
USB\VID_0644&PID_0200\00000110B551 : USB Mass Storage Device
USB\VID_413C&PID_2005\5&2DE04A89&0&2 : USB Human Interface Device
USBSTOR\DISK&VEN_TEAC&PROD_USB___HS-CF_CARD&REV_4.00\00000110B551&0: TEAC USB HS-CF Card USB Device
USBSTOR\DISK&VEN_TEAC&PROD_USB___HS-MS_CARD&REV_4.00\00000110B551&2: TEAC USB HS-MS Card USB Device
USBSTOR\DISK&VEN_TEAC&PROD_USB___HS-SD_CARD&REV_4.00\00000110B551&3: TEAC USB HS-SD Card USB Device
USBSTOR\DISK&VEN_TEAC&PROD_USB___HS-XD/SM&REV_4.00\00000110B551&1: TEAC USB HS-xD/SM USB Device
14 matching device(s) found.- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
Thanks for reporting back. Well, that should NOT be happening. I'll get on that straight away. My initial guess is something I put in the .ini file for Matrox that somehow matches the ATI files.
*Edit
Well, this part of your finisher log is very interesting:
2007-09-07 10:11:51 : <FLTR> Verifying requirements for exception [M-1] (6 of 23 exceptions).
2007-09-07 10:11:51 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2007-09-07 10:11:51 : <FLTR> Found tagfile "C:\WINDOWS\system32\Mtx*.dll" (1/1).
2007-09-07 10:11:51 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2007-09-07 10:11:51 : <FLTR> Wildcard specified for +infFiles requirement: scan for .inf files (1 of 1 +infFiles).
2007-09-07 10:11:51 : <FLTR> ! Could not match +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> ! Could not match +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183&REV_00" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> Matched +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> => All requirements for exception [M-1] have been met!
2007-09-07 10:11:51 : <FLTR> Verifying requirements for exception [A-2] (7 of 23 exceptions).
2007-09-07 10:11:51 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2007-09-07 10:11:51 : <FLTR> Found tagfile "C:\D\G\A\2\CPanel.exe" (1/1).
2007-09-07 10:11:51 : <FLTR> 3. -hwids (ANY -hwids must be matched)
2007-09-07 10:11:51 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2007-09-07 10:11:51 : <FLTR> Wildcard specified for +infFiles requirement: scan for .inf files (1 of 1 +infFiles).
2007-09-07 10:11:51 : <FLTR> ! Could not match +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> ! Could not match +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183&REV_00" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> Matched +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> => All requirements for exception [A-2] have been met!
2007-09-07 10:11:51 : <FLTR> Verifying requirements for exception [A-6] (8 of 23 exceptions).
2007-09-07 10:11:51 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2007-09-07 10:11:51 : <FLTR> Found tagfile "C:\D\G\A\6\CPanel.exe" (1/1).
2007-09-07 10:11:51 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2007-09-07 10:11:51 : <FLTR> Wildcard specified for +infFiles requirement: scan for .inf files (1 of 1 +infFiles).
2007-09-07 10:11:51 : <FLTR> ! Could not match +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> ! Could not match +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183&REV_00" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> Matched +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> => All requirements for exception [A-6] have been met!
2007-09-07 10:11:51 : <FLTR> Verifying requirements for exception [A-A] (9 of 23 exceptions).
2007-09-07 10:11:51 : <FLTR> 1. tagFiles (ALL tagFiles must be found)
2007-09-07 10:11:51 : <FLTR> Found tagfile "C:\D\G\A\A\CPanel.exe" (1/1).
2007-09-07 10:11:51 : <FLTR> 4. +infFiles (ANY +infFiles must be matched)
2007-09-07 10:11:51 : <FLTR> Wildcard specified for +infFiles requirement: scan for .inf files (1 of 1 +infFiles).
2007-09-07 10:11:51 : <FLTR> ! Could not match +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> ! Could not match +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183&REV_00" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> Matched +infFile"C:\D\G\A\1\CX_50960.inf" through the HWID "PCI\VEN_1002&DEV_7183" (original HWID: "PCI\VEN_1002&DEV_7183&SUBSYS_0D021028&REV_00").
2007-09-07 10:11:51 : <FLTR> => All requirements for exception [A-A] have been met!Notice how all the criteria are being met by a single .inf? 
According to your log, you should have the ATICCC installed as well as the control panel. Someone else reported that error as well but we couldn't track it down to anything. Oh yeah, it was you back on page-3 that reported the double ATI install. Did you have the QSC enabled in the DPBase? If so, please delete everything in the QSC folder.
Last edited by mr_smartepants (2007-09-08 00:35:37)
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
Re: Testers needed for new Graphics driverpacks
Hi.....
Yep it was me who reported the the ATICCC + control panel thing. I don't have QSC enabled.....I am using method 2 and DPs_BASE.EXE recommends disabling QSC for method 2. (Why?).....
I did check in case I had an old QSC folder lying around (I did used to enable QSC when I first started using DriverPacks) but there isn't one where.
HTH.
Chris.
- Jaak
- Old Timer Rookie
- Offline
Re: Testers needed for new Graphics driverpacks
Hi
Method 2: when one does NOT use QSC, one can get bitten by tiny bugs.
Method 1, without QSC, one gets bitten by a big bug.
Erik?
could you perhaps update your tute with parts of the txt I use in the tute I keep online?
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
Jaak wrote:
Erik?
could you perhaps update your tute with parts of the txt I use in the tute I keep online?
Sure Jaak,
When I get some free time this weekend I'll take care of it.
cwbshaw, I'm still at a loss why your finisher log looks like it does. I'm going to try to recreate your setup and install it over the weekend. Can you email me at mr_smartepants_a-t_driverpacks.net with your specific integration contents/order?
I've already tested using all the DriverPacks together and I'm not encountering your errors.
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
DP_Graphics_B_wnt5_x86-32_709.1
http://dev.driverpacks.thesneaky.com/dr … 2_709.1.7z
MD5: 6603E1C0452A2400EA73157BC38EE027
chud & cwbshaw, can you two download and test this nightly build? I did not include any Dell specific drivers, but I fixed some of the Intel (deleted I\7, added I\4 for 845G) and the Matrox (.ini edit).
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
- Jaak
- Old Timer Rookie
- Offline
Re: Testers needed for new Graphics driverpacks
Erik, the 7.09.1 Graphics B is already finalised.
Like you said, the DELL specific files can seriously add a humongous amount to the DP, and the updated embedded was so new it got in the way of so many other HWIDs... (even the old embedded version was kinda iffy)
I figured the fix had to be published asap.
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
Thanks Jaak,
The .ini M-1 section was looking for a MTX*.dll when it didn't need to (so I took it out). I figure just the .inf/exe matching would be sufficient.
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
Re: Testers needed for new Graphics driverpacks
Hi mr_smartpants, thanks for sorting this, I will try and give it a blast on monday - just one quick question was wondering about ;
Dell driverpack R96000.exe w/cat file
DriverVer=01/23/2005,6.14.10.4020
supporting 865G driver (VEN_8086&DEV_2572)
Above Dell pack appears to be newer then your I\5\ folder with 865 support that is
DriverVer=08/20/2004,6.14.10.3889
Incidently the newest driver on Intels site I could find with 865 support is
DriverVer=09/20/2005,6.14.10.4396
this driver supports the following
%iMGM% = i852GM, PCI\VEN_8086&DEV_3582
%iSDG% = i865G, PCI\VEN_8086&DEV_2572
%iGDGD0% = i915G0, PCI\VEN_8086&DEV_2582
%iGDGD1% = i915G1, PCI\VEN_8086&DEV_2782
%iALVD0% = i915GM0, PCI\VEN_8086&DEV_2592
%iALVD1% = i915GM1, PCI\VEN_8086&DEV_2792
%iLPGD0% = i945G0, PCI\VEN_8086&DEV_2772
%iLPGD1% = i945G1, PCI\VEN_8086&DEV_2776
[url]http://downloadcenter.intel.com/T8Clear … e=Windows* XP Professional&lang=eng[/url]
Last edited by chud (2007-09-10 03:16:48)
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
chud wrote:
Incidently the newest driver on Intels site I could find with 865 support is
DriverVer=09/20/2005,6.14.10.4396
Hmmm, that's odd. When I refreshed the Intel folders, that driver wasn't listed (at least I don't remember it) which was why the changelog read I\5 was unchanged.
I'll compare the .infs and add it in there. Thanks for pointing that out.
I'm reluctant to add Dell drivers into the Intel folders, only because I would like to keep the DriverPacks as generic as possible. We may add them in if Dell makes a 'unified' package that covers a wide range of their products, otherwise we'd be forever updating these DriverPacks just for incremental changes to a single platform.
*Edit,
I remember why I left I\5 alone now...It was the only driver to support 830M (And 845G/865G), the newer driver drops 830M support. Seeing how you can't even buy new Socket 478 mobos with 845/865/875 chipsets anymore (I've only found them on ebay), we may be revamping the whole Intel folder into a 'legacy' DP later in the future. Either that, or breaking the driver signing by combining all the driver files together along with all the .infs...should save some weight.
Anyway, I'll see what I can do.
Last edited by mr_smartepants (2007-09-10 06:54:17)
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
Re: Testers needed for new Graphics driverpacks
hehe ok, i would much rather it work than be as new as possible anyway
what did you think about using link junctions to remove duplicate files, i presume they will appear transparent to the .cat file?
- Jaak
- Old Timer Rookie
- Offline
Re: Testers needed for new Graphics driverpacks
Hi
the CAT files have HWID information in them too.. do a right-click for properties, and you see what I mean.
edit, the latest driver for 865G drops two HWIDs we only have in i\5
[Intel.Mfg]
;%iMGM% = i852GM, PCI\VEN_8086&DEV_3582 ; duped by a still newer
%iSDG% = i865G, PCI\VEN_8086&DEV_2572 ;is newest (but drops two HWIDs)
;%iGDGD0% = i915G0, PCI\VEN_8086&DEV_2582 ; duped by a still newer
;%iGDGD1% = i915G1, PCI\VEN_8086&DEV_2782 ; duped by a still newer
;%iALVD0% = i915GM0, PCI\VEN_8086&DEV_2592 ; duped by a still newer
;%iALVD1% = i915GM1, PCI\VEN_8086&DEV_2792 ; duped by a still newer
;%iLPGD0% = i945G0, PCI\VEN_8086&DEV_2772 ; duped by a still newer
;%iLPGD1% = i945G1, PCI\VEN_8086&DEV_2776 ; duped by a still newer
if we intend to update i\5 we would have to actually add the driver rather than update it.
That would mean another intel for these two
[Intel.Mfg]
%i830M% = i830M, PCI\VEN_8086&DEV_3577
%iBKDG% = i845G, PCI\VEN_8086&DEV_2562
;%iSDG% = i865G, PCI\VEN_8086&DEV_2572 ; duped by a still newer
a right mess, right?
Let us suppose that intel are generic ones, and that we slap in all the newest drivers for DELL's.
If DELL use generic HWIDs, and use OEM-modified chips, we could create a lot of problems.
I don't mind looking at them, tho.
Last edited by Jaak (2007-09-10 10:16:06)
The answer was 42?
Kind regards, Jaak.
Kind regards, Jaak.
Re: Testers needed for new Graphics driverpacks
Hi....
Tried the Graphics B 7.09.1 but still got the same Matrox popup. I tried it both with and without QSC, but still got the same result on both the Dell Optiplex 745 and the Optiplex GX620.
The DPsFnshr.log for the Optiplex 745 is viewable at:
http://cwbshaw.diinoweb.com/files/DPsFnshr.log
....and the HWID list is the same as my last post (same machine).
HTH.
Chris.
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
cwbshaw wrote:
Tried the Graphics B 7.09.1 but still got the same Matrox popup. I tried it both with and without QSC, but still got the same result on both the Dell Optiplex 745 and the Optiplex GX620.
OK, grasping at straws here. Can you retest by integrating into a fresh source after replacing all three graphics DriverPacks .ini files with the following code:
Graphics_A
[DriverPack]
platform = "wnt5_x86-32"
name = "Graphics A"
; version 709.1
rootDir = "D\G"
; OPTIONAL
classes = "Display"
driverCount = 2
decompSize = 174
compSize = 66.1
[A-1]
; REQUIRED
exc_count = 2
; OPTIONAL
exc_1_tagFiles = 3
exc_1_tagFile1 = "%SystemDrive%\ATICCC.ins"
exc_1_tagFile2 = "%DPSROOT%\D\G\A\1\ATICCC.exe"
exc_1_tagFile3 = "%SystemRoot%\system32\atidemgx.dll"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 1
exc_1_+infFile1 = "%DPSROOT%\D\G\A\1\*.inf"
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = "%DPSROOT%\D\G\A\1\ATICCC.exe"
exc_2_tagFiles = 3
exc_2_tagFile1 = "%SystemDrive%\ATICCP.ins"
exc_2_tagFile2 = "%DPSROOT%\D\G\A\1\ATICCP.exe"
exc_2_tagFile3 = "%SystemRoot%\system32\atidemgx.dll"
exc_2_+hwids = 0
exc_2_-hwids = 0
exc_2_+infFiles = 1
exc_2_+infFile1 = "%DPSROOT%\D\G\A\1\*.inf"
exc_2_-infFiles = 0
exc_2_commands = 1
exc_2_command1 = "%DPSROOT%\D\G\A\1\ATICCP.exe"Graphics_B
[DriverPack]
platform = "wnt5_x86-32"
name = "Graphics B"
; version 709.1
rootDir = "D\G"
; OPTIONAL
classes = "Display"
driverCount = 44
decompSize = 383
compSize = 58.1
[3-1]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 1
exc_1_tagFile1 = "%SystemRoot%\system32\3dfxV2ps.dll"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 1
exc_1_+infFile1 = "%DPSROOT%\D\G\3\1\*.inf"
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = "%DPSROOT%\D\G\3\1\V2_OC_control_panel.exe"
[A-5]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 3
exc_1_tagFile1 = "%SystemDrive%\ATICCP.ins"
exc_1_tagFile2 = "%DPSROOT%\D\G\A\1\ATICCP.exe"
exc_1_tagFile3 = "%SystemRoot%\system32\atidemgr.dll"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 1
exc_1_+infFile1 = "%DPSROOT%\D\G\A\5\*.inf"
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = "%DPSROOT%\D\G\A\1\ATICCP.exe"
exc_2_tagFiles = 3
exc_2_tagFile1 = "%SystemDrive%\ATICCC.ins"
exc_2_tagFile2 = "%DPSROOT%\D\G\A\1\ATICCC.exe"
exc_2_tagFile3 = "%SystemRoot%\system32\atidemgr.dll"
exc_2_+hwids = 0
exc_2_-hwids = 0
exc_2_+infFiles = 1
exc_2_+infFile1 = "%DPSROOT%\D\G\A\5\*.inf"
exc_2_-infFiles = 0
exc_2_commands = 1
exc_2_command1 = "%DPSROOT%\D\G\A\1\ATICCC.exe"
[M-1]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 1
exc_1_tagFile1 = "%SystemRoot%\system32\mtxparm.sys"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 1
exc_1_+infFile1 = "%DPSROOT%\D\G\M\1\*.inf"
exc_1_-infFiles = 0
exc_1_commands = 1
exc_1_command1 = "%DPSROOT%\D\G\M\1\matrox.exe"Graphics_C
[DriverPack]
platform = "wnt5_x86-32"
name = "Graphics C"
; version 709.1
rootDir = "D\G"
; OPTIONAL
classes = "Display"
driverCount = 8
decompSize = 205
compSize = 64.0
[A-2]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 2
exc_1_tagFile1 = "%DPSROOT%\D\G\A\2\CPanel.exe"
exc_1_tagFile2 = "%SystemRoot%\system32\atidemgr.dll"
exc_1_+hwids = 0
exc_1_-hwids = 1
exc_1_-hwid1 = "PCI\VEN_1002&DEV_5653&SUBSYS_00701025&REV_00"
exc_1_+infFiles = 2
exc_1_+infFile1 = "%DPSROOT%\D\G\A\2\C2_40334.inf"
exc_1_+infFile2 = "%DPSROOT%\D\G\A\2\CX_40334.inf"
exc_1_-infFiles = 0
exc_1_commands = 3
exc_1_command1 = "%DPSROOT%\D\G\A\2\CPanel.exe -y -o%DPSTMP%"
exc_1_command2 = "%DPSTMP%\setup.exe /K"
exc_1_command3 = "cmd.exe /c rd /s /q %DPSTMP%"
[A-6]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 2
exc_1_tagFile1 = "%DPSROOT%\D\G\A\6\CPanel.exe"
exc_1_tagFile2 = "%SystemRoot%\system32\atidemgr.dll"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 2
exc_1_+infFile1 = "%DPSROOT%\D\G\A\6\C2_26766.inf"
exc_1_+infFile2 = "%DPSROOT%\D\G\A\6\CX_26766.inf"
exc_1_-infFiles = 0
exc_1_commands = 3
exc_1_command1 = "%DPSROOT%\D\G\A\6\CPanel.exe -y -o%DPSTMP%"
exc_1_command2 = "%DPSTMP%\setup.exe /K"
exc_1_command3 = "cmd.exe /c rd /s /q %DPSTMP%"
[A-A]
; REQUIRED
exc_count = 1
; OPTIONAL
exc_1_tagFiles = 2
exc_1_tagFile1 = "%DPSROOT%\D\G\A\A\CPanel.exe"
exc_1_tagFile2 = "%SystemRoot%\system32\atidemgr.dll"
exc_1_+hwids = 0
exc_1_-hwids = 0
exc_1_+infFiles = 2
exc_1_+infFile1 = "%DPSROOT%\D\G\A\A\C2_21962.inf"
exc_1_+infFile2 = "%DPSROOT%\D\G\A\A\CX_21962.inf"
exc_1_-infFiles = 0
exc_1_commands = 3
exc_1_command1 = "%DPSROOT%\D\G\A\A\CPanel.exe -y -o%DPSTMP%"
exc_1_command2 = "%DPSTMP%\setup.exe /K"
exc_1_command3 = "cmd.exe /c rd /s /q %DPSTMP%"If you notice, I made the .ini exceptions more strict by adding additional tagfiles. It's difficult for the older ATI drivers in the C DP because they mostly contain the same-name files.
Last edited by mr_smartepants (2007-09-11 05:43:34)
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
Re: Testers needed for new Graphics driverpacks
Hi....
Will try this first thing in the morning.....
Chris.
- mr_smartepants
- Administrator & DriverPacks Developer
- Offline
Re: Testers needed for new Graphics driverpacks
Thank you. Looking forward to your test results.
Oh, and before anyone asks...I'm already working on the ATI Catalyst 7.9 suite released yesterday.
Read BEFORE you post. HWID tool DriverPacks Tutorial DONATE!
Not all heroes wear capes, some wear Kevlar!
Not all heroes wear capes, some wear Kevlar!
Re: Testers needed for new Graphics driverpacks
Success!
That fixed both the Matrox popup and also the ATI CCC and CCP problem. Now the OptiPlex 745 and GX620 don't get the Matrox popup and they only show the ATI CCC on the taskbar.....no CCP.
Hope this helps.
Chris.