Run(@ComSpec & " / c " ~ application hangs

[Skitty]

Im running a program using this command~

Run(@ComSpec & ' /c "' & $ProgPath & '" -default',"",@SW_HIDE)

And to my horror autoit treats this as if I were to use RunWait, how can I prevent autoit from waiting for the program to close which is not supposed to close anytime soon while still running it from the command line?

Edited March 21, 2012 by THAT1ANONYMOUSEDUDE

[UEZ]

I assume the application behind $ProgPath is not closing.

What is behind $ProgPath?

Br,

UEZ

[Skitty]

Just another script I've got set up to monitor some stuff, the problem really is that I would expect that autoit would just run the program and continue execution unlike "runwait", I've stumbled into this behavior before and ignored it using another method but this time I really want to be able to execute an app from the command line without showing the command line and having the cmd.exe process exit after executing it and not stay there aiting for the app it ran to close, as it won't close anytime soon..

[Jos]

Tell us the version of AutoIt3 you use and give us something to test with.

[Skitty]

Well, it basically behaves the same way with anything you run via @Comspec, and now that I read up on its switches "which I should have done before", I realize that the /c switch makes the command prompt stand idly by until the program it executed has finished, I would have expected there to be a switch to change this behavior as well but it seems that no matter what you do, the command prompt will always wait for a command it executed to finish, including programs it has executed, this is weird.

I'm using AutoIt v3.3.8.1 but this seems to happen with any version.

In example~

Run(@ComSpec & ' /c "' & @SystemDir & 'taskmgr.exe"',"",@SW_HIDE)

running that will make autoit pause until you close task manager, I would have thought the run() function would just run the command and continue it's execution but that's not how it works as I see..

Edited March 21, 2012 by THAT1ANONYMOUSEDUDE

[Jos]

The Run() function returns fine, but what you probably experience is that the Shelled application is a child of the AutoIt3 task and SciTE "thinks" your script isn't finished.

Run this and see you get the taskid returned immediately.

$rc = Run(@ComSpec & ' /c "' & @SystemDir & 'taskmgr.exe"',"",@SW_HIDE)

ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $rc = ' & $rc & @crlf & '>Error code: ' & @error & @crlf) ;### Debug Console

Edited March 21, 2012 by Jos

[Skitty]

The run Func returns fine, but what you probably experience is that the Shelled application is a child of the AutoIt3 task and SciTE "thinks" your script isn't finished.

Run this and look down your Taskmanager for CMD.EXE with the returned TASKNR;

$rc = Run(@ComSpec & ' /c "' & @SystemDir & 'taskmgr.exe"',"",@SW_HIDE)

ConsoleWrite('@@ Debug(' & @ScriptLineNumber & ') : $rc = ' & $rc & @crlf & '>Error code: ' & @error & @crlf) ;### Debug Console

I felt so stupid when I opened process explorer, ran my program again and noticed it was actually scite waiting for the program to close...

I should have looked closer when doing this..

Local $PID = Run(@ComSpec & ' /c "' & $ProgPath & '" -Default',"",@SW_HIDE)
   Sleep(3000)
   ProcessClose($PID)

This seems to work only the autoit3wrapper seems to stay alive afterwards.

Edited March 21, 2012 by THAT1ANONYMOUSEDUDE

[Jos]

This is only when you run it from within SciTE so is this anything you need to worry about?

[Skitty]

This is only when you run it from within SciTE so is this anything you need to worry about?

Nope, not really, aside from the inconvenience of having to manually terminate the autoit wrapper when testing, everything's fine I guess, thank you for the effort/help

[Jos]

Had a closer look and have adapted AutoIt3Wrapper to terminate when the shelled AutoIt3.exe has ended avoid it to wait for any shelled task with Run.

Try the current Beta Autoit3Wrapper.

Jos