X-Recipient: archive-cygwin AT delorie DOT com X-Spam-Check-By: sourceware.org Date: Sun, 28 Jun 2009 12:30:10 +0200 From: Corinna Vinschen To: cygwin AT cygwin DOT com Subject: Re: popup consoles on Windows 7 Message-ID: <20090628103010.GT30864@calimero.vinschen.de> Reply-To: cygwin AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com References: <20090626083640 DOT GF30864 AT calimero DOT vinschen DOT de> <416096c60906260239r5bdaf60bw6a9febe885726f55 AT mail DOT gmail DOT com> <20090626102313 DOT GA12963 AT calimero DOT vinschen DOT de> <416096c60906260503o52ae73ben1140bbbd2db993bb AT mail DOT gmail DOT com> <20090626121215 DOT GJ30864 AT calimero DOT vinschen DOT de> <416096c60906260541t56687113p9c940d4251f68405 AT mail DOT gmail DOT com> <20090626133618 DOT GA14187 AT calimero DOT vinschen DOT de> <20090626145213 DOT GK30864 AT calimero DOT vinschen DOT de> <416096c60906270139y33e2888cq148430eebb744b71 AT mail DOT gmail DOT com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <416096c60906270139y33e2888cq148430eebb744b71@mail.gmail.com> User-Agent: Mutt/1.5.19 (2009-02-20) Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: 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 On Jun 27 09:39, Andy Koppe wrote: > 2009/6/26 Corinna Vinschen: > > On Jun 26 15:08, Julio Costa wrote: > >> I've been following this discussion, crossing fingers to someone came > >> to some conclusion, as this is the biggest show-stopper for Cygwin in > >> several months. > >> > >> I've not access to a Win 7, but I would like at least to drop some > >> ideas to someone with more insight comment on and (hopefully) come to > >> a solution. > >> > >> 1) If we make a service (let's call it cygconsole, or include it in > >> cygserver, whatever), with no desktop interaction, whose only purpose > >> is to AllocConsole()... > >> 1.a) do that console gets created? > >> 1.b) Is it invisible? > >> > >> 2) IF the two answers are true, then > >> 2.a) Do an arbitary process can do an attachconsole to the PID of that service? > >> > >> IF it is also an YES, we have a framework for an > >> workaround/alternative implementation! Cool? > > > > It's an interesting idea, but rather tricky to implement.  I assume > > you will get an ERROR_ACCESS_DENIED when trying to attach to a console > > of another user, and a cygserver service would usually run under SYSTEM. > > Relying on a service at all doesn't sound overly tempting, either.  I'm > > still hoping for another solution. > > How about implementing this idea solely in the Cygwin DLL rather than > through a service, i.e. the first process that needs a hidden console > allocates one, and any subsequent processes attach to that. > > Only problem is that the console is automatically freed once all > processes using it have finished, so a new one would have to be > allocated again when another process comes along that needs one. Yeah, that could be an option as a per-session workaround if there's no other way to accomplish it. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple