jd21@prism.gatech.EDU (DEMMERS,JAMES L) (02/01/90)
A friend of mine has just purchased an Amiga 2500 and has included the Virusx
software in his startup sequence. His problem is that whenever he boots the
system, an error message appears that states: "cold capture vector is not set
to 0" and something else about a virus maybe present in RAM. Has anyone out
there had any similar experience with this software on a 2500 (or other
machine)?
Thanks in advance.
--
DEMMERS,JAMES L
Georgia Institute of Technology, Atlanta Georgia, 30332
uucp: ...!{decvax,hplabs,ncar,purdue,rutgers}!gatech!prism!jd21
Internet: jd21@prism.gatech.edues1@cunixb.cc.columbia.edu (Ethan Solomita) (02/02/90)
In article <5550@hydra.gatech.EDU> jd21@prism.gatech.EDU (DEMMERS,JAMES L) writes: >A friend of mine has just purchased an Amiga 2500 and has included the Virusx >software in his startup sequence. His problem is that whenever he boots the >system, an error message appears that states: "cold capture vector is not set >to 0" and something else about a virus maybe present in RAM. Has anyone out >there had any similar experience with this software on a 2500 (or other >machine)? VirusX and SetPatch conflict. If SetPatch is run with option set for the fatter Agnus (which I assume it is) VirusX for some reason thinks there may be a virus. Obviously there isn't. If you run virusx at the beginning of your startup-sequence, which you should anyway, there won't be a problem. -- Ethan
hrlaser@gryphon.COM (Harv Laser) (02/04/90)
In article <2769@cunixc.cc.columbia.edu>, es1@cunixb.cc.columbia.edu (Ethan Solomita) writes: > VirusX and SetPatch conflict. If SetPatch is run with option > set for the fatter Agnus (which I assume it is) VirusX for some reason > thinks there may be a virus. Obviously there isn't. If you run virusx > at the beginning of your startup-sequence, which you should anyway, > there won't be a problem. > -- Ethan VirusX 4.0 has a "-r" option. Run your "SetPatch r" at the TOP of your startup-seq like the gods intended :-) and then "Virusx -r" after that and there'll be no clash and VirusX will stop bitching at you. Works fine on *my* A2500. -- Harv Laser People/Link: CBM*HARV hrlaser@gryphon.COM <routing site>!gryphon!hrlaser gryphon!hrlaser@elroy.jpl.nasa.gov
bear@bu-pub.bu.edu (Blair M. Burtan) (02/06/90)
>>>>> On 1 Feb 90 21:00:28 GMT, es1@cunixb.cc.columbia.edu (Ethan Solomita) said: >> In article <5550@hydra.gatech.EDU> jd21@prism.gatech.EDU (DEMMERS,JAMES L) writes: >A friend of mine has just purchased an Amiga 2500 and has included the Virusx >software in his startup sequence. His problem is that whenever he boots the >system, an error message appears that states: "cold capture vector is not set >to 0" and something else about a virus maybe present in RAM. Has anyone out >there had any similar experience with this software on a 2500 (or other >machine)? >> VirusX and SetPatch conflict. If SetPatch is run with option >> set for the fatter Agnus (which I assume it is) VirusX for some reason >> thinks there may be a virus. Obviously there isn't. If you run virusx >> at the beginning of your startup-sequence, which you should anyway, >> there won't be a problem. >> -- Ethan I had the same problem. This has something to do with chip ram I think. The lastest version of VirusX (4.0) has a parameter -r that fixes this problem. -- --------------------------- Signature Version 1.0 --------------------------- | bear@bu-pub.bu.edu enge05c@buacca.bu.edu | | "There are many perks in being the mother of a living god. | | Nice apartment, car, free parking." | -----------------------------------------------------------------------------
joe@cbmvax.commodore.com (Joe O'Hara - PA) (02/07/90)
In article <BEAR.90Feb6091703@bass.bu.edu> bear@bu-pub.bu.edu (Blair M. Burtan) writes: >>>>>> On 1 Feb 90 21:00:28 GMT, es1@cunixb.cc.columbia.edu (Ethan Solomita) said: > >>> In article <5550@hydra.gatech.EDU> jd21@prism.gatech.EDU (DEMMERS,JAMES L) writes: >>A friend of mine has just purchased an Amiga 2500 and has included the Virusx >>software in his startup sequence. His problem is that whenever he boots the >>system, an error message appears that states: "cold capture vector is not set >>to 0" and something else about a virus maybe present in RAM. Has anyone out >>there had any similar experience with this software on a 2500 (or other >>machine)? > >>> VirusX and SetPatch conflict. If SetPatch is run with option >>> set for the fatter Agnus (which I assume it is) VirusX for some reason >>> thinks there may be a virus. Obviously there isn't. If you run virusx >>> at the beginning of your startup-sequence, which you should anyway, >>> there won't be a problem. >>> -- Ethan > >I had the same problem. This has something to do with chip ram I think. >The lastest version of VirusX (4.0) has a parameter -r that fixes >this problem. The "r" option of Setpatch redirects the vector so that RAD: remains intact on rebooting with 1Meg Agnus. Users who don't use rad: can edit their startup sequence to eliminate the r option from the setpatch command. Earlier versions of VirusX will then be happy. -- ========================================================================== Joe O'Hara || Disclaimer: I didn't say that! Commodore Electronics Ltd || Product Assurance || "I never lie when I have sand in my shoes." Systems Evaluation Group || - Geordi LeForge, Star Trek TNG ==========================================================================