Does anyone know if it is possible to force Windows XP (x86/x64) to treat signed and unsigned drivers equally, and not prefer a signed driver over an unsigned one?
I know it is possible to disable signature enforcement and stop the warning popups and such, this is not what I need. I need Windows to stop automatically preferring a signed "generic" (device ClassCode [CC] INF entry) driver over an unsigned "specific" (device [VEN&DEV] INF entry) driver.
I'm trying to manually slipstream motherboard chipset drivers into XP setup.. and the 250+ tiny INF and associated CAT files supplied by the OEM drive me nuts. 
So I decided to build a single compiled INF file, similar to what I did for my Windows 9x Chipset INFs. Which is fine, except that it is unsigned, while XP's MACHINE.INF is signed. So Setup refuses to use my INF for, say, the PCI-E Root Ports, because it has a generic Class Code entry for these in MACHINE.INF, and uses it with generic names. But it does pick up my INF for the SMBus controller and gives it its proper name, because no other driver matches it. This is maddening... 
Yes, I can manually force the use of the specific unsigned driver on the other devices through the device manager after the desktop is reached, but this defeats the purpose of having the driver slipstreamed to begin with. I can also edit MACHINE.INF with the new data and break its signature in the process.. but this leads to other dumb behavior, such as popups about "Terminal Server" device drivers during SETUP that require user interaction and break the unattended process.