Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <C9A8E1D07093D111B76A0000F8C9918A03E146CE@zrtpd003.us.nortel.com>
From: "Christopher Jones" <cbjones AT nortelnetworks DOT com>
To: cygwin AT sourceware DOT cygnus DOT com
Subject: RE: runtime failure in 20000710 and 20000711 snapshots
Date: Thu, 13 Jul 2000 11:23:40 -0400
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: multipart/alternative;
              boundary="----_=_NextPart_001_01BFECDE.51A69630"

------_=_NextPart_001_01BFECDE.51A69630
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

> Charles Wilson wrote:
> >=20
> > This should probably go to cygwin-developers, but I don't think
> > non-subscribers can post there. Anyway, I'm getting a popup=20
> window that
> > reads:
> >=20
> > The application failed to initialize properly (0xc0000022).=20
> Click on OK
> > to terminate the application.
> > [...]
> > Or is there something wrong with my configuration that is=20
> foobaring the
> > newer dll's?
>=20
> No, there's something wrong with the tarball. I have just downloaded
> and I have seen the following entry:
>=20
> -rw-r--r-- dj/games   627200 2000-07-12 21:11:23 usr/bin/cygwin1.dll
>=20
> You will notice that the executable bits aren't set. This results
> in unset executable bits in the ACL when ntsec is ON. You can
> solve that by using `chmod +x=B4 on that dll.
>=20
> Unfortunately a DLL must have executable bit set in the ACL to be
> runtime loadable by NT/W2K.

I have a recent snapshot (07/08) so I took a look at this and indeed =
the
execute bit does not show up for any of the .dll files in usr/bin/.  In =
my
case I explicitly set nontsec in the CYGWIN variable and some =
applications
are working while others are not.  I've tried using chmod +x on those =
dlls
without affect.  The bits still remain rw-r--r--... this is on a FAT
partition under NT 4.0 with binary mounts.  Is chmod supposed to do =
anything
in this case?

Brian

------_=_NextPart_001_01BFECDE.51A69630--