Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/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
Date:	Fri, 11 Oct 2002 19:52:24 -0400
From:	Christopher Faylor <cgf AT redhat DOT com>
To:	cygwin AT cygwin DOT com
Subject:	Re: "Application failed to initialize (0xc0000022)"
Message-ID:	<20021011235224.GC21033@redhat.com>
Reply-To:	cygwin AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
References:	<20021011180345 DOT GA1488 AT tishler DOT net> <GBEGLOMMCLDACBPKDIHFGEPJCLAA DOT gsw AT agere DOT com>
Mime-Version:	1.0
In-Reply-To:	<GBEGLOMMCLDACBPKDIHFGEPJCLAA.gsw@agere.com>
User-Agent:	Mutt/1.4i

On Fri, Oct 11, 2002 at 05:40:25PM -0400, Gerald S. Williams wrote:
>Jason Tishler wrote:
>> > Is it possible that this is an aspect of the dreaded "rebase" issue?
>> 
>> I don't think so.  If it was, then you would have experienced fork()
>> failures with messages (not dialogs) like the following:
>
>That was my initial impression also. But what could
>cause that error? Given its nature, I'd be really
>surprised if nobody else had run into it.

It's usually caused by the use of CYGWIN=ntsec and cygwin1.dll not having
executable permissions, I believe.  It's showed up here from time to time.

So, doing something like:

c:\>set CYGWIN=ntsec
c:\>chmod a+rx /bin/*

may help.

cgf
--
Please do not send me personal email with cygwin questions.
Use the resources at http://cygwin.com/ .

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -