![]() ![]() Now as some people are pointing out, Microsoft also has a user-mode driver framework which doesn't seem to have the requirements of the kernel module. you need trust from Microsoft, not just the user. ![]() You need to satisfy both for your driver to run, and you can see that MCVR is a requirement for loading a driver on newer Windows versions, i.e. telling the kernel to execute the code immediately). ![]() putting it in the right directory and setting up the settings and everything so that it can be loaded) versus actually loading the driver (i.e. ![]() The distinction being made across the columns is between installing the driver (i.e. It seems like on that page they're referring to the actual binary as the "kernel module" and to the overall package as the "driver package" (not all of which is executable kernel-mode code). If they're for devices, they're called "device drivers" if they're for filtering the file system, they're called "file system filter drivers", etc. I'm not aware of anything called a "kernel module" in the Windows world (despite the name on that page). Yeah I can see why you're confused about the terminology. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |