1,601

FatArnold wrote:

I tried dumping some gd-rom today with my PX-708. Unfortunately I get a segfault as soon as I enable /c2. Without /c2 the dump starts. Happens both on linux and the latest windows release.

Uploaded test version.

F1ReB4LL wrote:

DIC dump to the left, old bin-cue dump to the right. And I really don't think these 2 bytes should be zeroed.

How about cdtoimg?

1,602 (edited by ajshell1 2018-09-23 05:01:06)

I'm going to try dumping that disc with all of the other methods I can find, and then see what sarami has to say.

I finished that data dump. It doesn't match a dump that I made with an older version of DIC

EDIT: setting the drive speed to 4x seems to have fixed it. Yay!

And the dump that I made matches a dump with an older version of DIC.

sarami wrote:
FatArnold wrote:

I tried dumping some gd-rom today with my PX-708. Unfortunately I get a segfault as soon as I enable /c2. Without /c2 the dump starts. Happens both on linux and the latest windows release.

Uploaded test version.

Thank you so much for everything! Tried reading a GD-ROM just now and the dump went just as it should.

However, now it segfaults after the dump. But all the data seem to be dumped correctly smile

AppVersion
    x86, AnsiBuild, 20180923 110347
/c2 val1 is omitted. set [4000]
/c2 val2 is omitted. set [0]
/home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/ doesn't exist, so create.
CurrentDirectory
    /home/rebecca/Desktop/DiscImageCreator_linux_test
WorkingPath
     Argument: 4Wheel/4Wheel.bin
     FullPath: /home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/4Wheel.bin
        Drive: /
    Directory: home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/
     Filename: 4Wheel
    Extension: .bin
StartTime: 2018/09/23(Sun) 11:16:05
Set the drive speed: 2822KB/sec
This drive supports [OpCode: 0xd8, SubCode: 0]
This drive supports [OpCode: 0xd8, SubCode: 1]
This drive supports [OpCode: 0xd8, SubCode: 2]
This drive supports [OpCode: 0xd8, SubCode: 8]
Checking SubQ adr (Track) 18/18
Checking SubRtoW (Track) 18/18
Reading DirectoryRecord    1/   1
Set OpCode: 0xd8, SubCode: 8(Raw)
Creating .scm from 45000 to 549151 (LBA) 549150
No C2 errors
Descrambling img (LBA) 504149/504150
Exec /home/rebecca/Desktop/DiscImageCreator_linux_test/./EccEdc_linux.out check /home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/4Wheel.img
FILE: /home/rebecca/Desktop/DiscImageCreator_linux_test/4Wheel/4Wheel.img
Checking sectors (LBA) 504149/504149
[NO ERROR] User data vs. ecc/edc match all
Segmentation fault

Logs: https://mega.nz/#!6gAACaYK!AC-o6GHrPiW9 … yJStw7GHsY

1,604 (edited by celebi 2018-09-23 16:49:29)

But READ12 (0xa8) can't read it. Perhaps READ CD (0xbe) is also same. It's weird...
Is this a protection? I don't know. Maybe iR0b0t or Jackal or reentrant know it?

I re-checked again with CD Manipulator and Clone CD, it seems that even those tools don't know how to handle this sector properly. Clone CD fills sector 150 with "55" while CD Manipulator fills the same sector with "00". Does that make any sense? Which tool should I trust more?

Would it be helpful to upload a subdump dump?

All contributions are from my own disks and only for my own documentation and backup purposes. Don't ask me to share any files. If you want the disks, buy them.

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

1,606

Is there any command combination that will restart an interrupted run? I got a Address boundary error partway through retrying sectors with c2 errors, and I'd like to tell it to continue testing the sectors noted in the c2Errors file. It looks like you can specify the sectors to retry yourself manually, but it'd be much nicer if it could resume without too much manual intervention.

1,607 (edited by celebi 2018-09-23 18:23:12)

In any way plz upload SCM dump that HAS that faulty sector...

