The free OSR Learning Library has more than 50 articles on a wide variety of topics about writing and debugging device drivers and Minifilters. From introductory level to advanced. All the articles have been recently reviewed and updated, and are written using the clear and definitive style you've come to expect from OSR over the years.
Check out The OSR Learning Library at: https://www.osr.com/osr-learning-library/
Production Level : The unwashed masses of classroom environments.
OS: Windows 10 Pro
I have a few diskless windows 10 clients booting from ipxe and iscsi. It's kind of awesome and extremely niche use case. I would like to know how setup.exe forces the nic driver to a boot critical start type? To clarify the inf is not that start type. Can anyone better explain what reflected into the image means? In the case of boot critical drivers? I'm not sure that's the same path iscsi follows. But it seems close.
is there a way to manually do this using dism/winpe to an already imaged (sysprep'd) volume? I am trying to NOT have to use setup.exe to accomplish the same thing.
Reason is backend is block storage. Setup.exe is the only way I know of to apply an image to be iscsi bootable. But that's now a full installation that's block unique. My hope is to have a single master sysprep'd image and a differencing image per client. Saves 18gb per client.
At this point I'd like to ask for books, terminology corrections, further reading, and anything else to understand the initia driver load boot process.
|Upcoming OSR Seminars|
|OSR has suspended in-person seminars due to the Covid-19 outbreak. But, don't miss your training! Attend via the internet instead!|
|Internals & Software Drivers||7 February 2022||Live, Online|
|Kernel Debugging||21 March 2022||Live, Online|
|Developing Minifilters||23 May 2022||Live, Online|
|Writing WDF Drivers||12 September 2022||Live, Online|