DiscImageCreator

[sarami]

I have few hundred discs with -153 offset that report C2 error on Plextors.

Is it same reason as Club Saturn (/viewtopic.php?t=14779 … ub-saturn/) ?

Plex and non-plex dumps are different in 1 byte, 0x00 in Plex dump (with error), 0x01 in non-plex dump (no error).

Which result did he adopt?

[reentrant]

Yes, it's the same stuff as in Club Saturn. PX760 and PX716 return the same C2 pointers but the data is different in those 24 bytes between models. I have PX4012 and the issue is there too.

[sarami]

Uploaded http://www.mediafire.com/file/eq80y20l9 … st.7z/file
I've not tested.
- added: search "F0 F0 F0 00 00 00 0F 0F 0F 0F" of C2

[reentrant]

And what would happen when you find it?

[Nexy]

These are not mastering errors that I want to skip, they are perfectly valid sectors. I'm tired of wasting $5/ea on getting a disc resurfaced when there is nothing wrong with the disc. If I let it sit and retry 50000 times it sometimes can read them, it's just a problem with firmware or whatever, and I prefer not to beat the hell out of my drive for something like that.

Now that you've ordered that Ski-Doo racing disc, maybe you can make reading the ring sectors not hang forever too.

:EDIT:

logs https://drive.google.com/open?id=1XUGzR … PpuCIECD9M

[RibShark]

It is possible to read into the lead-out (~13 sectors or so) on the same Blu-Ray Drives that support BEh (READ CD) with the CD-DA flag by using the vendor command to read into the cache. The command is as follows:

Code: Select all

F1 06 xx xx xx xx yy yy yy yy
xx - address to read
yy - length of data to return

Whenever reading a sector of the drive with BEh, that sector and the sectors following it get put into the cache at location 0x00000000. Each sector in the cache is 0xB00 in length. By reading the last sector of the disc, the following lead out sectors will get put into the cache starting at the address 0x00000B00, allowing them to be read with the command. The data returned by the command is formatted as follows (presuming the sector was originally read with the BEh command with CD-DA flag, 001b subchannel bits, and C2 error reporting; I haven't tested with other flags):

Code: Select all

0x000-0x92F - Main Channel (Scrambled)
0x930-0x98F - P-W Subchannel
0x990-0x99F - Q Subchannel
0x9A0-0x9A3 - (unknown)
0x9A4-0xAC9 - C2 Error Bits
0xACA-0xB00 - (unknown)

I am not sure what the unknowns are, but this should be enough to allow for full dumping of any CD with these drives: since they could already read into the lead-in and dump discs with a negative combined offset, this method of reading into the lead-out should allow discs with a positive combined offset to be dumped.

@Sarami: Please could you implement this into DiscImageCreator, it would enable dumping for a lot more people who lack Plextors!

[Nexy]

I did some testing dumping with the ASUS drive, DIC seems to have some slight bugs with it. It dumped a few discs with combined negative offset seemingly fine. I tested it also with the problem disc and it has the same C2 errors. Here's the log for that one too.

https://drive.google.com/open?id=14HV6x … vBdyH1a1pU

[sarami]

It is possible to read into the lead-out (~13 sectors or so) on the same Blu-Ray Drives that support BEh (READ CD) with the CD-DA flag by using the vendor command to read into the cache. The command is as follows:

Which vendor supports this command? Where did you get this info? Is there a specification like ecma, t10.org etc?

And what would happen when you find it?

It doesn't look on these patterns as c2 errors.

These are not mastering errors that I want to skip, they are perfectly valid sectors.

Yes, but your disc is single data track. There is no merit to use DIC.

[RibShark]

It is possible to read into the lead-out (~13 sectors or so) on the same Blu-Ray Drives that support BEh (READ CD) with the CD-DA flag by using the vendor command to read into the cache. The command is as follows:

Which vendor supports this command? Where did you get this info? Is there a specification like ecma, t10.org etc?

I reverse engineered the firmware myself; as I said in my previous post, it is supported by the same LG/ASUS Blu-Ray drives that support BEh scrambled reading. There is no specification.

[sarami]

I tried it.
1. Read LBA 0 of a disc with BEh and cdda flag on ASUS Blu-Ray drive. My drive support BEh scrambled reading.
2. Set and send command {0xf1, 0x06, 0, 0, 0, 0, 0, 0, 0x0b, 00}
3. Returned error [Key-Asc-Ascq: 05-24-00 = ILLEGAL_REQUEST - INVALID FIELD IN CDB]