sarami wrote:
F1ReB4LL wrote:

There should be more logic in determining, if the EAN sector between tracks belongs to the previous or to the next track.

PC Engine Disc is very irregular. I buy it and check it.

Nope, you don't understand smile EAN sector itself is a replacement of one of the usual subchannels sectors. And when you see it between 2 tracks - it can be either the last sector of the previous track or the first sector of the next track, you can only guess smile So you should compare it against the rest of the gaps. For example, you have such EAN sector between 2 tracks and it either belongs to the previous sector (and the gap is 00:01:74) or to the next sector (and the gap is 00:02:00) => you need to compare both cases against the rest of the gaps. If all the other gaps end with 00, then this one is obviously 00:02:00. If only the first gap ends with 00 and all the rest (at least 2) end with 74, then this one is obviously 00:01:74. Hope, you've got my point.
You don't need to buy, I can give you .sub examples.

Thanks all.
WIP3
http://www.mediafire.com/download/u0olo2c51f2qv13/
change: c2 error fix logic.
add: output hash(crc32, md5, sha1) to .dat file

>EAN Sector
Please wait.

178 (edited by pablogm123 2013-10-25 15:21:48)

Could you post the Unicode release of WIP3?

Wishlist:

-An option to override (for certain CDDAs with data pushed to the lead-out, such as the example posted below) the standard offset correction proposed by AccurateRip.

-This text can be removed, no longer applicable.

c2: Check C2 error (Only CD)
        Take twice as long

-To remove the [TRACK x] sections of the generated ccd file, and the CATALOG entrie as well. These sections aren't needed because the gaps and EAN/MCN are already defined by the actual subcode when burning the disc using the RAW DAO 96 mode of CloneCD. And add one CR+LF to separe each section, to read better the generated file.

Original:

https://www.dropbox.com/s/zp80ugnqam4ulib/Original.ccd

My suggestion:

https://www.dropbox.com/s/tzf8nhk9e14k6ay/Modified.ccd


Problems detected:

-An error is reported and the dump contain something unexpected: non-deinterleaved subcode data interleaved with the main channel. Dumping this audio disc.

Command line used: discimagecreator -rall g: 8 Tenbu-CDDA c2

OS
        MajorVersion: 5, MinorVersion: 2, BuildNumber: 3790
AppVersion
        x86, Ansi build
BuildDate
        Oct 25 2013 22:13:58
Input File Name
         path: Tenbu-CDDA
        drive:
          dir:
        fname: Tenbu-CDDA
          ext:
Start -> 2013-10-25(Fri) 15:47:40
Creating bin from 36992 to 36992 (LBA)  36992
Creating img(LBA)  36991/ 36991

Creating bin, cue, ccd(Track)  2/ 2
Failed to search file [F:exec][L:255]
End -> 2013-10-25(Fri) 15:48:46

Screenshot of the dumped files, with the foreign and unexpected data selected

http://img34.imageshack.us/img34/3433/w2hx.png

http://img820.imageshack.us/img820/4461/tbf3.png

-Dumping a game CD (mixed mode CD) the same error is reported, but dumped files don't contain anything weird and hashes are the expected ones:

Command line used: discimagecreator -rall g: 8 Tenbu c2

OS
        MajorVersion: 5, MinorVersion: 2, BuildNumber: 3790
AppVersion
        x86, Ansi build
BuildDate
        Oct 25 2013 22:13:58
Input File Name
         path: Tenbu
        drive:
          dir:
        fname: Tenbu
          ext:
Start -> 2013-10-25(Fri) 15:59:09
Creating bin from 195346 to 195347 (LBA) 195347
Creating img(LBA) 195345/195345

Descrambling data sector of img(LBA)  92039/ 92039
Creating bin, cue, ccd(Track)  9/ 9
Failed to search file [F:exec][L:255]
End -> 2013-10-25(Fri) 16:04:46

P.S.: No dat file is generated.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Input File Name
         path: Tenbu-CDDA
        drive:
          dir:
        fname: Tenbu-CDDA
          ext:

I didn't suppose that drive and dir was null string.
Where is file created? In case of windows7, C:\Users\<username>

180 (edited by pablogm123 2013-10-25 17:19:42)

http://img198.imageshack.us/img198/9616/t5u2.png

http://img811.imageshack.us/img811/1207/i1m4.png

Files are created in the expected folder, c:\temp.


===============================

I have to specify the absolute path of the output file so that discimagecreator will work OK. Previous releases worked OK with relative paths.

http://img843.imageshack.us/img843/9055/5d35.png

http://img96.imageshack.us/img96/9844/kla8.png

http://img809.imageshack.us/img809/32/z55j.png

===============================

I strongly think that the hashes of the single file image and the overread part should be stored into a separated .dat file, so that the .dat can be used to submit the dumps as is it, without cutting/deleting anything.

Instead of:

        <rom name="Test (Track 01).bin" size="22007664" crc="695cbd0e" md5="bde971cfe8f86bc2dcfaf863f759823c" sha1="1bb24ed4874882e3e41db4b1cf8b2130be5493e2"/>
        <rom name="Test (Track 02).bin" size="4812192" crc="712aa00a" md5="97dbe54a83324eb07e2eb58af4366449" sha1="d6b673285b0dfed78afecc6b5ab47d62c5bd4c91"/>
        <rom name="Test (Track 03).bin" size="10591056" crc="14e115db" md5="42777657546f96f6343b075880bc433c" sha1="eab4c74de41d399fad7cf7bca9ea3e0942a6082f"/>
        <rom name="Test (Track 04).bin" size="49396704" crc="30614992" md5="75a725b2dc23d034d69a9609d7c2919e" sha1="757ce8199bd8c0535bc81d97d7c3bb48b9a0c484"/>
        <rom name="Test (Track 05).bin" size="49396704" crc="fa277a55" md5="3ee9af95307a2451152b7ceae7d85baa" sha1="65dbb0f512605389cf832e218db0a029232ce46e"/>
        <rom name="Test (Track 06).bin" size="49396704" crc="2d333c0b" md5="bcf0bdf1d8f378effc9eacb361e5189a" sha1="35fca09480ca880e321359f3622adf54be241a9b"/>
        <rom name="Test (Track 07).bin" size="49396704" crc="76debae8" md5="a5554704c3c5154c3d48dd6d5f556512" sha1="2f285e7c9a04679d597b94b0826a8c8d05019d0c"/>
        <rom name="Test (Track 08).bin" size="49396704" crc="76b54493" md5="fad997de6349cb3e2ea672fb133f18cc" sha1="f2ce6b3b884dd80090b18000c860d4f9b5f7c927"/>
        <rom name="Test (Track 09).bin" size="49396704" crc="c0f1960a" md5="edba053337114eb04735be56a0f4f875" sha1="f19df3b99407c0c3660bfd4f931ff801f4a09c35"/>
        <rom name="Test (Track 10).bin" size="49396704" crc="202d43a9" md5="f313d66551b839e859958fd3fc6c9cc8" sha1="6143253d9001d8072bfd6e33c71301f0604ddc6d"/>
        <rom name="Test (Track 11).bin" size="49396704" crc="1f71f588" md5="27112576eb14eb59e8c1d766758a6235" sha1="59721618cef37f46026bfc1570920ecb1982acaf"/>
        <rom name="Test (Track 12).bin" size="49396704" crc="90ae9a7a" md5="9cafe2a5cf0c2333ec62aed6491bee94" sha1="285203fa563a934a1e2345eb072ff5b14003c7a9"/>
        <rom name="Test (Track 13).bin" size="49396704" crc="a4b672be" md5="2b10bb48487e8e5874bc2e0544e796ff" sha1="6ece379704ba9f79ef53fcd4b888b8e9c67c7a71"/>
        <rom name="Test (Track 14).bin" size="50984304" crc="f2b7e73b" md5="3e43604d7fa0e05c776608c50ec5bdd9" sha1="c1bec3d9f041750cc45def404304870916811450"/>
        <rom name="Test (Track 15).bin" size="49396704" crc="308b608d" md5="b2e499d8f4f3355e8f3d5b66daf27ec5" sha1="c820531b0cea1a503fc38bcd21b7eb846137a24c"/>
        <rom name="Test (Track 16).bin" size="3984288" crc="ef421e96" md5="438e402e804c9922af32ff11f094d52d" sha1="ec25d0165241be025174d4f713b42a79a4a8b335"/>
        <rom name="Test (Track 17).bin" size="2474304" crc="9aa1ee4c" md5="9e7ce788f4072835c942291c9592035a" sha1="619a597408599b5b2cef1a3b2592b960d71037c1"/>
        <rom name="Test (Track 18).bin" size="11470704" crc="8bb16d1f" md5="999a4626bc1bc83866e35509191c79a4" sha1="e020a94db1ca300d621a34ea313d7c16f2291734"/>
        <rom name="Test (Track 19).bin" size="11473056" crc="5ba6d9c1" md5="6ba4a10865ae11f67077133330b267c0" sha1="e80957ad4c9aedbf756e039057041705bac7d196"/>
        <rom name="Test (Track 20).bin" size="11470704" crc="366945ad" md5="66879d8f6f86f1acf43e986b84e010e8" sha1="868ed316e29e030392f05e68be0c2b3061ea4763"/>
        <rom name="Test (Track 21).bin" size="11473056" crc="703e48be" md5="8573560c3179d657386a84fe07b2f0d4" sha1="c76d3d0b26a58754759cc1396fcc33e9281c54ee"/>
        <rom name="Test (Track 22).bin" size="12352704" crc="e9522535" md5="8413bb1634998aa04c363aedfedf3226" sha1="1eff452220065a6b4bcf268d2099bcfe121681e2"/>
        <rom name="Test (Track 23).bin" size="9003456" crc="3f81fdff" md5="39321c80cc9ec171385c97b95c1c2530" sha1="f3965757875dd3c9bce6909792366ed273dad2b1"/>
        <rom name="Test (Track 24).bin" size="16988496" crc="ee4b1788" md5="9d9b26fa1d10b2359730b45162d38331" sha1="73b3e60fdcd51790ed4d15aaa75f28df8fd85876"/>
        <rom name="Test.bin" size="2352" crc="be97ce3f" md5="9e297efc7a522480ef89a4a7f39ce560" sha1="fe1a9e36e57b299b68f2d0f07bbed05c08d460ed"/>
        <rom name="Test.img" size="722449728" crc="1d7594fe" md5="7b6227648094f309c597ebc4a766ecb4" sha1="87b316d0e1ecf58d3a32067c4e504be7b5492243"/>

