Re: Chipset x64

Updated to 10.07.1

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

Updated to 10.11

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

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:


The directories are classified according to the following:

   All\   
            Contains INF files designed for
            Windows* 2000, Windows* XP, Windows Server* 2003,
            Windows Server* 2008, and Windows* Vista

   Win7\   
            Contains INF files designed for
            Windows* 7 and Windows Server* 2008 R2

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?

Re: Chipset x64

v9.2.0.1016 isn't final.  It's pre-release.  So who knows what folder layout Intel will go with once final.  v9.1.2.1008 is still the current final from the official Intel downloads page.
But it wouldn't surprise me that they would segregate the drivers like that.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

mr_smartepants wrote:

v9.2.0.1016 isn't final.  It's pre-release.  So who knows what folder layout Intel will go with once final.  v9.1.2.1008 is still the current final from the official Intel downloads page.
But it wouldn't surprise me that they would segregate the drivers like that.

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)

Re: Chipset x64

Wow I didn't even notice.  You're right.  These packs support both Vista & Win7 so including everything won't hurt unless there's an integration error.  But before releasing, I always do a test integration with DISM.  No errors, no problems.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

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)

Re: Chipset x64

Only issue with integrating the intel chipset drivers I have is dmi_pci.inf and the 'High Precision Event Timer'

In the device manager properties Resource tab it conflicts with another driver...fix is to uninstall (make sure to fully delete INF), reboot and reinstall

I guess because of this problem is why it was removed for Windows 7 back in 9.1.1.1015 (Link)

Last edited by ricktendo64 (2010-12-31 03:24:57)

Re: Chipset x64

Fragbert wrote:

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.

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!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

Intel Chipsets 9.2.0.1021

http://downloadcenter.intel.com/Detail_ … p;lang=deu

Re: Chipset x64

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

Re: Chipset x64

Updated to 11.04

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

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 :

http://i51.tinypic.com/foj5hh.png

http://i54.tinypic.com/2zrnz7m.png

http://i51.tinypic.com/2q1tqbp.png

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)

Re: Chipset x64

That HPQ0006 is for the HP QuickLaunch buttons.
http://www.tricksguide.com/windows-7vis … q0006.html

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

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

Known errors:
x64\C\Intel\1\NehalMEX.inf
x64\C\Intel\1\Tcreek.inf
x64\C\Nvidia\2\nf4sys.inf
Error - The driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

Has this been resolved?

Re: Chipset x64

Before anyone asks, yes, I'm already aware of the new Intel 9.2.0.1030 chipset WHQL drivers.
http://downloadcenter.intel.com/Detail_ … p;lang=eng

@TechDud, I didn't get a chance to update the changelog with my test results.  I will for 11.05

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

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

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

Re: Chipset x64

Don't bother, 9.2.2.1029 or newer will be released shortly on intel.com, its already on stationdrivers and they are WHQL

Re: Chipset x64

Good to know.  Thanks Fragbert.

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

Updated to 11.05.1

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

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

Re: Chipset x64

Ah, that's because I stupidly deleted the i386 folder.  Fixed in my local copy of DriverPack Chipset 11.06

Read BEFORE you post.  HWID tool   DriverPacks Tutorial   DONATE!
http://driverpacks.net/userbar/admin-1.png
Not all heroes wear capes, some wear Kevlar!

Re: Chipset x64

mr_smartepants wrote:

Ah, that's because I stupidly deleted the i386 folder.  Fixed in my local copy of DriverPack Chipset 11.06

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. smile

Re: Chipset x64

I have found some issues in integrating this x64 Win7 Chipset into boot.wim x64 file...
The errors I have encountered are:

Installing 71 of 231 - x64\C\Intel\1\NehalMEX.inf: Error - The
driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

Installing 77 of 231 - x64\C\Intel\1\Tcreek.inf: Error - The
driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

Installing 92 of 231 - x64\C\Nvidia\2\nf4sys.inf: Error - The
 driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

Installing 100 of 231 - x64\C\USB\FTDI\ftdibus.inf: Error - An
error occurred. The driver package could not be installed.
For more information, check for log files in the <windir>\inf folder of the target image.

