I dumped this game with Perfectrip and with Isobuster and the result is different!!
1) Dumping procedure with Isobuster:
I extracted the 2 data tracks separately, ignoring any gap that may be present (EAC doesn't detect the gap --> "Unknown") and I got the result that match with the database entry
Here's the data:
rom ( name "track 01.bin" size 645419376 crc 9274fe89 md5 1e7458c1049ea890d06875ecd482f803 sha1 24b49e9063e015dd54cd34c74bcb2c2cdc47ebd3 )
rom ( name "track 02.bin" size 42895776 crc 9c543465 md5 7f9aef56db4dcfacfae97c28aef54866 sha1 27162ae90fd4111885b6cdeaca4b25c4978eec23 )
I don't think that this procedure is correct, an eventual ("Unknown") track 02 pregap is added at the end of the track 01 and both tracks are incorrect!
2) Dumping procedure with Perfectrip:
I calculated the factory write offset with d8 (-647) and I dumped the game with the standard settings; Perfectrip detected a track 02 pregap of 2.00 sec and the result is that both tracks have different checksums! The cue is obviously different too!
Here's the data:
rom ( name "01.- bof4.track.bin" size 645066576 crc 60072356 md5 ef9b8e88137731fd1bd1c574628e5101 sha1 203ba1698fc262c18edc761af8a65753708f2046 )
rom ( name "02.- bof4.track.bin" size 43248576 crc ed4f34b5 md5 c5f4302e3c783b0b9c22f15db7f6b6a9 sha1 dc0fa59967976a4e37315a6b63a7bbbc9536a85a )
cue:
FILE "01.- bof4.track.bin" BINARY
TRACK 01 MODE2/2352
INDEX 01 00:00:00
FILE "02.- bof4.track.bin" BINARY
TRACK 02 MODE2/2352
INDEX 00 00:00:00
INDEX 01 00:02:00
I believe that this is the most correct way to dump this game, given the fact that Perfectrip detected the correct track 02 pregap!
Let me know what you (forum tech experts) think!
In both cases I scanned the image with CDMage and zero errors.
As further note I confirm the data present in the database entry and I can specify a few things:
Write offset: -647
Libcrypt: No
Errors count: 0