You are not logged in. Please login or register.
Redump Forum → Posts by celebi
Hi,
unfortunately, for the Safecracker submission, the ISBN and barcodes I submitted are for the box/specific SKU. The disc itself (shown on the backside of the disc cover) has a different ISBN and barcode:
ISBN 1-55345-022-1
Barcode: 6 25904 29440 1
The ISBN and barcode of the box could be provided through the comments.
All the best
celebi
I gave this a try on a couple of drives I have. I have two Optiarc drives, so I include both of them.
I was also trying this on my LG GH22LS30. Turns out I killed it. It got stuck at the first bruteforce stage, so I powercycled it mid-run. Which was a bad idea. The drive started to rapidly bang it's head against whatever wall is in the drive and refuses to read any disc since then, no matter if it is a DVD or a CD.
Well, at least I can say it died for science.
Thank you for your reply! I have an idea on how to do it with redumper... But I need more investigation for this protection. I know how to handle the "usual" ringed protections, but the ones with the audio tracks are especially tricky.
reentrant, I have a bunch of ring protected discs that have the broken sectors within multiple audio tracks.
Is cdarchive able to read audio sectors properly as well?
If you can cut the unneeded bytes and descramble everything with no errors, the errors count should be 0.
Was that related to the disc in question I dumped? If so, can you lead me to the steps how I can strip the unneeded bytes and manually descramble the file?
Request
Language and Region filter of dat file like no-intro
+1!
I have another suggestion: Is it possible extend the "My Dumps" page to allow downloading a .dat file that only contains the user's owned discs/dumps?
Thanks sarami for your great support!!
Is it now safe to submit the DIC dump? Which comment should I choose regarding this weird sector 150? What about the error count - "1" as reported by CD Manipulator and CloneCD or "0" as reported by DIC+edcchk?
sarami, the dumps of cdtroimg and the scrambled DIC file differ. From what I can tell, DIC is missing the first 32 bytes of the image.
First few bytes of the DIC .scm image:
First few bytes of the cdtoimg image:
Trying to read the pregap threw lots of errors - log file and resulting dump available at https://www87.zippyshare.com/v/Xhoz9VMK/file.html
Is it possible that this is a disc with a mastering error instead of a copy protection?
Thanks for your help!
~celebi
Nope, all sectors are mode 1.
Uploaded test. http://www.mediafire.com/file/eq80y20l9 … st.7z/file
fixed: Skipped this error.
Thanks a lot, with this test version I was able to dump this disk. Interestingly the checksums doesn't match with either CD Manipulator or Clone CD.
And even more interesting is that edcchk hasn't detected an error in sector 150 (00:02:00) and just detected it as Mode 1 data sector.
In any way plz upload SCM dump that HAS that faulty sector...
Sorry, the sector 150 I'm referring to is at 00:02:00.
What's the best way to obtain an .scm dump without DIC? Dumping with DIC fails so early that it doesn't create a .scm file. I tried with "cd", "data" and "audio" option.
But READ12 (0xa8) can't read it. Perhaps READ CD (0xbe) is also same. It's weird...
Is this a protection? I don't know. Maybe iR0b0t or Jackal or reentrant know it?
I re-checked again with CD Manipulator and Clone CD, it seems that even those tools don't know how to handle this sector properly. Clone CD fills sector 150 with "55" while CD Manipulator fills the same sector with "00". Does that make any sense? Which tool should I trust more?
Would it be helpful to upload a subdump dump?
I'm actually not completely sure that it's a copy protection... ProtectionID and similar tools don't detect it.
I *think* it's some sort of copy protection since the disc is in pretty good condition and I don't want to believe that's in an unintentional read error just at sector 150... Also look at the TOC, there's a small second and third track just a few seconds long...
UPDATE: Issueing /d8 doesn't help. However, subdump can read the sector without issues...
Thanks for your reply. The issue persists with the latest update unfortunately.
I have an issue with dumping "Anno 1602 - Im Namen des Königs". The disc dates back to 1999 and seems to use a copy protection that includes a broken/defective sector 150.
CD Manipulator is able to dump the disc (matching checksums with two different drives) by skipping sector 150.
DIC command:
E:\_Tools\Programs\DiscImageCreator.exe cd F D:\Redump\Anno 1602 - Im Namen des Koenigs (Germany)\Anno 1602 - Im Namen des Koenigs (Germany).bin 4 /c2 20 /ns /sf Playing around with the different copy protection related parameters doesn't help.
DIC error log:
LBA[000000, 0000000]: [F:ReadCDForSegaDisc][L:1104]
Opcode: 0xa8
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-83 = MEDIUM_ERROR - VENDOR UNIQUE ERROR
lpCmd: a8, 00, 00, 00, 00, 00, 00, 00, 00, 01, 00, 00
dwBufSize: 2048
LBA[000000, 0000000]: [F:ReadCDForFileSystem][L:574]
Opcode: 0xa8
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-83 = MEDIUM_ERROR - VENDOR UNIQUE ERROR
lpCmd: a8, 00, 00, 00, 00, 00, 00, 00, 00, 01, 00, 00
dwBufSize: 2048All logs: https://www93.zippyshare.com/v/FsXrzNR5/file.html
Is there any way to fix this?
Great tool and research!
Tool must be run as admin because it has some other functions like ripping sectors which require admin.
Does that mean that the tool has the ability to rip the DPM information from the CD/DVD itself?
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!!
same here.
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 
)
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.
I dumped 5 safedisc discs, ranging from Safedisc v1.x to 4.6.
Logs: https://www.sendspace.com/file/l7lxjq
C2 error is always 312 bit.
At least for one good safedisc disc I can confirm that *all* sectors with C2 errors are 312 bit.
Most of the sectors of my bad safedisc disc have 312 bit too, the random ones have random values. Logs of the bad disc attached. I'll try to confirm more good safedisc disks.
Logs of the bad disc after a full redump: https://www.sendspace.com/file/9i1ne5
sarami, thanks for the new test version.
Just trying with another known good safedisc disk - I'll see if checksums match with "old" stable version and latest test version. Hold on - logs will follow. Then I'll see if the new test version can do something about the bad safedisc disc.
I'll post the logs of the bad disc too... maybe I can finally get a good dump without any unintentional C2 errors.
I did a few more runs on that problematic disc - it seems that it is in a condition that makes it unusable for proper dumping. I get not only random C2 errors (that get fixed by the re-readings, so the new feature works as expected), but also sync issues. Damn.
sarami, thank you for the fast implementation of this feature request!
It depends on the settings. For my first test run, I used 5 re-reads, but that missed about 20 sectors with unintentional C2 errors (verified against ripping with CloneCD with always creates 579 bad sectors - I guess CloneCD does re-reading right away).
With 5 re-readings, ripping time increased about 5 minutes using my Plextor W5224A at 24x reading speed.
If you want no ripping time increase, just use /sf /c2 0 to disable it.
Update: Test run with 25 re-reads went down to 581 sectors with C2 errors. Now trying with lower read speed and 100 re-reads... Still wonder why CloneCD seems to get past the unintentional C2 errors each and every run.
Redump Forum → Posts by celebi
Powered by PunBB 1.4.4, supported by Informer Technologies, Inc.
Currently installed 6 official extensions. Copyright © 2003–2009 PunBB.