DiscImageCreator

[sarami]

Updated. Disabled the incorrect sub desync.

[jhmiller]

Dump made with the last test version seems to be all ok.

Link to files:
https://mega.nz/#!xIlgzQaT!8q9UJebTaH14 … xikZ7ddnQQ

Code: Select all

DiscImageCreator.exe gd g T-8115N.bin 8 /q

AppVersion
        x86, AnsiBuild, Apr 24 2018 19:24:28
CurrentDirectory
        D:\
WorkingPath
         Argument: T-8115N.bin
         FullPath: D:\T-8115N
            Drive: D:
        Directory: 
         Filename: T-8115N
        Extension: .bin
Start time: 2018-04-24(Tue) 14:53:40
[WARNING] /c2 option isn't set. The result of dumping may be incorrect if c2 error exists.
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 0]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 1]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 2]
LBA[045000, 0x0afc8]: [F:ExecSearchingOffset][L:110]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 04, 00, 00, af, c8, 00, 00, 01, f8, 04, 00
dwBufSize: 2448
Couldn't read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 4]
Checking SubQ adr (Track)  1/ 1
Checking SubRtoW (Track)  1/ 1
Reading DirectoryRecord    3/   3
Set OpCode: 0xbe, SubCode: 1(Raw)
Creating bin from 44999 to 549150 (LBA) 549149
Descrambling img (LBA) 504149/504150
Exec ""D:\EccEdc.exe" check "D:\T-8115N.img""
FILE: D:\T-8115N.img
Checking sectors (LBA) 504149/504149
[NO ERROR] User data vs. ecc/edc match all
Creating bin, cue (Track)  5/ 5
Calculating hash: T-8115N.scm
Calculating hash: T-8115N.img
Calculating hash: T-8115N (Track 3).bin
Calculating hash: T-8115N (Track 4).bin
Calculating hash: T-8115N (Track 5).bin
End time: 2018-04-24(Tue) 15:10:00

[F1ReB4LL]

- added: cue file of GD-ROM image

Out of curiosity, does it check for CATALOG, ISRC, FLAGS, CD-TEXT fields in GD mode? Very unlikely to see them there, but still

[sarami]

It only checks LDA. Do you know the GD-ROM these fields have?

[F1ReB4LL]

No. But how will we know? Checking each .sub manually is a hard work.

[xTMODx]

Not sure if this has been talked about yet, but xTMODx discovered a but in DIC when dumping PSX discs with high error counts. Unless using the /s flag it keeps dumping incorrectly. xTMODx do you still have those logs?

yea finally i came to this, so here are the logs from the dump whit errors...

first dump using PX-712A with this command "dic cd i: dump 8 /c2"

https://www92.zippyshare.com/v/zFm4yhdo/file.html

Code: Select all

<rom name="dump (Track 1).bin" size="222619152" crc="b56470c1" md5="d9216b8bfa6cc8b2e50733ca505e9c45" sha1="4d4ac76965a98d35db2a342d35cdf84781e4ddd2" />
<rom name="dump (Track 2).bin" size="176400" crc="46ec4749" md5="0f06439a8c3b5b45317de8ff57eb5f99" sha1="c9091cc16fce0476bfff2a0375466274030ad3cd" />
<rom name="dump (Track 3).bin" size="176400" crc="04870751" md5="71fd739808de47f41143b9bb637e2515" sha1="4e5564f9495c0e5bccfb4205b7103cd1248367d0" />
<rom name="dump (Track 4).bin" size="455041440" crc="b6e3447d" md5="ced858e5742690a195a12ac2a800d89a" sha1="733ac6091918e79098ed19bab080b7d0a79317cb" />

second dump using PX-712A with this command "dic cd i: dump 8 /c2 /s 2"

https://www8.zippyshare.com/v/giwB05KB/file.html

Code: Select all

