I've noticed that the ID you get with KernelIoControl(IOCTL_HAL_GET_DEVICEID
.. . .) is a big long. Nothing earth shattering in that news I know.

I just wonder when using it for licensing if it is a bit long to expect a
customer to type it into a web page along with credit card numbers and so
forth.

I don't feel secure enough with the Handango method of using the Owner ID.

So I've thought about some alternatives, including:

A shorter "activation code" that checks the internet for status through a
web service.
A shorter hash of the DeviceID that can be used to generate a license code.

Any ideas?

Nathan

I've figured out that an "activation code" could end up being 32 characters
as well.

So I am left with the question: how long is enough to be unique enough?

Nathan

"Nathan" <nmNOSPAMXX$$@hp.com> wrote in message
news:%23Q$zs%(E-Mail Removed)...
> I've noticed that the ID you get with
> KernelIoControl(IOCTL_HAL_GET_DEVICEID . . .) is a big long. Nothing earth
> shattering in that news I know.
>
> I just wonder when using it for licensing if it is a bit long to expect a
> customer to type it into a web page along with credit card numbers and so
> forth.
>
> I don't feel secure enough with the Handango method of using the Owner ID.
>
> So I've thought about some alternatives, including:
>
> A shorter "activation code" that checks the internet for status through a
> web service.
> A shorter hash of the DeviceID that can be used to generate a license
> code.
>
> Any ideas?
>
> Nathan
>
>

I had a similar problem and really don't have a good answer other than try
to extract the DeviceID number for your customer via the app to transfer or
send to you for registration. It is very accident prone to have the
customer try to type in 32 chars....
"Nathan" <nmNOSPAMXX$$@hp.com> wrote in message
news:%23Q$zs%(E-Mail Removed)...
> I've noticed that the ID you get with
> KernelIoControl(IOCTL_HAL_GET_DEVICEID . . .) is a big long. Nothing earth
> shattering in that news I know.
>
> I just wonder when using it for licensing if it is a bit long to expect a
> customer to type it into a web page along with credit card numbers and so
> forth.
>
> I don't feel secure enough with the Handango method of using the Owner ID.
>
> So I've thought about some alternatives, including:
>
> A shorter "activation code" that checks the internet for status through a
> web service.
> A shorter hash of the DeviceID that can be used to generate a license
> code.
>
> Any ideas?
>
> Nathan
>
>

"Harry Simpson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
>I had a similar problem and really don't have a good answer other than try
>to extract the DeviceID number for your customer via the app to transfer or
>send to you for registration. It is very accident prone to have the
>customer try to type in 32 chars....

It sounds like there is plenty of good reason to have an activation process
where details are transmitted via the web. I wondered if this was overdoing
it but it seems right.

Nathan