(12 replies, posted in General discussion)

The tool is useful for identifying discs which might have protection, but due to the false positives, the discs will still need to be checked with pSX 1.13 and a USA BIOS (other regions are not suitable) or with the above no$psx method.
With pSX the game will either show the mod screen or freeze, it usually happens right away but sometimes you have to start the game.


(12 replies, posted in General discussion)

I found a good case to prove the false positive text issue. I checked this Japan demo and it only has the text in the file. The full game is protected (freezes).

EDIT: More examples are Alundra 2 & Ape Escape. Only the Japan versions are protected, the others just have the JP text.
Alundra 2 also gets a false positive with MODPAR & Version 1 of your tool.


(12 replies, posted in General discussion)

I did a test with no$psx and I noticed that Window/TTY Debug Messages logs some CD cmds. Protected games have the below log when the game does the mod check. I didn't see the cmds with MediEvil II, unless the game doesn't check until the end lol.
The old MODPAR tool does find a mod check code if you scan a save state, but I wonder if it's not active in this version.
EDIT: I tried a end game save for MediEvil II (USA) and it turns out it does have the protection after all. I think it only checks near the end of the game!

CDROM Command: 02 xx xx xx
CDROM Command: 0E 01
CDROM Command: 16
CDROM Command: 0B
CDROM Command: 03
CDROM Command: 19 04
CDROM Command: 19 05
CDROM Command: 09


(12 replies, posted in General discussion)

Thanks for the update! Version 2 works for those Japan games, but I think the text search is giving a false positive for MediEvil II (USA). I tested it for a while and I didn't get the mod screen. Seems odd that it would have the text and no protection though.


(12 replies, posted in General discussion)

The first one is tricky. The mod screen shows up after you start a new game and finish the beginning dialog, which takes a few minutes. Another slow one is "Disney's The Emperor's New Groove (USA)", the tool detects this one.


(12 replies, posted in General discussion)

I tested your program and it works great for the games I tested. I found some games where it couldn't detect the protection.

Here are the games:
Ore no Shikabane wo Koete Yuke (Japan)
Saru! Get You! (Japan) (v1.0), (v1.1), (Demo)

It was probably hidden by someone, I don't see it in the deleted feed. An admin can check if it was.

Btw, can you double check this write offset? http://redump.org/disc/37221/


(50 replies, posted in General discussion)

Use IsoBuster to extract "PS3_GAME/PARAM.SFO"

Then you can check the version at the bottom and see if it's different.

I vote for storing them unformatted. There are some unusual codes that would be nice to preserve.

Mastering SID: Some XBOX USA discs have IFPI130
Mould SID: Some PS2 USA discs have 72xx or IFPI 72xx

The first one is a USA region disc, I added it to the USA wiki. Homeland is dumped. The others are developer NR discs, and I'm not sure if redump wants those or not. Here's a topic about dumping NR and RVT-R discs.

Some serials are unknown and they are not very useful for the list. I might add the Japanese titles to the list sometime though.

Edit: The serials would help with adding/matching the titles to the database, so I will add the ones I can in the next update.

That Mario special disc is dumped here: http://redump.org/disc/22900/

The Wii Japan discs are already on the wiki, and the other Wii lists haven't been made yet. It would be better to keep those for now so they don't confuse anyone.


(50 replies, posted in General discussion)

The only accurate way to get them is by changing the system settings or checking for in-game language options. Even games with matching EBOOT.BINs can have different languages (see FFXIII-2).

Lite-On iHBS212 & iHBS312 both work as well. The ASUS BW-12B1LT/ST drives should work too, but these are not confirmed.

You cannot use IsoBuster with the PS3 drive. The drive has to be authenticated first, which only the 3k3y app will do.

Regarding dumps/verifications using the 3k3y method, they are good, but I don't think we could accept them since the image has to be modified.  neutral


I corrected the dump above and added the missing barcode serials. Thanks for pointing it out.

pablogm123 wrote:

Understood, iR0b0t. When Rocket submits that verification I will put both tags in the edition field, «PlayStation the Best» and «PlayStation the Best for Family».

Pablo, please only put "PlayStation the Best for Family" in the edition field. There are some dumps that are missing the "for Family" text, the dumpers probably just checked the "PlayStation the Best" checkbox and didn't mention the "for Family" text.


(74 replies, posted in General discussion)

Time to bump this topic for a new discussion!

