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
Is your feature request related to a problem? Please describe.
There is a known issue with Plextor firmwares sometimes not correctly detecting all SecuROM sectors. As a result, some submissions of PC discs to redump are missing information (usually the first sector at 00:01:74).
Describe the solution you'd like
Each SecuROM version has a known number of sectors that should be present. MPF should parse the number of SecuROM sectors actually detected and compare it against these known numbers:
Pre-v3 - 216
v3 - 90
v4 - 99
post-v4 - 11
Where the number of sectors is any number other than the above, an error message should be popped up/added to the !submissionInfo.txt file noting a possible error and directing the dumper to the redump forums.
Describe alternatives you've considered
It is possible that this behaviour could be requested to be implemented at the dumping tool (DIC/redumper), but as this is not an issue which can be resolved by fixing either tool, and as both are currently accepted for redump submission, it would be preferable for MPF to make this check.
Is your feature request related to a problem? Please describe.
There is a known issue with Plextor firmwares sometimes not correctly detecting all SecuROM sectors. As a result, some submissions of PC discs to redump are missing information (usually the first sector at 00:01:74).
Describe the solution you'd like
Each SecuROM version has a known number of sectors that should be present. MPF should parse the number of SecuROM sectors actually detected and compare it against these known numbers:
Where the number of sectors is any number other than the above, an error message should be popped up/added to the !submissionInfo.txt file noting a possible error and directing the dumper to the redump forums.
Describe alternatives you've considered
It is possible that this behaviour could be requested to be implemented at the dumping tool (DIC/redumper), but as this is not an issue which can be resolved by fixing either tool, and as both are currently accepted for redump submission, it would be preferable for MPF to make this check.
Additional context
Two forum posts describe this issue in more detail http://forum.redump.org/post/105561/#p105561 and http://forum.redump.org/topic/56767/ibm-pc-temporarily-discarded-dumps-from-duyc37/
The text was updated successfully, but these errors were encountered: