You are not logged in. Please login or register.
DriverPacks.net Forum » Posts by chud
V4 driver dont work.....this is the exact same mouse on each pc(Dell rebranded Logitech)
GX745 V3.1.0.0 - works fine
USB\VID_046D&PID_C016\5&18E0A94F&0&2 [corded optical wheel mouse, under HID devices]
USB\VID_413C&PID_2101&MI_00\6&5E51BFE&0&0000 [USB human interface device, under HID devices]
HID\VID_046D&PID_C016\6&1A600EB3&0&0000 [ HID-compliant optical wheeel mouse, under mice and other poitning devices]
GX150 V4 - not work
USB\VID_046D&PID_C016\5&35B73D88&0&2
does going back to DP_Input_wnt5_x86-32_070113.7z fix this issue?
eethball: its an issue with Dell USB corded optical mouse (rebadged Logitech) - I seem to recall having the issue last week with an older pack (that had the file) and it just said the device couldn't start and so didn't work. I got it working in the end by forcing it to be a regular HID device and using the MS driver.
Pack V7.09.08 - Getting error with missing file "WdfCoInstaller01005.dll" from
d\3\in\l\s
why has this file been removed, its referenced in the SourceDisksFiles entries ??
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?
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]
Since rebuilding with all the latest packs few days ago I am getting instant BSOD/reboot with Lattitude D430, D810, GX745 (and probably everything else), I don't know what pack causing it though
update * please ignore this, its a bug in Winimage , when you drag and drop files into the .ima file and save, sometimes the save doesn't take, which casused this problem as sysprep was then missing the mass storage section!
..
Hi,
Why does the new info file in it say my Dell Novotel Merlin 3g stuff was moved to the WLAN pack when it IS NOT (at 706 so not exactly likely to be) - looked on forum and link to test one (http://dev.driverpacks.thesneaky.com/dr … -32_708.7z) doesnt work anyway
The ClassGUID is 'system device' anyway and shouldn't have gone near the wlan pack - its more related to modems than wireless anyway as doesn't use Wireless Zero Configuration etc.
Jaak: the 3g things are actually System Devices so should be in main packs (just looked at the ClassGUID)
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.
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.
firstly the sysprep -bdsm didnt have any effect on anything so ignore that theory
hi mr_smarte, the bdsm bit is to also add other mass storage controllers from the driverpacks and so changes on what you decide to include or not include for text mode setup bit, and also when the structure changes or new drivers are added etc.
I will try just having the right info but rolled back so there is no INFCACHE as I belive that was what I was temporarily doing when it was working, purely by good luck.
Have had a look at artcile, which I will persue if this doesnt fix it - (seems to say that only occurs if the group policy is set though, which it isn't -"The Enable trusted publisher lockdown Group Policy setting is turned on, and you do not have the appropriate certificate in your Trusted Publishers certificate store.")
*cries* has anyone got anywhere with this?
If its an insurmountable problem please let everyone know, at least then I can make a routine at and of installer to manually do it rather than keep hanging on.
Cheers
just rebuilt and confirmed sysprep -bmsd is doing same thing makePNF does - which I presume is the cause of this. I will try doing the sysprep-bmsd, saving the info out, then rolling back in VMWARE and building next proper test without the -bmsd step , which is what I think I was coincidently doing when I first disabled makePNF and therefore discovered the solution. I am not at work to try tomorrow but will try first thing on Monday - and if its not that then I am pretty stumped as to why it worked other day and didn't for ages before that or now.
mr_smartepants - I am working on a theory as to the problem and what happened before when i thought i 'solved' it. A couple of weeks back I posted that they now worked, when I stopped using makePNF.exe in my build process. At this point they were all working fine. The reason I recall was because it stopped the double entries of what it was looking at finding the driver, i.e. both the oemxxx.inf and the .inf in the driverpack dir. Unfortunately I dont seem to have saved (or have with me) the setupapi log from when it worked to compare. I am almost sure the double entries stopped when I stopped using makepnf & hence driver worked - however as you can see they are back. Now I think its possible that using 'sysprep -bmsd' to populate the mass storage section is casuing a similar efect to makePNF was - which I have a feeling at the same point in time I had turned off. Hence using either makePNF or sysprep -bmsd is causing this double inf progblem , although quite why this only seemes to effect intel graphics drivers, I do not know.
I am just going to do another test build in vmware and see whats in the log after sysprep is done, to see if its making the INFCACHE files for the graphics card.
[2007/08/30 10:07:31 700.3 Driver Install]
#-019 Searching for hardware ID(s): pci\ven_8086&dev_2572&subsys_01511028&rev_02,pci\ven_8086&dev_2572&subsys_01511028,pci\ven_8086&dev_2572&cc_030000,pci\ven_8086&dev_2572&cc_0300
#-018 Searching for compatible ID(s): pci\ven_8086&dev_2572&rev_02,pci\ven_8086&dev_2572,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
#I022 Found "PCI\VEN_8086&DEV_2572" in C:\WINDOWS\Inf\oem1618.inf; Device: "Intel(R) 82865G Graphics Controller"; Driver: "Intel(R) 82865G Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i865G".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [i865G]. Rank: 0x0000e001. Effective driver date: 08/20/2004.
#I393 Modified INF cache "C:\WINDOWS\Inf\INFCACHE.1".
#I022 Found "PCI\VEN_8086&DEV_2572" in C:\WINDOWS\Inf\oem21.inf; Device: "Intel Corporation 865 Embedded Graphics Controller"; Driver: "Intel Corporation 865 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_2572" in C:\WINDOWS\DriverPacks\D\G\I\5\ialmnt5.inf; Device: "Intel(R) 82865G Graphics Controller"; Driver: "Intel(R) 82865G Graphics Controller"; Provider: "Intel Corporation"; Mfg: "Intel Corporation"; Section name: "i865G".
#I087 Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
#I023 Actual install section: [i865G]. Rank: 0x0000e001. Effective driver date: 08/20/2004.
#I022 Found "PCI\VEN_8086&DEV_2572" in C:\WINDOWS\DriverPacks\D\G\I\7\iegd.inf; Device: "Intel Corporation 865 Embedded Graphics Controller"; Driver: "Intel Corporation 865 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.
#-166 Device install function: DIF_SELECTBESTCOMPATDRV.
#I063 Selected driver installs from section [iegd_alm] in "c:\windows\inf\oem21.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_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.
#E122 Device install failed. Error 1168: Element not found.
#E157 Default installer failed. Error 1168: Element not found.
[2007/08/30 10:16:25 3564.2]
Used latest graphics packs when I made my last post
2007-08-28 20:10:59 (didnt see your reply)
and it didn't work on 865, same problem.
sorry I've been getting drunk and such over bank holiday w/e - ill do a build tonight and try and get a chance to test it tomorrow
Hi eethball, I know it doesn't work, people have been posting about it for months 
mr_smartepants, great - please let me know when Intel is sorted I will test it. I dont understand why they get de-ranked if driver signing is disabled anyway??
path looks wrong?
Windows\DriverPacks\D\D\3\P\H\ >>something missing here? <<HPZC3212.DLL
****************************************
>> Intel embedded graphics fubar'd (again?) <<
****************************************
Optiplex GX270 and GX260 fail at their embedded Intel graphics, (I think it was fine with whatever lastest graphics packs were in last few weeks)
Am getting this :
Driver node not trusted, rank changed from 0x00002001 to 0x0000e001.
SFC is turned off with the sfc_os.dll from RyanVM - specifically
offset 0xECE4, changed 3B C0 EB 32 90 to 83 F8 9D 75 08
and
offset 0x0140, changed E2 E0 to 55 5B
DriverPacks.net Forum » Posts by chud
Powered by PunBB, supported by Informer Technologies, Inc.
Currently installed 3 official extensions. Copyright © 2003–2009 PunBB.
[ Generated in 0.026 seconds, 6 queries executed ]