I’m not sure where to go next.
One of my clients has a series of USB video cameras that are not
UVC-compliant. I did custom drivers for them a decade ago. We’ve been
through the WHQL process twice in that time, and are now trying again. Â
The driver passed the HCK for Windows 7 and 8.1 with no problems, but
the HLK for Windows 10 gets five test failures, all apparently with the
same root cause. They create a Media Foundation topology, and when they
call StartPreviewAsync, they’re getting an 80004001, saying that an
interface is not implemented. The camera works just fine in the Camera
app (which use MF), and the CHAOS video capture tests all pass. And
it’s not like there’s a list somewhere saying "here are the property
sets that a driver must implement in order to pass WHQL."Â There should
be, but there isn’t.
In an ideal world, I’d like to find the source code for the video tests
somewhere to see what interface they’re asking for, but I doubt that the
new openness in Redmond goes quite that far yet. Any clues welcome.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
You know SOME of the WHQL tests DO have source code available. It might be VBScript though. I think it was stored in some subdirector on the HLK controller machine. I know this was the case some of the networking tests.
Jan
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@probo.com
Sent: Friday, February 2, 2018 6:08 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] HLK Troubles
I’m not sure where to go next.
One of my clients has a series of USB video cameras that are not UVC-compliant. I did custom drivers for them a decade ago. We’ve been through the WHQL process twice in that time, and are now trying again. The driver passed the HCK for Windows 7 and 8.1 with no problems, but the HLK for Windows 10 gets five test failures, all apparently with the same root cause. They create a Media Foundation topology, and when they call StartPreviewAsync, they’re getting an 80004001, saying that an interface is not implemented. The camera works just fine in the Camera app (which use MF), and the CHAOS video capture tests all pass. And it’s not like there’s a list somewhere saying “here are the property sets that a driver must implement in order to pass WHQL.” There should be, but there isn’t.
In an ideal world, I’d like to find the source code for the video tests somewhere to see what interface they’re asking for, but I doubt that the new openness in Redmond goes quite that far yet. Any clues welcome.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
—
NTDEV is sponsored by OSR
Visit the list online at: http:
MONTHLY seminars on crash dump analysis, WDF, Windows internals and software drivers!
Details at http:
To unsubscribe, visit the List Server section of OSR Online at http:</http:></http:></http:>
In my experience, this is EXACTLY the kind of problem that you can get help from the WHQL folks on. They have, or at least USED to have, actual test devs who would field these questions and provide reasonable answers.
Peter
OSR
@OSRDrivers