Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!ames!ncar!gatech!bloom-beacon!oberon!sm.unisys.com!csun!solaria!ecphssrw@afws.csun.edu
From: ecphssrw@afws.csun.edu (Stephen Walton)
Newsgroups: comp.sys.amiga
Subject: VirusX 3.10/Blitzdisk Conflict
Summary: Don't put VirusX and BlitzDisk too close together on startup
Message-ID: <498@solaria.csun.edu>
Date: 24 Feb 89 19:02:31 GMT
Sender: ecphssrw@solaria.csun.edu
Reply-To: ecphssrw@afws.csun.edu (Stephen Walton)
Organization: California State Univ., Northridge
Lines: 15

I just spent almost two hours systematically tracking down why my
new, improved startup-sequence on my A2000 crashed the system.
The problem turned out to be VirusX 3.10 and BlitzDisk V2.0 being
too close together:  if they were, a subsequent LoadWB caused the
crash.  The order in which VirusX and BlitzDisk are loaded doesn't
matter;  a "Wait 10 Secs" between them seems to do the trick.
(This is with BlitzDisk and VirusX on an FFS partition.  Maybe a
floppy startup won't show the problem.)

I am reporting the problem to both Microsmiths and VirusX's author
via BIX and PeopleLink, respectively.  Meanwhile, beware.
--
Stephen Walton, Dept. of Physics & Astronomy, Cal State Univ. Northridge
RCKG01M@CALSTATE.BITNET       ecphssrw@afws.csun.edu
swalton@solar.stanford.edu    ...!csun!afws.csun.edu!ecphssrw