uploaded 20150812 test ver.
do you know which drives works best with newer protections?
I don't know because I don't have enough protect disc to test and I recommend a drive only plextor made in Shinano Kenshi.
You are not logged in. Please login or register.
Redump Forum → Posts by sarami
uploaded 20150812 test ver.
do you know which drives works best with newer protections?
I don't know because I don't have enough protect disc to test and I recommend a drive only plextor made in Shinano Kenshi.
iR0b0t wrote:CodeLock http://redump.org/discs/quicksearch/cod … ction/only
and other discs which use intentional c2 errors in combination with any other protections.
You could set this custom command in priority to EccEdc, which is "/rc" i think.
I don't have these protect disc. plz wait.
I bought this. http://redump.org/disc/31708/
and I found it this protect has "icd*" text in IMAGE_SECTION_HEADER of the EXE file. (by PoxyLok http://gf.wiretarget.com/copylok.htm
iR0b0t, what kind of USB do you connect your 760a using?
Beginning from LBA 2120 it does not show any reading status messages and is only updating LBA numbers++
I don't yet understand why the data which I expected can't acquire even though a reading error doesn't happen...
I need more time to investigate the cause.
Besides of this, what can cause LBA number being shifted by 2 ?
Creating img (LBA) 2119/327442[F:ProcessReadCD][L:192] OperationCode: 0xd8
LBA[002121, 0x00849] Read error. padding 0x55 [2336byte]
I confirmed it, I'll fix it by next update.
Thanks.
===================== Main Channel, LBA[002121, 0x00849] ======================
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
0( 0) 00 ff ff ff ff ff ff ff ff ff ff 00 01 b0 20 61
LBA[002121, 0x00849] Read error. padding 0x55 [2336byte]
===================== Main Channel, LBA[002121, 0x00849] ======================
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
0( 0) 00 ff ff ff ff ff ff ff ff ff ff 00 01 b0 21 61
===================== Main Channel, LBA[002406, 0x00966] ======================
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
0( 0) 00 ff ff ff ff ff ff ff ff ff ff 00 01 b4 05 61
LBA[002406, 0x00966] Read error. padding 0x55 [2336byte]
===================== Main Channel, LBA[002406, 0x00966] ======================
+0 +1 +2 +3 +4 +5 +6 +7 +8 +9 +A +B +C +D +E +F
0( 0) 00 ff ff ff ff ff ff ff ff ff ff 00 01 b4 06 61
LBA[002120, 0x00848], 2336 bytes have been already replaced at 0x55
LBA[002121, 0x00849], 2336 bytes have been already replaced at 0x55
LBA[002122, 0x0084a], 2336 bytes have been already replaced at 0x55
LBA[002123, 0x0084b], 2336 bytes have been already replaced at 0x55
LBA[002124, 0x0084c], 2336 bytes have been already replaced at 0x55
LBA[002125, 0x0084d], 2336 bytes have been already replaced at 0x55
:
:
LBA[002193, 0x00891], 2336 bytes have been already replaced at 0x55
LBA[002194, 0x00892], 2336 bytes have been already replaced at 0x55
A reading error doesn't seem to happen from 2122 to 2194 but replaced 0x55.
How does the error or message show from 2122 to 2194 on the console?
Don't know the cause...
- added: mainlog
- changed: log file name
If you have time, could you test by /rc 20, 30, 60
2105-2196
2405-2496
...
have the same pattern.
They begin with an incomplete sector (due to combined offset of +18 in this case),
the next sector has a repeated sector ID, i will make an example of the first group:
2105-2196
Sector 2105 has a correct header ID.
Sector 2106 has a repeated sector ID from sector 2105.
Sector 2107 has a repeated sector ID from sector 2106.
...
Sector 2121 has a repeated sector ID from sector 2120.
Beginning by sector 2121 and ending at sector 2196 all sectors have a repeated sector ID from sector 2120.
The last sector of this group = 2196 is not completelly replaced by 0x55.
Probably this problem is fixed. (But 2105, 2405, 2778... is replaced yet)
I don't want to dump it again just yet, because this disc took me 11 hours to dump.
/rc If read error, continue reading and ignore c2 error on specific
sector (Only CD)
For LaserLock, RingPROTECH, safedisc, smartE
val timeout value (default: 60)
If you reduce a ripping time, you should set "timeout value" (60 is 60sec=1min) If you set 30, ripping time will be reduced about 1/2, if you set 15, about 1/4.
Source: NEC PCFX Der Langrisser FXNHE618
Thank you.
- added: check PCFX sector
Those sectors should not have been replaced i think.
You can identify laserlock discs by a file called "LASERLOK.IN", but i think you already have it set.
Your log
Detected [LASERLOK.IN], Skip error from 337 to 10336
I have thought that those error sector should be replaced at 0x55.
If you right, it's difficult for me to recognize whether it is an error sector...
sarami, it should be okay now for SafeDisc 3.15.XXX
My disc does return 1 error more, but its due to a scratch.
I do believe this issue is fixed now, thanks for that.
Thanks test. Uploaded test version.
QQ: is the SH-D162C supported for GDRom dumping?
I don't know because I don't have this drive...
When ripping a data DVD I get this in the command line windows: (PX-708A)
http://www.13thmonkey.org/documentation … c3r10g.pdf
According to this pdf, format 02 means the thing that returns the Disc Key obfuscated by using a Bus Key.
SenseData Key-Asc-Ascq: 05-6f-02, ILLEGAL_REQUEST - COPY PROTECTION KEY EXCHANGE
FAILURE - KEY NOT ESTABLISHED
Failure - Format 02
This error means the thing that can't get disc key because KEY NOT ESTABLISHED.
format 03 means the thing that returns the BCA(Burst Cutting Area) information on DVD media.
[F:ReadDVDStructure][L:360] OperationCode: 0xad
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
Failure - Format 03
This error means the thing that your drive doesn't support getting BCA.
[F:ReadDVD][L:53] OperationCode: 0xa8
ScsiStatus: 02, CHECK_CONDITION
SenseData Key-Asc-Ascq: 05-24-00, ILLEGAL_REQUEST - INVALID FIELD IN CDB
This drive doesn't support streaming
I'll omit this streaming bit in the future because it isn't necessary.
There is another SafeDisc game which doesn't work as expected, i guess it will be the same for all SafeDisc 3.15.XXX
Attached 2 exe. But I don't have a SafeDisc 3.15.XXX. So I don't know whether it works as expected.
sarami wrote:I found this.
ftp://ftp.t10.org/t10/document.95/95-104r0.pdf
http://www.pioneerelectronics.com/pio/p … ManV31.pdf
So, I coded a new option to test.Option Info /d8 Use 0xd8 as ReadCD command forcibly (for data disc)
What's different about this?
for these drives
http://forum.redump.org/post/49337/#p49337
e.g.
I bought the SONY CDU948S and I found this drive supporting 0xd8.
BTW, in case of PLEXTOR, /d8 option don't need. (Because it is by default on)
one of my SafeDisc 1.35.000 games crashes on DIC if used /rc parameter.
Attached exe. But I don't test it.
I found this.
ftp://ftp.t10.org/t10/document.95/95-104r0.pdf
http://www.pioneerelectronics.com/pio/p … ManV31.pdf
So, I coded a new option to test.
Option Info
/d8 Use 0xd8 as ReadCD command forcibly (for data disc)
CodeLock http://redump.org/discs/quicksearch/cod … ction/only
and other discs which use intentional c2 errors in combination with any other protections.
You could set this custom command in priority to EccEdc, which is "/rc" i think.
I don't have these protect disc. plz wait.
is SafeDisc dumped with '55' pattern finally? using /rc parameter?
I think so.
sarami, any chance you can add command line support for replacing ALL sectors with C2 errors by '55' pattern?
What kind of disc needs it? If you can, could you tell me the disc titile and other info.
I am using "audio" command to dump lead-in, lead-out.
If you dump an audio CD from lba 0 to end, you should use "cd" command.
This disc is ring and sector error protect.
The problems of the ring protect are the same as this -> http://forum.redump.org/post/30465/#p30465
- improved: c2 error fixing (& omitted /c2 val 4)
possibly the difference of read cd command might affect the result... (possibly clonecd, isobuster, cd manipulator use 0xbe. DIC uses 0xd8)
- added: /be option for cd
/be Use 0xbe as ReadCD command
https://dl.dropboxusercontent.com/u/355 … adowMan.7z (should be up in a few minutes) Used latest test version
The reason of the huge sub & c2 error is unknown at this time, but possibly the difference of read cd command might affect the result... (possibly clonecd, isobuster, cd manipulator use 0xbe. DIC uses 0xd8)
Uploaded test ver.
- fixed: detect adr sector
- fixed: Label Gate CD, XCP disc
Any clue why I get this error? https://dl.dropboxusercontent.com/u/35528562/DIC.jpg
Logs: https://dl.dropboxusercontent.com/u/355 … eltica2.7z
Uploaded test ver.
About Securom, I can upload clonecd, isobuster, cd mainpulator dump and the one from DIC if that helps?
All DIC log plz.
But I want to know why the hash is different.
Securom v3 or less doesn't seem to work correctly. I get different hashes then ISObuster, CloneCD and CD Manipulator dump
This dump matches my ISOBuster, CloneCD and CD Manipulator dump: http://redump.org/disc/18323/
Securom v3 or less is subchannel protection (like libcrypt). So the cause that the hash varies is different.
Found another:
CATALOG 0000000000000
FILE "TerraOEM.bin" BINARY
TRACK 01 MODE43/2352
INDEX 01 00:00:00
Uploaded 20150522
I have a disc here that is error free with other tools. DIC detects errors. I tried a different drive, same hashes and error free.
Could you tell me the all your ripping drive? (vendor, model, firmware version)
Redump Forum → Posts by sarami
Powered by PunBB 1.4.4, supported by Informer Technologies, Inc.
Currently installed 6 official extensions. Copyright © 2003–2009 PunBB.