So, I'm using the current Wii Backup Manager to make transferring backups to this new HDD more convenient, and I'm transferring games that are just the game partition so they're under the 4GB limit and don't need to be split for the FAT32 filesystem. Out of curiosity, I've compared the MD5 hashes between the two, and they're totally different, despite the filesize being exactly the same number of bytes. Is this a cause for concern? Is this normal? The GameCube Backup Manager didn't do this when I checked those games.
I didn't have full scrubbing mode enabled, and I did have it set to calculate MD5 hashes during transfer. I don't have permanent changes to Wii disc header or changes to WBFS disc header allowed, either. Looking through the settings, I don't see any reason for it to do anything but directly copy the file over without alterations. I'm wondering if this is a bug, or if it's intended behavior, what exactly is the cause of this? And, would it be better to delete the mismatched files and copy them over manually, or is it probably fine?
EDIT: Oh duh, silly me, it completely slipped my mind that renaming a file affects its hash. That was foolish. Never mind then, it's all good!
EDIT: No, it doesn't affect the hash to rename it.
I didn't have full scrubbing mode enabled, and I did have it set to calculate MD5 hashes during transfer. I don't have permanent changes to Wii disc header or changes to WBFS disc header allowed, either. Looking through the settings, I don't see any reason for it to do anything but directly copy the file over without alterations. I'm wondering if this is a bug, or if it's intended behavior, what exactly is the cause of this? And, would it be better to delete the mismatched files and copy them over manually, or is it probably fine?
EDIT: Oh duh, silly me, it completely slipped my mind that renaming a file affects its hash. That was foolish. Never mind then, it's all good!
EDIT: No, it doesn't affect the hash to rename it.
Last edited by leejaclane,