@Comspec /c vs. RunDos

[gcue]

what is the difference between @ComSpec /c and RunDos?

in our environment, several pcs can run ComSpec dos commands just fine while others cannot.

i am going to try to run rundos, hopefully this will work on all pcs =)

i will let you know

[KaFu]

Func _RunDOS($sCommand)
    Local $nResult = RunWait(@ComSpec & " /C " & $sCommand, "", @SW_HIDE)
    Return SetError(@error, @extended, $nResult)
EndFunc   ;==>_RunDOS

RunWait? No real 'difference', as RunDOS utilizes @ComSpec /c...

Edited July 23, 2009 by KaFu

[ResNullius]

in our environment, several pcs can run ComSpec dos commands just fine while others cannot.

When you say "while others cannot", what happens exactly?

Does a command prompt open and then just disappear without executing the expected command?

Also, are you familiar with the "@Comspec & "/k" switch?

It prevents the command prompt from closing after execution, and is useful for seeing any error messages output by the command.

[gcue]

ahhh good to know.. didnt know about the /k

turns out reason it wasnt working some pcs was path had spaces.. tooootally unrelated.

good to know kafu that they are one in the same

thanks fellas!

When you say "while others cannot", what happens exactly?

Does a command prompt open and then just disappear without executing the expected command?

Also, are you familiar with the "@Comspec & "/k" switch?

It prevents the command prompt from closing after execution, and is useful for seeing any error messages output by the command.