Posts [ 12 ]

I search for info on this and see that there are a few post complaining about hangs etc caused by this. I made a 3rd party pack out of the following driver and it worked fine. However the current Grapics packs do not work for me at all.Graphics A 9.06Graphics B 9.06Graphics C 8.12.1ftp://ftp.us.dell.com/video/R126541.EXE

Well I looked, and DriverPack Graphics B \I4\igxp32.inf has your HWIDs. I had edited it to remove duplicates (and broke driver signing in the process).That may be why it doesn't work for you if you haven't disabled driver signing.I'll have a look at those Dell drivers...*Edit, They're from 2006. I'm not going to replace I4 for those. I'll replace my edited .inf with the original one. Can you test that one after I upload?

I will test what ever you want.I guess i don't really understand the driver signing. I just run the DP_Install_Tool.cmd from SAD. Didn't know that if there was driving signing issues they wouldn't install.

Ok here is the story with the DP_Graphics_B_wnt5_x86-32_90701.7zI run SAD once and it find something and installs something. I still have exclamations in Device manager. I run a second time and it actually hangs this time

I am not really sure about seeding the chipset driver, never done that.Anyway i just wanted you to know the hang that i get from the DP_Graphics_B_wnt5_x86-32_90701 is reproducable via SAD. after the reboot though everything is dandy.

However, the driver is not installed properly when using SAD using the latest chipset and graphics drivers. I tried the suggestion of copying the inf files from the \D\C\I1 to my Windows\inf folder prior to deployment, and that did not help.

As you can see, the C:\WINDOWS\system32\DRVSTORE\igxp32_757949EFDD70357EE37252D828ACA09CDF5C75B7 folder gets deleted after this failure. As a test, I copied the d\g\i4 folder to C:\WINDOWS\system32\DRVSTORE\igxp32_757949EFDD70357EE37252D828ACA09CDF5C75B7, went to Device Manager, and tried to manually update the driver to what was at C:\WINDOWS\system32\DRVSTORE\igxp32_757949EFDD70357EE37252D828ACA09CDF5C75B7. That failed with a "Handle is Invalid" error. I assume that is the same as what happens in the log above.

Next, I pointed the Update Driver dialog in Device Manager to an expanded version of the d\g\i4 folder that I had elsewhere on the hard disk (in a path with a shorter total name, if that matters). For whatever reason, that worked--the driver installed just fine.

Still, the automated stuff launched via the DP_Install_Tool.cmd script fails. Any hope of fixing this? I hope these details help.

I have been out of the weeds of the Windows sysadmin game for awhile, and I've found the tools and information on these forums to be wonderful. Thank you all for your efforts!