Sorry, the sector 150 I'm referring to is at 00:02:00.

What's the best way to obtain an .scm dump without DIC? Dumping with DIC fails so early that it doesn't create a .scm file. I tried with "cd", "data" and "audio" option.

All contributions are from my own disks and only for my own documentation and backup purposes. Don't ask me to share any files. If you want the disks, buy them.

1,608

Uploaded test. http://www.mediafire.com/file/eq80y20l9 … st.7z/file

fixed: Skipped this error.

LBA[000000, 0000000]: [F:ReadCDForFileSystem][L:574]
    Opcode: 0xa8
    ScsiStatus: 0x02 = CHECK_CONDITION
    SenseData Key-Asc-Ascq: 03-02-83 = MEDIUM_ERROR - VENDOR UNIQUE ERROR
lpCmd: a8, 00, 00, 00, 00, 00, 00, 00, 00, 01, 00, 00
dwBufSize: 2048

added: support unnamed protection
I created 2 text files. 1st line is comment. 2nd line is file name.
EdcEccErrorProtect.txt (e.g. http://redump.org/disc/45814/ )

# This is a file to fix the edc/ecc error sector. Please write the file name you want to fix the error
CD.IDX

ReadErrorProtect.txt (e.g. http://redump.org/disc/43270/ )

# This is a file not to read sector. Please write the file name you want to read skipping
SYSTEM.LSK

To use this file, please use /sf option.


added: support laserlock and proring (needs optiarc drive)
How to dump (almost same CDArchive)
e.g. http://redump.org/disc/30992/
1. dump the disc except the protected file using plextor drive.

DiscImageCreator.exe cd <driveletter> <filename> <drivespeed> /sf

* DIC detects the protection like this.

Detected [LASERLOK.IN], from 337 to 10336

2. when dumping finished, eject the disc from plex drive and insert it in optiarc drive.
3. dump the protected file

DiscImageCreator.exe data <driveletter> <filename> <drivespeed> 337 10338 /sf /sk 76

* CD has a offset, so please specify more +1 or +2 than endlba. (e.g. 10336 -> 10338)
* /sk is below.

        /sk     Skip sector for physical protect (e.g. proring, LaserLock etc.)
                        val     sector num

4. merge plextor image and optiarc image

DiscImageCreator.exe merge <plex img> <opti img>

* I don't test yet about other ring protection.


FatArnold wrote:

However, now it segfaults after the dump. But all the data seem to be dumped correctly

cue file is missing. Is windows build also same?

1,609 (edited by reentrant 2018-09-24 07:04:40)

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?

1,610 (edited by celebi 2018-09-25 20:29:34)

Uploaded test. http://www.mediafire.com/file/eq80y20l9 … st.7z/file

fixed: Skipped this error.

Thanks a lot, with this test version I was able to dump this disk. Interestingly the checksums doesn't match with either CD Manipulator or Clone CD.

And even more interesting is that edcchk hasn't detected an error in sector 150 (00:02:00) and just detected it as Mode 1 data sector.

All contributions are from my own disks and only for my own documentation and backup purposes. Don't ask me to share any files. If you want the disks, buy them.

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?

1,612

Nope, all sectors are mode 1.

All contributions are from my own disks and only for my own documentation and backup purposes. Don't ask me to share any files. If you want the disks, buy them.

1,613

celebi wrote:

Interestingly the checksums doesn't match with either CD Manipulator or Clone CD.

And even more interesting is that edcchk hasn't detected an error in sector 150 (00:02:00) and just detected it as Mode 1 data sector.

Because descrambled sector of LBA 0 (sector 150) is no problem. As you say, CD Manipulator and Clone CD is padding this sector by 0x00 or 0xff.

This is a similar case http://forum.redump.org/post/56314/#p56314

Firstly, you need to check by cdtoimg. http://www.mediafire.com/file/9b31r4fv4 … g.rar/file
This is a simple 0xd8 ripping tool. Please check if 1st sector is really same as dic's 1st sector.

Secondly, you need to check the pregap sector of 1st track.

DiscImageCreator.exe audio <DriveLetter> <Filename> <DriveSpeed> -5000 0

Please check the position of the sync (00 FF FF .. FF 00)

1,614 (edited by celebi 2018-09-29 10:24:14)

sarami, the dumps of cdtroimg and the scrambled DIC file differ. From what I can tell, DIC is missing the first 32 bytes of the image.

First few bytes of the DIC .scm image:
https://abload.de/img/dicscmrhd8k.png

First few bytes of the cdtoimg image:
https://abload.de/img/cdtoimgn8cv1.png

Trying to read the pregap threw lots of errors - log file and resulting dump available at https://www87.zippyshare.com/v/Xhoz9VMK/file.html

Is it possible that this is a disc with a mastering error instead of a copy protection?

Thanks for your help!

~celebi

All contributions are from my own disks and only for my own documentation and backup purposes. Don't ask me to share any files. If you want the disks, buy them.

1,615 (edited by sarami 2018-09-29 14:42:29)

celebi wrote:

DIC is missing the first 32 bytes of the image.

First 40 bytes are cut. Because .scm is an image the offset is calculated. I confirmed cdtoimg image was same as _disc log.

========== 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..
celebi wrote:

Trying to read the pregap threw lots of errors - log file and resulting dump available at

Thanks. I found offset of the pregap (and TOC) area was -22.

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

Due to incomplete/garbage sync from 0020 to 0027, offset of LBA 0 is shifted to -20.

celebi wrote:

Is it possible that this is a disc with a mastering error instead of a copy protection?

Probably yes. F1ReB4LL comments about Gulf War: Soukouden -> http://redump.org/disc/45432/

1,616 (edited by reentrant 2018-09-29 14:51:47)

This example shows the power of DIC + Plextor drives smile

1,617 (edited by celebi 2018-09-29 15:00:36)

Thanks sarami for your great support!!

Is it now safe to submit the DIC dump? Which comment should I choose regarding this weird sector 150? What about the error count -  "1" as reported by CD Manipulator and CloneCD or "0" as reported by DIC+edcchk?

All contributions are from my own disks and only for my own documentation and backup purposes. Don't ask me to share any files. If you want the disks, buy them.

1,618

Here a dump with CATALOG 000000000000 (one 0 less than normal): http://redump.org/disc/55821/

Logs: https://mega.nz/#!T1gSQS6Q!L-frCQXIBkqX … fy3Pf41Fo8

DIC bug?

1,619

Jackal wrote:

Here a dump with CATALOG 000000000000 (one 0 less than normal):

fixed: 2nd argument of snprintf (linux only) http://www.mediafire.com/file/uw3e03kdk … t.tar/file

celebi wrote:

Which comment should I choose regarding this weird sector 150? What about the error count -  "1" as reported by CD Manipulator and CloneCD or "0" as reported by DIC+edcchk?

Perhaps admin or moderator will judge it properly.

1,620

Hey sarami. Did you ever address my recent post on SafeDisc? nightson has also talked to me recently, stating that he is getting the same issue.

1,621

Your startopia and Battlefield 1942 have C2 errors except 312 and 288 bits. You or other person needs to get mint-conditioin disc, I think.

1,622 (edited by niemand 2018-10-04 06:57:28)

I've got a disc with three audio tracks followed by one data track. The dump completes without /ms, but the last track is misaligned. Running DiscImageCreator with /ms seems to work fine, but Read error. padding [2352byte] starts to appear around the area where the data track begins.

1,623

some changed about /ms http://www.mediafire.com/file/eq80y20l9 … st.7z/file

niemand wrote:

but Read error. padding [2352byte] starts to appear around the area where the data track begins.

My plextor (755sa, 4824a) can read only 6 sectors about lead-in of 2nd session.
191391 is the last sector of 1st session. 191392 - 195891 are leadin of 2nd session. 195892 is the 1st sector of 2nd session.

LBA[191389, 0x2eb9d], audio
LBA[191390, 0x2eb9e], audio
LBA[191391, 0x2eb9f], audio
LBA[191392, 0x2eba0], MSF[43:b3:67], mode 2 no edc, Subheader isn't same. [0x10]:0000, [0x11]:0x28, [0x12]:0x20, [0x13]:0x1e, [0x14]:0x80, [0x15]:0x08, [0x16]:0x40, [0x17]:0x06, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[28]), [3](SubMode[20]), Form 2, [4](CodingInfo[1e])Reserved, 
LBA[191393, 0x2eba1], MSF[43:b3:68], mode 2 no edc, Subheader isn't same. [0x10]:0000, [0x11]:0x28, [0x12]:0x20, [0x13]:0x1e, [0x14]:0x80, [0x15]:0x08, [0x16]:0x40, [0x17]:0x06, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[28]), [3](SubMode[20]), Form 2, [4](CodingInfo[1e])Reserved, 
LBA[191394, 0x2eba2], MSF[43:b3:69], mode 2 no edc, Subheader isn't same. [0x10]:0000, [0x11]:0x28, [0x12]:0x20, [0x13]:0x1e, [0x14]:0x80, [0x15]:0x08, [0x16]:0x40, [0x17]:0x06, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[28]), [3](SubMode[20]), Form 2, [4](CodingInfo[1e])Reserved, 
LBA[191395, 0x2eba3], MSF[43:b3:70], mode 2 no edc, Subheader isn't same. [0x10]:0000, [0x11]:0x28, [0x12]:0x20, [0x13]:0x1e, [0x14]:0x80, [0x15]:0x08, [0x16]:0x40, [0x17]:0x06, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[28]), [3](SubMode[20]), Form 2, [4](CodingInfo[1e])Reserved, 
LBA[191396, 0x2eba4], MSF[43:b3:71], mode 2 no edc, Subheader isn't same. [0x10]:0000, [0x11]:0x28, [0x12]:0x20, [0x13]:0x1e, [0x14]:0x80, [0x15]:0x08, [0x16]:0x40, [0x17]:0x06, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[28]), [3](SubMode[20]), Form 2, [4](CodingInfo[1e])Reserved, 
LBA[191397, 0x2eba5], MSF[43:b3:72], mode 2 no edc, Subheader isn't same. [0x10]:0000, [0x11]:0x28, [0x12]:0x20, [0x13]:0x1e, [0x14]:0x80, [0x15]:0x08, [0x16]:0x40, [0x17]:0x06, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[28]), [3](SubMode[20]), Form 2, [4](CodingInfo[1e])Reserved, 
LBA[191398, 0x2eba6], MSF[00:00:00], zero sync
LBA[191399, 0x2eba7], MSF[00:00:00], zero sync
LBA[191400, 0x2eba8], MSF[00:00:00], zero sync
 :
LBA[195889, 0x2fd31], MSF[00:00:00], zero sync
LBA[195890, 0x2fd32], MSF[00:00:00], zero sync
LBA[195891, 0x2fd33], MSF[00:00:00], zero sync
LBA[195892, 0x2fd34], MSF[43:33:67], mode 2 form 1, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[00]), [3](SubMode[00]), Form 1, [4](CodingInfo[00])
LBA[195893, 0x2fd35], MSF[43:33:68], mode 2 form 1, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[00]), [3](SubMode[00]), Form 1, [4](CodingInfo[00])
LBA[195894, 0x2fd36], MSF[43:33:69], mode 2 form 1, SubHeader[1](IsInterleaved[00]), [2](ChannelNum[00]), [3](SubMode[00]), Form 1, [4](CodingInfo[00])
 :

1,624

sarami wrote:

Perhaps admin or moderator will judge it properly.

I haven't understood if the sector is damaged/wrongsized or just has some additional sync bytes before the actual sync.

1,625

I think "just has some additional sync bytes before the actual sync." But the dumping of another disc is needed for verification.