Hardware ID's
Posted: Mar 20, 2002 @ 6:32amPage 1 of 1
Posted: Mar 20, 2002 @ 6:32amPosted: Mar 20, 2002 @ 6:52amI seem to recall that Compaq had some form SDK addition on their PPC developer site that included commands for accessing this. I never really looked into it though.
Posted: Mar 20, 2002 @ 7:45amI already know how to obtain ID's from PPC2k2 devices & from earlier Ipaq's. It's the other ARM based devices i'm more interested in. Although i wouldn't mind some more general info on Device IDs.
Posted: Mar 20, 2002 @ 2:31pmThe only Pocket PC 2000 device supporting ESN is the iPaq. No SH3, MIPS or even the @migo supports ESN.
Dan East
Dan East
Posted: Mar 20, 2002 @ 3:34pmisn' that serial nr inbuilt into the cpu????
Posted: Mar 20, 2002 @ 5:29pmThanks Dan, exactly what i wanted to know.
I'm still interested in an answer to (c), though i.e Are there any other ARM-based PPC2000 devices, even if little-known or a variant on an existing device?
I'm still interested in an answer to (c), though i.e Are there any other ARM-based PPC2000 devices, even if little-known or a variant on an existing device?
Posted: Mar 20, 2002 @ 6:34pmI don't know of any other ARM PPC 2000 devices besides those two.
Are you sure about the ESN with all PPC 2002 devices? Have you verified it on a device?
Dan East
Are you sure about the ESN with all PPC 2002 devices? Have you verified it on a device?
Dan East
Posted: Mar 21, 2002 @ 12:35amThe only other ARM-based PPC2000 device i can find are the series of Symbol devices, although they are targeted more at industry use. Their ID's can also be obtained (RCM_GETUNIQUEUNITID in their SDK) but i'm not sure if it's permanent.
I am pretty sure about PPC2K2 devices, although i haven't found the words 'ESN' or 'permanent' in any docs. However, MS do mention its use for 'security purposes & verification' and also suggest for one of the types of app that may target PPC2K2 as 'Applications requiring access to the unique device ID for digital rights management or other reasons.'
As of yet, i haven't verified it on devices due to owning only Ipaqs, but the timing couldn't be better... For the next couple of weeks i'm borrowing 4 other ARM devices (& a HPC), so i should be able to confirm my findings.
As you can probably guess, i required this information to implement copy-protection for an ARM-only app. Seeing that i should hopefully now be able to obtain hardware IDs for all Ipaq & PPC2K2 devices, I think it should be fairly easy to implement this for the majority of devices in use. For the other ARM devices, which probably amounts to less than 5% of ppc users, i could then generate a key based on non-permanent info like Owner Info, etc. Now i've just got to work out a decent way of generating a 2nd 'unlocking' code...
I am pretty sure about PPC2K2 devices, although i haven't found the words 'ESN' or 'permanent' in any docs. However, MS do mention its use for 'security purposes & verification' and also suggest for one of the types of app that may target PPC2K2 as 'Applications requiring access to the unique device ID for digital rights management or other reasons.'
As of yet, i haven't verified it on devices due to owning only Ipaqs, but the timing couldn't be better... For the next couple of weeks i'm borrowing 4 other ARM devices (& a HPC), so i should be able to confirm my findings.
As you can probably guess, i required this information to implement copy-protection for an ARM-only app. Seeing that i should hopefully now be able to obtain hardware IDs for all Ipaq & PPC2K2 devices, I think it should be fairly easy to implement this for the majority of devices in use. For the other ARM devices, which probably amounts to less than 5% of ppc users, i could then generate a key based on non-permanent info like Owner Info, etc. Now i've just got to work out a decent way of generating a 2nd 'unlocking' code...
Posted: Mar 24, 2002 @ 11:56pmConfirmed - Permanent Hardware ID's.