1,651

Test complete. The new dump with that test version of DIC produces a bin file with the exact same checksum as an older version of DIC, and it doesn't reread all those errors. Thank you very much.

1,652

I get an error when I try to dump the Dreamcast game Nightmare Creatures II (T-9504N USA).

AppVersion
        x86, AnsiBuild, 20181116  95206
CurrentDirectory
        D:\Sistemas\Dreamcast\DC Dumper
WorkingPath
         Argument: T-9504N.bin
         FullPath: D:\Sistemas\Dreamcast\DC Dumper\T-9504N.bin
            Drive: D:
        Directory: \Sistemas\Dreamcast\DC Dumper\
         Filename: T-9504N
        Extension: .bin
StartTime: 2018/11/17(Sat) 11:18:45
Set the drive speed: 1411KB/sec
[WARNING] /c2 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:114]
        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) 89/89
Checking SubRtoW (Track) 89/89
Reading DirectoryRecord   17/  17
Set OpCode: 0xbe, SubCode: 1(Raw)
Creating .scm from 44999 to 549150 (LBA) 378764[F:ProcessReadCD][L:281] GetLastError: 121, Se agot¾
el tiempo de espera del semßforo.

Retry 1/10
LBA[358765, 0x5796d]: [F:ProcessReadCD][L:281]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 03-11-00 = MEDIUM_ERROR - UNRECOVERED READ ERROR
Retry 2/10
Reread 378764 sector
Creating .scm from 44999 to 549150 (LBA) 549149
[L:2103] Internal error. Failed to analyze the subchannel. Track[67]/[89]
EndTime: 2018/11/17(Sat) 11:36:39

Link to the DIC files:
https://mega.nz/#!cV1nAIqL!yWS5LU2r3ghm … 2ajmoGSkb8

I love my XKey, my WODE and my 3Key.
Cerrar MegaUpload sólo es el comienzo de la censura, será el fin de la libertad.
Nada es verdad, todo está permitido.

