Hmm, I thought i had rights to "when it's ready!" (tm)mr.vince wrote:Yes, "when it's ready!" (tm)
Make sure to have a feature in there that is a life saver when dealing with dodgy disks:
when a verify error occurs during writing, and when the whole write operation is over, be able to just retry the bad sectors for a rewrite. Often old disks need a little scrub before they write just fine afterwards. I hate to redo a full disk write just for 1 or 2 bad apples which resolve themselves after some scrubbing.
Same remark for reading
-> Rattlecopy is the only copier to my knowledge who had this feature and as said before, it helped me a lot with dodgy disks doing sometimes 20 or 30 retries until the individual tracks were one at the time read OK and thus preserved.
ps: The Wildewutz write GUI is simply awful, no overview, no post-operation warning if there was an error, no logfile (nor can scroll up!), no verify and no retries.
Writing via the command line is really easy. If you don't like WildeWutz (which was a fun project anyway) it's as simple as using the -w switch.
And for the backup part, some floppies require a lot of retries before all tracks are read OK. It is just so time consuming to have to reread all the tracks just to rectify a handful of bad ones, with the added risk that a good read track may be read bad the next time due to the unstable nature of the old magnetic fields.
Usually, a disk is good or bad. If a track needs more than 2-3 retries (except for some special protection which is hit or miss and where the write process will automatically adapt to this), the media is bad.