Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!viusys!uxui!unislc!dave From: dave@unislc.uucp (Dave Martin) Newsgroups: comp.sys.amiga.programmer Subject: Re: zoo? why does it grind the disk? Message-ID: <1991Apr9.013826.29270@unislc.uucp> Date: 9 Apr 91 01:38:26 GMT References: Organization: unisys Lines: 19 From article , by robtu@itx.isc.com (Rob Tulloh): ... > I don't know why zoo would need to thrash the disk to add files. > Can anyone offer an explanation? I've noticed that zoo does this with requests to list the contents of the archive (but not when extracting) too. It happens when the size of the directory containing the archive has exceeded the capabilities of the buffers for the harddisk to cache the entire directory. (Sorry about the iky sentence) It does this when given the entire name of the archive including the .zoo, or when given a partial name. It seems to be doing some kind of directory scan (possibly more than once). It does not do it when extracting though. -- VAX Headroom Speaking for myself only... blah blah blahblah blah... Internet: DMARTIN@CC.WEBER.EDU dave@saltlcy-unisys.army.mil uucp: dave@unislc.uucp or use the Path: line. Now was that civilized? No, clearly not. Fun, but in no sense civilized.