Search options (Page 1 of 4)

I believe Redumper does not work as far back as Windows XP.

You will have to use DiscImageCreator if you want to dump on the Windows XP machine.

Sarami, a verification for http://redump.org/disc/74375/ was recently dumped using 20250101 which had a different pregap for Track 4 (00:02:49). I have attached the logs.

========== TOC with pregap ==========
    Track  1, Ctl 4, Mode 1, Index0   -150, Index1      0
    Track  2, Ctl 0, Mode 0, Index0  44850, Index1  45000
    Track  3, Ctl 0, Mode 0, Index0  62592, Index1  62792
    Track  4, Ctl 0, Mode 0, Index0  68996, Index1  69195
    Track  5, Ctl 0, Mode 0, Index0  79270, Index1  79470
    Track  6, Ctl 0, Mode 0, Index0  95142, Index1  95342
    Track  7, Ctl 0, Mode 0, Index0  99005, Index1  99205
    Track  8, Ctl 0, Mode 0, Index0 101340, Index1 101540
    Track  9, Ctl 0, Mode 0, Index0 103517, Index1 103717
    Track 10, Ctl 0, Mode 0, Index0 107547, Index1 107747
    Track 11, Ctl 0, Mode 0, Index0 109585, Index1 109785

Track 4 Index 0 in _disc.txt returned 68996 (199 sector pregap)

To determine if datname modifiers are actually needed, are you able to check langs for the following:
http://redump.org/disc/60790/
http://redump.org/disc/58720/
http://redump.org/disc/70643/

Please upload logs zip

If you have the time to, submitting logs from both tools is good. But it is not required.

I will see if superg can respond to your questions, better than I could.

In what way did you think that DIC is better?
If you can then dumping with both can help ensure the dump is good, but Redumper is recommended for the majority of discs.

As for why the dumps are different, the logs give hints as to non-zero errors, invalid sync sectors.
There are some scenarios that Redumper and DIC deal with unexpected sectors differently.
I would have to look at the logs closer to be sure.

Also, please update your MPF to the latest version (3.3.0) which contains the recommended version of Redumper and has fixed a lot of bugs.

Work to support automatic/semi-automatic dumping of ring protection (or a subset of ring protection) is being done in redumper.

Until then, this is the guide you should follow for ringed discs. It is not for the faint of heart, takes a lot of time and effort:
http://www.wiki.redump.org/index.php?ti … ping_Guide

Other drive models have been known to overdump. It must be something to do with XboxOne discs and the drives that support them. Fortunately, overdumping is simple to fix. I have moved this thread to verifications.

Hi, your dump is 29 sectors over-dumped.
I expect if you remove 29 sectors (59392 bytes) from the end of your dump, it will match with redump.
I'm not sure why it overdumped, something about the drive. The PIC tells us the correct dump size (22978238464 bytes)

Sorry for yet another request, but could you dump with this version of DIC?
https://github.com/saramibreak/DiscImag … 190326.zip

This is the version that was used by the dumper in the current entry. Perhaps DIC has changed since then.

Hello, to your question, we format barcodes with a single space character in between regardless of the size of the whitespace between the numbers: 8 23162 00295 4

Also, the mastering SID you have is "IFPI L039 11/14/03 20:01:48"
We only retain the SID code itself in that field, "IFPI L039", the remaining text belongs in the mastering code (assuming it is lasered/etched). If it is stamped (on the mould itself) then it is "Additional Mould" text.