By now, hopefully you’ve read Part 1 of this article series, which introduced you to IBW and its basic concepts.
In this article, we’ll be going slightly deeper to try out the more advanced route in IBW.
We’re going to jump right back into creating an image with IBW. To help jog your memory, here’s a brief walkthrough. If you were following the steps from the previous blog article, this should be pretty familiar. If you haven’t yet read part one, please check it out here.
Note that one modification from the previous article is that we’re going to check the Modify Drivers and Modify Features checkbox on the summary screen. For this demo, we’re going to modify the template we started from by adding drivers and features to it.
Hardware to Driver Mapping
Selecting Modify Drivers brings up the above screen, which allows you to choose the type of hardware to driver mapping you would like. When starting from a template, IBW chooses the Automatically detect devices option for you by default, which is why drivers mapped appeared in the previous summary screen. You can change this option by following the below:
- Automatically detect devices
IBW will automatically detect the hardware on the target device and map drivers to the detected hardware.
- Choose a PMQ
If you ran TAP.exe on another device, you can import the PMQ file here to have the drivers for that device installed.
- Do not select additional drivers
IBW will remove the automatically detected drivers and you won’t have the option to add any other drivers.
For this walkthrough, I’ll select Automatically detect devices and click next.
The following screen lists your unmapped devices (hardware that we detected but don’t have drivers for), and any internal or 3rd party drivers that will be installed.
If you’d like to add drivers for unmapped devices or if you’d like to add other miscellaneous drivers to your image, you can do so by clicking the Add Drivers button.
Feature Package Selection
Because we clicked the Modify Features checkbox back on the summary screen, we’re brought to this page that allows us to add or remove packages.
Because we started with a template, the packages specified in the template have been checked for us. If you want to add or remove packages, you can check or uncheck their corresponding boxes. If you want to go back to the original template, you can click the Revert to original button at the top.
If any packages are added to or removed from the template, you need to Resolve Dependencies. This examines the packages in current configuration and adds in any other packages that are necessary for them to function. You can check or uncheck the Resolve optional dependencies checkbox to specify whether you’d like optional dependencies in your configuration. An example of an optional dependency relationship might be the help files for Internet Explorer. Internet Explorer will work fine without the help files, and you may or may not want them depending on your needs.
When you click the Resolve Dependencies button, you may get a popup that asks you to choose between a few packages. In this case, I’ve accidentally chosen both the Command Prompt and Windows Explorer as my default shell. Because these two packages can’t both be the default, I have to choose between them.
Once you’ve resolved all of your conflicts, you’re brought back to the feature package selection screen. If you’re happy with everything, you can click Next to move on.
This summary screen gives you a final overview of what will be installed in your image. If you’re happy with everything, click Next to move on to disk selection. If you do want to change something, you can click the back button (blue arrow at the top left of the screen).
After clicking Next on the summary screen, you arrive at the Disk Selection screen, which was discussed in IBW Part I. Select the disk or partition you’d like to install, click Next, and you’re installing!
If you have any questions or comments about IBW, feel free to post a comment on this blog, and I’ll get back to you.
Thanks for reading, and look for more advanced blog articles on IBW in the near future!