> This behavior was actually a core copy protection trick. The custom drive writing the commercial software would gate the transitions in the middle of a sector, leading to a region that would read different noise every time.
Can you explain that a bit more? On the software side, how could you detect if you had a pirated disk or not? Read a few times the same data and make sure it'd always be different?
Can you explain that a bit more? On the software side, how could you detect if you had a pirated disk or not? Read a few times the same data and make sure it'd always be different?