why does this line error?

[unclefishy]

can somebody explain this why this errors?

it will compile fine, and the path is correct... but it chokes every time and my syntax seems to be correct.

Thanks

RunWait(@COMSPEC & " /c Start ", "C:\ntst-tmp\visio-test1\VISPRO.msi")

[Danny35d]

Try it....

RunWait(@COMSPEC & " /c Start C:\ntst-tmp\visio-test1\VISPRO.msi", @ScriptDir)

[GEOSoft]

can somebody explain this why this errors?

it will compile fine, and the path is correct... but it chokes every time and my syntax seems to be correct.

Thanks

RunWait(@COMSPEC & " /c Start ", "C:\ntst-tmp\visio-test1\VISPRO.msi")

Try

ShellExecuteWait("C:\ntst-tmp\visio-test1\VISPRO.msi")

[unclefishy]

I didn't realize that i could use shell exe... slick.

works like a champ!!

Thanks a bunch GEOsoft

[GEOSoft]

Try it....

RunWait(@COMSPEC & " /c Start "C:\ntst-tmp\visio-test1\VISPRO.msi", @ScriptDir)

I'm pretty sure that won't work either. An msi file is not an executable.

To use Run it would have to be

Run(@SystemDir & "\msiexec.exe /i C:\ntst-tmp\visio-test1\VISPRO.msi")

There is no need to use @Comspec in there either

Edited May 8, 2007 by GEOSoft

[Jos]

I'm pretty sure that won't work either. An msi file is not an executable.

To use Run it would have to be

That will work since start.exe acts the same as ShellExecute().

[GEOSoft]

That will work since start.exe acts the same as ShellExecute().

Ahhhhh yes!! Another momentary lapse.

I still find that in most instances ShellExecute is the way to go and I reserve @Comspec for those instances where I want to run native commands that would normally be used in a command window.

[unclefishy]

it seems however when i use the shellexecute command that it breaks the winwaitactive command right after it... where when i launch with the following it seems to launch and understand the winwaitactive command, and thus can proceed to 'send'

RunWait(@COMSPEC & " /c Start C:\ntst-tmp\visio-test1\VISPRO.msi")

[Jos]

it seems however when i use the shellexecute command that it breaks the winwaitactive command right after it... where when i launch with the following it seems to launch and understand the winwaitactive command, and thus can proceed to 'send'

RunWait(@COMSPEC & " /c Start C:\ntst-tmp\visio-test1\VISPRO.msi")

You should use ShellExecute() in stead of ShellExecuteWait() since you want it to launch the program and continue the script . Edited May 8, 2007 by JdeB

[unclefishy]

really?

so instead of using

ShellExecuteWait("C:\ntst-tmp\visio-test1\VISPRO.msi")

i should change it to just

ShellExecute("C:\ntst-tmp\visio-test1\VISPRO.msi")

[Jos]

really?

so instead of using

ShellExecuteWait("C:\ntst-tmp\visio-test1\VISPRO.msi")

i should change it to just

ShellExecute("C:\ntst-tmp\visio-test1\VISPRO.msi")

The last line works because Runwait Shells Start which shells MSIEXEC and then returns.

So effectively it acts as Run()

shellexecutewait() doesn;t break your WinWaitActive() command, but your script stops until the MSIEXEC is finished.

Try ShellExecute() .

[unclefishy]

thanks for the explination... that helps me wrap my melon around it a little better!