X-Recipient: archive-cygwin AT delorie DOT com X-SWARE-Spam-Status: No, hits=-0.7 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KHOP_THREADED,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_NO,RCVD_IN_HOSTKARMA_YE,T_RP_MATCHES_RCVD X-Spam-Check-By: sourceware.org From: "Paul Maier" To: References: <001b01cd6644$60032300$20096900$@de> <20120720085024 DOT GY31055 AT calimero DOT vinschen DOT de> In-Reply-To: <20120720085024.GY31055@calimero.vinschen.de> Subject: AW: setup.exe fails on Windows 7 - please help Date: Sun, 22 Jul 2012 02:01:26 +0200 Message-ID: <004701cd679d$239a3ed0$6acebc70$@de> MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com > > Hi, > > > > setup.exe brings hundreds of identical popups with error message: > > > > bash.exe: > > The application could not be started (0xc000000d). *) > > > > All the .exe files are there in the bin folder, but when I double click on bash.exe or > any other .exe, > > I get the same message. > > > > Only ps.exe works normally. > > > > Cygwin worked without problem for a year on the same machine. > > > > I had completely deleted the folder D:\program\cygwin from my drive and started over, > but it's the same. > > > > Thank you for any help! > > > > Regards, > > Paul > > > > > > *): original German text: Die Anwendung konnte nicht korrekt gestartet werden > (0xc000000d). > Very weird, 0xC000000D is "Invalid parameter". I would guess that you > have a BLODA problem: > > http://cygwin.com/faq/faq.using.html#faq.using.bloda > Hi! thank you, this is solved now. It took me _hours_ of debugging. I found a copy of cygwin1.dll in an other directory. Feature request: Would it take long to add a check at the beginning of setup.exe, that looks for orphaned copies of cygwin1.dll? And if so, ask the user if setup.exe should be aborted or continued on user's risk. setup.exe runs approx. 3 hours plus 4 hours of debugging. -> Such a check can save 1 day. Greetings, Paul -- 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