You are not logged in. Please login or register.
Active topics Unanswered topics
Post new reply
Post new reply
Compose and post your new reply
You may use: BBCode Images Smilies
All fields with bold label must be completed before the form is submitted.
Topic review (newest first)
I think part of the issue is that cleanrip 2.0.0-datel2 ignores all errors; I wonder if it would be possible to check the error and only ignore it if it's a 030200 (No Seek Complete) while still stopping for other errors. I'm not sure if such a check would affect dump times or not. (I guess a log of all unreadable sectors and the corresponding errors would be useful too; Cleanrip 2.1.1's skips file is close to that and probably could be used as a starting point.)
It does sound like your dump is correct; once the 2.0.0-datel2 dump finishes go ahead with submitting it. I've also purchased this same title and should be able to verify it in a week or so.
My dump is confirmed broken. I'm still investigating what happened and grabbing my original dumps and redumps off of my Wii Harddrive. I apologize for my error.
Pokechu22 wrote:Datel titles usually have their main code starting at 0x50000000. If that area is completely blank, your dump is probably bad. Cleanrip 2.1.1 doesn't know what to do with most datel titles and will have everything after 0x01F00000 zero'd out without trying to read it, while 2.0.0-datel2 will attempt to read it, ignoring any errors for the unreadable sectors and filling those sectors with 0x55. If everything is still 0x55, that's a bad sign. Also if there are 0x55-filled sectors in the middle of code that otherwise looks fine, that's probably a bad sign.
Check if the game starts properly on console; if it's unable to read it normally when you launch it, then there's no hope of cleanrip doing the right thing unfortunately. Otherwise, you can try testing your dumps with dolphin; Datel being Datel the games don't launch unless you've got the GC bios and have DSP LLE enabled though. If you get error messages other than FIFO overruns, and if it doesn't start, your dump probably still isn't correct.
Even if you eventually get something that matches what's in the database, verification dumps are always useful (especially for discs as volatile as these).
It's also worth noting that the numbers in the ringcode can be the same for multiple discs; Advance Game Port and both Cheat Construction Kit videos (PAL and NTSC) are 04070501 (see images), though they have different text. To my understanding, the numbers are a date (in the form of year month day 01); the Cube magazine discs help establish this.
My dump has data at 0x50000000 which ends at 0x50300000, something the verified dump doesn't have. My dump boots on a wii via nintendont and on dolphin with the settings you described. I couldn't do that with the verified dump. Using a hex editor, I found that the verified dump is missing a lot of data that my dump seems to have. Using a hex editor, I found the verified dump is missing lots of random chunks of data. I tried mapping it out all the differences between my dump and the verified dump, but gave up after the 8th missing chunk of data that I found.
I used cleanrip 2.1.1 with these skip settings.
<skipcrc crc100000="50CD767F" skipfill="55"/>
<skip start="01F00000" stop="4FFFFFFF"/>
<skip start="50300000" stop="570FFFFF"/>
And I consistently get a working dump with the same hash. I am currently dumping it again with 2.0.0-datel2, but I really hate how long it takes, especially knowing these disks are prone to failure. My disk is in pretty amazing condition. Once it is done I'll compare the ring codes and see if there's any differences.
If anyone would like my dumped file for investigation, I would be happy to supply it via PM or something.
Welcome, obtain your password here.
(check the spam folder in case there will be no message in your inbox)
Feel free to ask question on the forum, or via Discord about how to get started preserving games with Redump:
Discord
Datel titles usually have their main code starting at 0x50000000. If that area is completely blank, your dump is probably bad. Cleanrip 2.1.1 doesn't know what to do with most datel titles and will have everything after 0x01F00000 zero'd out without trying to read it, while 2.0.0-datel2 will attempt to read it, ignoring any errors for the unreadable sectors and filling those sectors with 0x55. If everything is still 0x55, that's a bad sign. Also if there are 0x55-filled sectors in the middle of code that otherwise looks fine, that's probably a bad sign.
Check if the game starts properly on console; if it's unable to read it normally when you launch it, then there's no hope of cleanrip doing the right thing unfortunately. Otherwise, you can try testing your dumps with dolphin; Datel being Datel the games don't launch unless you've got the GC bios and have DSP LLE enabled though. If you get error messages other than FIFO overruns, and if it doesn't start, your dump probably still isn't correct.
Even if you eventually get something that matches what's in the database, verification dumps are always useful (especially for discs as volatile as these).
It's also worth noting that the numbers in the ringcode can be the same for multiple discs; Advance Game Port and both Cheat Construction Kit videos (PAL and NTSC) are 04070501 (see images), though they have different text. To my understanding, the numbers are a date (in the form of year month day 01); the Cube magazine discs help establish this.
Forunately the ring codes will tell you. Datel uses unique ringcodes for every revision, we have encountered revisions of datel discs before. If your ring codes match exactly to the letter, then yes something is wrong with one of the dumps.
Because these discs are so poorly pressed, it's also possible that the original dump is incorrect, too. There's so little data on the discs that it's hard to know.
Most of my Datel Discs no longer read at this point so I can't go through and dump them again. If your disc consistently dumps differently, then it's possible that your disc is different (with Datel, always a possibility), your disc is damaged, or my disc was damaged.
Hey! So I have been backing up my GameCube collection and found a possible bad dump. My ISO has a different checksum than the one posted here. http://redump.org/disc/54408/
At first I was using Cleanrip 2.1.1, which according to the wiki isn't going to work if you want to compare it to the redump hashes, so I downloaded CleanRip 2.0.0-datel2 and tried again but I was still getting a mismatch. I decided to compare my file with a the dump that matches the hashes in the redump database and found that mine has a whole sector that was missing! (Specifically, I have missing data between 0x4FFFFFFF and 0x50300000)
I am requesting an account so I can post my dump and hopefully get the entry for this game corrected.