p1@arkham.wimsey.bc.ca (Rob Slade) (01/26/91)
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.