76

(72 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.

How did you use the lamp during scanning? Good work though, I didn't think it was possible to scan them.

An admin will also need to add this information to make it verified.

It was designed to work with all Xbox discs, but only Xbox 1 was tested before it was released. usurper did not know about the 360 dumping issue.

FreeCell does not work with Xbox 360 discs yet. You will have to wait for a new version.

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
TAB

Different Mould SID Codes for different discs is normal.

Does your ISO file size match that dump? Seems odd that yours wouldn't match if it's the same edition as his.

83

(1,462 replies, posted in General discussion)

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

84

(1,462 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

85

(1,462 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.

86

(1,462 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.

87

(1,462 replies, posted in General discussion)

I found some CCD file issues:

CloneCD wrote:

[TRACK 1]
MODE=0
FLAGS= DCP
INDEX 1=30

DiscImageCreator wrote:

[TRACK 1]
MODE=0
INDEX 0=0
INDEX 1=30

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

88

(1,462 replies, posted in General discussion)

The ANSI build is crashing on CD-TEXT CDs with these two versions:
20130222
20130203

Yes, read the topic in the Dumpers forum. All Xbox/360 dumps are missing the L1 video partition. The database must be fixed in order to accept new dumps. Please wait smile .

90

(8 replies, posted in Fixes & additions)

I have already confirmed it is Q using a microscope a while ago. A microscope is too powerful for some PS3 discs, though, so you have to use a magnifying glass instead. I can see the Q's tail with just my eyes on most PS2/3 discs, so a scope isn't necessary.

91

(1,462 replies, posted in General discussion)

That was the issue, thanks! The PerfectRip tracks now match EAC when using -98. I had to manually move the gaps to the correct position, though.

92

(1,462 replies, posted in General discussion)

sarami wrote:
Enker wrote:

but -686 is needed for PerfectRip

Why is needed for PerfectRip?

I think it is probably a drive firmware issue causing this to happen. I tested CDs with CD-TEXT and without CD-TEXT, both need -686 in PerfectRip. EAC needs +98 for both. Hopefully you can find the cause when you get the drive.

sarami wrote:
Enker wrote:

Program does not keep periods in the file name (v1.1 gets named as v1)

Determined that the period since the last extension.
So, please specify an extension.
This issue is Windows OS specification.

That explains it. I wasn't adding an extension since it's usually added automatically. Can you make the program ignore extensions?

93

(1,462 replies, posted in General discussion)

Here are a few drive issues to make note of:

PX-W1210TA/PX-W2410TA (Data-only CDs):
Sense data, Key:Asc:Ascq:05:64:00(ILLEGAL_REQUEST. ILLEGAL MODE FOR THIS TRACK)

PX-W1210TA/PX-W2410TA (CDs without CD-TEXT):
Sense data, Key:Asc:Ascq:05:24:00(ILLEGAL_REQUEST. INVALID FIELD IN CDB)
CDTEXT on SCSIOP_READ_TOC
    Undefined CDROM_READ_TOC_EX_FORMAT_CDTEXT on this drive

PX-W2410TA (CDs with CD-TEXT):
Doesn't dump tracks correctly. Bad TOC MSF for last audio track (PX-W1210TA also has this issue).


These are issues with discimagecreator:

Crashes after running these commands (Tested 32bit):
DiscImageCreator.exe -c D:
DiscImageCreator.exe -s D:

End line issue:
DiscImageCreator.exe -split foo.dec
DiscImageCreator BuildDate:[Jan 28 2013 23:59:57]
Start -> 2013-01-28(Mon) 14:40:03
Split File(num)  5/ 5End -> 2013-01-28(Mon) 14:40:57

ReadMe.txt issue:
PX-W2410TA(PX-W2410A)    1.04    +686 is right
+98 is right, but -686 is needed for PerfectRip

Could you also add this issue to the first post?:
Program does not keep periods in the file name (v1.1 gets named as v1)

94

(1,462 replies, posted in General discussion)

sarami wrote:

Please tell me px_d8 log & dump data to cdtoimg (about sector 1-5) your PX-W1210TA (1.10) & PX-W2410TA (1.04)

Here is the px_d8 log and cdtoimg data: http://www.mediafire.com/?0yya05nd27pz842

The PX-W2410TA is the only drive still detecting the wrong CD offset, the PX-W1210TA is correct with the 1.10 firmware.

95

(1,462 replies, posted in General discussion)

Need overread sector is now set to 1 after updating the PX-W1210TA (1.10), but the PX-W2410TA (1.04) still has Need overread sector: 2, which is making the CD offset +590 instead of +2.

I am still getting this error with both drives:

SCSI bus status codes:02-CHECK_CONDITION [F:ReadTOCText][L: 1696]
Sense data, Key:Asc:Ascq:05:24:00(ILLEGAL_REQUEST. INVALID FIELD IN CDB)

96

(1,462 replies, posted in General discussion)

sarami wrote:

If you use Windows7, check off below
explorer -> tool(T) -> folder option(O) -> show tab 'Do not show extensions that are registered'

Hiding or showing file extensions doesn't fix the issue.

Now I've got another bug to report. I noticed that the combined offset is detected incorrectly for these two Plextor drives: PX-W1210TA, PX-W2410TA
The combined offset is detected as +588 samples too big, but the disc still dumps correctly, just the CD offset is listed wrong. I noticed this in the log: Need overread sector: 2
This is set to 1 for my working Plextors, and it looks like it needs to be set to 1 for these two drives as well.
Here is a log file: http://www.mediafire.com/?5y8kdp4q42t27rj

The following errors appear before the dumping starts with both of these drives:

PX-W1210TA
SCSI bus status codes:02-CHECK_CONDITION [F:ReadConfiguration][L:1089]
Sense data, Key:Asc:Ascq: 05:20:00(ILLEGAL_REQUEST. INVALID COMMAND OPERATION CO
DE)

PX-W2410TA
SCSI bus status codes:02-CHECK_CONDITION [F:ReadTOCText][L: 1696]
Sense data, Key:Asc:Ascq:05:24:00(ILLEGAL_REQUEST. INVALID FIELD IN CDB)
Can't get CDROM_TOC_CD_TEXT_DATA

97

(1,462 replies, posted in General discussion)

You fixed the dumping problem smile The tracks now match PerfectRip's and the database. The log still has ISRC entries though. Here is a link with the subcode and log files: http://www.mediafire.com/?yvido8a9uc88ooq

98

(1,462 replies, posted in General discussion)

Could you upload a 32-bit version? I can't test 64-bit programs.

99

(1,462 replies, posted in General discussion)

sarami wrote:

upload version 20121228.

All three issues are still present in this version, though I didn't expect them to be fixed yet.

sarami wrote:

For the present, cleaning your pickup lens of drive & disc.

1. I redumped the disc at speed 0 with the new version and it produced a cleaner sub file, but the issue still remains. The disc is very clean, but there is a tiny spot I see that could be causing the issue.

sarami wrote:

This file is created by perfectrip? If so, please look at the setting for your PC.

2. Both your program and PerfectRip have the file name issue. I don't think there is any setting I can change to fix this. Other programs I use don't have this issue.

3. Take a look below to see the problem I'm talking about. The first 3 bytes are the issue.

ccd file wrote:

EF BB BF 5B 43 6C 6F 6E 65 43 44 5D 0D 0A 56 65   ï»¿[CloneCD]..Ve

cue file wrote:

EF BB BF 46 49 4C 45 20 22 54 6F 75 73 68 69 6E   ï»¿FILE "Toushin

100

(1,462 replies, posted in General discussion)

I'm still on old 32-bit, but that would be nice for many others I'm sure. This program would be a good addition to the dumping guides, once all of the issues are fixed.