Message-Id: <200410160316.i9G3GZn8025497@delorie.com> Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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" To: Subject: RE: non-interactive cygwin setup Date: Fri, 15 Oct 2004 22:16:28 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit In-Reply-To: X-IsSubscribed: yes > > AllocConsole can only pop up a *new* console (right?), > > Quoting MSDN > (): > > 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/