Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw From: aeshq!harry@uunet.UU.NET (Harry Pulley) Newsgroups: comp.virus Subject: Followup to my STONED problem (PC) Message-ID: <0006.9105301427.AA10625@ubu.cert.sei.cmu.edu> Date: 29 May 91 13:40:36 GMT Sender: Virus Discussion List Lines: 21 Approved: krvw@sei.cmu.edu Last night I used scanv72 on my floppy (the one that gave me the famous message in the first place). It was in the boot sector! I had heard that scanv76 was buggy, but I thought that STONED was an old enough virus that it would still be able to detect it. Oh well, a few hours were wasted scanning floppies with v76 -not a big loss. I will take home a copy of v77 today. N.B. this system was at home, not in a gov't building (we only run UNIX in my project, so I don't think we have the right to use scan/clean/etc...). Thanks for any replies, I'm still interested in the way that STONED works. [Ed. There's a great description (IMHO) of the Stoned virus available for anonymous FTP on cert.sei.cmu.edu. The file name is stoned.descript.lawrie and it is in the pub/virus-l/docs directory. The description was written by Mike Lawrie (ccml.rures@f4.n494.z5.fidonet.org) - Thanks Mike!] Harry.