I understand that you're trying to help make the process faster, but the process exists for a reason. One set of logs = one verification. The logs are not for "crediting" (redump dumper field isn't about credit, it's about who we contact if a dump may be bad). Neither are they about trust, even the most trusted dumpers have to supply 1 set of logs per disc, even for ones that match. It's not that we don't believe you, we store these logs as they contain information beyond just the resulting hashes.
I hope you can understand. It's also why we strongly suggest that dumpers submit some verifications before going on to dump hundreds of discs as they may not understand the redump process.

Please just retain the second set of logs, you can rename it xxxx_logs-2.zip or whatever.
You can continue to post both identical discs in the same forum post.
You don't have to ensure that the correct submissioninfo.txt is inside the logs, it is the redumper/DIC logs we need.

Hello, your account will be made once an admin can get to it.
In the meantime, if you'd like to discuss Korean PS2 please get in touch with me via the VGPC discord: https://discord.gg/AHTfxQV
I manage the Korean PS2 missing lists and can help you source some games if you live outside of Korea.

Specifically with Ribshark's firmware.

5

(3 replies, posted in Verifications)

Please link to the entry you are verifying: http://redump.org/disc/33998/

Heya, thanks for posting.

We only add ringcode info for discs that have been dumped and confirmed to match. While it's extremely likely that your disc matches the one in redump, unfortunately your ringcode can't be added unless it was dumped to our standards. This is to ensure that all the data in redump is accurate and trustworthy.
If you do ever get the ability to dump the disc (easiest method is with a homebrew Wii) then let us know and it can be added.

7

(3 replies, posted in General discussion)

This dump (System Disc 2) was descrambled using the old DIC version and the descrambled dense.bin matched the TOSEC dump hashes.
If anyone else encounters this problem with ice.exe, you can use the files I've uploaded. Place dense.bin in the same folder and run the .bat which will call DIC and produce a descrambled dense.dec

Added here: http://redump.org/disc/115501/

8

(1 replies, posted in Guests & account requests)

TYBO wrote:

I am collecting all of the gamecube games inthe regional versions and version differences.

Do you own physical discs and have a method of dumping them in order to contribute to redump?

Hello, there are a handful of PS3 disc entries that do not have disc keys. If a page does not have a disc key, the dumper was not able to dump the key (i.e. it was dumped with a PC bluray drive only). There are also cases where a disc dumps fine but the key had problems being extracted. So you (or someone else) would have to buy the game and verify the dump with the key in order for it to be added to redump.
I don't mean to accuse you specifically of it, but we would also appreciate it if people do not try to contact dumpers for keys or ISOs, thanks.

The game in question: http://redump.org/disc/33636/
The game did not have any languages listed before.
I have confirmed it only has Spanish in-game and have updated the entry.
As there is only one language present, the dat name has not changed.

fuzzball wrote:

Why not do so with the disc number?

Some discs do:
http://redump.org/disc/109304/
...
http://redump.org/disc/109315/

---

But some do not:
http://redump.org/disc/115000/
...
http://redump.org/disc/115009/

It may be how they are printed on-disc. I think it is currently inconsistent.
See also: http://redump.org/disc/78652/ which has (Disc X), due to Roman Numerals.

(Track 01) occurs for games with 10 or more tracks, to ensure they will be ordered correctly.
For games with fewer than 10 tracks, there is no need for the leading zero.

Barthax wrote:

Thanks.  No iPhone but several old phones lying around - will have to keep trying. smile

I recommend using OpenCamera app in Android for this purpose: https://play.google.com/store/apps/deta … &gl=US

If you have an iphone (or other phone with a sufficiently powerful flash/camera), use an app that allows for taking video with the flash on. At the right angle, you can see the ringcodes like in the image attached. It can take a bit of trial-and-error to get the exact angle, but I've found it to be the easiest way.

Submit disc 1 and 2 as verifications, and disc 3 as a new disc.

It sounds like you have a Wii with homebrew. CleanRip is safe to use, it is used by many people here.
CleanRip provides more reliable DVD reading than "dvd dumper" and outputs a log file. That way we can be sure the hashes are correct.

You can get cleanrip here:
https://github.com/emukidid/cleanrip/releases/tag/2.2.0

If you'd like to contribute, the easiest way is to please make an account on the forum then dump the disc with CleanRip on a Wii and post the CleanRip dumpinfo.txt and .bca files to the forum. You will also need to post the ringcodes on the back of the disc, more info is here: http://wiki.redump.org/index.php?title= … ii_Console
If you have any questions about the process, just let us know.

