Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!usc!brutus.cs.uiuc.edu!zaphod.mps.ohio-state.edu!wuarchive!mit-eddie!uw-beaver!Teknowledge.COM!unix!hplabs!hp-sdd!ncr-sd!ncrlnk!ncrwic!wsucsa!mwjester
From: mwjester@wsucsa.uucp
Newsgroups: comp.sys.atari.st
Subject: Re: zoo problems
Message-ID: <13255@wsucsa.uucp>
Date: 14 Feb 90 11:03:11 GMT
References: <9221@cbnewsm.ATT.COM>
Distribution: comp.sys.atari.st
Organization: Wichita State Univ., Wichita, Ks.
Lines: 30

In article <9221@cbnewsm.ATT.COM>, wao@cbnewsm.ATT.COM (william.a.oswald) writes:
> Has anyone on the net successfully unpacked a zoo file
> (anything.zoo) using any of the available zoo programs?
> I have down loaded several .zoo files using XMODEM and
> KERMIT and have tried to unpack them using several ZOO
> programs (booz for example). Nothing works. I always
> get a CRC error.
> 
> Thanks
> Bill wao@cbnewsm.att.com
>      wao@aloft.att.com

I originally got zoo from terminator (the file zoobin.arc, if I recall) and
have had very few problems...and these problems have been caused by doing a
file transfer in the wrong mode.  A typical sequence for me might be:

ftp a file from an internet site to the local VAX
kermit the file from VAX to ST (using Uniterm)
unzoo the file

As long as I remember to use binary as the type, things come out OK.  For the
FTP part, this usually means SET TYPE I; on the VAX end of Kermit, it's SET
FILE TYPE BINARY.  In Uniterm, binary is an option on the Kermit dialog box.
One check that helps when FTPing - the number of bytes transferred should be
equal to the filesize (if the host lists sizes in bytes, e.g.Unix).  If the
counts don't match, you _will_ get CRC errors.

Hope this helps - feel free to email with questions.

Max J.