DiscImageCreator

[reentrant]

Ok, thx for the info.

I also read somewhere that changing reading speed could help recover bad sectors. If the cd is spinning at low speed the head might loose position of the track when it tries to read scratched area. When the disc spins faster the head has less chance to loose position of the track because it "hovers above scratch for shorter time".

Maybe this could also be implemented. What do you think?

[sarami]

I agree. Low speed may not be good.
/viewtopic.php?p=39758#p39758

ref.
http://www.ippinkan.com/magazine/magazine_2013-3.htm

取り込みに使うCD-Rドライブは、本来24-48倍速という高速でCD-Rを回転させます。この速度になるとディスクは、「自らのジャイロ効果」で安定します。ジャイロ効果で安定して回転するディスクを支えるための「主軸(ベアリング）」は、高回転時に安定するように「がたつきを大きく（大きめのクリアランス）で設計されます。クリアランスの大きいベアリングを低速で回すと、ディスクの振れが大きくなります。ディスクは高回転で回す方が安定し、読み取りエラーが少なくなる。

I don't know the detail about the hardware, but this article may be reliable.

[F1ReB4LL]

What areas does DIC read for DC? 0...leadout and 45000...leadout? Maybe worth to read the 24941...38689 ringcode area as well? Ringcode area goes as a 2nd session with its own TOC (HD area is a 3rd session).

[sarami]

What areas does DIC read for DC? 0...leadout and 45000...leadout?

dic reads from 45000 to 549150 using gd command.

Maybe worth to read the 24941...38689 ringcode area as well?

Tried. It seems these area has the mode 2 sector.

[F1ReB4LL]

Have you ever tried to test every sector from 0 to 44849 to find out, which sectors are readable? GD-ROM format is badly documented even in the official SEGA docs. I have "GD-ROM Format Basic Specifications Ver. 2.14 " and "GD-ROM Format Specification Details Ver. 1.32" and they don't even mention the lead-in area for the security zone, the doc says sectors 24600...24940 and 38690...39352 are the 'mirror' (unreadable) areas, but that's not correct, the secutity (ring) area has its own lead-in, it goes before the sector 24941, sectors 24825...24940, I think, but can't say for sure where does it exactly start, since it's hard to read the sectors before 24853 on my drives (but 24853 to 24940 are clearly the security area TOC sectors).
The doc mentions the lead-in area for the HD zone, which contains 6675 sectors and goes before the HD zone, so it _should_ be in the sectors 38175...44849, then, but that means it starts in the 2nd unreadable 'mirror' zone, so I don't understand anything

The HD zone starts not at 45000, btw, but at 44850, sectors 44850...44999 contain the 3rd track's pregap.

[sarami]

24400...24602 AMSF[05:30:02] -> lead-out
24603...24793 AMSF[05:32:43] -> unknown subQ (Mirror # 1 ?)
24794...25104 AMSF[05:36:54] -> subQ all zero
25105...38692 AMSF[08:37:67] -> normal subQ (SEGA Logo ?)
38693...38699 AMSF[08:37:74] -> unknown subQ (Mirror # 2 ?)
38700                                        -> unreadable

Have you ever tried to test every sector from 0 to 44849 to find out, which sectors are readable?

0...24399 and 38701...44849 -> test it tonight.

but that's not correct, the secutity (ring) area has its own lead-in, it goes before the sector 24941, sectors 24825...24940, I think, but can't say for sure where does it exactly start, since it's hard to read the sectors before 24853 on my drives (but 24853 to 24940 are clearly the security area TOC sectors).

As far as seeing the log, these area haven't the normal lead-in/TOC subQ. I don't know whether these area is trully TOC or not.

The HD zone starts not at 45000, btw, but at 44850, sectors 44850...44999 contain the 3rd track's pregap.

I agree.

Btw, what drive and tools you use to read HD area?

[F1ReB4LL]

24400...24602 AMSF[05:30:02] -> lead-out
24603...24793 AMSF[05:32:43] -> unknown subQ (Mirror # 1 ?)
24794...25104 AMSF[05:36:54] -> subQ all zero
25105...38692 AMSF[08:37:67] -> normal subQ (SEGA Logo ?)
38693...38699 AMSF[08:37:74] -> unknown subQ (Mirror # 2 ?)
38700                                        -> unreadable

Hmm, very weird results. I've thought 1st leadout and SEGA Logo area addresses are constant. Or, maybe, your drive 'lies' somehow?

Btw, what drive and tools you use to read HD area?

CDTool v1.2 b21
Optiarc AD-7200A w/swapping and PX-760 without swapping (though, PX looses tracking all the time when reading that area).

[sarami]

tested kuon no kizuna (Drive: TS-H353A)

Code: Select all

    0... 1428 AMSF[00:21:03] -> track1 and 2
 1429...24602 AMSF[05:30:00] -> lead-out
24603...24793 AMSF[05:32:43] -> unknown/corrupt subQ (Mirror # 1 ?)
                                main channel is all zero
24794...25104 AMSF[05:36:54] -> subQ all zero
                                main channel is all 0xff
25105...38692 AMSF[08:37:67] -> normal subQ (SEGA Logo ?)
                                RMSF of LBA 25105 is 00:02:14, so 'SEGA Logo?' perhaps starts from LBA 24941.
                                main channel is the mode 2
38693...38699 AMSF[08:37:74] -> unknown/corrupt subQ (Mirror # 2 ?)
38700...44849                -> unreadable (ILLEGAL_REQUEST - ILLEGAL MODE FOR THIS TRACK)

your drive 'lies' somehow?

Maybe so about mirror area, but I think the lead-out and SEGA logo sub is perhaps correct.

[celebi]

Thank you sarami for creating this software!

However, I ran into a few issues. Unfortunately, I currently doesn't have a Plextor drive - the one I ordered was DOA. I don't know when the second one I ordered will arrive.

I found a DH-16A6S in my stack of drives. It is an iHAS 120 clone. It doesn't supports /d8, but is capable of reading in scrabled mode according to DIC.

However, when I try to dump a disc, most discs will fail while dumping - it seems that the drive cannot properly read the last sector and therefore reports a non-existing error.

This also accurs on basically all other drives I own using DIC with the "data" command - the last sector will always fail.

Using the DH-16A6S for some reason always requires me to add the /sf command on *all* discs regardless if they are protected or not, otherwise the ripping process stops at around LBA 45 with a semaphore issue.

UPDATE: I think you can ignore the issue with the DH-16A6S - when I redump a disk that's in the redump DB with CDM, I get wrong checksums while the DS8ACSH dump matches the redump DB. So maybe you could focus on the issues I have with my remaining drives combined with "data" mode?

Example 1, using the DH-16A6S (flashed with iHAS 120 firmware, but also happens with the official one):

Code: Select all

C:\Users\user>C:\Users\user\Desktop\Redump\DiscImageCreator.exe cd d: E:\Redump\Tests\DH-16A6S\DH-16A6S_1.bin 0 /c2
AppVersion
        x86, AnsiBuild, Dec 10 2017 17:54:51
/c2 val1 is omitted. set [4000]
/c2 val2 is omitted. set [0]
E:\Redump\Tests\DH-16A6S\DH-16A6S_1.bin doesn't exist, so create.
CurrentDirectory
        C:\Users\user
WorkingPath
         Argument: E:\Redump\Tests\DH-16A6S\DH-16A6S_1.bin
         FullPath: E:\Redump\Tests\DH-16A6S\DH-16A6S_1.bin
            Drive: E:
        Directory: \Redump\Tests\DH-16A6S\
         Filename: DH-16A6S_1
        Extension: .bin
Start time: 2018-01-07(Sun) 09:15:48
Set the drive speed: 8468KB/sec
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 1, SubCode: 0]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 1, SubCode: 1]
LBA[008380, 0x020bc]: [F:GetLBAForSubChannelOffset][L:58]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-21-00 = ILLEGAL_REQUEST - LOGICAL BLOCK ADDRESS OUT OF RANGE
lpCmd: be, 04, 00, 00, 20, bc, 00, 00, 01, fa, 01, 00
dwBufSize: 2742
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 1, SubCode: 2]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 1, SubCode: 4]
LBA[008380, 0x020bc]: [F:GetLBAForSubChannelOffset][L:58]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-21-00 = ILLEGAL_REQUEST - LOGICAL BLOCK ADDRESS OUT OF RANGE
lpCmd: be, 04, 00, 00, 20, bc, 00, 00, 01, fa, 04, 00
dwBufSize: 2742
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 2, SubCode: 0]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 2, SubCode: 1]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 2, SubCode: 2]
This drive can read a data sector at scrambled mode [OpCode: 0xbe, C2flag: 2, SubCode: 4]
LBA[008380, 0x020bc]: [F:ReadCDForCheckingReadInOut][L:434]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-21-00 = ILLEGAL_REQUEST - LOGICAL BLOCK ADDRESS OUT OF RANGE
lpCmd: be, 04, 00, 00, 20, bc, 00, 00, 01, f8, 00, 00
dwBufSize: 2742
End time: 2018-01-07(Sun) 09:16:10

This disc is an unprotected IBM PC disc. Sector count is 8380 and it rips fine with CDM.

Example 2, same disc, using a Slimtype DS8ACSH (some OEM drive, don't know the real vendor)

Code: Select all

C:\Users\user>C:\Users\user\Desktop\Redump\DiscImageCreator.exe data f: E:\Redump\Tests\DS8ACSH\DS8ACSH.bin 0 0 8380 /c2
AppVersion
        x86, AnsiBuild, Dec 10 2017 17:54:51
/c2 val1 is omitted. set [4000]
/c2 val2 is omitted. set [0]
E:\Redump\Tests\DS8ACSH\DS8ACSH.bin doesn't exist, so create.
CurrentDirectory
        C:\Users\user
WorkingPath
         Argument: E:\Redump\Tests\DS8ACSH\DS8ACSH.bin
         FullPath: E:\Redump\Tests\DS8ACSH\DS8ACSH.bin
            Drive: E:
        Directory: \Redump\Tests\DS8ACSH\
         Filename: DS8ACSH
        Extension: .bin
Start time: 2018-01-07(Sun) 09:21:45
Set the drive speed: 4234KB/sec
LBA[008381, 0x020bd]: [F:GetLBAForSubChannelOffset][L:58]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-21-00 = ILLEGAL_REQUEST - LOGICAL BLOCK ADDRESS OUT OF RANGE
lpCmd: be, 00, 00, 00, 20, bd, 00, 00, 01, fa, 01, 00
dwBufSize: 2742
LBA[008381, 0x020bd]: [F:GetLBAForSubChannelOffset][L:58]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-21-00 = ILLEGAL_REQUEST - LOGICAL BLOCK ADDRESS OUT OF RANGE
lpCmd: be, 00, 00, 00, 20, bd, 00, 00, 01, fa, 04, 00
dwBufSize: 2742
Checking SubQ adr (Track)  1/ 1
Checking SubRtoW (Track)  1/ 1
Reading DirectoryRecord   12/  12

Set OpCode: 0xbe, SubCode: 1(Raw)
Checking SubQ ctl (Track)  1/ 1
LBA[-00001, 0xffffffff]: [F:ProcessReadCD][L:1501]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 05-2c-00 = ILLEGAL_REQUEST - COMMAND SEQUENCE ERROR
LBA[-00001, 0xffffffff] Read error. padding [2352byte]
Creating bin from 0 to 8380 (LBA)   8379
No C2 errors
Exec ""C:\Users\users\Desktop\Redump\EccEdc.exe" check "E:\Redump\Tests\DS8ACSH\DS8ACSH.bin""
FILE: E:\Redump\Tests\DS8ACSH\DS8ACSH.bin
Checking sectors (LBA)   8380/  8380
[ERROR] Number of sector(s) where 2336 byte is all 0x55: 1
Total errors: 1
Total warnings: 0
End time: 2018-01-07(Sun) 09:22:41

This time, it seems that DIC is trying to read one sector that's simply not present - and this is always happening when using DIC with the data command. If I limit the reading range from 0-8380 to 0-8379, then it will still fail reading the last sector.

Is there something that could be done about this or are my drives all incompatible and I have to either use another dumping software (hopefully not) or wait until I could obtain a real plextor drive?

I tried all versions of DIC I could find, but always the same issues.

Please note that while the DS8ACSH is connected using the PC's internal SATA bus, I'm using a SATA/IDE-USB-Converter for the DH-16A6S.

[sarami]

It seems your drive can't read lead-in/out. Such drive can't get the audio sector correctly.

wait until I could obtain a real plextor drive?

I think so.