This is the mail archive of the
cygwin@sources.redhat.com
mailing list for the Cygwin project.
RE: runtime failure in 20000710 and 20000711 snapshots
- To: cygwin at sourceware dot cygnus dot com
- Subject: RE: runtime failure in 20000710 and 20000711 snapshots
- From: "Christopher Jones" <cbjones at nortelnetworks dot com>
- Date: Thu, 13 Jul 2000 11:23:40 -0400
> Charles Wilson wrote:
> >
> > This should probably go to cygwin-developers, but I don't think
> > non-subscribers can post there. Anyway, I'm getting a popup
> window that
> > reads:
> >
> > The application failed to initialize properly (0xc0000022).
> Click on OK
> > to terminate the application.
> > [...]
> > Or is there something wrong with my configuration that is
> foobaring the
> > newer dll's?
>
> No, there's something wrong with the tarball. I have just downloaded
> and I have seen the following entry:
>
> -rw-r--r-- dj/games 627200 2000-07-12 21:11:23 usr/bin/cygwin1.dll
>
> 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´ on that dll.
>
> 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