And yes, many of the old-school (and entry level) tuts were from the DOS era. ORC's?
The risk of this style of approach is that it must be compatible with every single drive manufactured combined with every floppy controller because it must produce exactly the same OS-level error pathology with intentional physical damage. (Another approach is inducing low level MFM errors without physically modifying the media but it requires special hardware.)
Also, as with physical hasps (dongles), copy protection magic codes, install floppy disk writable decrementing counters, damaged sector key disks, and pretty much every other technique, these checks always exist somewhere as binary instructions in the executable and can be located with a debugger and/or hex editor through binary search and/or call stack tracing heuristics in a relatively short time.
As long as it works for most of the marketplace, support can work out something for the 0.1% when they call or write in.
