Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Date: Mon, 5 Sep 2005 13:49:00 -0400 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: 1.5.18-1: Crash launching COMMAND.COM (W98) Message-ID: <20050905174859.GB3621@trixie.casa.cgf.cx> Reply-To: cygwin@cygwin.com References: <1125870155.32392.ezmlm@cygwin.com> <431BFA1D.5040903@cs.yale.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/