This:

        <rom name="Test (Track 01).bin" size="22007664" crc="695cbd0e" md5="bde971cfe8f86bc2dcfaf863f759823c" sha1="1bb24ed4874882e3e41db4b1cf8b2130be5493e2"/>
        <rom name="Test (Track 02).bin" size="4812192" crc="712aa00a" md5="97dbe54a83324eb07e2eb58af4366449" sha1="d6b673285b0dfed78afecc6b5ab47d62c5bd4c91"/>
        <rom name="Test (Track 03).bin" size="10591056" crc="14e115db" md5="42777657546f96f6343b075880bc433c" sha1="eab4c74de41d399fad7cf7bca9ea3e0942a6082f"/>
        <rom name="Test (Track 04).bin" size="49396704" crc="30614992" md5="75a725b2dc23d034d69a9609d7c2919e" sha1="757ce8199bd8c0535bc81d97d7c3bb48b9a0c484"/>
        <rom name="Test (Track 05).bin" size="49396704" crc="fa277a55" md5="3ee9af95307a2451152b7ceae7d85baa" sha1="65dbb0f512605389cf832e218db0a029232ce46e"/>
        <rom name="Test (Track 06).bin" size="49396704" crc="2d333c0b" md5="bcf0bdf1d8f378effc9eacb361e5189a" sha1="35fca09480ca880e321359f3622adf54be241a9b"/>
        <rom name="Test (Track 07).bin" size="49396704" crc="76debae8" md5="a5554704c3c5154c3d48dd6d5f556512" sha1="2f285e7c9a04679d597b94b0826a8c8d05019d0c"/>
        <rom name="Test (Track 08).bin" size="49396704" crc="76b54493" md5="fad997de6349cb3e2ea672fb133f18cc" sha1="f2ce6b3b884dd80090b18000c860d4f9b5f7c927"/>
        <rom name="Test (Track 09).bin" size="49396704" crc="c0f1960a" md5="edba053337114eb04735be56a0f4f875" sha1="f19df3b99407c0c3660bfd4f931ff801f4a09c35"/>
        <rom name="Test (Track 10).bin" size="49396704" crc="202d43a9" md5="f313d66551b839e859958fd3fc6c9cc8" sha1="6143253d9001d8072bfd6e33c71301f0604ddc6d"/>
        <rom name="Test (Track 11).bin" size="49396704" crc="1f71f588" md5="27112576eb14eb59e8c1d766758a6235" sha1="59721618cef37f46026bfc1570920ecb1982acaf"/>
        <rom name="Test (Track 12).bin" size="49396704" crc="90ae9a7a" md5="9cafe2a5cf0c2333ec62aed6491bee94" sha1="285203fa563a934a1e2345eb072ff5b14003c7a9"/>
        <rom name="Test (Track 13).bin" size="49396704" crc="a4b672be" md5="2b10bb48487e8e5874bc2e0544e796ff" sha1="6ece379704ba9f79ef53fcd4b888b8e9c67c7a71"/>
        <rom name="Test (Track 14).bin" size="50984304" crc="f2b7e73b" md5="3e43604d7fa0e05c776608c50ec5bdd9" sha1="c1bec3d9f041750cc45def404304870916811450"/>
        <rom name="Test (Track 15).bin" size="49396704" crc="308b608d" md5="b2e499d8f4f3355e8f3d5b66daf27ec5" sha1="c820531b0cea1a503fc38bcd21b7eb846137a24c"/>
        <rom name="Test (Track 16).bin" size="3984288" crc="ef421e96" md5="438e402e804c9922af32ff11f094d52d" sha1="ec25d0165241be025174d4f713b42a79a4a8b335"/>
        <rom name="Test (Track 17).bin" size="2474304" crc="9aa1ee4c" md5="9e7ce788f4072835c942291c9592035a" sha1="619a597408599b5b2cef1a3b2592b960d71037c1"/>
        <rom name="Test (Track 18).bin" size="11470704" crc="8bb16d1f" md5="999a4626bc1bc83866e35509191c79a4" sha1="e020a94db1ca300d621a34ea313d7c16f2291734"/>
        <rom name="Test (Track 19).bin" size="11473056" crc="5ba6d9c1" md5="6ba4a10865ae11f67077133330b267c0" sha1="e80957ad4c9aedbf756e039057041705bac7d196"/>
        <rom name="Test (Track 20).bin" size="11470704" crc="366945ad" md5="66879d8f6f86f1acf43e986b84e010e8" sha1="868ed316e29e030392f05e68be0c2b3061ea4763"/>
        <rom name="Test (Track 21).bin" size="11473056" crc="703e48be" md5="8573560c3179d657386a84fe07b2f0d4" sha1="c76d3d0b26a58754759cc1396fcc33e9281c54ee"/>
        <rom name="Test (Track 22).bin" size="12352704" crc="e9522535" md5="8413bb1634998aa04c363aedfedf3226" sha1="1eff452220065a6b4bcf268d2099bcfe121681e2"/>
        <rom name="Test (Track 23).bin" size="9003456" crc="3f81fdff" md5="39321c80cc9ec171385c97b95c1c2530" sha1="f3965757875dd3c9bce6909792366ed273dad2b1"/>
        <rom name="Test (Track 24).bin" size="16988496" crc="ee4b1788" md5="9d9b26fa1d10b2359730b45162d38331" sha1="73b3e60fdcd51790ed4d15aaa75f28df8fd85876"/>

