How to set path for RUN?

[ledigeine]

I am trying to run an exe that is here we'll say, g:\folder

When trying this, Run(@ComSpec & " /c " & "g:\folder\file.exe" , "", @SW_HIDE) my program will error out.

So if i open a cmdprompt then do the old:

g:

cd\folder

then type file.exe

it will launch.

How with RUN would I recreate that?

Also if i just open a cmdprompt and type, g:\folder\file.exe it will error just the same as that run command up there.

Looks like I need to be in the folder before i can do the exe for my program to actually launch with out errors.

Sorry i have looked around but didnt seem to find anything.

[BrewManNH]

What error are you getting? Saying it "error(s) out" is really not helpful to troubleshooting your issue.

[ledigeine]

Oh i said that because its an error related to the program im calling... its not an autoit error.

The program i work with will error when I call it while not at its path. So if im starting at C: and run g:folderfile.exe it will error. But if i go to g:folder and run file.exe it will run just fine.

With the Run command can you run something from a set path?

I hope this is more clear.

[AdmiralAlkex]

You are talking about setting the working directory, which is the second parameter to Run(). I will let you piece that puzzle together.

[ledigeine]

You are talking about setting the working directory, which is the second parameter to Run(). I will let you piece that puzzle together.

Thank you... i think with all the other jazz in my run command that i pulled from the helpfile or these forums was a bit confusing. So i didnt know what part I could change while letting it still do its thing.

I guess i need to understand the @comspec part as well as the " /c " part... i didnt think i could alter that so i didnt really wana alter much else.

Working now!

[BrewManNH]

@Comspec is just a macro shortcut to the cmd.exe program, usually located in C:\Windows\system32 on x86 systems. The /c tells the cmd.exe program to close the console window after the program has finished running, use /k to keep it open if you need to see what if any output is in the window for debugging purposes. The @SW_HIDE at the end of the statement keeps the console window hidden, so it opens cmd.exe in a window, but you never see it, which is why you NEED to use /c if you're going to keep the window hidden because there's no way to close the cmd.exe window after it has finished other than through the task manager.

[ledigeine]

Thank you sir for explaining this all, was always afraid of that line of code ha.

[BrewManNH]

Glad I could help, not everything is in the help file (or easily found if it is in there).