Re: DiscImageCreator
Posted: Sat Mar 31, 2018 2:27 am
This disc had the first 2 LibCrypt sectors undetected: https://redump.info/disc/50247/
Logs: https://drive.google.com/open?id=1ClsZ6 … 32TtOFAaxd
Maybe it's better to stop using prefixed ranges, and just not fix any subs in case /ns is used? because it happens a lot that some LibCrypt/SecuROM data goes undetected.
Or set a limit to how much corruption is fixed in each Q-channel sector. Now it fixed 4 bytes total, including 2 in CRC. I doubt that read corruption can occur on so many bytes at once, and also in both CRC bytes?
Logs: https://drive.google.com/open?id=1ClsZ6 … 32TtOFAaxd
Maybe it's better to stop using prefixed ranges, and just not fix any subs in case /ns is used? because it happens a lot that some LibCrypt/SecuROM data goes undetected.
Or set a limit to how much corruption is fixed in each Q-channel sector. Now it fixed 4 bytes total, including 2 in CRC. I doubt that read corruption can occur on so many bytes at once, and also in both CRC bytes?
I always thought that /ns option should produce identical dumps...