1. Region is defined as the place the game was sold/marketed for/available in, not the regional restrictions of a console (e.g. PSX). Some PSX PAL discs were only sold in specific regions (e.g. Sweden, France as you've said), and did not receive Europe-wide releases, so are listed on redump by the more specific region identifier. An example would be http://redump.org/disc/6858/ which is the European release but only had English language available. http://redump.org/disc/18697/ is the French release with only French language, so is labelled as France in redump. Another example: There are a few Korea-region PSX discs that run on NTSC-J consoles that were only sold in Korea: http://redump.org/discs/system/psx/region/K

2. EXE date is the file date for the executable file on the disc, not exactly the disc the CD was printed but it gives some indication. The PVD date is another indicator as to which disc is "newer". Where revisions are clear, redump labels them as you've mentioned. In the case of Armored Core (USA), the EXE date is identical and the Reprint's PVD date is not valid, it is not a clear revision. Reprint is labelled as "EDC: Yes" which is my guess as to the difference between the disc dumps, it is likely the actual game content is the same, however I am not 100% sure on this. So for these alt/rerelease/reprint versions, so it is up to you.

3. You can view a single category in redump with http://redump.org/discs/system/psx/category/Games or you can filter the redump PSX dat by category using your dat tool of choice.

For the purposes of verifying your own dumps, if you get the same hash as redump on any drive, you can be confident the dump is good. For redump, only the drives listed on the wiki are acceptable. All other drives have a variety of feature support, and redump does not recommend anything in particular.

20

(2 replies, posted in General discussion)

Nemok wrote:

Interesting!

You also mentioned on github that IRDs were "useful for decrypting ISOs after they have been dumped on a PC blu-ray drive". I didn't know that, actually so far I only used the key directly with the old command-line tool PS3Dec.

So do you plan on adding ISO decryption functionality to IRDKit ?

I made that comment in reference to RPCS3's mention of IRD files here: https://rpcs3.net/quickstart

But, it shouldn't be too difficult to add decryption to the tool, perhaps in the next version!

21

(2 replies, posted in General discussion)

I've released a toolkit for creating PS3 IRD files, and other features.
https://github.com/Deterous/LibIRD/releases/
It is command-line only and requires .NET 8 installed.
A UI for this will be added within MPF eventually

Creating an IRD (with different options for providing keys):

irdkit create game.iso
irdkit create game.iso -k A125B2FF16B9B18D5C18B5630B501643
irdkit create game.iso -f game.key
irdkit create game.iso -l game.getkey.log

IRDKit can also print info about IRDs (all fields) and ISOs (PS3_DISC.SFB and PARAM.SFO)

irdkit info game.iso
irdkit info game.ird

IRDKit can also provide a comparison between two similar IRDs, showing the difference between the two:

irdkit diff game1.ird game2.ird

Improvements over 3k3y ISOTools, Redump2IRD, and ManaGunZ:

  • Only requires a redump ISO. Does not require Disc Key/Disc ID/PIC. Pulls key from redump.org and generates ID/PIC.

  • Correctly hashes non-contiguous files

  • Produces reproducible IRDs, 1:1 correspondence with redump ISOs

  • Much faster for large ISOs, ISOs with many files

  • Create IRDs for an entire PS3 ISO set in one command

Sorry, I shortened the printed serial, it does have -STD. Here's the links (can't be viewed without logging in).
BCUS-98195 (BVSS-032970A1): http://redump.org/disc/48706/
BCUS-98182-MGS, BCUS-98182-STD (BVSS-020710A1): http://redump.org/disc/48705/

However please do make an account and contribute when an admin gets to making you an account! (Unfortunately Hotmail, Outlook, Gmail and Web.de may block emails from redump, so you may need to use a different email, protonmail is a free email that you can use if you need one).

If you are looking for the PS3 Welcome discs, they are in the BD-Video DAT as they are not actually PS3 discs. This DAT is not made public, hence you cannot find them by searching on redump.org without logging in.

redump.org currently has entries for BCUS 98156 (Ringcode BVSS-011760A1), BCUS-98182 (Ringcode BVSS-020710A1), BCUS-98195 (Ringcode BVSS-032970A1), BCUS-98213 (Ringcode BVDL-052280A1), and BCUS 98156R (Ringcode BVSS-017190A1).
If you have a different serial/ringcode, then it would be missing from redump. BCUS-98213 also needs verification.

It is of course appreciated that you wish to contribute to redump, you can still provide your logs (following the guide on the wiki) to verify these discs.

I have not used that specific drive model, but you will need to ensure it is a JB8 model and it will need to be flashed with specific firmware:
http://wiki.redump.org/index.php?title= … T_firmware

This wiki page is still a work-in-progress, it currently suggests using the 3.02 firmware, but Ribshark's custom 3.10 firmware is now compatible with redumper and can be recommended for use.

25

(8 replies, posted in General discussion)

funkmata wrote:

Really?  I don't see any fields in the DAT file for "date added" for any games listed.  Also, this method doesn't seem to track when entries are removed or updated, hence why I'd like to compare older releases vs. new ones.

"Date added" field is in redump.org only. Yes, this makes it difficult to rebuild an old DAT, redump isn't flexible.
I still don't understand why you want a DAT from a specific date. If it's just information you want, you should be able to get it from redump.org itself (or ask directly), as the DATs don't contain anything that isn't visible in redump.org