Xref: news-dnh.mv.net comp.os.msdos.djgpp:1749
Path: news-dnh.mv.net!mv!news.NH.Destek.Net!news2.net99.net!news.cais.net!ringer.cs.utsa.edu!swrinde!news.uh.edu!uuneo.neosoft.com!news!sandmann
From: Charles Sandmann <sandmann AT praline DOT no DOT NeoSoft DOT com>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: djgpp2 and TBAV
Date: Fri, 25 Aug 1995 17:36:23 CDT
Organization: NeoSoft Internet Services +1 713 968 5800
Lines: 9
References: <DDvEG2 DOT 41u AT jade DOT mv DOT net> <mictaliDDvHxL DOT 84w AT netcom DOT com> <Pine DOT A32 DOT 3 DOT 91 DOT 950825122621 DOT 15802A-100000 AT srv1 DOT freenet DOT calgary DOT ab DOT ca>
Reply-To: sandmann AT clio DOT rice DOT edu
Nntp-Posting-Host: praline.no.neosoft.com
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

> yeah, but a lot of bbss use tbav as a heuristics scanner for incoming 
> uploads, so if djgpp2 programs always fail it, they will always be 
> rejected, so programmers using djgpp2 might have a hard time distributing 
> their programs through bbss.

If someone posts what the bug in TBAV is, maybe an alternate way of linking
can workaround the bug.  There is nothing virus-like in the stub to trigger
such a warning.  The source is available for the stub, so someone with this 
buggy scanner needs to find out what it doesn't like.