Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!wuarchive!psuvax1!psuvm!cunyvm!ndsuvm1!mtus5!ldshaner From: Leon D. Shaner Newsgroups: comp.sys.amiga Subject: Re: zoo & gurus Message-ID: <90079.102857LDSHANER@MTUS5.BITNET> Date: Tuesday, 20 Mar 1990 10:28:57 EST Organization: Computing Technology Services, Michigan Technological Univ. References: <1277@lpami.wimsey.bc.ca> I've had repeated trouble unzooing files greater than 800 K in length. In particular when the NewTek3 Demo was first posted on Xanth, it was something like 1.7mb. I ftp'd it to a sun and uuencoded it, split it into parts, copied it to I*M floppies brought it home and joined the parts, uudecoded it (which gave no errors) and then proceded to unzoo it. The first disk came out which means zoo liked the first 800 or so K-bytes. Then part way through the second disk, it said the rest of the archive was corrupt. Obviously I'm using a hard drive. Is it possible that the writers of zoo never anticipated being able to unzoo archives larger than a floppy and hardcoded some magic number as the upper limit? Incidentally, I got curious and took the complete uuencoded file as it ended up on my machine and I re-split it, copied it to I*M floppies again, took it back to the Sun and rejoined/uudecoded the archive, found a copy of zoo somewhere and unzooed the result with no errors. Both my version of zoo and the one on the Sun were v2.00. I have had the same trouble many times since. I usually do most of the archive manipulations on my machine since my Sun access is limited, but now (as I am sure most do) I do the unzooing on the Sun. Any ideas what the problem may be? Anyone else notice this? ------- +--------------------------------+-----------------------------------+ | LEON D. SHANER :BBS: AMIGA BITSWAP CENTRAL DISPATCH: | EE UNDER GRAD. : (906)487-0006 <-AMIGA ONLY! : | MICHIGAN TECHNOLOGICAL UNIVERSITY : FREE! - 24 HOURS - 80 MB : +------------------------------------+-----------------------------------+