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 10:18:17 +0000
Organization:	BT Adastral Park, Martlesham Heath, Ipswich, UK
Lines:	33
Message-ID:	<75gj4ts9d0t4a2eu5r565h8uocrctb5vnu@4ax.com>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1001224081539 DOT 7747E-100000 AT is> <9250eb$a84$00$1 AT news DOT t-online DOT com>
NNTP-Posting-Host:	bt772568.btlabs.bt.co.uk
Mime-Version:	1.0
X-Trace:	pheidippides.axion.bt.co.uk 977912406 21437 132.146.59.26 (27 Dec 2000 10:20:06 GMT)
X-Complaints-To:	postmaster AT axion DOT bt DOT co DOT uk
NNTP-Posting-Date:	27 Dec 2000 10:20:06 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 Sun, 24 Dec 2000 15:18:09 +0100, "Peter Remmers"
<Peter DOT Remmers AT t-online DOT de> wrote in article
<9250eb$a84$00$1 AT news DOT t-online DOT com>:

>So the port stays blocked for all other DOS AND Windows applications
>for the life of the DOS box that uses/used the port.
...
>In the case of the  DOS session "command.com" is the program that uses the
>port. When command.com exits the DOS session ends and the port is deallocated.

In that case, would a DOS command along the lines of ...

command.com /C myprog.exe

or perhaps 

%COMSPEC% /C myprog.exe

work? This runs up a new command.com, that session of command.com runs
myprog.exe and then exits, hopefully freeing up the COM port) get
around the problem? It might need an extra .bat file to contain this
info, but if it works it looks like a simple workaround to the
limitations of DOS.

Of course, the port is still locked for the lifetime of myprog.exe,
but this may be better than for the lifetime of the DOS box.

HTH,

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

- Raw text -