And this in another .dat file (or dropped at all):

        <rom name="Test.bin" size="2352" crc="be97ce3f" md5="9e297efc7a522480ef89a4a7f39ce560" sha1="fe1a9e36e57b299b68f2d0f07bbed05c08d460ed"/>
        <rom name="Test.img" size="722449728" crc="1d7594fe" md5="7b6227648094f309c597ebc4a766ecb4" sha1="87b316d0e1ecf58d3a32067c4e504be7b5492243"/>
On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

181

Would also like an option to set the number of read retires on error , rather than a hard coded value.

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

182 (edited by sarami 2013-10-26 06:43:42)

WIP4
http://www.mediafire.com/download/u0olo2c51f2qv13/
fix
- usage text
- searching that is created file list (relative path OK)
- output dat file
add
- reread retries times (default 750)
examine
- override offset correction
- remove section of ccd file
- EAN sector (PC Engine)

Much better now dumping game discs!

A little problem detected dumping this audio disc:

http://redump.org/disc/25711/

The generated cue, only the last track is marked with DCP flag:

The very same problem reported (audio files contain non-deinterleaved subcode data) yesterday is present still.

A sample:

https://www.dropbox.com/s/5msvzgm0dyt711f/Test%20%28Track%2024%29.bin
FILE "Test (Track 01).bin" BINARY
  TRACK 01 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 02).bin" BINARY
  TRACK 02 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 03).bin" BINARY
  TRACK 03 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 04).bin" BINARY
  TRACK 04 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 05).bin" BINARY
  TRACK 05 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 06).bin" BINARY
  TRACK 06 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 07).bin" BINARY
  TRACK 07 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 08).bin" BINARY
  TRACK 08 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 09).bin" BINARY
  TRACK 09 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 10).bin" BINARY
  TRACK 10 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 11).bin" BINARY
  TRACK 11 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 12).bin" BINARY
  TRACK 12 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 13).bin" BINARY
  TRACK 13 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 14).bin" BINARY
  TRACK 14 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 15).bin" BINARY
  TRACK 15 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 16).bin" BINARY
  TRACK 16 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 17).bin" BINARY
  TRACK 17 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 18).bin" BINARY
  TRACK 18 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 19).bin" BINARY
  TRACK 19 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 20).bin" BINARY
  TRACK 20 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 21).bin" BINARY
  TRACK 21 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 22).bin" BINARY
  TRACK 22 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 23).bin" BINARY
  TRACK 23 AUDIO
    INDEX 01 00:00:00
