DiscImageCreator

[sarami]

Thanks. Uploaded the latest test.
added: Skip rereading for safedisc 312 errors
              => The problem is that dic skips rereading if unintentional error is also 312.

[celebi]

Thanks, I'll give it a try.

=> The problem is that dic skips rereading if unintentional error is also 312.

How is the bit number for C2 errors calculated and how high is the chance that an unintentional error is exactly 312? Still improves the reliability compared to previous versions though...

EDIT: Btw, have you looked into mainError.txt from the bad disc I submitted? Assuming all unintentional C2 errors could be fixed, would this be a good or a bad dump? I don't know what those "header generated" messages mean.

[sarami]

dic gets the c2 (294 byte=2352bit). If error exists, a bit stands and coutinue checking this 2352 times.

Code: Select all

how high is the chance that an unintentional error is exactly 312?

Unintentional error changes every times CD is read, but I don't know how high rate (depending on CD).
Anyways, I always recommend dumping at least twice, especially bad condition disc.

I don't know what those "header generated" messages mean.

Sync is 12byte (00 FF ... FF 00)

Code: Select all

========== LBA[002832, 0x00b10]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF 7F FF FF FF  FF FF FF 00 01 B9 A3 61   ...............a
========== LBA[002832, 0x00b10]: Main Channel ==========
       +0 +1 +2 +3 +4 +5 +6 +7  +8 +9 +A +B +C +D +E +F
0000 : 00 FF FF FF FF FF FF FF  FF FF FF 00 01 B9 57 61   ..............Wa

Fixed 0x7f to 0xff.

Assuming all unintentional C2 errors could be fixed, would this be a good or a bad dump?

Check _EdcEcc.txt. I don't know the error of this disc is truly 584 because I don't have this.

[celebi]

Currently DIC is reporting various error counts - waiting for the current dump to complete with a higher re-read count. CloneCD always reports 579 errors for that disc.

So in general, header regenerated messages/sync errors are not harmful as long as I get matching checksums over multiple reads?

Thanks for your support man! (and sorry for asking all those (stupid?) questions )

[celebi]

sarami, I cannot thank you enough!

With the latest test version skipping the 312 bit errors, I finally managed to get several (!) dumps of the previously bad disk matching the dumps I made with CloneCD using a different drive. So finally I have a good dump that will soon enter the redump database. Nice and clean 579 bad sectors, image perfectly working. Thanks again!

I'm very sure that my Plextor W5224 isn't great when it comes to uninententional C2 errors mixed with the Safedisc errors - it detected a few of the Safedisc errors with other bit counts and tried to re-read them too. It should be also noted that the Plextor had issues dumping that disc in CloneCD (random errors there too) while my cheap slimline drive always produced a good dump in CloneCD with the same disc.

I think I should get another Plextor model for safedisc discs in bad condition. If I remember correctly, Nexy reported issues with some Safedisc discs with that drive too - maybe it can only read the Safedisc discs in the first run if they are in perfect condition.

Thanks again!!

[user7]

Just dumped an official Sony "Review Version" CD-R of TOTAL NBA 98 and noticed a warning in terminal:

Code: Select all

[WARNING] Number of sector(s) where subheader(0x10 - 0x17) isn't same: 1

What does this mean? Can I still submit it?

Here are the full logs: https://drive.google.com/open?id=1ZbO6C … AnuPVp5Kb3

[F1ReB4LL]

Just a non-standard sector, nothing special. I'd say "error count: 1", even if it's just a warning.

[sarami]

Uploaded test version.
- added:

Code: Select all

        mds <mdsfile>
                Parse Alchohol 120/52 mds file and output to readable format

Code: Select all

        /am     Scan anti mod string
                        For PlayStation

- fixed: audio/data command (didn't work from 2017-12-10)

[reentrant]

I'm having troubles with data command in latest git version. DIC seems to get stuck at the very beginning.

Is it possible to introduce another reading mode in which I supply disc offset and drive offset and DIC behaves as in cd mode (dumps multiple tracks) and pads missing data with 0s? I have drives with better error correction and I want to compare resulting dumps (track to track basis). Right now it's real PITA to do it due to offset correction. This feature would really be great. Something like data command but with offset correction and splitting tracks...

[sarami]

I'm having troubles with data command in latest git version. DIC seems to get stuck at the very beginning.

I fixed it yesterday.

I want to compare resulting dumps (track to track basis)

Are these useful?
/viewtopic.php?t=8348 … ort-added/
/viewtopic.php?t=8828

EDIT (2/25)
- added: bd command

Code: Select all

        bd <DriveLetter> <Filename> [/f (val)] [/q]
                Dumping a BD from A to Z

I tested some ps3 disc on ASUS BC-12D2HT and the hash matched.
- improved: PC-FX disc (Super PCEngine Fan Deluxe - Special CD-ROM Vol. 1)

EDIT (2/26)
- fixed: Doesn't check reading lead-in/out when uses audio command.

Is HL-DT-ST UH12NS30 still a drive that works

/viewtopic.php?t=10572 … ification/
I don't have this drive, but he reported this drive worked about scrambled and lead-in.

I found the similar drive (ASUS BC-12D2HT).
This can read lead-in (-145 to -1) and read CD by scramble mode.

EDIT (2/27)
- fixed: /am