From:	Greg Thomas <thomasgd AT omc DOT bt DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Async COM managing
Date:	Wed, 27 Dec 2000 12:57:06 +0000
Organization:	BT Adastral Park, Martlesham Heath, Ipswich, UK
Lines:	17
Message-ID:	<ulpj4t8sl7hompsqcl9vetbosms6754jek@4ax.com>
References:	<75gj4ts9d0t4a2eu5r565h8uocrctb5vnu AT 4ax DOT com> <Pine DOT SUN DOT 3 DOT 91 DOT 1001227141432 DOT 10199C AT is>
NNTP-Posting-Host:	bt772568.btlabs.bt.co.uk
Mime-Version:	1.0
X-Trace:	pheidippides.axion.bt.co.uk 977921935 23445 132.146.59.26 (27 Dec 2000 12:58:55 GMT)
X-Complaints-To:	postmaster AT axion DOT bt DOT co DOT uk
NNTP-Posting-Date:	27 Dec 2000 12:58:55 GMT
X-Newsreader:	Forte Agent 1.8/32.548
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

On Wed, 27 Dec 2000 14:16:07 +0200 (IST), Eli Zaretskii
<eliz AT is DOT elta DOT co DOT il> wrote in article
<Pine DOT SUN DOT 3 DOT 91 DOT 1001227141432 DOT 10199C AT is>:

>No, I don't think so.  You need to say "start myprog.exe", to make 
>myprog.exe run in a different DOS box.  Then, when myprog.exe exits, its
>DOS box will close, and the COM port should be freed.

On reflection, I agree. It is Windows handling the locking of the
port, not command.com - I was getting hung up with a
mis-interpretation of "When command.com exits the DOS session ends and
the port is deallocated."

Greg
-- 
This post represents the views of the author and does
not necessarily accurately represent the views of BT.

- Raw text -