Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!nstn.ns.ca!news.cs.indiana.edu!widener!netnews.upenn.edu!vax1.cc.lehigh.edu!cert.sei.cmu.edu!krvw From: microsoft!c-rossgr@uunet.uu.net Newsgroups: comp.virus Subject: re: Product Test, Flu_Shot+ (PC) Message-ID: <0014.9105232038.AA03593@ubu.cert.sei.cmu.edu> Date: 23 May 91 16:38:42 GMT Sender: Virus Discussion List Lines: 31 Approved: krvw@sei.cmu.edu >From: Chris McDonald ASQNC-TWS-R-SO >. The commercial firm is now Microcom Software Division which >markets Virex-PC. While Mr. Greenberg actually sold Microcom Flu_Shot++, not >Flu_Shot+, I was somewhat surprised when version 1.81 reached the repository i n >December 1990. This version came bundled with a demonstration copy of the >viral scanning capability of Virex-PC. Subsequent electronic communications >with Mr. Greenberg suggest that Microcom may view continued releases of >Flu_Shot+ as a commonsense marketing strategy to migrate users to their >commercial product. Yeah, FLU_SHOT++ got renamed to Virex-PC. I happen to *still* like the name of FLU_SHOT++ more, but offer me enough money and... Chances are good that future releases of FLU_SHOT+ (You're falling behind, Chris: Version 1.82 is out the door) will *not* include the bundle of the VIRX scanner. Bundling them together meaks it difficult to release one without the other and can create some auditing nightmares. Additionally, looking at people downloading from my BBS, everybody seems to download both the FLU_SHOT+ archive (which contains VIRX) *and* VIRX. By unbundling, the download time will be lessened (important on pay services) and the ability to update each independently of the other is enhanced. Microcom's permission to allow me to continue to enhance and release FLU_SHOT+ is a credit to their marketplace acumen, I think. Ross