Wirt ponders the state of copy protecting client (pc)
installed s/w:

>For several different products we're in the process of
>developing, we need a method of uniquely identifying PC's
>in the same way that we can identify HP3000's via the
>HPSUSAN number for reasons of minimizing piracy.

I would ask a third question: why?

We spent considerable amount of time dealing with copy protection
in client (pc) software and after considerable hassle with
customers upgrading components and the s/w not working we decided
to give it up.

Be careful how you proceed or you will end up upsetting your
customers in a very big way :-)

duane percox

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *