Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!wuarchive!uwm.edu!ogicse!uidaho!ted.cs.uidaho.edu!hermens
From: hermens@ted.cs.uidaho.edu
Newsgroups: comp.sys.mac.apps
Subject: Re: Problems with SAM 2.0
Message-ID: <1991Apr08.022523.21152@groucho>
Date: 8 Apr 91 02:25:23 GMT
References: <369.27fc4f76@mbcl.rutgers.edu>
Sender: @groucho
Organization: University of Idaho
Lines: 26
Nntp-Posting-Host: ted.cs.uidaho.edu.101.129.in-addr.arpa


  I received updates for SAM 2.0 right up to the time that SAM 3.0 was
made available.  I have no complaints.  In fact, Mr. Cozza is reachable and
I have submitted information about SAM 2.0 to him.

Leonard

In article <369.27fc4f76@mbcl.rutgers.edu> friedman@mbcl.rutgers.edu writes:
>The lab I work in has owned SAM 2.0 for several months.  We have found that one
>of the problems with this program is the apparent haphazard manner by which
>updates are distributed.  Some friends have told me that they get cards with
>the information they need to update the Virus Clinic and SAM CDEV.  We only
>find out about the updates when we see a posting.  Apparently, the author, Paul
>Cozza, is unreachable as he has people who post messages for him.
>
>I would think (IMHO) that in addition to posting notices, which might be missed on the
>newsgroups, a more reliable alternative would be to place the info in various
>archives so that one might periodically check that they have kept their SAM's
>up to date.  
>
>Rich
>Friedman@mbcl.rutgers.edu
>
>PS The last virus I got new codes for was about 6 months ago.  If anyone could
>pass along the list of codes I might have missed, I would appreciate.
>Rich