DiscImageCreator

[user7]

With LITE ON iHBS112-04 2 drive:

Somewhere around here: Creating iso(LBA) 16833824/23652352
the slowdown occurs, it becomes very slow...

https://drive.google.com/file/d/1aNOKPS … sp=sharing

[sarami]

ReadCapacity is also same as ReadTOC.

Code: Select all

========== ReadCapacity ==========
    Max LBA + 1: 23652352 (0x168e800)

I can't fix this problem now. By the way, how about other BD-R?

[user7]

I can't fix this problem now. By the way, how about other BD-R?

Same way. which size is correct? 33gb or 45gb? i can do more tests if necessary.

[Maddog]

I am sure a good explanation exists, but thought to ask about it.
I just dumped a PS2 CD ROM: /viewtopic.php?t=20293 … to-no-ken/
At first pass, the dump came back with some C2 errors. However, final checksums of the dump with the errors were the same as the existing verified dump. I gave this disc a thorough wash with soap and it fixed the errors, resulting in same checksums again but this time with 0 C2 errors as expected.

I was wondering how a disc with C2 errors can still come back with the correct checksums? Theory says that C2 is uncorrectable error which *should* break the dump and cause wrong checksums, but probably I understand something wrongly here and would love to hear explanation from the experts.

Logs of the dump with C2 errors: https://mega.nz/#!30hAyAyB!eRiljbOBIBnf … pwpe5hgZ1Q
Logs of dump of same disc without C2 errors: https://mega.nz/#!v95wWYhJ!Pp7cAIze9SnG … hERx9f-gF4

[sarami]

I was wondering how a disc with C2 errors can still come back with the correct checksums?

Due to rereading, all sectors with c2 errors turned no error sectors. See _c2Error.txt

which size is correct?

I don't know now.

[user7]

I don't know now.

well i've got over a dozen of these things. is there anyone we can ask? should i buy another drive model to test with?

[sarami]

With LITE ON iHBS112-04 2 drive:

Try to update the firmware https://www.firmwarehq.com/Lite-On/iHBS … files.html

http://www.mediafire.com/file/eq80y20l9 … st.7z/file
- fixed: UDF logs

[user7]

Thank you, I've redumped with updated firmware and new DIC as well as IsoBuster https://drive.google.com/file/d/15PSYB6 … sp=sharing

dic size: 34,139,484,160 bytes
isobuster: 34,138,947,584 bytes (same size as before)

[Resistiv]

DIC is having issues dumping an Enhanced CD. When reaching the second session and after the 20000 msec sleep, the drive seemingly stops, and after a bit the following errors are thrown and then the drive re-spins up:

Code: Select all

Creating .scm (LBA) 302492/307699[F:ProcessReadCD][L:280] GetLastError: 121, The semaphore timeout period has expired.

LBA[302494, 0x49d9e]: [F:ProcessReadCD][L:280]
        Opcode: 0xbe
        ScsiStatus: 0x02 = CHECK_CONDITION
        SenseData Key-Asc-Ascq: 02-04-01 = NOT_READY - LUN_NOT_READY - BECOMING_READY

The LUN_NOT_READY error then throws for every remaining sector of the disc. See attached logs for an example (the dump was cancelled as it would take ages to error through all the sectors): https://mega.nz/#!wE40jCCK!zniqKYJNtHsi … GaZxXt6RlE
Currently using a PX-5224TA through a USB IDE interface, tested on multiple Enhanced CDs to confirm similar results.

[sarami]

DIC is having issues dumping an Enhanced CD

No problem with my 5224TA  (also 4824TA and 755SA). If you have other plextor, try it.