DriverPacks.net Forum - Integrate drivers to boot.wim or install.wim

Re: Integrate drivers to boot.wim or install.wim

2013-04-18T05:18:32Z

Just a final update on this old question - it's been doing my head in a bit...

The combination of UEFI and mSATA was (is) causing confusion.

Essentially, it seems that disabling secure boot, and enabling CSM (BIOS) mode, plus making sure the Intel RST drivers were available (I stuck them in $WinPEDriver$ folder rather than integrate them) seems to resolve most of the issues I was having.

The only thing unresolved is that I'm almost certain that this machine would boot with the disks ID's different from one boot to the next. Unfortunately having resolved the other parts of this that were confusing me I no longer have access to these machines for testing. I'm certain that sometimes the main HD would be Disk 0, other times it would be Disk 1 which caused some issues with my unattended script.

Bottom line, is that the Driver Packs were not at fault (as usual!) and it was more about understanding the various hardware options on this new machine.

Thanks for your help,
Rod

Re: Integrate drivers to boot.wim or install.wim

2013-01-30T02:53:13Z

Sorry to take a while to update this and thank you for the replies so far.

mr_smartepants - this machine is a beast, and that is part of the problem.

I think the install needs driver packs chipset and mass storage, but also the Intel RST drivers as well. To be honest, though, I'm not absolutely sure. I'm almost there, and will update this post once I'm certain what's going on.

The reason for my confusion is the mSATA drive. This means that the main drive is disk 2, not disk 0 (or even one) so my unattend.xml needs adjusting, too. I've been confusing myself because of the variety of errors and continuing to get errors when everything looks right. Think I'm on top of it now, just got to sort it out.

Do you guys have any suggestions as to how I might create a single unattend.xml file that will always install to the largest available drive or similar no matter how many drives are in the system?

Regards,
Rod

Re: Integrate drivers to boot.wim or install.wim

2013-01-05T05:10:26Z

beefy...

might be interesting to poke around in some files from that crash. it might log a device failure that would put us over the top.

Re: Integrate drivers to boot.wim or install.wim

2013-01-04T18:09:57Z

Yes, try loading DriverPack Chipset to the image and see if that helps.
It's always possible that we're missing some drivers that are required by that hardware.
Wow, that laptop is a beast!

Re: Integrate drivers to boot.wim or install.wim

2013-01-04T17:26:50Z

are you using a flatfile, or loading ISO into RAM?

Also, Windows 7 doesn't support USB 3.0 nativly so you'll need to add chip-set to get USB 3.0 support.

Re: Integrate drivers to boot.wim or install.wim

2013-01-04T12:05:58Z

Happy New Year,
Struck a problem or two, was hoping you might be able to provide some pointers.

