DJBarry004 Wrote:Thanks for explaining. Got other question: Does the MD5 hash changes when the ISO is compressed with Dolphin or does it remains the same (doesn´t change at all even when compressed into a .GCZ file)?
To answer your question, for future reference, the purpose of advanced hashing algorithms like MD5 is to verify data integrity, byte-for-byte. Theoretically, even a single bit (a 0 or a 1) out of order should create a different hash. If the algorithm didn't detect even these slight changes, it would be of little use in verifying that the data is preserved 100% in its original state.
DJBarry004 Wrote:3- Third of all, I found other errors, and this time it seems to be related to the HLE audio engine.
Not exactly. It's coming from somewhere in Dolphin's PowerPC emulation, not its DSP emulation. Whatever SignatureDB is doing, it may rely on some of the GC's functions that are good candidates for High Level Emulation (a lot of OS calls have historically been HLE'd in GC emulators, from what I've seen). It doesn't seem like a particularly big deal if you ask me.
As long as your MD5 hash matches this hash others have verified (661634c2817e65cfa257796e3fb5f7c2 for the PAL version, which I assume you're using?) then there's really no need to dump again, since your copy is a byte-for-byte copy of the original game disc.