I need IRD files for the PS3 discs, any chance for this to happen?
There are a lot of IRD files out there, not for all discs though, having official redump IRD files would really be great.
1 2021-01-24 10:51:38
Topic: Would it be possible to provide IRD files for PS3 discs? (2 replies, posted in General discussion)
2 2017-02-21 03:28:57
Re: Problem dumping LaserLock protected disc. (13 replies, posted in General discussion)
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.
- 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.
RAW = 2352 byte sector
M1_USER = 2048 byte of user data assuming mode 1 sector
-37 = 2048 - 37 byte of user data3 2017-02-19 19:52:01
Re: Problem dumping LaserLock protected disc. (13 replies, posted in General discussion)
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.
4 2017-02-19 00:07:48
Re: Problem dumping LaserLock protected disc. (13 replies, posted in General discussion)
Why is that?
Anyway I made a small python script to compare my 5 dumps of track 1 so far.
And there are indeed 12 ranges with bad sectors.
Bad blocks found: 732
Bad range: 1 : (2137, 2194) : 57
Bad range: 2 : (2509, 2571) : 62
Bad range: 3 : (2810, 2871) : 61
Bad range: 4 : (3187, 3244) : 57
Bad range: 5 : (3559, 3621) : 62
Bad range: 6 : (3936, 3993) : 57
Bad range: 7 : (4308, 4370) : 62
Bad range: 8 : (4687, 4745) : 58
Bad range: 9 : (4984, 5046) : 62
Bad range: 10 : (5360, 5422) : 62
Bad range: 11 : (5735, 5797) : 62
Bad range: 12 : (6261, 6319) : 585 2017-02-18 22:44:57
Re: Problem dumping LaserLock protected disc. (13 replies, posted in General discussion)
So basically read the data track as many times as possible with different drives and do a sector compare?
I could use a python script to compare the single sectors, the sectors which never match must be the bad ones.
6 2017-02-18 04:24:33
Re: DiscImageCreator (3,497 replies, posted in General discussion)
sarami wrote:
Seeing the log, I don't understand the cause of error.
Is this a same disc? http://www.ebay.de/p/pizza-syndicate-mi … 2209711205
If so, I'll buy to test.
Yes it's "Mehr Biss", here are some scans for the cover and disc
https://i.imgsafe.org/7bd0e6e5b8.jpg
https://i.imgsafe.org/7bd10be302.jpg
https://i.imgsafe.org/7bd11e6611.jpg
I'm not sure if I still have the original box to look up the barcode.
7 2017-02-17 01:36:34
Topic: Problem dumping LaserLock protected disc. (13 replies, posted in General discussion)
I have a disc, Outcast (German) (Disc 2), which uses LaserLock protection and I can't seem to get a consistent dump from this.
The disc has one data track and multiple audio tracks, only the data track is different every time the audio tracks always match.
Is it even possible to dump this reliably?
I'm using DIC with PX-W4824A.
Command line is "DiscImageCreator.exe cd w: oc2\oc2.cue 8 /c2 /rc"
8 2017-02-17 01:13:17
Re: DiscImageCreator (3,497 replies, posted in General discussion)
sarami wrote:
Is this the same disc? If so, I don't know why the error came to happen.
The latest firmware of PX-W4824 is 1.07. I recommend the update.
No the main game worked at first try, this is the mission cd which also has two data tracks but always causes this error.
I didn't really pay attention to the drives firmware but the change log from 1.06 to 1.07 says only "Improvement of writing quality of TDK CD-R media." I wouldn't expect any change from upgrading but I tried anyway and as expected it still fails.
9 2017-02-12 20:10:45
Re: DiscImageCreator (3,497 replies, posted in General discussion)
The mission cd to Pizza Syndicate also has two data tracks and DIC throws this error
D:\redump\__tools\DiscImageCreator_20161119\Release_ANSI>DiscImageCreator.exe cd
w: pizza_cd\pizza_cd.cue 4 /c2
OS
Windows XP Professional Service Pack 3 32bit
AppVersion
x86, AnsiBuild, Nov 19 2016 18:33:03
/c2 val1 is omitted. set [1024]
/c2 val2 is omitted. set [4096]
/c2 val3 is omitted. set [4]
CurrentDirectory
D:\redump\__tools\DiscImageCreator_20161119\Release_ANSI
WorkingPath
Argument: pizza_cd\pizza_cd.cue
FullPath: D:\redump\__tools\DiscImageCreator_20161119\Release_ANSI\pizz
a_cd\pizza_cd
Drive: D:
Directory: \redump\__tools\DiscImageCreator_20161119\Release_ANSI\pizza_
cd\
Filename: pizza_cd
Extension: .cue
Start time: 2017-02-12(Sun) 13:05:38
Set the drive speed: 705KB/sec
This drive support [command: 0xd8, subch: 00]
This drive support [command: 0xd8, subch: 0x1]
This drive support [command: 0xd8, subch: 0x2]
This drive support [command: 0xd8, subch: 0x3]
This drive support [command: 0xd8, subch: 0x8]
Checking reading lead-out -> OK
Checking SubQ adr (Track) 2/ 2
Checking SubRtoW (Track) 2/ 2
Reading DirectoryRecord 8/ 8
LBA[000000, 0000000], [F:ReadCDForVolumeDescriptor][L:909] OperationCode: 0xa8
ScsiStatus: 0x02 = CHECK_CONDITION
SenseData Key-Asc-Ascq: 03-02-83 = MEDIUM_ERROR - OTHER
lpCmd: a8, 00, 00, 03, f2, 0b, 00, 00, 00, 01, 00, 00
dwBufSize: 2048
End time: 2017-02-12(Sun) 13:05:48