#Nitro software piracy software
In fact, if the self destruct system is hardware based (and not based on save data), the cart might be able to detect dumping software being used on it and then destroy itself, but that would require considerable extra circuitry to detect the data reading done by the dumper. You could also do the same by deliberately burning out a fuse on the card (mabye an efuse) or even using a capacitor to store enough power to fry the card (and even the DS or AR, depending on how nasty they want it to be).
#Nitro software piracy code
The easiest way to make retail cards self destruct would be for the "self destruct" code to write certain data to the save area (which is writable) and have the game refuse to run if that data is found, similar to what Comex did with his DVDX installer. It could destroy the retail card, but it would require special hardware (or programming) on the card. Note: The numbers I'm using for the games per month/year is hypothetical, but the first run release numbers are always around 20k. If Nintendo tries to force a "Internet Connection Required" gig on all games with this code, how would the sales of their games go with people who lack a wifi connection? Would a person without Wifi be able to play that brand new game that they just bought? I'm not sure how big it is but storing 720k keys after a year would take up quite a bit of space. Now, take the current memory space on the DSi. Coding wise, that's already a good sum, but if this continues out throughout a year at three games a month, that's 720,000 individual keys and the console must compare them to a list of valid keys. That totals out to 40 to 60 thousand individual keys. Now take the number of games released in a month (about two or three). That means 20k keys to be made and programmed on a first run. Every game that gets released often runs on a 20k print. If you do the math, you'll see that the genuine key code is bound for failure.
0 kommentar(er)
