DEVICE_ID broken on HP iPaq 210 models?

Sean McLeod · Joined: 11 Feb 2008 Posts: 5

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

Archived from group: microsoft>public>pocketpc>developer

Peter Foot · Joined: 01 Sep 2007 Posts: 56

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" wrote in message @microsoft.com...
> 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
>

Sean McLeod · Joined: 11 Feb 2008 Posts: 5

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" wrote in message
> @microsoft.com...
> > 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
> >
>

Sean McLeod · Joined: 11 Feb 2008 Posts: 5

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" wrote in message
> > @microsoft.com...
> > > 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
> > >
> >

Sean McLeod · Joined: 11 Feb 2008 Posts: 5

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" wrote in message
> > > @microsoft.com...
> > > > 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
> > > >
> > >

Scott Yost [MSFT] · Joined: 15 Aug 2007 Posts: 245

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" wrote in message @microsoft.com...
> 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" wrote in message
>> > > @microsoft.com...
>> > > > 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
>> > > >
>> > >

Sean McLeod · Joined: 11 Feb 2008 Posts: 5

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" wrote in message
> @microsoft.com...
> > 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" wrote in message
> >> > > @microsoft.com...
> >> > > > 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
> >> > > >
> >> > >
>
>
>

Scott Yost [MSFT] · Joined: 15 Aug 2007 Posts: 245

Honestly, the specification of these IOCTLs is a mess and you don't want to
dive too deep down the rabbit hole. But some implementations return
different things for IOCTL_HAL_DEVICE_ID depending on the size you pass into
them. Some of them return different things depending on whether you ask for
something that is sizeof(DEVICE_ID) vs. something that is
sizeof(UNIQIE_DEVICEID). That might be happening on those device. It boils
down to an overlapping spec between Windows CE and Windows Mobile so some
OEMs wrote the code once and serviced both platforms with it. This is one of
the reasons I recommend standardizing on GetDeviceUniqueId() (assuming it's
available for your target customers).

--
Scott Yost
Software Development Engineer/Test
Microsoft Corp.

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

"Sean McLeod" wrote in message @microsoft.com...
> 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" wrote in message
>> @microsoft.com...
>> > 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" wrote in
>> >> > > message
>> >> > > @microsoft.com...
>> >> > > > 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
>> >> > > >
>> >> > >
>>
>>
>>

controlling notification leds (on and off) on iPAQ I'm looking to find out if there is any way of controlling the power or bluetooth (or any other) led on my ipaq 2490 (running Windows Mobile 5). I just need simple ON and OFF I have looked around and it seems that the older version of the .

Not able to browse internet page using IE in HP iPAQ Hi, We have developed an 802.11 client card and its NDIS miniport driver(NDIS 5.0). To configure the card we also developed one supplicant and protocol driver. This protocol driver will reside above the miniport driver. We are targeting for Windows Mobile

Programatically setting iPAQ backlight Hello All: I need to control the backlight brightness on one of the newer model iPAQs. Chris Tacke, et. als postings about setting the backlight registry settings and then broadcasting a to do this were pretty cute, but n

error message on ipaq download This question has probably been asked a million times, and has a simple solution, but im going to ask it any way im developing the ipaq(SA1110) with embedded visual tools, and the 2002 ppc. When i attempt to download my program to the processor the conne

compact framework problem for HP iPAQ hx2190 Hi, I have a HP iPAQ hx2190 device. But it is a compact framework 1.0 device. I would like to upgrade it to 2.0 but it is unsuccessful and it poped up an error msg about the software could not be installed in this device. But I have tried to use the same