[added 15.0.23] Run command, capture STDOUT

[Grovkillen]

It would be really great if we could capture the STDOUT from a run command instead of having to rely on piping it to the clipboard or an external file. Something like this:

Code: Select all

Let>RP_CAPTURE_STDOUT=1
RunProgram>wmic path Win32_OperatingSystem get LastBootUpTime

//RP_STDOUT=20201202082216.500000+060

This incline that the RP_CAPTURE_STDOUT behaves like RP_WAIT=1 since we need to wait for the cmd to finish.

EDIT:
Since 15.0.23 this is working!

Code: Select all

Let>RP_CAPTURESTDOUT=1
RunProgram>wmic path Win32_OperatingSystem get LastBootUpTime
MDL>RP_STDOUT

Or more cleaned up:

Code: Select all

Let>RP_CAPTURESTDOUT=1
Let>RP_WINDOWMODE=0
RunProgram>wmic path Win32_OperatingSystem get LastBootUpTime
RegEx>[\S\s]*(\d{14}\.\d*\+\d*)[\S\s]*,RP_STDOUT,0,,,1,$1,LAST_BOOT_UP_TIME
MDL>LAST_BOOT_UP_TIME

[Grovkillen]

Would this be considered to be added?

[Marcus Tettmar]

Hi,

I have added this to the wish list for investigation.

[Grovkillen]

Thanks for the feedback!

[Grovkillen]

I'm currently coding a INI file handler which will support UTF8, delete (section/entry), timestamping of changes, concatinate value (front/back), timestamp to value, and a history log. It will be a terminal application. When requesting a value to be read or updated I want to be able to get this info straight from the command line and thus a capture of STDOUT would be awesome. *FINGERS CROSSED*

[fightcancer]

Seconding this request!

[mightycpa]

One more user that wants it!! That's over 300, by my count!

[Grovkillen]

I see more and more use of this enhancement suggestion. It's not ideal to have multiple scripts relying on the clipboard to get data and piping the output to files make the file system involved which will slow things down and involve more commands in MS. Please consider this request

[Grovkillen]

I found another use case for this:

Code: Select all

Let>RP_WAIT=1
Let>RP_WINDOWMODE=0
Let>PATH_TO_FILE=K:\SE\0D140\270001_Testkub.par
Let>CMD_TO_RUN=cmd /c c: & certutil -hashfile "%PATH_TO_FILE%" MD5 | clip
RunProgram>CMD_TO_RUN
GetClipBoard>HASH_OF_FILE,0
Let>CLEANUPT_REGEX=[\S\s]*([a-f0-9]{32})[\S\s]*
RegEx>CLEANUPT_REGEX,HASH_OF_FILE,0,,,1,$1,HASH_OF_FILE
MDL>HASH_OF_FILE

Instead of having to pipe it to a output file I would love to have it passed back into the script without the need for the clipboard.

[Marcus Tettmar]

https://help.mjtnet.com/article/222-version-history

[Grovkillen]

OH!!!! HAPPY!

[Grovkillen]

Updated now that this is live and working great

Code: Select all

Let>RP_WINDOWMODE=0
Let>RP_CAPTURESTDOUT=1
Let>PATH_TO_FILE=K:\SE\0D140\270001_Testkub.par
Let>CMD_TO_RUN=certutil -hashfile "%PATH_TO_FILE%" MD5
RunProgram>CMD_TO_RUN
Let>CLEANUP_REGEX=[\S\s]*([a-f0-9]{32})[\S\s]*
RegEx>CLEANUP_REGEX,RP_STDOUT,0,,,1,$1,HASH_OF_FILE
MDL>HASH_OF_FILE

[Grovkillen]

Sometimes you need to add cmd /c ahead of the command for it to return a result.

[Grovkillen]

Can someone confirm that this is working with RP_ADMIN=1?

[JRL]

This works for me:
(Note the use of "Between>" rather than "RegEx>")
Looks like your file is on a shared drive, be sure your admin user has access to the share.

Code: Select all

Let>PATH_TO_FILE=L:\A\Run MyTime.exe

Let>RP_WINDOWMODE=0
Let>RP_CAPTURESTDOUT=1
Let>RP_Admin=1

Let>CMD_TO_RUN=cmd /c certutil -hashfile "%PATH_TO_FILE%" MD5
RunProgram>CMD_TO_RUN
Between>RP_STDOUT,:%crlf%,%crlf%Cert,HASH_OF_FILE,Match_Num
MDL>HASH_OF_FILE_1