Reinstalled AutoIt and AutoIt Bata, now Run() fails!

[leecole]

What have I done? Compiled applications fail on this system when they sxecute a Run() statement.

Prior to this I reinstalled latest AutoIt and SciTe and AutoIt Brta.

[Zedna]

Show us your script and what exact is error message?

[leecole]

Show us your script and what exact is error message?

I don't have the script available on this system, but ALL Autoit compiled programs fail on a Run() statement on this system.

I get a AutoIt Error

Line 0 (File "D:\Program Files\AutoXvid\MediaBrowser.exe")

Run(@ScriptDir & "\AutoXvid.exe " & $a_file[1],"")

Error: Unable to execute the external program.

AutoXvid,exe is in same folder as MediaBrowser.exe.

Suddenlly, ALL AutoIt compiled programs fail to properly execute a Run(). MediaBrowser is just the simpleist of them all. It just uses a FileOpenDialog to select a *.mpg and executes AutoXvid.exe passing Drive:\Path\FileName.mpg as cmdline.

[leecole]

I don't have the script available on this system, but ALL Autoit compiled programs fail on a Run() statement on this system.

I get a AutoIt Error

Line 0 (File "D:\Program Files\AutoXvid\MediaBrowser.exe")

Run(@ScriptDir & "\AutoXvid.exe " & $a_file[1],"")

Error: Unable to execute the external program.

AutoXvid,exe is in same folder as MediaBrowser.exe.

Suddenlly, ALL AutoIt compiled programs fail to properly execute a Run(). MediaBrowser is just the simpleist of them all. It just uses a FileOpenDialog to select a *.mpg and executes AutoXvid.exe passing Drive:\Path\FileName.mpg as cmdline.

I do not believe that the installs of AutoIt, SciTe, or AutoIt Beta, has anything to do with my problem. These AutoIt programs were developed on another system, and I have verified that they do work on other systems. I guess, the sort of help, I am looking for, is internally, what does the Run() program do? For instance BAT programs exeute external programs OK, but all of a sudden, my AutoIt programs fail. Looking for help to detrmine what is fouled up!!!

[McGod]

There is no beta at this time.

[Zedna]

My opinion is that you moved your app to directory with spaces in it's name so your code:

Run(@ScriptDir & "\AutoXvid.exe " & $a_file[1],"")oÝ÷ ÚÈhºW[y«­¢+ÙIÕ¸ ÌäìÅÕ½ÐìÌäìµÀìMÉ¥ÁѥȵÀìÌäìÀäÈíÕѽaÙ¥¹áÅÕ½ÐìÌäìµÀìÀÌØí}¥±lÅt°ÅÕ½ÐìÅÕ½Ðì¤

Try to copy your app to C:\TEMP\ and try it there.

Am i right?

EDIT:

Or maybe the same problem is with your file names and need to be closed with ""

Edited February 13, 2007 by Zedna

[leecole]

My opinion is that you moved your app to directory with spaces in it's name so your code:

Run(@ScriptDir & "\AutoXvid.exe " & $a_file[1],"")oÝ÷ ÚÈhºW[y«­¢+ÙIÕ¸ ÌäìÅÕ½ÐìÌäìµÀìMÉ¥ÁѥȵÀìÌäìÀäÈíÕѽaÙ¥¹áÅÕ½ÐìÌäìµÀìÀÌØí}¥±lÅt°ÅÕ½ÐìÅÕ½Ðì¤

Try to copy your app to C:\TEMP\ and try it there.

Am i right?

EDIT:

Or maybe the same problem is with your file names and need to be closed with ""

Yes, and no. Run() works OK now, when the program being executed is in @ScripDir, but fails when It attempts to execute a program in "Program Files". Almost every program I have, uses COM or some other freature that requires a Beta compile. Has something changed in last few betas with the RUN()???? This program's Run() statements were written years ago. The primary program it executes (ALWAYS) is AutoGK.exe which always installs itself in "Program Files".

I understand how to fix this, but I feel sure that the Beta it was compiled with made a serious change to the Run().

[Valik]

First of all, did you even bother to read the post that says there is no current beta? Any beta you are using is out-dated, period. Second, do you bother to think before you accuse? If Run() were that broken, don't you think we'd, you know, have fixed it by now?

I suggest you stop trying to blame us for your incompetence and look at what has changed in your environment. All you've done so far is complain about some non-existent problem in our code but have completely neglected to show any of your code. I'm not even going to attempt to guess what non-enforced invariant has been broken on your system but I'd almost guarantee you've moved something and now the path can't be found.