Darren New wrote:
> It works under any version of Windows you're likely to be running these
> days.

Not really.

& in a Windows prompt has a different meaning. a & b is like Unix's "a; b;"
(runs both commands, one after the other) and a && b is the same as in Unix
(runs both commands, but if a fails then b isn't run).

I have a port of Unix's "env" command that, due to a *bug*, returns
immediately and leaves the program running. I abuse that to run stuff in
the background on Windows. Either that or I start cygwin :)

Post a reply to this message