gotenks98 Posted November 18, 2011 Share Posted November 18, 2011 I just wanted to ask if anyone does this. What I wanted to do is inject the drivers there in hopes that the boot.wim file will pass on the needed drivers to the windows install so that after first logon a machine has everything it needs. If this is the case will it pass on what is needed or will it do everything? Link to comment Share on other sites More sharing options...
iamtheky Posted November 18, 2011 Share Posted November 18, 2011 (edited) like this*this is assuming windows 7 and these drivers are signed. Edited November 18, 2011 by iamtheky Link to comment Share on other sites More sharing options...
jaclaz Posted November 19, 2011 Share Posted November 19, 2011 For the record contents of code boxes at reboot.pro are botched.This:http://reboot.pro/15275/http://pastehtml.com/view/b4t99xk89.htmlMay be of use .jaclaz Link to comment Share on other sites More sharing options...
gotenks98 Posted November 20, 2011 Author Share Posted November 20, 2011 Not sure what reboot pro has to do with this, I am talking about just regular windows installations. Its alot easier to update boot.wim than it is to update install.wim. One image versus doing 4+ depending on the disc. I have tried the $drivers$ thing or whatever the sentax is, it does not always work well where as with dism you know right away if drivers are going to work or not. I just need to know the expected behavior of how windows handles the drivers from install to post install. Link to comment Share on other sites More sharing options...
ricktendo Posted November 20, 2011 Share Posted November 20, 2011 I dont think (dont quote me on this) boot.wim passes the drivers to the main Windows install Link to comment Share on other sites More sharing options...
cluberti Posted November 20, 2011 Share Posted November 20, 2011 It does not - boot.wim uses injected drivers only during it's own load (of WinPE). If you want drivers injected into the installed OS, you need to either inject them into the install.wim (and index) of the version of Windows you're installing, or use other methods like those described on Technet. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now