Chipset x64 (Page 2 of 4)

Hey guys, long time no post. I just noticed in the readme.txt for the latest intel release v9.2.0.1016 (and this may apply to many prior releases!) that only the WIN7 folder has valid drivers for Windows 7. It specifically states:

If you think about it, this makes sense since so many inf's in that "ALL" folder are ancient. Does it really make sense to integrate an inf for a 915 chipset from 2003? I do notice the ALL folder has more recent chipset inf's for current hardware that is not covered in WIN7, so this is still unclear for me. I discovered this distinction in the intel readme after trying to diagnose some BSODs in the new version of VirtualBox that now can emulate an ICH9 chipset instead of the ancient PIIX3.

What are your thoughts?

9.1.2.1008 and all prior releases on intel.com that I bothered to dig through say the very same thing in their readme.txt's

This appears to be standard practice since their first Win7 compatible release.

So now that we've established there's no difference between the newer leaked WHQL's and past releases' folder structures - it begs the question are the ones in the "ALL" folder really supposed to be integrated or not? What makes this more confusing is that the ALL folder has infs for ICH9 but WIN7 does not (only ich7/8). Odd?

Last edited by Fragbert (2010-12-30 09:17:11)

Yes I confirm too, DISM integrates ALL no problem, at least no error in integrating. If the driver truly is for Vista only, DISM will complain (for example, the separate 7 and vista drivers in radeon catalyst driver distro). But, as we know sometimes a gremlin can sneak in like that blasted ATI filter driver. I just wonder though if adding those older inf's to specifically a win7 install can confuse Win7? I actually opened a live chat support ticket with intel to dig into this, mentioning how ich9 isnt in WIN7, but 7 and 8 are - and he just gave a cryptic "ICH9 support is built in Windows 7" and I need to contact MS about slipstreaming. Ha.

It would be nice to know if you ran the chipset inf installer on a live windows 7 system if the installer itself would use any INF's from "ALL" even though they are not supposed to be for Windows 7.

Probably not something worth aching over - I realized soon enough that my virtualbox woes are nothing to do with these folders. The new Virtualbox is just a POS that BSODs when rebooting for many others and you have to power the VM on/off to get a clean boot if you wanna use ICH9 and HD audio support - bah!!

Last edited by Fragbert (2010-12-31 00:15:25)

Hmmm, I should add that to my "to do" list since I have an ICH9R chip and I'm working on the new SAD2 utility.  I could do a test install on a spare drive with a base Win7, then "update" the driver and check the file versions.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

Intel Management Engine 7.0.0.1144
http://downloadcenter.intel.com/Detail_ … p;lang=deu

lets report what happenend under win7sp1:

EDIT: fetched all the x64 packs, put in the x64 folder and decided to do method_2 , well everything ran thru but at the 30 secs finish there came 1-2 error "could not find specific file " .

a lots of unknown devices were recoqnized, 3 are still un-recoqnized . while i checked device_manager , it said "please reboot". yeah that's clear cause of the chipset and so on . after reboot finally the synaptics s/w appeared in the taskbar and it again said "ey please reboot".

well i try to re-run , hope there's nothing damaged at the first shot ;-) keep you updated.

EDIT2: well those 3 arent recoqnized, tried 3 times re-run :

Edit3: this "serial pci" stuff is nothing else than "intel AMT mgmt driver" -> hp download -> sp45131.exe , perhaps you could "include" in your driverpacks? another post below this subforum talks about intel/dell AMT
i try to post anothet screenshot how it looks after updating with hp's driver next week ok?
dpinst.log:
http://www.mediafire.com/file/8eepcg2tx … DPINST.LOG

.txt log of the .cmd script , at the end there came 2-3 errors saying "could access file" . try to make a screenshot again perhaps while "clean up" it hadnt chance to access specific files ?
http://www.mediafire.com/file/eazpz85bc39654r/loggy.txt

as the loggy.txt says "everything was fine".. besides those 3 above werent recoqnized.

regards

Last edited by raummusik (2011-04-16 19:43:01)

I noticed in a changelog a while ago that there were(is?) known errors in the pack.

Has this been resolved?

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

Yup, I got the subtle hint.
I'm not nagging, just doing what i can to support The Effort. 

Last edited by TechDud (2011-04-23 08:48:41)

Forum Rules & Guidelines   HWID's tool   Unknown Devices (Win7-max) LatencyMon - NT6.x
MemTest86+    Video Memory Stress Test    D-P-C Driver Latency Tester (Win7-max)

Good to know.  Thanks Fragbert.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!

Not all heroes wear capes, some wear Kevlar!

FYI: The FTDI folder with ftdibus.inf fails to integrate via DISM on Windows 7 x64, all the rest integrate fine (code = '0')

No worries friend! All in all, the latest DP releases are pretty slick. As you can tell by my flurry of posts, I was doing a few updates to my integration base, so thought I'd report which folders had gremlins.