This seems like another ring protection similar to Laserlock and CD Ring Protect. Jackal or Reentrant will have to chime in here if they have ever dealt with that particular protection, and if there is a method of dumping it. I gave up trying to dump discs with these protections as the results are inconsistent and we have no way of knowing if the dump is good or not.
Re: Issues dumping PC disc with "Code Lock" copy protection (18 replies, posted in General discussion)
sarami, please remove this cab scanning stuff, this is out of scope for DIC. Please make a separate tool or make it off by default.
Rib ran a patent search for SecuROM, document here https://patentimages.storage.googleapis … 2631A1.pdf
Rib/Wiggy2k found the one for CDilla/SafeDisc as well here https://patentimages.storage.googleapis … 353890.pdf
Nice, interested to look at what /p does.
Oh nice sarami, glad to see you working on this!
Yeah its doing something to measure the angular velocity which gives some idea of the density of the recording. I guess its doing this via read seeks, maybe Reentrant has some further insight on how it works and translates to the tables it makes.
I've never had issues with it on CDs, only bugs on certain dual layer DVDs like GTA IV and Supreme Commander.
Can you check how it does the error stuff with that Skidoo discs, it has a way of dealing with the errors where it doesn't hang infinitely. No other tool I found can do this.
That's weird, I was able to capture it, I sent you a log before but you said something about not being able to open it. Maybe its because I am using a USB adapter?
OK, I was just curious actually if there was some miscommunication because of language differences. I'm going by what he said, I'll prod him to post here again.
Now that you have Bushound working, can you also analyze what Alcohol does with errors and DPM. Would be great to have all in one solution that is actively developed. I cannot get Alcohol developers to address bugs even though I paid full price for it.
I'm curious if you misunderstood what RibShark was saying.
Are you trying to read those sectors? Because that will of course fail, it can't overread. But reading the last sector possible then using 0xF1 to fetch all remaining from the buffer (it's quite large afaik) should work?
I verified that VOB Protect CD has illegal MSF, so these all need to be redumped without /sf
That kind of sucks, the DVD drives are awful and unreliable
I use it on Windows 7 64 bit Enterprise without an issue, and no, it's not an illegal version.
Could he really get the scrambled sector data by the method? I can't use bushound readily because it's really expensive.
It's been free for personal use for some time now ?
He told me he didn't have code, and that he just edited the command in the buffer with bushound.
Also latest version will crash if the drive tray is open.
+1764 is enough for 99.9% of discs if more won't work, there's only a few discs in db with larger offset.
I'll post logs next time I run into that.
Would you make ecc/edc checks be ignored on audio tracks, this should solve the false error problem.
Any word on the error handling?
I don't understand how to see this log.
It's a text file that has logged all the scsi commands, search it for "medium error" to see what it does when encountering the sync errors.
I did try to dump with CloneCD too, it hangs forever in the same manner that DIC does. I am unable to capture how Daemon Tools handles it since they cloak the driver.
I did a bushound capture when dumping Settlers III Mission CD with alcohol to see how it handles the errors in the rings without aborting or hanging forever. It seems to use a different mode according to RibShark when encountering medium errors. I am hoping you may find this useful to improve DIC to handle such errors better and not hang forever on them.
My hopes for this are because using the file skipping misses the protected areas readable sectors which cause the protection checks to fail. I think this disc uses laserlock or proring tech, I am not sure.
I made a dump of the Ski-Doo X-Team Racing disc as well, but this one didn't provide anything interesting, I will try with clonecd to see if it's advanced sector scanner is more efficient.
Re: Reason for Plextor requirement for PC CD-ROMs? (2 replies, posted in General discussion)
It's the positive offsets yes, and also CDDA needs offset correction. Also they dump the disc in audio mode with C2 error correction so that we are sure the dump is good. The drives which support this stuff are listed on sarami's FAQ for DIC. You can buy an ASUS BD drive which is capable of these things.
Currently we do not take subchannel data because it has no error correction possible without using EAC like method of multiple re-reads but there is no guarantee that it is correct. We do keep SecuROM sub data for those games. DIC does dump subchannels, but they are corrected and we cannot take this is as valid data.
Currently there is no way to preserve topology based protections perfectly, so if you want to use your images which have that (SecuROM, StarForce etc) then you need to make your own MDS files with Alcohol for personal use.
The readme in the OP has a list of supported drives. https://github.com/saramibreak/DiscImag … /README.md
There's another bug in ecc/edc check. It doesn't report the single SecuROM error when the disc is mainly mode 2 and has a single mode 1 sector.
LBA[332302, 0x5120e], MSF[73:52:52], mode 2 form 1, SubHeader(IsInterleaved), (ChannelNum), (SubMode), Form 1, Data, (CodingInfo) LBA[332303, 0x5120f], MSF[73:52:53], mode 1 LBA[332304, 0x51210], MSF[73:52:54], mode 2 form 1, SubHeader(IsInterleaved), (ChannelNum), (SubMode), Form 1, Data, End audio, (CodingInfo) LBA[332305, 0x51211], MSF[73:52:55], mode 2 form 1, SubHeader(IsInterleaved), (ChannelNum), (SubMode), Form 1, (CodingInfo) LBA[332306, 0x51212], MSF[73:52:56], mode 2 form 1, SubHeader(IsInterleaved), (ChannelNum), (SubMode), Form 1, (CodingInfo) [NO ERROR] User data vs. ecc/edc match all
Multiple files are supported from 20191022 162447, please edit C2ErrorProtect.txt.
Different hashes are outputted every time.
Well yeah, it's not really suited to these kinds of discs and requires manual work, but we need to be able to get an initial dump to work from first without waiting a really long time. I was hoping you could improve how it handles errors, much like Alcohol does with it's advanced error scanner that uses a different mode. But improve it so it tries to re-read sectors that don't have the heavy sync errors.
Either way if we could skip the files with the errors that would be great, but currently you can't specify multiple files to skip, it only accepts one.