This is the mail archive of the
cygwin
mailing list for the Cygwin project.
RE: non-interactive cygwin setup
- From: "Gary R. Van Sickle" <g dot r dot vansickle at worldnet dot att dot net>
- To: <cygwin at cygwin dot com>
- Date: Fri, 15 Oct 2004 22:16:28 -0500
- Subject: RE: non-interactive cygwin setup
> > 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/