The system is FC4 and the wine version is 0.9.5. The condition is wine produces a rapid string of errors when attempting to open an application. The original error is lost. I have tried redirecting by changing the redirecting '>' with both '1>' and '2>'. In any event the original error is lost out of the buffer and redirection does not work. How can the full output be captured? How can the error be identified? Thanks - Dan
On 1/17/06, Dan Sawyer <dansawyer@earthlink.net> wrote:> The system is FC4 and the wine version is 0.9.5. The condition is wine > produces a rapid string of errors when attempting to open an > application. The original error is lost. I have tried redirecting by > changing the redirecting '>' with both '1>' and '2>'. In any event the > original error is lost out of the buffer and redirection does not work. >wine app.exe >& error.log -- James Hawkins
>>>>> "Dan" == Dan Sawyer <dansawyer@earthlink.net> writes:Dan> The system is FC4 and the wine version is 0.9.5. The condition is Dan> wine produces a rapid string of errors when attempting to open an Dan> application. The original error is lost. I have tried redirecting Dan> by changing the redirecting '>' with both '1>' and '2>'. In any Dan> event the original error is lost out of the buffer and redirection Dan> does not work. What shell? "echo $SHELL". For (ba)sh and friends: WINEDEBUG=... wine <command.exe> >log 2>&1 for tcsh and friends env WINEDEBUG=... wine <command.exe> >& log -- Uwe Bonnes bon@elektron.ikp.physik.tu-darmstadt.de Institut fuer Kernphysik Schlossgartenstrasse 9 64289 Darmstadt --------- Tel. 06151 162516 -------- Fax. 06151 164321 ----------