> I heard that under this OS, WDF device drivers must be certified.
There are 2 absolutely different requirements:
a) on on x64 Vista+ OSes, the kernel-mode binaries must be digitally signed, or they will not load.
Solution: your company should purchase Verisign or Globalsign code signing cert with KMCS support, then you should study the signing procedure (google for KMCS) and do this, probably as a part of the build process.
b) since w2k up, drivers installed by INF files must have the whole driver package signed by the WinQual team in Redmond, or they will show nasty dialogs on install.
You can avoid to sign the package at all, this will make the red dialog. Or, you can sign it without WinQual with your own cert (from step “a” above or such), this will make the yellow dialog of “Do you trust software from this company”?
The dialog can only be answered by interactively logged-on admin. Otherwise, the driver package install fails.
After the driver package is installed to driver store, no more checks are made.
Pre-Vista, this dialog cannot be suppressed at all. On Vista+, this dialog can be suppressed by installing your cert to Trusted Publishers. More so, the yellow dialog described above has the checkbox of “always trust”, which does exactly this.
To sign with WinQual, you need to a) deploy DTM b) run DTM tests over your driver c) save their logs d) open WinQual account e) pay some small money to MS f) submit your driver package with DTM logs to WinQual.
Usually, WinQual is an issue only for mass-market devices. If your device is a part of some vertical solution to a narrow market - then probably the yellow dialog (or the requirement to preinstall your cert to Trusted Publishers) is OK.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com