[Wine] Odd window behaviour

[Martin Gregorie]

On Sun, 2011-08-21 at 13:38 -0500, doh123 wrote:
> I'm not really sure where the problem lies, but have you tried doing like...
> 
> 
> Code:
> wine fcw32.exe &
> 
I was about to suggest exactly the opposite. Instead, try running the
program from a wrapper script:

---------------Start of script---------------
#!/bin/bash
export WINEDEBUG=trace+file
export WINEPREFIX=$HOME/.wineprefixname
cd $HOME/path/to/directory/containing/fcw32.exe
wine fcw32.exe 2>$HOME/fcw32.log
----------------End of script----------------

Put this script anywhere, commenting out the WINEDEBUG line if you don't
need it and changing the WINEPREFIX and 'cd' lines to match your setup.
Make the script executable: "chmod u+x scriptname" and you can test run
it from the command line. 

Once its working OK and the debug information is ending up in your login
directory in a file called fcw32.log, you can make a launcher that runs
the *script* rather than the bare "wine fcw32.exe" command. This will
put the trace you need in the same place as when the script was run from
the command line.

All wine tracing and error reporting is sent to stderr, so the log file
is captured by redirecting channel 2.

Its most important that the log file name is prefixed by $HOME or the
log file will end up wherever you change directory to before running the
program.

For what its worth, I always use this approach to running programs under
wine because the convenience of debugging the wrapper script in a
terminal window vastly outweighs the work needed to create the script. 


Martin
 

 


> 
> 
> ?
> 
> The shell script should stop running and just leave the Wine process running
> 
> 
> 
>