Redump Forum

Posted: **Sun Feb 19, 2017 3:15 am**

sarami wrote:
Jackal wrote:CodeLock and LaserLock are similar in that you try to get as many readable sectors as possible with one or more non-plextor drives until you get consistent results. CodeLock patterns can vary: https://redump.info/discs/quicksearch/cod … tion/only/
Ripping the CodeLock by plextor with 0xd8, the strange string can be seen.
Code: Select all
beware the jabberwock my son the jaws that bite the claws that snatch
CDManipulator and CloneCD recognize the sector including this string as error sector.
Game: Rune https://redump.info/disc/31708/
hex editor of sector 2327 http://www.imagebam.com/image/0b922f533425871
Left is ripped by plextor PX-W5224A with 0xd8, right is ripped by TSSTcorp DVD-ROM TS-H353A.
Do you think this CDM/CloneCD (right) images are correct? If you so, what is the reason?

I don't know which dump is 'correct', but if I had to choose between 2 dumps with different error count, I would pick the one with the least amount of errors.. Especially if only 1 brand (Plextor) gives different results for whatever reason and most other drives give consistent results.

Posted: **Sun Feb 19, 2017 1:52 pm**

Jackal wrote:The error count seems to be 1 more for each range than what you calculated?
If 2137 is the first error and 2194 the last, then the total errors in that range is 58.

And please check with your Plextor drive if the start of each error range is the same everywhere as those combined results? It's possible that one of the non-Plextor drives starts 1 sector earlier on some ranges. I don't know why this happens, but I've seen this happen on some drives (my Plextor drives and the Optiarc one always give the same start sector for each range).
As for the end sectors, you can't say for sure if the current results are final, unless you do a manual check. It's possible that some sectors are readable but only after multiple retries. It's really tricky.
It would probably be a good idea if I purchase this game as well, so that we can verify these results. Is this the disc that you're trying to dump? http://ogdb.eu/imageview.php?image_id=1 … mp;limit=0 (with the same ringcode?)
Or maybe you have one of the other LaserLock titles that is already dumped, and you could try to verify it. Then we'll know for sure that your method is reliable.

edit: I just bought Outcast, so we should be able to compare results by the end of the week.

Yeah it's of by one because I forgot to add one to the result.
This is comparing the 5 dumps I have from track 1, each sector that is unique across all dumps is considered bad and if the same sector matches across multiple dumps it's good. I'm simply doing a binary compare of all sectors across all dumps.
Also I checked the good ranges most sectors match 5/5 but not all do.

Code "Sonopress ROMM Z-3580-2/OUTCAST2/2 B" looks good.
This is the only LaserLock title I have currently.

I was reading about twin sectors somewhere but I don't know if LaserLock uses them.
DIC also supports reading the disc in reverse but the /rc switch seems to be ignored as it tries to reread all failed sectors with c2 errors.

Posted: **Mon Feb 20, 2017 9:28 pm**

Does DIC insert dummy sectors, if there are read problems, filled with 0x55 for user data?
IsoBuster fills in "Corrupted Sector - Have fun - Smart Projects" for sectors it can't read.

Changed my script to exclude the aforementioned sectors, this changed the result slightly.
Also I added some extensive checksumming of data blocks and found some things.

Code: Select all

 - before an unreadable range the sectors user data is repeated
   (2108, 2136): 29
   (2481, 2508): 28
   (2781, 2809): 29
   (3158, 3186): 29
   (3531, 3558): 28
   (3907, 3935): 29
   (4280, 4307): 28
   (4659, 4686): 28
   (4956, 4983): 28
   (5332, 5359): 28
   (5707, 5734): 28
   (6233, 6260): 28
 - user data for sectors < 10033 has a lot of similarity
   there are a lot of ranges with 8 sectors where only some of the last 37 bytes of user data differs
 - there are some duplicated sectors (user data) (10033, 10267)

I still don't know what the bad sectors should be replaced with.

With some more dumps I'm down to 604 bad sectors.
I'll attach my current log file which includes checksums for all sectors, good ranges as well as bad ranges.
Log checksums explained, all checksums are sha1.

Code: Select all

RAW     = 2352 byte sector
M1_USER = 2048 byte of user data assuming mode 1 sector
-37     = 2048 - 37 byte of user data

Posted: **Tue Feb 21, 2017 1:17 am**

Could you write down the ranges and sector count like you did before but after the fixes?

And you should always have /RC switch enabled for DIC when dumping error sectors! so that the user data gets the 0x55 pattern like CDM/CloneCD does. If you forgot this in previous dumps then plz fix them.

I will post my results later this week or early next week, when my copy arrives.

edit: Added my dump.. You should redump your disc with CDM/CloneCD because IsoBuster replaces error sectors with non-error sectors.

Redump Forum

Problem dumping LaserLock protected disc.

Re: Problem dumping LaserLock protected disc.

Re: Problem dumping LaserLock protected disc.

Re: Problem dumping LaserLock protected disc.

Re: Problem dumping LaserLock protected disc.