DiscImageCreator

[sarami]

Still unsure how to make it work. Can you please tell me step by step?

1. Check the 1st LBA when reading error occurs.
2. Check which file has the 1st error LBA by IsoBuster.
3. Rewrite the 2nd line of ReadErrorProtect.txt by its filename.
4. Exec dvd command with /sf flag.

[reentrant]

Hi sarami. I have a safedisc protected disc and I want to report some weird info. Below is a list of C2 error counters from protected range:
240
264
288
312

Each of these vary by 24. I can confirm that this is correct info.

[user7]

DIC seems to have failed dumping a PS3 beta (BD-R) that IsoBuster dumped fine https://drive.google.com/file/d/1X_RHep … sp=sharing

PS: Please publish a new stable release to github :3

[sarami]

Hi sarami. I have a safedisc protected disc and I want to report some weird info. Below is a list of C2 error counters from protected range:
240
264
288
312

Each of these vary by 24. I can confirm that this is correct info.

ok. I trust your info.

DIC seems to have failed dumping a PS3 beta (BD-R)

Weird... My BD-RE disc is no problem.

Code: Select all

========== TOC ==========
      Data Track  1, LBA        0 - 23652351, Length 23652352
                                              Total  23652352
========== DiscStructure ==========
FormatCode: 00, Sendable:  No, Readable: Yes, FormatLength: 4098
========== DiscInformationFromPIC ==========
                DiscInformationIdentifier: DI
                    DiscInformationFormat: 01
             NumberOfDIUnitsInEachDIBlock: 28
                         DiscTypeSpecific: 02
    DIUnitSequenceNumber/ContinuationFlag: 00
           NumberOfBytesInUseInThisDIUnit: 63
                       DiscTypeIdentifier: BDW
                   DiscSize/Class/Version: 02
            DIUnitFormatDependentContents: 2401000001000000000000000002000000194e7e01ec6464464646463c3c3c3c00000000c0427b0a0a4a4a1bc0427b0a0a4a4a1b
 

PS: Please publish a new stable release to github :3

I've asked to F1ReB4LL about VideoNow. Please wait for several days/weeks. You can use test version.

[user7]

DIC is failing to dump a PC cdrom i have https://drive.google.com/file/d/16NfLQi … sp=sharing

This seems to be the issue: [F:GetFilenameToSkipError][L:150] GetLastError: 2, The system cannot find the file specified.

I'm also getting that error on an action replay PS2 disc when trying to dump with:
DiscImageCreator.exe cd g ActionReplay.bin 48 /sf /c2

[enderghast13]

DIC failed to dump a PS2 Action Replay disc that I bought. The disc seems to be in pristine condition. I stopped the dump part way through because no new sectors were being read and it was taking forever for each new sector, even though I used the /sf flag. Logs are attached.

[sarami]

This seems to be the issue: [F:GetFilenameToSkipError][L:150] GetLastError: 2, The system cannot find the file specified.

You lost ReadErrorProtect.txt

DIC failed to dump a PS2 Action Replay disc that I bought.

It seems last 40 sectors have errors.

[reentrant]

I have DVD9 disc and DIC reports following data:

========== SectorLength ==========
    LayerZeroSector: 2010896 (0x1eaf10)
========== PhysicalFormatInformation ==========
           BookVersion: 1
              BookType: DVD-ROM
           MinimumRate: 10.08 Mbps
              DiskSize: 120mm
             LayerType: Layer contains embossed data
             TrackPath: Parallel Track Path
        NumberOfLayers: Double Layer
          TrackDensity: 0.74â╩m/track
         LinearDensity: 0.293â╩m/bit
    StartingDataSector:  196608 (0x30000)
         EndDataSector: 1730300 (0x1a66fc)
    EndLayerZeroSector:       0 (0)
               BCAFlag: No
         MediaSpecific:

========== SectorLength ==========
    LayerZeroSector: 1533693 (0x1766fd)
    LayerAllSector : 3544589 (0x36160d)

Why LayerZeroSector is different in both cases?

[sarami]

Each of these vary by 24. I can confirm that this is correct info.

LayerZeroSector: 1533693 (0x1766fd)

Updated test version.

[F1ReB4LL]

/viewtopic.php?t=16974 … de-gozaru/ -- this was dumped not with recent DIC version (yet), but the logs show the DIC has used a wrong TOC/Sub desync detection logic there. The TOC points at sector 47869, DIC says the track starts at 47870 according to the subs, but that's wrong. The Q-channel of the sector 47869 contains the EAN data, but the P-channel is filled with 0xFF and the next sector's P-channel is filled with 0x00, that means the sector 47869 belongs to the Track 10 according to the the subs as well.