Search options (Page 53 of 66)

Nope, you don't understand EAN sector itself is a replacement of one of the usual subchannels sectors. And when you see it between 2 tracks - it can be either the last sector of the previous track or the first sector of the next track, you can only guess So you should compare it against the rest of the gaps. For example, you have such EAN sector between 2 tracks and it either belongs to the previous sector (and the gap is 00:01:74) or to the next sector (and the gap is 00:02:00) => you need to compare both cases against the rest of the gaps. If all the other gaps end with 00, then this one is obviously 00:02:00. If only the first gap ends with 00 and all the rest (at least 2) end with 74, then this one is obviously 00:01:74. Hope, you've got my point.
You don't need to buy, I can give you .sub examples.

Looks good here, but you've done it not the way I've said. You're trying to fix each sector right after the error was found. And I still think it's better to read all the sectors "as is", make a list of incorrect ones and reread them after all the sectors were read. That should give better results, since when you read 1 sector many times, it may return cached results and when you reread all bad sectors in a batch after you have dumped the whole disc, you can be sure no caching is involved As I've said already, Subdump works exactly this way and it's usually good in fixing read errors.

Other than that, it definetely works now.

Even on 40x speed it now takes more than 5 hours to dump a scratchless disc. I don't understand, how do you do your c2 reporting. Both 0xBE and 0xD8 have c2 reporing flags, when you set them, you get 2742 bytes/sector output (2352 data + 294 c2 + 96 subs), you need to:

1) Read all the sectors from LBA #0 to leadout
2) Check the 294-bytes c2 part for each sector. Each sector contains 2352 bytes of data and 294 bytes * 8 = 2352 bits of c2 errors reports. So, each byte of data has 1 c2 bit of data, which can be either 0 or 1. 0 - no c2 error in this byte, 1 - c2 error is there.
3) Make a list/array of the sectors, where at least 1 bit = 1. For each corrupted sector make a list/array of the corrupted bits.
4) Empty the cache and reread all the sectors with c2 errors. For each sector compare the new c2 part against the previous and if the sector still has c2 errors, but at least 1 sector is fixed - replace it and remove from the list of corrupted bits. If the sector doesn't have any c2 errors left, remove it from the list of corrupted sectors.
5) If the number of rereads isn't reached (you've said you want 80 times), retry the step 4).

http://www.mediafire.com/file/g02374d32 … v1.5.1.zip -- anyone to test?

Different pressings of the same version of the game with different checksums. xM, xS, xA, etc. are taken from the ringcode.

Yours matches TruRip dump, compared with mine - 2 bytes difference (0x00 in 2 places in your dump, 0xFF in mine, the rest is the same), so they are different dumps and different masters.

Do the tracks match my dump? I can give you a .sub, so you could burn it and dump with your tool to check the decoding.

MAME uses the most recent USA version as a parent, earlier versions and japanese ones are clones.

Proper cues can be taken with subdump; if there is a TOC vs sub mismatch - we add the entry with TOC-based gaps as a primary dump and the one with subs-based gaps as a secondary dump which is hidden (for documentation purposes). So, yes, they can be dumped, but still with a lot of manual work But you need to use either a Plextor or a swappable drive, since with a regular READ command certain areas can be unreadable for subdump and you won't get a proper .sub and a proper .cue.

Single stars inside the ringcodes - yes, needed. Multiple stars like "* ** *******" aren't needed. Try to PM iRr0b0t about the logos. We usually include "Mastered by Nimbus" logo as text into the ringcode field, so these ones should be also included at the very end of the ringcode, IMO. Or, at least, in the comments.

iR0b0t: maybe one more field is needed for these logos? Mastering Code, Mastering Logos (?), Mastering SID Code, Toolstamp, Mould SID Code, Additional Mould Text?

Why don't you use C2 error reporting? You could reread the sectors with C2 errors and even merge the multiple read results of the same errorneous sector (since C2 shows the exact error bytes, so you could take out all the good bytes from a single sector).