microsoft os descriptor (usb)

Can anyone help me locate the information on how to implement the Microsoft
OS descriptor in a USB device? I found some "os descriptor" defines and
structs in the 2003 DDK which, when returned by my device does seem to make
WinXP SP2 to query for more information. However, I have not found (ddk
help, microsoft.com, google, etc.) any documentation whatsoever on how to
correctly/fully implement this.

http://www.microsoft.com/whdc/system/bus/usb/USBFAQ_intermed.mspx

<quote>
The Microsoft OS descriptor is a set of data structures that IHVs can use to
include extra information in device firmware, information that Microsoft OS
descriptor-enabled applications and operating systems can extract. The data
is extracted by vendor-specific USB requests to the device as indicated in
the OS Descriptor specification. The information retrieved will provide the
operating system and/or applications with additional information about the
device and its special features.

For additional information about the Microsoft OS descriptors, please visit
USB Architecture and Driver Support.
</quote>

Thanks in advance

Pavel
Wed Aug 18 15:42:59 CDT 2004

http://www.microsoft.com/whdc/system/bus/usb/USBFAQ_intermed.mspx

--PA

"Tim Schuerewegen" <wincepb-at-xgsdev-dot-com> wrote in message news:#tDQlzUhEHA.2544@TK2MSFTNGP10.phx.gbl...
> Can anyone help me locate the information on how to implement the Microsoft
> OS descriptor in a USB device? I found some "os descriptor" defines and
> structs in the 2003 DDK which, when returned by my device does seem to make
> WinXP SP2 to query for more information. However, I have not found (ddk
> help, microsoft.com, google, etc.) any documentation whatsoever on how to
> correctly/fully implement this.

Tim
Wed Aug 18 16:06:59 CDT 2004

That URL, which was in my original post, contains hardly any information on
how to implement the Microsoft OS descriptor on the device itself.

> http://www.microsoft.com/whdc/system/bus/usb/USBFAQ_intermed.mspx
>
> --PA

Pavel
Wed Aug 18 16:59:26 CDT 2004

Oops. Sorry.
I've definitely seen detailed info somewhere - probably in the Hardware newsletter about 2 months ago.
Maybe I have a copy at work.

--PA

"Tim Schuerewegen" <wincepb-at-xgsdev-dot-com> wrote in message news:usuRQdWhEHA.3428@TK2MSFTNGP11.phx.gbl...
> That URL, which was in my original post, contains hardly any information on
> how to implement the Microsoft OS descriptor on the device itself.
>
> > http://www.microsoft.com/whdc/system/bus/usb/USBFAQ_intermed.mspx
> >
> > --PA
>
>

Tim
Thu Aug 19 07:52:46 CDT 2004

I found the "microsoft os descriptor" patent on espacenet.com which contains
some more information and even an example. Might just be enough to implement
this feature on my device. However, I would still be grateful if anyone
(Microsoft?) can point me to the apparently missing information on the
Microsoft site.

> Oops. Sorry.
> I've definitely seen detailed info somewhere - probably in the Hardware
> newsletter about 2 months ago.
> Maybe I have a copy at work.

martinbo
Thu Aug 19 14:10:44 CDT 2004

------=_NextPart_0001_45DC282D
Content-Type: text/plain
Content-Transfer-Encoding: 7bit

The documentation on the Microsoft OS Descriptor requires a signed legal
agreement. This legal agreement should be posted on the WHDC site in the
next month or two. Prior to that, you would need to go through Microsoft
support channels to get execute this agreement.

If you have a Premier support contract, you can contact your Technical
Account Manager (TAM) about the agreement. If not, you will need to open a
support request with Microsoft. Please refer to the following URL for more
information on how to do this:


http://support.microsoft.com/common/international.aspx?rdpath=fh;en-us;cntac
tms

Thanks,
Martin Borve [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_45DC282D
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20 The documentation on the Microsoft OS Descriptor requires a signed legal agreement. This legal agreement should be posted on the WHDC site in the next month or two. Prior to that, you would need to go through Microsoft support channels to get execute this agreement.
\par
\par If you have a Premier support contract, you can contact your Technical Account Manager (TAM) about the agreement. If not, you will need to open a support request with Microsoft. Please refer to the following URL for more information on how to do this:
\par
\par http://support.microsoft.com/common/international.aspx?rdpath=fh;en-us;cntactms
\par
\par Thanks,
\par Martin Borve [MSFT]
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_45DC282D--

Robert
Fri Aug 20 13:08:32 CDT 2004

That looks very much like a cheap trick to make USB devices Windows
specific. At least the mediocre API and keeping it in private indicates
that.

The idea to place icons and other OS specific information in the device
has been rejected by USB developers years ago already.

BTW it is also a sure way to increase the price of the device.

Pavel
Fri Aug 20 16:54:14 CDT 2004

"Robert Marquardt" <robert_marquardt@gmx.de> wrote in message news:OvGUrCuhEHA.2540@TK2MSFTNGP10.phx.gbl...
> That looks very much like a cheap trick to make USB devices Windows
> specific. At least the mediocre API and keeping it in private indicates
> that.
>
> The idea to place icons and other OS specific information in the device
> has been rejected by USB developers years ago already.
>
> BTW it is also a sure way to increase the price of the device.

This seems to be in line with a broader MS initiative to define
OS specific descriptors for number of PnP buses.
Something about this can be found in the Winhec and devcon presentations
published on the web.
--PA

Robert
Fri Aug 20 23:54:03 CDT 2004

Pavel A. wrote:

> This seems to be in line with a broader MS initiative to define
> OS specific descriptors for number of PnP buses.
> Something about this can be found in the Winhec and devcon presentations
> published on the web.
> --PA

The next try to make hardware Windows specific.

The first try was Windows-compatible CPUs. A major marketing success of
MS. The next one was the Windows key, the wheel and then the extra
shortcut keys on the keyboard. Recently the "improved" wheel etc.

Pavel
Sat Aug 21 20:49:58 CDT 2004

"Robert Marquardt" <robert_marquardt@gmx.de> wrote in message news:uFpZZrzhEHA.2880@TK2MSFTNGP10.phx.gbl...
> The next try to make hardware Windows specific.

Yes. At three companies I worked for recently, we designed new
devices for Windows first (based on HCT requirements) , then - maybe - for Linux,
and never specifically for something else.

--PA