<rom name="dump (Track 1).bin" size="579471648" crc="d69cc14b" md5="d14b18d67b80a82048eaf8c5cddb31d7" sha1="23fb0f026864e5c7a2239c30ec675a7804110238" />
<rom name="dump (Track 2).bin" size="26641104" crc="2043a212" md5="19f131c97f5b58982782ade572863bb9" sha1="a80ff9a111217b94fdef968860046b29f778b870" />
<rom name="dump (Track 3).bin" size="39544176" crc="5e7447f2" md5="3983d8c423157f3021a0ca926a5a17e2" sha1="9f295039cc410b63668b2cd8f4ac725a61a72c7a" />
<rom name="dump (Track 4).bin" size="32356464" crc="f070454d" md5="32b46b97fdc55b6ccff99fcc1ed7ff97" sha1="32b149cbbae92462121b5c0e1f86adebc8052563" />

third dump using PX-716AL with this command "dic cd k: dump 8 /c2"

https://www108.zippyshare.com/v/ywfMQIhQ/file.html

Code: Select all

<rom name="dump (Track 1).bin" size="579471648" crc="d69cc14b" md5="d14b18d67b80a82048eaf8c5cddb31d7" sha1="23fb0f026864e5c7a2239c30ec675a7804110238" />
<rom name="dump (Track 2).bin" size="26641104" crc="2043a212" md5="19f131c97f5b58982782ade572863bb9" sha1="a80ff9a111217b94fdef968860046b29f778b870" />
<rom name="dump (Track 3).bin" size="39896976" crc="6d2f46eb" md5="08f4af071109d0f56890c8a27139c3be" sha1="c51cf73f5323d01c58de2205c75400b051e5b075" />
<rom name="dump (Track 4).bin" size="32003664" crc="3f57dea6" md5="6c7f66c1e878b096ec067ffb23e6a160" sha1="e78cdcda6ef8af3374b5d9291a365ab388cc3243" />

the third dump also produced "dump (Subs indexes).*" files so i had the dump twice with same command but different hash

Code: Select all

<rom name="dump (Subs indexes) (Track 1).bin" size="579471648" crc="d69cc14b" md5="d14b18d67b80a82048eaf8c5cddb31d7" sha1="23fb0f026864e5c7a2239c30ec675a7804110238" />
<rom name="dump (Subs indexes) (Track 2).bin" size="26641104" crc="2043a212" md5="19f131c97f5b58982782ade572863bb9" sha1="a80ff9a111217b94fdef968860046b29f778b870" />
<rom name="dump (Subs indexes) (Track 3).bin" size="32815104" crc="e69e6b20" md5="1b1570f5aa75ec53fbfb34690f9c4290" sha1="4fd36c4799361cc339b513fea92628bb63b49a51" />
<rom name="dump (Subs indexes) (Track 4).bin" size="39085536" crc="d2e1901a" md5="774a41621ac2e0c38ddadee295447efe" sha1="2c0282969171164b993639476774f58adbe4292e" />

fourth dump using PX-716AL with this command "dic cd k: dump 8 /c2 /s 2"

https://www106.zippyshare.com/v/WPmWflGS/file.html

Code: Select all

<rom name="dump (Track 1).bin" size="579471648" crc="d69cc14b" md5="d14b18d67b80a82048eaf8c5cddb31d7" sha1="23fb0f026864e5c7a2239c30ec675a7804110238" />
<rom name="dump (Track 2).bin" size="26641104" crc="2043a212" md5="19f131c97f5b58982782ade572863bb9" sha1="a80ff9a111217b94fdef968860046b29f778b870" />
<rom name="dump (Track 3).bin" size="39544176" crc="5e7447f2" md5="3983d8c423157f3021a0ca926a5a17e2" sha1="9f295039cc410b63668b2cd8f4ac725a61a72c7a" />
<rom name="dump (Track 4).bin" size="32356464" crc="f070454d" md5="32b46b97fdc55b6ccff99fcc1ed7ff97" sha1="32b149cbbae92462121b5c0e1f86adebc8052563" />

[sarami]

here are the logs from the dump whit errors...

1st and 3rd dumps are bad because it fails to get the sub-channel.
2nd and 4th dumps seems good but there are some sub-channel errors in 2nd dump and main-channel errors in 4th dump.

Anyway, try the latest release version. And it is also valid to change the reading speed (e.g. 16x 24x).

does it check for CATALOG, ISRC, FLAGS, CD-TEXT fields in GD mode?

Added.

And
added: GC/Wii (support GCC-4240N, 4243N, 4244N(not tested yet), 4246N(not tested yet))

