Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!unix.cis.pitt.edu!dsinc!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw
From: S72UZAW@TOE.TOWSON.EDU (Jan C. Zawadzki)
Newsgroups: comp.virus
Subject: Sunday V. in Turbo C 2.00: is false alarm possible? (PC)
Message-ID: <0002.9011281444.AA08768@ubu.cert.sei.cmu.edu>
Date: 26 Nov 90 22:28:00 GMT
Sender: Virus Discussion List <VIRUS-L@LEHIIBM1>
Lines: 24
Approved: krvw@sei.cmu.edu

Greetings...
        Can Turbo C 2.0 execs trigger a Sunday virus alarm?  I
re-installed TC from backups of the original disks, and Sunday virus
was reported (we scan *everything* that goes into our machines) on the
following:
        TC.EXE
        INSTALL.EXE
        GREP.COM [.exe? - I forget]
        UNPACK.COM
Curiously enough, the same was reported when I checked the *original*
disk set.  We have no history of an infection.  None of the
information on any of the machines is missing/damaged.  Are we
incredibly lucky, or does Turbo C trigger the warning?  Would someone
with an ORIGINAL copy of the disk set check?  I used SCAN v67 to
verify the infection, and the same files are reported as infected.  We
would greatly appreciate any help, at this point we are really not
sure what to do...

Jan

ps.  Borland is not aware of any such problems...
- ---
INet: yahn@midget.towson.edu
BNet: S72UZAW@TOWSONVX