You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I reported this to sarami (its DIC program), but this problem also affects the redumper program
One of the dumpers (Lugamo) has a SafeDisc disc and there are 2 files protected by SafeDisc (00000001.TMP and 00000002.TMP). Both files have intentional errors, but when redumper finishes the dump, it tries to read the sectors from 00000002.TMP again, which ends in failure. Is it possible for redumper, in addition to the 00000001.TMP file, to also skip intentional errors from the second file 00000002.TMP?
The version used is 310
Logs - http://forum.redump.org/post/114274/#p114274
The text was updated successfully, but these errors were encountered:
C2 10048-10136 range pattern is nothing like SafeDisc, variable bits.
If, in fact, 00000002.TMP belongs to [10029 .. 10183] like it's claimed, it might be a previously unknown variation but preserving it requires some fundamental changes in how we want to preserve such discs, very similar to new Datel protection that has yet to be handled by redumper. I will keep this open for now as a reference.
There is also a chance it's damaged disc, please provide .skeleton file generated from .bins with --force-split so I can double check 00000002.TMP LBA range.
I reported this to sarami (its DIC program), but this problem also affects the redumper program
One of the dumpers (Lugamo) has a SafeDisc disc and there are 2 files protected by SafeDisc (00000001.TMP and 00000002.TMP). Both files have intentional errors, but when redumper finishes the dump, it tries to read the sectors from 00000002.TMP again, which ends in failure. Is it possible for redumper, in addition to the 00000001.TMP file, to also skip intentional errors from the second file 00000002.TMP?
The version used is 310
Logs - http://forum.redump.org/post/114274/#p114274
The text was updated successfully, but these errors were encountered: