3,401

withered.silence wrote:

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.

3,402 (edited by withered.silence 2023-05-08 21:50:39)

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

sarami wrote:

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

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>

hmm

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.

3,403

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

3,404

MrPepka wrote:

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...

MrPepka wrote:

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"?

3,405

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

Post's attachments

2023-05-09 (1).png 1.5 mb, 6 downloads since 2023-05-09 

2023-05-09 (6).png 1.44 mb, 6 downloads since 2023-05-09 

2023-05-09 (7).png 1.49 mb, 6 downloads since 2023-05-09 

2023-05-09 (8).png 1.38 mb, 6 downloads since 2023-05-09 

2023-05-09.png 1.36 mb, 5 downloads since 2023-05-09 

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

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.

3,407

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?

Post's attachments

2023-05-11 (1).png 1020.25 kb, 6 downloads since 2023-05-11 

2023-05-11 (2).png 1022 kb, 6 downloads since 2023-05-11 

2023-05-11 (3).png 1.03 mb, 6 downloads since 2023-05-11 

2023-05-11 (4).png 1.01 mb, 6 downloads since 2023-05-11 

2023-05-11 (5).png 1006.6 kb, 6 downloads since 2023-05-11 

2023-05-11 (6).png 1005.77 kb, 6 downloads since 2023-05-11 

2023-05-11 (7).png 1020.76 kb, 6 downloads since 2023-05-11 

2023-05-11 (8).png 1010.91 kb, 6 downloads since 2023-05-11 

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

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.

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 http://redump.org/disc/102164/:

20220909

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

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.

Post's attachments

dic_old_disc.txt 29.3 kb, 6 downloads since 2023-05-12 

disc_20230413.txt 29.57 kb, 7 downloads since 2023-05-12 

You don't have the permssions to download the attachments of this post.
My drives: ASUS BW-16D1HT, Lite-On SOHD-167T, Plextor PX-W4824TA, Plextor PX-W5224TA (x2), Plextor PX-716AL (x2), Plextor PX-755A, Samsung TS-H352

3,410 (edited by sarami 2023-05-15 02:33:01)

@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

sarami wrote:

@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

@sarami

