_RunSTD

[w0uter]

for all the people that have trouble using STD

Func _RunSTD($s_p, $s_wd = @WorkingDir, $s_f = @SW_HIDE)
    Local $s_r = '', $i_pid = Run($s_p, $s_wd, $s_f, 2)
    While Not @error
        $s_r &= StdoutRead($i_pid)
    WEnd
    Return $s_r
EndFunc

ConsoleWrite(StringReplace(_RunSTD(@ComSpec & ' /c ipconfig /all'), @CR, '') & @LF)

[erifash]

Nice work w0uter! This could be really helpful for the new people.

[blitzkrg]

if i wanted to see the "output" of say a telnet session or ftp session could i use this?

lets say i need to authenticate to a firewall via telnet

so i write a script to run telnet and then enter my login and pw.

if i wanted to watch this process but not interact, could it be done?

[DaveF]

if i wanted to see the "output" of say a telnet session or ftp session could i use this?

lets say i need to authenticate to a firewall via telnet

so i write a script to run telnet and then enter my login and pw.

if i wanted to watch this process but not interact, could it be done?

Kind-of, yes. There are examples on this forum that do the latter part of what you describe, by AutoIt capturing the output of a console process and displaying it, in a GUI edit box for example, as in the example linked above.

The problem with doing specifically what you've asked is that Windows telnet won't run if the standard input is redirected (or XP's won't at least) which prevents AutoIt from entering "interactive" commands on your behalf.

I've used Console Telnet as a replacement for the Windows version, and I know that other forum users have used Plink because it will do both telnet and SSH.

for all the people that have trouble using STD

Thanks for this UDF, @w0uter, and I should have said so before now.

If you can come up with a UDF for _StdxxxReadLine I'd be interested to see how you'd make it work.

Edited October 4, 2005 by DaveF