1,751

LoStraniero91 wrote:

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.

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.

1,753 (edited by user7 2019-03-10 20:53:01)

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

1,754

reentrant wrote:

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.

user7 wrote:

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

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

========== 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
 
user7 wrote:

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.

1,755 (edited by user7 2019-03-20 16:23:47)

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

1,756 (edited by enderghast13 2019-03-20 21:33:50)

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.

Post's attachments

Ultimate Codes for use with Smac.7z 1.4 mb, 2 downloads since 2019-03-20 

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

1,757 (edited by sarami 2019-03-21 03:15:15)

user7 wrote:

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

You lost ReadErrorProtect.txt

enderghast13 wrote:

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

It seems last 40 sectors have errors.

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?

1,759

reentrant wrote:

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

reentrant wrote:

LayerZeroSector: 1533693 (0x1766fd)

Updated test version.