[jhmiller]

DIC crash whit Dreamcast game Silver (Europe - Serial: T-15106D-06).

Link to the DIC files:
https://mega.nz/#!hN8DRTaD!41cLLwhZ7uY6 … y0QbAxNG1g

The first time, I get this error "Directory Record is over 16384" and then DIC crash:

Code: Select all

AppVersion
        x86, AnsiBuild, Apr 27 2018 04:46:16
CurrentDirectory
        D:\Sistemas\Dreamcast\DC Dumper
WorkingPath
         Argument: T-15109D-06.bin
         FullPath: D:\Sistemas\Dreamcast\DC Dumper\T-15109D-06
            Drive: D:
        Directory: \Sistemas\Dreamcast\DC Dumper\
         Filename: T-15109D-06
        Extension: .bin
Start time: 2018-04-28(Sat) 19:29:52
[WARNING] /c2 option isn't set. The result of dumping may be incorrect if c2 error exists.
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 0]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 1]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 2]
LBA[045000, 0x0afc8]: [F:ExecSearchingOffset][L:110]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 04, 00, 00, af, c8, 00, 00, 01, f8, 04, 00
dwBufSize: 2448
Couldn't read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 4]
Checking SubQ adr (Track)  3/ 3
Checking SubRtoW (Track)  3/ 3
Directory Record is over 16384

In the following attempts DIC crahs after the "Checking SubRtoW (Track)  3/ 3":

Code: Select all

AppVersion
        x86, AnsiBuild, Apr 27 2018 04:46:16
CurrentDirectory
        D:\Sistemas\Dreamcast\DC Dumper
WorkingPath
         Argument: T-15109D-06.bin
         FullPath: D:\Sistemas\Dreamcast\DC Dumper\T-15109D-06
            Drive: D:
        Directory: \Sistemas\Dreamcast\DC Dumper\
         Filename: T-15109D-06
        Extension: .bin
Start time: 2018-04-28(Sat) 22:15:01
[WARNING] /c2 option isn't set. The result of dumping may be incorrect if c2 error exists.
LBA[045000, 0x0afc8]: [F:ExecSearchingOffset][L:110]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 03-11-00 = MEDIUM_ERROR - UNRECOVERED READ ERROR
lpCmd: be, 04, 00, 00, af, c8, 00, 00, 01, f8, 00, 00
dwBufSize: 2352
Couldn't read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 0]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 1]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 2]
LBA[045000, 0x0afc8]: [F:ExecSearchingOffset][L:110]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 04, 00, 00, af, c8, 00, 00, 01, f8, 04, 00
dwBufSize: 2448
Couldn't read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 4]
Checking SubQ adr (Track)  3/ 3
Checking SubRtoW (Track)  3/ 3

[sarami]

Changed: directory record size from 16384 to 65535

[jhmiller]

Changed: directory record size from 16384 to 65535

Thanks sarami, but why put a limit?
If another disc reaches that limit, again to change it.
Would not it be better not to limit it?

Edit:
With the test version "Apr 29 2018" continue to fail.

Code: Select all

AppVersion
        x86, AnsiBuild, Apr 29 2018 11:16:14
CurrentDirectory
        D:\Sistemas\Dreamcast\DC Dumper
WorkingPath
         Argument: T-15109D-06.bin
         FullPath: D:\Sistemas\Dreamcast\DC Dumper\T-15109D-06
            Drive: D:
        Directory: \Sistemas\Dreamcast\DC Dumper\
         Filename: T-15109D-06
        Extension: .bin
Start time: 2018-04-29(Sun) 11:43:52
[WARNING] /c2 option isn't set. The result of dumping may be incorrect if c2 error exists.
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 0]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 1]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 2]
LBA[045000, 0x0afc8]: [F:ExecSearchingOffset][L:110]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 04, 00, 00, af, c8, 00, 00, 01, f8, 04, 00
dwBufSize: 2448
Couldn't read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 0, SubCode: 4]
Checking SubQ adr (Track)  3/ 3
Checking SubRtoW (Track)  3/ 3
Directory Record is over 65535

https://mega.nz/#!cBlTxJiZ!2GrC42BycUo9 … SXeuK6ZvBg