Quote:
Originally Posted by chaley
Interesting. It seems that the 'start' command creates a new process then executes the specified command in it, which would isolate a command's strange behavior.
|
Yes, the new process isolates the problem. It took me half a day to find the "start" workaround. There's a bug ticket on this, that describes another workaround from Kovid using PowerShell.
Quote:
|
My guess is that Windows 7 automatically starts subprocesses, which is why I don't have the problem.
|
That's interesting, because Vista does have the problem.
Quote:
|
There is one experiment I would like to try, but I don't have access to an XP machine. My assumption is that the '|more' is there to ensure that the next 'start' does not execute until the first one finishes.
|
Using "more" is a nice trick that I hadn't seen. Simultaneous execution was a problem with using "start." I worked around it with a less subtle hack (loop waiting for output from the command above).
Quote:
What I wonder is whether using 'start /wait web2disk ...' without piping the output through 'more' would do the same thing. If someone with XP has the time and inclination, could you try it and post the results?
|
I'd be interested in the results, too. I may test on Vista when I get a chance. Anyone who knows that this works may want to hunt up the bug report and post the "more" workaround, with the others, to keep them all in a single spot.