DiscImageCreator

[sarami]

Am I doing something obviously wrong here?

Firstly, please use the latest version. https://github.com/saramibreak/DiscImag … g/20230413
And try without /am, plz.

[withered.silence]

Hi, sorry it took me so long, had to deal with other things in the meantime.

Firstly, please use the latest version. [...] And try without /am, plz.

Code: Select all

Microsoft Windows [Version 10.0.22621.1635]
(c) Microsoft Corporation. Alle Rechte vorbehalten.

C:\DiscImageCreator_20230413\Release_ANSI>DiscImageCreator.exe cd m image.bin 24 /c2 /nl
AppVersion
        32 bit, AnsiBuild, 20230413T211754
/c2 val1 was omitted. set [4000]
/c2 val2 was omitted. set [0]
/c2 val3 was omitted. set [0]
CurrentDirectory
        C:\DiscImageCreator_20230413\Release_ANSI
WorkingPath
         Argument: image.bin
         FullPath: C:\DiscImageCreator_20230413\Release_ANSI\image.bin
            Drive: C:
        Directory: \DiscImageCreator_20230413\Release_ANSI\
         Filename: image
        Extension: .bin
StartTime: 2023-05-08T22:49:42+0200
Set the drive speed: 4233KB/sec
DiskSize of [C:\DiscImageCreator_20230413\Release_ANSI]
        Total:   977202307072 bytes
         Used:   936137015296 bytes
        ---------------------------
        Space:    41065291776 bytes
         => There is enough disk space for dumping
[INFO] This drive has 295 offset in the c2. Changed to /s 2.
This drive (DVDR   PX-712A  ) supports [OpCode: 0xd8, SubCode: 0]
This drive (DVDR   PX-712A  ) supports [OpCode: 0xd8, SubCode: 1]
This drive (DVDR   PX-712A  ) supports [OpCode: 0xd8, SubCode: 2]
This drive (DVDR   PX-712A  ) supports [OpCode: 0xd8, SubCode: 8]
Checking reading lead-in -> OK
Checking SubQ adr (Track)  1/ 1
Checking SubRtoW (Track)  1/ 1
Checking Pregap sync, msf, mode (LBA)  -2864
Reading DirectoryRecord   10/  10
Set OpCode: 0xd8, SubCode: 8(Raw)
Checking SubQ ctl (Track)  1/ 1
Creating .scm (LBA)  45038/233627[F:ProcessReadCD][L:288] GetLastError: 121, Das Zeitlimit f³r die Semaphore wurde erreicht.

Please wait for 25000 milliseconds until the device is returned
EndTime: 2023-05-08T22:51:19+0200

C:\DiscImageCreator_20230413\Release_ANSI>

Edit: I just noticed that after this attempt, the drive was stuck with an orange LED and the drive disappeared from the list of devices. Maybe the adapter I'm using is faulty. Hopefully not the drive. I'm not sure.
I tried it with a slower reading speed (6 instead of 24) and it got to 6869 before quitting with the timeout message. Not sure if this gives any hints.

Edit2: I've just ordered a UGREEN branded USB adapter on Amazon that lists the IS611 controller in the description. It should arrive tomorrow and I'll report back if that changes anything.

[MrPepka]

Sorry to write here, but something is wrong with GitHub and I can't submit a new request there
I have a SafeDisc disc that also has unintentional C2 errors. DIC fixes them, but it does so in such a way that the dump is then corrupted. The problem only affects this one disc and interestingly only the LG drive, Plextor is not able to fix C2 errors on this disc. I tried changing the C2 offset to 295 and using the /s 2 command, but it didn't help, and with the /s 0 command, the dumping fails with "Failed to analyze sub-channel" error
The problem concerns sectors from about 14192 to about 17398. It is so strange that Plextor does not see any C2 errors in this area, only LG, and the sectors in which SafeDisc is in the range 809-10199, which is quite close to the problem area
https://mega.nz/file/omQxACwC#gh09rAsih … Hf1BlbkJD0
https://mega.nz/file/5iAX0S6B#92GInFyo7 … _r1nKl7e8k

[sarami]

Plextor is not able to fix C2 errors on this disc.

Does it means that plextor cannot fix errors by 5000 times? If yes, plz specify 10000, 20000, 30000...

The problem only affects this one disc and interestingly only the LG drive

Can you check yourself the different bytes of the two "SHOK_PL_CD1.bin"?

[MrPepka]

I checked it and both dumps in many different sections
I presume there are these broken sectors that are improperly repaired. I would have to somehow force Plextor to fix C2 errors on the same disc to somehow compare it to each other

[withered.silence]

Quick update on my issue, for anyone who happens to stumble upon a similar issue: It was the USB adapter. With the new one, the dump process finished successfully.

[MrPepka]

I did some research, compared the scm files (especially in the sectors where both of these files were incompatible with ECC/EDC) and noticed that the DIC replaces bad sectors with 0x55 both those protected by SafeDisc and those in which SafeDisc is not present and are unintentional C2. Is it possible to somehow tell DIC to replace only those sectors with SafeDisc to 0x55?

[Flashfire42]

Dumping Info:
    Dumping Program: DiscImageCreator 20230413
    Manufacturer: ASUS
    Model: BC-12D2HT
    Firmware: 3.01
    Reported Disc Type: DVD-ROM

Unsure if this is drive damage or a DIC issue or both but I have recently discovered my drive has been producing bad dumps with DIC reporting 0 issues in any of the logs. Its only thanks to the due diligence of other community members I discovered this. May be worth looking into if you have this model drive and to remember to always double dump.

[mictlantecuhtle]

FAO sarami

Recent builds of DIC (tested with 20230309 and 20230413) appear to be outputting incorrect information for multi-session discs. As far as I can see it is no longer correctly analysing the 1st sector and its lead-out, and is effectively treating the entire 1st sector as if it were lead-in for the 2nd. See as follows info from _disc.txt for https://redump.info/disc/102164/:

20220909

Code: Select all

Set OpCode: 0xd8, SubCode: 8(Raw)
 Lead-out length of 1st session: 6750
 Lead-in length of 2nd session: 4500
 Pregap length of 1st track of 2nd session: 150

20230413

Code: Select all

Set OpCode: 0xd8, SubCode: 8(Raw)
 Lead-in length of 2nd session: 208897
 Pregap length of 1st track of 2nd session: 150

Track sizes and hashes remain consistent across builds, it appears to just be the information output that is incorrect.

[sarami]

@mictlantecuhtle
I'm changing the code for dumping the multi-session disc https://github.com/saramibreak/DiscImag … issues/208 . Please wait a few days.

EDIT
Updated test version. https://github.com/saramibreak/DiscImag … r_test.zip
- deleted: /ms and the related code