I am wondering if there is a creative solution to a problem I am trying to solve. I have a Win10 RE based bootable USB stick that can boot couple of Lenovo laptops fine. I have figured out a way to get wifi networking work on this stick. I managed it by injecting all necessary drivers needed by these laptops pre-injected offline in the boot.wim.
Now I am trying to create this stick for 10 other laptop models. Dell and Hp. I have driver packages for each model.
I don't want to pre-inject drivers into the wim. I like to maintain a common boot.wim and a separate folder with model specific drivers. Then when boot.wim becomes a ramdisk during bootup, somehow make the driver folder visible inside the ramdisk (i.e x:\ drive). Then I have a batch file that knows how to load necessary drivers on the fly.
My question is if there is a way to make a folder outside of boot.wim but available on the usb stick become available inside the ramdisk.
I am aware of enumerating available drives in .bat file and look for drivers. That is not an option that works for the scenario I am trying to solve. For the sake brevity, I am not including all those details in this post.
To solve this issue, I started looking at various options. I find that boot.sdi is a mechanism that ramdisk driver uses to create the ramdisk. I also found that boot.sdi is a hollow container that fakes ntfs file system with links to boot.wim. When the boot loader efi application loads the .sdi file, it knows how to get to boot.wim and make it whole. I am wondering if there is a way to create boot.sdi that points to the wim as well as my folder.
I appreciate any pointers.
Edited by videoguy, 11 October 2017 - 05:05 PM.