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 data
Post's attachmentsoc2_f8_dumps.7z 785.53 kb, 20 downloads since 2017-02-21
You don't have the permssions to download the attachments of this post.