Newsgroups: comp.sys.amiga.programmer
Path: utzoo!utgpu!watserv1!sunee!avadekar
From: avadekar@sunee.waterloo.edu (Ashok Vadekar)
Subject: Re: zoo? why does it grind the disk?
Message-ID: <1991Apr9.135123.14305@sunee.waterloo.edu>
Keywords: zoo
Organization: University of Waterloo
References: <robtu.670882506@mexia> <1991Apr6.170351.13111@sunee.waterloo.edu> <1991Apr8.232658.1589@maths.tcd.ie>
Date: Tue, 9 Apr 1991 13:51:23 GMT
Lines: 30

In article <1991Apr8.232658.1589@maths.tcd.ie> ecarroll@maths.tcd.ie (Eddy Carroll) writes:
>This is true, but the real reason for the delay is that the original Amiga
>version of Zoo called Aztec's "expand wildcards" routine for every file
>on the command line, even if the filename didn't contain any wildcard
>characters. So, a command line like:
>
> zoo a zoofile file1 file2 file3 file4 file5 file6
>
>ended up scanning your current directory 6 times. If you had any number
>of files at all in your directory, this took forever.
>
>I believe the latest version of Zoo (V2.01) fixes this problem. I did
>a patch for Zoo 2.0 that fixes the problem as well, a while back. Other
>than that, using piped filenames is the way to go.
>
>Eddy
>-- 
>Eddy Carroll           ----* Genuine MUD Wizard  | "You haven't lived until
>ADSPnet:  cbmuk!cbmuka!quartz!ecarroll           |    you've died in MUD!"
>Internet: ecarroll@maths.tcd.ie                  |   -- Richard Bartle

Except that I have compiled that code using Lattice, and a zoo -v does the
same thing.  It is quite possible that both things are happening.  But
when it takes 5 minutes to list the contents of a 1 meg zoo archive
OFF OF A HARD DISK, it is VERY annoying.  I solved the problem by hacking
the zoo source to death.  I also added 'real' wildcard support (Ie. the way I
want it).  BTW, the Lattice wildcard routines, when running in MSDOS '*' mode
convert the filenames to lowercase.

Ashok Vadekar
