Conference hydra::amiga_v1

4260.0. "VirusX 4.01 Corupts DF2: Floppies" by CSC32::A_ANDERSON (DTN 592-4170 NSU/VAX) Sun Nov 11 1990 20:01

    Just to be on the safe side I down loaded the latest version of VirusX 
    from Tape:: the other day.   This is the first time I consitantly tried
    to  keep a Anti Viral program running.  I started to suffer serious
    disk problems with my external drive.  This is a 5 1/4 inch drive
    (DF2:) with a 3.5 inch latch circuit.  The internal 3.5 inch drive
    (DF0:) did not have any problems.  I did seem to have a few errors but 
    not the consistant data corruption I got on the 5 1/4 inch drive.  

    I am running a Amiga 2000, rev 6.2, Amiga Dos 1.3.2, VirusX 4.01. 68020 
    and ICD SCSI Host and ProRamm memory module with 4MB, and Xt-Bridge Board.  

    The problem was that writting to the disk would corrupt blocks 880 through 
    890.  They would end up with errors 23 and or errors 25.  The disk was no 
    longer mountable and had to be reformatted.  Maurauder did not have any 
    trouble so it appears to me to be an interaction with VirusX and the
    driver.  I believe Marauder bypasses the driver and does direct
    read's/write's to the drive.

    On one floppy the corruption was so sever that my Amiga Guru'ed during the 
    copy.  Also it would Guru when I tried to insert that floppy and let it 
    mount (8700000B.265F48F1).  Which translates to a Dead end Alert for
    the Dos.Library Key Out of Range error.  I had to degauss the diskette 
    then reinitialize it.

    I tried just a bare bones system.  No StartUp-Sequence (no Patches) the 
    default CLI window and LoadWB and VirusX as the only two running
    programs.  As soon as the copy got to the middle of the diskette it
    started to log disk errors.  From then on the disk was unreadable. 
    Reading the disk was not affected (prior to the corruption), formating
    also worked ok.

    Blocks 880 through 890 = Head 0 track 40.

    After killing VirusX everything is back to normal, I am on my forth backup 
    floppy while writing this with zero disk errors.

    I can not see what the 5 1/4 inch has to do with it.  Has anyone seen a 
    simular problem with VirusX 4.01 and a standard 3.5 inch drive as DF2:?  
    The only other thing is my system is one of those that VirusX always
    complains about the  CoolCapture vector if I use the SetPatch r,
    VirusX -r did not fix this either.  I do not know what the two problems 
    have in common, just thought I would throw it in as a possible clue/symptom.

    Any Ideas?

    I am assuming that the VirusX401.lzh on TAPE:: is a valid Anti Virus
    Program and not a Trojan Horse.  But it is a possiblily we need to
    investigate.

    Alan
    

    I have a different problem with VirusX V4.01. It appears to be
    incompatible with Quarterback V4.0. QB crashes when the first floppy is
    inserted. With VirusX V4.0 I have no such problem.
    
    -Paul

    VirusX 4.00 does not seem to have the DF2: Corruption problem.  I think
    I will stick with that version.