Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , 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: <431BFA1D.5040903@cs.yale.edu> Date: Mon, 05 Sep 2005 00:56:13 -0700 From: Sean Gugler 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 AT cygwin DOT com Subject: Re: 1.5.18-1: Crash launching COMMAND.COM (W98) References: <1125870155 DOT 32392 DOT ezmlm AT cygwin DOT com> In-Reply-To: <1125870155.32392.ezmlm@cygwin.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit 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. NEW STEPS TO REPRO 1. unpacked into a fresh folder from "cygwin-inst-20050901.tar.bz2" 2. renamed my old C:\Cygwin to be sure it was unreachable 3. snapshot didn't come with a shell, so I copied bash.exe from my old installation: "GNU bash, version 3.00.16(11)-release (i686-pc-cygwin)" 4. same problem as before: perpetual "illegal operation" dialog upon trying to invoke "COMMAND.COM" 5. tried with ash.exe as well, same result (version 20040127-3) - 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/