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
First of all, thank you for this wonderful software.
A nice feature would be to add the possibility to try every byte combination possible to recover a dead MFM sector and make it check against the crc value.
It would be useful in that context to be able to select the few wrong bytes of the bad track and be able to check automatically every byte combination on the selection and review the combinations matching the CRC value.
Best regards and thank you for your time.
The text was updated successfully, but these errors were encountered:
This is already implemented. The "Repair" button does a brute force guessing at the cell level. The issue is that the selected area should be short enough to limit the risk to have a crc collision. And the combinatorics can be very high with "large" area. Regarding your example, i thing this can't be fixed this way, the noise area appears quite large...
Thank you for your reply. I was unable to find good documentation about the repair function. How will it decide what has to be repaired? Do we have to tell it? How to select a start and end marker of the zone to be repaired? Best regards
Hello,
First of all, thank you for this wonderful software.
A nice feature would be to add the possibility to try every byte combination possible to recover a dead MFM sector and make it check against the crc value.
It would be useful in that context to be able to select the few wrong bytes of the bad track and be able to check automatically every byte combination on the selection and review the combinations matching the CRC value.
Best regards and thank you for your time.
The text was updated successfully, but these errors were encountered: