Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uunet!lll-winken!iggy.GW.Vitalink.COM!widener!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw
From: microsoft!c-rossgr@uunet.uu.net
Newsgroups: comp.virus
Subject: re: F-PROT and FluShot problems
Message-ID: <0007.9105071330.AA00939@ubu.cert.sei.cmu.edu>
Date: 6 May 91 19:23:53 GMT
Sender: Virus Discussion List <VIRUS-L@LEHIIBM1>
Lines: 21
Approved: krvw@sei.cmu.edu

>Date:    Fri, 03 May 91 17:10:20 +0000
>From:    umbc3!umbc3.umbc.edu!cs106132@uunet.UU.NET (cs106132)
>
>....  It happened when a variant of 4096 was active.
>...., the virus infected the system files (IBMBIO....), the result
>was a non-bootable hard disk.  This indicates [it] can actually
>contribute to the spread of this kind of viruses.  This is not a bug
>type of thing, it is a design flaw!
>   I repeated the same test using FluShot+ (1.81), the same thing
>happened in a slightly different manner.  But the system again became
>impossible to boot from the hard disk.  I had to run SYS C: to restore
>the sanity of the system.  Any comments?

Obviously I have a comment! :-)

Please let me know more about this varient on 4096 and I'll fix it up
in the next release of FLU_SHOT+ (Current release, by the way, is
version 1.82, released 4/7/91...next release is due out shortly).

Ross M. Greenberg
 Author, FLU_SHOT+ & Virex-PC