hrlaser@sactoh0.UUCP (Harv R. Laser) (12/18/89)
There've been some complaints posted concerning Steve Tibbett's newly- released VirusX 4.0 and I've been passing them to Steve via Plink email 'cuz he doesn't have net access. Here is his reply to those who have voiced problems:: QUOTE Could you drop this onto Usenet for me, Harv: VirusX 4.0 has one problem, that has been causing all the other ones that people have been reporting. VirusX 4.0 will, as part of its checking RAM continually for your running an infected executable, mistakenly use location $0 as a pointer. Normally location 0 is NULL anyway, so it doesn't make any difference... but it seems that some programs mistakenly write to location 0 (Null pointers and such), and just writing #1 to location 0 (as a long) will make it odd... causing VirusX to generate an address error. Apparently some versions of Commodore's A590 hard disk driver do this, and I've heard HardFrame does also, though haven't verified it. I'll try and take care of this problem in the next version of VirusX. Also, for V4.0, I changed the WAY I check disks to see if they are viruses I recognize - I changed which longwords of the bootblock I look at, for no real reason other than that it was easier to do it this way. Anyway, VirusX 4.0 recognizes MY copy of all the viruses that people have been saying 3.2 recognizes but 4.0 doesn't (Lamer Exterminator of some form, and one of the SCA variants). If you have a bootblock that 3.2 recognized and 4.0 doesn't, Please get it to me somehow: Plink=STEVEX, Bix=s.tibbett, my BBS (613-731-3419), etc.). Thanks, Harv... This should calm them down. 8-) ...Steve END OF QUOTE -- Harv Laser | SAC-UNIX, Sacramento, Ca. People/Link: CBM*HARV | UUCP=...pacbell!sactoh0!hrlaser