home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!ukma!darwin.sura.net!jvnc.net!netnews.upenn.edu!netnews.cc.lehigh.edu!news
- From: gary@sci34hub.sci.com (Gary Heston)
- Newsgroups: comp.virus
- Subject: Re: Checking high memory with VSCAN (PC)
- Message-ID: <0009.9211091912.AA05064@barnabas.cert.org>
- Date: 2 Nov 92 20:26:45 GMT
- Sender: virus-l@lehigh.edu
- Lines: 20
- Approved: news@netnews.cc.lehigh.edu
-
- ianst@qdpii.comp.qdpi.oz.au (Ian Staples) writes:
-
- [ about a discussion concerning potential high memory viruses ]
-
- >Hmmm... does this imply that once we all have OS/2 or whatever on 386s
- >or better, and 32-bit applications addressing oceans of flat memory
- >space then we will have to wait forever for SCAN or some other to scan
- >the whole bloody lot when we boot up each morning?
-
- No. During boot, you'd simply install Virscan as your first step, and
- let it trap anything that attempts to load while infected.
-
- On booting, the memory contents are ignored and overwritten, so there's
- no need to scan it.
-
- - --
- Gary Heston SCI Systems, Inc. gary@sci34hub.sci.com site admin
- The Chairman of the Board and the CFO speak for SCI. I'm neither.
- "...I looked out my window, and saw Kyle Pettys' car upside down, then I
- thought 'One of us is in real trouble'." Davey Allison, re: a 150MPH crash
-