>To the original poster: since there is no way to propagate tty information >through a cmd.exe session, I suppose the best solution would still be the >one Alexander proposed, i.e., live with it. Why would one want to call a >batch file from an xterm, anyway?
Some programs use batch files on windows. In my case, an ant build script to pops up a window when weblogic rmic is called. Another user had similar issues with Jam in Sept. 2001. If I don't use cmd.exe, I won't see errors. We also use batch files internally so developers can use either cygwin or cmd.exe depending on their own personal preference. This used to work, and still works for developers who don't upgrade as often as I do. Something changed. I can always use cmd.exe, but I prefer to work in xterm. Sept 2001: strange behavior regarding new cygwin 1.3.3 and cmd.exe http://sources.redhat.com/ml/cygwin/2001-09/msg01697.html
