Nice one! MMM's handle on managing command IO for stdout or stdin is not great. Saying that though there are some hack work around's to make it work.
I think your example looks good. Could be you need to run the script twice because the macro is running too fast and needs a break to process the environmental queues.
Check out this example:
1 | RUN ACTION | | | | RUN VIA CMD /C | title=runscript & C:\Program_Portable\mmm\script01 2 | RUN ACTION | | | | WAIT SECONDS | 1 3 | IF | WINDOW TITLE | runscript | NOT EXIST | CONTINUE 4 | RUN ACTION | | | | MESSAGE PROMPT | %CLIPBOARD%::clip
Here we set the cmd window title to 'runscript' and wait 1 second for the cmd to execute. Then at line 3 we check if the WINDOW TITLE for 'runscript' exists. If not we continue.
or this one: 1 | RUN ACTION | | | | RUN VIA CMD /C | C:\Program_Portable\mmm\script01 2 | RUN ACTION | | | | WAIT SECONDS | 1 3 | IF NOT | PROCESS NAME | cmd | EXIST | CONTINUE 4 | RUN ACTION | | | | MESSAGE PROMPT | %CLIPBOARD%::clip
Here we check for the process cmd. If NOT process cmd exist then we continue the macro.
I'm about to (sometime this month) release an update to MMM that adds some more functionality. It should make IO a bit easier. Until then, mad hacks like this will get it done.
Amazing Steve! The first example worked but I couldn't get the 2nd one to work. This hack should be enough for now and I look forward to your new release. At least I can parse any strings I need now using an external script. Again, I have to say you and MMM are wonderful! Features are so advanced! Thanks again!