Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!pacbell.com!iggy.GW.Vitalink.COM!widener!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw
From: Michael_Kessler.Hum@mailgate.sfsu.edu
Newsgroups: comp.virus
Subject: F-Driver.SYS and QEMM (PC)
Message-ID: <0007.9105311330.AA00359@ubu.cert.sei.cmu.edu>
Date: 30 May 91 17:02:00 GMT
Sender: Virus Discussion List <VIRUS-L@LEHIIBM1>
Lines: 10
Approved: krvw@sei.cmu.edu

Yesterday I re-optimized my memory allocation on a Zenith 386-SX
because it had lost 2K of memory.  As it ran through the process, the
Stoned virus was detected, and the system froze, as it should have.
However, the station had been used on and off several times since its
infection, with no detection by f-driver.sys (ver 1.15A), and I
suspect that the reason for this is that it had been loaded into high
RAM by QEMM when running OPTIMIZE.  I do not recall reading anything
about this in the F-PROT documentation.

MKessler@HUM.SFSU.EDU