@Zac67
That's the art of coping with protection schemes. If you can't analyse several 'identical' disks, you're much left to guessing.
Actually you're not. All the custom disk format protected disks must somehow decode the tracks themselves, and thus you can easily find the loader routine: It's normally located either in the bootblock itself, or the blocks loaded by the bootblock. Just save this code instead of executing it, and then disassemble it (by using ReSource or similar tool).
Naturally it takes lot of analysis skills and practice to figure out what the assembly code is doing and why, but in the end you will be able to figure out the disk format. It gets really interesting when the loader code has been obfuscated with some code scrambler, and some decoy code/loaders are inserted to fool the analyser. Also, later some anti-singlestep, anti-breakpoint and anti-resource methods were used aswell.
Often it was race against time: If the game could be sold for few days/weeks without a working crack, it would be making some profit. If the protection was trivial to crack, the illegal copies would seriously hurt the sales.
In a semi-related note: By just talking about these things I'll be
commiting a crime in about month when the new finnish copyright law gets in effect.