November 11, 2003

DevCon:How to Logo a Cool New Invention

Writing neat new security stuff that doesn't "fit" with Microsoft's standard tests for logo requirements (ie: "Designed for Windows") means I am forced to figure out other ways to get "logo"ized. Fortunately Microsoft realizes this drawback for developers like me, and has created a session for this.

That's why I am here. Apparently its something others care about as well, since they got a BOAT LOAD of TV equipment taping it.

There isn't much to blog about here, since its really just discussion on what the requirements are to "classify" a device, as well as the process of "testing" it through WHQL.

There is a really kewl new prototype program called "Code Coverage" for certifying devices that require no hardware, and doesn't fit in the "anti-virus" or "firewall" category. I am not sure if I can blog about it, so will have to refrain until I can talk to someone in the know and who can tell me if I can talk about it.

Some notes:


  • Use a multi-processor (or Hyper-Threading) system for testing
  • Enable Driver Verifier while running all test tools
  • Don't leave KdPrint() statements in retail driver (personal note: I can relate to this... VMWare drives me nuts in WinDbg with their mouse KdPrints that shouldn't be there!)

Posted by SilverStr at November 11, 2003 11:05 AM | TrackBack