Autoit-invoked cmd.exe

[cag8f 0]

I'm experiencing some unexpected behavior from an Autoit-invoked command prompt.  I can open a command prompt using:

Run("C:\WINDOWS\SYSTEM32\CMD.EXE")

After the Autoit script has finished, and the command prompt window still exists, I can run some commands like ipconfig and cd.. without issue.  However if I try to ping ('ping www.google.com'), a 2nd command prompt appears to try to open, then is immediately closed. Furthermore, this repeats itself infinitely to the point where I have to reset/logoff Windows (Win 7 32 bit) in order to kill those processes (task manager will not do it).  Anyone know why this is happening?

FYI this issue also occurs if I open the command prompt using 

Run(@ComSpec & " /K " & 'commandName', "", @SW_MAXIMIZE)

.

 

[Jos 2,168]

let me guess: You compiled your script and it is called "Ping.au3" ?

Jos

[Palestinian 13]

#RequireAdmin

Run("C:\WINDOWS\SYSTEM32\CMD.EXE")
WinWaitActive("Administrator")
Send('ping www.google.com')
Send("{ENTER}")

 

Works just fine

[cag8f 0]

Thanks JOS.  Yes I named my file Ping.au3, which obviously conflicts with an Autoit function.  I renamed mine and the issue was resolved.

[Jos 2,168]

Thanks JOS.  Yes I named my file Ping.au3, which obviously conflicts with an Autoit function.  I renamed mine and the issue was resolved.

It conflicts with the dos command Ping.exe and basically start shelling itself indefinitely.

Jos