Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
Message-ID: <000701c20e1e$e04c4de0$6fc82486@medschool.dundee.ac.uk>
Reply-To: <fergus AT bonhard DOT uklinux DOT net>
From: <fergus AT bonhard DOT uklinux DOT net>
To: <cygwin AT cygwin DOT com>
Cc: <fergus AT bonhard DOT uklinux DOT net>
Subject: Crashing setup.exe
Date: Fri, 7 Jun 2002 13:28:49 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000

>> Pavel Tsekov said :
>> So ... if you remove the setup.ini from the local
>> package directory, setup.exe won't crash.

Do you mean that separating the file named setup.ini from the folder named
release/ and then running the executable named setup.exe, will result in a
glitch-free installation or upgrade? If this is so and I have not
misunderstood you, then I have three questions. (A) How are the two
different locations of setup.ini and release/ to be identified to setup.exe
so that setup.exe knows about them? (B) At the moment, these two items
"arrive" together in a folder with a name like
ftp%3a%2f%2fmirrors.rcn.net%2fmirrors%2fsources.redhat.com%2fcygwin or some
such: should one therefore manually separate them after download but before
installation? (C) Does your cure apply to all O/S as far as you know? (If I
can discover the answer to (A) then I will try to sort out (B) and *C) for
myself. Thank you.)

Fergus


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/