Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!elroy.jpl.nasa.gov!ncar!asuvax!ukma!cs.widener.edu!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw
From: GB.SEC@Forsythe.Stanford.EDU (Info Security 3-9797)
Newsgroups: comp.virus
Subject: Virus vs. hardware failures
Message-ID: <0006.9103271735.AA27835@ubu.cert.sei.cmu.edu>
Date: 25 Mar 91 18:10:58 GMT
Sender: Virus Discussion List <VIRUS-L@LEHIIBM1>
Lines: 14
Approved: krvw@sei.cmu.edu

Eldar A. Musaev writes:

> I am very often disturbed by users who takes hardware failures for
> a virus....  What could we do to help users to distinct viruses
> and failures?

It has been my experience that it takes far less time to use your
favorite anti-virus software to first check if a virus is present.  If
there is no indication of a virus, then check for hardware and other
software kinds of problems.

Bill Bauriedel
Info. Security Office
Stanford Univ.