Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Request : CRC column / Repair #142

Open
ourIThome opened this issue Apr 9, 2020 · 0 comments
Open

Request : CRC column / Repair #142

ourIThome opened this issue Apr 9, 2020 · 0 comments

Comments

@ourIThome
Copy link

ourIThome commented Apr 9, 2020

Each file on an AmigaDOS disk contains an expected CRC for the file.

I am totally new to your tools, so maybe this exists ... or maybe would be nice to exist if not already there.

I use a PC tool called "ADF Workshop" - a GUI tool, where I can list the files on an ADF and see if there are problems needing to be fixed -- bad CRC for files get marked in red.

Unfortunately ADFW this doesn't have a repair this broken file, with this good file -- I think community worried about this feature being in the wrong hands / making further problems.

I would like if the CRC can be detected / scanned / report in the output ... that I might be able to identify the broken file, and have a "repair" option, where my potential fix file (or would be nice to point to a fix folder, and all file sizes matching are processed one at a time), its CRC is calculated ... looks to the ADF to see if the file CRC matches ... and then inplace overwrite the contents of the file to the ADF. Because I am looking for an inplace repair ... I am trying to minimise touching any other sectors / data.

I wish the data to inplace overwrite the same tracks and sectors where the file currently exists.

If you want this into two requests, I will raise two new ones and close this down -- I wanted to at least document what I would like, and why ... as the two kind of go hand in hand, and might help knowing what the intent is for. Cheers

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant