This application automatically updates itself to the latest version.
What does not
What was not tested
Copied taskkill.exe from the bug report.
|Operating system||Test date||Wine version||Installs?||Runs?||Used|
|Current||Ubuntu 12.04 "Precise" i386 (+ variants like Kubuntu)||Jan 25 2014||1.7.11||Yes||Yes||Gold||Ken Sharp|
|Show||Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)||Jan 21 2014||1.7.11||Yes||Yes||Gold||Ken Sharp|
|Show||Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)||Oct 06 2012||1.5.14||Yes||Yes||Bronze||Ken Sharp|
|Show||FreeBSD 9.0 x86_64||Oct 06 2012||1.4.1||Yes||Yes||Bronze||Ken Sharp|
|Show||Ubuntu 12.04 "Precise" amd64 (+ variants like Kubuntu)||Jul 23 2012||1.5.6||Yes||Yes||Silver||Ken Sharp|
|Bug #||Description||Status||Resolution||Other apps affected|
|26548||GómezPEER is always visible behind other windows||NEW||View|
|26549||Add support for setting processor priority (niceness)||NEW||View|
|26550||Top shows unnamed process when running GomezPEER||NEW||View|
|31517||Gomez Peer blanks screen and does not redraw correctly in Win XP mode||NEW||View|
|39030||wineserver --persistent doesn't start up system services||NEW||View|
Tested under Wine 1.7.38.
Thanks to Kåre Baastrup for the help.
At time of writing Wine fails to set process priority. To work around this you can use the ionice and nice programs which are available for most Linux distributions (and others).
ionice -c3 nice -n19 wine "c:\\Program Files\\Gomez\\GomezPEER\\bin\\GomezPEER.exe"
or better still:
chrt -i 0 wine "c:\\Program Files\\Gomez\\GomezPEER\\bin\\GomezPEER.exe"
The background process can use 100% CPU so if you do not do this you may notice a system slowdown.
Under Windows, GomezPEER.exe runs at normal priority and java.exe runs at idle priority. You can use a script to do this if you wish but the above should be adequate.
Note: The above will also start the wineserver in idle priority, so all other Wine applications will also be given the lowest priority. If you run other Windows processes you will want to run the above last. The following shell script should offer a clue as to how to work around this problem should you later need to start a new Windows application with normal priority.