FILE "Test (Track 24).bin" BINARY
  TRACK 24 AUDIO
    FLAGS DCP
    INDEX 01 00:00:00
On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

...
Start -> 2013-10-26(Sat) 19:05:38
Creating bin from 273739 to 273739 (LBA) 273739
Creating img(LBA) 273738/273738
Reread times    536, C2ErrorSectorNum    1
Descrambling data sector of img(LBA)  33024/ 33024
Creating bin, cue, ccd(Track) 35/35
...

http://www.sendspace.com/file/9zh956

DIC from 2013-10-06 dumps this disc fine (except 12th track), this one failed to fix the data track (10 errors left, if to check with CDMage), could you look at the logs, please? Seems to be a bug/degradation.

Also could you readd the C2 errors/rereading/fixing information on the screen again? Number of errors, current rereading number, number of errors fixed (per track and total), number of errors left (per track and total), etc. DIC from 2013-10-06 was way more informative.

185

The error checking F1REB4LL suggested still isn't working as described by him.

dic should continue to next sector on c2 error, after full disc is read then errors should be corrected by using c2 file. Error correction should be in this manner...

read c2 file
on sector error reread sector
if no error fix sector in image and mark c2 fixed
else next error sector
continue until all read error fixed or retries exhausted

this way disc does not get damaged further by heat from laser reading same area repeatedly. additionally buffer gets flushed for sure.

