From: "Syco" <sycoweb AT chez DOT com>
Newsgroups: comp.os.msdos.djgpp
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1001224081539 DOT 7747E-100000 AT is>
Subject: Re: Async COM managing
Lines: 44
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2014.211
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2014.211
Message-ID: <Rki16.4222$o77.12607499@nnrp1.proxad.net>
Date: Sun, 24 Dec 2000 08:20:01 GMT
NNTP-Posting-Host: 213.228.40.81
X-Complaints-To: abuse AT proxad DOT net
X-Trace: nnrp1.proxad.net 977646001 213.228.40.81 (Sun, 24 Dec 2000 09:20:01 MET)
NNTP-Posting-Date: Sun, 24 Dec 2000 09:20:01 MET
Organization: Guest of ProXad - France
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

I downloaded DZcomm just right now.
I will try ( in 2001 :-)  and will let you know the results.

Thanks you all.
Merry X. & Happy N.Y.

--
Syco
de Sycoweb
"Let me Alone ... But not Forever"
sur http://www.chez.com/sycoweb/puces/index.htm
ou http://www.multimania.com/sycoweb/puces/index.htm
Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> a écrit dans le message :
Pine DOT SUN DOT 3 DOT 91 DOT 1001224081539 DOT 7747E-100000 AT is...
>
> On Sat, 23 Dec 2000, Tim Nicholson wrote:
>
> > > Is it another way to obtain the expected result, without bioscom() ?
> > > Can I use another functions able to *OPEN* / init / send / receive /
> > *CLOSE*
> > > the com port and leave the things clean on exit ?
> >
> > I use a library called dzcomm which is an allegro add-on. It will allow
you
> > to access up to eight com ports and supports shared interrupts. You can
> > implicitly open and close ports at any speed that your UART chip
supports.
>
> The problem in this thread was that using a COM port from a DOS box would
> disallow other (DOS?) programs running on Windows from accessing the
> port.  Those other programs are not DJGPP programs and were certainly not
> written using DZComm.
>
> AFAIK, this is Windows' ``feature'': when a DOS program accesses a COM
> port, Windows makes it unavailable to other DOS boxes.  This seems to be
> Microsoft's way to ``virtualize'' the port.
>
> Are you saying that you tried this configuration, and DZComm somehow
> avoids the problem of making the COM port appear to be busy to other DOS
> boxes?  If so, the way to do that should be seen by studying the DZComm
> sources.
>