Xref: utzoo comp.sys.ibm.pc:21178 comp.binaries.ibm.pc.d:1327 Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!mailrus!umix!oxtrap!b-tech!m-net!mju From: mju@m-net.UUCP (Marc Unangst) Newsgroups: comp.sys.ibm.pc,comp.binaries.ibm.pc.d Subject: Re: DESCRIBE.TXT Message-ID: <2486@m2-net.UUCP> Date: 7 Nov 88 01:20:08 GMT References: <7377@dasys1.UUCP> <7409@dasys1.UUCP> Reply-To: mju@m-net.UUCP (Marc Unangst) Organization: M-NET, Ann Arbor, MI Lines: 23 In article <7409@dasys1.UUCP> tneff@dasys1.UUCP (Tom Neff) writes: > >How about "zoo lc *" which does the same thing for ZOO files? You put >in the comments. Sounds like you're trying to reinvent ZOO features in >an ARC context. If you have enough control over your archive system to >disrupt distribution packages by inserting alien files in other >people's ARCs, why not just convert them to ZOOs where you have the >complete freedom to include quick & easy descriptions. >to scan. Too simple? Or, as I mention above, there are ZOO comments. PKARC v3.5 and up has file and archive comments, too. One of the prime reasons that ZOO will probably never gain wide acceptance is the fact that it isn't backward-compatable with PKARC. People have to convert all their archives to ZOO. For a BBS with several megabytes of files, this could take a very long while. Perhaps if a person wrote a program to automatically re-pack all of a BBS's files with ZOO, it would help the changeover. The sysop would take the board down for a day, run ARC2ZOO, and then put it back up. -- "Don't find a fault. | Marc Unangst Find a remedy." | mju@m-net.ann-arbor.mi.us ...!uunet!umix!m-net!mju -Henry Ford |