1

(0 replies, posted in Dumps)

http://redump.org/disc/24538/

Mastering Code: GM Records    0401657009    CLIN5B Colin 05    CDPROJEKT
Mastering SID Code: IFPI LT58
Data Side Mould SID Code: IFPI Z931
Cover Side Mould SID Code: IFPI Z942

My disc has different mastering codes but apart from that everything matches 1:1

2

(5 replies, posted in Dumps)

> All models? or only 716A?
PX 716 and 760 affected. I don't have any other plextors to test.

> Always same pattern? Club Saturn has ... F0 F0 F0 00 00 00 0F 0F 0F 0F ...
Yes, it's this pattern. Exactly 24 bits are bad.

Keep in mind I have seen discs protected with SafeDisc which gave (288+24 = 312 C2 errors) - ajshell case. Out of those 312 C2 errors 24 bytes are spurious and should not be counted. This is weird. I know.

Did t....p method return any C2 bits?

When I compared bad data returned by my PX drives and correct data returned by non-PX drives, not all bytes marked as C2 were bad. Sometimes some bytes were good. This could be the case with your disc...

3

(0 replies, posted in Dumps)

Moved to single topic. Delete this post.

4

(5 replies, posted in Dumps)

This is known bug in Firmware of Plextor drives. 24 C2 errors in pattern: F0F0F0 0F0F0F.
I have tons of such discs. It cannot be fixed by rereading.

The algorithm is to use different drive and issue DIC data command and patch original image with data read from the other device. There's no other way.

You have to use /c2 on the other drive to be sure. I use 2 different drives, and after making sure the data is equal on both I patch the image.

That look on your face when you expected at least one new hash, and got nothing wink

6

(49 replies, posted in General discussion)

Wow, I forgot about this topic wink

If you're using version from 23th reply in this thread specify cue path as last argument!

7

(13 replies, posted in Dumps)

For your information: when your device reads data it also fixes read errors internally (Reed-Solomon codes) at the lowest level. What ajshell1 is doing is fixing read errors at higher level (RSPC codes).

I can imagine a CD with altered frames at lowest level that are automatically corrected by RS code. You won't even notice that the drive fixed it.

How about that? wink

8

(0 replies, posted in Fixes & additions)

http://redump.org/disc/5762/

I didn't dump it, just found more info on the net...

Region: Czech,Hun,Pl,Sk
New barcode

9

(1,651 replies, posted in General discussion)

This example shows the power of DIC + Plextor drives smile

10

(1,651 replies, posted in General discussion)

00 FF FF FF FF FF FF FF FF FF FF 00 01 82 00 61

When you XOR with 0x60 you get 1 = Mode 1. It makes sense.
All other sectors are mode 2?

Ok ^-^

Is it safe to assume those tools produced proper track 1? PSX games don't have mastering errors?

13

(1,651 replies, posted in General discussion)

sarami: It's going in a good direction but to speed things up you could also code sector range extraction from those discs. It's way faster to read specific 'n' sectors than entire cd, and merge command that merges single sectors - just like CDArchive does.

celebi:

