Is there something that can be done to prevent the installation of Silicon Image's resident control panel applet on machines that do not have any SI hardware? This is an issue that has been around since the old XP DP's too, so I'm not intending to single out this version.
26 2011-06-01 02:36:56
Re: MassStorage x64 (73 replies, posted in Vista / 7 DriverPack Mass Storage)
27 2011-06-01 02:34:23
Re: Touchpad Mouse x64 (53 replies, posted in 3rd Party Vista / 7 DriverPacks)
Just wanted to point out that when including this driverpack the installers for both hardare vendors (excluding the VM) leave resident programs and startup entries even if the hardware is not present.
28 2011-04-28 14:23:36
Re: Chipset x64 (85 replies, posted in Vista / 7 DriverPack Chipset)
Don't bother, 9.2.2.1029 or newer will be released shortly on intel.com, its already on stationdrivers and they are WHQL
29 2011-04-19 16:07:46
Re: Graphics A x64 (52 replies, posted in Vista / 7 DriverPack Graphics A)
Finally! New WHQLs for NVIDIA
30 2010-12-31 00:14:52
Re: Chipset x64 (85 replies, posted in Vista / 7 DriverPack Chipset)
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!!
31 2010-12-30 09:36:08
Re: Serious Problem with AMD PCI Express (3GIO) Chipset driver (27 replies, posted in Vista / 7 DriverPack Chipset)
The problem was that the amd/ati specific driver is called "pci.sys" and it will overwrite the standard win7 pci.sys, causing all the problems. This applies to VM's too. I assume this is long since addressed by smartypants but it would be nice if AMD would use a unique name so that we dont have to make a workaround for it.
32 2010-12-30 09:13:32
Re: Chipset x64 (85 replies, posted in Vista / 7 DriverPack Chipset)
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?
33 2010-12-30 05:15:52
Re: Vista and Win 7 driver packs are the same thing right? (3 replies, posted in Vista / 7 DriverPack Chipset)
http://forum.driverpacks.net/viewtopic. … 906#p41906 Perhaps I should have posted that here?
34 2010-12-30 04:53:32
Re: Chipset x64 (85 replies, posted in Vista / 7 DriverPack Chipset)
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* VistaWin7\
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?
35 2009-10-22 01:32:37
Re: [IMPL] Intel GMA driver package 6.14.10.5404 (Z7x/B77/H77support) (54 replies, posted in DriverPack Graphics)
updated req to package v14.38.10.5132
36 2009-10-22 01:24:16
Re: [REQ] Intel LAN v17.1a drivers (88 replies, posted in DriverPack LAN)
Updated request to v14.6
37 2009-08-20 02:46:58
Topic: [IMPL] Dell Wireless 1510 N WLAN Mini-Card for latitude E6400 (1 replies, posted in DriverPack WLAN)
Goes uninstalled on latest official and (as of this weekend) DP_WL nightly.
===========
PCI Devices
===========
PCI\VEN_1180&DEV_0822&SUBSYS_02331028&REV_21\4&A85581B&0&09F0: Ricoh SD Bus Host Adapter
PCI\VEN_1180&DEV_0832&SUBSYS_02331028&REV_04\4&A85581B&0&08F0: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1180&DEV_0843&SUBSYS_02331028&REV_11\4&A85581B&0&0AF0: Ricoh SD/MMC Host Controller
PCI\VEN_14E4&DEV_432B&SUBSYS_000D1028&REV_01\4&1CD20F91&0&00E1: Dell Wireless 1510 Wireless-N WLAN Mini-Card
PCI\VEN_8086&DEV_10F5&SUBSYS_02331028&REV_03\3&61AAA01&0&C8 : Intel(R) 82567LM Gigabit Network Connection
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_93\3&61AAA01&0&F0 : Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_282A&SUBSYS_02331028&REV_03\3&61AAA01&0&FA : Intel(R) ICH8M-E/ICH9M-E/PCHM SATA RAID Controller
PCI\VEN_8086&DEV_2917&SUBSYS_00000000&REV_03\3&61AAA01&0&F8 : Intel(R) ICH9M-E LPC Interface Controller - 2917
PCI\VEN_8086&DEV_2930&SUBSYS_02331028&REV_03\3&61AAA01&0&FB : Intel(R) ICH9 Family SMBus Controller - 2930
PCI\VEN_8086&DEV_2934&SUBSYS_02331028&REV_03\3&61AAA01&0&E8 : Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI\VEN_8086&DEV_2935&SUBSYS_02331028&REV_03\3&61AAA01&0&E9 : Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI\VEN_8086&DEV_2936&SUBSYS_02331028&REV_03\3&61AAA01&0&EA : Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI\VEN_8086&DEV_2937&SUBSYS_02331028&REV_03\3&61AAA01&0&D0 : Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI\VEN_8086&DEV_2938&SUBSYS_02331028&REV_03\3&61AAA01&0&D1 : Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI\VEN_8086&DEV_2939&SUBSYS_02331028&REV_03\3&61AAA01&0&D2 : Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI\VEN_8086&DEV_293A&SUBSYS_02331028&REV_03\3&61AAA01&0&EF : Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI\VEN_8086&DEV_293C&SUBSYS_02331028&REV_03\3&61AAA01&0&D7 : Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI\VEN_8086&DEV_293E&SUBSYS_02331028&REV_03\3&61AAA01&0&D8 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_2940&SUBSYS_00000000&REV_03\3&61AAA01&0&E0 : Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI\VEN_8086&DEV_2942&SUBSYS_00000000&REV_03\3&61AAA01&0&E1 : Intel(R) ICH9 Family PCI Express Root Port 2 - 2942
PCI\VEN_8086&DEV_2944&SUBSYS_00000000&REV_03\3&61AAA01&0&E2 : Intel(R) ICH9 Family PCI Express Root Port 3 - 2944
PCI\VEN_8086&DEV_2946&SUBSYS_00000000&REV_03\3&61AAA01&0&E3 : Intel(R) ICH9 Family PCI Express Root Port 4 - 2946
PCI\VEN_8086&DEV_2A40&SUBSYS_00000000&REV_07\3&61AAA01&0&00 : Mobile Intel(R) 4 Series Chipset Processor to DRAM Controller - 2A40
PCI\VEN_8086&DEV_2A42&SUBSYS_02331028&REV_07\3&61AAA01&0&10 : Mobile Intel(R) 4 Series Express Chipset Family
PCI\VEN_8086&DEV_2A43&SUBSYS_02331028&REV_07\3&61AAA01&0&11 : Mobile Intel(R) 4 Series Express Chipset Family
25 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&1DAB7EFA&0 : USB Root Hub
USB\ROOT_HUB\4&2113274D&0 : USB Root Hub
USB\ROOT_HUB\4&267B533E&0 : USB Root Hub
USB\ROOT_HUB\4&28F89E5E&0 : USB Root Hub
USB\ROOT_HUB\4&2F35B773&0 : USB Root Hub
USB\ROOT_HUB\4&F88EED4&0 : USB Root Hub
USB\ROOT_HUB20\4&2752B58A&0 : USB Root Hub
USB\ROOT_HUB20\4&3D9C819&0 : USB Root Hub
USB\VID_0A5C&PID_5800\0123456789ABCD : USB Composite Device
USB\VID_0A5C&PID_5800&MI_00\6&66DE6C9&0&0000 : Broadcom USH CV w/o Fingerprint Sensor
USB\VID_0A5C&PID_5800&MI_01\6&66DE6C9&0&0001 : USB Smart Card reader
11 matching device(s) found.
=============
Input Devices
=============
No matching devices found.
============
ACPI Devices
============
ACPI\ACPI0003\2&DABA3FF&0 : Microsoft AC Adapter
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_0 : Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_1 : Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz
ACPI\PNP0000\4&DCE5D5B&0 : Programmable interrupt controller
ACPI\PNP0100\4&DCE5D5B&0 : System timer
ACPI\PNP0103\4&DCE5D5B&0 : High Precision Event Timer
ACPI\PNP0200\4&DCE5D5B&0 : Direct memory access controller
ACPI\PNP0303\4&DCE5D5B&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0800\4&DCE5D5B&0 : System speaker
ACPI\PNP0A03\2&DABA3FF&0 : PCI bus
ACPI\PNP0B00\4&DCE5D5B&0 : System CMOS/real time clock
ACPI\PNP0C01\1 : System board
ACPI\PNP0C01\2 : System board
ACPI\PNP0C01\3 : System board
ACPI\PNP0C01\4 : System board
ACPI\PNP0C01\5 : System board
ACPI\PNP0C04\4&DCE5D5B&0 : Numeric data processor
ACPI\PNP0C09\0 : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1 : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0A\2 : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&0 : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0 : ACPI Sleep Button
ACPI\PNP0C14\0 : Microsoft Windows Management Interface for ACPI
ACPI\PNP0F13\4&DCE5D5B&0 : PS/2 Compatible Mouse
ACPI\THERMALZONE\THM_ : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
28 matching device(s) found.
============
HDA Audio
============
HDAUDIO\FUNC_01&VEN_111D&DEV_76B2&SUBSYS_10280233&REV_1003\4&380800DF&0&0001: IDT High Definition Audio CODEC
HDAUDIO\FUNC_01&VEN_8086&DEV_2802&SUBSYS_80860101&REV_1000\4&380800DF&0&0201: Intel(R) High Definition Audio HDMI Service
2 matching device(s) found.
============
RAID Devices
============
PCI\VEN_8086&DEV_282A&SUBSYS_02331028&REV_03\3&61AAA01&0&FA
Name: Intel(R) ICH8M-E/ICH9M-E/PCHM SATA RAID Controller
Hardware ID's:
PCI\VEN_8086&DEV_282A&SUBSYS_02331028&REV_03
PCI\VEN_8086&DEV_282A&SUBSYS_02331028
PCI\VEN_8086&DEV_282A&CC_010400
PCI\VEN_8086&DEV_282A&CC_0104
Compatible ID's:
PCI\VEN_8086&DEV_282A&REV_03
PCI\VEN_8086&DEV_282A
PCI\VEN_8086&CC_010400
PCI\VEN_8086&CC_0104
PCI\VEN_8086
PCI\CC_010400
PCI\CC_0104
1 matching device(s) found.38 2009-08-20 02:45:26
Topic: [REQ] IDT HD audio codec for Dell Latitude E6400 (1 replies, posted in DriverPack Sound)
Goes uninstalled on latest official and (as of this weekend) DP_S nightly.
===========
PCI Devices
===========
PCI\VEN_1180&DEV_0822&SUBSYS_02331028&REV_21\4&A85581B&0&09F0: Ricoh SD Bus Host Adapter
PCI\VEN_1180&DEV_0832&SUBSYS_02331028&REV_04\4&A85581B&0&08F0: OHCI Compliant IEEE 1394 Host Controller
PCI\VEN_1180&DEV_0843&SUBSYS_02331028&REV_11\4&A85581B&0&0AF0: Ricoh SD/MMC Host Controller
PCI\VEN_14E4&DEV_432B&SUBSYS_000D1028&REV_01\4&1CD20F91&0&00E1: Dell Wireless 1510 Wireless-N WLAN Mini-Card
PCI\VEN_8086&DEV_10F5&SUBSYS_02331028&REV_03\3&61AAA01&0&C8 : Intel(R) 82567LM Gigabit Network Connection
PCI\VEN_8086&DEV_2448&SUBSYS_00000000&REV_93\3&61AAA01&0&F0 : Intel(R) 82801 PCI Bridge - 2448
PCI\VEN_8086&DEV_282A&SUBSYS_02331028&REV_03\3&61AAA01&0&FA : Intel(R) ICH8M-E/ICH9M-E/PCHM SATA RAID Controller
PCI\VEN_8086&DEV_2917&SUBSYS_00000000&REV_03\3&61AAA01&0&F8 : Intel(R) ICH9M-E LPC Interface Controller - 2917
PCI\VEN_8086&DEV_2930&SUBSYS_02331028&REV_03\3&61AAA01&0&FB : Intel(R) ICH9 Family SMBus Controller - 2930
PCI\VEN_8086&DEV_2934&SUBSYS_02331028&REV_03\3&61AAA01&0&E8 : Intel(R) ICH9 Family USB Universal Host Controller - 2934
PCI\VEN_8086&DEV_2935&SUBSYS_02331028&REV_03\3&61AAA01&0&E9 : Intel(R) ICH9 Family USB Universal Host Controller - 2935
PCI\VEN_8086&DEV_2936&SUBSYS_02331028&REV_03\3&61AAA01&0&EA : Intel(R) ICH9 Family USB Universal Host Controller - 2936
PCI\VEN_8086&DEV_2937&SUBSYS_02331028&REV_03\3&61AAA01&0&D0 : Intel(R) ICH9 Family USB Universal Host Controller - 2937
PCI\VEN_8086&DEV_2938&SUBSYS_02331028&REV_03\3&61AAA01&0&D1 : Intel(R) ICH9 Family USB Universal Host Controller - 2938
PCI\VEN_8086&DEV_2939&SUBSYS_02331028&REV_03\3&61AAA01&0&D2 : Intel(R) ICH9 Family USB Universal Host Controller - 2939
PCI\VEN_8086&DEV_293A&SUBSYS_02331028&REV_03\3&61AAA01&0&EF : Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293A
PCI\VEN_8086&DEV_293C&SUBSYS_02331028&REV_03\3&61AAA01&0&D7 : Intel(R) ICH9 Family USB2 Enhanced Host Controller - 293C
PCI\VEN_8086&DEV_293E&SUBSYS_02331028&REV_03\3&61AAA01&0&D8 : Microsoft UAA Bus Driver for High Definition Audio
PCI\VEN_8086&DEV_2940&SUBSYS_00000000&REV_03\3&61AAA01&0&E0 : Intel(R) ICH9 Family PCI Express Root Port 1 - 2940
PCI\VEN_8086&DEV_2942&SUBSYS_00000000&REV_03\3&61AAA01&0&E1 : Intel(R) ICH9 Family PCI Express Root Port 2 - 2942
PCI\VEN_8086&DEV_2944&SUBSYS_00000000&REV_03\3&61AAA01&0&E2 : Intel(R) ICH9 Family PCI Express Root Port 3 - 2944
PCI\VEN_8086&DEV_2946&SUBSYS_00000000&REV_03\3&61AAA01&0&E3 : Intel(R) ICH9 Family PCI Express Root Port 4 - 2946
PCI\VEN_8086&DEV_2A40&SUBSYS_00000000&REV_07\3&61AAA01&0&00 : Mobile Intel(R) 4 Series Chipset Processor to DRAM Controller - 2A40
PCI\VEN_8086&DEV_2A42&SUBSYS_02331028&REV_07\3&61AAA01&0&10 : Mobile Intel(R) 4 Series Express Chipset Family
PCI\VEN_8086&DEV_2A43&SUBSYS_02331028&REV_07\3&61AAA01&0&11 : Mobile Intel(R) 4 Series Express Chipset Family
25 matching device(s) found.
===========
USB Devices
===========
USB\ROOT_HUB\4&1DAB7EFA&0 : USB Root Hub
USB\ROOT_HUB\4&2113274D&0 : USB Root Hub
USB\ROOT_HUB\4&267B533E&0 : USB Root Hub
USB\ROOT_HUB\4&28F89E5E&0 : USB Root Hub
USB\ROOT_HUB\4&2F35B773&0 : USB Root Hub
USB\ROOT_HUB\4&F88EED4&0 : USB Root Hub
USB\ROOT_HUB20\4&2752B58A&0 : USB Root Hub
USB\ROOT_HUB20\4&3D9C819&0 : USB Root Hub
USB\VID_0A5C&PID_5800\0123456789ABCD : USB Composite Device
USB\VID_0A5C&PID_5800&MI_00\6&66DE6C9&0&0000 : Broadcom USH CV w/o Fingerprint Sensor
USB\VID_0A5C&PID_5800&MI_01\6&66DE6C9&0&0001 : USB Smart Card reader
11 matching device(s) found.
=============
Input Devices
=============
No matching devices found.
============
ACPI Devices
============
ACPI\ACPI0003\2&DABA3FF&0 : Microsoft AC Adapter
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_0 : Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz
ACPI\GENUINEINTEL_-_X86_FAMILY_6_MODEL_23\_1 : Intel(R) Core(TM)2 Duo CPU P8400 @ 2.26GHz
ACPI\PNP0000\4&DCE5D5B&0 : Programmable interrupt controller
ACPI\PNP0100\4&DCE5D5B&0 : System timer
ACPI\PNP0103\4&DCE5D5B&0 : High Precision Event Timer
ACPI\PNP0200\4&DCE5D5B&0 : Direct memory access controller
ACPI\PNP0303\4&DCE5D5B&0 : Standard 101/102-Key or Microsoft Natural PS/2 Keyboard
ACPI\PNP0800\4&DCE5D5B&0 : System speaker
ACPI\PNP0A03\2&DABA3FF&0 : PCI bus
ACPI\PNP0B00\4&DCE5D5B&0 : System CMOS/real time clock
ACPI\PNP0C01\1 : System board
ACPI\PNP0C01\2 : System board
ACPI\PNP0C01\3 : System board
ACPI\PNP0C01\4 : System board
ACPI\PNP0C01\5 : System board
ACPI\PNP0C04\4&DCE5D5B&0 : Numeric data processor
ACPI\PNP0C09\0 : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0C0A\1 : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0A\2 : Microsoft ACPI-Compliant Control Method Battery
ACPI\PNP0C0C\2&DABA3FF&0 : ACPI Power Button
ACPI\PNP0C0D\2&DABA3FF&0 : ACPI Lid
ACPI\PNP0C0E\2&DABA3FF&0 : ACPI Sleep Button
ACPI\PNP0C14\0 : Microsoft Windows Management Interface for ACPI
ACPI\PNP0F13\4&DCE5D5B&0 : PS/2 Compatible Mouse
ACPI\THERMALZONE\THM_ : ACPI Thermal Zone
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ROOT\ACPI_HAL\0000 : ACPI Multiprocessor PC
28 matching device(s) found.
============
HDA Audio
============
HDAUDIO\FUNC_01&VEN_111D&DEV_76B2&SUBSYS_10280233&REV_1003\4&380800DF&0&0001: IDT High Definition Audio CODEC
HDAUDIO\FUNC_01&VEN_8086&DEV_2802&SUBSYS_80860101&REV_1000\4&380800DF&0&0201: Intel(R) High Definition Audio HDMI Service
2 matching device(s) found.
============
RAID Devices
============
PCI\VEN_8086&DEV_282A&SUBSYS_02331028&REV_03\3&61AAA01&0&FA
Name: Intel(R) ICH8M-E/ICH9M-E/PCHM SATA RAID Controller
Hardware ID's:
PCI\VEN_8086&DEV_282A&SUBSYS_02331028&REV_03
PCI\VEN_8086&DEV_282A&SUBSYS_02331028
PCI\VEN_8086&DEV_282A&CC_010400
PCI\VEN_8086&DEV_282A&CC_0104
Compatible ID's:
PCI\VEN_8086&DEV_282A&REV_03
PCI\VEN_8086&DEV_282A
PCI\VEN_8086&CC_010400
PCI\VEN_8086&CC_0104
PCI\VEN_8086
PCI\CC_010400
PCI\CC_0104
1 matching device(s) found.39 2009-07-15 02:42:18
Re: [REL] DP_WebCam_wnt5_x86-32_1009 (84 replies, posted in 3rd Party DriverPacks)
90626 caused BSOD's after initial setup. Anybody else have this problem? I isolated it to webcam only after a process of elimination, I use all other DriverPacks and 3rd party DriverPacks.
40 2009-05-21 09:10:09
Topic: [REQ] Updated Dell PERC SAS drivers, gen 5 and 6 (0 replies, posted in DriverPack Mass Storage)
Version 2.23.0.32
41 2009-04-17 06:16:20
Re: [REQ] IDT High Definition Audico CODEC (1 replies, posted in DriverPack Sound)
http://downloadmirror.intel.com/16741/e … I_V153.exe
New version 6162!
42 2009-04-08 00:39:14
Re: Vista-Tool 1.0 (39 replies, posted in Vista-Tool)
Pasha_ZZZ wrote:
When I integrate IE8 (unpack EXE, get 2 MSU - IE & langpack, unpack MSUs, get 2 CABs from each MSU, integrate IE8 CABs with Vista-Tool, in next session integrate langpack CABs) - after installing Vista (right before user creation) I had "Updates: stage 3 of 3 - 100% complete" for about 15 minutes, then computer restarts & I see this message again. System is in infinite loop.
IE8 is tricky - the best way is to install ie8 from setupcomplete.cmd and then run the updates after a reboot (you can still automate this by having the setupcomplete.cmd add entries to HKLM\..\runonce).
43 2009-04-04 04:08:45
Re: Vista-Tool 1.0 (39 replies, posted in Vista-Tool)
One bug that I have noticed is that drivers will not integrate unless I flush all the log files generated from a prior driver integration. Does anybody else notice this? This may be a problem with WAIK too as I had to omit logging in the cmd prompt to get things going.
Also, is there any way to integrate unsigned drivers? Specifically I can not get Vista to load nvidia beta drivers (like 182.47 for instance) for the GTX 2xx. Only using nvidia's latest WHQL release will install.
Also - vista has built-in IaStor (intel matrix storage) RAID drivers at v6.xx - I integrate the latest WHQL drivers (v8.7) for that and Vista still insists on using the older version. Is there a way to force this or remove the older driver cleanly?
44 2009-03-26 05:08:40
Re: [IMPL] Intel GMA driver package 6.14.10.5404 (Z7x/B77/H77support) (54 replies, posted in DriverPack Graphics)
updated to v6.14.10.5042 from package v14.38.2.5042
45 2009-03-26 05:01:05
Re: Did I Miss Something? - ISO image size (3 replies, posted in Vista-Tool)
It's more to it than that, please re-read.
46 2009-03-24 18:58:22
Re: Did I Miss Something? - ISO image size (3 replies, posted in Vista-Tool)
47 2009-03-23 03:40:28
Re: Audio x64 (78 replies, posted in Vista / 7 DriverPack Audio)
Creative Labs Sounblaster PCIe X-Fi (titanium) now official
48 2009-03-21 12:46:34
Re: MassStorage x64 (73 replies, posted in Vista / 7 DriverPack Mass Storage)
Excuse me, but dont dare accuse me of spamming when I made ONE POST about this error less than a day ago! Somebody ELSE also brought this error up. You see, this is what happens when there is a genuine bug, multiple people will report it. What you should do is instead of getting all defensive saying that we are imagining things, is at least take note and make a genuine effort (time permitting) to reproduce the error - which I suspect you have not done as of yet. If you want to reproduce the error, simply run an x64 install with this x64 pack in a x64 VM. I guarantee you will see it.
People who develop these kinds of projects do so with the understanding that there are bugs and that people who report them are doing a SERVICE - not "whining" as you put it. You may not think so but we are very much helping you to improve the only decent Vista unattended integration tool in exisitence.
I understand completely that you have no time to constantly update a huge project like this - a reply from you saying as much is much better than "sorry, dont see it here, tough luck". A project like this most certainly should be an open group project much like XP driverpacks are now. The more people the better - but since this is Vista that will be hard to do since it is such a pariah in the unattended community.
I am not a programmer so the best I can offer you is reporting bugs and specifics on how they are reproduced - and I have quite a few now on Vista-Tools if you would be willing to listen instead of dismiss.
49 2009-03-21 11:46:02
Re: MassStorage x64 (73 replies, posted in Vista / 7 DriverPack Mass Storage)
muiz wrote:
@Fragbert why dont you make the packs instead of whining about things.
I assumed you would make such a one-lined, dismissive and defensive reply. A pity.
50 2009-03-21 08:16:14
Re: MassStorage x64 (73 replies, posted in Vista / 7 DriverPack Mass Storage)
Muiz, in this case and in the past when multiple persons state they have the same specific problem with VistaTool, your response sounds as if the issue is imaginary unless you see it yourself on your PC and you reply with a VERY curt "no problem here, sorry". We appreciate your efforts in putting out driverpacks and the tool - but the attitude you convey when people are reporting bugs is completely the opposite of other contributors to this community.
DriverPacks BASE would never get where it is today if Basharat told everybody with a bug to report that he cant help because he sees no problem on his end.
Specifically for this SI bug, I too notice this on VMs (in addition to my PCs) and since the beauty of a VM is that it elimates any variable's with hardware configuration, this leads me to believe that you have not tested in a VM or bothered to check your control panel in an existing VM.
Food for thought.