That's a good approach Martin. Here is a single generalized version of your script that can be used to run any of many Windows programs. In addition to the ability to work with various programs, it includes some comments and the ability to restore the initial working directory upon completion.
<code>
#!/bin/bash
# usage: I install this executable script as $HOME/bin/runwine
# To run the Windows program e-sword I simply type runwine e-sword
# or I click a graphic shortcut that does that.
export WINEPREFIX=$HOME/.wine_${1}
pushd $WINEPREFIX/Program Files/${1}
wine ${1}.exe
popd
</code>
This script can be made more robust by adding a couple of validity tests and more flexible by supporting command line parameters to be passed to the Windows program.
--
Jim
-----Original Message-----
From: Martin Gregorie <martin@xxxxxxxxxxxx>
To: wine-users@xxxxxxxxxx
Sent: Wed, 02 Apr 2014 7:16
Subject: Re: uninstalling something that didn't work
---->8====
I never use the default prefix. I always create a separate prefix for
each app or group of related programs and always launch Wine apps with a
small shell script. In the following example the script, which has four
lines, is called myapp and runs a Windows app called MyApp, whose
installer put it in C:\Program Files\MyApp within a wine prefix
called .wine_myapp:
#!/bin/bash
export WINEPREFIX=$HOME/.wine_myapp
cd $WINEPREFIX/Program Files/MyApp
wine myapp.exe
After you've written the script it should be made executable:
chmod u+x myapp
and then to command "myapp" should run the Windows app. You can run it
from the command line (useful for debugging) make a KDE launcher to run
it.
The advantage if this is both that you can easily get rid of an app or
Windows program you no longer want and that some apps may need DLLs or
Windows versions that prevent other apps from running if they are all in
the same prefix. If they are in separate prefixes they can't interfere
with each other.
HTH
Martin
