[comp.sys.amiga] VirusX_4.0 Problems

a186@mindlink.UUCP (Harvey Taylor) (12/08/89)

    Is anybody else getting gurus from VirusX_4.0?

   The first thing I ran into was that if I used the -k flag
 [check KickTagPntr], I got a requester that the KickTagPntr was set
 and should I clear it? This happened with the 3 finger salute, but
 not on cold boots. What is the difference, I wondered? RAD:? Sure
 enough, I disassembled the ramdrive.device and it messes around with
 the KickTagPntr. Okay, so I won't use the -k option. This might save
 you some grey hair.

   I do not think I have any virus. KV passes all my cC: & C2: files. I
 generally practice safe sex ;-). There have been no weird messages, no
 upside down screens, no unexplained disk accesses, no unexplained gurus.
   [Well you know what it's like when you're programming ;-)]

   But I have still been getting Gurus. On my system [B2000/2meg in
 8UP/ A2090A/no ECS], the Task Control Block for VirusX_4.0 was sitting
 at $20C730, and I got used to seeing that number over the last week.
 The Gurus were not caught by GOMF1.0. They were address errors;
 $00000003.x [and once an illegal instruction error].

    When I got a $20C730 Guru while I was online, I went back to 3.2...
 What is your experience?

 <-Harvey

 "The optimist thinks that this is the best of all possible worlds;
                          the pessimist knows it." -R.J.Oppenheimer
     Harvey Taylor      Meta Media Productions
      uunet!van-bc!rsoft!mindlink!Harvey_Taylor
              a186@mindlink.UUCP

a186@mindlink.UUCP (Harvey Taylor) (12/09/89)

In <10540@attctc.Dallas.TX.US>, davidg@attctc.Dallas.TX.US (David Gunter)
writes:
: From article <774@mindlink.UUCP>, by a186@mindlink.UUCP (Harvey Taylor):
: >
: >     Is anybody else getting gurus from VirusX_4.0?
: >
:    [We agree RAD: uses the KickTagPntr.]
:
: >    But I have still been getting Gurus.  [ ... ]
: >  The Gurus were not caught by GOMF1.0. They were address errors;
: >  $00000003.x [and once an illegal instruction error].
:
: GOMF1.0 is not completely efficient, so that doesn't surpries me,
: either. :-) Your best bet here is to go to the store and get GOMF3.0
: (is there a later version than this?).  You'd be amazed at the
: difference!

   Well yeah, but...
 there shouldn't be any gurus in the first place!

   I have had several other people report VirusX_4.0 gurus. So far, I
 have not figured out what the common factors are, if any.
   If you get VirusX_4.0 gurus, please describe your setup.

   <-Harvey

 "Always forgive your enemies; nothing annoys them so much." -Wilde
      Harvey Taylor      Meta Media Productions
       uunet!van-bc!rsoft!mindlink!Harvey_Taylor
               a186@mindlink.UUCP

davidg@attctc.Dallas.TX.US (David Guntner) (12/10/89)

From article <774@mindlink.UUCP>, by a186@mindlink.UUCP (Harvey Taylor):
> 
>     Is anybody else getting gurus from VirusX_4.0?
> 
>    The first thing I ran into was that if I used the -k flag
>  [check KickTagPntr], I got a requester that the KickTagPntr was set
>  and should I clear it? This happened with the 3 finger salute, but
>  not on cold boots. What is the difference, I wondered? RAD:? Sure
>  enough, I disassembled the ramdrive.device and it messes around with
>  the KickTagPntr. Okay, so I won't use the -k option. This might save
>  you some grey hair.

This was no surprise to me, since in the documentation for v3.2 he mentions
that he doesn't check the KickTagPntr for that very reason.  He finally added
it as an option (-k) since, alas, a virus can use it to hang around after
reboot (just like when it hooks into the ColdCapture, CoolCapture, or
WarmCapture vectors).  So if you use RAD:, you're best bet is to not use the
-k switch.  If you don't use RAD:, then by all means set it, since that will
eliminate one more way that a virus can hang around after reboot.
 
[stuff deleted]
 
>    But I have still been getting Gurus. On my system [B2000/2meg in
>  8UP/ A2090A/no ECS], the Task Control Block for VirusX_4.0 was sitting
>  at $20C730, and I got used to seeing that number over the last week.
>  The Gurus were not caught by GOMF1.0. They were address errors;
>  $00000003.x [and once an illegal instruction error].

GOMF1.0 is not completely efficient, so that doesn't surpries me, either. :-)
Your best bet here is to go to the store and get GOMF3.0 (is there a later
version than this?).  You'd be amazed at the difference!
 
>     When I got a $20C730 Guru while I was online, I went back to 3.2...
>  What is your experience?

I haven't had any visits from the Guru, by ever since I started using v4.0
of VirusX, my terminal program (I'm using JRComm v0.94a) hangs on me every
once in a while (usually at the WORST possible time... 8-]).
                        --Dave

-- 
        David Guntner  UUCP: {ames, mit-eddie}!attctc!davidg
                       INET: davidg@attctc.Dallas.TX.US  (killer)
"...New ship, but she's got the right name. ...Treat     --Admiral L. McCoy
 her like a lady, and she'll always bring you home."   "Encounter at Farpoint"

kim@uts.amdahl.com (Kim DeVaughn) (12/10/89)

In article <774@mindlink.UUCP>, a186@mindlink.UUCP (Harvey Taylor) writes:
> 
>     Is anybody else getting gurus from VirusX_4.0?
> 
>    The first thing I ran into was that if I used the -k flag
>  [check KickTagPntr], I got a requester that the KickTagPntr was set
>  and should I clear it?

Well, no Guru's.  But I get the KickTagPtr requester up using the -k flag
if setfont (and/or repfont) was in my s-s.  With them commented out, the
-k option seemed happy enough (no requester), even though rad: was always
getting mounted (though I did not try it with from a cold start, where rad:
would not have previously existed).

I've turned the -k option off, as I really cannot tolerate Topaz ...

/kim
-- 
UUCP:  kim@amdahl.amdahl.com
  or:  {sun,decwrl,hplabs,pyramid,uunet,oliveb,ames}!amdahl!kim
DDD:   408-746-8462
USPS:  Amdahl Corp.  M/S 249,  1250 E. Arques Av,  Sunnyvale, CA 94086
BIX:   kdevaughn     GEnie:   K.DEVAUGHN     CIS:   76535,25