View Single Post
Old 11-05-2009, 07:20 PM   #11
mbovenka
Wizard
mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.mbovenka ought to be getting tired of karma fortunes by now.
 
Posts: 2,079
Karma: 14079267
Join Date: Oct 2007
Location: Almere, The Netherlands
Device: Kobo Sage
Quote:
Originally Posted by JvdW View Post
I'm doing some batch work too and noticed the same problem.
Joop, Kovid gave me the hint to try PowerShell instead of CMD. Just running the batch file under PS didn't work any better than under CMD, but what *did* work was feeding the batchfile as standard input to PS, like this:

PowerShell -command - < batchfile.bat

Don't ask me why that works, but it does. Perhaps Kovid will figure it out :-). The same trick doesn't work for CMD, though.
mbovenka is offline   Reply With Quote