Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sources.redhat.com
From: "Noel L Yap" <yap_noel@jpmorgan.com>
To: matts@bluesguitar.org
cc: Cygwin@Sourceware.Cygnus.Com
Message-ID: <8525692A.007481B0.00@nyc-ntgw-n01.ny.jpmorgan.com>
Date: Fri, 28 Jul 2000 17:12:36 -0400
Subject: Re: Upon further inspection...
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline

I guess it's not the same problem I'm having -- I'm on NT4.

Noel


matts@bluesguitar.org on 2000.07.28 16:25:00

To:   cygwin@sourceware.cygnus.com
cc:   (bcc: Noel L Yap)
Subject:  Upon further inspection...


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@sourceware.cygnus.com


This communication is for informational purposes only.  It is not intended as
an offer or solicitation for the purchase or sale of any financial instrument
or as an official confirmation of any transaction. All market prices, data
and other information are not warranted as to completeness or accuracy and
are subject to change without notice. Any comments or statements made herein
do not necessarily reflect those of J.P. Morgan & Co. Incorporated, its
subsidiaries and affiliates.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com