Technique to fix bad sectors??

[bird@MCS.COM (Joe Walters)]

Today I tried to backup my Texas.II Vol 7 disk (REAL old history), and
found that it had suffered bit rot (a Nathan Mates saying that amuses
me and also describes the problem).

The disk now has six sectors on different tracks that are bad
(1529 ($5F9), 1551 ($60f), 1564 ($61C), 1566 ($61E), 1581 ($62D),
1594 ($634).

These are text/AppleWorks files so one or more errors probably would
result in one or more misspellings, which I could fix with the spell
checker if I could only read them in.

ProSel 8/16 is no help cause it can only lockout bad blocks that do not
belong to a file. Any further input on the value in this situation is
welcomed - I don't think there is any. I could not get Block Warden to
read the bad sectors so it isn't helpfull in this situation.

My main hope became Copy ][ +. In the Sector Editor for 3.5" disks
I can read the bad sectors if I use the Patched options to ignore
errors in the checksum, etc. What I cannot figure out is how to tell
Copy ][+ to write the sector out using computed checksums for the
data.

Appendix C says:

Parm    Orig     Parm
Num     Value    Name
----   -------   -----
65      FF       DEPI
     Check for data field checksum error? FF = yes, 00 = No
     REVERSED!! $FF = No, $00 = Yes. Correct your manual.

Leaving this parameter to its default ($FF) the disk is copied with no
errors, however, the resultant disk has the same exact errors as the
original.

Changing this parameter to $00 causes the Sector Copy to abort after
reading all sectors with a "2" in the result field for the bad
sectors as outlined above.

What I'm looking for is a Copy ][+ 9.1 process that will allow reading
the bad sectors (the default now), and then write them out using the
correct checksums for the address and data. (Actually, almost any
version of Copy ][+ since I have most of them and their manuals.)

Kind Regards,

-- 
	Joe Walters:  bird@mcs.net
	To know and not to do is to not yet know