Search options (Page 38 of 56)

tested kuon no kizuna (Drive: TS-H353A)

    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)

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

dic reads from 45000 to 549150 using gd command.

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

It's possible.
https://github.com/saramibreak/DiscImag … dforCD.cpp
Change the Line 1640:

throw FALSE;

to

break;

or comment out 'throw FALSE;'

But is it really uncorrectable errors? Please try the default times (4000).

Yes. It's checked by the func 'ContainsC2Error' of the Line 1630.

My DL disc

             TrackPath: Opposite Track Path
        NumberOfLayers: Double Layer
          TrackDensity: 0.74μm/track
         LinearDensity: 0.293μm/bit
    StartingDataSector:  196608 (0x30000)
         EndDataSector: 15995449 (0xf41239)
    EndLayerZeroSector: 2224591 (0x21f1cf)

Your log

                 TrackPath: Parallel Track Path
            NumberOfLayers: Double Layer
              TrackDensity: 0.74μm/track
             LinearDensity: 0.293μm/bit
        StartingDataSector:   196608 (0x30000)
             EndDataSector:  1702255 (0x19f96f)
        EndLayerZeroSector:        0 (0)

I had thought all of the DL disc is 'Opposite Track Path', but this DL disc has 'Parallel Track Path'. I understood DIC can't dump 'PTP' and 'DL' disc. I don't know how to fix this now.

Some changed. http://www.mediafire.com/file/eq80y20l9 … or_test.7z
I have PX-755SA too, but my 755 can't get the scrambled sector when dumps the HDA of GD-ROM using the audio trap disc, so I can't test. (In the case of my PC, if doesn't use the audio trap disc, dic can dump the HDA till 79:59:74. I don't know why.)

And I changed VS2015 to VS2017. Please download and install the redistributable package. https://aka.ms/vs/15/release/VC_redist.x86.exe

All sectors.

It's really weird...

c2 error offset is perhaps same as main channel offset. To confirm this, it needs to test by the large offset disc (over 588 samples) and its disc has c2 error.

*2017-12-10
- added: Reading path table & directory record of GDROM HD Area
- added: Reading joliet file system (if iso9600 didn't read)
- added: Writing the hash of the toc vs. subs desync disc and the scrambled main channel (.scm file)
- added: Argument of /f option (to delete the drive cache per specific value)
- changed: Rename _sub.txt to _subReadable.txt
- fixed: Dumping of GDROM (didn't work from 2017-08-18)
- fixed: 1st sector of the pregap sector has invalid index of the subchannel
- rewrote: Recovering C2 error (only plextor. not support no-plextor drive now)
            => I definitely understood the plextor drive has -1 sector offset about C2 error.

use '/c2'

Because these programs dump the data sector as data sector (0xbe mode), but dic dumps the data sector as audio sector (0xd8 mode), then audio sector is descrambled to data sector.

It seems your drive doesn't support reading lead-out.

This is bug. scrambled dumping isn't supported too. Please use the recommended drive.

There are 3 file systems in disc (iso9660, Romeo ?, Joliet).
Ref: https://www.isobuster.com/help/file_systems

I confirmed there are the root directory record in 69 sector of joliet, but there aren't it in iso9660... originally, there should be it in 24 sector but this sector has all zero byte.
dic reads only iso9660 now. So if it can't read iso9660 properly, it should read joliet. Please wait until fix it.

I'll divide the toc and sub indexes.

Thx.
_volDesc.txt

                                   :
              Length of Directory Record: 34
        Extended Attribute Record Length: 0
                      Location of Extent: 335260
                             Data Length: 2048
                 Recording Date and Time: 2002-10-31 16:31:47 -05:00
                              File Flags: 2 (Visible, Directory, Disassociated, File has't record format, Owner/Group ID has't, Final Directory Record)
                          File Unit Size: 0
                                    :

========== LBA[000020, 0x00014]: Path Table Record ==========
         Length of Directory Identifier: 1
    Length of Extended Attribute Record: 0
                     Position of Extent: 335260
              Number of Upper Directory: 1
                   Directory Identifier: 
                                 :

This disc points 335260 sector as the position of root directory, but this sector is all zero byte, so dic can't read the directory record and can't detect the protect.
I think the correct position of root dir is 21 or 22 or 23 or 24.

Can Isobuster read the directory correctly?