Newsgroups: comp.sys.mac.system
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!think.com!linus!linus!mwunix.mitre.org!jblue
From: jblue@mwunix.mitre.org (Jason D. Blue)
Subject: Re: Virex 3.2 and System 7
Message-ID: <jblue.676729717@mwunix.mitre.org>
Sender: news@linus.mitre.org (News Service)
Nntp-Posting-Host: mwunix.mitre.org
Organization: The MITRE Corporation, Bedford MA
References: <1991Jun12.084640.5226@massey.ac.nz>
Date: 12 Jun 91 12:28:37 GMT

news@massey.ac.nz (USENET News System) writes:

>Then a while later when I wanted to print a file on a laserwriter, no joy.
>Virex 3.2 init appears to stop laserprinting on system 7.0! I didn't believe
>this for a start, so I tried it on several other machines around campus using
>system 7 (we were all using IIci's), and the same problem.

Al,

Virex INIT 3.2 is not system 7 compatible.  Version 3.5 (accourding to the 
compatibility chart) will be compatible, and will be out soon, I hope.
I talked to Microcom, and they said approximatly 4-8 weeks.

The application works fine, as does any version of the application.

I encountered the printing problem back when I was using the Beta copy of
7, and notified Microcom of it.  Usually I would encounter a system bomb or
freeze when I tried printing using PrintMonitor and VirexINIT loaded.

The problem itself is with Virex INIT's option to scan files when opened.
If you disable this option, you should be OK.  I was also told that this
option under System 7 might not detect viruses.

Jason
The MITRE Corporation