Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!burl!we13!ihnp4!zehntel!hplabs!sri-unix!Eaton.HFED@AMSAA.ARPA From: Eaton.HFED@AMSAA.ARPA Newsgroups: net.micro.cpm Subject: re: disk editor for cpm/1791 Message-ID: <17310@sri-arpa.UUCP> Date: Wed, 14-Mar-84 01:41:00 EST Article-I.D.: sri-arpa.17310 Posted: Wed Mar 14 01:41:00 1984 Date-Received: Sat, 10-Mar-84 14:07:45 EST Lines: 17 DUU and DU2 (with more features) are indeed excellent disk editors. There is however one slight problem when dealing with disks with bad sectors. My BIOS and I assume most BIOS' trap errors and will not return the data to DUU or DU2 if one is detected. This leaves the contents of the previous read in DUU's buffer. I wrote quick and dirty DDT routines to turn off error detection while attemting to repair bad sectors and then reenable error detection when I'm done. NEVER! "That's NEVER EVER try fixing a bad track by doing: read.. write.. increment.. loop. Fix those nasty little sectors one at a time "manually". I completeletely destroyed a directory by doing the afforementioned "never ever". The error handling/reporting by those programs "should" abort loops and return error messages to the user. Jesse (who knows more than one way to destroy a disk)