QUOTE (Zaranthan @ Aug 18 2008, 05:29 PM)
If you break the copy protection, you lose the registration. The next time the software checks for updates, it fails a critical CRC check and you get a message from Evo telling you that your license is invalidated.
Or, you could somehow let the hacker copy the copy protected program, then break the protection on his copy. That way the original buyer would still get his patches. But, you don't just go out and download patches in 2070 like you do nowadays. The program suite just has an updater that applies the necessary changes automatically. If updates were packaged neatly into little files you could collect, they'd be practically free among hackers for exactly the reasons you put forth.
It boils down to verisimilitude. The world doesn't work like that, because if nobody's paying for it, then the corps aren't selling it.
I can see degradation being the protection method. If you treat them like BTLs it makes sense that you get a copy and an access code that enables the "chip" for a certain amount of time after activation or for a set number of uses. So if you download "pilot groundvehicle 4" you either get 10 uses or 1 month from registration (first usage). After that number of uses the chip stops working until you give it another access code. AS this technology is the SAME that BTL chips use I have to assume that there are rules someplace about removing BTL protection, so it already works in both the fluff and mechanics.
Timers can be set for either time or usage and they due suffer from degradation so you can't just hold on to them forever. You want to crack it and there are rules for that too.
From Unwired pg 151:Cracking the Timer: The self-erasing features of the Timer
option can by bypassed by a Software + Logic (10, 1 hour)
Extended Test (using Hardware instead of Software in the case of
programs run from a chip, like some skillsofts).