The integration process seems to go fine - drivers load with DISM successfully to both BOOT.WIM and INSTALL.WIM. I load them to image 2 in BOOT.WIM and image 3 in INSTALL.WIM (I'm installing Windows 7 Pro). When trying to boot, it gets as far as 'Starting setup' then I get a message about not having drivers for the CD/DVD. I assume that this is actually the USB thumb drive emulating a CD/DVD, but I'm unsure as to why I get the message.

The machine is a brand new Dell Vostro 3560 - USB 3 ports only. BIOS says that the SATA controller is in 'Intel Smart Response Technology' mode, but if I change to AHCI mode it also fails. I don't want to use IDE mode. HWIDs.txt is below, hope that helps.

Thanks,
Rod Clark

===========
PCI Devices
===========
PCI\VEN_8086&DEV_0154&SUBSYS_056E1028&REV_09\3&11583659&0&00: 3rd Gen Core processor DRAM Controller - 0154
PCI\VEN_8086&DEV_0151&SUBSYS_056E1028&REV_09\3&11583659&0&08: Xeon(R) processor E3-1200 v2/3rd Gen Core processor PCI Express Root Port - 0151
PCI\VEN_8086&DEV_1E12&SUBSYS_056E1028&REV_C4\3&11583659&0&E1: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 2 - 1E12
PCI\VEN_8086&DEV_1E2D&SUBSYS_056E1028&REV_04\3&11583659&0&D0: Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E2D
PCI\VEN_8086&DEV_1E57&SUBSYS_056E1028&REV_04\3&11583659&0&F8: Intel(R) HM77 Express Chipset LPC Controller - 1E57
PCI\VEN_8086&DEV_1E14&SUBSYS_056E1028&REV_C4\3&11583659&0&E2: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 3 - 1E14
PCI\VEN_8086&DEV_1E26&SUBSYS_056E1028&REV_04\3&11583659&0&E8: Intel(R) 7 Series/C216 Chipset Family USB Enhanced Host Controller - 1E26
PCI\VEN_1002&DEV_6840&SUBSYS_056E1028&REV_00\4&222499E&0&0008: AMD Radeon HD 7670M
PCI\VEN_8086&DEV_1E20&SUBSYS_056E1028&REV_04\3&11583659&0&D8: High Definition Audio Controller
PCI\VEN_8086&DEV_0166&SUBSYS_056E1028&REV_09\3&11583659&0&10: Intel(R) HD Graphics 4000
PCI\VEN_8086&DEV_1E31&SUBSYS_056E1028&REV_04\3&11583659&0&A0: Intel(R) USB 3.0 eXtensible Host Controller - 0100 (Microsoft)

PCI\VEN_8086&DEV_1E3A&SUBSYS_056E1028&REV_04\3&11583659&0&B0: Intel(R) Management Engine Interface
PCI\VEN_8086&DEV_282A&SUBSYS_056E1028&REV_04\3&11583659&0&FA: Intel(R) Mobile Express Chipset SATA RAID Controller
PCI\VEN_8086&DEV_1E10&SUBSYS_056E1028&REV_C4\3&11583659&0&E0: Intel(R) 7 Series/C216 Chipset Family PCI Express Root Port 1 - 1E10
PCI\VEN_8086&DEV_0887&SUBSYS_44628086&REV_C4\4&39DE1E7E&0&00E1: Intel(R) Centrino(R) Wireless-N 2230
PCI\VEN_10EC&DEV_8168&SUBSYS_056E1028&REV_07\4&11540BE9&0&00E0: Realtek PCIe GBE Family Controller
PCI\VEN_8086&DEV_1E22&SUBSYS_056E1028&REV_04\3&11583659&0&FB: Intel(R) 7 Series/C216 Chipset Family SMBus Host Controller - 1E22
17 matching device(s) found.

===========
USB Devices
===========
USB\VID_8087&PID_0024\5&356A24C6&0&1 : Generic USB Hub
USB\VID_138A&PID_0011\ED4EF930C5CC : Validity Sensor
USB\VID_1BCF&PID_2895&MI_00\7&5E81193&0&0000 : Integrated Webcam
USB\VID_8087&PID_0024\5&1C9C9BE1&0&1 : Generic USB Hub
USB\ROOT_HUB30\4&27D251BD&0&0 : USB Root Hub (xHCI)
USB\VID_8087&PID_07DA\6&2D3B92E5&0&5 : Intel(R) Centrino(R) Wireless Bluetooth(R) 4.0 + High Speed Adapter
USB\ROOT_HUB20\4&A977F4A&0 : USB Root Hub
USB\ROOT_HUB20\4&58B0204&0 : USB Root Hub
USB\VID_1BCF&PID_2895\6&39DBDB0D&0&5 : USB Composite Device
USB\VID_0BDA&PID_0129\20100201396000000 : Realtek USB 2.0 Card Reader
10 matching device(s) found.

=============
Input Devices
=============
No matching devices found.

============
ACPI Devices
============
ACPI\PNP0C01\2 : System board
ACPI\PNP0C02\1 : Motherboard resources
ACPI\PNP0C02\2 : Motherboard resources
ACPI\INT0800\4&37011F08&0 : Intel(R) 82802 Firmware Hub Device
ACPI\PNP0C0A\1 : Microsoft ACPI-Compliant Control Method Battery
ACPI\DLL056E\4&37011F08&0 : Dell Touchpad
ACPI\PNP0C09\4&37011F08&0 : Microsoft ACPI-Compliant Embedded Controller
ACPI\PNP0100\4&37011F08&0 : System timer
ACPI\PNP0C14\0 : Microsoft Windows Management Interface for ACPI
ACPI\PNP0103\0 : High precision event timer
ACPI\PNP0C0D\2&DABA3FF&1 : ACPI Lid
ACPI\INT3392\2&DABA3FF&1 : Intel(R) Rapid Start Technology Device
ROOT\ACPI_HAL\0000 : ACPI x64-based PC
ACPI\PNP0A08\0 : Pci Bus
ACPI_HAL\PNP0C08\0 : Microsoft ACPI-Compliant System
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_1: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_2: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_3: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_4: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_5: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_6: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_7: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\GENUINEINTEL_-_INTEL64_FAMILY_6_MODEL_58_-_______INTEL(R)_CORE(TM)_I7-3632QM_CPU_@_2.20GHZ\_8: Intel(R) Core(TM) i7-3632QM CPU @ 2.20GHz
ACPI\PNP0B00\4&37011F08&0 : System CMOS/real time clock
ACPI\DLLK056E\4&37011F08&0 : Standard PS/2 Keyboard
ACPI\PNP0000\4&37011F08&0 : Programmable interrupt controller
ACPI\PNP0C0C\4&37011F08&0 : ACPI Power Button
ACPI\FIXEDBUTTON\2&DABA3FF&1 : ACPI Fixed Feature Button
ACPI\INT3F0D\4&37011F08&0 : Motherboard resources
ACPI\PNP0200\4&37011F08&0 : Direct memory access controller
ACPI\ACPI0003\4&37011F08&0 : Microsoft AC Adapter
ACPI\INT340E\2&DABA3FF&1 : Motherboard resources
ACPI\PNP0C04\4&37011F08&0 : Numeric data processor
ACPI\SMO8810\1 : STMicroelectronics 3-Axis Digital Accelerometer
34 matching device(s) found.

============
HDA Audio
============
HDAUDIO\FUNC_01&VEN_8086&DEV_2806&SUBSYS_80860101&REV_1000\4&1FF2F789&0&0301: Intel(R) Display Audio
HDAUDIO\FUNC_01&VEN_14F1&DEV_506E&SUBSYS_1028056E&REV_1000\4&1FF2F789&0&0001: Conexant SmartAudio HD
2 matching device(s) found.

============
RAID Devices
============
PCI\VEN_8086&DEV_282A&SUBSYS_056E1028&REV_04\3&11583659&0&FA
Name: Intel(R) Mobile Express Chipset SATA RAID Controller
Hardware ID's:
PCI\VEN_8086&DEV_282A&SUBSYS_056E1028&REV_04
PCI\VEN_8086&DEV_282A&SUBSYS_056E1028
PCI\VEN_8086&DEV_282A&CC_010400
PCI\VEN_8086&DEV_282A&CC_0104
Compatible ID's:
PCI\VEN_8086&DEV_282A&REV_04
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.

Re: Integrate drivers to boot.wim or install.wim

2012-12-20T18:28:27Z

You got it! Good luck.

Re: Integrate drivers to boot.wim or install.wim

2012-12-20T06:27:33Z

Thanks for the quick and concise response, really appreciate the help you give.

Those answers confirm what I thought was the case so I'll:

1. Use DISM to add Mass Storage and Chipset to BOOT.WIM
2. Use DISM to add Mass Storage, Chipset, LAN and probably WLAN to INSTALL.WIM
3. Use you SAD2 script or manual downloads to handle the rest

That should be the most efficient in all respects for my needs.

Thanks again,
Rod

Re: Integrate drivers to boot.wim or install.wim

2012-12-20T05:59:20Z

Merry Christmas to you too.

Rambo wrote:

1. Since the Chipset drivers seem to be the ones that contain USB 3 drivers, won't I need to add those to BOOT.WIM as well as the Mass Storage ones?

Yes. We typically recommend users only integrate dpms into boot.wim but in reality you can integrate whatever you want (Chipset, LAN, etc.). But keep in mind that the more drivers you integrate into the boot.wim, the LONGER the boot process will take as ALL those drivers are loaded into RAM. In the past, some users went through the ridiculous process of loading ALL the DriverPacks into the boot.wim. While that would work, it would be very stupid.

Rambo wrote:

2. Do drivers added to BOOT.WIM 'carry over' to INSTALL.WIM and the final installation, or is it necessary to add Mass Storage (and possibly Chipset) to both WIM files?

No. Drivers added to boot.wim only allow the installation utility to "see" the installation target (hard drive) or sources (DVD, USB, network share, etc.). If a driver is needed by the system to "see" a drive controller, and the driver is only loaded into the boot.wim, then the installation (file copy stage) will go OK, but you'll likely get a BSOD during the later stages when no driver is found and the installer can't find the drive anymore.

Integrate drivers to boot.wim or install.wim

2012-12-20T04:56:10Z

Firstly, a Merry Christmas to all at DriverPacks.net

I'm about to update my Win 7 deployment DVD/USB and planning on using DISM to integrate drivers, rather the the $WinPEDriver$ method I've used in the past. I need to make sure that booting from a USB 3 attached thumb drive or DVD will work.

Looking around here, the advice seems to be to use DISM to add Mass Storage to BOOT.WIM, then others such as Chipset, LAN, WLAN (I think that's all I need) to INSTALL.WIM - I know about getting the indexes correct...

My questions are:
1. Since the Chipset drivers seem to be the ones that contain USB 3 drivers, won't I need to add those to BOOT.WIM as well as the Mass Storage ones?

2. Do drivers added to BOOT.WIM 'carry over' to INSTALL.WIM and the final installation, or is it necessary to add Mass Storage (and possibly Chipset) to both WIM files?

Thanks,
Rod