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: Charles Wilson <cwilson at ece dot gatech dot edu>, DJ Delorie <dj at delorie dot com>
- Subject: Re: runtime failure in 20000710 and 20000711 snapshots
- From: Corinna Vinschen <vinschen at cygnus dot com>
- Date: Thu, 13 Jul 2000 15:14:44 +0200
- CC: cygwin at sourceware dot cygnus dot com
- References: <396D364D.6A019EC1@ece.gatech.edu>
- Reply-To: cygwin <cygwin at sources dot redhat dot com>
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.
DJ, can you explicitely care for the x-bit in the tarballs?
Corinna
--
Corinna Vinschen
Cygwin Developer
Cygnus Solutions, a Red Hat company
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com