========== OpCode[0xd8]: SubCode[0]: Check Drive + CD offset ==========
========== LBA[000000, 0000000]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 5C 7A B9 E3 32 C9 D5 96  DF 2E D8 1C 5A 89 FB 26   \z..2.......Z..&
0010 : C3 5A D1 FB 1C 43 49 F1  F6 C4 46 D3 72 DD E5 99   .Z...CI...F.r...
0020 : 00 FF FF FF FF FF FF FF  00 FF FF FF FF FF FF FF   ................
0030 : FF FF FF 00 01 82 00 61  00 28 00 1E 80 08 60 06   .......a.(....`.
0040 : A8 02 FE 81 80 60 60 28  28 1E 9E 88 68 66 AE AA   .....``((...hf..
0050 : FC 7F 01 E0 00 48 00 36  80 16 E0 0E C8 04 56 83   .....H.6......V.
0060 : 7E E1 E0 48 48 36 B6 96  F6 EE C6 CC 52 D5 FD 9F   ~..HH6......R...
0070 : 01 A8 00 7E 80 20 60 18  28 0A 9E 87 28 62 9E A9   ...~. `.(...(b..
0080 : A8 7E FE A0 40 78 30 22  94 19 AF 4A FC 37 01 D6   .~..@x0"...J.7..

I don't like this lines:
0020 : 00 FF FF FF FF FF FF FF  00 FF FF FF FF FF FF FF   ................
0030 : FF FF FF 00 01 82 00 61

D8 reads ok, but 'higher level' read commands fail. So my conclusion is that there's something either with Header or ECC/EDC.
It looks like these devices don't like such patterns?

14

(1,651 replies, posted in General discussion)

By saying sector 150 you mean:
A: Sector with MSF 00:02:00
B: Sector with MSF 00:04:00

Some tools start sectors numbering from 0 and some from 150...
In any way plz upload SCM dump that HAS that faulty sector...

15

(1,651 replies, posted in General discussion)

That 'data' command looks ok.

To be 100% sure I would look at the resulting image under hex editor and cut end / paste start sectors to match 'cd' image if there are some inconsistencies. Or maybe this is not necessary at all.

16

(1,651 replies, posted in General discussion)

ajshell1: I have a weird theory. My Plextor on some discs with offset -153 gives me C2 errors with 24 bad bits (I know this is firmware bug). You on the other side have discs with 288 bits. When you add both you get 312 = value valid for SafeDisc. I think you might be experiencing similar bug but with different "pattern"...

Could you rip with non plextor drive and data command and /c2?

17

(49 replies, posted in General discussion)

Here's is some info for DVD and BD (correction codes): http://citeseerx.ist.psu.edu/viewdoc/do … p;type=pdf

DVDs have RSPC code and can contain bad sectors but this has to be done in factory. I don't know if home devices can burn discs with incorrect correction codes...

18

(1,651 replies, posted in General discussion)

Or the fix is to force /sf flag even when protection wasn't found.

19

(49 replies, posted in General discussion)

I'll look at it during the weekend. Should be possible...

20

(49 replies, posted in General discussion)

I used HxD Hex Editor. It's a simple copy & paste app. You don't have to use it anymore (use new CDArchive).

21

(49 replies, posted in General discussion)

231096 - 230946 = 150 = 2sec = pregap. Try to lower it by few hundred sectors. DIC dump is bugged if error range crosses tracks & pregap area...

22

(49 replies, posted in General discussion)

_Maki wrote:
reentrant wrote:

Run EdcEcc with fixex command. It will replace them with 0x55 and retry...
I have OptiArc 7290.

LBA[230940, 0x3861c], mode 1
LBA[230941, 0x3861d], mode 1
LBA[230942, 0x3861e], mode 1
LBA[230943, 0x3861f], mode 1
LBA[230944, 0x38620], mode 1
LBA[230945, 0x38621], mode 1
LBA[230946, 0x38622], This sector has invalid sync
LBA[230947, 0x38623], This sector has zero sync
LBA[230948, 0x38624], This sector has zero sync
LBA[230949, 0x38625], This sector has zero sync
LBA[230950, 0x38626], This sector has zero sync
LBA[230951, 0x38627], This sector has zero sync
LBA[230952, 0x38628], This sector has zero sync
LBA[230953, 0x38629], This sector has zero sync
LBA[230954, 0x3862a], This sector has zero sync
LBA[230955, 0x3862b], This sector has zero sync
LBA[230956, 0x3862c], This sector has zero sync

Why those sectors are bad? I think EdcEcc will fix also this:
LBA[230946, 0x38622], This sector has invalid sync

I can introduce another command fixex2 which would fix sectors in specific range...


Hey thanks, that helped! Time to reextract those sectors...

I don't really know why those sectors are bad. It happened when I dumped it with /frs and /fre.
Every sector after that range has bad sync. You can see it in the original _EdcEcc.txt

Maybe I blanked it too close to the second track?

What are the values of parameters:  /frs and /fre? Only sectors inside range should be bad. Try smaller range (maybe it cannot cross tracks, dunno).

I uploaded new CDArchive that accepts cue path as argument for -m (merge mode). Sectors are merged to correct track file now.

23

(49 replies, posted in General discussion)

Run EdcEcc with fixex command. It will replace them with 0x55 and retry...
I have OptiArc 7290.

LBA[230940, 0x3861c], mode 1
LBA[230941, 0x3861d], mode 1
LBA[230942, 0x3861e], mode 1
LBA[230943, 0x3861f], mode 1
LBA[230944, 0x38620], mode 1
LBA[230945, 0x38621], mode 1
LBA[230946, 0x38622], This sector has invalid sync
LBA[230947, 0x38623], This sector has zero sync
LBA[230948, 0x38624], This sector has zero sync
LBA[230949, 0x38625], This sector has zero sync
LBA[230950, 0x38626], This sector has zero sync
LBA[230951, 0x38627], This sector has zero sync
LBA[230952, 0x38628], This sector has zero sync
LBA[230953, 0x38629], This sector has zero sync
LBA[230954, 0x3862a], This sector has zero sync
LBA[230955, 0x3862b], This sector has zero sync
LBA[230956, 0x3862c], This sector has zero sync

Why those sectors are bad? I think EdcEcc will fix also this:
LBA[230946, 0x38622], This sector has invalid sync

I can introduce another command fixex2 which would fix sectors in specific range...

24

(49 replies, posted in General discussion)

It would be easier if I implement in CDArchive cue file support so that sectors are merged in the right track.
I can do it over weekend...

25

(49 replies, posted in General discussion)

_Maki wrote:

Hello everyone,

I'm currently trying to dump a few of my favorite games that are protected by those pesky rings of unread sectors in the disc. I've read up on the general way to go about it, but I do lack the tools and basically instructions to use them. I already own a Plextor drive and an Optiarc, and I'm ready to put the effort into it. But I would obviously appreciate your help. smile

Hello,
   The steps are:

1) You need to get error range. Launch alcohol, set: ignore read error, fast error skip, ass (100 sectors step)
write down 2 values, when the error range starts and where it ends. Say error range is from sector begin=100 000,  end=120 000
2) Get DIC: DiscImageCreator_2018_02_29_Skip.rar
3) Launch disc ripping with DIC but add 2 extra parameters: /frs 99900 /fre 120100

