DrCoolZic wrote:Yes you are right the minimum distance is 32 bytes (usually 24 x $4E + 8 x $00) but here we only have 13 bytes (2 x $4E + 11 x $00)
Te minimum gap II size at MFM is 28, not 32.
But using the read address command you should be able to read 18 sector address even if all sectors with address above 11 are not readable.
Yes, of course. Although it is problematic to read all the headers because the pairs are too close. The standard Pasti imaging tool will miss some headers.
“ID within ID” (somewhat similar to Sector within Sector).
I'm pretty sure this was used in a couple of other french games. Can't remember the titles, though, would need to check.
I have attached the description of the protections I am aware of for Audio Sculpture to this post.
The track 3 uses potentially many protection mechanisms. But I am not sure which one are actually used / checked
It was more than two years since I checked the protection and I'm afraid I don't remember the details. Give me a couple of days and I would try to answer that as good as possible.
Having the write splice inside sector 10 can potentially create fuzzy bits. This behavior breaks the rule above, and therefore the protection need some tolerance ...
That's correct. It is not only about weak bits per se. The splice area tends to be magnetically noisy and irregular. You might read different things in different drives, even when it always reads the same in a specific drive. That's why this protection in the PC was usually used for custom applications, where the publisher (or developer) typically had direct contact with the customer and could solve any potential issues with the disk.
As I believe I said in this thread, I thinks there seems
to be some tolerance in the code that checks the protection. Don't remember the exact details and I didn't fully reverse engineer the code anyway.