1,526

Uploaded as releases https://github.com/saramibreak/DiscImag … r/releases

*2018-07-26
- added: CSS authentication
          => CSS.exe is needed. Please download and put exe into Release_ANSI directory of DIC.
             https://github.com/saramibreak/CSS/releases
- added: Linux build
- fixed: Reading directory record of GD-ROM
- fixed: /s option (/s 0 and /c2 can't use together)
- fixed: Disc log of DVD (Region)

*2018-08-12
- added: xboxswap, xgd2swap, xgd3swap command
- added: Reading param.sfo
- added: makefile for linux
- improved: Reading sub-channel (create QGenSector from QNextSector - 1 and QPrevSector + 1)
- fixed: _splitpath for linux (added null checking)

*2018-08-28
- added: Support XGD3 dumping on kreon drive
- fixed: Rereading of SecuROM/Libcrypt
- deleted: some warning

1,527

Hi sarami, i've noticed Xbox One and PS4 discs no longer have the layerbreak info in _disc.txt

Where is this info? We wish to retrieve it for the DICUI output file for easy new dump submission.

1,528 (edited by Jackal 2018-08-30 08:03:48)

@sarami, for XGD3 discs dumped with kreon, I suppose it can only dump SSv1? there's no point in adding SSv1 info for these discs, so it would be better to disable the SS.BIN output?

1,529

user7 wrote:

Xbox One and PS4 discs no longer have the layerbreak info in _disc.txt

I don't know yet how to get the L0, L1 length and layerbreak of BD.

Jackal wrote:

it would be better to disable the SS.BIN output?

It's possible. Btw, please tell me the differences of SS and SSv1 and SSv2. I don't understand yet why there's no point in adding SSv1 info for these discs.

It seems ss_sector_range.exe (1.0d-alpha) supports "XGD3 SSv1" and "XGD3 AP25". What is AP25?

            if(filled == false)
            {
                 //Fix XGD3 SSv1 ss.bin
                 m_buf[552] = 1;   // 0x01
                 m_buf[553] = 0;   // 0x00

                 m_buf[561] = 91;  // 0x5B
                 m_buf[562] = 0;   // 0x00

                 m_buf[570] = 181; // 0xB5
                 m_buf[571] = 0;   // 0x00

                 m_buf[579] = 15;  // 0x0F
                 m_buf[580] = 1;   // 0x01
            }
            else
            {
                 //Fix XGD3 AP25 ss.bin
                 m_buf[72]  = 1;   // 0x01
                 m_buf[73]  = 0;   // 0x00
                 m_buf[75]  = 1;   // 0x01
                 m_buf[76]  = 0;   // 0x00

                 m_buf[81]  = 91;  // 0x5B
                 m_buf[82]  = 0;   // 0x00
                 m_buf[84]  = 91;  // 0x5B
                 m_buf[85]  = 0;   // 0x00

                 m_buf[90]  = 181; // 0xB5
                 m_buf[91]  = 0;   // 0x00
                 m_buf[93]  = 181; // 0xB5
                 m_buf[94]  = 0;   // 0x00

                 m_buf[99]  = 15;  // 0x0F
                 m_buf[100] = 1;   // 0x01
                 m_buf[102] = 15;  // 0x0F
                 m_buf[103] = 1;   // 0x01
            }

1,530 (edited by Jackal 2018-08-30 11:29:01)

AP25 is SSv2: https://360boxmodz.wordpress.com/about- … formation/

The SSv1 dumps from kreon drives are missing the protection (angle) bytes that are needed for XGD3 (and some XGD2?) games.

1,531

Could you upload the dumping log files of XGD3 (Battlefield 3 (Disc 1) (Multiplayer/Co-Op)) and the SSv2 using XBC and ABGX360 if you still have it?

1,532 (edited by Jackal 2018-08-30 15:17:24)

Attached some files

Post's attachments

bf3.zip 18.26 kb, 2 downloads since 2018-08-30 

You don't have the permssions to download the attachments of this post.

1,533

ss_sector_range supports XGD3 SSv1 just because its possible to get those via kreon drives. We don't store those hashes in database though.

PX-760A (+30), PX-W4824TA (+98), GSA-H42L (+667), GDR-8164B (+102), SH-D162D (+6), SOHD-167T (+12)

1,534

https://github.com/saramibreak/DiscImag … r/releases
*2018-09-01
- added: Drive speed of bd and xbox. (If you don't use this, please specify 0)
- changed: No output XGD3 SSv1
- improved: Security Sector log of XBOX (added timestamp etc.)

1,535 (edited by xTMODx 2018-09-02 22:52:37)

I am getting different hash for a coverdisc dump
old DIC produce no error but the new has one error

https://i.imgur.com/aJjWPGk.jpg

DiscImageCreator_20160805_dump.7z https://www65.zippyshare.com/v/vMoPfE4C/file.html

DiscImageCreator_20180901_dump.7z https://www65.zippyshare.com/v/atdJUszC/file.html

1,536

More and more strange cases recently. Also http://forum.redump.org/post/62651/#p62651 and http://forum.redump.org/post/62472/#p62472

Does the c2 feature work properly?

Post's attachments

41-2_JPN_Bikini Karate(DISK2).7z 3.52 mb, 2 downloads since 2018-09-03 

AP_CDR_1998-02.7z 5.89 mb, 3 downloads since 2018-09-03 

Lost & Found Volume 3 (Disc 1 of 3) - Deep Fear (USA) [81804] (Disc 1 of 2).7z 3.24 mb, 2 downloads since 2018-09-03 

You don't have the permssions to download the attachments of this post.

1,537

xTMODx wrote:

DiscImageCreator_20160805_dump.7z

EdcEcc.txt says

LBA[305469, 0x4a93d], This sector is audio or scrambled data or corrupt data
LBA[305470, 0x4a93e], This sector is audio or scrambled data or corrupt data
LBA[305471, 0x4a93f], This sector is audio or scrambled data or corrupt data
LBA[305472, 0x4a940], This sector is audio or scrambled data or corrupt data
User data vs. ecc/edc match all
xTMODx wrote:

DiscImageCreator_20180901_dump.7z

LBA[305469, 0x4a93d], MSF[67:54:69], mode 1
LBA[305470, 0x4a93e], MSF[67:54:70], mode 1
LBA[305471, 0x4a93f], MSF[67:54:71], mode 1
LBA[305472, 0x4a940], MSF[66:d4:72], unknown mode: a1
[ERROR] Number of sector(s) where mode(0x0f) is unknown: 1
    Sector: 305472, 

mainError.txt

LBA[305469, 0x4a93d]: Track[01]: Invalid mode. 
========== LBA[305469, 0x4a93d]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 66 D4 69 81   ............f.i.
LBA[305470, 0x4a93e]: Track[01]: Invalid mode. 
========== LBA[305470, 0x4a93e]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 66 D4 70 A1   ............f.p.
LBA[305471, 0x4a93f]: Track[01]: Invalid mode. 
========== LBA[305471, 0x4a93f]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 66 D4 71 A1   ............f.q.
LBA[305472, 0x4a940]: Track[01]: Invalid mode. Invalid reserved byte. Skip descrambling
========== LBA[305472, 0x4a940]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 66 D4 72 A1   ............f.r.
0010 : 00 28 00 1E 80 08 60 06  A8 02 FE 81 80 60 60 28   .(....`......``(
0020 : 28 1E 9E 88 68 66 AE AA  FC 7F 01 E0 00 48 00 36   (...hf.......H.6
0030 : 80 16 E0 0E C8 04 56 83  7E E1 E0 48 48 36 B6 96   ......V.~..HH6..
0040 : F6 EE C6 CC 52 D5 FD 9F  01 A8 00 7E 80 20 60 18   ....R......~. `.
0050 : 28 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   (...............
0060 : 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................
0070 : 00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00   ................

Normal scrambled mode is '0x61' (mode 1 disc) or '0x62' (mode 2 disc). But these sectors are irregular (0x81, 0xA1). Old DIC doesn't descramble these sectors that irregular scrambled mode has.
DIC of 2017-2018 descrambles these. But 305472 sector is incomplete as data sector. This is a mastering error. So, latest DIC perserves this sector as is.

F1ReB4LL wrote:

Does the c2 feature work properly?

I see it later.

1,538

So i can submit from new DIC build and error count is 4 or 1? CDmage reports 4 errors

1,539

How about edccchk v1.26?

1,540 (edited by Jackal 2018-09-04 17:52:18)

Another issue where DIC gives 3 errors (2 discs give the same dump), but a CloneCD dump from non-plextor drive gives 0 errors.

Can you check what's wrong?

1,541

Hey Sarami. I've had a problem with some PC games with SafeDisc. Occaisonally, DIC will report an error count of 288 in a SafeDisc sector, and will attempt to reread it over and over again, never succeeding.

Let me know if you want some specific examples.

1,542

sarami wrote:

How about edccchk v1.26?

I have only edcchk 1.11 here the result

Post's attachments

1.jpg 72.07 kb, 1 downloads since 2018-09-03 

You don't have the permssions to download the attachments of this post.

I checked xTMODx's issue. The problem is because of mastering error on a disc. Few months ago the algorithm was changed from:

"Always descramble sectors of data track"

to:

"Descramble sector of data track if there's a proper sync and mode"

New DIC doesn't descramble last sector because of invalid mode.
So in this case DIC worked as expected.

1,544 (edited by reentrant 2018-09-03 21:10:58)

Jackal wrote:

Another issue where DIC gives 3 errors (2 discs give the same dump), but a CloneCD dump from non-plextor drive gives 0 errors.

https://www12.zippyshare.com/v/xttyLELo/file.html

Can you check what's wrong?

Jackal I also have disc (german coverdisk) that also gives me no read errors but essentially the data returned by non PX-device is bad. I bet this is some weird mastering error that only scrambled reader can handle.

Some drives incorrectly handle such sectors in firmware and return wrong data thus masking read errors!!

LBA[041489, 0x0a211], MSF[09:15:14], mode 1 User data vs. ecc/edc doesn't match
LBA[041490, 0x0a212], MSF[8d:a0:6c], invalid sync
LBA[041491, 0x0a213], MSF[8a:20:2e], invalid sync
LBA[041492, 0x0a214], MSF[09:15:17], mode 1

Option 2:

I have a disc that triggers some bug in Plextor firmware. Yes - Plextor firmware has bugs! The effect is the same as yours. Few sectors corrupted in the middle of the disc. I don't remember exactly which disc it was, but reripping solved the problem. Have you tried reripping your disc?

I think my disc returned some C2 errors & screwed 50-100 consecutive sectors without returning any C2 data.

Another Plextor bug: Some discs with -153 offset from 'takt' trigger a weird bug and return constant C2 data pattern 0F0F0F F0F0F0. 24 bytes in total corrupted.

I'm on a spree today. Another issue: only 10 SecuROM sectors for http://redump.org/disc/55050/

Logs: https://mega.nz/#!XW5TgJIT!T8Uh9_u8xq20 … 1rIOIutUdM

I cooperated with AlMagno and he made a sub dump with CDTool, I then cleaned it with CDGTool and found misdetected SecuROM sector:

00:01:74
01:08:50
01:14:68
01:37:49
02:04:22
02:28:25
02:49:58
02:55:71
03:21:07 !
03:26:61
03:30:54
Found Q CRC error
-----------------
Q CRC value from the file       : 3B01
Computed Q CRC value            : F730
Offsets                         : 00 01 02 03 04 05 06 07 08 09  10 11
Q fields                        : CA TR PO RM RS RF ZE AM AS AF  CR CR
Q subcode data just before error: 41 01 01 03 19 06 00 03 21 06  05 70
Q subcode data with error       : 41 01 01 03 19 27 00 03 21 03  3B 01
Q subcode data just after error : 41 01 01 03 19 08 00 03 21 08  2B 16
Which offset to change, enter q=quit, s=skip, or an offset: 0 to 11: s

1,546 (edited by sarami 2018-09-08 12:59:41)

xTMODx wrote:

I have only edcchk 1.11 here the result

I understood CDmage looked invalid mode sector on error sector and edcchk didn't look it on non error sector.

reentrant wrote:

"Always descramble sectors of data track"

to:

"Descramble sector of data track if there's a proper sync and mode"

No, to be exact...

"Descramble sector of data track if there's a proper sync and mode"

to:

"Always descramble sectors of data track"

to:

"Descramble sector of data track if there's a proper sync and reserved (only mode 1)"
reentrant wrote:

Q CRC value from the file       : 3B01
Computed Q CRC value            : F730

3B01 XORed with 0x8001 is BB01, not F730. So perhaps this sector also has random errors in RMSF or AMSF or CRC.
There are huge suberror in this disc, so it needs to be dumped by other good-condition disc.

ajshell1 wrote:

I've had a problem with some PC games with SafeDisc.

Plz upload the log of latest version.


F1ReB4LL wrote:

Does the c2 feature work properly?

I say yes if the drive reports c2 errors properly.

1,547 (edited by sarami 2018-09-04 06:27:13)

Jackal wrote:

Another issue where DIC gives 3 errors (2 discs give the same dump), but a CloneCD dump from non-plextor drive gives 0 errors.

https://www12.zippyshare.com/v/xttyLELo/file.html

Can you check what's wrong?

mainError

0900 : 7D A4 4D 62 45 A3 B0 63  20 29 7D 4A 9B E6 87 CC   }.MbE..c )}J....
0910 : 98 12 82 C1 B0 21 D7 BB  00 FF FF FF FF FF FF FF   .....!..........
0920 : FF FF FF 00 08 95 16 61  00 9B D5 CB A3 0A E1 A3   .......a........
LBA[041491, 0x0a213]: Track[01]: Invalid sync. Skip descrambling
========== LBA[041491, 0x0a213]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : AA 83 EC 83 12 E2 67 09  6A 0A 88 8C 8A 20 2E 86   ......g    j.... ..
0010 : 23 01 3D AF 2F 45 EF 35  73 52 F8 2F 48 0D 05 18   #.=./E.5sR./H...

Sync exists, but it's slided behind 24 bytes. Perhaps drive's cache is broken (or firmware/drive/dic bugs?). It maybe is fixed if rereading (but it's not supported yet in this case).

1,548

sarami wrote:

3B01 XORed with 0x8001 is BB01, not F730. So perhaps this sector also has random errors in RMSF or AMSF or CRC.
There are huge suberror in this disc, so it needs to be dumped by other good-condition disc.

Ok. I'll look for another new disc to go back to dump.

Thank you!

1,549

Okay sarami, here are some logs:

This disc has some additional damage to it, but I don't think that's what is causing the attempted rereads on sectors with SafeDisc. I've seen that 288 bit error thing occur in other discs, but I don't remember which discs.

Post's attachments

startopia.zip 228.77 kb, 2 downloads since 2018-09-04 

You don't have the permssions to download the attachments of this post.

1,550

http://forum.redump.org/post/58182/#p58182
"312" sectors are intentional c2 errors, but I don't know all intentional errors are 312.
At least please check rereading at 10000 times.

discimagecreator cd f Startopia (USA) 32 /c2 10000 /d8 /sf