X-Spam-Check-By: sourceware.org To: cygwin AT cygwin DOT com From: Rolf Campbell Subject: Re: cygwin1.dll possible bug Date: Mon, 20 Feb 2006 14:00:14 -0500 Lines: 17 Message-ID: References: <022020061447 DOT 1372 DOT 43F9D692000F41EB0000055C22007610640A050E040D0C079D0A AT comcast DOT net> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit User-Agent: Thunderbird 1.5 (Windows/20051201) In-Reply-To: X-IsSubscribed: yes Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm Precedence: bulk List-Unsubscribe: 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 Gland Vador wrote: > Eric Blake wrote: >> What about the newest one? > > I have tried almost all snapshots available on this page. I went until > the oldest in order to track on which snapshot it broke. > > The newest one doesn't work for me. When I launch a dos batch file in > the bash, it tries to execute it line by line and not calling the cmd.exe. Warning: this is a "me too" message. For those of your emotionally sensitive to this type of message, you should probably just skip this message. This is something that I've noticed about the newer snapshots too, running .bat files dies on "@ECHO" command not found (and every other DOS batch file construct). -- 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/