From: Arthur I Schwarz <Arthur_I_Schwarz@raytheon.com>
To: ramon@usofm.com
Cc: cygwin@cygwin.com
Subject: Re: 0x6756a0 win32 error renders cygwin almost useless
Date: Fri, 15 Jul 2005 19:29:00 -0000 [thread overview]
Message-ID: <OF23FAAEAB.88F6B1A1-ON8825703F.006A327E-8825703F.006B0DD8@mck.us.ray.com> (raw)
>Can anybody diagnose this problem? Thanks in advance /r?
I have continuous problems installing. Setup ungracefully crashes when
either an install is attempted on a file not downloaded or if the setup.ini
has an unresolvable reference. Hence I have a strategy to installing. If
all else fails:
1. Go to the registry and delete all entries to 'cygwin' and 'cygnus' and
'red hat' if appropriate.
2. I always save the old cygwin (C:/cygwin -> C:/cygwin.old), and
3. Create a new cygwin root (C:/cygwin), and then
4. Do a reinstall.
Occassionally setup will corrupt the installation so that it is
unrecoverable - which seems to be what you are experiencing. Repeat above.
I've tried to identify and fix setup errors but can't seem to get it
compiled and linked. So I gave up. But there does appear to be some
ungraceful coding in setup - and lest I get flamed - Cygwin and the Cygwin
staff to a person seem excellent.
art
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
next reply other threads:[~2005-07-15 19:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-15 19:29 Arthur I Schwarz [this message]
2005-07-15 19:51 ` Christopher Faylor
2005-07-20 21:47 ` Ramón Fallon
-- strict thread matches above, loose matches on Subject: below --
2005-07-14 20:28 Ramón Fallon
2005-07-14 21:15 ` Larry Hall
2005-07-20 22:29 ` Ramón Fallon
2005-07-25 0:04 ` Alan Wehmann
2005-07-26 4:32 ` Alan Wehmann
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=OF23FAAEAB.88F6B1A1-ON8825703F.006A327E-8825703F.006B0DD8@mck.us.ray.com \
--to=arthur_i_schwarz@raytheon.com \
--cc=cygwin@cygwin.com \
--cc=ramon@usofm.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).