Sign in to follow this  
Followers 0
cag8f

Autoit-invoked cmd.exe

5 posts in this topic

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)

.

 

Share this post


Link to post
Share on other sites



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

Share this post


Link to post
Share on other sites

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

1 person likes this

Visit the SciTE4AutoIt3 Download page for the latest versions  - Beta files                                How to post scriptsource        Forum Rules
 
Live for the present,
Dream of the future,
Learn from the past.
  :)

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0