Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!hc!pprg.unm.edu!unmvax!ncar!boulder!sunybcs!rutgers!mcnc!ecsvax!urjlew
From: urjlew@ecsvax.UUCP (Rostyk Lewyckyj)
Newsgroups: comp.sys.amiga
Subject: Re: Clock virus rumors
Summary: Yes But...
Message-ID: <6563@ecsvax.UUCP>
Date: 27 Feb 89 02:52:42 GMT
References: <36423@bbn.COM>
Organization: UNC Educational Computing Service
Lines: 12

In article <36423@bbn.COM>, denbeste@bbn.com (Steven Den Beste) writes
a lengthy explanation of why there can be no such thing as a virus
that hides in the NVM of a computer clock. But perhaps some of the
people using this term were thinking of a whatever virus whose effect
was to clobber the registers in the clock, or code used to access
the clock, as the mischief that they do. Rather than displaying a
cute message or erasing the disks. Fortunately so far all of these
suspicious cases have resolved themselves into inadvertant clobbering
of the clock registers by buggy applications problems, harware glitches,
or buggy clock maintenance programs.
But who knows, tomorrow we may find that indeed some wierdo has released
just such a clock eating virus. Why??   Why indeed.