Project

General

Profile

Emulator Issues #12000

Dolphin says that my dump of TLOZ: The Wind Waker is a bad dump everytime I check it's validity, but I don't know why

Added by Delta 3 months ago. Updated 3 months ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
% Done:

0%

Operating system:
N/A
Issue type:
Bug
Milestone:
Regression:
No
Relates to usability:
No
Relates to performance:
No
Easy:
No
Relates to maintainability:
No
Regression start:
Fixed in:

Description

Game Name?

The Legend of Zelda: The Wind Waker

Game ID? (right click the game in the game list, Properties, Info tab)

GZLE01

MD5 Hash? (right click the game in the game list, Properties, Verify tab, Verify Integrity button)

def1ac7ef52aff97542cb3b3ab8a0826

What's the problem? Describe what went wrong.

I cannot get to the start screen, it's all black and doesn't even ave sound.

What steps will reproduce the problem?

Dumping the game using CleanRip and then trying to play it. that's it.

Is the issue present in the latest development version? For future reference, please also write down the version number of the latest development version.

5.0-11701

Is the issue present in the latest stable version?

I'm not sure, as far as I've searched nothing has come up.

What are your PC specifications? (CPU, GPU, Operating System, more)

Intel Core i5-8300H CPU @ 2.30 GHz
Nvidia 1050
Windows 10

History

#1 Updated by pokechu22 3 months ago

Your dump might just be bad. Did cleanrip generate a GLZE01-dumpinfo.txt file? If so, can you post it? If it didn't generate one, it probably errored in the middle of the dump, and you'll need to dump it again.

Note that the correct hash (as per http://redump.org/disc/1086/) is d8e4d45af2032a081a0f446384e9261b; although they both start with the letter d and thus might look similar at first glance, they aren't the same.

#2 Updated by Delta 3 months ago

pokechu22 wrote:

Your dump might just be bad. Did cleanrip generate a GLZE01-dumpinfo.txt file? If so, can you post it? If it didn't generate one, it probably errored in the middle of the dump, and you'll need to dump it again.

Note that the correct hash (as per http://redump.org/disc/1086/) is d8e4d45af2032a081a0f446384e9261b; although they both start with the letter d and thus might look similar at first glance, they aren't the same.

Here it is:

--File Generated by CleanRip v2.1.1--

Filename: GZLE01
Internal Name: THE LEGEND OF ZELDA The Wind Waker for USA
MD5: d8e4d45af2032a081a0f446384e9261b
SHA-1: 6b5f06c10d50ebb4099cded88217eb71e5bfbb4a
CRC32: AD21C2BA
Version: 1.00
Verified: Yes
Seconds: 724

#3 Updated by JosJuice 3 months ago

This seems more like a support question that would fit in the forums rather than here, but...

Do you have a modchip installed in your Wii? Depending on the settings, they can edit the apploader to add a region-free patch, making the dump become a bad dump. But I don't think this explains why the game wouldn't run.

#4 Updated by Delta 3 months ago

JosJuice wrote:

Do you have a modchip installed in your Wii?

Nope, it's all vanilla except for the Homebrew Launcher.

#5 Updated by Pikachu025 3 months ago

Uh, that dumpinfo.txt has the correct hash. I think your SD card (or whatever you dumped to) might be bad, try a different one.

#6 Updated by pokechu22 3 months ago

Hm, the hash in the dump info matches the one from redump (and it even is marked as verified). Cleanrip calculates the hash as it goes, so it might be that your storage device failed in some way in the dumping process, so the generated ISO file is wrong, but the disc was read correctly. Maybe try running a disk check on your storage device (right-click it in windows explorer, select properties, then tools, then "check" under error checking).

#7 Updated by Delta 3 months ago

pokechu22 wrote:

...running a disk check on your storage device (right-click it in windows explorer, select properties, then tools, then "check" under error checking).

I just tried that and Windows stated that there's nothing wrong. I will try another drive however, as I'm in dire straights over here.

#8 Updated by Delta 3 months ago

Here's the solution:

I formatted my drive to NTFS instead of keeping it as FAT32. In retrospect I should've mentioned that, so forgive me. However, I wanted to thank every one of you that have helped my get here. Cheers!

#9 Updated by JosJuice 3 months ago

  • Status changed from New to Invalid

Also available in: Atom PDF