Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sources DOT redhat DOT com>
List-Help:	<mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT sources DOT redhat DOT com
Delivered-To:	mailing list cygwin AT sources DOT redhat DOT com
Message-ID:	<004001bff8d1$e8083ad0$3c5350d8@guinness>
From:	"Matthew Smith" <matts AT bluesguitar DOT org>
To:	"Cygwin" <cygwin AT sourceware DOT cygnus DOT com>
Subject:	Upon further inspection...
Date:	Fri, 28 Jul 2000 15:25:00 -0500
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 5.00.2919.6700
X-MimeOLE:	Produced By Microsoft MimeOLE V5.00.2919.6700

Upon further inspection, I've learned it's not a sh problem at all.  What
was happening was that the shell script in question was creating a .bat file
on the fly, and then execing the .bat file.  It seems that Microsoft in
their infinite wisdom has changed the behavior of cmd.exe between Windows
NT4 and Windows 2k.  Under Windows 2k, try creating a simple .bat file that
echos something to the screen.  Then try to run the batch file by saying
./file.bat.  It will spit this out to the screen:

'.' is not recognized as an internal or external command,
operable program or batch file.

Which was the problem I was having.  Bummer.

cheers,
-Matt Smith


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -