Date: Wed, 27 Dec 2000 14:16:07 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Greg Thomas <thomasgd AT omc DOT bt DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Async COM managing
In-Reply-To: <75gj4ts9d0t4a2eu5r565h8uocrctb5vnu@4ax.com>
Message-ID: <Pine.SUN.3.91.1001227141432.10199C@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 27 Dec 2000, Greg Thomas wrote:

> >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?

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.