Re: DiscImageCreator
Posted: Mon Mar 27, 2017 2:50 pm
The error of the last two sections is a "common" issue with dcdumper.
You have to delete the previous section (47) and, normally, in the next try, the 2 last sections (48 and 49) are dumped.
Anyway I recommend you to change the options a bit in the dcdumper.
In my case it is better to use fewer sections of larger size and fewer passes.
I have used: -i56018 -p4
This make 9 sections of aprox 125 MB and in 4 passes.
But that is another subject.
Today I tried again with DIC, and the errors come again.
It starts to dump and after a while it stops showing:
"SenseData Key-Asc-Ascq: 05-64-00 = ILLEGAL_REQUEST - ILLEGAL MODE FOR THIS TRACK"
I don't know why errors occurs using DIC and the H353A.
But with dcdumper can read to the end, using the same discs in the same unit.
I've dumped the same disc in the SHD162C using dcdumper and the result is exact the same that in the H353A.
If I can help you in any way, tell me.
If you can understand my English
You have to delete the previous section (47) and, normally, in the next try, the 2 last sections (48 and 49) are dumped.
Anyway I recommend you to change the options a bit in the dcdumper.
In my case it is better to use fewer sections of larger size and fewer passes.
I have used: -i56018 -p4
This make 9 sections of aprox 125 MB and in 4 passes.
But that is another subject.
Today I tried again with DIC, and the errors come again.
It starts to dump and after a while it stops showing:
"SenseData Key-Asc-Ascq: 05-64-00 = ILLEGAL_REQUEST - ILLEGAL MODE FOR THIS TRACK"
Code: Select all
D:\DIC\DiscImageCreator.exe gd t SANGOVI.bin 8 /c2 /s0
OS
Windows 7 Professional Service Pack 1 64bit
AppVersion
x86, AnsiBuild, Mar 14 2017 22:07:12
/c2 val1 is omitted. set [1024]
/c2 val2 is omitted. set [4096]
/c2 val3 is omitted. set [4]
/s val is omitted. set [1]
CurrentDirectory
D:\DIC
WorkingPath
Argument: SANGOVI.bin
FullPath: D:\DIC\SANGOVI
Drive: D:
Directory: \DIC\
Filename: SANGOVI
Extension: .bin
Start time: 2017-03-27(Mon) 21:13:27
Allocating packed memory for C2 errors: 8192
LBA[000000, 0000000], [F:ExecCheckingByteOrder][L:1269] OperationCode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 00, 00, 00, 00, 00, 00, 00, 01, fa, 01, 00
dwBufSize: 2742
This drive doesn't support [command: 0xbe, c2flag: 0x1, subch: 0x1]
LBA[000000, 0000000], [F:ExecCheckingByteOrder][L:1269] OperationCode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 00, 00, 00, 00, 00, 00, 00, 01, fa, 02, 00
dwBufSize: 2742
This drive doesn't support [command: 0xbe, c2flag: 0x1, subch: 0x2]
LBA[000000, 0000000], [F:ExecCheckingByteOrder][L:1269] OperationCode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 00, 00, 00, 00, 00, 00, 00, 01, fa, 04, 00
dwBufSize: 2742
This drive doesn't support [command: 0xbe, c2flag: 0x1, subch: 0x4]
LBA[000000, 0000000], [F:ExecCheckingByteOrder][L:1269] OperationCode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 00, 00, 00, 00, 00, 00, 00, 01, fc, 01, 00
dwBufSize: 2742
This drive doesn't support [command: 0xbe, c2flag: 0x2, subch: 0x1]
LBA[000000, 0000000], [F:ExecCheckingByteOrder][L:1269] OperationCode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 00, 00, 00, 00, 00, 00, 00, 01, fc, 02, 00
dwBufSize: 2742
This drive doesn't support [command: 0xbe, c2flag: 0x2, subch: 0x2]
LBA[000000, 0000000], [F:ExecCheckingByteOrder][L:1269] OperationCode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB
lpCmd: be, 00, 00, 00, 00, 00, 00, 00, 01, fc, 04, 00
dwBufSize: 2742
This drive doesn't support [command: 0xbe, c2flag: 0x2, subch: 0x4]
This drive can read a data sector at scrambled mode [subch: 00]
This drive can read a data sector at scrambled mode [subch: 0x1]
This drive can read a data sector at scrambled mode [subch: 0x2]
LBA[045000, 0x0afc8], [F:ExecSearchingOffset][L:64] OperationCode: 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 [subch: 0x4]
Checking SubQ adr (Track) 1/ 1
Checking SubRtoW (Track) 1/ 1
Set read command: 0xbe, subcode reading mode: Raw
LBA[045049, 0x0aff9], [F:ProcessReadCD][L:1469] OperationCode: 0xbe
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-64-00 = ILLEGAL_REQUEST - ILLEGAL MODE FOR THIS TRACK
End time: 2017-03-27(Mon) 21:13:35But with dcdumper can read to the end, using the same discs in the same unit.
I've dumped the same disc in the SHD162C using dcdumper and the result is exact the same that in the H353A.
If I can help you in any way, tell me.
If you can understand my English
