Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!nwnexus!happym!rwing!nanook
From: nanook@rwing.UUCP (Robert Dinse)
Newsgroups: comp.sys.tandy
Subject: Re: zoo CRC problem on Tandy 6000:  FIX
Summary: CRC
Message-ID: <214@rwing.UUCP>
Date: 10 Jan 91 21:29:41 GMT
References: <1991Jan9.093708.12518@eng.ufl.edu>
Distribution: na
Organization: Totally Unorganized
Lines: 26

In article <1991Jan9.093708.12518@eng.ufl.edu>, jc@joker.mil.ufl.edu (Jim Castleberry) writes:
 >I've tracked down a problem in running zoo on the Tandy 6000 which causes
 >it to create archives with bad crc's.  Though the fix is somewhat obvious,
 >I haven't seen it mentioned on the net, and I've seen others mention the
 >problem with no solution, so I thought I'd post it.
 >
 >The problem is that the zoo "add" code uses *LOTS* of stack.  In my test
 >runs under adb 24k was not enough.  The docs recommend using lots of stack,
 >but the Tandy makefile, mkx68, has flags which result in the default 8k stack.
 >The resulting underrun ends up trashing the static crc table but is not
 >enough to cause a core dump, hence the crc errors.
 >
 >So, to fix it edit mkx68 to use a stack size of 32k by adding "-F 8000"
 >to the "ldswitch=", then recompile.  I also added "-DLINT" to the "cflags="
 >to cut the sccs strings out of the executable, but it will run with or
 >without them.
 >
 >Enjoy!
 >	Jim


     For what it's worth, both zoo and rzsz work fine with the default
stack space if compiled with gcc instead of cc.

     I am curious how not having enough stack space causes this error
since I would expect it instead to cause core dumps.