Thanks for this, unfortunately it doesn't solve the issue I'm having. In order to correctly calculate the session lengths (see comments for http://redump.org/disc/102164/) we need _disc.txt to contain the following as it did previously:

- Lead-out length of 1st session
- Lead-in length of 2nd session
- Pregap length of 1st track of 2nd session

No version after 20220909 (including the test version above) includes this information. As such we are unable to process some multi-session dumps made with recent DIC builds

My drives: ASUS BW-16D1HT, Lite-On SOHD-167T, Plextor PX-W4824TA, Plextor PX-W5224TA (x2), Plextor PX-716AL (x2), Plextor PX-755A, Samsung TS-H352

3,412

"Lead-out length of 1st session" is 6750.
"Lead-in length of 2nd session" is 4500.
"Pregap length of 1st track of 2nd session" is 150.
They are always same.

I've recently encountered an issue where DiscImageCreator is failing to report DVD read errors on multiple discs, while Isobuster and redumper both report read errors. I believe these read errors are resulting from hardware failures from my internal DVD drive, and not disc errors (they are flawless discs and read without errors on other drives). I have experienced these symptoms with builds 20220707, 20230303, and 20230413. This results in 2048-byte blocks containing NULL bytes instead of the correct bytes.

In DIC code, I see that it doesn't directly check ScsiStatus, but rather:

if (swb.SenseData.SenseKey == SCSI_SENSE_NO_SENSE &&
    swb.SenseData.AdditionalSenseCode == SCSI_ADSENSE_NO_SENSE &&
    swb.SenseData.AdditionalSenseCodeQualifier == 0x00) {
    bNoSense = TRUE;
}
...
if (bNoSense) {
    *byScsiStatus = SCSISTAT_GOOD;
}

Is it possible that because DIC doesn't directly check ScsiStatus, that it is missing some bad reads?

Attached are logs for the GOOD and BAD dump from DiscImageCreator for a specific disc with the failing drive (both report no errors in the log).

Post's attachments

redump_102564_DIC_20230413_BAD_logs.zip 19.85 kb, 7 downloads since 2023-05-25 

redump_102564_DIC_20230413_OK_logs.zip 19.85 kb, 7 downloads since 2023-05-25 

You don't have the permssions to download the attachments of this post.
BW-16D1HT | PX-W4824TU | PX-W5224A | PX-760A | PX-712A | Plextor Premium | Pioneer 209DBK | TS-H352C | TS-H353A | Wii

3,414

bikerspade wrote:

Is it possible that because DIC doesn't directly check ScsiStatus, that it is missing some bad reads?

Try this test version in this thread(https://github.com/saramibreak/DiscImag … 1551409465)
And use /ps aa, please.
https://github.com/saramibreak/DiscImag … r_test.zip

3,415

https://github.com/saramibreak/DiscImag … g/20230606
20230606
- added: support BD-RE BH16NS40 1.03
- added: print ProductRevisionLevel and VendorSpecific of the drive in the command-line screen
- added: /v for printing the version & build info
- added: _suppl.dat for .scm, .img, .raw, _SS.bin, _DMI.bin, _PFI.bin, _PIC.bin
- added: support GC/Wii dumping for Plextor
- added: when used /raw, .iso is generated using .raw
- added: support dvd raw dumping for ASUS/LG/Lite-on drives
- added: generate (Track 00)(Session 1), (Track 00)(Session 2), (Track AA)(Session 1), (Track AA)(Session 2), (Track 01)(-LBA), (Track xx)(Pregap)
         when multi-session disc is dumped [xx is the 1st track number of the 2nd session]
- added: /ra for dumping a specified range of sectors
- added: support macOS (It's alpha)
- added: support /rr and /ps when /r is used
- changed: C2 error rereading logic
- changed: generate (Track 0), (Track 1)(-LBA), (Track AA) for all single-session disc (not only audio but data)
- changed: when /ps is used, transfer length is 1
- changed: /ps val accepts from 0x00 to 0xff
- changed: targetname for linux
- fixed: crash when fix C2 errors by the non-plextor drive
- fixed: if ext is not specified and dvd command is used, .iso is added automatically
- fixed: subReadableLog when track is aa
- fixed: scsi error handling when /raw is used
- fixed: Failed to get (Track 01)(-LBA) when the 1st sector is MCN
- deleted: /ms and the related code

3,416 (edited by user7 2023-06-24 23:29:47)

Trying to dump an audio CD on Mac, can someone (who's done it before) tell me where I'm going wrong?

here's my command: audio disk6 clubsaturnusa 72

The example command: audio <DriveLetter> <Filename> <DriveSpeed(0-72)> <StartLBA> <EndLBA+1>

Dunno how to get these: <StartLBA> <EndLBA+1>
are they required?

All my posts and submission data are released into Public Domain / CC0.

3,417

So it turns out that dic and redumper CLI can only be run through certain directories on macOS. (It won't work out of Downloads folder or the Desktop for instance).

What we got to work for redumper is /Users/[username]/bin

All my posts and submission data are released into Public Domain / CC0.

3,418

https://drive.google.com/file/d/1cikxNb … 4O5P6/view - the log is full of "Subchannel & TOC doesn't sync." messages, but no "Sub Indexes" tracks/cue created? Why?

3,419

F1ReB4LL wrote:

the log is full of "Subchannel & TOC doesn't sync." messages, but no "Sub Indexes" tracks/cue created? Why?

I dumped Tengai Makyou: Ziria(http://redump.org/disc/37134/) and "Sub Indexes" are dumped. I'm not sure why Ys Book I & II (USA) are not dumped.

3,420

sarami wrote:
F1ReB4LL wrote:

the log is full of "Subchannel & TOC doesn't sync." messages, but no "Sub Indexes" tracks/cue created? Why?

I dumped Tengai Makyou: Ziria(http://redump.org/disc/37134/) and "Sub Indexes" are dumped. I'm not sure why Ys Book I & II (USA) are not dumped.

Can you add more debug info logging to understand the problem?

3,421

F1ReB4LL wrote:

Can you add more debug info logging to understand the problem?

Added it.
https://www.mediafire.com/file/eq80y20l … st.7z/file

3,422

https://github.com/saramibreak/DiscImag … g/20230909
*2023-09-09
- added: support dumping RVT-R/NR with Plextor drive
- added: reading speed for /c2
- added: subchannel correction when the lead-in is dumped
- added: command-line message to the log file
- changed: transfer length when fixes C2 errors on BW-16D1HT drive with firmware 3.10
- changed: (Track AA).scm filesize

sarami wrote:
F1ReB4LL wrote:

Can you add more debug info logging to understand the problem?

Added it.
https://www.mediafire.com/file/eq80y20l … st.7z/file

Logs for DiscImageCreator_test dump of Ys Book I & II (USA) [TurboDuo]:
https://drive.google.com/file/d/1fkLA6r … sp=sharing

3,424

Kyaerosaber wrote:

Logs for DiscImageCreator_test dump of Ys Book I & II (USA) [TurboDuo]:

"Sub Indexes" tracks/cue are created. I think it's no problem.

3,425 (edited by user7 2023-09-28 01:18:10)

DIC is treating intentional C2 errors (unlicensed) with /sf like regular C2 errors. keeps trying to re-read.

Looks like DUMMY.ZIP is triggering the issue (it's usually BIG.DAT).

All my posts and submission data are released into Public Domain / CC0.