DiscImageCreator

[antimatter]

, Having problems dumping a coverdisc with DIC.

Dumped with DIC test branch from 20180515.
DIC finds

Code: Select all

Detected intentional subchannel in LBA -1 => SecuROM Type 4 (a.k.a. NEW)

after completing, subIntention.txt only has 1 line

Code: Select all

MSF: 00:01:74 Q-Data: 410100 00:00:00 00 00:01:74 0121

tested bin file for protection & errors:
ArayScanner2023, BurnOut1.03, ProtectionID v6.9.0 find no protection.
edccchk-v1.26-win32 finds 0 errors.

SecuROM should have 1 error? correct?

Dumped with CloneCD and bin, cue match DIC's so dump is fine but sub's incorrect?

Just tried latest test DIC,

Code: Select all

D:\ReDump_PC\game>DiscImageCreator.exe cd K: "game.bin" 2 /sf /c2 10 /d8 /ns /s 2
AppVersion
        x86, AnsiBuild, 20180825 95905
/sf val is omitted. set [60]
/c2 val2 is omitted. set [0]
CurrentDirectory
        D:\ReDump_PC\game
WorkingPath
         Argument: game.bin
         FullPath: D:\ReDump_PC\game\game.bin
            Drive: D:
        Directory: \ReDump_PC\game\
         Filename: game
        Extension: .bin
StartTime: 2018/08/25(Sat) 08:37:30
Set the drive speed: 0KB/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 reading lead-out -> OK
Checking SubQ adr (Track)  1/ 1
Checking SubRtoW (Track)  1/ 1
Reading DirectoryRecord   90/  90
Checking EXE  865
[INFO] Protection can't be detected. /sf, /ss is ignored.
Set OpCode: 0xd8, SubCode: 8(Raw)
LBA[-00001, 0xffffffff]: Q[410100000000000001740121]
Detected intentional subchannel in LBA -1 => SecuROM Type 4 (a.k.a. NEW)
Checking SubQ ctl (Track)  1/ 1
Creating .scm (LBA)    537/311480

and SecuROM again detected but now dumping freezes at creating scm at 537 & stays there.

Edit: forgot to upload logs: https://www.sendspace.com/file/dqpjhb

[sarami]

Refixed: rereading about SecuROM/Libcrypt http://www.mediafire.com/file/eq80y20l9 … st.7z/file

[antimatter]

Redumped with latest test DIC. Dump completed and hashes match older DIC & CloneCD.

Question: DIC reads the disc as having SecuROM with 1 line in the subIntention.txt but no other program finds any protection. Is DIC reading a false positive on the SecuROM protection?

Logs: https://www.sendspace.com/file/xv2hzb

[sarami]

changed: how to detect SecuROM Type 4 (11 errors version) http://www.mediafire.com/file/eq80y20l9 … st.7z/file

[antimatter]

Worked. Dumped with no false detection of SecuROM.

[sarami]

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

Code: Select all

*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

[user7]

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.

[Jackal]

@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?

[sarami]

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.

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?

Code: Select all

            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
            }

[Jackal]

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.