Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!bloom-beacon!bu-cs!dartvax!eleazar.dartmouth.edu!jalden
From: jalden@eleazar.dartmouth.edu (Joshua M. Alden)
Newsgroups: comp.sys.mac
Subject: Re: GateKeeper <-> DiskFit
Message-ID: <12076@dartvax.Dartmouth.EDU>
Date: 3 Feb 89 15:16:11 GMT
References: <3472@bgsuvax.UUCP> <964@atux01.UUCP>
Sender: news@dartvax.Dartmouth.EDU
Reply-To: jalden@eleazar.dartmouth.edu (Joshua M. Alden)
Organization: Dartmouth College, Hanover, NH
Lines: 24

In article <964@atux01.UUCP> jlc@atux01.UUCP (J. Collymore) writes:
>In article <3472@bgsuvax.UUCP>, maner@bgsuvax.UUCP (Walter Maner) writes:
>> GateKeeper 1.0 interacts fatally with Network DiskFit 1.41 causing DiskFit to
>> think files are locked (error 45) when in fact they are not.  DiskFit does
>> not recover gracefully from this problem and may corrupt your save set in
>> the process of trying to recover.  So, set GateKeeper's override switch to
>> on before your backup.  Or, set up exceptions for DiskFit.  It is DiskFit's
>> use of PBSetCatInfo that causes GateKeeper to try to intervene.
>
>I'm not sure if this will help, but a few weeks ago I got an upgrade notice
>regarding Diskfit 1.5.  You may want to call the people out at SuperMac and
>ask them if this is a problem with DiskFit 1.5.

    I had this problem a few days ago.  I just made myself a DiskFit
disk without GateKeeper.  I keep the disk isolated and use it only when
I know that I'm working with something that's not infected, courtesy of
Interferon 3.0.  It's a little extra trouble to run Interferon, but not
much.
                                                      -Joshua Alden.

"And I - I have shown him ... that a man without hope ... is a man
   without fear"

             |Josh Alden:   jalden@eleazar.dartmouth.edu|