Re: DEVICE_ID broken on HP iPaq 210 models?

Okay so GetDeviceUniqueID() is implemented by hashing the DEVICE_ID using the
supplied program's data as the salt, as opposed to using some other OEM
mechanism to return a unique device ID?

If so I'm a bit suprised since as I mentioned in the original post the 2
test HP iPaq 210 devices we have return the exact same data for DEVICE_ID and
since we're supplying the same salt data I'm suprised then that we get back
two unique IDs from GetDeviceUniqueID().

Cheers

"Scott Yost [MSFT]" wrote:

GetDeviceUniqueID is likely to shield you from some errors in how the
underlying DEVICE_ID is implemented..There's only so much it can do though.
If the whole structure is duplicated on every single device, then
GetDeviceUniqueId will always be duplicate as well.
--
Scott Yost
Software Development Engineer/Test
Microsoft Corp.

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

"Sean McLeod" <SeanMcLeod@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:9505D214-70D1-4528-B83E-B1EC23834685@xxxxxxxxxxxxxxxx
Just an update, I tried the WM5+ API GetDeviceUniqueID() on the HP iPaq
210
and it does appear to return unique IDs for the 2 different devices we
have
for testing.

Cheers

"Sean McLeod" wrote:

Oops, forget to include the link for the blog posting I refered to below:

http://blogs.msdn.com/windowsmobile/archive/2006/01/09/510997.aspx

Cheers

"Sean McLeod" wrote:

Okay thanks although we support Windows Mobile 2003 devices as well
with the
same exe so we would need to implement a runtime check and use
GetProcAddress() for GetDeviceUniqueId().

IOCTL_HAL_GET_DEVICEID has also been working fine on loads of other
Windows
Mobile 5 and Windows Mobile 6 devices, even from HP. They just seem to
have
broken the implementation on this particular model.

Also taking a look at this Microsoft blog posting about
GetDeviceUniqueId()
and the comments by developers complaining that some OEMs have also
managed
to mess up the OEM part of the implementation such that
duplicate/non-unique
device IDs are being returned.

So I'm not holding out too much hope that HP will have got the OEM
portion
of this API correct.

Microsoft really needs a better logo program to catch these sort of OEM
errors before the devices are allowed to be released as branded Windows
Mobile devices.

Cheers

"Peter Foot" wrote:

On all Windows Mobile 5.0 and later devices you should use
GetDeviceUniqueId. See the SDK documentation for usage.

Peter

--
Peter Foot
Microsoft Device Application Development MVP
www.peterfoot.net | www.inthehand.com
In The Hand Ltd - .NET Solutions for Mobility

"Sean McLeod" <SeanMcLeod@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:B1122CC9-75FA-4221-8719-67C40B409410@xxxxxxxxxxxxxxxx
Hi

We use the DEVICE_ID structure returned by IOCTL_HAL_GET_DEVICEID
to get a
unique device ID for use in our licensing scheme for our Pocket PC
software.

We have noticed though that the newly released HP iPaq 210 models
don't
appear to return unique device data in the DEVICE_ID struct.

The PresetID bytes are the null terminated Unicode string
"PocketPC".

The PlatformID bytes are the null terminated ansi string
"HPIPAQ210_24337".

Has anyone else noticed this?

If so is there an alternative mechanism to get a unique device ID
on HP
210
models?

Cheers





.

Relevant Pages

  • Re: DEVICE_ID broken on HP iPaq 210 models?
    ... GetDeviceUniqueId will always be duplicate as well. ... So I'm not holding out too much hope that HP will have got the OEM ... Microsoft really needs a better logo program to catch these sort of OEM ... unique device ID for use in our licensing scheme for our Pocket PC ...
    (microsoft.public.pocketpc.developer)
  • Re: DEVICE_ID broken on HP iPaq 210 models?
    ... down to an overlapping spec between Windows CE and Windows Mobile so some ... Software Development Engineer/Test ... supplied program's data as the salt, as opposed to using some other OEM ... unique device ID for use in our licensing scheme for our Pocket ...
    (microsoft.public.pocketpc.developer)
  • Re: DEVICE_ID broken on HP iPaq 210 models?
    ... I tried the WM5+ API GetDeviceUniqueIDon the HP iPaq 210 ... and it does appear to return unique IDs for the 2 different devices we have ... Also taking a look at this Microsoft blog posting about GetDeviceUniqueId() ... So I'm not holding out too much hope that HP will have got the OEM portion ...
    (microsoft.public.pocketpc.developer)
  • Re: DEVICE_ID broken on HP iPaq 210 models?
    ... Also taking a look at this Microsoft blog posting about GetDeviceUniqueId ... So I'm not holding out too much hope that HP will have got the OEM portion ... unique device ID for use in our licensing scheme for our Pocket PC ...
    (microsoft.public.pocketpc.developer)