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 Delivered-To: mailing list cygwin AT cygwin DOT com Message-ID: <3C5E2672.7050808@siriushk.com> Date: Mon, 04 Feb 2002 14:13:06 +0800 From: Timothy Lee User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.8+) Gecko/20010929 X-Accept-Language: en-us MIME-Version: 1.0 To: Michael A Chase CC: cygwin AT cygwin DOT com Subject: Re: cygwin-1.3.3+: Using ASH to executing .com files -- causes Invalid Page Fault References: <3C5E122D DOT 1080803 AT siriushk DOT com> <00ee01c1ad38$e997ad50$0d00a8c0 AT mchasecompaq> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit I've tried your suggestion of changing the path order, but IPF still occurs. On the other hand, bash and tcsh cause no problems. Timothy >I can't recreate the problem under WinXP. Try putting your VIM and Cygwin >directories at the front of the path instead of the back to see if that >makes a difference. > >It might be interesting to see if the problem occurs under bash or tcsh as >well. >-- >Mac :}) > >>Since upgrading from cygwin-1.3.2, I've noticed that "sh" always causes >>Invalid Page Fault when executing .com files. >> >>The crash is 100% reproduceable on difference machines running Win98 and >>cygwin 1.3.3 or higher: >> >> C:\windows>sh >> $more.com /? >> >>At this point, a IPF will be generated, with the dialog box titled "SH", >>and the content: >> -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/