also agree, please restore verbose sector error and retry

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

WIP5
http://www.mediafire.com/download/u0olo2c51f2qv13/
[fix]
c2 error correction on offset plus disc.
analyze EAN sector.

Problems dumping from a PX-W4824TU drive, which works fine with another programs:

Failed to read CD for MCN [F:ReadTOCFull][L:1819]
DeviceIoControl with SCSI_PASS_THROUGH_DIRECT command failed [F:ReadCDForSearchi
ngOffset][L:989], GetLastError: 121, The semaphore timeout period has expired.
End -> 2013-10-28(Mon) 14:56:48

After 3/4 retries:

C:\TEMP>discimagecreator -rall h: 24 test.bin c2 2000
OS
        MajorVersion: 5, MinorVersion: 2, BuildNumber: 3790
AppVersion
        x86, Ansi build
BuildDate
        Oct 28 2013 22:40:16
Current dir
          dir: C:\TEMP
Input File Name
         path: test.bin
        drive:
          dir:
        fname: test
          ext: .bin
Start -> 2013-10-28(Mon) 14:59:32
DeviceIoControl with SCSI_PASS_THROUGH_DIRECT command failed [F:ReadTOCText][L:1
873], GetLastError: 121, The semaphore timeout period has expired.
Creating bin from 262446 to 262446 (LBA) 262446
Creating img(LBA)  55033/262445

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

These bugs happen at other plextor drive? 4824TU only?

Yes, with my PX-755SA (connected via JMB363) I cannot reproduce this bug. That drive is actually a 4824TA (ATAPI) installed in a USB 2.0 (NEC chipset, as far I kwow) enclosure.

By the way, the reread of bad sectors works OK, testing by ripping two identical CDs (one undamaged, another one with the metallic layer somewhat damaged) and getting identical hashes.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

I don't have 4824. The cause don't understand at present.

Yes, works good here. But you list a number of sectors with c2 errors ("Reread times  22, ErrSectorNum    7/   7"), while, as I've already said earlier, it's better to show a number of error bytes per sector according to the 294-bytes C2-error part in each sector and to take the good bytes from each rereading, instead of trying to reread the entire sector without errors.

For example, there are 5 C2 errors in the sector #123 (bytes 2, 5, 10, 15 and 20 are corrupted).
1st reread: 4 C2 errors (bytes 5, 10, 15 and 20 are corrupted, byte 2 is good - you replace it in the dump) - 4 errors left.
2nd reread: 8 C2 errors (bytes 2, 3, 4, 5, 6, 15, 20, 25 are corrupted, byte 10 is good - you replace it in the dump) - 3 errors left.
3rd reread: 7 C2 errors (bytes 2, 3, 4, 5, 10, 15 and 20 are corrupted, nothing fixed, nothing to replace) - 3 errors left
4th reread: 10 C2 errors (bytes 1, 2, 3, 4, 5, 6, 7, 8, 9 and 10 are corrupted, bytes 15 and 20 are good - you replace them in the dump) - 1 error left
etc.

192 (edited by pablogm123 2013-10-29 17:51:13)

This is the exact method used by the PlexTools program, the mode 5.

Recover the best bytes (least errors) per sector

When Uncorrectable Errors are found, the damaged area will be read again for a number of times (Retries) at the selected speed. When the errors stay, the bytes with the least errors will be used to re-assemble the original data.

http://wiki.hydrogenaudio.org/index.php … ry_Options

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

pablogm123 wrote:

This is the exact method used by the PlexTools program, the mode 5.

Btw, sarami could also implement 2 different modes: 1 like now, tries to reread the sector until there's no c2 errors and 2 like I've described and like it's described in this wiki, to take the good bytes from the sectors with c2 errors.

And, please, move the rereading number to the commandline, 750 isn't always enough.

194

May have discovered part of others issues.

