My company uses an in-house built UMDF USB driver to drive their imagesetter interface devices for 32 and 64 bit operating systems from Windows XP thru Windows Server 2008 R2.
The driver is now at a point where we need to get it WHQL certified so that we can sign it to enable silent installation on customer machines.
I have a VeriSign certificate and a WinQual account, and have been trawling my way through the WinQual site looking for information about what tests I have to run for the WHQL submission package without much success.
I have a couple of questions:
- Is there an ‘Idiot’s Guide’ for getting WHQL certification for a UMDF Usb driver?
If not, can anybody point me the appropriate URLs to go to for information.
- My hardware only connects to the PC via a USB cable.
Do I need to get it certified too and does it need to also pass WLK certification?
If so is there an Idiots Guide for this.
Thanks in advance,
Peter Young
Supplementary question.
My device is an imagesetter interface which communicates with the host via a USB cable.
Which WHQL category does my device fall under?
> have been trawling my way through the WinQual site looking for
information about what tests I have to run for the WHQL
submission package without much success.
All that are in DTM Studio’s Device Console when you choose your submission.
If this is in-house and you have a verisign cert you can ‘release
sign’ your drivers and just skip WHQL entirely. See the kernel code
signing walkthrough section on release signing drivers.
Mark Roddy
On Thu, Feb 24, 2011 at 5:04 AM, wrote:
> My company uses an in-house built UMDF USB driver to drive their imagesetter interface devices for 32 and 64 bit operating systems from Windows XP thru Windows Server 2008 R2.
> The driver is now at a point where we need to get it WHQL certified so that we can sign it to enable silent installation on customer machines.
>
> I have a VeriSign certificate and a WinQual account, and have been trawling my way through the WinQual site looking for information about what tests I have to run for the WHQL submission package without much success.
>
> I have a couple of questions:
> 1. Is there an ‘Idiot’s Guide’ for getting WHQL certification for a UMDF Usb driver?
> ? ?If not, can anybody point me the appropriate URLs to go to for information.
> 2. My hardware only connects to the PC via a USB cable.
> ? ?Do I need to get it certified too and does it need to also pass WLK certification?
> ? ?If so is there an Idiots Guide for this.
>
> Thanks in advance,
> Peter Young
>
> —
> NTDEV is sponsored by OSR
>
> For our schedule of WDF, WDM, debugging and other seminars visit:
> http://www.osr.com/seminars
>
> To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>
xxxxx@vgieurope.com wrote:
I have a VeriSign certificate and a WinQual account, and have been trawling my way through the WinQual site looking for information about what tests I have to run for the WHQL submission package without much success.
I have a couple of questions:
- Is there an ‘Idiot’s Guide’ for getting WHQL certification for a UMDF Usb driver?
If not, can anybody point me the appropriate URLs to go to for information.
There’s a little bit of philosophy, and a lot of procedure.
Philosophically, you just need to understand that YOU are doing all the
work. You run the tests, you package the results up, and you send them
to WHQL. WHQL simply checks that the tests all passed, signs the CAT
file, and returns that to you. They never even load your driver.
Procedurally, that first step (“run the tests”) is were the pain lies.
There is a very good white paper called “How to Use DTM for Windows
Vista System Logo Testing” that proved to be invaluable to me:
http://msdn.microsoft.com/en-us/windows/hardware/gg487486.aspx
The white paper describes whole-system testing; you’ll have to
interpolate a little to do single-device testing. It took me a half a
week of reading, cogitating, and experimenting before I felt ready to
start, but once I dug in, the process wasn’t all that bad.
- My hardware only connects to the PC via a USB cable.
Do I need to get it certified too and does it need to also pass WLK certification?
If so is there an Idiots Guide for this.
The only think WHQL certifies is your driver. If your device falls into
one of the pre-defined classes, then your WHQL submission will also earn
you the right to use the Windows logo in your marketing materials. If
not, then you will file as an “unclassified” device, which cannot use
the logo.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
xxxxx@vgieurope.com wrote:
Supplementary question.
My device is an imagesetter interface which communicates with the host via a USB cable.
Which WHQL category does my device fall under?
The category is determined by what interfaces your driver exposes. What
“Class” do you specify in your INF? Do you expose a standard printer
interface? If so, then you’d be in the printer category. Do you have a
strictly custom interface, talking to your own custom software? If so,
then you are “unclassified”.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
Tim,
My device has a two-stage driver installation process.
The first stage INF is a USB class device but this is for the firmware loading and renumeration.
The second stage INF is a custom class so I am guessing that ‘unclassified’ is the right category.
I had come to this conclusion myself, but thank you for the confirmation.
–
Peter Young, xxxxx@vgieurope.com
VGI Europe
xxxxx@vgieurope.com wrote:
My device has a two-stage driver installation process.
The first stage INF is a USB class device but this is for the firmware loading and renumeration.
The second stage INF is a custom class so I am guessing that ‘unclassified’ is the right category.
I had come to this conclusion myself, but thank you for the confirmation.
You can do both of those in the same INF file. Your firmware loader has
an extremely short lifetime, so it doesn’t really matter where it ends up.
The Class=USB category was intended for host controllers and hubs, not
for “generic” USB devices.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.