FIRST SOME SIMPLE CHECKS
After an image has been built that includes a custom driver, you can examine the image file to check that the driver file is in the image and that its registry setting are included. You can check these by opening the image file:
1. Go to Solution Explorer.
2. Right-click on the Operating System Project.
3. Choose Show Built Image.
Three branches show: Boot Registry, Registry, and (All Files).
4. Expand the (All Files) branch, and search for the driver DLL file.
5. When the OS is loading, it runs Boot Manager to load the system OAL. During this phase it has a separate set of registry entries: Boot Registry. You can ignore this for now.
6. Expand the Registry branch and find the driver’s registry under HKLM\Drivers\Builtin if it is to be loaded at startup, or under HKLM\Drivers if not. Check that the correct subkey values are in place for the driver.
If the driver file isn’t in the image, check that the driver subproject BIB file is correct, including that it is syntactically correct. If the entries are there, check that the driver should be included in the image. If the registry entries are not included, then check the syntax of the registry file and again check that the driver should be included in the image.
Some of the interim build files in the FlatRelease directory can be useful for determining configuration issues. The Fmerge tool runs once for each parameter file type (BIB, REG, and so on) to create one such file to be built into the image.