MFC Application

[OmYcroN]

Hi ! This is my first post here and it's with a problem i have with my audio driver. I m using autoit to start "Setup.exe" but it gives me an error like it s incompatible with the device but if i double click "Setup.exe" it works. I ve tried with a .bat but the same result. Can anyone tell me how to do this in autoit ? What are this mfc applications and why they have this problem with external execution ? Thx in advance. Glad to be on this forum !

Edited March 30, 2008 by OmYcroN

[d4rk]

Welcome to the 4rum

if you can manually open it, so let's the autoIT manually open it too

mousemove()
mouseclick()

it woul be change with the diffrent screen solution

[OmYcroN]

There is a problem. The exe will be executed from a"panel" so i don t want the folder to be opened with the exe.

[MHz]

Since no code is shown of the attempts with the Bat or AutoIt script so where the scripts started in the same working directory as Setup.exe? I could possibly only imagine a working directory issue unless Setup.exe is bugged.

[OmYcroN]

The thing is that the path is correct (exe starts) but instead of installing the driver like when i db click it , it shows me a dialog saying that i don t have the right chip etc.

[MHz]

The thing is that the path is correct (exe starts)...

That does not answer my question to the working directory. My concern for the working directory is that Setup.exe is possibly looking for files in it's own working directory and if it does not find them, then it may show an odd error.

Example, you may need to pass the working directory (2nd parameter)

RunWait(@ScriptDir & '\folder\setup.exe', @ScriptDir & '\folder')

[OmYcroN]

Many Thanks !!!

Run(@ScriptDir & '\CMedia9738\setup.exe', @ScriptDir & '\CMedia9738')

It worked. Could u explain a little about the line above ? And thx again.

[MHz]

Sure, I will try.

When you double click a file to run it, it inherits the working directory where the file resides. So it can see files in it's own directory. So if the setup.exe looks for config.ini without specifying a path, then it does see it in it's working directory.

So if you ran this

Run(@ScriptDir & '\CMedia9738\setup.exe')

then setup.exe was probably looking for a file in the working directory which may have been @ScriptDir (or inherited working directory from CMD Prompt...) instead of @ScriptDir & '\CMedia9738' where it expected it. The setup file is using relative addressing to access the files within it's working directory.

[OmYcroN]

Thanx again ! I anderstand now what was the problem.