> That's all. > > Regards > Jose >
As you can see, there is lots of variation in results. Windows is multi-tasking. Once you do a single wait, that will often be enough for any new task to regain the cpu and do more processing, eg, to change default window captions. But it depends on what else is happening on your system ... Combining all commands meant to match a given application into a single script called from one autorun entry is a good idea. You can also use events instead of waits to get rid of delays that affect all processing. Or you could insert a single delay for all autorun entries by using * as label and then a wait command as the first entry. You pick the choice that works for you. I would not force any of these by building one into autorun processing.
