As I understand it, it works like this:
You can use your WHQL signing key to test-sign your components and add the
"Microsoft Test Root Authority" signing certificate to the "trusted root
authorities" certificate store on your test system.
This will then cause PUMA to load the component, but in "test mode."
Apps that pass the "allow test mode" flag (test apps) will then work.
(Apps that have access to real-live production content [production apps]
will *not* pass the flag, and the APIs will [correctly] fail.)
Once everything is tested and working you can submit through WHQL, sign
the relevant contracts (Exhibit B), and get a "real" signature.
Production apps will then work with your components even with production
content.
For an example of passing a "test mode" flag (in this case, to the Trusted
Audio Drivers system) see:
http://blogs.msdn.com/b/matthew_van_eerde/archive/2009/11/10/how-to-turn-on-hdcp-or-scms-in-an-audio-playback-app.aspx
-----Original Message-----
From: wdmaudiodev-bounce@xxxxxxxxxxxxx
[mailto:wdmaudiodev-bounce@xxxxxxxxxxxxx] On Behalf Of e-t172
Sent: Monday, September 27, 2010 2:27 PM
To: wdmaudiodev@xxxxxxxxxxxxx
Subject: [wdmaudiodev] Re: Problem with test signed driver package
On 27/09/2010 23:22, Paul Titchener wrote:
So this means that there is no way to fully test an APO before you
submit it for logo certification?
That seems to be a pretty severe restriction, is that really true?
