DiscImageCreator (Page 137 of 141)

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

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

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?

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.

@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

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

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

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.

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