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/
I'm changing how we display our property pages for a custom PCI card. Previously we used a co-installer to create the device property pages, but with the recent changes to Microsoft's Hardware Signing Portal, it now rejects the method we were using (Installer32). I've modified the DLL and INF supplied with the driver to use the (EnumPropPages32) way to show the property pages. This works fine with a clean OS never having the driver installed, but when trying to upgrade the driver in the device manager, it will not make any changes in the registry settings created from an older install. I've read online in the Microsoft help pages that if a custom class is already defined in the registry, the [ClassInstall32] section is ignored when a driver is updated. Any AddReg or DelReg entries are ignored under the [ClassInstall32] section. It also looks as though the DelReg directive is deprecated, so making any changes via the INF file is probably not possible.
Basically, I need to delete the registry setting (Installer32) and add a (ClassInstall32) under my driver class with a new DLL and exported function.
Is there a means to do this in the INF file itself, or should this be done by the Installer application?
|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!|
|Kernel Debugging||13-17 May 2024||Live, Online|
|Developing Minifilters||1-5 Apr 2024||Live, Online|
|Internals & Software Drivers||11-15 Mar 2024||Live, Online|
|Writing WDF Drivers||26 Feb - 1 Mar 2024||Live, Online|