CyberStretch,

My second example is not quite the same as with CL`s challenge code, in their setup all complete files would be stored on the CD and a hacker only needs to figure out a way to circumvent the security. In my example, however, the data on the CD is willingly corrupted by the manufacturer and will only run with a personalized installer.
Usage of CCard, CVV etc. would only be used to get the installer going, after installation it could be backed to diskette by the buyer and safely removed from the harddisk.

With an initial diskspace usage of 500Mb there are zillions of places to hide personal data, not necessarily CCard info, pointing to the buyer.
No routines that check if P5 is legally installed, just (encrypted) buyer info put anywhere in the P5 files by the installer. Hackers wouldn`t know where to look and what to look for as there is no en/decryption code available anymore.

So, still CL have their software protected, buyers still can install whenever/however they want after a single registration process.

I still think this (in a proper worked out form, of course) will be a good way to secure software.

MaxxArcher