Today I dumped a PS2 CD game (http://redump.org/disc/32979/ ) and got 3 errors in my .img_EdcEcc.txt file. They are as follows:

[ERROR] Number of sector(s) where user data doesn't match the expected ECC/EDC: 1
    Sector: 127524, 
[ERROR] Number of sector(s) where sync(0x00 - 0x0c) is invalid: 2
    Sector: 127525, 127526, 
Total errors: 3
Total warnings: 0

The command I used was:

DiscImageCreator.exe cd F ISO\DORAJOURNEY\DORAJOURNEY.bin 1 /c2 2000 /q

The hash for the resulting DORAJOURNEY.bin file did not match redump, nor did the cuesheet look the same:

FILE "DORAJOURNEY.bin" BINARY
  TRACK 01 MODE2/2352
    INDEX 01 00:00:00
    INDEX 02 28:20:24

redump:

FILE "Nick Jr. Dora the Explorer - Journey to the Purple Planet (USA).bin" BINARY
  TRACK 01 MODE2/2352
    INDEX 01 00:00:00

When I dump the game in IsoBuster, the resulting file matches redump. I also made another dump a long time ago with ImgBurn using a different drive which also matched redump. I also tried dumping twice in DIC, once at 48x speed and once at 1x. Neither time had any C2 errors and were both done using a PX-716A. Any ideas as to what's going on?

1,654 (edited by sarami 2018-11-18 14:09:04)

jhmiller wrote:

I get an error when I try to dump the Dreamcast game Nightmare Creatures II (T-9504N USA).

Thanks.

     Audio Track 65, LBA 246317 - 247595, Length   1279
     Audio Track 66, LBA 247596 - 249096, Length   1501
      Data Track 67, LBA  45000 - 179294, Length 134295
     Audio Track 68, LBA 179295 - 180120, Length    826
     Audio Track 69, LBA 180121 - 181021, Length    901

An overflow occurred. This was fixed.

20181118 (Windows)
http://www.mediafire.com/file/eq80y20l9 … or_test.7z
20181118 (Linux)
http://www.mediafire.com/file/uw3e03kdk … x_test.tar

enderghast13 wrote:

Today I dumped a PS2 CD game (http://redump.org/disc/32979/ ) and got 3 errors in my .img_EdcEcc.txt file.

Perhaps same problem. http://forum.redump.org/post/63137/#p63137
If you have plextor drives except for PX-716, try it.

1,655

Thanks sarami.
With the new test version I was able to do the dump !!!

I love my XKey, my WODE and my 3Key.
Cerrar MegaUpload sólo es el comienzo de la censura, será el fin de la libertad.
Nada es verdad, todo está permitido.

sarami, I don't have any other Plextors to try it with, but dumping the CD at 8x speed made it match redump.
Thanks you.

Are there any PCI/PCIe IDE/ATA cards that are supported/work with DIC?

I figured out today that the ancient Promise Ultra133 XT2 that I had in my spare parts box is incompatible,[1] but I'm hoping there's a more recent option that will give me at least two extra IDE/ATA ports that I can attach drives to for DIC. All of the i7-compatible motherboards I have only have one IDE/ATA port, and I've got 4-5 format-specific drives with that interface which I'd like to put in my legacy-media-dumping system.

If there's an interest in debugging the Ultra133 problem, I'm happy to help out with that too, but I assume that supporting 15+-year-old cards is not a priority smile.

[1] I assume because its driver makes attached drives look like SCSI devices instead of ATAPI.

1,658

Cut Into Fourteen Pieces wrote:

Are there any PCI/PCIe IDE/ATA cards that are supported/work with DIC?

If drives are recognized with your PC, DIC will work.

sarami wrote:
Cut Into Fourteen Pieces wrote:

Are there any PCI/PCIe IDE/ATA cards that are supported/work with DIC?

If drives are recognized with your PC, DIC will work.

OK, thank you. I have a bunch of drives that work when attached directly to an IDE port on a motherboard, or via a USB adapter, but fail to read discs via DIC when attached to one of the two ports on the PCI card. They can be used in Windows, just not to dump images via DIC.

I am confident that the PCI card works, because I just used it to dump a disc image of an original Xbox dev kit's hard drive.

I've tried with the following drives just now so that I'd have raw output for you:

- PX-712A
- GDR-8163B
- TS-H352C
- Samsung SM308 (random DVD drive I had laying around which I've gotten good dumps from using other pre-DIC tools)

Here is the output when dumping a standard retail PS2 disc when the first two are connected directly to the motherboard:

C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd x test-px712a-motherboard.iso 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-px712a-motherboard.iso
         FullPath: C:\DiscImageCreator\Release_ANSI\test-px712a-motherboard.iso
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-px712a-motherboard
        Extension: .iso
StartTime: 2018/11/22(Thu) 13:47:34
LBA[000000, 0000000]: [F:ReadEeprom][L:889]
        Opcode: 0xf1
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 06-28-00 = UNIT_ATTENTION - NOT READY TO READY CHANGE, MEDIUM MAY HAVE CHANGED
Please wait for 40000 milliseconds until the device is returned
Set the drive speed: 11080KB/sec
Reading DirectoryRecord    3/   3
Creating iso(LBA)  2136560/ 2136560
Calculating hash: test-px712a-motherboard.iso [4375674880/4375674880]
Calculating hash: PFI.bin [2048/2048]
Calculating hash: DMI.bin [2048/2048]
EndTime: 2018/11/22(Thu) 13:55:26
C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd d test-gdr-8163b-motherboard.iso 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-gdr-8163b-motherboard.iso
         FullPath: C:\DiscImageCreator\Release_ANSI\test-gdr-8163b-motherboard.iso
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-gdr-8163b-motherboard
        Extension: .iso
StartTime: 2018/11/22(Thu) 13:56:40
Set the drive speed: 11080KB/sec
Reading DirectoryRecord    3/   3
Creating iso(LBA)  2136560/ 2136560
Calculating hash: test-gdr-8163b-motherboard.iso [4375674880/4375674880]
Calculating hash: PFI.bin [2048/2048]
Calculating hash: DMI.bin [2048/2048]
EndTime: 2018/11/22(Thu) 14:03:08

Here is the output when I try to dump the same disc with the drives connected to the Ultra133 PCI card instead:

C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd s test-sm308.iso 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-sm308.iso
         FullPath: C:\DiscImageCreator\Release_ANSI\test-sm308.iso
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-sm308
        Extension: .iso
StartTime: 2018/11/22(Thu) 13:23:44
LBA[000000, 0000000]: [F:SetDiscSpeed][L:752]
        Opcode: 0xbb
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-20-00 = ILLEGAL_REQUEST - INVALID COMMAND OPERATION CODE
LBA[000000, 0000000]: [F:ReadDiscStructure][L:816]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
EndTime: 2018/11/22(Thu) 13:23:44
C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd d test-px712a.iso 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-px712a.iso
         FullPath: C:\DiscImageCreator\Release_ANSI\test-px712a.iso
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-px712a
        Extension: .iso
StartTime: 2018/11/22(Thu) 13:22:11
Set the drive speed: 11080KB/sec
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 69 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 6d failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 52 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 61 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 41 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 37 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 2e failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed

[ DiscImageCreator.exe crashes - popup in Windows with error reporting option ]
C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd e test-GDR-8163B.txt 8

AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-GDR-8163B.txt
         FullPath: C:\DiscImageCreator\Release_ANSI\test-GDR-8163B.txt
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-GDR-8163B
        Extension: .txt
StartTime: 2018/11/22(Thu) 13:31:52
Set the drive speed: 11080KB/sec
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 69 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 6d failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 52 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 61 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 41 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 52 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 36 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed

[ DiscImageCreator.exe crashes - popup in Windows with error reporting option ]
C:\DiscImageCreator\Release_ANSI>DiscImageCreator.exe dvd d test-TS-H352C.txt 8
AppVersion
        x86, AnsiBuild, 20181022 162920
CurrentDirectory
        C:\DiscImageCreator\Release_ANSI
WorkingPath
         Argument: test-TS-H352C.txt
         FullPath: C:\DiscImageCreator\Release_ANSI\test-TS-H352C.txt
            Drive: C:
        Directory: \DiscImageCreator\Release_ANSI\
         Filename: test-TS-H352C
        Extension: .txt
StartTime: 2018/11/22(Thu) 13:29:33
Set the drive speed: 11080KB/sec
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 69 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 6d failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 43 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 52 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 61 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 41 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 74 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 2d failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 32 failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed
LBA[000000, 0000000]: [F:ReadDiscStructure][L:970]
        Opcode: 0xad
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
FormatCode: 5c failed

[ DiscImageCreator.exe crashes - popup in Windows with error reporting option ]

If this is something you're interested in troubleshooting, I'm happy to buy you one of these cards if it will help, or send you money to buy one yourself. They're old, but there are tons of them out there on eBay, etc.

If there's an equivalent, more modern card that you know works and is < US$100, I'm also happy to just buy it. My goal here is to be able to quickly dump discs without having to power down and swap cables. I try to avoid IDE cable swapping if at all possible, because it's so easy to bend or break the pins.

My fallback plan is to buy a USB => IDE adapter for each of the drives and connect them to a hub inside the tower.

1,660

Cut Into Fourteen Pieces wrote:

Here is the output when I try to dump the same disc with the drives connected to the Ultra133 PCI card instead:

FormatCode: 43, 69, 6d etc... are not defined. It seems the Ultra133 PCI card doesn't support ReadDiscStructure command. Please try to update the driver of PCI card if not latest.

sarami wrote:
Cut Into Fourteen Pieces wrote:

Here is the output when I try to dump the same disc with the drives connected to the Ultra133 PCI card instead:

FormatCode: 43, 69, 6d etc... are not defined. It seems the Ultra133 PCI card doesn't support ReadDiscStructure command. Please try to update the driver of PCI card if not latest.

I'm using the latest driver, and the latest BIOS sad.

I'm reasonably sure this card isn't going to work, based on what you've said.

It sounds like I'm the first person in this specific situation (needing to add more IDE/ATA ports to an existing system for use with DIC), so I'm going to order these and see if either of them work any better:

https://www.amazon.com/IO-Crest-SI-PEX4 … 00BI4Z4H6/

https://www.amazon.com/Port-PCI-Control … 000P9VHOO/

I'll report back in a week or two, once I've had time to test.

Good news: both of those cards (the StarTech 2 Port PCI IDE Controller Adapter Card, and the IOCrest PCIe SI-PEX40059) both work for me with DIC under Windows 10. The StarTech card is a little hard for me to recommend, however, because it blocks the use of the next slot down on the motherboard. If one doesn't need that slot, or the PCI slot is the last slot, that wouldn't be a problem. The IDE connector will press against the next card down when a cable is connected to the IOCrest card, but at least it doesn't actually block the slot. I guess if one is handy with a soldering iron, they could also swap out the downward-facing IDE connectors on either card for ones that face outward.

1,663

sarami, do you think you could get your CSS tool to be able to detect RCE protection? Currently that CSS tool outputs all DVD-Video information needed except for RCE protection info. It would be great if we could get DIC/CSS to detect it without the need to use DVDDecrypter.

1,664

ajshell1 wrote:

do you think you could get your CSS tool to be able to detect RCE protection?

Did you see this? http://forum.redump.org/post/64390/#p64390 https://www.dvdtalk.com/rce.html
If you have RCE discs, please check by same step. And if you have other protected discs (Sony ARccOS, UOP, Disney X-Project DRM, Cinavia Protection etc.), please teach me the detail.

1,665 (edited by user7 2018-12-20 07:14:47)

http://redump.org/disc/58106/

I dumped this twice with DICUI and got the same hashes, then dumped again with ISO Buster and got a different hash. Let me know if I need to run further tests, this is going up for sale on Sunday and I won't have it shortly after.

Here's the xDelta patch, i think i made this right https://drive.google.com/file/d/1RmtQg8 … sp=sharing

1,666

user7 wrote:

Let me know if I need to run further tests

Please try other tools.

1,667

DICUI matches IMGBURN

1,668

Test version
20181223 (Windows)
http://www.mediafire.com/file/eq80y20l9 … or_test.7z
20181223 (Linux)
http://www.mediafire.com/file/uw3e03kdk … x_test.tar

added: /vn option

        /vn     Search specific bytes
                        For VideoNow

fixed: CDTEXT

I have a GD that seem to be impossible to dump. Promo version of Tom Clancy's Rainbow Six incl. Eagle Watch Missions.

Disc is like new.

This is what my 708 gives me: https://mega.nz/#!rgJEFYpK!_ipAJ19QpHFp … FHYzjGi3xk

Other drives give similar results.

1,670

FatArnold wrote:

I have a GD that seem to be impossible to dump.

It seems c2 errors exist in your disc.

1,671 (edited by Jackal 2018-12-24 22:03:26)

Here's a type of SecuROM that seems to be different from all previous types:

http://redump.org/disc/45559/

http://redump.org/disc/58232/

The things that are unclear to me:

- For Diablo II: Lord of Destruction, SecuROM sector 157 was not included in the SubIntention. What was causing this?

- Could the write offset of +576 be wrong? it's -12 plus 588 samples (1 sector). I've never seen this offset before.

- Can you plz double check if the SecuROM data is correct and if there are really 99 "modified" sectors for this SecuROM version?

Here are the log files for Diablo, and also an unmodified CloneCD.sub from another drive:
https://www50.zippyshare.com/v/jUraqxWb/file.html
https://www50.zippyshare.com/v/dVsXalzo/file.html

Thx for your help smile

1,672

Uploaded. http://www.mediafire.com/file/eq80y20l9 … st.7z/file But I haven't tested yet because I don't have same type of SecuROM.

Jackal wrote:

- Could the write offset of +576 be wrong? it's -12 plus 588 samples (1 sector). I've never seen this offset before.

Colin McRae Rally 2.0 http://redump.org/disc/31587/
This disc has also same issue.
1. OpCode[0xd8]: SubCode[0] shows -59.
2. OpCode[0xd8]: SubCode[2] shows -647.
3. OpCode[0xd8]: SubCode[8] shows -647.

I think -647 is correct.

Post's attachments

colin_disc.txt 70.45 kb, 1 downloads since 2018-12-25 

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

1,673

sarami wrote:
FatArnold wrote:

Seems to be a bug with the Linux DIC. No dat is created.

Windows build uses xmllite, but this library doesn't support other OS, so linux build hasn't supported to output the xml doc yet, not bug.

20181229 (Linux)
http://www.mediafire.com/file/uw3e03kdk … x_test.tar
added: output dat (tinyxml2 is used.)

1,674 (edited by Jackal 2018-12-31 16:43:10)

sarami wrote:

Uploaded. http://www.mediafire.com/file/eq80y20l9 … st.7z/file But I haven't tested yet because I don't have same type of SecuROM.

Jackal wrote:

- Could the write offset of +576 be wrong? it's -12 plus 588 samples (1 sector). I've never seen this offset before.

Colin McRae Rally 2.0 http://redump.org/disc/31587/
This disc has also same issue.
1. OpCode[0xd8]: SubCode[0] shows -59.
2. OpCode[0xd8]: SubCode[2] shows -647.
3. OpCode[0xd8]: SubCode[8] shows -647.

I think -647 is correct.

So is it safe to assume that all discs in the database with -59 offset are actually -647, and +576 are actually -12?
Is it possible that other offsets are also affected?
And securom data remains the same? (the test version produces the same data)

And what about audio tracks that are dumped with -59 offset? (I'm not sure if there are any)

1,675

Jackal wrote:

So is it safe to assume that all discs in the database with -59 offset are actually -647, and +576 are actually -12?
Is it possible that other offsets are also affected?

I'm not sure about it, but many sony dadc discs have -647. At least, I hope all 99 modified SecuROM discs are dumped again to get _disc.txt.

Jackal wrote:

And securom data remains the same? (the test version produces the same data)

SubCode[0] dumps only main-channel. dic only uses this to output offsets in _disc.txt. No problem about sub-channel.
Or does this question mean that SecuROM sector 157 haven't fixed yet?


Jackal wrote:

And what about audio tracks that are dumped with -59 offset? (I'm not sure if there are any)

Perhaps main-channel is shifted for 1 sector if discs are dumped by old method (isobuster+eac, perfectrip+eac)