Quantcast
Channel: Symantec Connect - ブログエントリ
Viewing all articles
Browse latest Browse all 5094

DS 7.5 - Adding NIC drivers to boot.wim (WinPE 4.0 pre-boot configuration)

$
0
0
X86 - intel i217 and intel i218 manual driver injection
Twitter カードのスタイル: 
summary

Following up from article at link below where we explained how to mount and un-mount boot.wim:

https://www-secure.symantec.com/connect/blogs/ds-7x-mounting-bootwim-file-access-folder-structure-enable-checkaddremove-files-and-folders

In this post, we will go through the process of manually injecting x86 drivers for the network card Intel i217 i218 into boot.wim

1 - First of all we need to prepare the Driver's Folder by cleaning up all the unecessary drivers/files

To see how to pick the correct driver for a specific NIC, and how to do the clean-up please have a look at this article:

(..Under construction...)

 

The final product will look something like this:

300_0.jpg

2 - The above folder is now stored as C:\NDIS63\ 

let's access the command prompt with admin rights and have the boot.wim mounted at folder c:\mount\

125.jpg

3 - to inject the Drivers we run the following command:

DISM /Image:C:\Mount /Add-Driver /Driver:C:\NDIS63 /recurse

128.jpg

4 - the driver e1d6332 has been succesfully injected in the mounted pre-boot environment

129.jpg

5 - It is possible now to un-mount the folder

The pre-boot configuration "boot.wim" is ready for WinPe 4.0 booting on machines with Intel i217 and i218 network cards

For info on how to un-mount the folder, see article below:

https://www-secure.symantec.com/connect/blogs/ds-7x-mounting-bootwim-file-access-folder-structure-enable-checkaddremove-files-and-folders

 

NOTE:

If you found the above information useful, please give this article a thumbs-up (top right of the post) or add a comment below. Your feedback would be really appreciated – Thank you, Mauro


Viewing all articles
Browse latest Browse all 5094

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>