PlayOnLinux stores the architecture used in a configuration file for each Wineprefix, and if you don't set it it could be set to amd64. You should use POL_System_SetArch 'x86' instead of export WINEARCH='win32'. Your comments at the top should have the Wine version that you are actually using. I'm not really sure what /usr/bin/env playonlinux-bash does, since all the functions are normal bash functions imported in the source command farther down. I always use #!/bin/bash at the beginning of my scripts. Looks like it's a bug in the POL website. POL_Wine wineboot -k # Kill all processes POL_Wine_WaitBefore '$TITLE' # Display generic wait message that doesn't block the script from continuing POL_Wine start /unix '$INSTALLER' # start /unix is not usually recommended but neccessary in this case

It might be easier to simply do something like this: The only problem with the way you're doing it is possibly (I don't actually know if this happens) running into problems with wineserver not closing or something. To kill ALL processes in a virtual drive, you incorperate into your scriptД«ut that's not really useful without being able to check to make sure you're not killing the installer too.

Have you actually run your script yet?ДЄs for killing GoogleUpdate.exe, I have to say I don't know an answer.

However, according to the previous article you linked to, it should work so long as the directories are already created. I don't know what kind of file the installer is, although that's what many are. For example,Д¬abextract -d '$GOOGLE_PATH' '$INSTALLER'Д«ut that only works on MS cabinet files. You might be able to use the cabextract program.

Gimp nik collection