home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!yale.edu!jvnc.net!netnews.upenn.edu!netnews.cc.lehigh.edu!news
- From: frisk@complex.is (Fridrik Skulason)
- Newsgroups: comp.virus
- Subject: Re: Vshield vs Virstop (PC)
- Message-ID: <0014.9212221358.AA03720@barnabas.cert.org>
- Date: 22 Dec 92 00:24:47 GMT
- Sender: virus-l@lehigh.edu
- Lines: 13
- Approved: news@netnews.cc.lehigh.edu
-
- maven@kauri.vuw.ac.nz (Jim Baltaxe) writes:
-
- >Maybe this is being greedy, but would it be possible for you to put a
- >switch into VIRSTOP that would force it to use the Secure scan
- >mechanism?
-
- Possible, but difficult. The biggest problem is that VIRSTOP is written in
- 100% assembly, while the Secure scan is in a C/assembly mix. If I created
- a "Secure Scan" version of Virstop, I don't see how I could get the memory
- requirements below 30K. The 2K size (if using /DISK) is ok for most users,
- but 30K is a different story...
-
- - -frisk
-