🚀 go-pugleaf

In article <847@rex.cs.tulane.edu> cleeland@rex.UUCP (Chris Cleeland) writes:
.
.I think that what probably happened is that the first time that you ran
.Interferon, it got infected (this happened to me once when I forgot -- God
.what a mess!).  So, Disinfectant did its deed, and cleaned things up.  Then,
.when you ran Interferon again, the System got infected again.
.
.The reason that Disinfectant doesn't get infected is b/c each time it is
.launched, it performs a check upon itself and disinfects if necessary.  Then
.it goes on with its other business (disinfecting your disks).
.
.Maybe you should try running Disinfectant on your copy of Interferon...
.
>Chris Cleeland, Tulane University

Sorry if my message was unclear the first time...I  *didn't* run interferon
prior to running disinfectant.  I scanned with disinfectant 1.1, found
system, finder, and several applications dirty (nVIR.a), disinfected with
disinfectant, ran disinfectant again which claimed everything was clean,
then ran a *reliably clean* interferon which claimed system was still dirty.

I didn't take any chances...I threw system away.


		    UCLA Computer Science Department
   -- Larry         3413 Boelter Hall   Los Angeles 90024  (213) 825-2145
	 Prince     UUCP:    {ucbvax,sdcrdcf}!ucla-cs!prince
		    ARPAnet:  prince@CS.UCLA.EDU