Prev: INF for Ports class CDC USB device using usbser.sys fails DTM
Next: Access permission for registry in Windows 7
From: Elliot on 22 Apr 2010 19:38
We are starting to switch to Microsoft's WinUSB.sys device driver for
some of our USB devices. We access the driver thru WinUSB.dll . To get our
driver 'signed' so that the user does not see any warnings on Vista and
Windows 7 when the USB device is plugged in, it looks like we have to submit
a driver package to WHQL in order to get a signed catalog file back from
Microsoft.

Our .inf file contains our USB vid/pid and refers to WinUSB.sys .
So...apparently, we need to submit a driver package with .inf and .cat files
and test logs for our device to WHQL even though WinUSB.sys came from
Microsoft.

Is my understanding of the situation correct?
From: Doron Holan [MSFT] on 23 Apr 2010 18:38
correct, you need to get the INF, CAT and all of the coinstaller DLLs
submitted as a packge so you can get them signed

d

--

This posting is provided "AS IS" with no warranties, and confers no rights.


"Elliot" <Elliot(a)discussions.microsoft.com> wrote in message
news:D8F6FA59-7633-4519-84FB-3257A3D324A6(a)microsoft.com...
> We are starting to switch to Microsoft's WinUSB.sys device driver for
> some of our USB devices. We access the driver thru WinUSB.dll . To get our
> driver 'signed' so that the user does not see any warnings on Vista and
> Windows 7 when the USB device is plugged in, it looks like we have to
> submit
> a driver package to WHQL in order to get a signed catalog file back from
> Microsoft.
>
> Our .inf file contains our USB vid/pid and refers to WinUSB.sys .
> So...apparently, we need to submit a driver package with .inf and .cat
> files
> and test logs for our device to WHQL even though WinUSB.sys came from
> Microsoft.
>
> Is my understanding of the situation correct?

From: mpv on 23 Apr 2010 19:51
Hi,

"Doron Holan [MSFT]" <doron.holan(a)online.microsoft.com> wrote in message
news:%23ZRnwWz4KHA.4888(a)TK2MSFTNGP06.phx.gbl...
> correct, you need to get the INF, CAT and all of the coinstaller DLLs
> submitted as a packge so you can get them signed
>
I don't think you have to get the package signed by WHQL, because as you
state, WinUSB is already signed. All you need is a certificate from a CA
from the shortlist (that have a cross certificate from Microsoft). We got
one from GlobalSign.
With the tools from the WDK, you can then generate a .cat file from your
..inf file, and sign it yourself. Add that to your package and that should be
enough. We did it that way.

Regards, Matt


From: Tim Roberts on 23 Apr 2010 23:37
"mpv" <nospam(a)forget.it> wrote:
>>
>I don't think you have to get the package signed by WHQL, because as you
>state, WinUSB is already signed. All you need is a certificate from a CA
>from the shortlist (that have a cross certificate from Microsoft). We got
>one from GlobalSign.
>With the tools from the WDK, you can then generate a .cat file from your
>.inf file, and sign it yourself. Add that to your package and that should be
>enough. We did it that way.

Well, it depends on what you need. You don't need to sign the driver for
KMCS purposes, because it's already signed. But if you want to avoid the
"unsigned driver" warning at install time, then you need to get the driver
PACKAGE signed by WHQL.
--
Tim Roberts, timr(a)probo.com
Providenza & Boekelheide, Inc.
From: mpv on 24 Apr 2010 04:56
Hi,

"Tim Roberts" <timr(a)probo.com> wrote in message
news:vlp4t5l3671ik1rglohf0vjbce9o9121fe(a)4ax.com...
> Well, it depends on what you need. You don't need to sign the driver for
> KMCS purposes, because it's already signed. But if you want to avoid the
> "unsigned driver" warning at install time, then you need to get the driver
> PACKAGE signed by WHQL.

In this specific case (already signed WinUSB), I don't think so, and I am
speaking from experience.
We use a Wise script, together with the WinUSB co-installers, DPInst.exe
(which also has a 64 bit version), and the .inf file with corresponding
signed .cat file. That is enough. On installing the package on Vista 64 or
W7 64, we do not get a warning, just a dialog whether you want to trust our
company in future.
We have never had any business with WHQL.
(You yourself helped me find a bug in the MS example WinUSB .inf file, for
which I am still grateful.)

Regards, Matt


 |  Next  |  Last
Pages: 1 2 3
Prev: INF for Ports class CDC USB device using usbser.sys fails DTM
Next: Access permission for registry in Windows 7