Run fails on vbs

[stev379]

Why would this fail with "Unable to execute external program"?

It works if I replace the vbs file name with "notepad.exe".

The vbs script runs without error when double-clicked, just not when called from this AutoIT script.

Run(@SystemDir & "\FILE.vbs")

[Jos]

Why would this fail with "Unable to execute external program"?

It works if I replace the vbs file name with "notepad.exe".

The vbs script runs without error when double-clicked, just not when called from this AutoIT script.

Run(@SystemDir & "\FILE.vbs")

<{POST_SNAPBACK}>

Try:

Run(@comspec & " /c cscript.exe " & @SystemDir & "\FILE.vbs")

[stev379]

Pefect!

Thanks!

[stev379]

Related question:

The vbs script is very small (sets dns suffix for this connection) and has minor error checking to see if input was entered or not. This works when just the vbs script is double clicked. However, when running the vbs script from the AutoIT script, it completes it's task without error, but fails to return the success message or failure message if I cause it to fail.

Just to be clear, the error checking text for this action is within the vbs script. If there is a way to set the DNS suffix with AutoIT, that would work even better. I just haven't found a way to do so.

The question:

How can the error checking within the vbs script take place when the vbs script is called from an AutoIT script?

OR

How can a DNS suffix for this connection be set with an AutoIT script?

Thanks for any help or suggestions!!

[FuryCell]

Try:

Run(@comspec & " /c cscript.exe " & @SystemDir & "\FILE.vbs")

<{POST_SNAPBACK}>

Cscript.exe causes the script to output to the command line instead of a message box. The Command window might be disappearing before you can see its output.

try this instead:

Run(@comspec & " /c Wscript.exe " & @SystemDir & "\FILE.vbs")

[stev379]

Thanks!!

That did the job.