Re: [INFO] Microsoft discussion on how driver injection methods work (NT6)

null@example.com (ricktendo64) — Mon, 20 Aug 2012 07:03:42 +0000

Good stuff m_s

Re: [INFO] Microsoft discussion on how driver injection methods work (NT6)

null@example.com (OverFlow) — Fri, 17 Aug 2012 02:50:49 +0000

Exactly... Same as any other PE

some things do remain the same

Re: [INFO] Microsoft discussion on how driver injection methods work (NT6)

null@example.com (mr_smartepants) — Sun, 12 Aug 2012 06:24:56 +0000

...reserved for future expansion...

[INFO] Microsoft discussion on how driver injection methods work (NT6)

null@example.com (mr_smartepants) — Sun, 12 Aug 2012 06:23:37 +0000

Source: http://support.microsoft.com/kb/2686316
Applies to all NT6 OS types (Vista, Win7, Win8, Server2008, Server2012).
Does NOT apply to NT5 OS types (Win2000 thru XP/2003).

This link provides tons of info on different injection methods, their use, and expected outcomes.

Driver Limitations:
Please keep in mind that there are some drivers that can be included and/or loaded that may not be functional during WinPE portion of installation. This would include, but is not limited too; video drivers, wireless adapter drivers, and audio drivers. The behavior described in this document is not specific to BootCritical drivers (drivers need during bootu-p such as controller drivers for access to hard drive) and is in affect for all drivers loaded during installation/deployment.

The above confirms my reasoning that only dpms and possibly DriverPack Chipset & DriverPack LAN are the only packs that should be injected into the boot.wim.

DriverPacks.net Forum - [INFO] Microsoft discussion on how driver injection methods work (NT6)

Re: [INFO] Microsoft discussion on how driver injection methods work (NT6)

Re: [INFO] Microsoft discussion on how driver injection methods work (NT6)

Re: [INFO] Microsoft discussion on how driver injection methods work (NT6)

[INFO] Microsoft discussion on how driver injection methods work (NT6)