public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Paul Maier" <svn-user@web.de>
To: <cygwin@cygwin.com>
Subject: AW: setup.exe fails on Windows 7 - please help
Date: Sun, 22 Jul 2012 00:03:00 -0000	[thread overview]
Message-ID: <004701cd679d$239a3ed0$6acebc70$@de> (raw)
In-Reply-To: <20120720085024.GY31055@calimero.vinschen.de>


> > 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

  reply	other threads:[~2012-07-22  0:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-20  6:55 Paul Maier
2012-07-20  8:50 ` Corinna Vinschen
2012-07-22  0:03   ` Paul Maier [this message]
2012-07-22  3:19     ` AW: " Mark Geisert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='004701cd679d$239a3ed0$6acebc70$@de' \
    --to=svn-user@web.de \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).