Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!samsung!sdd.hp.com!usc!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw From: p1@arkham.wimsey.bc.ca (Rob Slade) Newsgroups: comp.virus Subject: Stoned in partition table (PC) Message-ID: <0006.9101281420.AA16983@ubu.cert.sei.cmu.edu> Date: 25 Jan 91 22:00:01 GMT Sender: Virus Discussion List Lines: 13 Approved: krvw@sei.cmu.edu brinkley@cs.utexas.edu (Paul Brinkley) writes: > the disk, and Stoned is still there. Someone at the lab suggested Did you boot from a clean system disk before you started all this effort? Stoned is resident in memory, and will, of course, re-infect your disk as soon as you have prepared it if you do not boot from a clean source first. I apologize if you *have* done this, but we are seeing repeated reports of this kind. FPROT deals very effectively with the Stoned variants that I have seen, and low level formats, re-partitioning and so forth are unnecessary extremes to go to.