Run with STDERR_CHILD and STDOUT_CHILD fails.

[RLL]

HI,

I'm running a simple "Run" script from windows that runs the dos "find" intrinsic.

$pid = Run(@Comspec & ' /k ' & $findCmd , "someStartupDirectory", @SW_SHOW, $STDERR_CHILD + $STDOUT_CHILD)

thIs fails with a windows error box: "Findi String (grep) Utility has encountered a problem and needs to close. blah blah".

If I Run

$pid = Run(@Comspec & ' /k ' & $findCmd , "someStartupDirectory", @SW_SHOW)

it runs, the output in the dos window is correct.

Anybody have a clue as to what's wrong? Because the short Run command works, I'm not suspicious of the $findCmd string nor of the startupDirectory.

For some reason the hook into stderr and stdout is failing (my guess).

Ron

[RLL]

I've gone a bit further.

I've changed $findCmd to run search.bat that turns echo on, echos the input, then runs dos "find".

search.bat

echo on

echo %1 %2 %3

find %1 %2 %3

Running this, I am getting stdout back from the child process (the echo output), but windows find is failing with the error window described above = no output from find.

I'll roll my own find in C/C++.

This may be trouble for others in the future.

Ron

[BrewManNH]

It would be most helpful if the whole script was posted, plus the contents of the batch file. Otherwise we're taking shots in the dark, considering $findcmd has no information for us to look at. Also, we could probably suggest ways of doing whatever it is you're trying to do without ever calling up a run command by using internal AutoIt commands to do whatever it is.

[NickTheWeird]

RLL,

   Did you ever determine why using @STDOUT_CHILD within the Run command will not work ? I am having the same issues.

 

(yes, I l know its a 4 year old post, but Ive been searching for 2 days now)

Edited September 20, 2015 by NickTheWeird

[Jos]

Just start a new thread with your question and your source giving the issues. 

Jos