Xref: utzoo comp.sys.amiga.tech:15228 comp.sys.amiga:69166 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!sdd.hp.com!uakari.primate.wisc.edu!pikes!mercury.cair.du.edu!isis!chanson From: chanson@isis.cs.du.edu (Chris Hanson) Newsgroups: comp.sys.amiga.tech,comp.sys.amiga Subject: Re: Disk woes. Message-ID: <1990Oct18.012922.2186@isis.cs.du.edu> Date: 18 Oct 90 01:29:22 GMT References: <1990Oct11.193142.13719@ecst.csuchico.edu> <1990Oct12.124753.14723@sisd.kodak.com> <2076@jimi.cs.unlv.edu> <1990Oct12.232707.28954@caen.engin.umich.edu> <1990Oct12.235513.16858@hoss.unl.edu> Reply-To: chanson@isis.UUCP (Chris Hanson) Distribution: na Organization: Matrix Lines: 27 > All the program does is reads a directory, and for every file with a .zoo extension, it extracts it, lharcs it, then moves it back. The problem is that after the first file FROM floppy, it crashes when it hits the ExNext function. < If I recall, doesn't the filesystem sometimes eat it when you add/remove files between an ExNext and another ExNext? Perhaps if you were to build a 'hit list' (so to speak ;) of all the files to process BEFORE you began the conversion process. Then you would have all your directory scanning done before you started creating/removing files. And then again, I may be totally off track. The reason it would work on HDs and RAMdisks, but not floppies,is that they use different FileSystems. Your floppy is probably (unless you're really weird) using OFS, your HD is probably FFS, and the RAMdisk uses some GodOnlyKnowsWhatItIsFS. Give it a try. Can't hurt. More ridiculous effluvium from the mouth of: Chris - Xenon -- #define chanson Christopher_Eric_Hanson || Lord_Xenon || Kelson_Haldane I work, but you don't know who I work for. And they don't know I'm here. "...Other fish to fly." -E. Miles