XYplorer Beta Club

I don't know what it is, but I seem to have the hardest time with the Run command for scripting. I have the 'setting' command in there to disable background processing, but yet it seems like I still need to use the 'wait' command as when I use 'run', the 'wait' portion of the 'run' command is not honored.

I really want the the line with 'run' in it to be something along the lines of: run """$current\purge.bat.lnk""", , 2; but the '2' never seems to be honored, and when I do try to use it, I get "%1 is not a valid Win32 application". Other iterations that I try seem to tell me something about Overflow 0/0. Does anyone have any help for this?
Thank you for any help that anyone can provide.

How do you add the , , 2
run """$current\purge.bat.lnk""", , 2;

Don't put it inside the quotes.
(Maybe misunderstood? And: not tested...)

Now with a bit of testing:
run "cmd /c ""$current\purge.bat.lnk""", , 2;

should really help.

By the way: what syntax is this:
set $current, <curpath>;

(Yes, I know: it's not wrong )

PeterH,

That seemed to do the trick. Never even crossed my mind to put the cmd /c option in there. Thank you so much!

Since you asked about the set $current, <curpath>; my intent was to make sure that I kept that path in case I changed directories during the file operations. But now, I may not have to do that.

Thank you again!

hermhart wrote:Since you asked about the set $current, <curpath>;

heh, I'm sure his implication was that we usually write it as: $current = <curpath>;
( or to please Peter: $current = "<curpath>"; )

This is easier to a skimming eye.

SammaySarkar wrote:

hermhart wrote:Since you asked about the set $current, <curpath>;

heh, I'm sure his implication was that we usually write it as: $current = <curpath>;

Yesss!

SammaySarkar wrote: ( or to please Peter: $current = "<curpath>"; )

This is easier to a skimming eye.

Nonono
I'd say <curpath> is a variable, and so needs no quotes.
Though quotes are allowed here, no question

D'oh!