Xref: utzoo comp.sys.amiga:75861 comp.sys.amiga.tech:17488 Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!clyde.concordia.ca!thunder.mcrcim.mcgill.edu!snorkelwacker.mit.edu!apple!mips!sdd.hp.com!samsung!uunet!nuchat!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga,comp.sys.amiga.tech Subject: Re: HD Errors Message-ID: <7464@sugar.hackercorp.com> Date: 5 Jan 91 14:31:38 GMT References: <37492@cup.portal.com> <1991Jan2.190655.15790@jato.jpl.nasa.gov> <1991Jan3.141624.25450@forwiss.uni-passau.de> <1991Jan3.230319.3648@jato.jpl.nasa.gov> <17128@cbmvax.commodore.com> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 16 In article <17128@cbmvax.commodore.com> jesup@cbmvax.commodore.com (Randell Jesup) writes: > Another point to realize is that most amiga users wouldn't know what > to do with an fsck-equivalent. So why do you provide one (DiskDoctor)? One that doesn't work very well, at that. About the only time we have to do more than "fsck -y" is when there are physical disk problems. I'll agree with you that for non-simple problems, you need more smarts. But how about at least providing a reliable DiskDoctor for the 90% case, and an in-place fsck for developers? DiskSalv isn't really a viable alternative for hard disks. -- Peter da Silva. `-_-' .