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?
As EvanAnderso and Meic said, yes. Think of it as the Schrodinger's cat of copy protection; as long as the bad sector is in a state of quantum superposition, the game works. It's when the superposition collapses into a definitive state that the game fails to load.
The writer would simply refrain from writing anything for a moment, leaving the original bulk-erased magnetic nothingness in the middle of a sector.
This article re: imaging floppies in the analog domain made the rounds on HN a couple years ago:
https://scarybeastsecurity.blogspot.com/2021/05/recovering-l...
The comments have some good links and background:
Here's Applesauce's author's description, FWIW:
> At the lowest level, they are all capturing the amount of time between magnetic flux transitions on the media. The real differentiator comes from what you do with all of these flux timings.
And not only in a meaningless "not as accurate" sense -- the drive loses exactly the information that's critical to implementing a working copy. That's why you have to sample a track multiple times for the benefit of downstream analysis/RE tools, and why a naive capture can't be written back to a disk to get the same results.
It's not a good situation. A driver reader that *could* measure the actual flux transitions wouldn't have these problems, but we don't have such a device yet.
My point was that a true capture is/should-be possible, but not with the hardware as implemented by Greaseweazel et. al.
>Is there something you're confused about regarding floppy drives?
after reading all of that, i'm so confused i no longer even know what a floppy drive is or what it was meant to do
A more authentic representation of the flux on the disk could be made by amplifying and sampling the analog waveform straight off the drive heads. A variety of signal processing functions could be applied to that waveform vs. what the electronics on the drive will do.
This is a distressingly common misperception. In fact the flux stream that you get out of a reader like a Greaseweazle is the TTL-level signal from the drive. This is the output of a differential amplifier and crossing detector. In theory, the raw drive head will show zero volts when nothing is changing under the read head, a very small positive voltage when the magnetic flux reverses in one direction, and a symmetric negative signal when it shifts the other way.
What you get out of the amplifier is a digital (!) pulse of ~1us when the signal shifts in either direction. And due to the way the amplifier works, when "nothing is changing" it tends to just amplify noise in the environment and invent fictitious transitions. Proper disk encodings limit the distance between transitions (generally to no more than three bit cells) to deal with this.
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. Correct consumer hardware isn't able to do that.
And that's why the flux files are so large: they're storing multiple revolutions of every track, precisely so that tools like the WOZ (Apple) or ATX (Atari) converters can intuit the style of copy protection (there seems to be no clean equivalent in the Commodore world, their "archived" copy protected media tends to be reverse engineered the last I checked?)
A fun project I'd love to see someone try some day would be to wire up a proper analog ADC chain (doesn't need to be more than ~8 bit at 2 Mhz or so) to the unamplified drive head output and see if a cleaner representation of the flux can be read.