runwait with lots of parameters

[rossnixon]

Hi all, I've looked at other messages about this, honest... but how do I debug runwait?

I have executed my program OK in a batch file, but as it requires a couple of variables, I want runwait to do this.

In the batch file it looks like this (made it look generic for ease of reading):

"full_program_path" option1 option2 option3 "full_input_path" "output_filename" option4 option5 option6 option7 "input_filename"

Note: all the double quotes are expected by my program.

I used FileGetShortName to get "full_program_path" into $myProg

and have got "full_input_path into $thePath

I'm unsure about use of the ampersand and single quotes in this:

RunWait(@ComSpec & ' /c ' & $myProg 'option1 option2 & $thePath "output_filename" option4 option5 option6 option7 "input_filename"')

Can anyone spot incorrect use of & ' " or space characters?

Or is there a way to spot error messages before runwait closes? Thanks.

[Valuater]

Autoit Wrappers to the rescue!!!

See " Examples of using @Comspec "

http://www.autoitscript.com/forum/index.ph...st&p=133769

8)

[MHz]

Can anyone spot incorrect use of & ' " or space characters?

Or is there a way to spot error messages before runwait closes? Thanks.

The highlighting in a editor picks up errors like Scite4AutoIt3.

RunWait(@ComSpec & ' /c "' & $myProg & '" option1 option2 "' & $thePath & '" "output_filename" option4 option5 option6 option7 "input_filename"')

Use /k switch instead of /c to keep window open for debugging purposes.

Edited May 3, 2007 by MHz

[rossnixon]

The highlighting in a editor picks up errors like Scite4AutoIt3.

(snip answer)

Use /k switch instead of /c to keep window open for debugging purposes.

Thanks, with your example and a little tweaking I got it working, thanks.

I like EDXOR as an editor, but will try Scite4AutoIt3 if I get similar problems next time.

I hereby recommend that MHz be promoted to GHz for his valuable help to newbies!