Jump to content

Recommended Posts

try the following, it will create a command window and won't close till you close it, this way you can see if there are errors

RunWait (@ComSpec & ' /k ping ' & $data2 & ' /t /l ' & $data)

SciTE for AutoItDirections for Submitting Standard UDFs

 

Don't argue with an idiot; people watching may not be able to tell the difference.

 

Link to post
Share on other sites

the command will work, i also noticed the ping command ignored all ctrl-breaks etc.. so i started the ping like above and then ran a script with just the processclose command in it and it killed the ping.

SciTE for AutoItDirections for Submitting Standard UDFs

 

Don't argue with an idiot; people watching may not be able to tell the difference.

 

Link to post
Share on other sites

yw B)

you might to think about putting some error checking in there, if they forget to set the data, and hit the start then it should not run the command

Edited by gafrost

SciTE for AutoItDirections for Submitting Standard UDFs

 

Don't argue with an idiot; people watching may not be able to tell the difference.

 

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
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...