[buserror]

Yes and that was VERY easily defeated too -- you just had to take the floppy, very carefully align the synchronization hole with your copy, and take a pinhead and make your own little scratch in the same place.

It was a bit silly to be honest -- this was the easiest copy protection to bypass!

[hota_mazi]

That won't work, because the actual disk inside the sleeve will never be aligned the same way your copy is.

The protection is not the hole in the sleeve, it's the hole in the disk. For example, the garbage reads would happen on track 12, $230 bytes after the $D5 $AA $96 marker. Good luck physically reproducing this.

These protections are trivial to remove in code, though.

[buserror]

You clearly have never looked at a floppy before making "that won't work" comments, but floppies have a sync hole that is aligned.

And having made multiple copies like that, I know very well it worked pretty well as a method -- it's very likely why that method never became the 'uncopiable' it was claimed to be when it came out.

[StillBored]

The apple ][ didn't have the hardware to read the sync hole (much less a sensor to detect where the head was, hence the clatter on reset as the head bangs into the endstop). That was part of the magic, each sector had a sync field and then a few bytes and a track/sector number.

That is of course why its not just a simple case of locating where the burned hole was relative to the sync hole because the "physical" location of a sector offset on the disk would normally vary from disk to disk (or for that matter from track to track) or format to reformat.

[hota_mazi]

I have seen many floppies, but you don't seem to know how the Apple ][ encodes bytes on the floppy because of the Disk 2 limitations. See my remark about the $D5 $AA $96 marker, and if you want to learn more, look up "6 and 2 encoding".