Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!yale!cs.yale.edu!fischer-michael From: fischer-michael@cs.yale.edu (Michael Fischer) Newsgroups: comp.sys.atari.st Subject: Re: VAULT problems Message-ID: <27875@cs.yale.edu> Date: 19 Dec 90 14:46:04 GMT References: <1990Dec19.132054.28228@watmath.waterloo.edu> Sender: news@cs.yale.edu Organization: Yale University Computer Science Dept., New Haven, CT 06520-2158 Lines: 28 Nntp-Posting-Host: ginkgo.theory.cs.yale.edu Originator: fischer@ginkgo.CS.Yale.Edu In article <1990Dec19.132054.28228@watmath.waterloo.edu> ljdickey@watmath.waterloo.edu (L.J.Dickey) writes: >In article > larserio@ifi.uio.no writes: >>I have a BIG problem with THE VAULT hard disk backup !!! >>It won't work at all together with the DCACHE hard disk cache program. > >Remember Turtle? Turtle insists that it be in control of everything. >Its own ram disk, everything. I wonder of the writer of The Vault >made the same assumptions, but did not build in the checks to make sure. Please, keep your cool and don't start speculations flying on the net. All that Lars reported is that he has a problem running THE VAULT and DCACHE together. We don't know what the problem is, but we are trying to find it. Meanwhile, don't run them together. They both apparently work fine for most people most of the time when used separately. TURTLE, too, seems to work well for many people, and I don't understand your implicit criticism of it. The problem with the VAULT/DCACHE combination could lie with either program, and it is not necessarily due to one of the writers making "assumptions"---it could be due to a plain old ordinary unintentional bug: accidently overwriting memory not belonging to the program, using a signed int someplace instead of an unsigned, a problem with the compiler or a library routine, etc. -- ================================================== | Michael Fischer | ==================================================