Message-Id:	<200410160316.i9G3GZn8025497@delorie.com>
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"Gary R. Van Sickle" <g DOT r DOT vansickle AT worldnet DOT att DOT net>
To:	<cygwin AT cygwin DOT com>
Subject:	RE: non-interactive cygwin setup
Date:	Fri, 15 Oct 2004 22:16:28 -0500
MIME-Version:	1.0
In-Reply-To:	<Pine.GSO.4.61.0410151109070.20921@slinky.cs.nyu.edu>
X-IsSubscribed:	yes

> > AllocConsole can only pop up a *new* console (right?),
> 
> Quoting MSDN 
> (<http://msdn.com/library/en-us/dllproc/base/allocconsole.asp>):
> 
>     A process can be associated with only one console, so the 
> AllocConsole
>     function fails if the calling process already has a 
> console. A process
>     can use the FreeConsole function to detach itself from its current
>     console, then it can call AllocConsole to create a new console or
>     AttachConsole to attach to another console.
> 
> So, basically, if there's another console, that console will be used.
> 

I should have added, "...in the context in question."  I though sure that
this was already tried, and whoever was doing it was unable to get a usable
console handle and eventually gave up.  What the problem may have been, or
even if I'm remembering correctly, I know not.

-- 
Gary R. Van Sickle
 


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -