The device is a normal PCI device that doesn’t fall into one of the built-in vendor categories, so I created its own class that just adds the class name and a default icon to the registry.
It’s my understanding that universal infs cannot contain a ClassInstall32 section, which I use to help define the device class. Is there any way around this to get my inf to conform to the universal requirements?
There is no workaround. Use the system class and life is simple.
Bent from my phone
From: xxxxx@lists.osr.com on behalf of xxxxx@gmail.com Sent: Tuesday, May 2, 2017 8:20:26 PM To: Windows System Software Devs Interest List Subject: [ntdev] Creating an universal inf for a device with a custom class
The device is a normal PCI device that doesn’t fall into one of the built-in vendor categories, so I created its own class that just adds the class name and a default icon to the registry.
It’s my understanding that universal infs cannot contain a ClassInstall32 section, which I use to help define the device class. Is there any way around this to get my inf to conform to the universal requirements?
No, there isn’t really. We don’t apply any class based policy on the system class as it contains a large variety of devices.
Bent from my phone
From: xxxxx@lists.osr.com on behalf of xxxxx@gmail.com Sent: Wednesday, May 3, 2017 12:54:16 AM To: Windows System Software Devs Interest List Subject: RE:[ntdev] Creating an universal inf for a device with a custom class
I’m pretty new to writing INFs for drivers. Is there any downside to classifying it as such?
The downside is that your device won’t appear in a distinct category in Device Manager. If you don’t care… there are no other downsides that I’m aware of.