Re: Requirements or Restrictions using "Imaging Device" in Windows Driver Manager
- From: David.C.Reaves@xxxxxxxxx
- Date: Sat, 9 Aug 2008 10:49:51 -0700 (PDT)
On Aug 8, 8:56 pm, Tim Roberts <t...@xxxxxxxxx> wrote:
David.C.Rea...@xxxxxxxxx wrote:
We have created a digital camera for a specific customer who requires
that the camera display an icon in Windows Device Manager under
"Imaging Devices". We can accomplish this using the "Imaging Device"
GUID in the INF file ( GUID = {6bdd1fc6-810f-11d0-
bec7-08002be2092f} ).
That's what I tend to use for web cameras, because you do inherit automatic
WIA support.
However, the camera does not support WIA and is
not intended to be a "Still Image" camera.
Doesn't matter; Windows will provide automatic WIA and TWAIN support, and
will actually allow applications to grab snapshots from the stream.
If you really don't want it to be exposed in Scanners and Cameras, you can
choose to put it in Media class instead of Image class:
Class=Media
ClassGUID={4d36e96c-e325-11ce-bfc1-08002be10318}
If we submit the device to
USB-IF for compliance testing, will this cause a problem?
USB-IF doesn't test the functionality of your device. They won't use the
driver at all. They're going to test your electrical compliance, your
descriptors, your response to power states and resets, etc.
Did you really mean WHQL testing?
Are there any other restrictions/requirements for devices that use
this location in Driver Manager?
Not really, no.
--
Tim Roberts, t...@xxxxxxxxx
Providenza & Boekelheide, Inc.
Hi and thanks for the reply,
If you really don't want it to be exposed in Scanners and Cameras, you can
choose to put it in Media class instead of Image class:...
Our customer specifically requires us to use the Image class.
Doesn't matter; Windows will provide automatic WIA and TWAIN support, and
will actually allow applications to grab snapshots from the stream.
Our driver package (a user mode DLL and the generic Cypress kernel
mode driver CyUsb.sys) has a
proprietary API used only by the customer. There are is no TWAIN
support (nor streams available
to other applications).
Did you really mean WHQL testing?
Well, our main goals are to be USB-IF certified and to get the driver
package signed so that we
can perform a "silent" installation without the annoying "not signed"
or "not Windows Logo..." dialog
boxes appearing. We DO NOT need to be Windows Logo compliant.
However, it seems that to get the packaged signed we need WHQL
certification as well as a certificate from
an entity like Verisign (which we have). Correct me if I am wrong,
but this may not be as onerous as it once was:
1. We can perform the WHQL testing in-house using the Driver Test
Manager (DTM).
2. We then email the results to Microsoft (for ~$250.00 !!!!).
3. If the tests pass, we will be emailed the proper certificates to
allow our package to be signed.
If this is incorrect, please let me know!
In addition, there is something called an "unclassified signature".
Will this allow us to use the Image class without
needing to support WIA/STI?
Thanks,
DCR
Dave
.
- Follow-Ups:
- References:
- Requirements or Restrictions using "Imaging Device" in Windows Driver Manager
- From: David . C . Reaves
- Re: Requirements or Restrictions using "Imaging Device" in Windows Driver Manager
- From: Tim Roberts
- Requirements or Restrictions using "Imaging Device" in Windows Driver Manager
- Prev by Date: Re: NDIS_PACKET_8021Q_INFO
- Next by Date: Re: NDIS marshalling pointers
- Previous by thread: Re: Requirements or Restrictions using "Imaging Device" in Windows Driver Manager
- Next by thread: Re: Requirements or Restrictions using "Imaging Device" in Windows Driver Manager
- Index(es):
Relevant Pages
|
