Updating default PS3 dumping method

[rhynec]

The developer of ManaGunZ just released a test build of v1.41 which adds a check for disc reading errors (It will notify the user if a disc error is encountered while dumping, if no action is taken (e.g. cancel operation), the dumping procedure will continue). It'd be great if Bigmanjapan could test this build with his scratched copy of LittleBigPlanet: https://github.com/Zarh/ManaGunZ/issues/62

Version 1.41 has also apparently integrated the GetKeys package into MGZ. Switching from NTFS to FAT-32 should no longer required in the dumping procedure. Dumping 3Dump.bin should also now be unnecessary while using MGZ. I believe these changes are also in the test build, but it'd be worth to wait until the final v1.41 is released.

[Bigmanjapan]

I've tried using the 1.41 test build with the same scratched LittleBigPlanet disc.

https://youtu.be/Pc-yYqFAI7w

1. At 05:30 you can see that the log stating read errors appears which is nice.

2. At 06:33 you can see that 30/30 re-tries are reached on the first bad sector, no termination of dumping process or any prompt appearing happens. The log itself is already a pretty nice development but I would like to see a setting (that could be switched on and off in the global settings of the program, for example) that would make dumping process actually be terminated upon any bad sector reaching 30/30 re-tries. My reasoning is that, with multiMAN after I start dumping process, I go and do something else. I don't need to constantly monitor the screen since multiMAN will outright terminate the dumping process by itself. With ManaGunZ in its current state I need to monitor screen in order to know if read errors happened or not.

Also, I'm not sure why multiMAN and ManaGunZ make optical drive behave differently when read errors are encountered. Again, as I've described in my previous post multiMAN would stop and spin the disc again which is very audible while ManaGunZ doesn't do this, even in the 1.41 test version. It wouldn't matter much if the output dumps are correct, I guess. Just a thought.

3. At 07:43 you can see that Cancelled notification pops-up at the upper right corner. That's me trying to terminate the dumping process by pressing Circle button. For some reason, termination doesn't happen if the log is actively shown on screen. When I pressed Hide logs button at 08:14, the dumping process was allowed to be terminated.

I also tried using the newly implemented "Get files for redump.org" function seen at 0:23 in the above video. Works perfectly. And more than that, it outputs files with the custom filenames which include timestamps like this:

BCES01663_20210722_071038.getkey.log
BCES01663_20210722_071038.disc.pic

This is a nice improvement in comparison to GetKey since when keys are dumped via GetKey the output files' filenames would remain the same, meaning that GetKey would overwrite them. This forces dumpers to transfer the files to PC after each dump which wastes time. ManaGunZ improves on this, especially since it uses timestamps a dumper can dump multiple copies of the same game in one session and the files won't be overwritten.

So, ManaGunZ is approaching to be the dumping tool for me. Allow for automatic dumping process termination upon encountering read errors and I'll switch to it. And if FTP connection is added at some point, then I'll drop multiMAN entirely (haven't tried webMAN-MOD yet).

[hkkane]

I dumped 3 games via ManaGunZ_v1.41,All Size,CRC-32,MD5 and SHA1 match record,but disc key incorrect from built in getkey feature,I need to use standalone package dump correct disc key again,I don't know why
anyway I reported to dev
https://github.com/Zarh/ManaGunZ/issues/75

If this issues fixed,ManaGunZ Method is definitely better than MultiMAN Method

[user7]

>https://github.com/Zarh/ManaGunZ/issues ... -967122331

Looks like get 3Dump.bin issue got fixed?

PS3 4.8.8 firmware could very well be the final. Anyone know if Evilnat 4.8.8 is compatible with redump? It would be nice to have a "final" dumping guide update so. Rebug CFW seems to be extinct afterall.

[Bigmanjapan]

Allow for automatic dumping process termination upon encountering read errors and I'll switch to it. And if FTP connection is added at some point, then I'll drop multiMAN entirely (haven't tried webMAN-MOD yet).

https://youtu.be/UPDaB3OAESg

Dumping process terminates automatically upon exceeding allowed amount of re-tries now.

For the software to display log entries for each individual read error during dumping process (starts at 5:04 in the video above), the Show Logs option has to be enabled in Settings. It is disabled by default.

Looks like get 3Dump.bin issue got fixed?

Correct.

I haven't looked into Evilnat yet but ManaGunZ reached a point where it can replace MultiMAN + GetKey combination.

[rhynec]

PS3 4.8.8 firmware could very well be the final. Anyone know if Evilnat 4.8.8 is compatible with redump? It would be nice to have a "final" dumping guide update so. Rebug CFW seems to be extinct afterall.

ManaGunZ is compatible with all 4.8X firmware. So both latest Rebug (lite or DEX) and Evilnat should generate proper dumps for redump. Even Ferrox firmware should be compatible. Though, if dumps need to use a specfic FW (for reproducibility or to reduce variables), perhaps only Rebug REX 4.84.2 and Evilnat 4.88 should be "allowed".

[user7]

https://github.com/Zarh/ManaGunZ/issues/104

My system is completely locking up when I try to dump the GetKey info. I hope this can be resolved, if ManaGunZ can work out the bugs then we can remove the old convoluted dumping method from the wiki.