Return-Path: XPUM04@prime-a.central-services.umist.ac.uk
Received: from G.SEI.CMU.EDU by ubu.cert.sei.cmu.edu (5.61/2.3)
        id AA03521; Tue, 19 Jun 90 07:21:24 -0400
Received: from SEI.CMU.EDU by g.sei.cmu.edu (5.61/2.5)
        id AA28599; Tue, 19 Jun 90 07:21:21 -0400
Received: from nsfnet-relay.ac.uk by sei.cmu.edu (5.61/2.3)
        id AA01632; Tue, 19 Jun 90 07:21:16 -0400
Received: from sun.nsfnet-relay.ac.uk by vax.NSFnet-Relay.AC.UK 
           via Janet with NIFTP  id aa05233; 19 Jun 90 9:38 BST
From: Anthony Appleyard <XPUM04@prime-a.central-services.umist.ac.uk>
To: DAVIDF@cs.heriot-watt.ac.uk
Date:         Tue, 19 Jun 90 09:42:24 BST 
Message-Id:   <$TGWFCWKBBCVN at UMPA>
Subject:      Here is Virus-L vol 0 #0922



Virus-L Digest Thu, 22 Sep 88, Volume 0 : Issue #0922

Today's Topics

Viruses and media
Time article bashes the media...
HDSENTRY.ARC

------------------------------

Date:         Thu, 22 Sep 88 00:27:00 EST
From:         Dimitri Vulis <DLV@CUNYVMS1>
Subject:      Viruses and media

In one of the first paragraphs, the TIME story describes the user struck by
a virus seeking through all 360 concentric circles  of  data  on  the  disk
(very  near  quotation  from  memory).  Apparently,  the  writer confused a
kilobyte (as in 360K) with a track (as in 96tpi). Also today, NY times  ran
a  story  (discussed  here  previously) about a guy convicted of planting a
time bomb, except it called it a virus. This is actually an  AP  story,  so
it's  mpt surprising: AP style manual has a section called 'computer terms'
which defined 'disk operating system' as a collection  of  disks  and  disk
drives  to  read  them.  However,  I'd  expect that Time magazine would let
someone who knows the difference between a track and a Kbyte read the story
before printing it. I think it's highly irresponsible on the  part  of  the
media  to  write  about  things  they  don't  understand and to confuse the
public. Explaining the need for  security  to  the  users  is  hard  enough
without it.

Dimitri Vulis, CUNY Math Department

P.S. My wife and I wrote a letter to AP about their  Style  manual  listing
something  like 50 inaccuracies in the computer section, most of them quite
funny; I can email a copy to interested parties,  although  it  has  little
direct bearing on the virus topic.

--------------------

Date:         Thu, 22 Sep 88 09:21:38 EDT
From:         Ken van Wyk <luken@SPOT.CC.LEHIGH.EDU>
Subject:      Time article bashes the media...

The cover story in the September 26, 1988, seems to be  pretty  interesting
reading  for the most part. Most of the facts are clearly stated, albeit in
flashy jargon. At times, the jargon seems to border on sensationization, in
my opinion. They do, however, go on to bash the media for its  coverage  of
viruses by saying, "... On the other is the computer press, a collection of
highly  competitive  weekly tabloids that have seized on the story like pit
bulls, covering every outbreak with breathless copy and splashy headlines."
I thought this was amusing...

Ken

Kenneth R. van Wyk                   Calvin: Here, try this new cereal,
User Services Senior Consultant         Chocolate Frosted Sugar Bombs.
Lehigh University Computing Center   Hobbes: Gack!  Ptui!  :-(
Internet: <luken@Spot.CC.Lehigh.EDU> Calvin: Yeah, they're a bit bland until
BITNET:   <LUKEN@LEHIIBM1>              you scoop some sugar on them.

--------------------

Date:         Thu, 22 Sep 88 23:11:05 CST
From:         James Ford <JFORD1@UA1VM>
Subject:      HDSENTRY.ARC

Hello again. A while (ok, a GREAT while) back I asked if  anyone  had  ever
used  HDSENTRY.COM.  I  had  been  used it once, with some strange effects.

>First off, I'm using an IBM PS/2 M30 w/20M h-drive.  I backed up my harddisk
>and then ran the program.  I changed into a subdirectory and did a DEL *.*
>on it. The program gave the warning <<ALERT>> DESTRUCTIVE CALL BEING PREVENTED
>and didn't allow it.  Well, when I did a directory, it showed nothing.  BUT,
>after doing a warm boot, all files reappeared and ran fine.

After posting the above note, I asked if anyone would like to look  at  the
ASM  file  on  it to (maybe) try and correct the above problem. A couple of
people answered, but I couldn't locate the file.  NOW,  I  have  the  file.
Anyone  interested  in  doing a little debugging? I would, but I don't know
anything about assembly. James

--------------------

*** end of Virus-L issue ***
