Mark xennet.sys as boot-critical to simplify offline installation

Explicitly mark the xennet driver as boot-critical using the
"BootCritical=1" directive.  This causes dism.exe to reflect the
driver when performing an offline installation, thereby making it
available on the next boot (which may be an iSCSI boot, requiring a
functioning network).

This avoids the need to hack the registry to manually install the
driver (by creating the HKLM\CurrentControlSet\Services\xennet key and
corresponding entries in the CriticalDeviceDatabase).

Signed-off-by: Michael Brown <mbrown@fensystems.co.uk>

diff --git a/src/xennet.inf b/src/xennet.inf
index 88317849627b1f77406c043a88d200a5367bc023..d99ffed1ca77d84b2ca94978d3de1401541b2a1c 100644 (file)
--- a/src/xennet.inf
+++ b/src/xennet.inf
@@ -35,6 +35,7 @@ ClassGUID={4d36e972-e325-11ce-bfc1-08002be10318}
 Provider=%Company% 
 CatalogFile=xennet.cat
 DriverVer=01/01/1900,0.0.0.0
+BootCritical=1
 
 [DestinationDirs] 
 DefaultDestDir=12