Hi guys, I'm trying to dump Twinsen's Odyssey, which has the following structure
FILE "Twinsen's Odyssey (Track 01).bin" BINARY
TRACK 01 MODE1/2352
INDEX 01 00:00:00
FILE "Twinsen's Odyssey (Track 02).bin" BINARY
TRACK 02 AUDIO
INDEX 00 00:00:00
INDEX 01 00:03:00
FILE "Twinsen's Odyssey (Track 03).bin" BINARY
TRACK 03 AUDIO
INDEX 01 00:00:00
FILE "Twinsen's Odyssey (Track 04).bin" BINARY
TRACK 04 AUDIO
INDEX 01 00:00:00
FILE "Twinsen's Odyssey (Track 05).bin" BINARY
TRACK 05 AUDIO
INDEX 01 00:00:00
FILE "Twinsen's Odyssey (Track 06).bin" BINARY
TRACK 06 AUDIO
INDEX 01 00:00:00
FILE "Twinsen's Odyssey (Track 07).bin" BINARY
TRACK 07 AUDIO
INDEX 01 00:00:00
I used px_d8 to detect the write offset (+2) and I was able to get somewhat consistent results:
Track 1: Plextor 760A = Plextor Premium = NEC 3540A = Pioneer 115D (after using 'resize')
Track 2: Plextor 760A = Plextor Premium <> NEC 3540A = Pioneer 115D
Tracks 3-6: Plextor 760A = Plextor Premium = NEC 3540A = Pioneer 115D
Track 7: Plextor 760A = Plextor Premium <> NEC 3540A = Pioneer 115D (No overread in these two, so I'm not worried)
The problem is this:
If I try to use the Isobuster way to find the write offset, either the drives can't seek to the sector (192504 - 225) or the sector is always full of data, but if I just click on track 2 and use sector view (which leads to sector 192504) I can calculate the write offset.
So I took a look with HxD at what was at those 529200 bytes (3 second pregap) that I was removing with 'resize' and what I got was actual data, as you can see in the attachment (scroll to 2B80).
So what should I do here?