PS3 Dumping issue.

I just got a new pre-owned ps3 game that I dumped using the same method I described above, all hashes match those on redump. Really weird that it only happens with one game. I'm wondering if multiman keep some debug logs somewhere.

As for the problematic game in question:

The ring codes are

So yeah they do match.

I dumped it again without enabling direct disk access and choosing "Create ISO" directly from the game menu (as opposed to the video menu). I got the exact same hash:

This is a game I bought completely new and unopened. I always store my game discs carefully and in their case when not in use. The disc surface looks flawless, no scratches in view. Not a single read error when dumping.

I also tried to change the destination of the iso from the PS3 internal HDD to an external USB 3.0 HDD (FAT32 partition MBR) but I have the same issue. Press X to start the dump then nothing.

One thing I noticed is that there seem to be some encoding problem with the file name created when dumping. Japanese is often encoded using UTF8,UTF16 or SHIFT_JIS so there might be a conversion issue if multiman uses something like ASCII or ISO 8859-1 internally.

Technical jargon aside this is what I should get:

This is what I am actually getting:

When I try to FTP this over to my PC it doesn't work (I get a file doesn't exist error) until I renamed it on the PS3. I have other japanese games I dumped and they all worked although sometime the file name end up being a blank space like this:

Don't know if there's a way to specify the destination file name in multiman, if someone knows please let me know how. I would use something like dump.iso or disc.iso for all of my dump.

Ok I'll submit this dump then.

By the way, I know the file name doesn't affect the hashes. What I mean to say is that this is the only game I couldn't dump using the exact method described here http://wiki.redump.org/index.php?title= … ping_Guide so I was afraid I wasn't dumping the right data.

I thought that the weird filename might have something to do with the fact that the dumping process doesn't start using the usual method.

Anyway I can't really be sure the dump is correct unless someone dump that game and it matches mine (or lxxxl's in which case I'll know I did something wrong)

Thanks for the help!

Thanks for checking lxxxl,

I see that you used DICUI for your dump so I tried to do the same with my bluray drive and this time I get the same hash as you. I am just puzzled as to why the file is different when dumping from the PS3 vs from a PC with DICUI and a non PS3 OEM Bluray drive?

I do get an error using this method but I am guessing that is because I'm not using an OEM PS3 drive

Edit: I compared both files using a binary diff tool and I came to the conclusion that the ISO dumped by DICUI seems to be encrypted and the one dumped using my PS3 seems to be decrypted, I can verify that by mounting both ISO and trying to open:

On the DICUI dump it doesn't show the picture because the data is encrypted but on the PS3 dump it display a png picture just fine. So I am guessing to stay as close as possible to the original media we should use the encrypted version right?

This is what I am trying to explain I dumped all other games using "Direct disc access" in multiman I am guessing this enables 1:1 dump (encrypted), but for some reason this method didn't work for this particular game. It only worked without "Direct disc access" ie: decrypted. In the end it dumped correctly with DICUI on my PC and getting the disc key worked on the PS3 so I could combine both in my submission. If it ever does that again I'll just dump the game using DCUI.