From: Bill Currie <bcurrie AT tssc DOT co DOT nz>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Serial port access problem
Date: Thu, 19 Feb 1998 07:57:24 +1300
Organization: Telecommunication Systems Support Centre
Lines: 28
Message-ID: <34EB2F14.1DD6@tssc.co.nz>
References: <34E9C315 DOT 33BC AT bright DOT net> <34eebd2e DOT 22635036 AT news DOT magna DOT com DOT au>
NNTP-Posting-Host: node106.tssc.co.nz
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Andrew Cottrell wrote:
> 
> Rather than writing your own serial comms code you should check out
> the three serial comms packages and choose the best one for your
> application. The three applications are:
>         1) BCSERIO, Filename: BCSIO20.ZIP in the V2TK directory. Last
> I seen this still has an obscure bug. (I can't remember if this has
> been fixed.)

They've been fixed (there were two bugs, one cause a stack trace, the
other I think just didn't work, can't remember, but they were both in
functions I don't use myself), I just haven't got around to releasing it
yet :(  Part of the problem is I haven't had time to properly test the
fixes (the coredump stopped, but I don't know if the code works as
intended yet).

I've been giving out the latest version on request
(bill AT taniwha DOT tssc DOT co DOT nz), but I intend on releasing the next version
soon

> The other advantage of using an off the shelf packages is that they
> are easy to use and they work!!!!!

Thanks :)

Bill
-- 
Leave others their otherness