KernelIoControl( IOCTL_HAL_GET_DEVICEID ) - Supported by all OEMs?

Are all OEM's required to support this API? Is there some sort of Pocket PC
/ Windows CE certification/logo that will guarantee this API is available?
Finally, will this API return a unque device ID?
If not, is there a standard/recommended method for determining a unique
device ID? We would like to link a unique id to some security mechanisms in
our product

Thanks for input,

--
Jason Hinsperger
Product Manager
iAnywhere Solutions

Chris
Thu Nov 11 20:38:32 CST 2004

I do beleive all Pocket PC 2002 and 2003 devices are required to support it
as part of the logo certification process. Beyond that, it's up to the OEM
and many don't provide it (largely because not all hardware is uniquely
identifiable).

<ctacke/>

"Jason Hinsperger" <JasonHinsperger@discussions.microsoft.com> wrote in
message news:5DE0044D-3F2F-4D8C-ADE8-3B17F46CB121@microsoft.com...
> Are all OEM's required to support this API? Is there some sort of Pocket
> PC
> / Windows CE certification/logo that will guarantee this API is available?
> Finally, will this API return a unque device ID?
> If not, is there a standard/recommended method for determining a unique
> device ID? We would like to link a unique id to some security mechanisms
> in
> our product
>
> Thanks for input,
>
> --
> Jason Hinsperger
> Product Manager
> iAnywhere Solutions

MohitGupta
Thu Nov 11 22:37:02 CST 2004


HI Chris,

What microsoft says is GUID or DEVICEID or HARDWAREID is uniquely
identifiable.

Correct me if I am wrong.

I, at this moment, don't know the exact format of GUID, but atleast I know
this part is that DEVICEID is divided into 2 parts. Part 1 is the
manufacturers ID and Part 2 is the manufacturers uniquely Identifiable
number.

According to the above scenrio, every single hardware ID should be unique.

Correct me if I am wrong.



"Chris Tacke, eMVP" wrote:

> I do beleive all Pocket PC 2002 and 2003 devices are required to support it
> as part of the logo certification process. Beyond that, it's up to the OEM
> and many don't provide it (largely because not all hardware is uniquely
> identifiable).
>
> <ctacke/>
>
> "Jason Hinsperger" <JasonHinsperger@discussions.microsoft.com> wrote in
> message news:5DE0044D-3F2F-4D8C-ADE8-3B17F46CB121@microsoft.com...
> > Are all OEM's required to support this API? Is there some sort of Pocket
> > PC
> > / Windows CE certification/logo that will guarantee this API is available?
> > Finally, will this API return a unque device ID?
> > If not, is there a standard/recommended method for determining a unique
> > device ID? We would like to link a unique id to some security mechanisms
> > in
> > our product
> >
> > Thanks for input,
> >
> > --
> > Jason Hinsperger
> > Product Manager
> > iAnywhere Solutions
>
>
>

Chris
Fri Nov 12 08:55:22 CST 2004

Depends on how you look at it. You're right for PPC02 and 03. Beyond that
it's up to the OEM whether or not they implement it. Most PPC 2000 devices
did not support it, and few WinCE devices support it. It's not always a
simple task to have a static, unique identifier for all devices unless you
have some piece of hardware that either already has a serial number in it or
is programmable for one.

--
<ctacke/>
www.OpenNETCF.org
Your CF searches start and end here


"Mohit Gupta" <MohitGupta@discussions.microsoft.com> wrote in message
news:0D15778C-3D37-4A3B-927A-A2A8909DFF09@microsoft.com...
>
> HI Chris,
>
> What microsoft says is GUID or DEVICEID or HARDWAREID is uniquely
> identifiable.
>
> Correct me if I am wrong.
>
> I, at this moment, don't know the exact format of GUID, but atleast I know
> this part is that DEVICEID is divided into 2 parts. Part 1 is the
> manufacturers ID and Part 2 is the manufacturers uniquely Identifiable
> number.
>
> According to the above scenrio, every single hardware ID should be unique.
>
> Correct me if I am wrong.
>
>
>
> "Chris Tacke, eMVP" wrote:
>
>> I do beleive all Pocket PC 2002 and 2003 devices are required to support
>> it
>> as part of the logo certification process. Beyond that, it's up to the
>> OEM
>> and many don't provide it (largely because not all hardware is uniquely
>> identifiable).
>>
>> <ctacke/>
>>
>> "Jason Hinsperger" <JasonHinsperger@discussions.microsoft.com> wrote in
>> message news:5DE0044D-3F2F-4D8C-ADE8-3B17F46CB121@microsoft.com...
>> > Are all OEM's required to support this API? Is there some sort of
>> > Pocket
>> > PC
>> > / Windows CE certification/logo that will guarantee this API is
>> > available?
>> > Finally, will this API return a unque device ID?
>> > If not, is there a standard/recommended method for determining a unique
>> > device ID? We would like to link a unique id to some security
>> > mechanisms
>> > in
>> > our product
>> >
>> > Thanks for input,
>> >
>> > --
>> > Jason Hinsperger
>> > Product Manager
>> > iAnywhere Solutions
>>
>>
>>

Scott
Thu Nov 18 17:24:37 CST 2004

For modern devices (2003 at least, not sure about earlier) this is exactly
the API you should be using for your purpose. It will be supported by the
device.

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

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

"Jason Hinsperger" <JasonHinsperger@discussions.microsoft.com> wrote in
message news:5DE0044D-3F2F-4D8C-ADE8-3B17F46CB121@microsoft.com...
> Are all OEM's required to support this API? Is there some sort of Pocket
> PC
> / Windows CE certification/logo that will guarantee this API is available?
> Finally, will this API return a unque device ID?
> If not, is there a standard/recommended method for determining a unique
> device ID? We would like to link a unique id to some security mechanisms
> in
> our product
>
> Thanks for input,
>
> --
> Jason Hinsperger
> Product Manager
> iAnywhere Solutions