> > Without terminal log it is unlikely that anybody will able to help > you because > terminal log from Wine often contains some clues about what might be wrong. > So > please provide this log. I quote FAQ for your convenience: > > 6. Troubleshooting > 6.1. How can I get a debugging log? > Run your application from the command (see How should I start Windows > programs > from the command line?) > You can then copy the log from the screen and paste it into a file if it's > short. > To save a log to a file, redirect the output of wine to a file using Unix > shell > redirection, e.g. > $ cd ".wine/drive_c/Games/Tron" > $ wine tron.exe > log.txt 2>&1 > > I think one problem with these instructions is some users do not have a clue what a terminal is and the instructions are not very clear on that. I know there is a FAQ entry about this but it is not linked topic 6.1 -- John M. Drescher -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winehq.org/pipermail/wine-users/attachments/20090812/c18b9bc0/attachment.htm>