I noticed about a week ago that we have a few bad dumps in the database. I found these thanks to TheHustle. He had asked me how to dump one of them, but I found out they were not standard UMDs and they could not be dumped the usual way.

http://redump.org/disc/808/ [UCJB-98306]
http://redump.org/disc/1196/ [UCJB-98302]
http://redump.org/disc/1743/ [UCJB-98303]

These are demo discs with a game + video partition and the entire video section is corrupt in the dump I tested "UCJB-98302". I do not know which dumping tools were used to make these dumps, but I'm sure the video partition must be corrupted in all three dumps.

I bought one of the demo discs to try dumping this type of UMD myself, the demo disc I have is "UCJB-98306". My dump does not match the database, which is not surprising. I found a way to dump both partitions correctly, but they have to be dumped to separate .iso files.

Here are the instructions:
Note: UMD_DATA.BIN of each ISO has the partition number, 0001 & 0002.

1) Use UMDKiller V1.2 to dump the first partition. It will be saved to ms0:/ISO/UCJB-98306.iso.
2) Connect your PSP to a PC and rename the dumped ISO as "UCJB-98306_0001.iso" and then move it onto the PC.
3) Use UMDKillerPRX V1.5 to dump the second partition. It will be saved to ms0:/ISO/UCJB-98306.iso.
4) Connect your PSP to a PC and rename the dumped ISO as "UCJB-98306_0002.iso" and then move it onto the PC.
5) Open Notepad and type the text below, make sure to modify the filenames to match your ISOs.

copy /b UCJB-98306_0001.iso + UCJB-98306_0002.iso UCJB-98306_merged.iso

6) Save the file as Merge.bat and move it to the same location as the two ISO dumps.
7) Double-click the Merge.bat to merge the ISOs into one file, "UCJB-98306_merged.iso" is created.
8) Use clrmamepro's Dir2Dat function and uncheck everything except Add MD5+SHA1, create the .dat file to save the three ISO hashes.

There is currently no dumping tool that will dump both partitions at once, and I don't know if this is able to be done either. The dumps in the database were joined together to make the dump one file. I think merging the two ISOs is okay. There are very few game UMDs with two partitions, and we can include the non-merged hashes in the comments. The only issue with merging is that the video partition is unplayable after merging, but that may change in newer PSP CFW.

As a test, I also tried to dump Video UMDs using UMDKillerPRX V1.5, but only the 0002 partition will dump. PSP Filer 6.6 and UMDKiller V1.2 cannot be used on Video UMDs, so these UMDs will have to remain unsupported for now.

So how should we proceed? I think it would be safe to add the fixed dumps with the non-merged hashes in the comments.

Do you have an ice log for ChuChu Rocket? I found your log for Guilty Gear X.

They are part of the mastering code, but they don't always have a space between them. Most should have [TAB], but the dumpers will need to confirm if there is a space or not.

Here are some scans for reference:
No space


(2,586 replies, posted in General discussion)

The ISO 'Volume Space Size' is being logged incorrectly. My last post explains some issues with DVD dumping.


(2,586 replies, posted in General discussion)

Here are some DVD dumping issues/requests:

Only L0 is dumped on the following disc type (example):
TrackPath: Parallel Track Path
NumberOfLayers: Double Layer

Checking for "PhysicalFormatInformation: L1" will probably fix this issue.
Opposite Track Path DVD-9 discs are also being overdumped.

Could you please add TOC+Layer Information:
Session 1... (LBA: 0)
-> Track 01  (Mode 1, LBA: 0 - 4169567)
-> LeadOut  (LBA: 4169568)
Layer 0 Sectors: 2084944
Layer 1 Sectors: 2084624


(2,586 replies, posted in General discussion)

Thanks! I tested it and everything is working fine smile

I sent a message to iR0b0t about the redump .cue file issue.


(2,586 replies, posted in General discussion)

I agree with Nexy, the missing INDEX 0 for Track 1 is a bug with CloneCD. The .cue files here on redump don't have an INDEX 0 for Track 1 when INDEX 1 is >00:00:00. This should be fixed.

I noticed that the last track for my disc is being underdumped. The last 30 sectors are lost with DiscImageCreator and not with other tools.


(2,586 replies, posted in General discussion)

I found some CCD file issues:

CloneCD wrote:

INDEX 1=30

DiscImageCreator wrote:

INDEX 1=30

Here are the .ccd files: http://www.mediafire.com/?z3idm72x26751d8