Note that I extended a bit this range because I don't want Plextor to read near it
If you get any C2 errors before or after error range, extend it even more.
When ripping you might have to extend its beginning by 100 sectors and end by 5000! because Plextor is very bad at reading neer the ring.
In your case it would be /frs 99000 /fre 125000
The purpose of commands above is to fast skip error range and save the drive from rereading into this bad area

In next steps we'll be reading it with other tool and optiarc
4) Get CDArchive.rar
5) Execute: CDArchive.exe -x <driveNo> -d "<dir_where_sectors_are_dumped_to>" -e <rangeStart> <rangeEnd> <retries> <skipCount> <overread> <dir> "<bin_image_path>"

CDArchive.exe -x f -d "c:\Redump\PX\SECT" -e 90 210 10 3 10 fb "c:\Redump\PX\FXX.bin"
f = my OPTI drive
c:\Redump\PC\SECT - here it extracts sectors, this directory must exist
90 = range start, the same value as /frs
210 = range end, the same value as /fre
10 = sector read retry count
3 = if 3 consecutive sectors fail to read then drop reading in this direction
10 = sector overread count, leave 10 default
fb = read forward first, then backwards
c:\Redump\PX\FXX.bin - binary track 1 that is used as reference to check which sectors are bad and should be read by optiarc

6) Once process is complete you will have single sectors in c:\Redump\PX\SECT. Now it's time to merge them into image.

You do this by this command: CDArchive.exe -x f -d "c:\Redump\PX\SECT" -m "c:\Redump\PX\FXX.bin"

It's iterative process, you can once again run CDArchive.exe -x f -d "c:\Redump\PX\SECT" -e 90 210 10 3 10 fb "c:\Redump\PX\FXX.bin" to extract more sectors and later merge them with CDArchive.exe -x f -d "e:\Redump\PX\SECT" -m "c:\Redump\PX\FXX.bin"

After merging launch EccEdc with fixex command (argument is CUE file). This step is required as some sectors read by OptiArc might not be 100% fine. EccEdc will replace whem with 0x55, and you can retry step 6 until no sectors are read.

Make sure to delete contents of c:\Redump\PX\SECT after each iteration, as you don't want to merge the same sectors all the time.

Note #1:
It's very important to set skip value to at least 3-5 to eliminate case when there are few unreadable sectors and then some readable after those.

Note #2:
For discs with multiple rings like Laserlock you have to rip with DIC using biggest error range and repeat process with CDArchive with smaller error ranges as well as specifying valid ranges to extract good sectors!

Sorry for my english!