Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin-developers/>
List-Post:	<mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin-developers AT sources DOT redhat DOT com
Date:	Thu, 24 Aug 2000 21:45:38 -0400
Message-Id:	<200008250145.VAA21784@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	cygwin-developers AT sources DOT redhat DOT com
Subject:	setup status

I fixed the authentication code yesterday, got good reports from
people who had had problems before.

I just sent out a copy of setup.exe that adds logging.  It will
create two log files:

setup.log - summary information, grows with each install (i.e. history)
setup.log.full - complete information, but only for most recent install

If you're installing, these end up in the new cygwin root.  Otherwise,
they go at the root of wherever the files were downloaded too.  If the
user clicks the setup icon on the web page and does "download only",
the two logs end up on the desktop.  We'll usually want the
setup.log.full file to diagnose problems.

Feel free to add log() statements in setup as needed - see
cinstall/log.h.

I also fixed the password fields so that they show asterisks instead
of the real characters.

Unless anyone has a strong preference otherwise, I'm going to start
working on the non-IE5 network code next.

- Raw text -