Upon further inspection...

[Matthew Smith]

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