Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Date: Mon, 5 Sep 2005 13:49:00 -0400
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: 1.5.18-1: Crash launching COMMAND.COM (W98)
Message-ID: <20050905174859.GB3621@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
References: <1125870155 DOT 32392 DOT ezmlm AT cygwin DOT com> <431BFA1D DOT 5040903 AT cs DOT yale DOT edu>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <431BFA1D.5040903@cs.yale.edu>
User-Agent: Mutt/1.5.8i

On Mon, Sep 05, 2005 at 12:56:13AM -0700, Sean Gugler wrote:
>Brian Dessent replied to me:
>> There was a problem with launching 16 bit applications that occured
>> exactly as you state, but that was fixed around June and went into the
>> 1.5.18 release.  Try a snapshot.
>
>Thanks, Brian, good idea.  Alas, no luck.  If anyone knows of other
>test suites or experiments I could run to help isolate what's going
>wrong, please let me know.

This should be fixed in the latest snapshot at
http://cygwin.com/snapshots/ .

FYI, you shouldn't rename your whole c:\cygwin directory.  Doing that
effectively eliminates everything that you've downloaded.  You noticed
that there was no bash after you did that but there is also no awk, sed,
grep, gcc, etc.  The cygwin-inst tar ball is not a replacement for the
whole cygwin distribution.

You really only need to grab the DLL to test this.  You don't need
all of cygwin-inst.

cgf

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