Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <431CA835.5060502@cs.yale.edu>
Date: Mon, 05 Sep 2005 13:19:01 -0700
From: Sean Gugler <gugler-sean@cs.yale.edu>
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
MIME-Version: 1.0
To: cygwin@cygwin.com
Subject: Re: 1.5.18-1: Crash launching COMMAND.COM (W98)
References: <1125870155.32392.ezmlm@cygwin.com> <431BFA1D.5040903@cs.yale.edu> <20050905174859.GB3621@trixie.casa.cgf.cx>
In-Reply-To: <20050905174859.GB3621@trixie.casa.cgf.cx>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Nay, the crash well and truly persists even with correct application
of the 2005-09-01 snapshot, though I thank Brian and Christopher
for their encouragement.  I've tried to carefully isolate the issue
to Cygwin (see below), and believe the June fix was insufficient
for my environment.

Anyone else willing to take a crack at helping me discover whether
a flaw persists in Cygwin or if there remains something unusual
with my environment?


MY DUE DILIGENCE
-----------------
Please note, I made sure I had the most recent release (1.5.18-1)
before ever mailing this list.  I also tried putting the snapshot
CYGWIN1.DLL directly into my C:\Cygwin directory, yet the failure
persisted.  Only then did I attempt a "clean" run of the cygwin-inst
tar ball, ensuring I had no old cruft and only fresh snapshot binaries.
For reference, my former posts are at:
http://cygwin.com/ml/cygwin/2005-09/msg00058.html
http://cygwin.com/ml/cygwin/2005-09/msg00083.html

I suppose the most convincing test would be to do a completely clean
install from setup.exe, and if it yet fails, a clean install of
Windows 98 itself.  (shudder)

          - Sean


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