Merge partially damaged module copy 0 with copy 1

[Jirbun]

DR encounter this all the time, I guess they use the reading composite option.
But if I want to read copy 0 and 1 separately, then there are different areas in both copies that are unreadable represented in digits 21, is there a way to automatically merge the correct data between the two copies?

[pepe]

of course, you can write a small prog for doing that...

[fzabkar]

DR encounter this all the time, I guess they use the reading composite option.
But if I want to read copy 0 and 1 separately, then there are different areas in both copies that are unreadable represented in digits 21, is there a way to automatically merge the correct data between the two copies?

Upload your two copies and I'll write a merge tool for you. In fact, I may have already written one.

[Jirbun]

Thank you very much fzabkar!
Do you want to send it to me for a fee by email or do you upload it here for everyone?

Attachments

03 1.rar

(111.18 KiB) Downloaded 22 times

[fzabkar]

I'll upload it here when I get around to writing it. It's a relatively trivial task.

[fzabkar]

Using a hex editor, I replaced every sector that was filled with 0x21 with 0x00 (using search and replace). Then I merged the two files by bitwise OR-ing their contents.

I just need to modify my file merging tool to accommodate the bad sectors. Alternatively, if PC3000 can zero-fill each bad sector, then you can use this tool:

https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.exe

https://web.archive.org/web/20230522150553/http://www.users.on.net/~fzabkar/FreeBasic_W32/Utils/filmerg7.bas

I confirmed that the checksum for the merged module is 0x00000000.

Attachments

merged.7z

(65.51 KiB) Downloaded 17 times