For a long time, Microsoft has been mentioning in this group (and
various places in the documentation) that peripherals are required not
use Class=USB in their infs because that's reserved for host controllers
and hubs. Dire WHQL consequences have been hinted at.

I was just trying to convince one of our firmware guys of this, and he
pointed out that there are several .inf files in Windows\INF that
violate this rule, including many that are WHQL signed... notably many
things that act like thumb drives such as media players, as well as a
couple of modems (mostly this question comes up around here with respect
to development devices such as FTDI/EZ-USB/etc.).

So... What's the current state of this advise? What's the actual fallout
if you violate this rule?
--
Ray

Re: USB class by Doron

Doron
Tue Jun 20 21:01:09 CDT 2006

you shouldn't do it, stuff like this is internally being cleaned out slowly.
use your own class.

d

--
Please do not send e-mail directly to this alias. this alias is for
newsgroup purposes only.
This posting is provided "AS IS" with no warranties, and confers no rights.


"Ray Trent" <rat@nospam.nospam> wrote in message
news:OIgNDLKlGHA.4508@TK2MSFTNGP05.phx.gbl...
> For a long time, Microsoft has been mentioning in this group (and various
> places in the documentation) that peripherals are required not use
> Class=USB in their infs because that's reserved for host controllers and
> hubs. Dire WHQL consequences have been hinted at.
>
> I was just trying to convince one of our firmware guys of this, and he
> pointed out that there are several .inf files in Windows\INF that violate
> this rule, including many that are WHQL signed... notably many things that
> act like thumb drives such as media players, as well as a couple of modems
> (mostly this question comes up around here with respect to development
> devices such as FTDI/EZ-USB/etc.).
>
> So... What's the current state of this advise? What's the actual fallout
> if you violate this rule?
> --
> Ray