You should probably add some kind of initialization command before dumping. Sometimes it will just abort with a drive not ready error. I have to open isobuster and hit refresh a couple of times before it works again.

The hashing takes ages too, unoptimized routines there? Will you improve them?

Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

195 (edited by pablogm123 2013-10-30 04:48:53)

@Sarami: I would like that you could implement an option to skip the splitting of the dump and the unscrambling of the data tracks.

So that this tool could act as a cdtoimg-d8 replacement, but with automatic offset correction (or manual when you implement the option to override the automatic offset correction for dumping certain audio discs), subcode dumping and C2 error reporting (and rereads with C2 pointers taking into account).

And to defeat the drive's cache when performing rereads, just use the special FUA command as suggested before. I think that this is the best option to flush the cache if you could implement it.

This post:

http://forum.redump.org/post/45164/#p45164

And this tool to test if your drive supports FUA (you have to insert an audio disc in good condition):

http://download.cdfreaks.com/download/155

If supported you will see:

[+] Plextor flush command: accepted
[+] Plextor flush tests: 20/20

P.S.: I agree, the hashing is somewhat slow compared with another utilities.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

196 (edited by sarami 2013-10-31 13:33:46)

>F1ReB4LL
I examine that fixes per a byte.
By the way, is there an offset for c2 error byte?
If an offset exists, is it different every drive?

>Nexy
>>Sometimes it will just abort with a drive not ready error.
If possible, please tell me the procedure to let it reappear in detail.
>>The hashing takes ages too, unoptimized routines there? Will you improve them
Please tell me the good open-src library.

>pablogm123
>> override the automatic offset correction
It will add at next wip.
>> drive's cache
Tested my drive. My 755sa don't support fua on 0xd8 cmd. I don't know why that is.
Therefore, even if I coded it, I can't test it that its code is correct.

C:\cachex.exe -i m:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on M is  PLEXTOR  DVDR   PX-755A   1.08

[+] Buffer size: 2048 kB, read cache is enabled
[+] Supported read commands: BEh 28h(FUA) D8h
C:\cachex.exe -p -c -r 0xd8 -n 20 m:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on M is  PLEXTOR  DVDR   PX-755A   1.08

[+] Plextor flush command: rejected
[+] Testing cache line size:
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors

197 (edited by pablogm123 2013-10-31 17:26:27)

Certain drivers and filter drivers, like the sptd.sys, can break that. Due to that and to avoid any possible kind of conflicts (like this one officially reported by Microsoft), in my system I don't install any software which installs upperfilters, lowerfilters and virtual drives, only software which uses the standard SPTI layer, nothing more.

Therefore, the FUA support (if ever implemented) to defeat the cache should be optional, via an additional command line parameter.

My other drive, even connected via an USB 2.0 enclosure supports it:

C:\>C:\cachex.exe -p -c -r 0xd8 -n 20 h:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on H is  PLEXTOR  CD-R   PX-W4824A 1.07

[+] Plextor flush command: accepted
[+] Plextor flush tests: 20/20
[+] Testing cache line size:
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors
 1169 kB / 509 sectors

By the way, did you run this program from a elevated cmd.exe process?

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot

Opened command prompt as admin

Commandline: cachex.exe -p -c -r 0xd8 -n 20 p:

    
    Drive on P is  PLEXTOR  CD-R   PX-W5224A 1.04
     
    [+] Plextor flush command: accepted
    [+] Plextor flush tests: 20/20
    [+] Testing cache line size:
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors
     581 kB / 253 sectors

Windows 7 64bit SP1
Daemon Tools Lite v4.46.1.0328
SPTD v1.83

199 (edited by Nexy 2013-11-01 01:51:36)

Sarami, you need to buy some SecuROM protected discs. Dumps are completely inconsistent... BUT this is not an entirely bad thing... apparently you stumbled on a way to dump the twin sectors (this is a good thing) if it can be made consistent it will be great. Both me and MrTikki have run across this now and we discussed it on IRC for awhile today.

