-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make most driver packages isolated #12
Labels
enhancement
New feature or request
Comments
dep2.txt |
gus33000
changed the title
Make most driver package isolated
Make most driver packages isolated
Feb 23, 2021
Current status for dependencies as of 2021-03-16
|
Current non isolated files
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Because of WCOS and newer guidelines from Microsoft, drivers should now be isolated.
An isolated driver is a driver whose files are only present in driverstore, and whose registry entries are loaded using standard mechanisms by loading it under HKR () only, and not hardcoded paths.
For most drivers, the conversion process only requires changing the destination folder to "13", which is the DriverStore id, and adjusting copy paths, and service paths.
Some other drivers however hardcode registry paths, or use Loadlibrary to an extent the driver store folder wouldn't be visible in path.
Additionally, driver packages must not rely on external libraries not present under Windows, and MSVC. These libraries thus need to be bundled with the corresponding driver to eliminate issues.
The text was updated successfully, but these errors were encountered: