Xref: utzoo comp.sys.mac.misc:7795 comp.sys.mac.system:2954 comp.sys.mac.wanted:2387 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!aplcen!boingo.med.jhu.edu!haven!mimsy!mojo!russotto From: russotto@eng.umd.edu (Matthew T. Russotto) Newsgroups: comp.sys.mac.misc,comp.sys.mac.system,comp.sys.mac.wanted Subject: Re: Directory Corrupted! Help! Message-ID: <1991Jan24.222703.10538@eng.umd.edu> Date: 24 Jan 91 22:27:03 GMT References: <1991Jan22.135217.3697@stb.info.com> Sender: news@eng.umd.edu (C-News) Organization: College of Engineering, Maryversity of Uniland, College Park Lines: 44 In article <1991Jan22.135217.3697@stb.info.com> jspear@stb.info.com (Artichoke) writes: > >Starting Point: >- 120M Quantum drive partitioned by Silver Lining 5.13 to 80 and 34M. >- System 6.0.7, Desktop Manager, zillions of inits and junk on 80M. >- 80M partition has less than 300K free space, optimized in Nov 90. >- No problems with 34M partitions, says Disk First Aid and others. > >What happened: >- Copy folder containing 2 files from floppy to root of the 80M, and > I get a folder containing two 0K files (on floppy they were 50K+) >- Delete the folder with empty files. Many explatives fill room. [lots of attempts to fix FOLDER FROM HELL] >- Run PC Tools Deluxe MacTools Rescue 1.0, "Fix Volumes, Unknown Prob" > -- Says Volume Info, Extent File and Catalog File are OK, but > -- Volume Bitmap didn't match catalog (repaired, it said) > -- Volume Bitmap freepace didn't match volume info (can't repair, > it says). >- Run Rescue again > -- Extent File BAD, "The file header block is damaged", no repair > offered. >- Reboot Mac, now when the system tries to mount the 80M partition I > get "This disk is damaged. Do you want to initialize it?" > SOOO PC Tools Deluxe made things worse, not better. > >What to do next? >- Buy yet another utility: Norton for the Mac? I don't know of any utility that can completely fix the directory damage that results in the undeletable folder (just fixing the directory valence doesn't do it) >- Write nasty letter to Apple and Central Point? Especially Central Point-- they shouldn't have damaged your directory more. >- Reinitialize/restore, and wait for next time this happens? Yes, since you have a current backup-- no other solution will result in a repaired directory structure. (and depending on how your backup is done-- file by file or image-- even this may not repair the directory structure) -- Matthew T. Russotto russotto@eng.umd.edu russotto@wam.umd.edu .sig under construction, like the rest of this campus.