For your information I am running the x86 dism tool to integrate these drivers, cos I don't have an x64 ready right now...
Procedure I am following is this one here: http://forum.driverpacks.net/viewtopic.php?id=5199

Are there any solutions to fix these errors?
Can I do something to help... increasing my learning curve even further...

EDIT 1: seems to have been reported earlier as well

TechDud wrote:

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

Known errors:
x64\C\Intel\1\NehalMEX.inf
x64\C\Intel\1\Tcreek.inf
x64\C\Nvidia\2\nf4sys.inf
Error - The driver package contains x64 boot-critical drivers, but the drivers are not properly signed.
Use the /forceunsigned option to install the drivers.

Has this been resolved?

Fragbert wrote:

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

EDIT 2:
Sorry for repeating this, only just saw that it had been reported earlier...
is there a quick fix for these glitches?
I think for the improperly signed ones, should be easily fixed, no as I guess it involves getting cat files from original sources is it not?

EDIT 3:
For the FTDI driver issue: I have found the homepage and driver download page, but I don't seem to know which package type you've used: D2XX drivers vs. Virtual COM port (VCP) drivers packages...
Can you elaborate then I can fix it here locally smile
Do you recommend using the /forceunsigned flag or not?

Last edited by mindwarper (2011-08-06 12:06:41)

http://d1syubgj0w3cyv.cloudfront.net/cdn/farfuture/Av2BDsDf_iiqO8a4dpI49DKicUs_0zEQtEPcTGyCqV4/perpetual:forever/userbar/tester-1.png

Re: Chipset x64

The FTDI drivers include both, I believe.  One set for Vcom Ports, the other for programmed dll access.  The two download pages link the same 2.08.14 version.
Latest readme.rtf:  http://www.ftdichip.com/Drivers/CDM/CDM … 20Info.rtf
Here's a D2XX programming guide if it helps. http://www.ftdichip.com/Support/Documen … 00071).pdf

the d2xx dll's are included in the ftdibus.inf driver.

[FtdiBus.NTamd64.Copy]
ftdibus.sys

[FtdiBus.NTamd64.Copy2]
ftbusui.dll
ftd2xx.dll,ftd2xx64.dll
FTLang.dll

[FtdiBus.NTamd64.Copy3]
ftd2xx.dll

[Strings]
Ftdi="FTDI"
DESC="CDM Driver Package - Bus/D2XX Driver"

& from the Logo Verification Report:

Submission ID: 1448749
Submission Date: 4/12/2011
Logo Completion Date: 4/12/2011
Company: Future Technology Devices International Ltd
Product Name: FTDIChip CDM Driver Package
Category: Device
Subcategory: Unclassified
Qualification Level: Signature Only - Microsoft Windows 2000 family - Unclassified
Signature Only - Microsoft Windows XP family, x86 - Unclassified
Signature Only - Microsoft Windows Server 2003 family, x86 - Unclassified
Signature Only - Microsoft Windows Server 2003 family, x64 - Unclassified
Signature Only - Microsoft Windows XP family, x64 - Unclassified
Signature Only - Microsoft Windows Vista family, x86 - Unclassified
Signature Only - Microsoft Windows Vista family, x64 - Unclassified
Signature Only - Windows Server 2008 family, x86
Signature Only - Windows Server 2008 family, x64
Signature Only – Device - Compatible with Windows 7
Signature Only - Device - Compatible with Windows 7 x64
Signature Only - Windows Server 2008 Release 2 family, x64
Marketing Names: N/A
Additional Information:
Firmware version: 2.08.14

If this programmable-access driver represents a security risk, perhaps ftdibus.inf & referenced files should be removed.  I like FTDI chipsets, so far; straight-outta-Glasgow. big_smile

Here you may find some utilities including COMport assignment, a custom-INF maker (never tried it).  There's a Vista-Gadget for it, too.  http://www.ftdichip.com/Support/Utilities.htm
The 'Longhorn' version of USBview is on that page, too.

Last edited by TechDud (2011-08-06 18:31:58)