public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: interactive-services-detection not started on 32-bit cywin executables
Date: Thu, 16 Jan 2014 19:15:00 -0000	[thread overview]
Message-ID: <52D82F93.7030806@cygwin.com> (raw)
In-Reply-To: <CAO2ddna1LtPWHsjr1TfKCRxVMMeqd3JvMoFHG8VW-9J=qZTACg@mail.gmail.com>

On 1/16/2014 12:10 PM, BGINFO4X wrote:
> Hello everybody,
>
> I have a "Windows service implementation of cygwin" via NSSM
> (http://nssm.cc/). I use cygwin 1.7.27 32 bits.
>
> If I configure the service as "allow service to interact with
> desktop", the UIODETEC.exe is not started, so I can't see the console.
>
> Do you know why uiodetect is not started with 32-bit cygwin
> executables?

And now trying it with a simple test (the one suggested at your link below)
it worked for me if the window in which the shell runs is running as
administrator.  Did you try that?

<http://blogs.msdn.com/b/patricka/archive/2010/04/27/what-is-interactive-services-detection-and-why-is-it-blinking-at-me.aspx>

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

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

  parent reply	other threads:[~2014-01-16 19:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-16 17:10 BGINFO4X
2014-01-16 18:56 ` Larry Hall (Cygwin)
2014-01-16 19:15 ` Larry Hall (Cygwin) [this message]
2014-01-17 11:53 Fwd: " BGINFO4X
2014-01-17 12:08 ` BGINFO4X
2014-01-19 22:49   ` Larry Hall (Cygwin)
     [not found]     ` <CAO2ddnZQ4otrozE-BqKzLn66wyL6oE8uVHLUA7zjF3T52kwg7g@mail.gmail.com>
2014-01-21 17:21       ` BGINFO4X

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=52D82F93.7030806@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).