Prev: Contiguous Memory allocation
Next: A KeQuerySystemTime alternate function under x64 ?
From: Jake on 25 Dec 2009 16:58
Pavel--

Interesting. Perhaps this is something MS has already changed or perhaps
the WinUSB driver doesn't add this to the device path.

This is on Vista 32-bit.

And, although you don't seem to believe me, the serial number is present and
fully verified on Windows, Linux, and Mac OS X as a real "honest to goodness"
USB serial number. I've got about 5 yrs of production behind this particular
device to prove that out, and every single USB "snoop" or inspection utility
shows the serial number reliably.



"Pavel A." wrote:

> "Jake" <Jake(a)discussions.microsoft.com> wrote in message
> news:DB9A65A2-2C3B-4EC1-A234-F9AC5F3DC73E(a)microsoft.com...
> > Pavel--
> >
> > Hm. They do... And I don't... I wonder if I'm doing something wrong?
> >
> > Will they just print, as usual? Here is an example string I'm getting:
> > \\?\usb#vid_XXXX&pid_YYYY#5&595e2b2&0&2#{7a1a3eb2-9c2c-47be-be55-ff3332a722fd}
> >
> > VID and PID have been replaced, but the remainder is verbatim.
>
> Hi Jake,
>
> If only my memory serves, when the serial number is present,
> it should be contained verbatim in the above string, somewhere between the
> vid & pid part and the {guid}.
>
> Regards,
> --pa
>
>
First  |  Prev  | 
Pages: 1 2 3 4
Prev: Contiguous Memory allocation
Next: A KeQuerySystemTime alternate function under x64 ?