On Mon, 2009-10-26 at 18:03 -0500, flyfisherman wrote: > "c:\program files\sierra\fear\fear.exe" &> log.txt > Here's the problem -----------------------^ The '&' shouldn't be there. In this context it starts the preceding command running in the background and immediately prompts for another command if its at the end of the line. If its not the last character in the line, the rest of the line is interpreted as a command. In this case the command > log.txt was after it and was executed. This creates a file called 'log.txt' and redirects nothing into it because there's nothing to the left of the > to redirect. If you'd written this: wine "c:\program files\sierra\fear\fear.exe" >log.txt it would have done what you intended - run fear.exe with stdout (shorthand for "standard output") redirected into log.txt. If stuff was written to the stderr, the standard error file, you'd see it on the console. If you wanted to capture it too in a separate file, wine "c:\program files\sierra\fear\fear.exe" >log.txt 2>errlog.txt would do the trick, while if you wanted it all in one file you'd use wine "c:\program files\sierra\fear\fear.exe" 2>&1 >logfile.txt which is the only other way you'd normally use '&' on a command line. Martin > > >
