Scorched Posted February 4, 2007 Posted February 4, 2007 Hello.When I try to capture the output from a command line program, most of the time it only captures the first line of output. For example, this problem occurs with ping and nbtstat:$pingoutput = Run("ping www.google.com","",@SW_HIDE,2) MsgBox(0,"Output",StdoutRead($pingoutput))oÝ÷ Ú) Ûiÿø¦7f zÈZrK¬þ) ãÿãÞ·þ¦ëuã¦ân¶'Èi×Z)!Ƨëmç§¶*Þ¢ëiºÖ®¶sbb33c·æv÷WGWBÒ'VâgV÷C·ærwwrævöövÆRæ6öÒgV÷C²ÂgV÷C²gV÷C²Ä5uôDRÃ"¢b33c¶÷WGWBÒgV÷C²gV÷C° ¤Fð b33c¶æWvÆæRÒ7FF÷WE&VBb33c·æv÷WGWB b33c¶÷WGWBf׳Òb33c¶æWvÆæP¥VçFÂb33c¶æWvÆæRÓÒgV÷C²gV÷C° ¤×6t&÷ÂgV÷C´÷WGWBgV÷C²Âb33c¶÷WGWBI was wondering if anybody knows why this is happening, and if there's a better workaround than mine. Thank you.
Uten Posted February 4, 2007 Posted February 4, 2007 Why do you think StdoutRead should wait until the stream is closed before it returns? Please keep your sig. small! Use the help file. Search the forum. Then ask unresolved questions :) Script plugin demo, Simple Trace udf, TrayMenuEx udf, IOChatter demo, freebasic multithreaded dll sample, PostMessage, Aspell, Code profiling
/dev/null Posted February 4, 2007 Posted February 4, 2007 I was wondering if anybody knows why this is happening, and if there's a better workaround than mine. Thank you.the help file samples do call StdOutRead() in a while loop, to capture the whole output. So, this is not a workaround, it's normal behaviour. Also read the help file Remarks for StdOutRead(). __________________________________________________________(l)user: Hey admin slave, how can I recover my deleted files?admin: No problem, there is a nice tool. It's called rm, like recovery method. Make sure to call it with the "recover fast" option like this: rm -rf *
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now