On the bad side, all SecuROM dumps are bad an need redone.

F1ReB4LL's idea is to read the disc linear in both directions , 0-end and end-0 to try and capture all twin sectors. But for some reason DIC reads the twin sectors at random.

Also, can you add a switch to save the unsplit scrambled dump from being deleted.

Also, error is "Unable to Access Device" happens randomly, I don't know what causes it. Other tools don't have this problem.

cachex mem test for fun.

Installed Software

Alcohol 120% 2.0.2 Build 3931
CloneCD v5.3.1.4
DVD Decrypter
EAC .99 PreBeta 5
ISOBuster v3.1
Nero Burning Rom v10 (nerocheck.exe removed)
Nero DiscSpeed 11
OptiDriveControl 1.51
UltraISO Premium v9.51

SPTD Layer v1.81

cachex.exe -i -p -c -r 0xd8 -n 20 d:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on D is  PLEXTOR  CD-R   PX-W5224A 1.04

[+] Buffer size: 2048 kB, read cache is enabled
[+] Supported read commands: BEh D8h
[+] Plextor flush command: accepted
[+] Plextor flush tests: 20/20
[+] Testing cache line size:
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors

cachex.exe -i -p -c -r 0xd8 -n 20 e:

CacheExplorer 0.8 - spath@cdfreaks.com

Drive on E is  PLEXTOR  DVDR   PX-760A   1.07

[+] Buffer size: 2048 kB, read cache is enabled
[+] Supported read commands: BEh D8h
[+] Plextor flush command: accepted
[+] Plextor flush tests: 20/20
[+] Testing cache line size:
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
 581 kB / 253 sectors
Plextor PX-760A 1.07 (+30) : Plextor PX-716SA 1.11 (+30) : Plextor PX-W5224A 1.04 (+30) : Plextor PX-W4824 1.07 (+30) : Plextor PX-W4012TA 1.07 (+98) : Plextor PX-W1610TA (+99) : Plextor PX-W1210TA 1.10 (+99) : Lite-On LTR-48246S (+6) : Lite-On LTR-52246S (+6) : Lite-On LH-20A1H LL0DN (+6) : BenQ DW1655 BCIB (+618) : ASUS DRW-2014L1 1.02 (+6) : Yamaha CRW-F1 (+733) : Optiarc SA-7290H5 1H44 (+48) : ASUS BW-16D1HT 3.02 (+6)

200 (edited by pablogm123 2013-11-01 01:47:46)

Good news! SPTD no longer breaks the FUA functionality, as was reported a time ago.

And I agree with the idea of keeping a copy of the scrambled dump, without splitting/unscrambling anything. For example, instead of deleting the original dump renaming it to .scrambled would be a good solution.

================

Regarding SafeDisc there is additionaly a little big problem. Different drives based on different chipsets will give you non-constant results, due to the different error treatment implemented by each different brand of chipsets. One given drive can extract uniformely one SafeDisc disc into scrambled form, but the bad sectors will differ from the ones dumped by another drive.

As sample: the first 15000 sectors of a SafeDisc 2 extracted using CDTool and audio trap disc. While each drive can obtain uniform scrambled reads, they differ from the another drive. Only filling these sectors with an arbitrary pattern (like 0x55) can deliver uniform dumps, but unfortunately this is neither a perfect nor elegant solution.

https://www.dropbox.com/s/rmcnp1l76io1uzc/NEC.7z
https://www.dropbox.com/s/uzkemlu2ks01s6v/Sanyo.7z
https://www.dropbox.com/s/z4v4cj5bwsw4roh/Sanyo-processed.bin
https://www.dropbox.com/s/llwr0wzw5ywudja/NEC-processed.bin

NEC: Pioneer DVR-107D.
Sanyo: Plextor PX-W4824TA.

On semi-vacation. MSF/AMSF to LBA/offset and viceversa calculator: link
To write properly occidental characters contained in japanese titles: screenshot
Spaces must be the fullwidth variant: link / screenshot