From:	"syco" <sycoweb AT chez DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Async COM managing
Date:	Fri, 22 Dec 2000 17:46:08 +0100
Organization:	sycoweb
Lines:	23
Message-ID:	<92005j$d2r$1@pollux.ip-plus.net>
References:	<91vcmd$3ap$1 AT pollux DOT ip-plus DOT net> <5137-Fri22Dec2000173842+0200-eliz AT is DOT elta DOT co DOT il>
NNTP-Posting-Host:	212.103.3.2
X-Trace:	pollux.ip-plus.net 977503219 13403 212.103.3.2 (22 Dec 2000 16:40:19 GMT)
X-Complaints-To:	news AT ip-plus DOT net
NNTP-Posting-Date:	22 Dec 2000 16:40:19 GMT
X-Newsreader:	Microsoft Outlook Express 4.72.2106.4
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.2106.4
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

>> How can I CLOSE ( and so release ) the com port used with bioscom() ?
>
>Is that on Windows?  If so, I'm afraid you'll need to exit the
>program.

Yes it is  :-(  ( Win95 ).
But even exiting my program, the port remains buzy.

> You could try initializing the port, but I'm not sure it
>will do what you want.
>
>Perhaps there's some Windows-wide setting that can make the COM port
>use be non-exclusive, but I don't know what that is.

I don't know if it exists. But I will search a little bit.

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 ?

Thanks.

- Raw text -