Great!Helpful..

No argument here, I used his article several times..Recently used the "uncheck retain matching PnP" bit to good effect on a stubborn driver.

"what to do in youur pakcage if Windows only wants to recognize its own driver for the device you are creating the package for" [:D]

But, I believe the part I quoted is in error.  I have yet to get a definitive answer from Microsoft. Or find official MSDN documentation to confirm it.  But I recently created a package that used subdirectories.  On a conference call wtih the vendor, they told me if you alter the inf file it breaks the signing.  Experimentation confirmed that.

Cheers,

I worked with Jezza at Liverpool Victoria in Croydon, Surrey, UK. Nice guy, great packager.

Bob, this is in error.  In fact, if you modify the INF file it will BREAK the code signing.  As far as I can tell, the inf file works fine and the drivers are recognized regardless of folder structure - assuming of course that it is a legit signed driver and the INF file is correct. 

The rest of the article is right on, though. Very helpful. 

Tip: Some drivers have several different folders containing the relevant files. If this appears to be the case, check the entries of the .inf file to see if there are references to files in a subfolder(s). 

If so, you may need to modify the file path entries in the .inf file, to allow all the files to be in ONE root folder.

All files for a specific driver need to be in one root folder along with the .inf file for a successful installation via DifX.