PlayOnLinux - User contributions [en]

How to Read Debug Logs

2020-10-28T19:15:32Z

Dadu042: /* Read the debug log */

== Get the debug log (from POL v4) ==
To access the debug log of a POL compatible software, in the main GUI click on the name of the software, then on the left side click the 'Debug' button.

On the right side appears the debug of the last uses. You may copy/paste the latest one to show it to someone else.

== Debug mode ==

=== Folders location ===
There is two folders where you can find POL/POM log files:
* /home/you/.PlayOnLinux/logs/game_name/ is the place where is store the '''installation log file''' when the game (or any software) is installed. This is the file to look at if the installation failed.
* /home/you/PlayOnLinux's virtual drives/game_name/ is the place where is stored the '''log file of the game/software when launched/running'''. Note: you can delete this file, it will be recreated automatically each time you run (or try to) the software.

=== Debug flags ===
It is possible to hide all Wine errors: "Debug Flags: -all". This avoid the size of the log file to increase, and (sometimes) avoid some slowness for the storage device.

Examples:
* "fixme-all"
* "-all,fixme-all"
* "-d3d"

See also: [https://wiki.winehq.org/Debug_Channels Debug flags listed on the Wiki of winehq.org].

== Read the debug log ==

=== Error related to Wine ('Unhandled page fault on read access ...', 'Unhandled exception: page fault ...') ===
Example:
{{Console|
wine: Unhandled page fault on read access to 0x00000008 at address 0x43adae (thread 0009), starting debugger...

Unhandled exception: page fault on read access to 0x00000008 in 32-bit code (0x0043adae).

Register dump:

CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b

EIP:0043adae ESP:0032fd40 EBP:00b90004 EFLAGS:00210202( R- -- I - - - )

EAX:00000032 EBX:00000000 ECX:00000000 EDX:0000fffe

ESI:00a8df82 EDI:00a8df9e

Stack dump:

0x0032fd40: 00439cf4 00a8df9e 00b9cccc 00000000

0x0032fd50: 00439bb4 0032fd88 00abceca 00000102

0x0032fd60: 0000013c 00000020 0043778c 00437848

0x0032fd70: 00000000 00000001 10042134 10042130

0x0032fd80: 00000001 0032fd90 00000006 00416611

0x0032fd90: 004452d6 00000000 00000001 00000001

Backtrace:

...
}}

For this kind of error log, the issue (it's a internal crash) is related to Wine not to POL.

Here are the best steps to follow:
# Try to use a newer Wine version inside POL (try up to the latest stable available in POL).
# If the issue occurs when installing the software you want, you may try to use a newer Wine version but this need some manual operations: copy the script (if from our website, find it into 'supported software') into a '.pol' (text) file. Edit it with a [https://en.wikipedia.org/wiki/Text_editor text editor] software in order to change the Wine version, save it. From POL, do load the script as a file (Menu 'Tools' -> 'Run a local script').
# After the tests above, you may search for help at https://winehq.org Note: the Playonlinux log will '''not be accepted''' there. You will have to reproduce the issue with Wine only (with a recent Wine version), in order to get a clean log.

=== Error related to Microsoft Dotnet ===

The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, ...' or one of its dependencies.

This error message in the log mean that installation of Microsoft DotNet 4.0 is required.

=== X3DAudio ===
{{Console|
002c:err:module:load_builtin_dll failed to load .so lib for builtin L"X3DAudio1_7.dll": libFAudio.so.0:
}}

Should (POL v4, 2019) be fixable by installing: [https://www.playonlinux.com/fr/app-635-POL_Install_xact.html POL_Install_xact]

=== Missing files ===

File(s) missing in your OS:

{{Console|
DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
}}

In this example DOS is missing the file 'libpng12.so.0' in your OS (for this file, look: [[Troubleshooting Common Problems]]).

== See also ==
* [[Troubleshooting Common Problems]]

Manual Installations

2020-08-22T21:10:22Z

Dadu042: /* An important step */

== Warning ==
Doing a manual installation is the '''hard way''' to use Playonlinux/Playonmac.

The easy way is to use a script already wrote by someone else (do search first into the 'Supported software' list, then in the forums), because the application that you want to use may need some additional libraries and it is very hard to know which ones.

== Was your software already tested with Wine by other users ? ==
If a software does not work with Wine, usually it will not work with Playonlinux/Playonmac.

Before to waste time, look first into https://appdb.winehq.org (at left side of the screen, click : 'Browse Apps'). 
In the test reports you may find informations about:
* Wine versions tested
* Software components used by the software (ie: [https://en.wikipedia.org/wiki/.NET_Framework Microsoft DotNet Framework], DirectX 10)
* [https://en.wikipedia.org/wiki/Middleware Middleware(s)] used by the software (ie: [https://en.wikipedia.org/wiki/Unity_(game_engine)|Unity Game Engine]).
* Missing [[Common Linux Libraries That Wine Might Need|common Linux Libraries that Wine might need]].

You may also look at the compatibility reports list of other projects using Wine such as:
* [https://pcgamingwiki.com/ pcgamingwiki.com] is also a fast way to find technical informations about games.
* The installation [http://www.gamersonlinux.com/forum/forums/guides.20/ guides hosted on Gamers on Linux.com].
* [https://lutris.net/ Lutris] (not commercial, run by enthusiasts. [https://en.wikipedia.org/wiki/Lutris Wikipedia]). Note: if you find the software you want, click 'View install script', then the button 'Download' ('the script'), this will show you the details about the tricks used by Lutris.
* [https://www.codeweavers.com/compatibility/ CodeWeavers] (pro support for Wine, commercial. [https://en.wikipedia.org/wiki/CodeWeavers Wikipedia])
* [https://github.com/PhoenicisOrg/scripts/tree/master/Applications POL v5 (Phoenicis)] scripts. Note: this software is still in [https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha Alpha version] state. Note: the scripts code will be completely different from POL v4.

== How to ==
=== In POL click the button 'Install' ===
At the bottom left of the window, click 'Install a non-listed program'.

=== An important step ===
This window is very important : ''''What would you like to do before installation ?'''' ([http://www.gamersonlinux.com/forum/attachments/acthree05-png.17168/ screenshot]) because it can allow :
* 'Use another version of Wine' (a version different from the ones that your POL installation already has).
* 'Configure Wine' (advanced setting, forcing Set_OS, ...).
* 'Install some libraries' (by using [[Components and Functions|POL/POM components and functions]] or [https://en.wikipedia.org/w/index.php?title=Winetricks WineTricks]).

=== Lots of steps ===
... Write me... (or look some examples tutorials already wrote for other softwares).

=== If your software requires Winetricks or POL libraries ===
[http://www.gamersonlinux.com/forum/attachments/acthree11-png.17174/ (screenshot example)]

* [https://www.playonlinux.com/en/supported_apps-100-0.html Details about the Playonlinux packages] (in the wiki, called 'Category: Features').

=== Shortcuts for the software installed ===
At the end of the manual installation, POL show you the list of .EXE files found in order to make shortcuts. Take the time to select carefully the files needed (you will be allow later to delete the useless shortcuts).

== Troubleshooting ==
If a application do not work, do not forget that you can try a other (install a newer) version of Wine. This is very useful for the old tutorials found on the web, Wine receive improvements and bug fixes.

== External links ==
* [http://www.gamersonlinux.com/forum/forums/guides.20/ www.gamersonlinux.com/] : Many examples of manual installations (called there 'step by step')

Troubleshooting Common Problems

2020-06-15T07:33:50Z

Dadu042: /* libFaudio.so.0 (libFaudio) */ Add Ubuntu 20.04

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

PlayOnLinux users, if winbind is not installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== PlayOnLinux ====

Do install WinBind.

Example on Ubuntu 18.xx : From Terminal, do type: 'sudo apt install winbind'.

==== PlayOnMac Edit the Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround (examples):
* Ubuntu 20.04:
{{Console|
sudo apt install libfaudio0
}}
* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

=== Vulkan missing ===

{{Console|0055:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
0055:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
}}

This mean that a Vulkan file [https://en.wikipedia.org/wiki/Vulkan_(API) (Wikipedia)] is not installed.

Fix:
* Look at: [https://github.com/lutris/docs/blob/master/InstallingDrivers.md this page].

=== Xterm missing ===

POL v4 need this software.

Fix: install it from the packages manager of your OS.

Example on Ubuntu (command line to type into a Terminal software):
<pre class='code bash'>
sudo apt install xterm
</pre>

=== libodbc.so ===

{{Console|ODBC_LoadDriverManager failed to open library "libodbc.so"}}

Fix: install it from the packages manager of your OS.

Example on Ubuntu (command line to type into a Terminal software):
<pre class='code bash'>
sudo apt install unixodbc
</pre>

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the FreeType font ([https://en.wikipedia.org/wiki/FreeType Wikipedia]) is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22 (you may need to read in this page: 'About a script stored in 'Supported software', how to install it with a newer Wine version ?').

Components and Functions

2020-06-09T08:55:57Z

Dadu042: /* mdac28 */

Details, use cases, related errors, and more on each component.

== POL/POM Configuration -> Display ==

These commands allow to script the [[The_Configuration_Window#Display_tab|display settings available in the GUI]].

=== GLSL Support ===
Default setting (2019) is "enabled".

=== DirectDraw Renderer ===
Default setting (2019) is "opengl".

'''Script/Shell command:'''
<pre class="playonlinux code">
POL_Wine_Direct3D "DirectDrawRenderer" "gdi"
</pre>

=== Video memory size ===
See [[Scripting_-_Chapter_11:_List_of_Functions#POL_SetupWindow_VMS_.284.0.2B.29|this page about the command 'POL_SetupWindow_VMS']].

=== Offscreen rendering mode ===

== AdobeAir ==

'''What is it?'''

"The Adobe AIR runtime enables developers to package the same code into native applications and games for Windows and Mac OS desktops as well as iOS and Android devices, reaching over a billion desktop systems and mobile app stores for over 500 million devices."

-from http://get.adobe.com/air/

'''What does it do?'''

Installs the Adobe Air package.

'''When would I need it?'''

Certain Adobe products require this to be installed as a dependency.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_AdobeAir
</pre>

'''Links:'''

http://get.adobe.com/air/

== amstream ==

'''What is it?'''

A installer for a library.

'''What does it do?'''

Installs on Windows a Microsoft library, part of [https://en.wikipedia.org/wiki/DirectShow DirectShow].

'''When would I need it?'''

Some games/apps made after the 1990's and before the 2010's, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_amstream
</pre>

== ATI_Black-Screen_Fix ==

POL_Call POL_Install_ATI_Black-Screen_Fix

== atmlib ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs 'Adobe Type Manager'.

'''When would I need it?'''

[https://en.wikipedia.org/wiki/Adobe_Type_Manager Wikipedia].

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_atmlib
</pre>

== cc580 ==

POL_Call POL_Install_cc580

== CentralizedUserDirs ==

POL_Call POL_Install_CentralizedUserDirs

== corefonts ==

'''What is it?'''

"TrueType is an outline font standard developed by Apple and Microsoft in the late 1980s as a competitor to Adobe's Type 1 fonts used in PostScript. It has become the most common format for fonts on both the Mac OS and Microsoft Windows operating systems."

from http://en.wikipedia.org/wiki/TrueType

'''What does it do?'''

Downloads and registers TrueType fonts (TTF). Here is a list of the fonts that will be installed into the given virtual drive:

* andale mono
* arial black
* arial (bold, italic, bold italic)
* comic sans ms (bold)
* courier new (bold, italic, bold italic)
* georgia (bold, italic, bold italic)
* impact
* times new roman (bold, italic, bold italic)
* trebuchet (bold, italic, bold italic)
* verdana (bold, italic, bold italic)
* webdings

'''When would I need it?'''

Any time you experience missing text in an application, this would be the first place you would want to start. This is usually installed by default, though. If this does not work, try '''tahoma''' or '''tahoma2''' from the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Install Components tab], as those are the usual suspects in such acts of font thievery.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_corefonts
</pre>

'''Links:'''

http://en.wikipedia.org/wiki/TrueType

== crypt32 ==

'''What is it?'''

''crypt32'' does quite a few things relating to decrypting/encrypting data. Basic information in the links below.

'''What does it do?'''

"It supports encryption, decryption, and manipulation of certificates and related data structures."

from http://wiki.winehq.org/Crypt32

'''When would I need it?'''

Most of this is taken care of within Wine via the ''builtin'' dll. You may run into times when the native dll is needed, in which case the POL debug log will spit out an error saying that it tried to do something with it and it failed (like ''unhandled exception'' or ''cannot find crypt32.dll'', etc.). If you do happen to run into an error like this, we highly encourage you to report it to https://appdb.winehq.org so that the community there can possibly implement a fix that is native to Wine, eliminating the need for the actual Windows dll.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_crypt32
</pre>

'''Links:'''

http://wiki.winehq.org/Crypt32

== dcom98 ==

Microsofts's [https://en.wikipedia.org/wiki/Distributed_Component_Object_Model Distributed Component Object Model], 1998.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_dcom98
</pre>

== DirectX ==

=== d3dcompiler_43 ===

POL_Call POL_Install_d3dcompiler_43

=== d3dx10 ===

POL_Call POL_Install_d3dx10

=== d3dx11 ===

POL_Call POL_Install_d3dx11

=== d3dx9 ===

POL_Call POL_Install_d3dx9

=== d3dx9_29 ===

POL_Call POL_Install_d3dx9_29

=== d3dx9_35 ===

POL_Call POL_Install_d3dx9_35

=== d3dx9_36 ===

POL_Call POL_Install_d3dx9_36

=== d3dx9_40 ===

POL_Call POL_Install_d3dx9_40

=== d3dx9_42 ===

POL_Call POL_Install_d3dx9_42

=== d3dx9_43 ===

'''What is it?'''

A installer for a library.

'''What does it do?'''

Installs the Windows library, part of [https://en.wikipedia.org/wiki/DirectX DirectX] 9 version 43 (the latest is the better).

'''When would I need it?'''

Some games/apps made for DirectX up to version 9, if these don't work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_d3dx9_43
</pre>

=== dinput8 ===

POL_Call POL_Install_dinput8

=== directmusic ===

POL_Call POL_Install_directmusic

=== directplay ===

POL_Call POL_Install_directplay

=== directx9 ===

POL_Call POL_Install_directx9

=== dinput ===

POL_Call POL_Install_dinput

=== dsound ===

POL_Call POL_Install_dsound

=== dxdiag ===

POL_Call POL_Install_dxdiag

=== dxfullsetup ===

POL_Call POL_Install_dxfullsetup

== Desura ==

POL_Call POL_Install_desura

== devenum ==

POL_Call POL_Install_devenum

== DisableCrashDialog ==

POL_Call POL_Install_DisableCrashDialog

== DosboxDrive ==

POL_Call POL_Install_DosboxDrive

== .NET ==

=== POL_Install_dotnet11 ===

=== POL_Install_dotnet11sp1 ===

=== POL_Install_dotnet20 ===

=== POL_Install_dotnet20sp1 ===

=== POL_Install_dotnet20sp2 ===

=== POL_Install_dotnet30 ===

=== POL_Install_dotnet30sp1 ===

=== POL_Install_dotnet35 ===

=== POL_Install_dotnet35sp1 ===

=== POL_Install_dotnet40 ===

== fakeie6 ==

'''What is it?'''

A installer for a audio/video library.

'''What does it do?'''

This let the OS think that Microsoft IE 6 is installed.

'''When would I need it?'''

Only for some games/apps that want IE 6.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_fakeie6
</pre>

== ffdshow ==

'''What is it?'''

A installer for a audio/video library.

'''What does it do?'''

Installs a codecs library, '[https://en.wikipedia.org/wiki/Ffdshow ffdshow]' (2014), in order to encode/decode audio/video files.

'''When would I need it?'''

Some games/apps that use audio/video files encoded by codecs supported by ffdshow.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_ffdshow
</pre>

== flashplayer ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs [https://en.wikipedia.org/wiki/Adobe_Flash_Player Adobe Flash Player files].

'''When would I need it?'''

Some games/apps that use files made with Adobe Flash (was quite common in the 2000's, mainly for web games).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_flashplayer
</pre>

== Flashplayer_ActiveX ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft's [https://en.wikipedia.org/wiki/ActiveX ActiveX] files (it was a competitor of Adobe Flash), up to the 2000's.

'''When would I need it?'''

Some games/apps that use files made with ActiveX (was quite common in the 2000's, mainly for web games and web apps).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_Flashplayer_ActiveX
</pre>

== FontsSmoothBGR ==

POL_Call POL_Install_FontsSmoothBGR

== FontsSmoothGrayScale ==

POL_Call POL_Install_FontsSmoothGrayScale

== FontsSmoothRGB ==

POL_Call POL_Install_FontsSmoothRGB

== gdiplus ==

'''What is it?'''

A installer.

'''What does it do?'''

Set Microsoft's [https://en.wikipedia.org/wiki/Graphics_Device_Interface Graphics Device Interface] graphic rendering mode.

'''When would I need it?'''

Some games/apps made up to the 2000's. Mainly when there is graphic rendering issues.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gdiplus
</pre>

== gecko ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Wine's fake version of Internet Explorer (implementation is based on a custom version of [https://en.wikipedia.org/wiki/Gecko_(software) Mozilla's Gecko]).

'''When would I need it?'''

Some games/apps made in the 2000's. Mainly when there is graphic issues.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gecko
</pre>

'''Link'''

[https://wiki.winehq.org/Gecko Gecko] described on winehq.org

== gfwl ==

'''What is it?'''

A installer.

'''What does it do?'''

Let the OS think that Games for Windows Live ([https://en.wikipedia.org/wiki/Games_for_Windows_%E2%80%93_Live Wikipedia]) is correctly working.

'''When would I need it?'''

Required by some games/apps made in the 2010's.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gfwl
</pre>

== gfwl86 ==

POL_Call POL_Install_gfwl86

== HackSteam ==

POL_Call POL_Install_HackSteam

== ie6 ==

POL_Call POL_Install_ie6

== ie8 ==

POL_Call POL_Install_ie8

== iv50 ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Intel's [https://en.wikipedia.org/wiki/Indeo Indeo] library.

'''When would I need it?'''

Some games/apps made in the 1990's up to 2000's, using video files encoded with Indeo.

'''Script/Shell command:'''

<pre class="playonlinux code">

POL_Call POL_Install_iv50
</pre>

== linuxtrack-wine ==

POL_Call POL_Install_linuxtrack-wine

== LunaTheme ==
Installs a [https://en.wikipedia.org/wiki/Windows_XP_visual_styles Windows XP style] (theme) named Luna.

POL_Call POL_Install_LunaTheme

== mdac28 ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft Data Access Components ([https://en.wikipedia.org/wiki/Microsoft_Data_Access_Components Wikipedia]).

'''When would I need it?'''

Some games/apps made in the 1990's up to ~2005. Mainly for apps that use a database in the background.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_mdac28
</pre>

== mfc ==

[https://en.wikipedia.org/wiki/Microsoft_Foundation_Class_Library Microsoft Foundation Class Library], a programming library for C++.

=== POL_Install_mfc40 ===
(1995)

=== POL_Install_mfc42 ===
(1998)

== Mono ==

[https://en.wikipedia.org/wiki/Mono_(software) Mono (Wikipedia)] is an open source implementation of the [https://en.wikipedia.org/wiki/Common_Language_Infrastructure Common Language Infrastructure] (.NET).

=== POL_Install_mono210 ===
v2.10 released in 2011.

=== POL_Install_mono26 ===

=== POL_Install_mono28 ===

== msasn1 ==

POL_Call POL_Install_msasn1

== msls31 ==

[https://www.playonlinux.com/fr/app-522-POL_Install_msls31.html POL_Call POL_Install_msls31]

'Microsoft LS' (Unix ls command for Microsoft).

== msvc ==

=== POL_Install_msvc100 ===

=== POL_Install_msvc80 ===

=== POL_Install_msvc90 ===

== msxml ==

=== POL_Install_msxml3 ===

=== POL_Install_msxml4 ===

=== POL_Install_msxml6 ===
'''What is it?'''

A installer for XML libraries.

'''What does it do?'''

Install Microsoft [https://en.wikipedia.org/wiki/MSXML MSXML] v6 (2005).

'''When would I need it?'''

Games/apps made before the 2010's years, that use XML files, for example to store text to displays or settings.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_msxml6
</pre>

== nop ==

POL_Call POL_Install_nop

== physx ==

POL_Call POL_Install_physx

== pngfilt ==

POL_Call POL_Install_pngfilt

== PrivateUserDirs ==

POL_Call POL_Install_PrivateUserDirs

== quartz ==

POL_Call POL_Install_quartz

== RegisterFonts ==

POL_Call POL_Install_RegisterFonts

== riched20 ==

=== POL_Install_riched20 ===

=== POL_Install_riched30 ===

== rsc ==

POL_Call POL_Install_rsc

== steam ==

'''What is it?'''

An installer for the game publishing platform Steam.

'''What does it do?'''

Downloads and Installs Steam client.

'''When would I need it?'''

Any time a game requires Steam to run.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_steam
</pre>

'''Links:'''

http://store.steampowered.com/

== steam_flags ==

'''What is it?'''

A helper script for Steam.

'''What does it do?'''

Set registry third-party flags to avoid steam installing them at the game's first launch.

'''When would I need it?'''

To avoid Steam reinstalling POL-installed dependencies (Wine sometimes requires some ''wizardry'' to get things working that the stock installers do not do, and can cause the application not to run if the workaround is overwritten or broken by the default installation being triggered by the Steam client.).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_steam_flags
</pre>

'''Links:'''

https://www.playonlinux.com/en/app-927-POL_Install_steam_flags.html

== tahoma ==

'''What is it?'''

An installer for the Microsoft font ''Tahoma''.

'''What does it do?'''

Downloads and registers ''Tahoma''.

'''When would I need it?'''

Any time the ''Tahoma'' font is needed.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_tahoma
</pre>

'''Links:'''

http://www.microsoft.com/typography/fonts/family.aspx?FID=19

== tahoma2 ==

'''What is it?'''

An alternative installer for the Microsoft font ''Tahoma''.

'''What does it do?'''

Downloads and registers Tahoma, but from a different package.

'''When would I need it?'''

Any time the ''Tahoma'' font is needed, where the regular ''Tahoma'' installer does not work (like Photoshop CS6).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_tahoma2
</pre>

'''Links:'''

http://www.microsoft.com/typography/fonts/family.aspx?FID=19

== ubigamelauncher ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs the Ubisoft's game launcher.

'''When would I need it?'''

Some games released by [https://en.wikipedia.org/wiki/Ubisoft Ubisoft].

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_ubigamelauncher
</pre>

== vbrun6 ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs [https://en.wikipedia.org/wiki/Visual_Basic Microsoft Visual Basic] v6 libraries (app last released in 1998).

'''When would I need it?'''

Some games/apps made after 1990, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_vbrun6
</pre>

== vcrun ==

=== POL_Install_vcrun2005 ===

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft Visual C++ libraries.

'''When would I need it?'''

Some games/apps made after 2003, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_vcrun2005
</pre>

=== POL_Install_vcrun2008 ===

=== POL_Install_vcrun2010 ===

=== POL_Install_vcrun2012 ===

=== POL_Install_vcrun2013 ===

=== POL_Install_vcrun6 ===

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft Visual C v6 (1989) libraries.

'''When would I need it?'''

Some games/apps made after 1988, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_vcrun6
</pre>

== VideoDriver ==

'''What is it?'''

A window does open and ask to select among the video cards installed. If there is only one video card, nothing happen.

'''What does it do?'''

Edit the Windows registry.

'''When would I need it?'''

If there is 2 video cards on the computer (ie: gaming notebooks, with a Intel iGPU + AMD GPU).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_VideoDriver
</pre>

== wine64b ==

Old command (before POL/POM v4).

POL_Call POL_Install_wine64b

== wineasio ==

'''What is it?'''

WineASIO provides an ASIO driver interface from Wine to jack for low-latency audio and advanced audio/MIDI routing.

'''What does it do?'''

Checks for the following:

* Checks that the virtual drive is 32-bit

* Makes sure that the user is part of the ''audio'' group

* Confirms the presence of ''jack'' and ''qjackctl''

Then, if all checks pass, WineASIO is downloaded and registered into that virtual drive.

'''When would I need it?'''

Certain Adobe products require this to be installed as a dependency.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wineasio
</pre>

'''Links:'''

http://sourceforge.net/projects/wineasio/

== winhttp ==

'''What is it?'''

Install a HTTP library.

'''What does it do?'''

Install some Windows files.

'''When would I need it?'''

Apps made before the 2010's years.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_winhttp
</pre>

== wininet ==

POL_Call POL_Install_wininet

== wintrust ==

POL_Call POL_Install_wintrust

== wmp10 ==

POL_Call POL_Install_wmp10

== wmp9 ==

'''What is it?'''

A installer.

'''What does it do?'''

Install Windows Media Player 9 (~2003).

'''When would I need it?'''

Games/apps made before the 2010's years, that use .WMV video files or .WMA audio files.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wmp9
</pre>

== wmpcodecs ==

'''What is it?'''

A installer.

'''What does it do?'''

Install Windows Media Player (v9) codecs (audio + video).

'''When would I need it?'''

Games/apps made before the 2010's years, that use .WMV video files or .WMA audio files.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wmpcodecs
</pre>

== wsh56 ==

POL_Call POL_Install_wsh56

== wsh57 ==

POL_Call POL_Install_wsh57

== xact ==

'''What is it?'''

A installer for audio libraries.

'''What does it do?'''

Installs Microsoft '[https://en.wikipedia.org/wiki/Cross-platform_Audio_Creation_Tool Cross-platform Audio Creation Tool]' (2002).

'''When would I need it?'''

Games/apps made before the 2010's years.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_xact
</pre>

== xinput ==

POL_Call POL_Install_xinput

== xmllite ==

'''What is it?'''

A installer for XML libraries.

'''What does it do?'''

Install Microsoft [https://en.wikipedia.org/wiki/MSXML MSXML] (2000's).

'''When would I need it?'''

Games/apps made before the 2010's years, that use XML files, for example to store text to displays or settings.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_xmllite
</pre>

== xna31 ==

POL_Call POL_Install_xna31

== xna40 ==

POL_Call POL_Install_xna40

== xvid ==

POL_Call POL_Install_xvid

== Other Functions ==

=== POL_Configurator_runparts ===

POL_Call POL_Configurator_runparts

=== POL_Download_retry ===

POL_Call POL_Download_retry

=== POL_Function_FontsSmoothBGR ===

POL_Call POL_Function_FontsSmoothBGR

=== POL_Function_FontsSmoothGrayScale ===

POL_Call POL_Function_FontsSmoothGrayScale

=== POL_Function_FontsSmoothRGB ===

POL_Call POL_Function_FontsSmoothRGB

=== POL_Function_NoCDWarning ===

'''What is it?'''

A warning message for the user of a script.

'''What does it do?'''

Does warn that the game/app will not work without a way to workaround the DRM (NoCD or other).

'''When would I need it?'''

To warn when a game can not work with POL/POM script without a NoCD.
Some DRMs does not work with Wine, originals CDs/DVDs are not recognized.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Function_NoCDWarning
</pre>

=== POL_Function_override_app_dlls ===

POL_Call POL_Function_override_app_dlls

=== POL_Function_OverrideDLL ===

POL_Call POL_Function_OverrideDLL

=== POL_Function_RootCommand ===

POL_Call POL_Function_RootCommand

=== POL_Function_sandbox ===

POL_Call POL_Function_sandbox

=== POL_Function_SetNativeExtension ===

POL_Call POL_Function_SetNativeExtension

=== POL_Function_simplecdscript ===

POL_Call POL_Function_simplecdscript

=== POL_Function_simplescript ===

POL_Call POL_Function_simplescript

=== POL_Function_Sleep ===

POL_Call POL_Function_Sleep

=== POL_Gamefront_Download ===

POL_Call POL_Gamefront_Download

=== POL_GetTool_samba3 ===

POL_Call POL_GetTool_samba3

=== POL_GoG_download ===

POL_Call POL_GoG_download

=== POL_GoG_Extract ===

POL_Call POL_GoG_Extract

=== POL_GoG_install ===

POL_Call POL_GoG_install

=== POL_GoG_setup ===

POL_Call POL_GoG_setup

Components and Functions

2020-06-09T08:54:07Z

Dadu042: /* gfwl */

Details, use cases, related errors, and more on each component.

== POL/POM Configuration -> Display ==

These commands allow to script the [[The_Configuration_Window#Display_tab|display settings available in the GUI]].

=== GLSL Support ===
Default setting (2019) is "enabled".

=== DirectDraw Renderer ===
Default setting (2019) is "opengl".

'''Script/Shell command:'''
<pre class="playonlinux code">
POL_Wine_Direct3D "DirectDrawRenderer" "gdi"
</pre>

=== Video memory size ===
See [[Scripting_-_Chapter_11:_List_of_Functions#POL_SetupWindow_VMS_.284.0.2B.29|this page about the command 'POL_SetupWindow_VMS']].

=== Offscreen rendering mode ===

== AdobeAir ==

'''What is it?'''

"The Adobe AIR runtime enables developers to package the same code into native applications and games for Windows and Mac OS desktops as well as iOS and Android devices, reaching over a billion desktop systems and mobile app stores for over 500 million devices."

-from http://get.adobe.com/air/

'''What does it do?'''

Installs the Adobe Air package.

'''When would I need it?'''

Certain Adobe products require this to be installed as a dependency.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_AdobeAir
</pre>

'''Links:'''

http://get.adobe.com/air/

== amstream ==

'''What is it?'''

A installer for a library.

'''What does it do?'''

Installs on Windows a Microsoft library, part of [https://en.wikipedia.org/wiki/DirectShow DirectShow].

'''When would I need it?'''

Some games/apps made after the 1990's and before the 2010's, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_amstream
</pre>

== ATI_Black-Screen_Fix ==

POL_Call POL_Install_ATI_Black-Screen_Fix

== atmlib ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs 'Adobe Type Manager'.

'''When would I need it?'''

[https://en.wikipedia.org/wiki/Adobe_Type_Manager Wikipedia].

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_atmlib
</pre>

== cc580 ==

POL_Call POL_Install_cc580

== CentralizedUserDirs ==

POL_Call POL_Install_CentralizedUserDirs

== corefonts ==

'''What is it?'''

"TrueType is an outline font standard developed by Apple and Microsoft in the late 1980s as a competitor to Adobe's Type 1 fonts used in PostScript. It has become the most common format for fonts on both the Mac OS and Microsoft Windows operating systems."

from http://en.wikipedia.org/wiki/TrueType

'''What does it do?'''

Downloads and registers TrueType fonts (TTF). Here is a list of the fonts that will be installed into the given virtual drive:

* andale mono
* arial black
* arial (bold, italic, bold italic)
* comic sans ms (bold)
* courier new (bold, italic, bold italic)
* georgia (bold, italic, bold italic)
* impact
* times new roman (bold, italic, bold italic)
* trebuchet (bold, italic, bold italic)
* verdana (bold, italic, bold italic)
* webdings

'''When would I need it?'''

Any time you experience missing text in an application, this would be the first place you would want to start. This is usually installed by default, though. If this does not work, try '''tahoma''' or '''tahoma2''' from the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Install Components tab], as those are the usual suspects in such acts of font thievery.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_corefonts
</pre>

'''Links:'''

http://en.wikipedia.org/wiki/TrueType

== crypt32 ==

'''What is it?'''

''crypt32'' does quite a few things relating to decrypting/encrypting data. Basic information in the links below.

'''What does it do?'''

"It supports encryption, decryption, and manipulation of certificates and related data structures."

from http://wiki.winehq.org/Crypt32

'''When would I need it?'''

Most of this is taken care of within Wine via the ''builtin'' dll. You may run into times when the native dll is needed, in which case the POL debug log will spit out an error saying that it tried to do something with it and it failed (like ''unhandled exception'' or ''cannot find crypt32.dll'', etc.). If you do happen to run into an error like this, we highly encourage you to report it to https://appdb.winehq.org so that the community there can possibly implement a fix that is native to Wine, eliminating the need for the actual Windows dll.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_crypt32
</pre>

'''Links:'''

http://wiki.winehq.org/Crypt32

== dcom98 ==

Microsofts's [https://en.wikipedia.org/wiki/Distributed_Component_Object_Model Distributed Component Object Model], 1998.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_dcom98
</pre>

== DirectX ==

=== d3dcompiler_43 ===

POL_Call POL_Install_d3dcompiler_43

=== d3dx10 ===

POL_Call POL_Install_d3dx10

=== d3dx11 ===

POL_Call POL_Install_d3dx11

=== d3dx9 ===

POL_Call POL_Install_d3dx9

=== d3dx9_29 ===

POL_Call POL_Install_d3dx9_29

=== d3dx9_35 ===

POL_Call POL_Install_d3dx9_35

=== d3dx9_36 ===

POL_Call POL_Install_d3dx9_36

=== d3dx9_40 ===

POL_Call POL_Install_d3dx9_40

=== d3dx9_42 ===

POL_Call POL_Install_d3dx9_42

=== d3dx9_43 ===

'''What is it?'''

A installer for a library.

'''What does it do?'''

Installs the Windows library, part of [https://en.wikipedia.org/wiki/DirectX DirectX] 9 version 43 (the latest is the better).

'''When would I need it?'''

Some games/apps made for DirectX up to version 9, if these don't work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_d3dx9_43
</pre>

=== dinput8 ===

POL_Call POL_Install_dinput8

=== directmusic ===

POL_Call POL_Install_directmusic

=== directplay ===

POL_Call POL_Install_directplay

=== directx9 ===

POL_Call POL_Install_directx9

=== dinput ===

POL_Call POL_Install_dinput

=== dsound ===

POL_Call POL_Install_dsound

=== dxdiag ===

POL_Call POL_Install_dxdiag

=== dxfullsetup ===

POL_Call POL_Install_dxfullsetup

== Desura ==

POL_Call POL_Install_desura

== devenum ==

POL_Call POL_Install_devenum

== DisableCrashDialog ==

POL_Call POL_Install_DisableCrashDialog

== DosboxDrive ==

POL_Call POL_Install_DosboxDrive

== .NET ==

=== POL_Install_dotnet11 ===

=== POL_Install_dotnet11sp1 ===

=== POL_Install_dotnet20 ===

=== POL_Install_dotnet20sp1 ===

=== POL_Install_dotnet20sp2 ===

=== POL_Install_dotnet30 ===

=== POL_Install_dotnet30sp1 ===

=== POL_Install_dotnet35 ===

=== POL_Install_dotnet35sp1 ===

=== POL_Install_dotnet40 ===

== fakeie6 ==

'''What is it?'''

A installer for a audio/video library.

'''What does it do?'''

This let the OS think that Microsoft IE 6 is installed.

'''When would I need it?'''

Only for some games/apps that want IE 6.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_fakeie6
</pre>

== ffdshow ==

'''What is it?'''

A installer for a audio/video library.

'''What does it do?'''

Installs a codecs library, '[https://en.wikipedia.org/wiki/Ffdshow ffdshow]' (2014), in order to encode/decode audio/video files.

'''When would I need it?'''

Some games/apps that use audio/video files encoded by codecs supported by ffdshow.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_ffdshow
</pre>

== flashplayer ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs [https://en.wikipedia.org/wiki/Adobe_Flash_Player Adobe Flash Player files].

'''When would I need it?'''

Some games/apps that use files made with Adobe Flash (was quite common in the 2000's, mainly for web games).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_flashplayer
</pre>

== Flashplayer_ActiveX ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft's [https://en.wikipedia.org/wiki/ActiveX ActiveX] files (it was a competitor of Adobe Flash), up to the 2000's.

'''When would I need it?'''

Some games/apps that use files made with ActiveX (was quite common in the 2000's, mainly for web games and web apps).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_Flashplayer_ActiveX
</pre>

== FontsSmoothBGR ==

POL_Call POL_Install_FontsSmoothBGR

== FontsSmoothGrayScale ==

POL_Call POL_Install_FontsSmoothGrayScale

== FontsSmoothRGB ==

POL_Call POL_Install_FontsSmoothRGB

== gdiplus ==

'''What is it?'''

A installer.

'''What does it do?'''

Set Microsoft's [https://en.wikipedia.org/wiki/Graphics_Device_Interface Graphics Device Interface] graphic rendering mode.

'''When would I need it?'''

Some games/apps made up to the 2000's. Mainly when there is graphic rendering issues.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gdiplus
</pre>

== gecko ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Wine's fake version of Internet Explorer (implementation is based on a custom version of [https://en.wikipedia.org/wiki/Gecko_(software) Mozilla's Gecko]).

'''When would I need it?'''

Some games/apps made in the 2000's. Mainly when there is graphic issues.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gecko
</pre>

'''Link'''

[https://wiki.winehq.org/Gecko Gecko] described on winehq.org

== gfwl ==

'''What is it?'''

A installer.

'''What does it do?'''

Let the OS think that Games for Windows Live ([https://en.wikipedia.org/wiki/Games_for_Windows_%E2%80%93_Live Wikipedia]) is correctly working.

'''When would I need it?'''

Required by some games/apps made in the 2010's.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gfwl
</pre>

== gfwl86 ==

POL_Call POL_Install_gfwl86

== HackSteam ==

POL_Call POL_Install_HackSteam

== ie6 ==

POL_Call POL_Install_ie6

== ie8 ==

POL_Call POL_Install_ie8

== iv50 ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Intel's [https://en.wikipedia.org/wiki/Indeo Indeo] library.

'''When would I need it?'''

Some games/apps made in the 1990's up to 2000's, using video files encoded with Indeo.

'''Script/Shell command:'''

<pre class="playonlinux code">

POL_Call POL_Install_iv50
</pre>

== linuxtrack-wine ==

POL_Call POL_Install_linuxtrack-wine

== LunaTheme ==
Installs a [https://en.wikipedia.org/wiki/Windows_XP_visual_styles Windows XP style] (theme) named Luna.

POL_Call POL_Install_LunaTheme

== mdac28 ==

POL_Call POL_Install_mdac28

== mfc ==

[https://en.wikipedia.org/wiki/Microsoft_Foundation_Class_Library Microsoft Foundation Class Library], a programming library for C++.

=== POL_Install_mfc40 ===
(1995)

=== POL_Install_mfc42 ===
(1998)

== Mono ==

[https://en.wikipedia.org/wiki/Mono_(software) Mono (Wikipedia)] is an open source implementation of the [https://en.wikipedia.org/wiki/Common_Language_Infrastructure Common Language Infrastructure] (.NET).

=== POL_Install_mono210 ===
v2.10 released in 2011.

=== POL_Install_mono26 ===

=== POL_Install_mono28 ===

== msasn1 ==

POL_Call POL_Install_msasn1

== msls31 ==

[https://www.playonlinux.com/fr/app-522-POL_Install_msls31.html POL_Call POL_Install_msls31]

'Microsoft LS' (Unix ls command for Microsoft).

== msvc ==

=== POL_Install_msvc100 ===

=== POL_Install_msvc80 ===

=== POL_Install_msvc90 ===

== msxml ==

=== POL_Install_msxml3 ===

=== POL_Install_msxml4 ===

=== POL_Install_msxml6 ===
'''What is it?'''

A installer for XML libraries.

'''What does it do?'''

Install Microsoft [https://en.wikipedia.org/wiki/MSXML MSXML] v6 (2005).

'''When would I need it?'''

Games/apps made before the 2010's years, that use XML files, for example to store text to displays or settings.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_msxml6
</pre>

== nop ==

POL_Call POL_Install_nop

== physx ==

POL_Call POL_Install_physx

== pngfilt ==

POL_Call POL_Install_pngfilt

== PrivateUserDirs ==

POL_Call POL_Install_PrivateUserDirs

== quartz ==

POL_Call POL_Install_quartz

== RegisterFonts ==

POL_Call POL_Install_RegisterFonts

== riched20 ==

=== POL_Install_riched20 ===

=== POL_Install_riched30 ===

== rsc ==

POL_Call POL_Install_rsc

== steam ==

'''What is it?'''

An installer for the game publishing platform Steam.

'''What does it do?'''

Downloads and Installs Steam client.

'''When would I need it?'''

Any time a game requires Steam to run.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_steam
</pre>

'''Links:'''

http://store.steampowered.com/

== steam_flags ==

'''What is it?'''

A helper script for Steam.

'''What does it do?'''

Set registry third-party flags to avoid steam installing them at the game's first launch.

'''When would I need it?'''

To avoid Steam reinstalling POL-installed dependencies (Wine sometimes requires some ''wizardry'' to get things working that the stock installers do not do, and can cause the application not to run if the workaround is overwritten or broken by the default installation being triggered by the Steam client.).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_steam_flags
</pre>

'''Links:'''

https://www.playonlinux.com/en/app-927-POL_Install_steam_flags.html

== tahoma ==

'''What is it?'''

An installer for the Microsoft font ''Tahoma''.

'''What does it do?'''

Downloads and registers ''Tahoma''.

'''When would I need it?'''

Any time the ''Tahoma'' font is needed.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_tahoma
</pre>

'''Links:'''

http://www.microsoft.com/typography/fonts/family.aspx?FID=19

== tahoma2 ==

'''What is it?'''

An alternative installer for the Microsoft font ''Tahoma''.

'''What does it do?'''

Downloads and registers Tahoma, but from a different package.

'''When would I need it?'''

Any time the ''Tahoma'' font is needed, where the regular ''Tahoma'' installer does not work (like Photoshop CS6).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_tahoma2
</pre>

'''Links:'''

http://www.microsoft.com/typography/fonts/family.aspx?FID=19

== ubigamelauncher ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs the Ubisoft's game launcher.

'''When would I need it?'''

Some games released by [https://en.wikipedia.org/wiki/Ubisoft Ubisoft].

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_ubigamelauncher
</pre>

== vbrun6 ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs [https://en.wikipedia.org/wiki/Visual_Basic Microsoft Visual Basic] v6 libraries (app last released in 1998).

'''When would I need it?'''

Some games/apps made after 1990, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_vbrun6
</pre>

== vcrun ==

=== POL_Install_vcrun2005 ===

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft Visual C++ libraries.

'''When would I need it?'''

Some games/apps made after 2003, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_vcrun2005
</pre>

=== POL_Install_vcrun2008 ===

=== POL_Install_vcrun2010 ===

=== POL_Install_vcrun2012 ===

=== POL_Install_vcrun2013 ===

=== POL_Install_vcrun6 ===

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft Visual C v6 (1989) libraries.

'''When would I need it?'''

Some games/apps made after 1988, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_vcrun6
</pre>

== VideoDriver ==

'''What is it?'''

A window does open and ask to select among the video cards installed. If there is only one video card, nothing happen.

'''What does it do?'''

Edit the Windows registry.

'''When would I need it?'''

If there is 2 video cards on the computer (ie: gaming notebooks, with a Intel iGPU + AMD GPU).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_VideoDriver
</pre>

== wine64b ==

Old command (before POL/POM v4).

POL_Call POL_Install_wine64b

== wineasio ==

'''What is it?'''

WineASIO provides an ASIO driver interface from Wine to jack for low-latency audio and advanced audio/MIDI routing.

'''What does it do?'''

Checks for the following:

* Checks that the virtual drive is 32-bit

* Makes sure that the user is part of the ''audio'' group

* Confirms the presence of ''jack'' and ''qjackctl''

Then, if all checks pass, WineASIO is downloaded and registered into that virtual drive.

'''When would I need it?'''

Certain Adobe products require this to be installed as a dependency.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wineasio
</pre>

'''Links:'''

http://sourceforge.net/projects/wineasio/

== winhttp ==

'''What is it?'''

Install a HTTP library.

'''What does it do?'''

Install some Windows files.

'''When would I need it?'''

Apps made before the 2010's years.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_winhttp
</pre>

== wininet ==

POL_Call POL_Install_wininet

== wintrust ==

POL_Call POL_Install_wintrust

== wmp10 ==

POL_Call POL_Install_wmp10

== wmp9 ==

'''What is it?'''

A installer.

'''What does it do?'''

Install Windows Media Player 9 (~2003).

'''When would I need it?'''

Games/apps made before the 2010's years, that use .WMV video files or .WMA audio files.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wmp9
</pre>

== wmpcodecs ==

'''What is it?'''

A installer.

'''What does it do?'''

Install Windows Media Player (v9) codecs (audio + video).

'''When would I need it?'''

Games/apps made before the 2010's years, that use .WMV video files or .WMA audio files.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wmpcodecs
</pre>

== wsh56 ==

POL_Call POL_Install_wsh56

== wsh57 ==

POL_Call POL_Install_wsh57

== xact ==

'''What is it?'''

A installer for audio libraries.

'''What does it do?'''

Installs Microsoft '[https://en.wikipedia.org/wiki/Cross-platform_Audio_Creation_Tool Cross-platform Audio Creation Tool]' (2002).

'''When would I need it?'''

Games/apps made before the 2010's years.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_xact
</pre>

== xinput ==

POL_Call POL_Install_xinput

== xmllite ==

'''What is it?'''

A installer for XML libraries.

'''What does it do?'''

Install Microsoft [https://en.wikipedia.org/wiki/MSXML MSXML] (2000's).

'''When would I need it?'''

Games/apps made before the 2010's years, that use XML files, for example to store text to displays or settings.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_xmllite
</pre>

== xna31 ==

POL_Call POL_Install_xna31

== xna40 ==

POL_Call POL_Install_xna40

== xvid ==

POL_Call POL_Install_xvid

== Other Functions ==

=== POL_Configurator_runparts ===

POL_Call POL_Configurator_runparts

=== POL_Download_retry ===

POL_Call POL_Download_retry

=== POL_Function_FontsSmoothBGR ===

POL_Call POL_Function_FontsSmoothBGR

=== POL_Function_FontsSmoothGrayScale ===

POL_Call POL_Function_FontsSmoothGrayScale

=== POL_Function_FontsSmoothRGB ===

POL_Call POL_Function_FontsSmoothRGB

=== POL_Function_NoCDWarning ===

'''What is it?'''

A warning message for the user of a script.

'''What does it do?'''

Does warn that the game/app will not work without a way to workaround the DRM (NoCD or other).

'''When would I need it?'''

To warn when a game can not work with POL/POM script without a NoCD.
Some DRMs does not work with Wine, originals CDs/DVDs are not recognized.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Function_NoCDWarning
</pre>

=== POL_Function_override_app_dlls ===

POL_Call POL_Function_override_app_dlls

=== POL_Function_OverrideDLL ===

POL_Call POL_Function_OverrideDLL

=== POL_Function_RootCommand ===

POL_Call POL_Function_RootCommand

=== POL_Function_sandbox ===

POL_Call POL_Function_sandbox

=== POL_Function_SetNativeExtension ===

POL_Call POL_Function_SetNativeExtension

=== POL_Function_simplecdscript ===

POL_Call POL_Function_simplecdscript

=== POL_Function_simplescript ===

POL_Call POL_Function_simplescript

=== POL_Function_Sleep ===

POL_Call POL_Function_Sleep

=== POL_Gamefront_Download ===

POL_Call POL_Gamefront_Download

=== POL_GetTool_samba3 ===

POL_Call POL_GetTool_samba3

=== POL_GoG_download ===

POL_Call POL_GoG_download

=== POL_GoG_Extract ===

POL_Call POL_GoG_Extract

=== POL_GoG_install ===

POL_Call POL_GoG_install

=== POL_GoG_setup ===

POL_Call POL_GoG_setup

Components and Functions

2020-06-09T08:51:39Z

Dadu042: /* fakeie6 */

Details, use cases, related errors, and more on each component.

== POL/POM Configuration -> Display ==

These commands allow to script the [[The_Configuration_Window#Display_tab|display settings available in the GUI]].

=== GLSL Support ===
Default setting (2019) is "enabled".

=== DirectDraw Renderer ===
Default setting (2019) is "opengl".

'''Script/Shell command:'''
<pre class="playonlinux code">
POL_Wine_Direct3D "DirectDrawRenderer" "gdi"
</pre>

=== Video memory size ===
See [[Scripting_-_Chapter_11:_List_of_Functions#POL_SetupWindow_VMS_.284.0.2B.29|this page about the command 'POL_SetupWindow_VMS']].

=== Offscreen rendering mode ===

== AdobeAir ==

'''What is it?'''

"The Adobe AIR runtime enables developers to package the same code into native applications and games for Windows and Mac OS desktops as well as iOS and Android devices, reaching over a billion desktop systems and mobile app stores for over 500 million devices."

-from http://get.adobe.com/air/

'''What does it do?'''

Installs the Adobe Air package.

'''When would I need it?'''

Certain Adobe products require this to be installed as a dependency.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_AdobeAir
</pre>

'''Links:'''

http://get.adobe.com/air/

== amstream ==

'''What is it?'''

A installer for a library.

'''What does it do?'''

Installs on Windows a Microsoft library, part of [https://en.wikipedia.org/wiki/DirectShow DirectShow].

'''When would I need it?'''

Some games/apps made after the 1990's and before the 2010's, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_amstream
</pre>

== ATI_Black-Screen_Fix ==

POL_Call POL_Install_ATI_Black-Screen_Fix

== atmlib ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs 'Adobe Type Manager'.

'''When would I need it?'''

[https://en.wikipedia.org/wiki/Adobe_Type_Manager Wikipedia].

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_atmlib
</pre>

== cc580 ==

POL_Call POL_Install_cc580

== CentralizedUserDirs ==

POL_Call POL_Install_CentralizedUserDirs

== corefonts ==

'''What is it?'''

"TrueType is an outline font standard developed by Apple and Microsoft in the late 1980s as a competitor to Adobe's Type 1 fonts used in PostScript. It has become the most common format for fonts on both the Mac OS and Microsoft Windows operating systems."

from http://en.wikipedia.org/wiki/TrueType

'''What does it do?'''

Downloads and registers TrueType fonts (TTF). Here is a list of the fonts that will be installed into the given virtual drive:

* andale mono
* arial black
* arial (bold, italic, bold italic)
* comic sans ms (bold)
* courier new (bold, italic, bold italic)
* georgia (bold, italic, bold italic)
* impact
* times new roman (bold, italic, bold italic)
* trebuchet (bold, italic, bold italic)
* verdana (bold, italic, bold italic)
* webdings

'''When would I need it?'''

Any time you experience missing text in an application, this would be the first place you would want to start. This is usually installed by default, though. If this does not work, try '''tahoma''' or '''tahoma2''' from the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Install Components tab], as those are the usual suspects in such acts of font thievery.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_corefonts
</pre>

'''Links:'''

http://en.wikipedia.org/wiki/TrueType

== crypt32 ==

'''What is it?'''

''crypt32'' does quite a few things relating to decrypting/encrypting data. Basic information in the links below.

'''What does it do?'''

"It supports encryption, decryption, and manipulation of certificates and related data structures."

from http://wiki.winehq.org/Crypt32

'''When would I need it?'''

Most of this is taken care of within Wine via the ''builtin'' dll. You may run into times when the native dll is needed, in which case the POL debug log will spit out an error saying that it tried to do something with it and it failed (like ''unhandled exception'' or ''cannot find crypt32.dll'', etc.). If you do happen to run into an error like this, we highly encourage you to report it to https://appdb.winehq.org so that the community there can possibly implement a fix that is native to Wine, eliminating the need for the actual Windows dll.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_crypt32
</pre>

'''Links:'''

http://wiki.winehq.org/Crypt32

== dcom98 ==

Microsofts's [https://en.wikipedia.org/wiki/Distributed_Component_Object_Model Distributed Component Object Model], 1998.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_dcom98
</pre>

== DirectX ==

=== d3dcompiler_43 ===

POL_Call POL_Install_d3dcompiler_43

=== d3dx10 ===

POL_Call POL_Install_d3dx10

=== d3dx11 ===

POL_Call POL_Install_d3dx11

=== d3dx9 ===

POL_Call POL_Install_d3dx9

=== d3dx9_29 ===

POL_Call POL_Install_d3dx9_29

=== d3dx9_35 ===

POL_Call POL_Install_d3dx9_35

=== d3dx9_36 ===

POL_Call POL_Install_d3dx9_36

=== d3dx9_40 ===

POL_Call POL_Install_d3dx9_40

=== d3dx9_42 ===

POL_Call POL_Install_d3dx9_42

=== d3dx9_43 ===

'''What is it?'''

A installer for a library.

'''What does it do?'''

Installs the Windows library, part of [https://en.wikipedia.org/wiki/DirectX DirectX] 9 version 43 (the latest is the better).

'''When would I need it?'''

Some games/apps made for DirectX up to version 9, if these don't work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_d3dx9_43
</pre>

=== dinput8 ===

POL_Call POL_Install_dinput8

=== directmusic ===

POL_Call POL_Install_directmusic

=== directplay ===

POL_Call POL_Install_directplay

=== directx9 ===

POL_Call POL_Install_directx9

=== dinput ===

POL_Call POL_Install_dinput

=== dsound ===

POL_Call POL_Install_dsound

=== dxdiag ===

POL_Call POL_Install_dxdiag

=== dxfullsetup ===

POL_Call POL_Install_dxfullsetup

== Desura ==

POL_Call POL_Install_desura

== devenum ==

POL_Call POL_Install_devenum

== DisableCrashDialog ==

POL_Call POL_Install_DisableCrashDialog

== DosboxDrive ==

POL_Call POL_Install_DosboxDrive

== .NET ==

=== POL_Install_dotnet11 ===

=== POL_Install_dotnet11sp1 ===

=== POL_Install_dotnet20 ===

=== POL_Install_dotnet20sp1 ===

=== POL_Install_dotnet20sp2 ===

=== POL_Install_dotnet30 ===

=== POL_Install_dotnet30sp1 ===

=== POL_Install_dotnet35 ===

=== POL_Install_dotnet35sp1 ===

=== POL_Install_dotnet40 ===

== fakeie6 ==

'''What is it?'''

A installer for a audio/video library.

'''What does it do?'''

This let the OS think that Microsoft IE 6 is installed.

'''When would I need it?'''

Only for some games/apps that want IE 6.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_fakeie6
</pre>

== ffdshow ==

'''What is it?'''

A installer for a audio/video library.

'''What does it do?'''

Installs a codecs library, '[https://en.wikipedia.org/wiki/Ffdshow ffdshow]' (2014), in order to encode/decode audio/video files.

'''When would I need it?'''

Some games/apps that use audio/video files encoded by codecs supported by ffdshow.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_ffdshow
</pre>

== flashplayer ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs [https://en.wikipedia.org/wiki/Adobe_Flash_Player Adobe Flash Player files].

'''When would I need it?'''

Some games/apps that use files made with Adobe Flash (was quite common in the 2000's, mainly for web games).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_flashplayer
</pre>

== Flashplayer_ActiveX ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft's [https://en.wikipedia.org/wiki/ActiveX ActiveX] files (it was a competitor of Adobe Flash), up to the 2000's.

'''When would I need it?'''

Some games/apps that use files made with ActiveX (was quite common in the 2000's, mainly for web games and web apps).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_Flashplayer_ActiveX
</pre>

== FontsSmoothBGR ==

POL_Call POL_Install_FontsSmoothBGR

== FontsSmoothGrayScale ==

POL_Call POL_Install_FontsSmoothGrayScale

== FontsSmoothRGB ==

POL_Call POL_Install_FontsSmoothRGB

== gdiplus ==

'''What is it?'''

A installer.

'''What does it do?'''

Set Microsoft's [https://en.wikipedia.org/wiki/Graphics_Device_Interface Graphics Device Interface] graphic rendering mode.

'''When would I need it?'''

Some games/apps made up to the 2000's. Mainly when there is graphic rendering issues.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gdiplus
</pre>

== gecko ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Wine's fake version of Internet Explorer (implementation is based on a custom version of [https://en.wikipedia.org/wiki/Gecko_(software) Mozilla's Gecko]).

'''When would I need it?'''

Some games/apps made in the 2000's. Mainly when there is graphic issues.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gecko
</pre>

'''Link'''

[https://wiki.winehq.org/Gecko Gecko] described on winehq.org

== gfwl ==

POL_Call POL_Install_gfwl

== gfwl86 ==

POL_Call POL_Install_gfwl86

== HackSteam ==

POL_Call POL_Install_HackSteam

== ie6 ==

POL_Call POL_Install_ie6

== ie8 ==

POL_Call POL_Install_ie8

== iv50 ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Intel's [https://en.wikipedia.org/wiki/Indeo Indeo] library.

'''When would I need it?'''

Some games/apps made in the 1990's up to 2000's, using video files encoded with Indeo.

'''Script/Shell command:'''

<pre class="playonlinux code">

POL_Call POL_Install_iv50
</pre>

== linuxtrack-wine ==

POL_Call POL_Install_linuxtrack-wine

== LunaTheme ==
Installs a [https://en.wikipedia.org/wiki/Windows_XP_visual_styles Windows XP style] (theme) named Luna.

POL_Call POL_Install_LunaTheme

== mdac28 ==

POL_Call POL_Install_mdac28

== mfc ==

[https://en.wikipedia.org/wiki/Microsoft_Foundation_Class_Library Microsoft Foundation Class Library], a programming library for C++.

=== POL_Install_mfc40 ===
(1995)

=== POL_Install_mfc42 ===
(1998)

== Mono ==

[https://en.wikipedia.org/wiki/Mono_(software) Mono (Wikipedia)] is an open source implementation of the [https://en.wikipedia.org/wiki/Common_Language_Infrastructure Common Language Infrastructure] (.NET).

=== POL_Install_mono210 ===
v2.10 released in 2011.

=== POL_Install_mono26 ===

=== POL_Install_mono28 ===

== msasn1 ==

POL_Call POL_Install_msasn1

== msls31 ==

[https://www.playonlinux.com/fr/app-522-POL_Install_msls31.html POL_Call POL_Install_msls31]

'Microsoft LS' (Unix ls command for Microsoft).

== msvc ==

=== POL_Install_msvc100 ===

=== POL_Install_msvc80 ===

=== POL_Install_msvc90 ===

== msxml ==

=== POL_Install_msxml3 ===

=== POL_Install_msxml4 ===

=== POL_Install_msxml6 ===
'''What is it?'''

A installer for XML libraries.

'''What does it do?'''

Install Microsoft [https://en.wikipedia.org/wiki/MSXML MSXML] v6 (2005).

'''When would I need it?'''

Games/apps made before the 2010's years, that use XML files, for example to store text to displays or settings.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_msxml6
</pre>

== nop ==

POL_Call POL_Install_nop

== physx ==

POL_Call POL_Install_physx

== pngfilt ==

POL_Call POL_Install_pngfilt

== PrivateUserDirs ==

POL_Call POL_Install_PrivateUserDirs

== quartz ==

POL_Call POL_Install_quartz

== RegisterFonts ==

POL_Call POL_Install_RegisterFonts

== riched20 ==

=== POL_Install_riched20 ===

=== POL_Install_riched30 ===

== rsc ==

POL_Call POL_Install_rsc

== steam ==

'''What is it?'''

An installer for the game publishing platform Steam.

'''What does it do?'''

Downloads and Installs Steam client.

'''When would I need it?'''

Any time a game requires Steam to run.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_steam
</pre>

'''Links:'''

http://store.steampowered.com/

== steam_flags ==

'''What is it?'''

A helper script for Steam.

'''What does it do?'''

Set registry third-party flags to avoid steam installing them at the game's first launch.

'''When would I need it?'''

To avoid Steam reinstalling POL-installed dependencies (Wine sometimes requires some ''wizardry'' to get things working that the stock installers do not do, and can cause the application not to run if the workaround is overwritten or broken by the default installation being triggered by the Steam client.).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_steam_flags
</pre>

'''Links:'''

https://www.playonlinux.com/en/app-927-POL_Install_steam_flags.html

== tahoma ==

'''What is it?'''

An installer for the Microsoft font ''Tahoma''.

'''What does it do?'''

Downloads and registers ''Tahoma''.

'''When would I need it?'''

Any time the ''Tahoma'' font is needed.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_tahoma
</pre>

'''Links:'''

http://www.microsoft.com/typography/fonts/family.aspx?FID=19

== tahoma2 ==

'''What is it?'''

An alternative installer for the Microsoft font ''Tahoma''.

'''What does it do?'''

Downloads and registers Tahoma, but from a different package.

'''When would I need it?'''

Any time the ''Tahoma'' font is needed, where the regular ''Tahoma'' installer does not work (like Photoshop CS6).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_tahoma2
</pre>

'''Links:'''

http://www.microsoft.com/typography/fonts/family.aspx?FID=19

== ubigamelauncher ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs the Ubisoft's game launcher.

'''When would I need it?'''

Some games released by [https://en.wikipedia.org/wiki/Ubisoft Ubisoft].

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_ubigamelauncher
</pre>

== vbrun6 ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs [https://en.wikipedia.org/wiki/Visual_Basic Microsoft Visual Basic] v6 libraries (app last released in 1998).

'''When would I need it?'''

Some games/apps made after 1990, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_vbrun6
</pre>

== vcrun ==

=== POL_Install_vcrun2005 ===

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft Visual C++ libraries.

'''When would I need it?'''

Some games/apps made after 2003, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_vcrun2005
</pre>

=== POL_Install_vcrun2008 ===

=== POL_Install_vcrun2010 ===

=== POL_Install_vcrun2012 ===

=== POL_Install_vcrun2013 ===

=== POL_Install_vcrun6 ===

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft Visual C v6 (1989) libraries.

'''When would I need it?'''

Some games/apps made after 1988, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_vcrun6
</pre>

== VideoDriver ==

'''What is it?'''

A window does open and ask to select among the video cards installed. If there is only one video card, nothing happen.

'''What does it do?'''

Edit the Windows registry.

'''When would I need it?'''

If there is 2 video cards on the computer (ie: gaming notebooks, with a Intel iGPU + AMD GPU).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_VideoDriver
</pre>

== wine64b ==

Old command (before POL/POM v4).

POL_Call POL_Install_wine64b

== wineasio ==

'''What is it?'''

WineASIO provides an ASIO driver interface from Wine to jack for low-latency audio and advanced audio/MIDI routing.

'''What does it do?'''

Checks for the following:

* Checks that the virtual drive is 32-bit

* Makes sure that the user is part of the ''audio'' group

* Confirms the presence of ''jack'' and ''qjackctl''

Then, if all checks pass, WineASIO is downloaded and registered into that virtual drive.

'''When would I need it?'''

Certain Adobe products require this to be installed as a dependency.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wineasio
</pre>

'''Links:'''

http://sourceforge.net/projects/wineasio/

== winhttp ==

'''What is it?'''

Install a HTTP library.

'''What does it do?'''

Install some Windows files.

'''When would I need it?'''

Apps made before the 2010's years.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_winhttp
</pre>

== wininet ==

POL_Call POL_Install_wininet

== wintrust ==

POL_Call POL_Install_wintrust

== wmp10 ==

POL_Call POL_Install_wmp10

== wmp9 ==

'''What is it?'''

A installer.

'''What does it do?'''

Install Windows Media Player 9 (~2003).

'''When would I need it?'''

Games/apps made before the 2010's years, that use .WMV video files or .WMA audio files.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wmp9
</pre>

== wmpcodecs ==

'''What is it?'''

A installer.

'''What does it do?'''

Install Windows Media Player (v9) codecs (audio + video).

'''When would I need it?'''

Games/apps made before the 2010's years, that use .WMV video files or .WMA audio files.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wmpcodecs
</pre>

== wsh56 ==

POL_Call POL_Install_wsh56

== wsh57 ==

POL_Call POL_Install_wsh57

== xact ==

'''What is it?'''

A installer for audio libraries.

'''What does it do?'''

Installs Microsoft '[https://en.wikipedia.org/wiki/Cross-platform_Audio_Creation_Tool Cross-platform Audio Creation Tool]' (2002).

'''When would I need it?'''

Games/apps made before the 2010's years.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_xact
</pre>

== xinput ==

POL_Call POL_Install_xinput

== xmllite ==

'''What is it?'''

A installer for XML libraries.

'''What does it do?'''

Install Microsoft [https://en.wikipedia.org/wiki/MSXML MSXML] (2000's).

'''When would I need it?'''

Games/apps made before the 2010's years, that use XML files, for example to store text to displays or settings.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_xmllite
</pre>

== xna31 ==

POL_Call POL_Install_xna31

== xna40 ==

POL_Call POL_Install_xna40

== xvid ==

POL_Call POL_Install_xvid

== Other Functions ==

=== POL_Configurator_runparts ===

POL_Call POL_Configurator_runparts

=== POL_Download_retry ===

POL_Call POL_Download_retry

=== POL_Function_FontsSmoothBGR ===

POL_Call POL_Function_FontsSmoothBGR

=== POL_Function_FontsSmoothGrayScale ===

POL_Call POL_Function_FontsSmoothGrayScale

=== POL_Function_FontsSmoothRGB ===

POL_Call POL_Function_FontsSmoothRGB

=== POL_Function_NoCDWarning ===

'''What is it?'''

A warning message for the user of a script.

'''What does it do?'''

Does warn that the game/app will not work without a way to workaround the DRM (NoCD or other).

'''When would I need it?'''

To warn when a game can not work with POL/POM script without a NoCD.
Some DRMs does not work with Wine, originals CDs/DVDs are not recognized.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Function_NoCDWarning
</pre>

=== POL_Function_override_app_dlls ===

POL_Call POL_Function_override_app_dlls

=== POL_Function_OverrideDLL ===

POL_Call POL_Function_OverrideDLL

=== POL_Function_RootCommand ===

POL_Call POL_Function_RootCommand

=== POL_Function_sandbox ===

POL_Call POL_Function_sandbox

=== POL_Function_SetNativeExtension ===

POL_Call POL_Function_SetNativeExtension

=== POL_Function_simplecdscript ===

POL_Call POL_Function_simplecdscript

=== POL_Function_simplescript ===

POL_Call POL_Function_simplescript

=== POL_Function_Sleep ===

POL_Call POL_Function_Sleep

=== POL_Gamefront_Download ===

POL_Call POL_Gamefront_Download

=== POL_GetTool_samba3 ===

POL_Call POL_GetTool_samba3

=== POL_GoG_download ===

POL_Call POL_GoG_download

=== POL_GoG_Extract ===

POL_Call POL_GoG_Extract

=== POL_GoG_install ===

POL_Call POL_GoG_install

=== POL_GoG_setup ===

POL_Call POL_GoG_setup

FAQ

2020-06-05T18:00:03Z

Dadu042: /* Why a online game does not work on my computer while the script is available from your website ? */

== PlayOnLinux and PlayOnMac ==

=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.

=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===
Read the advanced topic here:
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]

=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.

=== Do I have to install Wine to use PlayOnLinux? ===
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.

=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).

=== The application I am trying to install needs administrator rights to function correctly ===
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.

=== How do I install Steam, and Steam only? ===

If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:

# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window.

{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}

=== How can I use the CSMT patch with POL? ===

Up until recently (2015 ?), you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.).

Simply go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.

=== Why a online game does not work on my computer while the script is available from your website ? ===

Since the 2010's online games have the habit to auto upgrade themselves. This might break the compatibility we reached someday (in the top of the script code you can see the date when it was write).

Please post a comment in the script page of the game, the more details you post (ie: [http://wiki.playonlinux.com/index.php/How_to_Post_in_the_Forums#What_information_is_needed_in_my_post.3F example for the forums]), the more help you will get (not immediately). The more reports we get, the better choice we make. In the same way, the more bad reports we get, the faster we may disable a script.

== Website ==

=== How can I post a bug report? ===
* [[How to Post a Bug Report|How to Post a Bug Report]]

=== How can I contribute an installer for an application? ===
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]

Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]

=== How do I request a version of Wine with a certain patch? ===
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]

=== Where does PlayOnLinux store it's virtual drives and cache? ===
All virtual drives are created and store here:

<code>~/.PlayOnLinux/wineprefix/</code>

The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''

=== How do I run Wine/POL as root or sudo? ===
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism.

* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]

=== Is there a list of solutions for common problems? ===
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:

# [[Troubleshooting Common Problems|Troubleshooting Common Problems]]
# [https://appdb.winehq.org/ appdb.winehq.org]
# Searching the POL/POM forums (see [[How to Post in the Forums|How to Post in the Forums]])
# Search engines for the web, of course.

=== My post was closed with a semi-automated reply? What did I break? ===
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service.

Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:

* https://www.playonlinux.com/en/terms.html

* [[How to Post in the Forums|How to Post in the Forums]]

== I want to contribute ==

=== Bash; I really want to know more ===
* http://www.gnu.org/software/bash/

* http://linuxconfig.org/bash-scripting-tutorial

* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/

* http://www.tldp.org/LDP/abs/html/

=== Python; I really want to know more ===
* https://www.python.org/

* https://docs.python.org/2/tutorial/

* http://www.learnpython.org/

How to Request a Patched Version of Wine

2020-06-05T17:55:10Z

Dadu042:

'''*** WARNING: As of 2018, this whole page is obsolete. ***'''

What? You need to patch Wine to play a certain game? You can't compile to save your life? Never fear. We have a build service that can apply patches to Wine and make them available for use through PlayOnLinux/PlayOnMac! It is called '''WineBuild''', and this is how you can request it's services.

* Go to https://www.playonlinux.com or https://www.playonmac.com, and go to our "Bugs" section. The direct link is here: https://www.playonlinux.com/en/bugs.html

* Click "Report a problem" under the '''Quick tasks''' heading:

https://www.playonlinux.com/images/uploads/243.jpg

Fill out the form accordingly:

* Leave the '''Priority''' at the default of ''Low'' and from '''Tracker''', select '''PlayOnLinux (or PlayOnMac) -> Feature''':

https://www.playonlinux.com/images/uploads/244.jpg

* For '''Title''', use the following syntax:

<pre>
[WineBuild] - Title of your request
</pre>

For the body of the message, let us know what exactly you want, which version of Wine you want built, and which patch you want us to use. If you know that we already have patched Wine versions with the patch you want, request that, and if it is usable with that version of Wine, we can build it. If you don't know if we have it, please include a link to the patch, along with it's name, so that we can find it and attempt the build. If there are and special build notes that you need to add, please add those near the bottom of the message (any build instructions, flags, etc..).

https://www.playonlinux.com/images/uploads/245.jpg

From here, our team will look at the request and either:

* Put the patch and request into our queue, in which case it will be built during the next build window (it typically checks every 30 minutes for new build requests). You can see the progress of the build, as well as browse our repository of Wine builds here: https://www.playonlinux.com/wine/

* or request more information, either because something was missing from the request (like the link to a patch that we do not have, missing Wine version for build)

* or inform you that this build cannot be done for a given reason (incompatibility with version of Wine and patch or with other patches, that build already exists, or for any technical reason that stops the build from being done

FAQ

2020-06-05T17:51:03Z

Dadu042: /* Why a online game does not work on my computer while the script is available from your website ? */

== PlayOnLinux and PlayOnMac ==

=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.

=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===
Read the advanced topic here:
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]

=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.

=== Do I have to install Wine to use PlayOnLinux? ===
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.

=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).

=== The application I am trying to install needs administrator rights to function correctly ===
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.

=== How do I install Steam, and Steam only? ===

If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:

# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window.

{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}

=== How can I use the CSMT patch with POL? ===

Up until recently (2015 ?), you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.).

Simply go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.

=== Why a online game does not work on my computer while the script is available from your website ? ===

Since the 2020's online games have the habit to auto upgrade themselves. This might break the compatibility (in the top of the script code you can see the date when it was write).

Please post a comment in the script page of the game, the more details you post (ie: [http://wiki.playonlinux.com/index.php/How_to_Post_in_the_Forums#What_information_is_needed_in_my_post.3F example for the forums]), the more help you will get (not immediately). The more reports we get, the better choice we make.

== Website ==

=== How can I post a bug report? ===
* [[How to Post a Bug Report|How to Post a Bug Report]]

=== How can I contribute an installer for an application? ===
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]

Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]

=== How do I request a version of Wine with a certain patch? ===
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]

=== Where does PlayOnLinux store it's virtual drives and cache? ===
All virtual drives are created and store here:

<code>~/.PlayOnLinux/wineprefix/</code>

The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''

=== How do I run Wine/POL as root or sudo? ===
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism.

* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]

=== Is there a list of solutions for common problems? ===
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:

# [[Troubleshooting Common Problems|Troubleshooting Common Problems]]
# [https://appdb.winehq.org/ appdb.winehq.org]
# Searching the POL/POM forums (see [[How to Post in the Forums|How to Post in the Forums]])
# Search engines for the web, of course.

=== My post was closed with a semi-automated reply? What did I break? ===
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service.

Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:

* https://www.playonlinux.com/en/terms.html

* [[How to Post in the Forums|How to Post in the Forums]]

== I want to contribute ==

=== Bash; I really want to know more ===
* http://www.gnu.org/software/bash/

* http://linuxconfig.org/bash-scripting-tutorial

* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/

* http://www.tldp.org/LDP/abs/html/

=== Python; I really want to know more ===
* https://www.python.org/

* https://docs.python.org/2/tutorial/

* http://www.learnpython.org/

FAQ

2020-06-05T17:48:03Z

Dadu042: /* Why a online game does not work on my computer while the script is available from your website ? */

== PlayOnLinux and PlayOnMac ==

=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.

=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===
Read the advanced topic here:
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]

=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.

=== Do I have to install Wine to use PlayOnLinux? ===
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.

=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).

=== The application I am trying to install needs administrator rights to function correctly ===
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.

=== How do I install Steam, and Steam only? ===

If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:

# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window.

{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}

=== How can I use the CSMT patch with POL? ===

Up until recently (2015 ?), you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.).

Simply go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.

=== Why a online game does not work on my computer while the script is available from your website ? ===

Since the 2020's online games have the habit to auto upgrade themselves. This might break the compatibility (in the top of the script code you can see the date when it was wrote).

Please post a comment in the script page of the game, the more details you post (ie: [http://wiki.playonlinux.com/index.php/How_to_Post_in_the_Forums#What_information_is_needed_in_my_post.3F example for the forums]), the more help you will get (not immediately). The more reports we get, the better choice we make.

== Website ==

=== How can I post a bug report? ===
* [[How to Post a Bug Report|How to Post a Bug Report]]

=== How can I contribute an installer for an application? ===
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]

Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]

=== How do I request a version of Wine with a certain patch? ===
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]

=== Where does PlayOnLinux store it's virtual drives and cache? ===
All virtual drives are created and store here:

<code>~/.PlayOnLinux/wineprefix/</code>

The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''

=== How do I run Wine/POL as root or sudo? ===
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism.

* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]

=== Is there a list of solutions for common problems? ===
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:

# [[Troubleshooting Common Problems|Troubleshooting Common Problems]]
# [https://appdb.winehq.org/ appdb.winehq.org]
# Searching the POL/POM forums (see [[How to Post in the Forums|How to Post in the Forums]])
# Search engines for the web, of course.

=== My post was closed with a semi-automated reply? What did I break? ===
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service.

Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:

* https://www.playonlinux.com/en/terms.html

* [[How to Post in the Forums|How to Post in the Forums]]

== I want to contribute ==

=== Bash; I really want to know more ===
* http://www.gnu.org/software/bash/

* http://linuxconfig.org/bash-scripting-tutorial

* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/

* http://www.tldp.org/LDP/abs/html/

=== Python; I really want to know more ===
* https://www.python.org/

* https://docs.python.org/2/tutorial/

* http://www.learnpython.org/

FAQ

2020-06-05T17:41:01Z

Dadu042: /* Why a online game does not work on my computer while the script is available from your website ? */

== PlayOnLinux and PlayOnMac ==

=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.

=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===
Read the advanced topic here:
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]

=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.

=== Do I have to install Wine to use PlayOnLinux? ===
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.

=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).

=== The application I am trying to install needs administrator rights to function correctly ===
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.

=== How do I install Steam, and Steam only? ===

If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:

# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window.

{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}

=== How can I use the CSMT patch with POL? ===

Up until recently (2015 ?), you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.).

Simply go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.

=== Why a online game does not work on my computer while the script is available from your website ? ===

Since the 2020's online games have the habit to auto upgrade themselves. This might break the compatibility (in the top of the script code you can see the date when it was wrote).

Please post a comment in the script page of the game, the more details you post (ie: [http://wiki.playonlinux.com/index.php/How_to_Post_in_the_Forums#What_information_is_needed_in_my_post.3F example for the forums]), the more help you will get (not immediately).

== Website ==

=== How can I post a bug report? ===
* [[How to Post a Bug Report|How to Post a Bug Report]]

=== How can I contribute an installer for an application? ===
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]

Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]

=== How do I request a version of Wine with a certain patch? ===
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]

=== Where does PlayOnLinux store it's virtual drives and cache? ===
All virtual drives are created and store here:

<code>~/.PlayOnLinux/wineprefix/</code>

The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''

=== How do I run Wine/POL as root or sudo? ===
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism.

* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]

=== Is there a list of solutions for common problems? ===
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:

# [[Troubleshooting Common Problems|Troubleshooting Common Problems]]
# [https://appdb.winehq.org/ appdb.winehq.org]
# Searching the POL/POM forums (see [[How to Post in the Forums|How to Post in the Forums]])
# Search engines for the web, of course.

=== My post was closed with a semi-automated reply? What did I break? ===
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service.

Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:

* https://www.playonlinux.com/en/terms.html

* [[How to Post in the Forums|How to Post in the Forums]]

== I want to contribute ==

=== Bash; I really want to know more ===
* http://www.gnu.org/software/bash/

* http://linuxconfig.org/bash-scripting-tutorial

* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/

* http://www.tldp.org/LDP/abs/html/

=== Python; I really want to know more ===
* https://www.python.org/

* https://docs.python.org/2/tutorial/

* http://www.learnpython.org/

FAQ

2020-06-05T17:40:18Z

Dadu042: /* Why a online game does not work on my computer while the script is available from your website ? */

== PlayOnLinux and PlayOnMac ==

=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.

=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===
Read the advanced topic here:
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]

=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.

=== Do I have to install Wine to use PlayOnLinux? ===
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.

=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).

=== The application I am trying to install needs administrator rights to function correctly ===
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.

=== How do I install Steam, and Steam only? ===

If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:

# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window.

{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}

=== How can I use the CSMT patch with POL? ===

Up until recently (2015 ?), you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.).

Simply go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.

=== Why a online game does not work on my computer while the script is available from your website ? ===

Since the 2020's online games have the habit to auto upgrade themselves. This might break the compatibility (in the top of the script code you can see the date when it was wrote).

Please post a comment in the script page, the more details you post (ie: [http://wiki.playonlinux.com/index.php/How_to_Post_in_the_Forums#What_information_is_needed_in_my_post.3F example for the forums]), the more help you will get (not immediately).

== Website ==

=== How can I post a bug report? ===
* [[How to Post a Bug Report|How to Post a Bug Report]]

=== How can I contribute an installer for an application? ===
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]

Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]

=== How do I request a version of Wine with a certain patch? ===
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]

=== Where does PlayOnLinux store it's virtual drives and cache? ===
All virtual drives are created and store here:

<code>~/.PlayOnLinux/wineprefix/</code>

The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''

=== How do I run Wine/POL as root or sudo? ===
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism.

* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]

=== Is there a list of solutions for common problems? ===
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:

# [[Troubleshooting Common Problems|Troubleshooting Common Problems]]
# [https://appdb.winehq.org/ appdb.winehq.org]
# Searching the POL/POM forums (see [[How to Post in the Forums|How to Post in the Forums]])
# Search engines for the web, of course.

=== My post was closed with a semi-automated reply? What did I break? ===
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service.

Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:

* https://www.playonlinux.com/en/terms.html

* [[How to Post in the Forums|How to Post in the Forums]]

== I want to contribute ==

=== Bash; I really want to know more ===
* http://www.gnu.org/software/bash/

* http://linuxconfig.org/bash-scripting-tutorial

* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/

* http://www.tldp.org/LDP/abs/html/

=== Python; I really want to know more ===
* https://www.python.org/

* https://docs.python.org/2/tutorial/

* http://www.learnpython.org/

FAQ

2020-06-05T17:37:56Z

Dadu042: /* PlayOnLinux and PlayOnMac */ + online game

== PlayOnLinux and PlayOnMac ==

=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.

=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===
Read the advanced topic here:
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]

=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.

=== Do I have to install Wine to use PlayOnLinux? ===
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.

=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).

=== The application I am trying to install needs administrator rights to function correctly ===
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.

=== How do I install Steam, and Steam only? ===

If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:

# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window.

{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}

=== How can I use the CSMT patch with POL? ===

Up until recently (2015 ?), you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.).

Simply go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.

=== Why a online game does not work on my computer while the script is available from your website ? ===

Since the 2020's online games have the habit to auto upgrade themselves. This might break the compatibility (in the top of the script code you can see the date when it was wrote).

Please post a comment in the script page, the most details you post (ie: [http://wiki.playonlinux.com/index.php/How_to_Post_in_the_Forums#What_information_is_needed_in_my_post.3F example for the forums]), the more help you will get.

== Website ==

=== How can I post a bug report? ===
* [[How to Post a Bug Report|How to Post a Bug Report]]

=== How can I contribute an installer for an application? ===
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]

Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]

=== How do I request a version of Wine with a certain patch? ===
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]

=== Where does PlayOnLinux store it's virtual drives and cache? ===
All virtual drives are created and store here:

<code>~/.PlayOnLinux/wineprefix/</code>

The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''

=== How do I run Wine/POL as root or sudo? ===
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism.

* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]

=== Is there a list of solutions for common problems? ===
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:

# [[Troubleshooting Common Problems|Troubleshooting Common Problems]]
# [https://appdb.winehq.org/ appdb.winehq.org]
# Searching the POL/POM forums (see [[How to Post in the Forums|How to Post in the Forums]])
# Search engines for the web, of course.

=== My post was closed with a semi-automated reply? What did I break? ===
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service.

Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:

* https://www.playonlinux.com/en/terms.html

* [[How to Post in the Forums|How to Post in the Forums]]

== I want to contribute ==

=== Bash; I really want to know more ===
* http://www.gnu.org/software/bash/

* http://linuxconfig.org/bash-scripting-tutorial

* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/

* http://www.tldp.org/LDP/abs/html/

=== Python; I really want to know more ===
* https://www.python.org/

* https://docs.python.org/2/tutorial/

* http://www.learnpython.org/

FAQ

2020-06-05T17:31:38Z

Dadu042: /* How can I use the CSMT patch with POL? */

== PlayOnLinux and PlayOnMac ==

=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.

=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===
Read the advanced topic here:
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]

=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.

=== Do I have to install Wine to use PlayOnLinux? ===
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.

=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).

=== The application I am trying to install needs administrator rights to function correctly ===
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.

=== How do I install Steam, and Steam only? ===

If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:

# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window.

{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}

=== How can I use the CSMT patch with POL? ===

Up until recently (2015 ?), you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.).

Simply go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.

== Website ==

=== How can I post a bug report? ===
* [[How to Post a Bug Report|How to Post a Bug Report]]

=== How can I contribute an installer for an application? ===
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]

Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]

=== How do I request a version of Wine with a certain patch? ===
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]

=== Where does PlayOnLinux store it's virtual drives and cache? ===
All virtual drives are created and store here:

<code>~/.PlayOnLinux/wineprefix/</code>

The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''

=== How do I run Wine/POL as root or sudo? ===
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism.

* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]

=== Is there a list of solutions for common problems? ===
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:

# [[Troubleshooting Common Problems|Troubleshooting Common Problems]]
# [https://appdb.winehq.org/ appdb.winehq.org]
# Searching the POL/POM forums (see [[How to Post in the Forums|How to Post in the Forums]])
# Search engines for the web, of course.

=== My post was closed with a semi-automated reply? What did I break? ===
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service.

Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:

* https://www.playonlinux.com/en/terms.html

* [[How to Post in the Forums|How to Post in the Forums]]

== I want to contribute ==

=== Bash; I really want to know more ===
* http://www.gnu.org/software/bash/

* http://linuxconfig.org/bash-scripting-tutorial

* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/

* http://www.tldp.org/LDP/abs/html/

=== Python; I really want to know more ===
* https://www.python.org/

* https://docs.python.org/2/tutorial/

* http://www.learnpython.org/

Troubleshooting Common Problems

2020-06-02T19:37:58Z

Dadu042: /* Missing files */ Add libodbc

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

PlayOnLinux users, if winbind is not installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== PlayOnLinux ====

Do install WinBind.

Example on Ubuntu 18.xx : From Terminal, do type: 'sudo apt install winbind'.

==== PlayOnMac Edit the Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

=== Vulkan missing ===

{{Console|0055:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
0055:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
}}

This mean that a Vulkan file [https://en.wikipedia.org/wiki/Vulkan_(API) (Wikipedia)] is not installed.

Fix:
* Look at: [https://github.com/lutris/docs/blob/master/InstallingDrivers.md this page].

=== Xterm missing ===

POL v4 need this software.

Fix: install it from the packages manager of your OS.

Example on Ubuntu (command line to type into a Terminal software):
<pre class='code bash'>
sudo apt install xterm
</pre>

=== libodbc.so ===

{{Console|ODBC_LoadDriverManager failed to open library "libodbc.so"}}

Fix: install it from the packages manager of your OS.

Example on Ubuntu (command line to type into a Terminal software):
<pre class='code bash'>
sudo apt install unixodbc
</pre>

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the FreeType font ([https://en.wikipedia.org/wiki/FreeType Wikipedia]) is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22 (you may need to read in this page: 'About a script stored in 'Supported software', how to install it with a newer Wine version ?').

Troubleshooting Common Problems

2020-06-02T03:55:01Z

Dadu042: /* Missing files */ Xterm

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

PlayOnLinux users, if winbind is not installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== PlayOnLinux ====

Do install WinBind.

Example on Ubuntu 18.xx : From Terminal, do type: 'sudo apt install winbind'.

==== PlayOnMac Edit the Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

=== Vulkan missing ===

{{Console|0055:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
0055:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
}}

This mean that a Vulkan file [https://en.wikipedia.org/wiki/Vulkan_(API) (Wikipedia)] is not installed.

Fix:
* Look at: [https://github.com/lutris/docs/blob/master/InstallingDrivers.md this page].

=== Xterm missing ===

POL v4 need this software.

Fix: install it from the packages manager of your OS.

Example on Ubuntu (command line to type into a Terminal software):
<pre class='code bash'>
sudo apt install xterm
</pre>

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the FreeType font ([https://en.wikipedia.org/wiki/FreeType Wikipedia]) is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22 (you may need to read in this page: 'About a script stored in 'Supported software', how to install it with a newer Wine version ?').

Troubleshooting Common Problems

2020-05-17T09:20:30Z

Dadu042: /* FreeType font library */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

PlayOnLinux users, if winbind is not installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== PlayOnLinux ====

Do install WinBind.

Example on Ubuntu 18.xx : From Terminal, do type: 'sudo apt install winbind'.

==== PlayOnMac Edit the Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

=== Vulkan missing ===

{{Console|0055:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
0055:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
}}

This mean that a Vulkan file [https://en.wikipedia.org/wiki/Vulkan_(API) (Wikipedia)] is not installed.

Fix:
* Look at: [https://github.com/lutris/docs/blob/master/InstallingDrivers.md this page].

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the FreeType font ([https://en.wikipedia.org/wiki/FreeType Wikipedia]) is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22 (you may need to read in this page: 'About a script stored in 'Supported software', how to install it with a newer Wine version ?').

Troubleshooting Common Problems

2020-05-17T09:19:23Z

Dadu042: /* Vulkan missing */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

PlayOnLinux users, if winbind is not installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== PlayOnLinux ====

Do install WinBind.

Example on Ubuntu 18.xx : From Terminal, do type: 'sudo apt install winbind'.

==== PlayOnMac Edit the Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

=== Vulkan missing ===

{{Console|0055:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
0055:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
}}

This mean that a Vulkan file [https://en.wikipedia.org/wiki/Vulkan_(API) (Wikipedia)] is not installed.

Fix:
* Look at: [https://github.com/lutris/docs/blob/master/InstallingDrivers.md this page].

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22 (you may need to read in this page: 'About a script stored in 'Supported software', how to install it with a newer Wine version ?').

Troubleshooting Common Problems

2020-05-17T09:18:49Z

Dadu042: /* Vulkan missing */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

PlayOnLinux users, if winbind is not installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== PlayOnLinux ====

Do install WinBind.

Example on Ubuntu 18.xx : From Terminal, do type: 'sudo apt install winbind'.

==== PlayOnMac Edit the Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

=== Vulkan missing ===

{{Console|0055:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
0055:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
}}

This mean that a [https://en.wikipedia.org/wiki/Vulkan_(API) Vulkan] file is not installed.

Fix:
* Look at: [https://github.com/lutris/docs/blob/master/InstallingDrivers.md this page].

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22 (you may need to read in this page: 'About a script stored in 'Supported software', how to install it with a newer Wine version ?').

Troubleshooting Common Problems

2020-05-16T23:01:47Z

Dadu042: /* Missing files */ + Vulkan

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

PlayOnLinux users, if winbind is not installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== PlayOnLinux ====

Do install WinBind.

Example on Ubuntu 18.xx : From Terminal, do type: 'sudo apt install winbind'.

==== PlayOnMac Edit the Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

=== Vulkan missing ===

{{Console|0055:err:vulkan:wine_vk_init Failed to load libvulkan.so.1.
0055:err:vulkan:wine_vk_init Failed to load Wine graphics driver supporting Vulkan.
}}

This mean that the [https://en.wikipedia.org/wiki/Vulkan_(API) Vulkan] driver is not installed.

Fix:
* Look at: [https://github.com/lutris/docs/blob/master/InstallingDrivers.md this page].

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22 (you may need to read in this page: 'About a script stored in 'Supported software', how to install it with a newer Wine version ?').

POL & POM Terminology

2020-04-26T04:26:10Z

Dadu042: /* Components */

== Components / Functions ==

A "component" is a dependency, library, set of DLL's, etc., that Wine may need to use to get a program to run. The '''Install Components''' menu has similar functionality to other apps/scripts like ''winetricks''. If you are looking for a dependency from ''winetricks'', you will likely find it in the '''Install Components''' menu.

In the 2010's components were also called 'Functions'.

== Installer ==
A function or installer for PlayOnLinux/PlayOnMac. When you install a game or application from the '''Install''' menu, a script is downloaded and ran, which will guide you through the installation process. During installation, the installer will automatically use various functions to interact with our server and PlayOnLinux's API to gather everything needed to create a '''Virtual Drive''' to house your game or app.

== Script ==

A synonym of [[#installer|Installer]]

== Virtual drive ==
A virtual drive is simply the name that PlayOnLinux/PlayOnMac uses for a Wine '''WINEPREFIX''', which is essentially a self-contained Wine environment, complete with it's own ''drive_c'' & related folders and everything else. For more information on what a '''WINEPREFIX''' is, read [http://wiki.winehq.org/FAQ#Wineprefixes here].

== WineBuild ==

The name of the service and unofficial name of versions of Wine built specifically by our server, for use in PlayOnLinux/PlayOnMac. Just another name for "Wine version used for a POL/POM virtual drive". WineBuilds can be managed via the [[Managing Wine Versions|Manage Wine Versions]] dialogue.

The Configuration Window

2020-04-19T18:03:45Z

Dadu042: /* (1) - Mouse warp override */

The configuration window is where most of the action happens when it comes to customization, manual installs, testing, and debugging. Here we will cover all of the different items, tabs, fields, and buttons in detail. Let's get started.

== The Main Configuration Window ==

When you first install install PlayOnLinux/PlayOnMac and try to open the '''Configure''' window, it will be blank:

https://www.playonlinux.com/images/uploads/239.jpg

This is completely normal. It will start getting filled up after you install some software. After you install a few things, you will see more options:

https://www.playonlinux.com/images/uploads/241.jpg

=== (1) - Virtual Drive/Shortcut List ===

For each game or application that you install, a virtual drive and a shortcut will be associated with that application. The icon next to the Virtual Drive's name is the architecture of the '''WINEPREFIX'''. It will be either ''32'' or ''64'', indicating whether it is 32-bit or 64-bit.

=== (2) - General tab ===

The general tab has a number of options available to customize the virtual drive or the actual shortcut for running the app. This will be covered more in a moment. This is the default tab that you will see when highlighting a virtual drive or a shortcut.

=== (3) - Wine tab ===

This tab gives you quite a few options for configuring Wine itself. Any configuration done here is specific to the virtual drive or virtual drive of the shortcut highlighted in the Virtual Drive List.

=== (4) - Install Components tab ===

Install Components gives you access to a ton of dependencies that might be need to run applications through Wine. This includes .NET, DirectX, Microsoft Fonts, and much, much more. This list is covered in detail [[Components and Functions|here]].

=== (5) - Display tab ===

This is where you will be able to change to modify some of the registry entries for Wine's graphics support without actually going to the registry. Disable/Enable GLSL support, reported video memory size, etc..

=== (6) - Shortcut button ===

Clicking this button will search for .exe files in the selected virtual drive, and present you with a list of executables to create a shortcut from. You are also given an option to manually browse for an .exe.

=== (7) - Miscellaneous tab ===

Other features that do not fit into other categories. Running an .exe in the selected virtual drive, opening the POL Shell and virtual drive's directory, Mouse warp override options are found here.

=== (8) - Virtual Drive name ===

The name of the virtual drive.

=== (9) - Name of shortcut in virtual drive ===

The name of a shortcut contained within that virtual drive. You can have as many or as few as you would like. It is not uncommon to have multiple shortcuts, especially for manual installs or virtual drives with multiple apps installed.

=== (10) - New Virtual Drive button ===

This button opens a dialogue to create a new virtual drive. Useful for manual installs and testing. Please note that you will need to already have a '''POL WineBuild''' installed ('''Tools -> Manage Wine Versions''') to use this function correctly.

=== (11) - Remove Virtual Drive button ===

Click to delete the highlighted virtual drive. Use this with caution, as everything that is in the virtual drive will be deleted.

=== (12) - Virtual Drive/Shortcut name field ===

Depending on what you have highlighted (either a shortcut or a virtual drive), this will show you the name of it and allow you to modify it. It is recommended not to alter the virtual drive name once created, though the shortcut name is fine to customize in most cases.

=== (13) - Wine Version selection ===

A dropdown menu containing a list of installed Wine versions available for use in this virtual drive. Whichever is listed initially is the Wine versions in use in the highlighted virtual drive. The "plus" button allows you to open the '''Manage Wine Versions''' dialogue directly from this tab.

=== (14) - Debug Flags ===

These are debug flags to be used when launching a POL-installed application in '''Debug Mode'''. '''Debug Mode''' is covered in more detail here:

[[How to Read Debug Logs|How to Read Debug Logs]]

[http://wiki.playonlinux.com/index.php/Home#Advanced_Wine Advanced Wine]

=== (15) - Virtual Drive selection ===

When a shortcut is highlighted, this will allow you to assign the shortcut to a virtual drive. Whatever is initially listed is the current home of that shortcut.

=== (16) - Arguments field ===

When a shortcut is highlighted, this allows you to append command-line arguments to the executable that the shortcut links to. Useful for adding commanding-line options to a game's executable to enable in-game options and things like that.

== The Wine Tab ==

https://www.playonlinux.com/images/uploads/242.jpg

=== (1) - Configure Wine ===

This opens '''winecfg''' in the selected virtual drive. This is where you can set the version of Windows for the virtual drive, as well as set the virtual desktop settings and disks reported to Wine. For more information, check [http://wiki.winehq.org/winecfg here].

=== (2) - Registry Editor ===

Open up the Wine registry editor. Used for manually manipulating the Wine registry. For more information, check [http://wiki.winehq.org/regedit here].

=== (3) - Windows Reboot ===

Simply emulate a Windows reboot. Required by some applications during install.

=== (4) - Repair virtual drive ===

Essentially runs the process for creating a new virtual drive in the highlighted virtual drive. This is used in case the virtual drive fails to build correctly, or if a component/dependency for Wine fails to install or download correctly.

=== (5) - Wine uninstaller ===

A tool for uninstalling certain components out of a virtual drive, like Gecko, wine-mono, etc.. For more information, check [http://wiki.winehq.org/uninstaller here].

=== (6) - Kill processes ===

Kills all processes in virtual drive.

=== (7) - Task manager ===

Opens the Wine task manager, which is similar to the one found in Windows, in the highlighted virtual drive.

=== (8) - Command prompt ===

Opens a command prompt that emulates the Windows command prompt in the highlighted virtual drive. [http://wiki.winehq.org/cmd http://wiki.winehq.org/cmd]

== Install Components tab ==

This tab is where you will find dependencies to install. It is very similar to the functions in ''winetricks'', giving you the ability to automatically install dependencies that may be needed by Wine for certain applications.

The sheer complexity, size, and detail of this tab's content necessitates an entire section unto itself. That section can be viewed here:

* [[Components and Functions|Components and Functions]]

== Display tab ==

The '''Display tab''' gives you access to certain options that usually need to be set in the registry by hand. Off-screen rendering, GLSL support, and other options are found here.

https://www.playonlinux.com/images/uploads/249.jpg

=== (1) - GLSL Support ===

GLSL is the OpenGL Shading Language ([https://en.wikipedia.org/wiki/OpenGL_Shading_Language Wikipedia]).

Available options:

* ''default''
* ''enabled''
* ''disabled''

=== (2) - Direct Draw Renderer ===

Selects which ddraw renderer the backend should use.

Available options:

* ''default'' - OpenGL is the default setting
* ''gdi'' - Used for legacy reasons or if bugs exist in the OpenGL renderer
* ''opengl'' - Tells the backend to use OpenGL

=== (3) - Video memory size ===

Sets the amount of reported video memory (RAM) on your video card.

Available options:

* ''default'' - Simple auto-detection based on card type guessed from OpenGL capabilities
* ''list of common memory sizes''

=== (4) - Offscreen rendering mode ===

Avoids the depth buffer to copy between offscreen and onscreen targets. Introduces fallbacks in some drivers and exposes bugs in others.

Available options ([https://wiki.winehq.org/Useful_Registry_Keys ref]):

* ''default'' - fbo is the default setting
* ''fbo'' ([https://en.wikipedia.org/wiki/Framebuffer_object Framebuffer object)]
* ''backbuffer'' - Render offscreen render targets in the backbuffer
* ''pbuffer'' - Hardware accelerated rendering to an off-screen buffer, possibly with pixel formats which aren't normally supported by the X display
On Wikipedia you may read about [https://en.wikipedia.org/wiki/Multiple_buffering Multiple buffering].

=== (5) - Render target mode lock ===

Selects which mode is used for onscreen render targets.

Available options:

* ''default'' - Readtex is the default setting
* ''disabled'' - Disables render target locking
* ''readdraw'' - Uses glReadPixels for reading and writing
* ''readtex'' - Reads by glReadPixels, writes by drawing a textured quad

=== (6) - Multisampling ===

Mostly used for legacy options (games up to 1990's). It it no longer necessary to use any of the options.

Available options:

* ''default''
* ''enabled''
* ''disabled''

=== (7) - Strict Draw Ordering ===

Ensures any pending drawing operations are sent to the drivers at the cost of performance (frames per second).

Available options:

* ''default''
* ''enabled''
* ''disabled''

== Miscellaneous tab ==

The '''Miscellaneous tab''' provides functions that otherwise have no other proper place. These include opening up a POL shell in your default terminal, prefixing commands to shortcuts, and more.

https://www.playonlinux.com/images/uploads/254.jpg

=== (1) - Mouse warp override ===

Some games have issues with the mouse. This option has been known to correct this glitch in a lot of games.

Available options:

* ''default'' (enable)
* ''enable''
* ''disable''
* ''force''

=== (2) - Enter program's virtual drive or directory ===

Depending on what is highlighted on the left:

'''A:''' If the virtual drive is highlighted, you can open the virtual drive's directory in your system's default file browser

''or''

'''B:''' If the program shortcut is highlighted, you can open up the folder that the shortcut's executable file is located at in your system's default file browser

=== (3) - Open a shell ===

Open up your system's default terminal under the context of the virtual drive or program highlighted. You will have full access to the POL scripting API calls from there, as well as already be sandboxed within that virtual drive.

=== (4) - Run a .exe in this virtual drive ===

Allows you to run an .exe or .msi file within the context of the virtual drive or program highlighted. Will use whatever WineBuild is attached to that particular virtual drive, as well as sandboxing any action that happens therein.

=== (5) - Command to exec before running the program ===

When a program shortcut is highlighted, you can use this box to prefix commands to the shortcut. Handy in, say, the case of laptops with Nvidia and Intel graphics, and you need to use prefix ''primusrun'' or ''optirun'' before starting a particular game.

Manual Installations

2020-03-08T10:49:27Z

Dadu042: /* Was your software already tested with Wine by other users ? */

== Warning ==
Doing a manual installation is the '''hard way''' to use Playonlinux/Playonmac.

The easy way is to use a script already wrote by someone else (do search first into the 'Supported software' list, then in the forums), because the application that you want to use may need some additional libraries and it is very hard to know which ones.

== Was your software already tested with Wine by other users ? ==
If a software does not work with Wine, usually it will not work with Playonlinux/Playonmac.

Before to waste time, look first into https://appdb.winehq.org (at left side of the screen, click : 'Browse Apps'). 
In the test reports you may find informations about:
* Wine versions tested
* Software components used by the software (ie: [https://en.wikipedia.org/wiki/.NET_Framework Microsoft DotNet Framework], DirectX 10)
* [https://en.wikipedia.org/wiki/Middleware Middleware(s)] used by the software (ie: [https://en.wikipedia.org/wiki/Unity_(game_engine)|Unity Game Engine]).
* Missing [[Common Linux Libraries That Wine Might Need|common Linux Libraries that Wine might need]].

You may also look at the compatibility reports list of other projects using Wine such as:
* [https://pcgamingwiki.com/ pcgamingwiki.com] is also a fast way to find technical informations about games.
* The installation [http://www.gamersonlinux.com/forum/forums/guides.20/ guides hosted on Gamers on Linux.com].
* [https://lutris.net/ Lutris] (not commercial, run by enthusiasts. [https://en.wikipedia.org/wiki/Lutris Wikipedia]). Note: if you find the software you want, click 'View install script', then the button 'Download' ('the script'), this will show you the details about the tricks used by Lutris.
* [https://www.codeweavers.com/compatibility/ CodeWeavers] (pro support for Wine, commercial. [https://en.wikipedia.org/wiki/CodeWeavers Wikipedia])
* [https://github.com/PhoenicisOrg/scripts/tree/master/Applications POL v5 (Phoenicis)] scripts. Note: this software is still in [https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha Alpha version] state. Note: the scripts code will be completely different from POL v4.

== How to ==
=== In POL click the button 'Install' ===
At the bottom left of the window, click 'Install a non-listed program'.

=== An important step ===
This window is very important : ''''What would you like to do before installation ?'''' ([http://www.gamersonlinux.com/forum/attachments/acthree05-png.17168/ screenshot]) because it can allow :
* 'Use another version of Wine' (a version different from the ones that your POL installation already has).
* 'Configure Wine' (advanced setting, forcing Set_OS, ...).
* 'Install some libraries' (by using [https://en.wikipedia.org/w/index.php?title=Winetricks WineTricks] or POL functions).

=== Lots of steps ===
... Write me... (or look some examples tutorials already wrote for other softwares).

=== If your software requires Winetricks or POL libraries ===
[http://www.gamersonlinux.com/forum/attachments/acthree11-png.17174/ (screenshot example)]

* [https://www.playonlinux.com/en/supported_apps-100-0.html Details about the Playonlinux packages] (in the wiki, called 'Category: Features').

=== Shortcuts for the software installed ===
At the end of the manual installation, POL show you the list of .EXE files found in order to make shortcuts. Take the time to select carefully the files needed (you will be allow later to delete the useless shortcuts).

== Troubleshooting ==
If a application do not work, do not forget that you can try a other (install a newer) version of Wine. This is very useful for the old tutorials found on the web, Wine receive improvements and bug fixes.

== External links ==
* [http://www.gamersonlinux.com/forum/forums/guides.20/ www.gamersonlinux.com/] : Many examples of manual installations (called there 'step by step')

Manual Installations

2020-03-08T10:48:18Z

Dadu042: /* Was your software already tested with Wine by other users ? */

== Warning ==
Doing a manual installation is the '''hard way''' to use Playonlinux/Playonmac.

The easy way is to use a script already wrote by someone else (do search first into the 'Supported software' list, then in the forums), because the application that you want to use may need some additional libraries and it is very hard to know which ones.

== Was your software already tested with Wine by other users ? ==
If a software does not work with Wine, usually it will not work with Playonlinux/Playonmac.

Before to waste time, look first into https://appdb.winehq.org (at left side of the screen, click : 'Browse Apps'). 
In the test reports you may find informations about:
* Wine versions tested
* Software components used by the software (ie: [https://en.wikipedia.org/wiki/.NET_Framework Microsoft DotNet Framework], DirectX 10)
* [https://en.wikipedia.org/wiki/Middleware Middleware(s)] used by the software (ie: [https://en.wikipedia.org/wiki/Unity_(game_engine)|Unity Game Engine]).
* Missing [[Common Linux Libraries That Wine Might Need|common Linux Libraries that Wine might need]].

You may also look at the compatibility reports list of other projects using Wine such as:
* [https://pcgamingwiki.com/ pcgamingwiki.com] is also a fast way to find technical informations about games.
* The installation [http://www.gamersonlinux.com/forum/forums/guides.20/ guides hosted on Gamers on Linux.com].
* [https://lutris.net/ Lutris] (not commercial, run by enthusiasts. [https://en.wikipedia.org/wiki/Lutris Wikipedia]). Note: if you find the software you want, click 'View install script', then the button 'Download' ('the script'), this will show you the details about the tricks used by Lutris.
* [https://www.codeweavers.com/compatibility/ CodeWeavers] (pro support for Wine, commercial. [https://en.wikipedia.org/wiki/CodeWeavers Wikipedia])
* [https://github.com/PhoenicisOrg/scripts/tree/master/Applications POL v5 (Phoenicis)] scripts. Note: this software is still in [https://en.wikipedia.org/wiki/Software_release_life_cycle#Alpha Alpha version] state.

== How to ==
=== In POL click the button 'Install' ===
At the bottom left of the window, click 'Install a non-listed program'.

=== An important step ===
This window is very important : ''''What would you like to do before installation ?'''' ([http://www.gamersonlinux.com/forum/attachments/acthree05-png.17168/ screenshot]) because it can allow :
* 'Use another version of Wine' (a version different from the ones that your POL installation already has).
* 'Configure Wine' (advanced setting, forcing Set_OS, ...).
* 'Install some libraries' (by using [https://en.wikipedia.org/w/index.php?title=Winetricks WineTricks] or POL functions).

=== Lots of steps ===
... Write me... (or look some examples tutorials already wrote for other softwares).

=== If your software requires Winetricks or POL libraries ===
[http://www.gamersonlinux.com/forum/attachments/acthree11-png.17174/ (screenshot example)]

* [https://www.playonlinux.com/en/supported_apps-100-0.html Details about the Playonlinux packages] (in the wiki, called 'Category: Features').

=== Shortcuts for the software installed ===
At the end of the manual installation, POL show you the list of .EXE files found in order to make shortcuts. Take the time to select carefully the files needed (you will be allow later to delete the useless shortcuts).

== Troubleshooting ==
If a application do not work, do not forget that you can try a other (install a newer) version of Wine. This is very useful for the old tutorials found on the web, Wine receive improvements and bug fixes.

== External links ==
* [http://www.gamersonlinux.com/forum/forums/guides.20/ www.gamersonlinux.com/] : Many examples of manual installations (called there 'step by step')

Manual Installations

2020-03-08T10:32:56Z

Dadu042: /* Was your software already tested with Wine by other users ? */

== Warning ==
Doing a manual installation is the '''hard way''' to use Playonlinux/Playonmac.

The easy way is to use a script already wrote by someone else (do search first into the 'Supported software' list, then in the forums), because the application that you want to use may need some additional libraries and it is very hard to know which ones.

== Was your software already tested with Wine by other users ? ==
If a software does not work with Wine, usually it will not work with Playonlinux/Playonmac.

Before to waste time, look first into https://appdb.winehq.org (at left side of the screen, click : 'Browse Apps'). 
In the test reports you may find informations about:
* Wine versions tested
* Software components used by the software (ie: [https://en.wikipedia.org/wiki/.NET_Framework Microsoft DotNet Framework], DirectX 10)
* [https://en.wikipedia.org/wiki/Middleware Middleware(s)] used by the software (ie: [https://en.wikipedia.org/wiki/Unity_(game_engine)|Unity Game Engine]).
* Missing [[Common Linux Libraries That Wine Might Need|common Linux Libraries that Wine might need]].

You may also look at the compatibility reports list of other projects using Wine such as:
* [https://pcgamingwiki.com/ pcgamingwiki.com] is also a fast way to find technical informations about games.
* The installation [http://www.gamersonlinux.com/forum/forums/guides.20/ guides hosted on Gamers on Linux.com].
* [https://lutris.net/ Lutris] (not commercial, run by enthusiasts. [https://en.wikipedia.org/wiki/Lutris Wikipedia]). Note: if you find the software you want, click 'View install script', then the button 'Download' ('the script'), this will show you the details about the tricks used by Lutris.
* [https://www.codeweavers.com/compatibility/ CodeWeavers] (pro support for Wine, commercial. [https://en.wikipedia.org/wiki/CodeWeavers Wikipedia])

== How to ==
=== In POL click the button 'Install' ===
At the bottom left of the window, click 'Install a non-listed program'.

=== An important step ===
This window is very important : ''''What would you like to do before installation ?'''' ([http://www.gamersonlinux.com/forum/attachments/acthree05-png.17168/ screenshot]) because it can allow :
* 'Use another version of Wine' (a version different from the ones that your POL installation already has).
* 'Configure Wine' (advanced setting, forcing Set_OS, ...).
* 'Install some libraries' (by using [https://en.wikipedia.org/w/index.php?title=Winetricks WineTricks] or POL functions).

=== Lots of steps ===
... Write me... (or look some examples tutorials already wrote for other softwares).

=== If your software requires Winetricks or POL libraries ===
[http://www.gamersonlinux.com/forum/attachments/acthree11-png.17174/ (screenshot example)]

* [https://www.playonlinux.com/en/supported_apps-100-0.html Details about the Playonlinux packages] (in the wiki, called 'Category: Features').

=== Shortcuts for the software installed ===
At the end of the manual installation, POL show you the list of .EXE files found in order to make shortcuts. Take the time to select carefully the files needed (you will be allow later to delete the useless shortcuts).

== Troubleshooting ==
If a application do not work, do not forget that you can try a other (install a newer) version of Wine. This is very useful for the old tutorials found on the web, Wine receive improvements and bug fixes.

== External links ==
* [http://www.gamersonlinux.com/forum/forums/guides.20/ www.gamersonlinux.com/] : Many examples of manual installations (called there 'step by step')

Troubleshooting Common Problems

2020-02-26T19:36:26Z

Dadu042: /* PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

PlayOnLinux users, if winbind is not installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== PlayOnLinux ====

Do install WinBind.

Example on Ubuntu 18.xx : From Terminal, do type: 'sudo apt install winbind'.

==== PlayOnMac Edit the Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22 (you may need to read in this page: 'About a script stored in 'Supported software', how to install it with a newer Wine version ?').

Components and Functions

2020-02-26T07:05:52Z

Dadu042: /* GLSL Support */

Details, use cases, related errors, and more on each component.

== POL/POM Configuration -> Display ==

These commands allow to script the [[The_Configuration_Window#Display_tab|display settings available in the GUI]].

=== GLSL Support ===
Default setting (2019) is "enabled".

=== DirectDraw Renderer ===
Default setting (2019) is "opengl".

'''Script/Shell command:'''
<pre class="playonlinux code">
POL_Wine_Direct3D "DirectDrawRenderer" "gdi"
</pre>

=== Video memory size ===
See [[Scripting_-_Chapter_11:_List_of_Functions#POL_SetupWindow_VMS_.284.0.2B.29|this page about the command 'POL_SetupWindow_VMS']].

=== Offscreen rendering mode ===

== AdobeAir ==

'''What is it?'''

"The Adobe AIR runtime enables developers to package the same code into native applications and games for Windows and Mac OS desktops as well as iOS and Android devices, reaching over a billion desktop systems and mobile app stores for over 500 million devices."

-from http://get.adobe.com/air/

'''What does it do?'''

Installs the Adobe Air package.

'''When would I need it?'''

Certain Adobe products require this to be installed as a dependency.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_AdobeAir
</pre>

'''Links:'''

http://get.adobe.com/air/

== amstream ==

'''What is it?'''

A installer for a library.

'''What does it do?'''

Installs on Windows a Microsoft library, part of [https://en.wikipedia.org/wiki/DirectShow DirectShow].

'''When would I need it?'''

Some games/apps made after the 1990's and before the 2010's, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_amstream
</pre>

== ATI_Black-Screen_Fix ==

POL_Call POL_Install_ATI_Black-Screen_Fix

== atmlib ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs 'Adobe Type Manager'.

'''When would I need it?'''

[https://en.wikipedia.org/wiki/Adobe_Type_Manager Wikipedia].

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_atmlib
</pre>

== cc580 ==

POL_Call POL_Install_cc580

== CentralizedUserDirs ==

POL_Call POL_Install_CentralizedUserDirs

== corefonts ==

'''What is it?'''

"TrueType is an outline font standard developed by Apple and Microsoft in the late 1980s as a competitor to Adobe's Type 1 fonts used in PostScript. It has become the most common format for fonts on both the Mac OS and Microsoft Windows operating systems."

from http://en.wikipedia.org/wiki/TrueType

'''What does it do?'''

Downloads and registers TrueType fonts (TTF). Here is a list of the fonts that will be installed into the given virtual drive:

* andale mono
* arial black
* arial (bold, italic, bold italic)
* comic sans ms (bold)
* courier new (bold, italic, bold italic)
* georgia (bold, italic, bold italic)
* impact
* times new roman (bold, italic, bold italic)
* trebuchet (bold, italic, bold italic)
* verdana (bold, italic, bold italic)
* webdings

'''When would I need it?'''

Any time you experience missing text in an application, this would be the first place you would want to start. This is usually installed by default, though. If this does not work, try '''tahoma''' or '''tahoma2''' from the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Install Components tab], as those are the usual suspects in such acts of font thievery.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_corefonts
</pre>

'''Links:'''

http://en.wikipedia.org/wiki/TrueType

== crypt32 ==

'''What is it?'''

''crypt32'' does quite a few things relating to decrypting/encrypting data. Basic information in the links below.

'''What does it do?'''

"It supports encryption, decryption, and manipulation of certificates and related data structures."

from http://wiki.winehq.org/Crypt32

'''When would I need it?'''

Most of this is taken care of within Wine via the ''builtin'' dll. You may run into times when the native dll is needed, in which case the POL debug log will spit out an error saying that it tried to do something with it and it failed (like ''unhandled exception'' or ''cannot find crypt32.dll'', etc.). If you do happen to run into an error like this, we highly encourage you to report it to https://appdb.winehq.org so that the community there can possibly implement a fix that is native to Wine, eliminating the need for the actual Windows dll.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_crypt32
</pre>

'''Links:'''

http://wiki.winehq.org/Crypt32

== dcom98 ==

Microsofts's [https://en.wikipedia.org/wiki/Distributed_Component_Object_Model Distributed Component Object Model], 1998.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_dcom98
</pre>

== DirectX ==

=== d3dcompiler_43 ===

POL_Call POL_Install_d3dcompiler_43

=== d3dx10 ===

POL_Call POL_Install_d3dx10

=== d3dx11 ===

POL_Call POL_Install_d3dx11

=== d3dx9 ===

POL_Call POL_Install_d3dx9

=== d3dx9_29 ===

POL_Call POL_Install_d3dx9_29

=== d3dx9_35 ===

POL_Call POL_Install_d3dx9_35

=== d3dx9_36 ===

POL_Call POL_Install_d3dx9_36

=== d3dx9_40 ===

POL_Call POL_Install_d3dx9_40

=== d3dx9_42 ===

POL_Call POL_Install_d3dx9_42

=== d3dx9_43 ===

'''What is it?'''

A installer for a library.

'''What does it do?'''

Installs the Windows library, part of [https://en.wikipedia.org/wiki/DirectX DirectX] 9 version 43 (the latest is the better).

'''When would I need it?'''

Some games/apps made for DirectX up to version 9, if these don't work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_d3dx9_43
</pre>

=== dinput8 ===

POL_Call POL_Install_dinput8

=== directmusic ===

POL_Call POL_Install_directmusic

=== directplay ===

POL_Call POL_Install_directplay

=== directx9 ===

POL_Call POL_Install_directx9

=== dinput ===

POL_Call POL_Install_dinput

=== dsound ===

POL_Call POL_Install_dsound

=== dxdiag ===

POL_Call POL_Install_dxdiag

=== dxfullsetup ===

POL_Call POL_Install_dxfullsetup

== Desura ==

POL_Call POL_Install_desura

== devenum ==

POL_Call POL_Install_devenum

== DisableCrashDialog ==

POL_Call POL_Install_DisableCrashDialog

== DosboxDrive ==

POL_Call POL_Install_DosboxDrive

== .NET ==

=== POL_Install_dotnet11 ===

=== POL_Install_dotnet11sp1 ===

=== POL_Install_dotnet20 ===

=== POL_Install_dotnet20sp1 ===

=== POL_Install_dotnet20sp2 ===

=== POL_Install_dotnet30 ===

=== POL_Install_dotnet30sp1 ===

=== POL_Install_dotnet35 ===

=== POL_Install_dotnet35sp1 ===

=== POL_Install_dotnet40 ===

== fakeie6 ==

POL_Call POL_Install_fakeie6

== ffdshow ==

'''What is it?'''

A installer for a audio/video library.

'''What does it do?'''

Installs a codecs library, '[https://en.wikipedia.org/wiki/Ffdshow ffdshow]' (2014), in order to encode/decode audio/video files.

'''When would I need it?'''

Some games/apps that use audio/video files encoded by codecs supported by ffdshow.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_ffdshow
</pre>

== flashplayer ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs [https://en.wikipedia.org/wiki/Adobe_Flash_Player Adobe Flash Player files].

'''When would I need it?'''

Some games/apps that use files made with Adobe Flash (was quite common in the 2000's, mainly for web games).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_flashplayer
</pre>

== Flashplayer_ActiveX ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft's [https://en.wikipedia.org/wiki/ActiveX ActiveX] files (it was a competitor of Adobe Flash), up to the 2000's.

'''When would I need it?'''

Some games/apps that use files made with ActiveX (was quite common in the 2000's, mainly for web games and web apps).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_Flashplayer_ActiveX
</pre>

== FontsSmoothBGR ==

POL_Call POL_Install_FontsSmoothBGR

== FontsSmoothGrayScale ==

POL_Call POL_Install_FontsSmoothGrayScale

== FontsSmoothRGB ==

POL_Call POL_Install_FontsSmoothRGB

== gdiplus ==

'''What is it?'''

A installer.

'''What does it do?'''

Set Microsoft's [https://en.wikipedia.org/wiki/Graphics_Device_Interface Graphics Device Interface] graphic rendering mode.

'''When would I need it?'''

Some games/apps made up to the 2000's. Mainly when there is graphic rendering issues.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gdiplus
</pre>

== gecko ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Wine's fake version of Internet Explorer (implementation is based on a custom version of [https://en.wikipedia.org/wiki/Gecko_(software) Mozilla's Gecko]).

'''When would I need it?'''

Some games/apps made in the 2000's. Mainly when there is graphic issues.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_gecko
</pre>

'''Link'''

[https://wiki.winehq.org/Gecko Gecko] described on winehq.org

== gfwl ==

POL_Call POL_Install_gfwl

== gfwl86 ==

POL_Call POL_Install_gfwl86

== HackSteam ==

POL_Call POL_Install_HackSteam

== ie6 ==

POL_Call POL_Install_ie6

== ie8 ==

POL_Call POL_Install_ie8

== iv50 ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs Intel's [https://en.wikipedia.org/wiki/Indeo Indeo] library.

'''When would I need it?'''

Some games/apps made in the 1990's up to 2000's, using video files encoded with Indeo.

'''Script/Shell command:'''

<pre class="playonlinux code">

POL_Call POL_Install_iv50
</pre>

== linuxtrack-wine ==

POL_Call POL_Install_linuxtrack-wine

== LunaTheme ==
Installs a [https://en.wikipedia.org/wiki/Windows_XP_visual_styles Windows XP style] (theme) named Luna.

POL_Call POL_Install_LunaTheme

== mdac28 ==

POL_Call POL_Install_mdac28

== mfc ==

[https://en.wikipedia.org/wiki/Microsoft_Foundation_Class_Library Microsoft Foundation Class Library], a programming library for C++.

=== POL_Install_mfc40 ===
(1995)

=== POL_Install_mfc42 ===
(1998)

== Mono ==

[https://en.wikipedia.org/wiki/Mono_(software) Mono (Wikipedia)] is an open source implementation of the [https://en.wikipedia.org/wiki/Common_Language_Infrastructure Common Language Infrastructure] (.NET).

=== POL_Install_mono210 ===
v2.10 released in 2011.

=== POL_Install_mono26 ===

=== POL_Install_mono28 ===

== msasn1 ==

POL_Call POL_Install_msasn1

== msls31 ==

[https://www.playonlinux.com/fr/app-522-POL_Install_msls31.html POL_Call POL_Install_msls31]

'Microsoft LS' (Unix ls command for Microsoft).

== msvc ==

=== POL_Install_msvc100 ===

=== POL_Install_msvc80 ===

=== POL_Install_msvc90 ===

== msxml ==

=== POL_Install_msxml3 ===

=== POL_Install_msxml4 ===

=== POL_Install_msxml6 ===
'''What is it?'''

A installer for XML libraries.

'''What does it do?'''

Install Microsoft [https://en.wikipedia.org/wiki/MSXML MSXML] v6 (2005).

'''When would I need it?'''

Games/apps made before the 2010's years, that use XML files, for example to store text to displays or settings.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_msxml6
</pre>

== nop ==

POL_Call POL_Install_nop

== physx ==

POL_Call POL_Install_physx

== pngfilt ==

POL_Call POL_Install_pngfilt

== PrivateUserDirs ==

POL_Call POL_Install_PrivateUserDirs

== quartz ==

POL_Call POL_Install_quartz

== RegisterFonts ==

POL_Call POL_Install_RegisterFonts

== riched20 ==

=== POL_Install_riched20 ===

=== POL_Install_riched30 ===

== rsc ==

POL_Call POL_Install_rsc

== steam ==

'''What is it?'''

An installer for the game publishing platform Steam.

'''What does it do?'''

Downloads and Installs Steam client.

'''When would I need it?'''

Any time a game requires Steam to run.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_steam
</pre>

'''Links:'''

http://store.steampowered.com/

== steam_flags ==

'''What is it?'''

A helper script for Steam.

'''What does it do?'''

Set registry third-party flags to avoid steam installing them at the game's first launch.

'''When would I need it?'''

To avoid Steam reinstalling POL-installed dependencies (Wine sometimes requires some ''wizardry'' to get things working that the stock installers do not do, and can cause the application not to run if the workaround is overwritten or broken by the default installation being triggered by the Steam client.).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_steam_flags
</pre>

'''Links:'''

https://www.playonlinux.com/en/app-927-POL_Install_steam_flags.html

== tahoma ==

'''What is it?'''

An installer for the Microsoft font ''Tahoma''.

'''What does it do?'''

Downloads and registers ''Tahoma''.

'''When would I need it?'''

Any time the ''Tahoma'' font is needed.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_tahoma
</pre>

'''Links:'''

http://www.microsoft.com/typography/fonts/family.aspx?FID=19

== tahoma2 ==

'''What is it?'''

An alternative installer for the Microsoft font ''Tahoma''.

'''What does it do?'''

Downloads and registers Tahoma, but from a different package.

'''When would I need it?'''

Any time the ''Tahoma'' font is needed, where the regular ''Tahoma'' installer does not work (like Photoshop CS6).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_tahoma2
</pre>

'''Links:'''

http://www.microsoft.com/typography/fonts/family.aspx?FID=19

== ubigamelauncher ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs the Ubisoft's game launcher.

'''When would I need it?'''

Some games released by [https://en.wikipedia.org/wiki/Ubisoft Ubisoft].

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_ubigamelauncher
</pre>

== vbrun6 ==

'''What is it?'''

A installer.

'''What does it do?'''

Installs [https://en.wikipedia.org/wiki/Visual_Basic Microsoft Visual Basic] v6 libraries (app last released in 1998).

'''When would I need it?'''

Some games/apps made after 1990, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_vbrun6
</pre>

== vcrun ==

=== POL_Install_vcrun2005 ===

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft Visual C++ libraries.

'''When would I need it?'''

Some games/apps made after 2003, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_vcrun2005
</pre>

=== POL_Install_vcrun2008 ===

=== POL_Install_vcrun2010 ===

=== POL_Install_vcrun2012 ===

=== POL_Install_vcrun2013 ===

=== POL_Install_vcrun6 ===

'''What is it?'''

A installer.

'''What does it do?'''

Installs Microsoft Visual C v6 (1989) libraries.

'''When would I need it?'''

Some games/apps made after 1988, if Wine does not work without.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_vcrun6
</pre>

== VideoDriver ==

'''What is it?'''

A window does open and ask to select among the video cards installed. If there is only one video card, nothing happen.

'''What does it do?'''

Edit the Windows registry.

'''When would I need it?'''

If there is 2 video cards on the computer (ie: gaming notebooks, with a Intel iGPU + AMD GPU).

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Install_VideoDriver
</pre>

== wine64b ==

Old command (before POL/POM v4).

POL_Call POL_Install_wine64b

== wineasio ==

'''What is it?'''

WineASIO provides an ASIO driver interface from Wine to jack for low-latency audio and advanced audio/MIDI routing.

'''What does it do?'''

Checks for the following:

* Checks that the virtual drive is 32-bit

* Makes sure that the user is part of the ''audio'' group

* Confirms the presence of ''jack'' and ''qjackctl''

Then, if all checks pass, WineASIO is downloaded and registered into that virtual drive.

'''When would I need it?'''

Certain Adobe products require this to be installed as a dependency.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wineasio
</pre>

'''Links:'''

http://sourceforge.net/projects/wineasio/

== winhttp ==

'''What is it?'''

Install a HTTP library.

'''What does it do?'''

Install some Windows files.

'''When would I need it?'''

Apps made before the 2010's years.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_winhttp
</pre>

== wininet ==

POL_Call POL_Install_wininet

== wintrust ==

POL_Call POL_Install_wintrust

== wmp10 ==

POL_Call POL_Install_wmp10

== wmp9 ==

'''What is it?'''

A installer.

'''What does it do?'''

Install Windows Media Player 9 (~2003).

'''When would I need it?'''

Games/apps made before the 2010's years, that use .WMV video files or .WMA audio files.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wmp9
</pre>

== wmpcodecs ==

'''What is it?'''

A installer.

'''What does it do?'''

Install Windows Media Player (v9) codecs (audio + video).

'''When would I need it?'''

Games/apps made before the 2010's years, that use .WMV video files or .WMA audio files.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_wmpcodecs
</pre>

== wsh56 ==

POL_Call POL_Install_wsh56

== wsh57 ==

POL_Call POL_Install_wsh57

== xact ==

'''What is it?'''

A installer for audio libraries.

'''What does it do?'''

Installs Microsoft '[https://en.wikipedia.org/wiki/Cross-platform_Audio_Creation_Tool Cross-platform Audio Creation Tool]' (2002).

'''When would I need it?'''

Games/apps made before the 2010's years.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_xact
</pre>

== xinput ==

POL_Call POL_Install_xinput

== xmllite ==

'''What is it?'''

A installer for XML libraries.

'''What does it do?'''

Install Microsoft [https://en.wikipedia.org/wiki/MSXML MSXML] (2000's).

'''When would I need it?'''

Games/apps made before the 2010's years, that use XML files, for example to store text to displays or settings.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Install_xmllite
</pre>

== xna31 ==

POL_Call POL_Install_xna31

== xna40 ==

POL_Call POL_Install_xna40

== xvid ==

POL_Call POL_Install_xvid

== Other Functions ==

=== POL_Configurator_runparts ===

POL_Call POL_Configurator_runparts

=== POL_Download_retry ===

POL_Call POL_Download_retry

=== POL_Function_FontsSmoothBGR ===

POL_Call POL_Function_FontsSmoothBGR

=== POL_Function_FontsSmoothGrayScale ===

POL_Call POL_Function_FontsSmoothGrayScale

=== POL_Function_FontsSmoothRGB ===

POL_Call POL_Function_FontsSmoothRGB

=== POL_Function_NoCDWarning ===

'''What is it?'''

A warning message for the user of a script.

'''What does it do?'''

Does warn that the game/app will not work without a way to workaround the DRM (NoCD or other).

'''When would I need it?'''

To warn when a game can not work with POL/POM script without a NoCD.
Some DRMs does not work with Wine, originals CDs/DVDs are not recognized.

'''Script/Shell command:'''

<pre class="playonlinux code">
POL_Call POL_Function_NoCDWarning
</pre>

=== POL_Function_override_app_dlls ===

POL_Call POL_Function_override_app_dlls

=== POL_Function_OverrideDLL ===

POL_Call POL_Function_OverrideDLL

=== POL_Function_RootCommand ===

POL_Call POL_Function_RootCommand

=== POL_Function_sandbox ===

POL_Call POL_Function_sandbox

=== POL_Function_SetNativeExtension ===

POL_Call POL_Function_SetNativeExtension

=== POL_Function_simplecdscript ===

POL_Call POL_Function_simplecdscript

=== POL_Function_simplescript ===

POL_Call POL_Function_simplescript

=== POL_Function_Sleep ===

POL_Call POL_Function_Sleep

=== POL_Gamefront_Download ===

POL_Call POL_Gamefront_Download

=== POL_GetTool_samba3 ===

POL_Call POL_GetTool_samba3

=== POL_GoG_download ===

POL_Call POL_GoG_download

=== POL_GoG_Extract ===

POL_Call POL_GoG_Extract

=== POL_GoG_install ===

POL_Call POL_GoG_install

=== POL_GoG_setup ===

POL_Call POL_GoG_setup

Scripting - Chapter 11: List of Functions

2020-02-03T20:54:19Z

Dadu042: /* POL_RequiredVersion (4.0.15+) */

== Legend of colour for the arguments ==
* ''Colours not currently showing up right now. They will be added soon.''

Red: Required argument.

Orange : Required argument if further arguments are present, but can be left empty ("").

Blue : Optional argument, but in some cases required.

Green : Optional argument.

== Start and stop the graphical interface ==

=== POL_GetSetupImages (4.0+) ===

'''Purpose:'''

Download custom images that will be displayed during the installation wizard.

'''Arguments:'''

# Optional --force option to override any cached images
# URL of top image.
# URL of left image.
# Name of the cache directory where to store the images (usually $TITLE).

'''Description:'''

To liven up installations, two images are currently displayed by PlayOnLinux/PlayOnMac installers:

- a 150 by 356 pixels image at the left of "presentation" introductory screen

- a 64 by 64 pixels "icon" image at the upper right corner for the remaining of the installation

Default images are normally displayed, but they can be replaced by custom images of the same resolution using this statement. Both JPEG and PNG file formats are supported, JPEG being the preferred format.

Downloaded images will be stored in a cache to avoid repeated downloads. There's no cache invalidation mechanism, so in case incorrect images may have been put into users' cache, you can:

- either preceed arguments with --force to override any cache content;

- change the name of the cache directory to a different value. Make sure you still use something unique to the script though, say "$TITLE_201510120640", etc.

'''Prerequisite:'''

This statement must be used before '''POL_SetupWindow_Init'''.

'''Example:'''
<pre class="playonlinux code">
POL_GetSetupImages "http://files.playonlinux.com/resources/setups/AC2/top.jpg" "http://files.playonlinux.com/resources/setups/AC2/left.jpg" "$TITLE"
</pre>

=== POL_SetupWindow_Init (4.0+) ===

'''Purpose:'''

Opens the installation wizard window.

'''Arguments:'''

None

'''Description:'''

Open the UI window that will be used by the PlayOnLinux installation wizard script.

While few initialization statements must be run before '''POL_SetupWindow_Init''', most statements expect the installation window to be opened to either display some progression feedback, or report error cases; So this statement should be used very near the beginning of scripts.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_Init
</pre>

=== POL_SetupWindow_Close (4.0+) ===

'''Purpose:'''

Closes the installation wizard window.

'''Arguments:'''

None

'''Description:'''

Close the UI window; Well behaved installation scripts should use this statement before exiting. Since most statements expect the installation window to be opened to either display some progression feedback, so it is recommended to use '''POL_SetupWindow_Close''' as late as possible in the scripts.

If some error has been detected during the execution of the script by the embedded debugger (see "Debugging Commands" below), at this point PlayOnLinux/PlayOnMac will offer the user to send an automated bug report, containing a log of the script execution, and any comments (s)he wants to add about the issue.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_Close
</pre>

== PlayOnLinux graphical interface ==

{{Warning|All the functions below need the command POL_SetupWindow_Init to be executed beforehand.}}

=== POL_SetupWindow_presentation (4.0+) ===

'''Purpose:'''

Display a standard introductory screen for the install script and the software it's about to install.

'''Arguments:'''

# Software name (often $TITLE).
# Software publisher.
# Site of the publisher.
# Script author.
# Prefix name (usually $PREFIX).

'''Description:'''

This statement will display the name of the software the install script is about to install, along with basic informations about it, and the name of the script author, in a standardized format. If some "left image" has been setup with '''POL_GetSetupImages''', it will be displayed at the same time.

This can be used right before the installation starts, so the user has one more chance to check what is about to be installed, and eventually cancel the installation.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_presentation "$TITLE" "Mozilla" "http://www.mozilla.com" "SuperPlumus and NSLW" "$PREFIX"
</pre>

=== POL_SetupWindow_free_presentation (4.0+) ===

'''Purpuse:'''

Display a free format introductory screen.

'''Arguments:'''

# Software name (often $TITLE).
# Message.

'''Description:'''

In case the standardized format of '''POL_SetupWindow_presentation''' introductory screen does not fit the needs of the install script, this statement let you use any text you want instead. If some "left image" has been defined with '''POL_GetSetupImages''' statement, it will be displayed at the same time.

This can be used right before the installation starts, so the user has one more chance to check what is about to be installed, and eventually cancel the installation.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_free_presentation "$TITLE" "Welcome to Mozilla Firefox installation wizard."
</pre>

=== POL_SetupWindow_message (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).

'''Description:'''

Display a message.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_message "Hello world!" "$TITLE"
</pre>

=== check_one - POL_SetupWindow_missing (4.0-4.1.1) ===

'''Arguments for check_one:'''

# Program that must be present.
# Package that contains this program.

'''Description:'''

Check the availability of one or more programs required by the script.

Call check_one as many times as needed (once per program), then use POL_SetupWindow_missing.

'''Example:'''
<pre class="playonlinux code">
check_one "p7zip" "p7zip"
POL_SetupWindow_missing
</pre>

=== POL_SetupWindow_file (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# File to display.

'''Description:'''

Display the content of a file.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_file "Changelog" "$TITLE" "$POL_System_TmpDir/changelog.txt"
</pre>

=== POL_SetupWindow_licence (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# File to display.

'''Description:'''

Similar to the command POL_SetupWindow_file, but adds an "I agree" checkbox.

Useful for displaying licenses.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_licence "Licence:" "$TITLE" "$POL_System_TmpDir/licence.txt"
</pre>

=== POL_SetupWindow_pulsebar - POL_SetupWindow_pulse - POL_SetupWindow_set_text (4.0+) ===

'''Arguments for POL_SetupWindow_pulsebar:'''

# Message.
# Title (often $TITLE).

'''Arguments for POL_SetupWindow_pulse:'''

# Percentage.

'''Arguments for POL_SetupWindow_set_text:'''

# Current text.

'''Description:'''

Display a progression bar, from 0 to 100%.

POL_SetupWindow_pulsebar display the progression bar.

POL_SetupWindow_pulse changes the progression value, from 0 to 100%.

POL_SetupWindow_set_text modifies the current message (different from POL_SetupWindow_pulsebar message).

Useful for displaying licenses.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_pulsebar "Installing patchs 1 to 5." "$TITLE"

POL_SetupWindow_set_text "Installation of patch 1 in progress"
POL_Wine "$POL_System_TmpDir/patch1.exe"
POL_SetupWindow_pulse "20" # meaning 20%

POL_SetupWindow_set_text "Installation of patch 2 in progress"
POL_Wine "$POL_System_TmpDir/patch2.exe"
POL_SetupWindow_pulse "40"

POL_SetupWindow_set_text "Installation of patch 3 in progress"
POL_Wine "$POL_System_TmpDir/patch3.exe"
POL_SetupWindow_pulse "60"

POL_SetupWindow_set_text "Installation of patch 4 in progress"
POL_Wine "$POL_System_TmpDir/patch4.exe"
POL_SetupWindow_pulse "80"

POL_SetupWindow_set_text "Installation of patch 5 in progress"
POL_Wine "$POL_System_TmpDir/patch5.exe"
POL_SetupWindow_pulse "100"
</pre>

=== POL_SetupWindow_wait (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).

'''Description:'''

Display an indeterminate progress bar.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_wait "Please wait" "$TITLE"
</pre>

=== POL_SetupWindow_textbox (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Default value.

'''Description:'''

Display some window asking the user to type in something.

'''Return:'''

What the user typed is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_textbox "Votre pseudo :" "$TITLE"
</pre>

=== POL_SetupWindow_textbox_multiline (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Default value.

'''Description:'''

Similar to POL_SetupWindow_textbox, but typing happens on several lines.

'''Return:'''

What the user typed is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_textbox_multiline "Enter a description for the program" "$TITLE"
</pre>

=== POL_SetupWindow_browse (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Default value.

'''Description:'''

Ask the user to select a file.

'''Return:'''

The path of the file selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_browse "Please select the program." "$TITLE"
</pre>

=== POL_SetupWindow_question (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).

'''Description:'''

Ask a question to the user (that can be answered by Yes or No).

'''Return:'''

Answer is returned in the $APP_ANSWER variable (TRUE for Yes, FALSE for No).

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_question "Message" "Title"
</pre>

=== POL_SetupWindow_menu (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).

'''Description:'''

Display a menu to the user, asking him to select one entry among the choices provided.

'''Return:'''

The choice selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_menu "What's your favorite color?" "$TITLE" "Red~Green~Blue" "~"
</pre>

=== POL_SetupWindow_menu_num (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).

'''Description:'''

Similar to the command POL_SetupWindow_menu except that instead of returning the name of the selected choice (Red for example), it returns the position of the selected choice in the list, as a number (0 being the 1st choice).

'''Return:'''

The choice selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_menu_num "What's your favorite color?" "$TITLE" "Red~Green~Blue" "~"
</pre>

$APP_ANSWER will contain 0 if the user selected Red, 1 for Green, or 2 for Blue.

=== POL_SetupWindow_menu_list (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).
# Default choice.

'''Description:'''

Similar to the command POL_SetupWindow_menu but displays a drop-down list.

'''Return:'''

The choice selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_menu_list "What's your favorite color?" "$TITLE" "Red~Green~Blue" "~"
</pre>

=== POL_SetupWindow_checkbox_list (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).

'''Description:'''

Show a list of options and checkboxen to the user, asking him to select the option(s) he wants.

'''Return:'''

The option(s) selected by the user are returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_checkbox_list "What are your favorite colors?" "$TITLE" "Red~Green~Blue" "~"
if [ "$(echo $APP_ANSWER | grep -o "Red")" != "" ]
then
# Red was selected
fi
if [ "$(echo $APP_ANSWER | grep -o "Green")" != "" ]
then
# Green was selected
fi
if [ "$(echo $APP_ANSWER | grep -o "Blue")" != "" ]
then
# Blue was selected
fi
</pre>

=== POL_SetupWindow_cdrom (4.0+) ===

'''Description:'''

Ask the user to select a loaded CD/DVD.

'''Return:'''

The path to the drive selected by the user is returned in the $CDROM variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_cdrom
</pre>

=== POL_SetupWindow_check_cdrom (4.0+) ===

'''Arguments:'''

# 1, 2, etc. List of files that should be present.

'''Description:'''

Check, in order, if the files specified exist on the CD/DVD. If one is found, $CDROM_SETUP is set to the file path, and the script continues;

Otherwise, execute POL_SetupWindow_cdrom again.

'''Return:'''

Should be used right after POL_SetupWindow_cdrom.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_check_cdrom "Data/32_icon.ico"
</pre>

=== POL_SetupWindow_InstallMethod (4.0+) ===

'''Arguments:'''

# Comma separated list of installation methods available.

'''Description:'''

Ask the user want installation method he wants, among the available choices.

'''Available installation methods:'''

'''LOCAL, CD, DVD, DOWNLOAD, STEAM, STEAM_DEMO.'''

'''Return:'''

The choice selected by the user is returned in the $INSTALL_METHOD variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_InstallMethod "LOCAL,CD,STEAM"
</pre>

== POL_RequiredVersion (4.0.15+) ==

'''Arguments:'''

# Minimum version.

'''Description:'''

Checks that the user is running a version of PlayOnLinux/PlayOnMac that is at least equal to the version provided as argument; If not, stops the script execution while alerting the user that (s)he needs to upgrade to run the script.

This is very useful to put near the top of scripts that use statements of features that only appeared in a relatively version of PlayOnLinux/PlayOnMac.

Remarks:
* The sweet spot to place POL_RequiredVersion is between POL_SetupWindow_Init (the interface must be ready to display a user warning) and POL_Debug_Init (so that the usage of an old version of PlayOnLinux/PlayOnMac does not trigger all the embedded debugger/bug reporting workflow);
* While POL_RequiredVersion can display warnings on its own, this function only appeared in PlayOnLinux 4.0.15, and PlayOnLinux 4.0.14 is still the default in some distributions (2013) ; So for the time being, it is recommended to complement it with a check that the statement itself exists, as shown in the example below.
'''Prerequisite:'''

The command POL_SetupWindow_Init must have been used beforehand.

'''Example:'''
POL_RequiredVersion 4.0.18 || POL_Debug_Fatal "$TITLE won't work with $APPLICATION_TITLE $VERSION\nPlease update"

'''POL/POM and maximum Wine versions supported'''
* 4.2.2: Wine 3.0.3, and 3.20
* 4.2.12: Wine 3.0.3, and 3.20
* 4.3.4: Wine 3.0.5, 3.21, and 5.x

== POL_AdvisedVersion (4.0.15+) ==

'''Arguments:'''

# Minimum version.

'''Description:'''

Very similar to POL_RequiredVersion (see POL_RequiredVersion), but do not stop the script execution after having alerted the user.

The script should be able to run on older versions of PlayOnLinux/PlayOnMac, even if in some kind of degraded mode.

All remarks about POL_RequiredVersion apply; If you use both in the same script, put POL_RequiredVersion first.

'''Prerequisite:'''

The command POL_SetupWindow_Init must have been used beforehand.

'''Example:'''
NEEDED=4.0.18
POL_AdvisedVersion $NEEDED || POL_Debug_Message "$TITLE works better with $APPLICATION_TITLE $NEEDED\nPlease update"

== POL_Shortcut (4.0+) ==

'''Arguments:'''

# Executable filename.
# Launcher name (often $TITLE).
# Optional name of the icon to download from PlayOnLinux website.
# Optional executable arguments.
# Optional list of categories the program belongs to (4.2+)

'''Description:'''

Create a launcher in PlayOnLinux. If some path is specified before the executable filename, it will be interpreted relative to the "drive_c" subdirectory of the prefix. Note that Wine, like Windows, translates the name of the "Program Files" directory according to the user locale, so you should always use the special variable $PROGRAMFILES instead of its name in your own locale.

If no path is specified (recommended), the executable filename is looked up using a case insensitive [http://linux.die.net/man/7/glob glob] search, so you can use wildcards as needed; On the other hand if the program filename contains special characters they may require quoting to avoid being interpreted as wildcards.

PlayOnLinux can also create entries in system menus, but only if category(ies) is(are) provided. The list of valid categories can be found on freedesktop.org site (see [http://standards.freedesktop.org/menu-spec/latest/apa.html main] and [http://standards.freedesktop.org/menu-spec/latest/apas02.html additional] categories). More than one category can be provided, the list separated (and optionally terminated) by semicolons (;).

'''Prerequisite:'''

The command POL_Wine_SelectPrefix must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Shortcut "firefox.exe" "$TITLE"
</pre>

== POL_Shortcut_InsertBeforeWine (4.0+) ==

'''Arguments:'''

# Launcher name (often $TITLE).
# Command to add.

'''Description:'''

Allows to run an extra command each time a program will be about to start.

'''Example:'''
<pre class="playonlinux code">
POL_Shortcut_InsertBeforeWine "Jedi Knight II" "export __GL_ExtensionStringVersion=17700"
</pre>

== POL_Shortcut_QuietDebug (4.0.17+) ==
'''Arguments:'''

# Launcher name (often $TITLE).

'''Description:'''

Avoid displaying "This program may have crashed" dialog box when the program launched by a shortcut exits with a non-zero exitcode.

This is a bandaid for programs exiting with meaningless exitcodes, as it sometimes happens since it's of little consequence under Windows.

'''Example:'''
POL_Shortcut_QuietDebug "Sam and Max S2E1: Ice Station Santa"

== POL_Shortcut_Document (4.0.15+) ==
'''Arguments:'''
# Launcher name (often $TITLE).
# Path to some documentation file

'''Description:'''

Link some documentation file to an existing PlayOnLinux shortcut; The documentation will be available using Right-click on shortcut > Read the manual.

Document file is looked up using the same rules POL_Shortcut uses to find executables.

'''Prerequisite:'''

The command POL_Wine_SelectPrefix must have been used beforehand.

'''Example:'''
POL_Shortcut_Document "$TITLE" "README.txt"

== POL_Browser (4.0+) ==

'''Arguments:'''

# URL to open.

'''Description:'''

Opens a URL in the user's default Internet browser.

'''Example:'''
<pre class="playonlinux code">
POL_Browser "http://www.playonlinux.com"
</pre>

== POL_Download (4.0+) ==

'''Arguments:'''

# URL to download.
# (Optional) Expected MD5 digest of the downloaded file

'''Description:'''

Download a URL to a local file. The file will be created in the current directory, named after the last component of the URL.

If an expected MD5 digest is provided (recommended), the downloaded file will then be run thru the MD5 digest algorithm, and the result compared to the expected value. If they differ, it will be assumed the download broke and the user will be asked if (s)he wants the download to be reattempted.

This is a very effective way to ensure that the downloaded content is the expected one, however some URLs lead to resources that are very often updated, in which case providing an up-to-date MD5 digest can be impractical.

'''Example:'''
POL_Download "http://repository.playonlinux.com/divers/QuickTime.qtp" "417f9bf5ec52d3bfa5826b4905658dac"

== POL_Download_Resource (4.0+) ==

'''Arguments:'''

# URL to download.
# Expected MD5 digest of the downloaded file
# (Optional) Subfolder to download the file to

'''Description:'''

Download a URL to the local file cache, if not already present. The file will be created in $POL_USER_ROOT/ressources directory (unless some subfolder is provided, in which case it will be created under $POL_USER_ROOT/ressources/<subfolder>, creating the subfolder if needed), and named after the last component of the URL.

Contrary to POL_Download, '''the MD5 digest is mandatory''' for POL_Download_Resource, as it will not only be used to validate the download (see POL_Download), but is also used, if some file already exists in the cache, to check that it has the expected content.

Beware that files stored in the cache will potentially stay there for a very long time, since PlayOnLinux never does any kind of cache cleanup, based on time or size; So you should only use POL_Download_Resource for files that are likely to be reused, possibly because they're necessary for several install scripts.

'''Example:'''
POL_Download_Resource "http://downloads.sourceforge.net/ffdshow-tryout/ffdshow_beta7_rev3154_20091209.exe" "c3f75f29521f749f9c9fc5489544cb04"

== POL_System_TmpCreate (4.0+) ==

'''Arguments:'''

# Name of the temporary directory (often $PREFIX).

'''Description:'''

Creates the temporary directory dedicated to the script.

'''Return:'''

$POL_System_TmpDir will contain the path of the created temporary directory.

'''Example:'''
<pre class="playonlinux code">
POL_System_TmpCreate "$PREFIX"
</pre>

== POL_System_TmpDelete (4.0+) ==

'''Description:'''

Removes the script's temporary directory.

'''Example:'''
<pre class="playonlinux code">
POL_System_TmpDelete
</pre>

== POL_System_SetArch (4.0+) ==

'''Arguments:'''

# Supported architectures (see below).

'''Description:'''

Set the (Wine) architectures supported by the script.

'''Allowed values:'''

* '''auto''': Use the version of Wine matching the system architecture (Wine x86 on x86 and Wine x64 on amd64).

* '''x86''': Use the x86 version of Wine for installation (useful if the program doesn't work well with the x64 version).

* '''amd64''': Use the x64 version of Wine for installation (if the system architecture is x86, the script stops).

'''Example:'''
<pre class="playonlinux code">
POL_System_SetArch "auto"
</pre>

'''Prerequisite:'''

The command POL_Wine_PrefixCreate must be located after.

== POL_Call (4.0+) ==

'''Arguments:'''

# Function name.
# 2, 3, etc.: Function arguments, if necessary (very few functions take arguments).

'''Description:'''

Download and execute a script from the Functions category (the list of functions and their basic information for each can be found here: [[Components and Functions|Components and Functions]]).

'''Prerequisite:'''

For most functions, the commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Call POL_Install_vcrun6
</pre>

== Wine-related functions ==

=== POL_Wine_SelectPrefix (4.0+) ===

'''Arguments:'''

# Prefix name (often $PREFIX).

'''Description:'''

Select the prefix that will be used by Wine (mandatory, even if the prefix hasn't been created yet).

'''Example:'''
<pre class="playonlinux code">
POL_Wine_SelectPrefix "$PREFIX"
</pre>

=== POL_Wine_PrefixExists (4.0+) ===

'''Arguments:'''

# Prefix name (often $PREFIX).

'''Description:'''

Check if a prefix exists (useful for game extensions and patches).

'''Return:'''

The function displays True if the prefix exists, and False otherwise.

'''Example:'''
<pre class="playonlinux code">
if [ "$(POL_Wine_PrefixExists "$PREFIX")" = "False" ]
then
# The préfixe doesn't exist
fi
</pre>

=== POL_Wine_PrefixCreate (4.0+) ===

'''Arguments:'''

# Wine version.

'''Description:'''

Creates or updates a prefix. It is possible to use a version of Wine different from the one installed system wide on user's computer, by specifying this version as first argument.

'''Prerequisite:'''

The command POL_Wine_SelectPrefix must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_PrefixCreate "1.3.4"
</pre>

=== POL_Wine (4.0+) ===
'''Arguments:'''
* Program pathname.
* 2, 3, etc.: program arguments, if any.
'''Description:'''

This command will run the given program; It works exactly like the "wine" command, but uses the Wine versions management and logging facilities of PlayOnLinux.

While most programs started that way will behave synchronously (in other words, will block the script until they're finished), some don't and the POL_Command will need to be followed by a POL_Wine_WaitExit command to prevent the rest of the script from being executed before the program has finished.

See POL_Wine_WaitBefore and POL_Wine_WaitExit.

Note: Using '''start /unix''' before the program name can fix issues of access and installation paths with several CD/DVD. However, the use of start /unix makes POL_Wine asynchronous, and since asynchronous programs are not automatically killed if the script is aborted from PlayOnLinux side, it should only be used when necessary.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

=== POL_SetupWindow_VMS (4.0+) ===
'''Arguments:'''

# Minimum amount of onboard video memory required, in MB.

'''Description:'''

Ask the user how much (dedicated) RAM his videocard has, since it is actually very difficult to determine this value in a portable way.

If the value is lower than the minimum argument value, the user is warned that the program being installed is likely not to work correctly. In all cases, the script goes on and the value is written in the Wine registry.

The user reply is cached so that it doesn't need to be asked again during the next installations. In case of mistake, or if the amount of video memory changes, the cached value can be erased by opening the PlayOnLinux console, and typing "POL_Config_Delete VMS" (for a lack of GUI support at the moment).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_VMS "128"
</pre>

=== Set_OS (4.0+) ===

'''Arguments:'''

# Windows version to emulate.
# Service pack.

'''Description:'''

Modifies the Windows version emulated by Wine.

'''Default value:''' winxp (Windows XP).

'''Allowed values:'''

'''Windows versions''': win7, vista, win2003, winxp, win2k, winnt, winme, nt40, win98, win95, win31.

'''Services packs''': sp1, sp2, sp3.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_OS "winxp"
</pre>

=== Set_Managed (4.0+) ===

'''Arguments:'''

# On/Off.

'''Description:'''

Set if the window manager will be allowed to manage Wine windows.

'''Default value''': On.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_Managed "Off"
</pre>

=== Set_SoundDriver (4.0+) ===

'''Arguments:'''

# alsa/oss/esd.

'''Description:'''

Set the audio driver Wine will use.

{{Info|This command does nothing under PlayOnMac, since it is useless in that environment.}}

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_SoundDriver "alsa"
</pre>

=== POL_Wine_Direct3D (4.0+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\Direct3D].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_Direct3D "UseGLSL" "disabled"
</pre>

=== POL_Wine_X11Drv (4.0.14+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\X11 Driver].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_X11Drv "DXGrab" "Y"
</pre>

=== POL_Wine_DirectSound (4.0+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\DirectSound].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_DirectSound "HardwareAcceleration" "Emulation"
</pre>

=== POL_Wine_DirectInput (4.0+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\DirectInput].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_DirectInput "MouseWarpOverride" "force"
</pre>

=== POL_Wine_GetRegValue (4.0+) ===

'''Arguments:'''

# Setting to read (the key is not required).

'''Description:'''

This function returns the value of a setting from the registry.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Return:'''

The function displays the value of the specified setting.

'''Example:'''
<pre class="playonlinux code">
VALUE="$(POL_Wine_GetRegValue "MouseWarpOverride")"
</pre>

=== Set_Desktop (4.0+) ===

'''Arguments:'''

# On/Off.
# Virtual desktop width (if it is enabled).
# Virtual desktop height (if it is enabled).

'''Description:'''

Sets the Wine virtual desktop settings.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_Desktop "On" "1024" "768"
</pre>

=== Set_WineWindowTitle (4.0+) ===

'''Arguments:'''

# Virtual desktop name.

'''Description:'''

Set the title of the virtual desktop window (purely aesthetic effect).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_WineWindowTitle "$TITLE"
</pre>

=== POL_Wine_InstallFonts (4.0+) ===

'''Description:'''

This command installs standard (but not installed by default) fonts into the prefix.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_InstallFonts
</pre>

=== POL_Wine_SetVideoDriver (4.0+) ===

'''Description:'''

Set correct video driver (when Wine fails to do it properly).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_SetVideoDriver
</pre>

=== POL_Wine_OverrideDLL (4.0+) ===

'''Arguments:'''

# Mode of override.
# 3, 4, etc.: DLL names (without .dll suffix).

'''Description:'''

Set the override mode for one or more dynamic library(ies).

'''Allowed override modes:'''

"native", "builtin", "native,builtin", "builtin,native", or empty value ("") to disable the DLL(s).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_OverrideDLL "native" "msvcrt"
POL_Wine_OverrideDLL "" "msvcrt" # To disable the DLL
</pre>

=== POL_Wine_OverrideDLL_App (4.0+) ===

'''Arguments:'''

# Executable name.
# Mode of override.
# 3, 4, etc.: DLL names (without .dll suffix).

'''Description:'''

Set the override mode for one or more dynamic library(ies), but only for a specific program.

'''Allowed override modes:'''

"native", "builtin", "native,builtin", "builtin,native", or empty value ("") to disable the DLL(s).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_OverrideDLL_App "firefox.exe" "native" "msvcrt"
POL_Wine_OverrideDLL_App "firefox.exe" "" "msvcrt" # To disable the DLL
</pre>

=== POL_Wine_WaitBefore (4.0.15+) ===

'''Arguments:'''

# Program name.

'''Description:'''

Placed before a POL_Wine command that starts a program synchronously (ie a "blocking" POL_Wine command), it will display a standard wait message while it runs.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
POL_Wine_WaitBefore "$TITLE"

=== POL_Wine_WaitExit (4.0+) ===

'''Arguments:'''

# Program name.

'''Description:'''

Placed after a POL_Wine command that starts a program asynchronously (ie a "non-blocking" POL_Wine command), it will display a standard wait message while it runs and wait for its completion.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_WaitExit "$TITLE"
</pre>

=== POL_Wine_reboot (4.0+) ===

'''Description:'''

Emulate a Windows reboot.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_reboot
</pre>

== Debugging commands ==

=== POL_Debug_Init (4.0+) ===

'''Description:'''

Start debugging system.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Init
</pre>

=== POL_Debug_Message (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Write a message to the installation log (not shown to the user).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Message "Modifying config.cfg file."
</pre>

=== POL_Debug_Warning (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Write a warning message to the installation log (not shown to the user).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Warning "File config.cfg did not exist, creating one."
</pre>

=== POL_Debug_Error (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Write an error message to the installation log (not shown to the user).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Error "Error while modifying config.cfg file"
</pre>

=== POL_Debug_Fatal (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Raises a fatal error (the script is immediately aborted).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Fatal "Error while modifying config.cfg file"
</pre>

'''Previous:''' [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]

[[Category:Scripting]]

Scripting - Chapter 11: List of Functions

2020-01-21T11:07:01Z

Dadu042: /* POL_RequiredVersion (4.0.15+) */

== Legend of colour for the arguments ==
* ''Colours not currently showing up right now. They will be added soon.''

Red: Required argument.

Orange : Required argument if further arguments are present, but can be left empty ("").

Blue : Optional argument, but in some cases required.

Green : Optional argument.

== Start and stop the graphical interface ==

=== POL_GetSetupImages (4.0+) ===

'''Purpose:'''

Download custom images that will be displayed during the installation wizard.

'''Arguments:'''

# Optional --force option to override any cached images
# URL of top image.
# URL of left image.
# Name of the cache directory where to store the images (usually $TITLE).

'''Description:'''

To liven up installations, two images are currently displayed by PlayOnLinux/PlayOnMac installers:

- a 150 by 356 pixels image at the left of "presentation" introductory screen

- a 64 by 64 pixels "icon" image at the upper right corner for the remaining of the installation

Default images are normally displayed, but they can be replaced by custom images of the same resolution using this statement. Both JPEG and PNG file formats are supported, JPEG being the preferred format.

Downloaded images will be stored in a cache to avoid repeated downloads. There's no cache invalidation mechanism, so in case incorrect images may have been put into users' cache, you can:

- either preceed arguments with --force to override any cache content;

- change the name of the cache directory to a different value. Make sure you still use something unique to the script though, say "$TITLE_201510120640", etc.

'''Prerequisite:'''

This statement must be used before '''POL_SetupWindow_Init'''.

'''Example:'''
<pre class="playonlinux code">
POL_GetSetupImages "http://files.playonlinux.com/resources/setups/AC2/top.jpg" "http://files.playonlinux.com/resources/setups/AC2/left.jpg" "$TITLE"
</pre>

=== POL_SetupWindow_Init (4.0+) ===

'''Purpose:'''

Opens the installation wizard window.

'''Arguments:'''

None

'''Description:'''

Open the UI window that will be used by the PlayOnLinux installation wizard script.

While few initialization statements must be run before '''POL_SetupWindow_Init''', most statements expect the installation window to be opened to either display some progression feedback, or report error cases; So this statement should be used very near the beginning of scripts.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_Init
</pre>

=== POL_SetupWindow_Close (4.0+) ===

'''Purpose:'''

Closes the installation wizard window.

'''Arguments:'''

None

'''Description:'''

Close the UI window; Well behaved installation scripts should use this statement before exiting. Since most statements expect the installation window to be opened to either display some progression feedback, so it is recommended to use '''POL_SetupWindow_Close''' as late as possible in the scripts.

If some error has been detected during the execution of the script by the embedded debugger (see "Debugging Commands" below), at this point PlayOnLinux/PlayOnMac will offer the user to send an automated bug report, containing a log of the script execution, and any comments (s)he wants to add about the issue.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_Close
</pre>

== PlayOnLinux graphical interface ==

{{Warning|All the functions below need the command POL_SetupWindow_Init to be executed beforehand.}}

=== POL_SetupWindow_presentation (4.0+) ===

'''Purpose:'''

Display a standard introductory screen for the install script and the software it's about to install.

'''Arguments:'''

# Software name (often $TITLE).
# Software publisher.
# Site of the publisher.
# Script author.
# Prefix name (usually $PREFIX).

'''Description:'''

This statement will display the name of the software the install script is about to install, along with basic informations about it, and the name of the script author, in a standardized format. If some "left image" has been setup with '''POL_GetSetupImages''', it will be displayed at the same time.

This can be used right before the installation starts, so the user has one more chance to check what is about to be installed, and eventually cancel the installation.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_presentation "$TITLE" "Mozilla" "http://www.mozilla.com" "SuperPlumus and NSLW" "$PREFIX"
</pre>

=== POL_SetupWindow_free_presentation (4.0+) ===

'''Purpuse:'''

Display a free format introductory screen.

'''Arguments:'''

# Software name (often $TITLE).
# Message.

'''Description:'''

In case the standardized format of '''POL_SetupWindow_presentation''' introductory screen does not fit the needs of the install script, this statement let you use any text you want instead. If some "left image" has been defined with '''POL_GetSetupImages''' statement, it will be displayed at the same time.

This can be used right before the installation starts, so the user has one more chance to check what is about to be installed, and eventually cancel the installation.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_free_presentation "$TITLE" "Welcome to Mozilla Firefox installation wizard."
</pre>

=== POL_SetupWindow_message (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).

'''Description:'''

Display a message.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_message "Hello world!" "$TITLE"
</pre>

=== check_one - POL_SetupWindow_missing (4.0-4.1.1) ===

'''Arguments for check_one:'''

# Program that must be present.
# Package that contains this program.

'''Description:'''

Check the availability of one or more programs required by the script.

Call check_one as many times as needed (once per program), then use POL_SetupWindow_missing.

'''Example:'''
<pre class="playonlinux code">
check_one "p7zip" "p7zip"
POL_SetupWindow_missing
</pre>

=== POL_SetupWindow_file (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# File to display.

'''Description:'''

Display the content of a file.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_file "Changelog" "$TITLE" "$POL_System_TmpDir/changelog.txt"
</pre>

=== POL_SetupWindow_licence (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# File to display.

'''Description:'''

Similar to the command POL_SetupWindow_file, but adds an "I agree" checkbox.

Useful for displaying licenses.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_licence "Licence:" "$TITLE" "$POL_System_TmpDir/licence.txt"
</pre>

=== POL_SetupWindow_pulsebar - POL_SetupWindow_pulse - POL_SetupWindow_set_text (4.0+) ===

'''Arguments for POL_SetupWindow_pulsebar:'''

# Message.
# Title (often $TITLE).

'''Arguments for POL_SetupWindow_pulse:'''

# Percentage.

'''Arguments for POL_SetupWindow_set_text:'''

# Current text.

'''Description:'''

Display a progression bar, from 0 to 100%.

POL_SetupWindow_pulsebar display the progression bar.

POL_SetupWindow_pulse changes the progression value, from 0 to 100%.

POL_SetupWindow_set_text modifies the current message (different from POL_SetupWindow_pulsebar message).

Useful for displaying licenses.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_pulsebar "Installing patchs 1 to 5." "$TITLE"

POL_SetupWindow_set_text "Installation of patch 1 in progress"
POL_Wine "$POL_System_TmpDir/patch1.exe"
POL_SetupWindow_pulse "20" # meaning 20%

POL_SetupWindow_set_text "Installation of patch 2 in progress"
POL_Wine "$POL_System_TmpDir/patch2.exe"
POL_SetupWindow_pulse "40"

POL_SetupWindow_set_text "Installation of patch 3 in progress"
POL_Wine "$POL_System_TmpDir/patch3.exe"
POL_SetupWindow_pulse "60"

POL_SetupWindow_set_text "Installation of patch 4 in progress"
POL_Wine "$POL_System_TmpDir/patch4.exe"
POL_SetupWindow_pulse "80"

POL_SetupWindow_set_text "Installation of patch 5 in progress"
POL_Wine "$POL_System_TmpDir/patch5.exe"
POL_SetupWindow_pulse "100"
</pre>

=== POL_SetupWindow_wait (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).

'''Description:'''

Display an indeterminate progress bar.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_wait "Please wait" "$TITLE"
</pre>

=== POL_SetupWindow_textbox (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Default value.

'''Description:'''

Display some window asking the user to type in something.

'''Return:'''

What the user typed is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_textbox "Votre pseudo :" "$TITLE"
</pre>

=== POL_SetupWindow_textbox_multiline (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Default value.

'''Description:'''

Similar to POL_SetupWindow_textbox, but typing happens on several lines.

'''Return:'''

What the user typed is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_textbox_multiline "Enter a description for the program" "$TITLE"
</pre>

=== POL_SetupWindow_browse (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Default value.

'''Description:'''

Ask the user to select a file.

'''Return:'''

The path of the file selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_browse "Please select the program." "$TITLE"
</pre>

=== POL_SetupWindow_question (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).

'''Description:'''

Ask a question to the user (that can be answered by Yes or No).

'''Return:'''

Answer is returned in the $APP_ANSWER variable (TRUE for Yes, FALSE for No).

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_question "Message" "Title"
</pre>

=== POL_SetupWindow_menu (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).

'''Description:'''

Display a menu to the user, asking him to select one entry among the choices provided.

'''Return:'''

The choice selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_menu "What's your favorite color?" "$TITLE" "Red~Green~Blue" "~"
</pre>

=== POL_SetupWindow_menu_num (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).

'''Description:'''

Similar to the command POL_SetupWindow_menu except that instead of returning the name of the selected choice (Red for example), it returns the position of the selected choice in the list, as a number (0 being the 1st choice).

'''Return:'''

The choice selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_menu_num "What's your favorite color?" "$TITLE" "Red~Green~Blue" "~"
</pre>

$APP_ANSWER will contain 0 if the user selected Red, 1 for Green, or 2 for Blue.

=== POL_SetupWindow_menu_list (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).
# Default choice.

'''Description:'''

Similar to the command POL_SetupWindow_menu but displays a drop-down list.

'''Return:'''

The choice selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_menu_list "What's your favorite color?" "$TITLE" "Red~Green~Blue" "~"
</pre>

=== POL_SetupWindow_checkbox_list (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).

'''Description:'''

Show a list of options and checkboxen to the user, asking him to select the option(s) he wants.

'''Return:'''

The option(s) selected by the user are returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_checkbox_list "What are your favorite colors?" "$TITLE" "Red~Green~Blue" "~"
if [ "$(echo $APP_ANSWER | grep -o "Red")" != "" ]
then
# Red was selected
fi
if [ "$(echo $APP_ANSWER | grep -o "Green")" != "" ]
then
# Green was selected
fi
if [ "$(echo $APP_ANSWER | grep -o "Blue")" != "" ]
then
# Blue was selected
fi
</pre>

=== POL_SetupWindow_cdrom (4.0+) ===

'''Description:'''

Ask the user to select a loaded CD/DVD.

'''Return:'''

The path to the drive selected by the user is returned in the $CDROM variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_cdrom
</pre>

=== POL_SetupWindow_check_cdrom (4.0+) ===

'''Arguments:'''

# 1, 2, etc. List of files that should be present.

'''Description:'''

Check, in order, if the files specified exist on the CD/DVD. If one is found, $CDROM_SETUP is set to the file path, and the script continues;

Otherwise, execute POL_SetupWindow_cdrom again.

'''Return:'''

Should be used right after POL_SetupWindow_cdrom.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_check_cdrom "Data/32_icon.ico"
</pre>

=== POL_SetupWindow_InstallMethod (4.0+) ===

'''Arguments:'''

# Comma separated list of installation methods available.

'''Description:'''

Ask the user want installation method he wants, among the available choices.

'''Available installation methods:'''

'''LOCAL, CD, DVD, DOWNLOAD, STEAM, STEAM_DEMO.'''

'''Return:'''

The choice selected by the user is returned in the $INSTALL_METHOD variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_InstallMethod "LOCAL,CD,STEAM"
</pre>

== POL_RequiredVersion (4.0.15+) ==

'''Arguments:'''

# Minimum version.

'''Description:'''

Checks that the user is running a version of PlayOnLinux/PlayOnMac that is at least equal to the version provided as argument; If not, stops the script execution while alerting the user that (s)he needs to upgrade to run the script.

This is very useful to put near the top of scripts that use statements of features that only appeared in a relatively version of PlayOnLinux/PlayOnMac.

Remarks:
* The sweet spot to place POL_RequiredVersion is between POL_SetupWindow_Init (the interface must be ready to display a user warning) and POL_Debug_Init (so that the usage of an old version of PlayOnLinux/PlayOnMac does not trigger all the embedded debugger/bug reporting workflow);
* While POL_RequiredVersion can display warnings on its own, this function only appeared in PlayOnLinux 4.0.15, and PlayOnLinux 4.0.14 is still the default in some distributions (2013) ; So for the time being, it is recommended to complement it with a check that the statement itself exists, as shown in the example below.
'''Prerequisite:'''

The command POL_SetupWindow_Init must have been used beforehand.

'''Example:'''
POL_RequiredVersion 4.0.18 || POL_Debug_Fatal "$TITLE won't work with $APPLICATION_TITLE $VERSION\nPlease update"

== POL_AdvisedVersion (4.0.15+) ==

'''Arguments:'''

# Minimum version.

'''Description:'''

Very similar to POL_RequiredVersion (see POL_RequiredVersion), but do not stop the script execution after having alerted the user.

The script should be able to run on older versions of PlayOnLinux/PlayOnMac, even if in some kind of degraded mode.

All remarks about POL_RequiredVersion apply; If you use both in the same script, put POL_RequiredVersion first.

'''Prerequisite:'''

The command POL_SetupWindow_Init must have been used beforehand.

'''Example:'''
NEEDED=4.0.18
POL_AdvisedVersion $NEEDED || POL_Debug_Message "$TITLE works better with $APPLICATION_TITLE $NEEDED\nPlease update"

== POL_Shortcut (4.0+) ==

'''Arguments:'''

# Executable filename.
# Launcher name (often $TITLE).
# Optional name of the icon to download from PlayOnLinux website.
# Optional executable arguments.
# Optional list of categories the program belongs to (4.2+)

'''Description:'''

Create a launcher in PlayOnLinux. If some path is specified before the executable filename, it will be interpreted relative to the "drive_c" subdirectory of the prefix. Note that Wine, like Windows, translates the name of the "Program Files" directory according to the user locale, so you should always use the special variable $PROGRAMFILES instead of its name in your own locale.

If no path is specified (recommended), the executable filename is looked up using a case insensitive [http://linux.die.net/man/7/glob glob] search, so you can use wildcards as needed; On the other hand if the program filename contains special characters they may require quoting to avoid being interpreted as wildcards.

PlayOnLinux can also create entries in system menus, but only if category(ies) is(are) provided. The list of valid categories can be found on freedesktop.org site (see [http://standards.freedesktop.org/menu-spec/latest/apa.html main] and [http://standards.freedesktop.org/menu-spec/latest/apas02.html additional] categories). More than one category can be provided, the list separated (and optionally terminated) by semicolons (;).

'''Prerequisite:'''

The command POL_Wine_SelectPrefix must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Shortcut "firefox.exe" "$TITLE"
</pre>

== POL_Shortcut_InsertBeforeWine (4.0+) ==

'''Arguments:'''

# Launcher name (often $TITLE).
# Command to add.

'''Description:'''

Allows to run an extra command each time a program will be about to start.

'''Example:'''
<pre class="playonlinux code">
POL_Shortcut_InsertBeforeWine "Jedi Knight II" "export __GL_ExtensionStringVersion=17700"
</pre>

== POL_Shortcut_QuietDebug (4.0.17+) ==
'''Arguments:'''

# Launcher name (often $TITLE).

'''Description:'''

Avoid displaying "This program may have crashed" dialog box when the program launched by a shortcut exits with a non-zero exitcode.

This is a bandaid for programs exiting with meaningless exitcodes, as it sometimes happens since it's of little consequence under Windows.

'''Example:'''
POL_Shortcut_QuietDebug "Sam and Max S2E1: Ice Station Santa"

== POL_Shortcut_Document (4.0.15+) ==
'''Arguments:'''
# Launcher name (often $TITLE).
# Path to some documentation file

'''Description:'''

Link some documentation file to an existing PlayOnLinux shortcut; The documentation will be available using Right-click on shortcut > Read the manual.

Document file is looked up using the same rules POL_Shortcut uses to find executables.

'''Prerequisite:'''

The command POL_Wine_SelectPrefix must have been used beforehand.

'''Example:'''
POL_Shortcut_Document "$TITLE" "README.txt"

== POL_Browser (4.0+) ==

'''Arguments:'''

# URL to open.

'''Description:'''

Opens a URL in the user's default Internet browser.

'''Example:'''
<pre class="playonlinux code">
POL_Browser "http://www.playonlinux.com"
</pre>

== POL_Download (4.0+) ==

'''Arguments:'''

# URL to download.
# (Optional) Expected MD5 digest of the downloaded file

'''Description:'''

Download a URL to a local file. The file will be created in the current directory, named after the last component of the URL.

If an expected MD5 digest is provided (recommended), the downloaded file will then be run thru the MD5 digest algorithm, and the result compared to the expected value. If they differ, it will be assumed the download broke and the user will be asked if (s)he wants the download to be reattempted.

This is a very effective way to ensure that the downloaded content is the expected one, however some URLs lead to resources that are very often updated, in which case providing an up-to-date MD5 digest can be impractical.

'''Example:'''
POL_Download "http://repository.playonlinux.com/divers/QuickTime.qtp" "417f9bf5ec52d3bfa5826b4905658dac"

== POL_Download_Resource (4.0+) ==

'''Arguments:'''

# URL to download.
# Expected MD5 digest of the downloaded file
# (Optional) Subfolder to download the file to

'''Description:'''

Download a URL to the local file cache, if not already present. The file will be created in $POL_USER_ROOT/ressources directory (unless some subfolder is provided, in which case it will be created under $POL_USER_ROOT/ressources/<subfolder>, creating the subfolder if needed), and named after the last component of the URL.

Contrary to POL_Download, '''the MD5 digest is mandatory''' for POL_Download_Resource, as it will not only be used to validate the download (see POL_Download), but is also used, if some file already exists in the cache, to check that it has the expected content.

Beware that files stored in the cache will potentially stay there for a very long time, since PlayOnLinux never does any kind of cache cleanup, based on time or size; So you should only use POL_Download_Resource for files that are likely to be reused, possibly because they're necessary for several install scripts.

'''Example:'''
POL_Download_Resource "http://downloads.sourceforge.net/ffdshow-tryout/ffdshow_beta7_rev3154_20091209.exe" "c3f75f29521f749f9c9fc5489544cb04"

== POL_System_TmpCreate (4.0+) ==

'''Arguments:'''

# Name of the temporary directory (often $PREFIX).

'''Description:'''

Creates the temporary directory dedicated to the script.

'''Return:'''

$POL_System_TmpDir will contain the path of the created temporary directory.

'''Example:'''
<pre class="playonlinux code">
POL_System_TmpCreate "$PREFIX"
</pre>

== POL_System_TmpDelete (4.0+) ==

'''Description:'''

Removes the script's temporary directory.

'''Example:'''
<pre class="playonlinux code">
POL_System_TmpDelete
</pre>

== POL_System_SetArch (4.0+) ==

'''Arguments:'''

# Supported architectures (see below).

'''Description:'''

Set the (Wine) architectures supported by the script.

'''Allowed values:'''

* '''auto''': Use the version of Wine matching the system architecture (Wine x86 on x86 and Wine x64 on amd64).

* '''x86''': Use the x86 version of Wine for installation (useful if the program doesn't work well with the x64 version).

* '''amd64''': Use the x64 version of Wine for installation (if the system architecture is x86, the script stops).

'''Example:'''
<pre class="playonlinux code">
POL_System_SetArch "auto"
</pre>

'''Prerequisite:'''

The command POL_Wine_PrefixCreate must be located after.

== POL_Call (4.0+) ==

'''Arguments:'''

# Function name.
# 2, 3, etc.: Function arguments, if necessary (very few functions take arguments).

'''Description:'''

Download and execute a script from the Functions category (the list of functions and their basic information for each can be found here: [[Components and Functions|Components and Functions]]).

'''Prerequisite:'''

For most functions, the commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Call POL_Install_vcrun6
</pre>

== Wine-related functions ==

=== POL_Wine_SelectPrefix (4.0+) ===

'''Arguments:'''

# Prefix name (often $PREFIX).

'''Description:'''

Select the prefix that will be used by Wine (mandatory, even if the prefix hasn't been created yet).

'''Example:'''
<pre class="playonlinux code">
POL_Wine_SelectPrefix "$PREFIX"
</pre>

=== POL_Wine_PrefixExists (4.0+) ===

'''Arguments:'''

# Prefix name (often $PREFIX).

'''Description:'''

Check if a prefix exists (useful for game extensions and patches).

'''Return:'''

The function displays True if the prefix exists, and False otherwise.

'''Example:'''
<pre class="playonlinux code">
if [ "$(POL_Wine_PrefixExists "$PREFIX")" = "False" ]
then
# The préfixe doesn't exist
fi
</pre>

=== POL_Wine_PrefixCreate (4.0+) ===

'''Arguments:'''

# Wine version.

'''Description:'''

Creates or updates a prefix. It is possible to use a version of Wine different from the one installed system wide on user's computer, by specifying this version as first argument.

'''Prerequisite:'''

The command POL_Wine_SelectPrefix must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_PrefixCreate "1.3.4"
</pre>

=== POL_Wine (4.0+) ===
'''Arguments:'''
* Program pathname.
* 2, 3, etc.: program arguments, if any.
'''Description:'''

This command will run the given program; It works exactly like the "wine" command, but uses the Wine versions management and logging facilities of PlayOnLinux.

While most programs started that way will behave synchronously (in other words, will block the script until they're finished), some don't and the POL_Command will need to be followed by a POL_Wine_WaitExit command to prevent the rest of the script from being executed before the program has finished.

See POL_Wine_WaitBefore and POL_Wine_WaitExit.

Note: Using '''start /unix''' before the program name can fix issues of access and installation paths with several CD/DVD. However, the use of start /unix makes POL_Wine asynchronous, and since asynchronous programs are not automatically killed if the script is aborted from PlayOnLinux side, it should only be used when necessary.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

=== POL_SetupWindow_VMS (4.0+) ===
'''Arguments:'''

# Minimum amount of onboard video memory required, in MB.

'''Description:'''

Ask the user how much (dedicated) RAM his videocard has, since it is actually very difficult to determine this value in a portable way.

If the value is lower than the minimum argument value, the user is warned that the program being installed is likely not to work correctly. In all cases, the script goes on and the value is written in the Wine registry.

The user reply is cached so that it doesn't need to be asked again during the next installations. In case of mistake, or if the amount of video memory changes, the cached value can be erased by opening the PlayOnLinux console, and typing "POL_Config_Delete VMS" (for a lack of GUI support at the moment).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_VMS "128"
</pre>

=== Set_OS (4.0+) ===

'''Arguments:'''

# Windows version to emulate.
# Service pack.

'''Description:'''

Modifies the Windows version emulated by Wine.

'''Default value:''' winxp (Windows XP).

'''Allowed values:'''

'''Windows versions''': win7, vista, win2003, winxp, win2k, winnt, winme, nt40, win98, win95, win31.

'''Services packs''': sp1, sp2, sp3.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_OS "winxp"
</pre>

=== Set_Managed (4.0+) ===

'''Arguments:'''

# On/Off.

'''Description:'''

Set if the window manager will be allowed to manage Wine windows.

'''Default value''': On.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_Managed "Off"
</pre>

=== Set_SoundDriver (4.0+) ===

'''Arguments:'''

# alsa/oss/esd.

'''Description:'''

Set the audio driver Wine will use.

{{Info|This command does nothing under PlayOnMac, since it is useless in that environment.}}

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_SoundDriver "alsa"
</pre>

=== POL_Wine_Direct3D (4.0+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\Direct3D].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_Direct3D "UseGLSL" "disabled"
</pre>

=== POL_Wine_X11Drv (4.0.14+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\X11 Driver].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_X11Drv "DXGrab" "Y"
</pre>

=== POL_Wine_DirectSound (4.0+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\DirectSound].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_DirectSound "HardwareAcceleration" "Emulation"
</pre>

=== POL_Wine_DirectInput (4.0+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\DirectInput].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_DirectInput "MouseWarpOverride" "force"
</pre>

=== POL_Wine_GetRegValue (4.0+) ===

'''Arguments:'''

# Setting to read (the key is not required).

'''Description:'''

This function returns the value of a setting from the registry.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Return:'''

The function displays the value of the specified setting.

'''Example:'''
<pre class="playonlinux code">
VALUE="$(POL_Wine_GetRegValue "MouseWarpOverride")"
</pre>

=== Set_Desktop (4.0+) ===

'''Arguments:'''

# On/Off.
# Virtual desktop width (if it is enabled).
# Virtual desktop height (if it is enabled).

'''Description:'''

Sets the Wine virtual desktop settings.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_Desktop "On" "1024" "768"
</pre>

=== Set_WineWindowTitle (4.0+) ===

'''Arguments:'''

# Virtual desktop name.

'''Description:'''

Set the title of the virtual desktop window (purely aesthetic effect).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_WineWindowTitle "$TITLE"
</pre>

=== POL_Wine_InstallFonts (4.0+) ===

'''Description:'''

This command installs standard (but not installed by default) fonts into the prefix.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_InstallFonts
</pre>

=== POL_Wine_SetVideoDriver (4.0+) ===

'''Description:'''

Set correct video driver (when Wine fails to do it properly).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_SetVideoDriver
</pre>

=== POL_Wine_OverrideDLL (4.0+) ===

'''Arguments:'''

# Mode of override.
# 3, 4, etc.: DLL names (without .dll suffix).

'''Description:'''

Set the override mode for one or more dynamic library(ies).

'''Allowed override modes:'''

"native", "builtin", "native,builtin", "builtin,native", or empty value ("") to disable the DLL(s).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_OverrideDLL "native" "msvcrt"
POL_Wine_OverrideDLL "" "msvcrt" # To disable the DLL
</pre>

=== POL_Wine_OverrideDLL_App (4.0+) ===

'''Arguments:'''

# Executable name.
# Mode of override.
# 3, 4, etc.: DLL names (without .dll suffix).

'''Description:'''

Set the override mode for one or more dynamic library(ies), but only for a specific program.

'''Allowed override modes:'''

"native", "builtin", "native,builtin", "builtin,native", or empty value ("") to disable the DLL(s).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_OverrideDLL_App "firefox.exe" "native" "msvcrt"
POL_Wine_OverrideDLL_App "firefox.exe" "" "msvcrt" # To disable the DLL
</pre>

=== POL_Wine_WaitBefore (4.0.15+) ===

'''Arguments:'''

# Program name.

'''Description:'''

Placed before a POL_Wine command that starts a program synchronously (ie a "blocking" POL_Wine command), it will display a standard wait message while it runs.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
POL_Wine_WaitBefore "$TITLE"

=== POL_Wine_WaitExit (4.0+) ===

'''Arguments:'''

# Program name.

'''Description:'''

Placed after a POL_Wine command that starts a program asynchronously (ie a "non-blocking" POL_Wine command), it will display a standard wait message while it runs and wait for its completion.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_WaitExit "$TITLE"
</pre>

=== POL_Wine_reboot (4.0+) ===

'''Description:'''

Emulate a Windows reboot.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_reboot
</pre>

== Debugging commands ==

=== POL_Debug_Init (4.0+) ===

'''Description:'''

Start debugging system.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Init
</pre>

=== POL_Debug_Message (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Write a message to the installation log (not shown to the user).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Message "Modifying config.cfg file."
</pre>

=== POL_Debug_Warning (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Write a warning message to the installation log (not shown to the user).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Warning "File config.cfg did not exist, creating one."
</pre>

=== POL_Debug_Error (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Write an error message to the installation log (not shown to the user).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Error "Error while modifying config.cfg file"
</pre>

=== POL_Debug_Fatal (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Raises a fatal error (the script is immediately aborted).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Fatal "Error while modifying config.cfg file"
</pre>

'''Previous:''' [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]

[[Category:Scripting]]

Troubleshooting Common Problems

2019-12-24T14:29:23Z

Dadu042: /* FreeType font library */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22 (you may need to read in this page: 'About a script stored in 'Supported software', how to install it with a newer Wine version ?').

Troubleshooting Common Problems

2019-12-24T08:37:55Z

Dadu042: /* 'PresentationFramework, Version=4.0.0.0 (dotnet40) */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0, ...' (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22

Troubleshooting Common Problems

2019-12-24T08:36:43Z

Dadu042: /* Missing files */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

=== 'PresentationFramework, Version=4.0.0.0 (dotnet40) ===

{{Console|The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. assembly:PresentationFramework, Version=4.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35 type:<unknown type> member:<none>}}

This mean that Microsoft Dotnet 4.0 is missing and required.

Fix:
* From POL/POM Config window, do install 'dotnet40'.

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22

Troubleshooting Common Problems

2019-12-22T09:47:53Z

Dadu042: /* libjpeg.so.62 (libjpeg) */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22

Troubleshooting Common Problems

2019-12-22T09:47:40Z

Dadu042: /* Missing files */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

=== libpulse.so (libpulse) ===

{{Console|:err:module:load_so_dll failed to load .so lib "/home/username/.PlayOnLinux/wine/linux-x86/4.20/bin/../lib/wine/winepulse.drv.so": libpulse.so.0: cannot open shared object file: No such file or directoryALSA lib conf.c:3357:(snd_config_hooks_call) Cannot open shared library libasound_module_conf_pulse.so}}

Occured with POL 4.3.4 and Wine 4.20

Workaround:
* Ubuntu: apt-get install libpulse0 libpulse0:i386
* Archlinux: lib32-libpulse

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22

FAQ

2019-12-07T15:29:02Z

Dadu042: /* Is there a list of solutions for common problems? */

== PlayOnLinux and PlayOnMac ==

=== How do I find out if a game will run on PlayOnLinux/PlayOnMac? ===
Excellent question. Since POL/POM is a front-end for [https://winehq.org/ Wine], the first place to check, besides our [https://www.playonlinux.com/en/supported_apps.html Supported Software section], is WineHQ's [https://appdb.winehq.org/ AppDB]. There are many, many entries for a lot of different types of Windows applications, all submitted to the Wine community by users like yourself. If it is even remotely popular, and people have attempted to use it through Wine, it will likely be listed there.

=== How do I move PlayOnLinux virtual drives to another disk (with more free space)? ===
Read the advanced topic here:
* [[How to move PlayOnLinux virtual drives to another disk|How to move PlayOnLinux virtual drives to another disk]]

=== Why isn't PlayOnLinux downloading Photoshop (or whatever retail application) for me? ===
PlayOnLinux/PlayOnMac does not actually provide the applications. It provides the means to install those applications. You actually have to own, say, Photoshop CS6, in order to install Photoshop CS6. POL/POM does not provide any sort of pirated software in any way. This also applies to support regarding pirated software and cracks.

=== Do I have to install Wine to use PlayOnLinux? ===
Yes. You will want to have a 32-bit version of Wine installed on your system, along with the dependencies it suggests. POL will want to see it, and will use it's dependencies concurrently with POL's WineBuilds. Without getting too technical, POL will need it, so it is best to install it.

=== Will PlayOnLinux interfere with my current Wine or winetricks installations? ===
No. PlayOnLinux/PlayOnMac keeps all of it's resources, WineBuilds, and virtual drives contained in one folder, and will never interfere with your other WINEPREFIX created by vanilla Wine and winetricks (unless, of course, you start using winetricks for POL virtual drives or try to use vanilla Wine on a POL virtual drive, or something like that.).

=== The application I am trying to install needs administrator rights to function correctly ===
Wine does not implement privileges, so such message does not make any sense under Wine. Either it cannot be made to work, or emulated Windows version must be changed to some version that does not implement privileges (Win9x for instance) so that the installer changes its expectations.

=== How do I install Steam, and Steam only? ===

If you want to only install Steam for Windows into a Virtual Drive, you will need to do a manual installation. It is very simple:

# Open PlayOnLinux, download and install the WineBuild that you want from [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions].
# Open the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window], click New, and create a new Virtual Drive, naming it what you want, and selecting the WineBuild that you want to use when prompted.
# In the Configuration Window, select your new Virtual Drive, open the Install Components tab, and double-click '''Steam''' in that list. Steam will be installed into the Virtual Drive highlighted on the left side.
# On the General Tab of the Configuration Window, select '''Make a new shortcut from this virtual drive''', and select the Steam executable when shown in the list. This will create a shortcut in the main POL window.

{{Info|This is a manual install, and does not guarantee that the game that you install through Steam will work. If it does not work, you should check to see if there is already an installer for that game in our repository, and if not, you will need to check the [https://appdb.winehq.org AppDB at WineHQ] for your game to see if it needs any extra components or settings. As always, for manual installs, feel free to post up for help in the appropriate section of [https://www.playonlinux.com/en/forum-24-Manual_installations.html the forums].''}}

=== How can I use the CSMT patch with POL? ===

Up until recently, you would have needed to [http://wiki.playonlinux.com/index.php/How_to_Request_a_Patched_Version_of_Wine request a patched WineBuild]. Now, with the help of the devs at ''[http://www.wine-staging.com/ wine-staging]'', we have WineBuilds with the patchset from ''wine-staging'', which happen to contain the CSMT patch (for now; when patches from ''wine-staging'' get mainlined, they are dropped from the ''-staging'' versions of Wine, as they are now a default feature.).

Simply go to [http://wiki.playonlinux.com/index.php/Managing_Wine_Versions Manage Wine Versions] and download the WineBuild that you want, with the ''-staging'' suffix, and then use the '''Wine tab''' in the [http://wiki.playonlinux.com/index.php/The_Configuration_Window Configuration Window] to access '''Wine Configuration'''. You will find a checkbox to enable CSMT in the '''Staging tab'''.

== Website ==

=== How can I post a bug report? ===
* [[How to Post a Bug Report|How to Post a Bug Report]]

=== How can I contribute an installer for an application? ===
First, you would want to read our scripters tutorial here: [[Scripting - Chapter 1: Getting to know Bash|Scripting tutorial]]

Then once you have written and tested a script, and it is working, follow the instructions here to submit it to us: [[How to Contribute a Script|How to Contribute a Script]]

=== How do I request a version of Wine with a certain patch? ===
* [[How to Request a Patched Version of Wine|How to Request a Patched Version of Wine]]

=== Where does PlayOnLinux store it's virtual drives and cache? ===
All virtual drives are created and store here:

<code>~/.PlayOnLinux/wineprefix/</code>

The other files for Wine versions, resources, and components cache are located in '''~/.PlayOnLinux/'''

=== How do I run Wine/POL as root or sudo? ===
You don't. You should never, ever run Wine or POL as root or using sudo, or any other privilege escalation mechanism.

* [http://wiki.winehq.org/FAQ#head-96bebfa287b4288974de0df23351f278b0d41014 WineHQ FAQ regarding root/sudo use]

=== Is there a list of solutions for common problems? ===
Somewhat, as issues can vary a '''LOT''' between users, systems, Wine versions, graphics cards, etc.. As a start, you should check the following locations:

# [[Troubleshooting Common Problems|Troubleshooting Common Problems]]
# [https://appdb.winehq.org/ appdb.winehq.org]
# Searching the POL/POM forums (see [[How to Post in the Forums|How to Post in the Forums]])
# Search engines for the web, of course.

=== My post was closed with a semi-automated reply? What did I break? ===
Nothing. What that means is that your post is lacking information that we need to troubleshoot, or possibly violates our terms of service.

Check the following links to make sure that you didn't accidentally violate ToS, and that you are posting the information required:

* https://www.playonlinux.com/en/terms.html

* [[How to Post in the Forums|How to Post in the Forums]]

== I want to contribute ==

=== Bash; I really want to know more ===
* http://www.gnu.org/software/bash/

* http://linuxconfig.org/bash-scripting-tutorial

* http://www.tldp.org/LDP/Bash-Beginners-Guide/html/

* http://www.tldp.org/LDP/abs/html/

=== Python; I really want to know more ===
* https://www.python.org/

* https://docs.python.org/2/tutorial/

* http://www.learnpython.org/

Troubleshooting Common Problems

2019-12-05T09:04:12Z

Dadu042: /* What causes this error? */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. 
If the server (hosting the file to download) does updates or changes or remove the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22

How to Read Debug Logs

2019-12-02T21:41:30Z

Dadu042: /* Folders location */

== Get the debug log (from POL v4) ==
To access the debug log of a POL compatible software, in the main GUI click on the name of the software, then on the left side click the 'Debug' button.

On the right side appears the debug of the last uses. You may copy/paste the latest one to show it to someone else.

== Debug mode ==

=== Folders location ===
There is two folders where you can find POL/POM log files:
* /home/you/.PlayOnLinux/logs/game_name/ is the place where is store the '''installation log file''' when the game (or any software) is installed. This is the file to look at if the installation failed.
* /home/you/PlayOnLinux's virtual drives/game_name/ is the place where is stored the '''log file of the game/software when launched/running'''. Note: you can delete this file, it will be recreated automatically each time you run (or try to) the software.

=== Debug flags ===
It is possible to hide all Wine errors: "Debug Flags: -all". This avoid the size of the log file to increase, and (sometimes) avoid some slowness for the storage device.

Examples:
* "fixme-all"
* "-all,fixme-all"
* "-d3d"

See also: [https://wiki.winehq.org/Debug_Channels Debug flags listed on the Wiki of winehq.org].

== Read the debug log ==

=== Error related to Wine ('wine: Unhandled page fault on read access ...') ===
Example:
{{Console|
wine: Unhandled page fault on read access to 0x00000008 at address 0x43adae (thread 0009), starting debugger...

Unhandled exception: page fault on read access to 0x00000008 in 32-bit code (0x0043adae).

Register dump:

CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b

EIP:0043adae ESP:0032fd40 EBP:00b90004 EFLAGS:00210202( R- -- I - - - )

EAX:00000032 EBX:00000000 ECX:00000000 EDX:0000fffe

ESI:00a8df82 EDI:00a8df9e

Stack dump:

0x0032fd40: 00439cf4 00a8df9e 00b9cccc 00000000

0x0032fd50: 00439bb4 0032fd88 00abceca 00000102

0x0032fd60: 0000013c 00000020 0043778c 00437848

0x0032fd70: 00000000 00000001 10042134 10042130

0x0032fd80: 00000001 0032fd90 00000006 00416611

0x0032fd90: 004452d6 00000000 00000001 00000001

Backtrace:

...
}}

For this kind of error log, the issue (it's a internal crash) is related to Wine not to POL.

Here are the best steps to follow:
# Try to use a newer Wine version inside POL (try up to the latest stable available in POL).
# If the issue occurs when installing the software you want, you may try to use a newer Wine version but this need some manual operations: copy the script (if from our website, find it into 'supported software') into a '.pol' (text) file. Edit it with a [https://en.wikipedia.org/wiki/Text_editor text editor] software in order to change the Wine version, save it. From POL, do load the script as a file (Menu 'Tools' -> 'Run a local script').
# After the tests above, you may search for help at https://winehq.org Note: the Playonlinux log will '''not be accepted''' there. You will have to reproduce the issue with Wine only (with a recent Wine version), in order to get a clean log.

=== Error related to Microsoft Dotnet ===

The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, ...' or one of its dependencies.

This error message in the log mean that installation of Microsoft DotNet 4.0 is required.

=== X3DAudio ===
{{Console|
002c:err:module:load_builtin_dll failed to load .so lib for builtin L"X3DAudio1_7.dll": libFAudio.so.0:
}}

Should (POL v4, 2019) be fixable by installing: [https://www.playonlinux.com/fr/app-635-POL_Install_xact.html POL_Install_xact]

=== Missing files ===

File(s) missing in your OS:

{{Console|
DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
}}

In this example DOS is missing the file 'libpng12.so.0' in your OS (for this file, look: [[Troubleshooting Common Problems]]).

== See also ==
* [[Troubleshooting Common Problems]]

How to Read Debug Logs

2019-12-02T21:39:45Z

Dadu042: /* Folders location */

== Get the debug log (from POL v4) ==
To access the debug log of a POL compatible software, in the main GUI click on the name of the software, then on the left side click the 'Debug' button.

On the right side appears the debug of the last uses. You may copy/paste the latest one to show it to someone else.

== Debug mode ==

=== Folders location ===
There is two folders where you can find POL/POM log files:
* /home/you/.PlayOnLinux/logs/game_name/ is the place where is store the '''installation log file''' when the game (or any software) is installed.
* /home/you/PlayOnLinux's virtual drives/game_name/ is the place where is stored the '''log file of the game/software when launched/running'''. Note: you can delete this file, it will be recreated automatically.

=== Debug flags ===
It is possible to hide all Wine errors: "Debug Flags: -all". This avoid the size of the log file to increase, and (sometimes) avoid some slowness for the storage device.

Examples:
* "fixme-all"
* "-all,fixme-all"
* "-d3d"

See also: [https://wiki.winehq.org/Debug_Channels Debug flags listed on the Wiki of winehq.org].

== Read the debug log ==

=== Error related to Wine ('wine: Unhandled page fault on read access ...') ===
Example:
{{Console|
wine: Unhandled page fault on read access to 0x00000008 at address 0x43adae (thread 0009), starting debugger...

Unhandled exception: page fault on read access to 0x00000008 in 32-bit code (0x0043adae).

Register dump:

CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b

EIP:0043adae ESP:0032fd40 EBP:00b90004 EFLAGS:00210202( R- -- I - - - )

EAX:00000032 EBX:00000000 ECX:00000000 EDX:0000fffe

ESI:00a8df82 EDI:00a8df9e

Stack dump:

0x0032fd40: 00439cf4 00a8df9e 00b9cccc 00000000

0x0032fd50: 00439bb4 0032fd88 00abceca 00000102

0x0032fd60: 0000013c 00000020 0043778c 00437848

0x0032fd70: 00000000 00000001 10042134 10042130

0x0032fd80: 00000001 0032fd90 00000006 00416611

0x0032fd90: 004452d6 00000000 00000001 00000001

Backtrace:

...
}}

For this kind of error log, the issue (it's a internal crash) is related to Wine not to POL.

Here are the best steps to follow:
# Try to use a newer Wine version inside POL (try up to the latest stable available in POL).
# If the issue occurs when installing the software you want, you may try to use a newer Wine version but this need some manual operations: copy the script (if from our website, find it into 'supported software') into a '.pol' (text) file. Edit it with a [https://en.wikipedia.org/wiki/Text_editor text editor] software in order to change the Wine version, save it. From POL, do load the script as a file (Menu 'Tools' -> 'Run a local script').
# After the tests above, you may search for help at https://winehq.org Note: the Playonlinux log will '''not be accepted''' there. You will have to reproduce the issue with Wine only (with a recent Wine version), in order to get a clean log.

=== Error related to Microsoft Dotnet ===

The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, ...' or one of its dependencies.

This error message in the log mean that installation of Microsoft DotNet 4.0 is required.

=== X3DAudio ===
{{Console|
002c:err:module:load_builtin_dll failed to load .so lib for builtin L"X3DAudio1_7.dll": libFAudio.so.0:
}}

Should (POL v4, 2019) be fixable by installing: [https://www.playonlinux.com/fr/app-635-POL_Install_xact.html POL_Install_xact]

=== Missing files ===

File(s) missing in your OS:

{{Console|
DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
}}

In this example DOS is missing the file 'libpng12.so.0' in your OS (for this file, look: [[Troubleshooting Common Problems]]).

== See also ==
* [[Troubleshooting Common Problems]]

How to Read Debug Logs

2019-12-02T21:39:13Z

Dadu042: /* Folders location */

== Get the debug log (from POL v4) ==
To access the debug log of a POL compatible software, in the main GUI click on the name of the software, then on the left side click the 'Debug' button.

On the right side appears the debug of the last uses. You may copy/paste the latest one to show it to someone else.

== Debug mode ==

=== Folders location ===
There is two folders where you can find POL/POM log files:
* /home/you/.PlayOnLinux/logs/game_name/ is the place where is store the '''installation log''' when the game (or any software) is installed.
* /home/you/PlayOnLinux's virtual drives/game_name/ is the place where is stored the '''log file of the game/software when launched/running'''. Note: you can delete this file, it will be recreated automatically.

=== Debug flags ===
It is possible to hide all Wine errors: "Debug Flags: -all". This avoid the size of the log file to increase, and (sometimes) avoid some slowness for the storage device.

Examples:
* "fixme-all"
* "-all,fixme-all"
* "-d3d"

See also: [https://wiki.winehq.org/Debug_Channels Debug flags listed on the Wiki of winehq.org].

== Read the debug log ==

=== Error related to Wine ('wine: Unhandled page fault on read access ...') ===
Example:
{{Console|
wine: Unhandled page fault on read access to 0x00000008 at address 0x43adae (thread 0009), starting debugger...

Unhandled exception: page fault on read access to 0x00000008 in 32-bit code (0x0043adae).

Register dump:

CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b

EIP:0043adae ESP:0032fd40 EBP:00b90004 EFLAGS:00210202( R- -- I - - - )

EAX:00000032 EBX:00000000 ECX:00000000 EDX:0000fffe

ESI:00a8df82 EDI:00a8df9e

Stack dump:

0x0032fd40: 00439cf4 00a8df9e 00b9cccc 00000000

0x0032fd50: 00439bb4 0032fd88 00abceca 00000102

0x0032fd60: 0000013c 00000020 0043778c 00437848

0x0032fd70: 00000000 00000001 10042134 10042130

0x0032fd80: 00000001 0032fd90 00000006 00416611

0x0032fd90: 004452d6 00000000 00000001 00000001

Backtrace:

...
}}

For this kind of error log, the issue (it's a internal crash) is related to Wine not to POL.

Here are the best steps to follow:
# Try to use a newer Wine version inside POL (try up to the latest stable available in POL).
# If the issue occurs when installing the software you want, you may try to use a newer Wine version but this need some manual operations: copy the script (if from our website, find it into 'supported software') into a '.pol' (text) file. Edit it with a [https://en.wikipedia.org/wiki/Text_editor text editor] software in order to change the Wine version, save it. From POL, do load the script as a file (Menu 'Tools' -> 'Run a local script').
# After the tests above, you may search for help at https://winehq.org Note: the Playonlinux log will '''not be accepted''' there. You will have to reproduce the issue with Wine only (with a recent Wine version), in order to get a clean log.

=== Error related to Microsoft Dotnet ===

The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, ...' or one of its dependencies.

This error message in the log mean that installation of Microsoft DotNet 4.0 is required.

=== X3DAudio ===
{{Console|
002c:err:module:load_builtin_dll failed to load .so lib for builtin L"X3DAudio1_7.dll": libFAudio.so.0:
}}

Should (POL v4, 2019) be fixable by installing: [https://www.playonlinux.com/fr/app-635-POL_Install_xact.html POL_Install_xact]

=== Missing files ===

File(s) missing in your OS:

{{Console|
DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
}}

In this example DOS is missing the file 'libpng12.so.0' in your OS (for this file, look: [[Troubleshooting Common Problems]]).

== See also ==
* [[Troubleshooting Common Problems]]

Troubleshooting Common Problems

2019-11-15T08:50:11Z

Dadu042: /* libudev.so.0 (libudev) */

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. If the server hosting a certain file updates or changes the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

Udev is a device manager for the Linux kernel ([https://en.wikipedia.org/wiki/Udev Wikipedia]). 
This software is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22

Troubleshooting Common Problems

2019-11-15T08:46:26Z

Dadu042: /* Missing files */ Added for the search engine.

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. If the server hosting a certain file updates or changes the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 (libFaudio) ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 (libpng) ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 (libncurses) ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 (libudev) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 (libSM) ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 (libjpeg) ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22

Common Linux Libraries That Wine Might Need

2019-11-06T22:36:41Z

Dadu042: /* Games and softwares before 2010 */

Write me !

== Games and softwares between 1995 - 2005 ==
A lot of these games/softwares need the file MFC42.DLL ([https://en.wikipedia.org/wiki/Microsoft_Foundation_Class_Library Microsoft Foundation Class Library], it is a component of Microsoft Visual C). POL feature : [https://www.playonlinux.com/en/app-912-POL_Install_mfc42.html POL_Install_mfc42]

== Games and softwares between 2005 - 2020 ==
A lot of these games/softwares need a [https://en.wikipedia.org/wiki/.NET_Framework Microsoft DotNet framework]. The next problem is to know which version (usually: the newer the better).

== Games and softwares before 2010 ==
To make audio/music work, this piece of code may be required in the .POL installation script:

## Sound problem fix - pulseaudio related
[ "$POL_OS" = "Linux" ] && Set_SoundDriver "alsa"
[ "$POL_OS" = "Linux" ] && Set_SoundEmulDriver "Y"
## End Fix

== What components does a Windows software use ? ==
A way to know it is to submit the main .EXE file of the software to this meta-search engine : www.virustotal.com
then click the tab 'Details', then look under the line 'Imports'.

Common Linux Libraries That Wine Might Need

2019-11-06T22:35:59Z

Dadu042: /* Games and softwares before 2010 */

Write me !

== Games and softwares between 1995 - 2005 ==
A lot of these games/softwares need the file MFC42.DLL ([https://en.wikipedia.org/wiki/Microsoft_Foundation_Class_Library Microsoft Foundation Class Library], it is a component of Microsoft Visual C). POL feature : [https://www.playonlinux.com/en/app-912-POL_Install_mfc42.html POL_Install_mfc42]

== Games and softwares between 2005 - 2020 ==
A lot of these games/softwares need a [https://en.wikipedia.org/wiki/.NET_Framework Microsoft DotNet framework]. The next problem is to know which version (usually: the newer the better).

== Games and softwares before 2010 ==
To make audio/music work, this piece of code may be required in the .POL installation script:
{{Console|
## Sound problem fix - pulseaudio related
[ "$POL_OS" = "Linux" ] && Set_SoundDriver "alsa"
[ "$POL_OS" = "Linux" ] && Set_SoundEmulDriver "Y"
## End Fix
}}

== What components does a Windows software use ? ==
A way to know it is to submit the main .EXE file of the software to this meta-search engine : www.virustotal.com
then click the tab 'Details', then look under the line 'Imports'.

Common Linux Libraries That Wine Might Need

2019-11-06T22:34:34Z

Dadu042:

Write me !

== Games and softwares between 1995 - 2005 ==
A lot of these games/softwares need the file MFC42.DLL ([https://en.wikipedia.org/wiki/Microsoft_Foundation_Class_Library Microsoft Foundation Class Library], it is a component of Microsoft Visual C). POL feature : [https://www.playonlinux.com/en/app-912-POL_Install_mfc42.html POL_Install_mfc42]

== Games and softwares between 2005 - 2020 ==
A lot of these games/softwares need a [https://en.wikipedia.org/wiki/.NET_Framework Microsoft DotNet framework]. The next problem is to know which version (usually: the newer the better).

== Games and softwares before 2010 ==
To make audio/music work, this piece of code may be required in the .POL installation script:

# Sound problem fix - pulseaudio related
# [ "$POL_OS" = "Linux" ] && Set_SoundDriver "alsa"
# [ "$POL_OS" = "Linux" ] && Set_SoundEmulDriver "Y"
## End Fix

== What components does a Windows software use ? ==
A way to know it is to submit the main .EXE file of the software to this meta-search engine : www.virustotal.com
then click the tab 'Details', then look under the line 'Imports'.

Troubleshooting Common Problems

2019-11-05T05:52:52Z

Dadu042: /* Missing files */ FreeType font library

Here is a list of common errors and possible solutions. Not everything will be here, but this list will get a lot bigger as time goes on, and hopefully, with the help of the community, we can make this list very, very robust.

When trying a possible solution for an issue, please only try '''ONE''' solution at a time, and test to see if it worked.

== p11-kit: couldn't load module: ... ==

=== Debian-based variant ===
==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Mostly users of Debian, Ubuntu, Kubuntu, etc., Mint (and derivatives), 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

==== Common solutions ====

===== Install 32-bit version of p11-kit-trust.so =====

<pre class='code bash'>
sudo apt-get install p11-kit-modules:i386
</pre>

===== Create a symlink =====

(for systems before multiarch feature?)

''found at http://askubuntu.com/a/384018''

<pre class='code bash'>
sudo /usr/local/bin/getlibs -p p11-kit:i386
sudo ln -s /usr/lib32/i386-linux-gnu/pkcs11/p11-kit-trust.so /usr/lib/i386-linux-gnu/pkcs11/p11-kit-trust.so
</pre>

=== RPM-based variant ===

==== Error ====

{{Console|p11-kit: couldn't load module: /usr/lib/pkcs11/p11-kit-trust.so: /usr/lib/pkcs11/p11-kit-trust.so: cannot open shared object file: No such file or directory}}

==== Who might encounter this error? ====

Users of Fedora, 64-bit systems.

==== What causes this error? ====

The 32-bit version of ''p11-kit-trust.so'' is either not installed, or is not located in an area that Wine expected it to be.

We need a 32-bit version of the package p11-kit-trust, but as explained [https://bugzilla.redhat.com/show_bug.cgi?id=1060764 here], there is a packaging issue, requiring manual install.

==== Common solutions ====

Go on the web interface of a RPM mirror, and search for `p11-kit-trust`, for i386 architecture. ([https://rpmfind.net/linux/rpm2html/search.php?query=p11-kit-trust&submit=Search+...&system=&arch=i686 this link] does most of the job for you)

Download the package corresponding with your Fedora version, and install it with `dnf install /path/to/downloaded/file`

You may then run into similar errors, but with different files. You can find the missing packages with `dnf provides /path/to/missing/file`, then install them simply with `dnf install package-name`

== Error in FS_Check ==

=== Error ===

{{Console|The following file is located on a fuse filesystem. It might prevent wine from working}}

=== Who might encounter this error? ===

Anyone trying to run an executable file in Wine/POL that is located on an NTFS filesystem.

=== What causes this error? ===

Wine can get grumpy with how NTFS, Linux, and Wine interact with each other. This warning is simply there to alert you to this fact. Most of the time, this error can be ignored.

=== Common solutions ===

==== Move executable to a native Linux filesystem ====

Simply move the executable file in question to your native Linux filesystem, and this error will go away. It will only appear when trying to execute a file that is located on a FUSE filesystem.

== Failed to use ICMP ==

=== Error ===

{{Console|err:winediag:IcmpCreateFile Failed to use ICMP (network ping), this requires special permissions.
}}

=== Who might encounter this error? ===

Anyone trying to run an application that wants to ping out. On POSIX-compliant systems, ''ping'' needs admin rights. ''NOTE:'' '''NEVER''' run Wine or POL as root.

=== What causes this error? ===

When a program tries to send an ICMP packet running through POL/Wine, it will fail, as it needs administrative rights, and we never run POL or Wine as ''root'', do we? ;)

=== Common solutions ===

==== Switch to WineBuild ''1.7.45-staging'' or higher ====

There is a fix for this in the Wine-Staging builds found in '''Manage Wine Versions''', so that should be tried first.

==== Give rights to POL's WineBuild ====

In most instances, you will see a command to remedy this. Most of the time, it is missing the final argument, which is the particular instance of Wine that you are running. These solutions work fine for Vanilla Wine, but not POL. For POL, you have to point the particular command to POL's WineBuild for that particular virtual drive.

For instance, '''AION'''.

All of POL's WineBuilds are stored in ~/.PlayOnLinux/wine/

Within this folder, you have different sub-folders for architecture, and then Wine version. In the case of '''AION''':

{{Console|/home/username/.PlayOnLinux/wine/linux-x86/1.7.36}}

Find out which Wine version your application needs:

# Open the Configuration Window
# In the General tab, when your virtual drive is selected, look at the name of the version of Wine in use.

Now, the command you would want to run is:

'''NOTE''': ''Do NOT copy and paste these commands. They need to be modified for your particular situation.''

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine}}

or

{{Console|sudo setcap cap_net_raw+epi /home/username/.PlayOnLinux/wine/linux-x86/1.7.36/bin/wine-preloader}}

'''NOTE:''' ''I have seen both bin/wine and bin/wine-preloader shown in examples, so for posterity, I am including both.''

Essentially, the syntax for this is as follows:

{{Console|sudo setcap cap_net_raw+epi /home/'''username'''/.PlayOnLinux/wine/'''WineArchitecture'''/'''WineVersion'''/bin/wine}}

Replace:

* '''username''' with your current username

* '''Wine Architecture''' with either '''linux-x86''' (32-bit virtual drive) or '''linux-amd64''' (64-bit virtual drive)

* '''Wine Version''' with the '''EXACT''' name listed in the '''Wine dropdown menu''' in the '''General tab''' of the ''' Configuration Window'''

== Error! Files mismatch ==

=== Error ===

{{Console|''someurl''

Error! Files mismatch

Local: ''md5resultexpected''

Server: ''md5resultdownloaded''

Do you want to retry?
}}

=== Who might encounter this error? ===

This can happen to any user on any system. It is also architecture agnostic.

=== What causes this error? ===

When POL scripts use certain API calls, there is a positional argument for the MD5 hash, to make sure that the downloaded file is intact and is not different than what has been tested. If the server hosting a certain file updates or changes the file in question, or if the download fails, the MD5 will be different, and will throw an error.

=== Common solutions ===

==== File bug report with POL ====

If this happens, it is something that the POL team should be made aware of. Please let us know so that we can take measures to correct this issue. As long as we can get the new file successfully, we can grab the MD5 hash and change the script so that this error will not pop up again (of course, if the file changes, this will happen again, and should be reported.).

== The application you are trying to install needs administrator rights... ==

=== Error ===

{{Console|The application you are trying to install needs administrator rights to function correctly.}}

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Wine does not implement privileges as some Windows applications may expect, so if a program relies on certain aspects of Windows' user rights that Wine does not or cannot implement, it will fail.

=== Common solutions ===

==== File bug report with WineHQ ====

Anything like this should be reported directly to WineHQ's team, as they would need to troubleshoot and possibly develop a workaround to the permissions issue. You can find their bug system here:

* [https://bugs.winehq.org/ WineHQ's Bugzilla]

== League of Legends Stuck on Logo (after Champ Select) ==

=== Error ===

League of Legends simply stalls at the logo after the champion select dialogue.

=== Who might encounter this error? ===

Anyone on any distro may see this error

=== What causes this error? ===

Multiple d3d libraries that come with Wine apparently, according to threads like [https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html this], do not offer the performance that the native d3d libraries do.

=== Common solutions ===

==== Install needed components ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html https://www.playonlinux.com/en/topic-11344-HOWTO_Fix_League_Of_Legends_stuck_on_Logo_after_champ_select.html]

# Install in POL: d3dx10, d3dx11, d3dx9 (only d3dx9, not the other d3dx9_etc) and directx9
# It will break your Adobe Air (already installed in the virtual drive). I really don't know why but it does it, so we have to fix, go to Configure Wine, then select the tab Libraries and add the lib "dnsapi" and set it to "builtin, native"

== PlayOnMac: SECUR32_initNTLMSP ntlm_auth was not found or is outdated ==

=== Error ===

{{Console|err:winediag:SECUR32_initNTLMSP ntlm_auth was not found or is outdated. Make sure that ntlm_auth 3.0.25 is in your path. Usually, you can find it in the winbind package of your distribution.}}

=== Who might encounter this error? ===

PlayOnMac users, even if Samba and winbind are installed.

=== What causes this error? ===

PlayOnMac is not reading the correct path for some reason.

=== Common solutions ===

==== Edit PlayOnMac Bash script to properly set path ====

Instructions adapted from this thread:

[https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html https://www.playonlinux.com/en/topic-13072-Dreaded_ntlm_auth.html]

# Edit ''/Applications/PlayOnMac.app/Contents/MacOS/playonmac''
# Change ''#!/bin/bash'' to ''#!/bin/bash --login'', save, and try to start PlayOnMac

== No sound (err:module:load_builtin_dll... libasound.so.2...) ==

=== Error ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winealsa.drv": libasound.so.2: cannot open shared object file: No such file or directory.}}

=== Who might encounter this error? ===

Any user on any system may experience this.

=== What causes this error? ===

Missing 32-bit library; in this case, ''libasound2''.

=== Common solutions ===

==== Install the 32-bit version of libasound2 ====

Refer to your distro's docs for the package name for that system. 64-bit systems, because of how Wine/POL works, will almost always need the 32-bit version of libraries used for Wine/POL. Multiarch system's with support for package management with mixed-architectures should check manually if this error is coming up (some distros put things in odd places or don't handle multiarch support very well.).

== About a script stored in 'Supported software', how to install it with a newer Wine version ? ==

When a script is becoming very old (ie: 5 years), it sometimes might fail to run on some newer operating system. If it fail to complete, it is impossible to upgrade later the Wine version from the Configuration window.

Here is how to workaround the issue:
* Find the page of the script/software you want to install, inside [https://www.playonlinux.com/en/supported_apps.html 'Supported apps'] of this website.
* Display the code from the 'Source code' button.
* Open (or copy) a text file on your computer.
* Edit the text file with a text editor software.
* Copy then paste the content from the website to the text file (replace all the content).
* Search for the following text: WORKING_WINE_VERSION="1.3.2" (the number is a example).
* Replace the Wine version with something else.
* Save the text file.
* Rename it in order to give it a '.pol' file extension.
* Now in POL/POM v4, run this new script file from the menu 'Tools' then 'Run a local script'.

Note: if you get better results, please contribute by reporting in the forum (post the OS version and the Wine version used).

== Missing files ==

=== libFaudio.so.0 ===

{{Console|0009:err:module:load_so_dll failed to load .so lib "/home/YourUseNname/.PlayOnLinux/wine/linux-amd64/4.15/bin/../lib/wine/x3daudio1_7.dll.so": libFaudio.so.0: cannot open shared object file: No such file or directory}}

Explanation:
From Wine 4.5, Wine requires libfaudio0 as a dependency ([https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 ref]). FAudio is a drop in replacement for XAudio2, X3DAudio, XAPO, and XACT3 ([https://github.com/FNA-XNA/FAudio ref]). [https://forum.level1techs.com/t/faudio-for-dummies-ubuntu-based-distros/144345 A full FAQ].

Workaround:
* This way (OK as of 2019-09-28):
{{Console|
cd ~/Desktop

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/amd64/libfaudio0_19.07-0~bionic_amd64.deb

wget https://download.opensuse.org/repositories/Emulators:/Wine:/Debian/xUbuntu_18.04/i386/libfaudio0_19.07-0~bionic_i386.deb

cd ~/Desktop

sudo dpkg -i libfaudio0_19.07-0~bionic_amd64.deb libfaudio0_19.07-0~bionic_i386.deb

sudo apt --fix-broken install
}}

* Ubuntu 18.04: [https://askubuntu.com/questions/1145473/how-do-i-install-libfaudio0/1145491 howto] (outdated as of 2019-09-28, because broken links)

=== libpng12.so.0 ===

{{Console|DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://www.linuxuprising.com/2018/05/fix-libpng12-0-missing-in-ubuntu-1804.html Fix libpng12-0 Missing In Ubuntu 18.04 Or 18.10] (2018)

=== libncurses.so.5 ===

{{Console|DOSBox: error while loading shared libraries: libncurses.so.5: cannot open shared object file: No such file or directory}}

Workaround: unknown.

=== libudev.so.0 ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winebus.sys": libudev.so.0: : cannot open shared object file: No such file or directory}}

This file is not included anymore in Ubuntu from v18.04.

Workaround:
* [https://linuxconfig.org/how-to-fix-cannot-open-shared-object-file-libudev-so-0-error-on-ubuntu-18-04-bionic-beaver-linux How to fix Cannot open shared object file libudev.so.0 error on Ubuntu 18.04 Bionic Beaver Linux ] (2019)

=== libSM.so.6 ===

{{Console|err:module:load_builtin_dll failed to load .so lib for builtin L"winex11.drv": libSM.so.6: cannot open shared object file: No such file or directory}}

Fix: install of 32-bit version of this package:
<pre class='code bash'>
sudo apt install libsm6:i386
</pre>

=== libjpeg.so.62 ===

{{Console|002d:err:wincodecs:JpegDecoder_CreateInstance Failed reading JPEG because unable to find libjpeg.so.62}}

Occured with POL 4.3.4 and Wine 4.0.1
This file is not included anymore in Ubuntu from v18.04

Workaround:
* sudo apt-get install libjpeg62
* sudo apt-get install libjpeg62:i386

== FreeType font library ==

{{Console|Wine cannot find the FreeType font library. To enable Wine to use TrueType fonts please install a version of FreeType greater than or equal to 2.0.5.}}

This issue occurs when the Freetype font is not installed, or outdated.

Workaround:
* Ubuntu 18.04: edit the script in order to use at least Wine v2.22

Scripting - Chapter 9: Standardization

2019-11-02T16:58:57Z

Dadu042: /* Setting the software categorie */ Fix

== Standardization, what is this thing? ==

To improve script readability, maintainability, debugging, and translation, scripts are standardized. This means that things need to be added or modified so that scripts will look and behave in a similar fashion.

Let us go over the details...

== Make your script available under Mac OS X using PlayOnMac ==

It may be useful to clarify (for those who would not know) that PlayOnLinux and PlayOnMac are really the same software, sharing the same code. Only the name changes depending on the operating system. So, making your script available to PlayOnMac users can be very easy. You just have to check that your script runs fine under Mac OS X. Even if you don't have any Mac OS X at hand, for small and simple software one can expect that, if it works correctly under GNU/Linux, there's a 99% probability that it will also work under Mac OS X.

To make your script available under Mac OS X, check the box "PlayOnMac compatible" of the new script submission form of the PlayOnLinux website. Read more here:

* [[How to Contribute a Script|How to Contribute a Script]]

== Standardization; let's begin ==

First, we shall be introduced to several items regarding standardization in scripts.

=== The $TITLE variable ===

You should assign the variable '''$TITLE''' with the name of the script, and use it every time the name of the script is required.

'''Example:'''
<pre class="playonlinux code">
#!/usr/bin/env playonlinux-bash
[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"

TITLE="Mozilla Firefox" # Should be present in all your scripts

POL_SetupWindow_Init
...
POL_SetupWindow_presentation "$TITLE" "Mozilla" "http://www.mozilla.com" "YourNickname" "MozillaFirefox"
...
POL_Shortcut "firefox.exe" "$TITLE"
...
</pre>

Obviously, adapt it to the name of your script (that usually matches the name of the software it installs).
The variable '''$TITLE''' is notably required for the use of PlayOnLinux's debugging system.

=== Use the $TITLE variable for window titles ===

To avoid confusing the user with disparate window titles, it is recommended to use the variable '''$TITLE''' as window title.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_message "Message" "$TITLE"
POL_SetupWindow_browse "Message" "$TITLE"
POL_SetupWindow_wait "Message" "$TITLE"
</pre>

=== The $PREFIX variable ===

'''Example:'''
<pre class="playonlinux code">
#!/usr/bin/env playonlinux-bash
[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"

TITLE="Mozilla Firefox"
PREFIX="MozillaFirefox"

POL_SetupWindow_Init
...
POL_SetupWindow_presentation "$TITLE" "Mozilla" "http://www.mozilla.com" "YourNickname" "$PREFIX"
...
POL_Wine_SelectPrefix "$PREFIX"
...
POL_System_TmpCreate "$PREFIX"
...
</pre>

=== Some informations about the script ===

It is recommended to provide some information near the beginning of the script, right after the #!/bin/bash line. Headers like this are standard practice in any script or source code, and should be applied as such.

'''Syntax:'''
<pre class="playonlinux code">
#!/usr/bin/env playonlinux-bash
# Date : (Year-month-day hour-min)
# Last revision : (Year-month-day hour-min)
# Wine version used :
# Distribution used to test : Distribution
# Author : Your nickname
# PlayOnLinux : version of POL used to make the script
# Script licence : GPL3 recommended (2018)
# Program licence : License of the main software installed by the script
</pre>

'''Example:'''
<pre class="playonlinux code">
#!/usr/bin/env playonlinux-bash
# Date : (2011-11-19 06-39)
# Last revision : (2011-11-19 06-39)
# Wine version used : 1.3.4
# Distribution used to test : Ubuntu 10.04 LTS
# Author : Your nickname
# PlayOnLinux : 4.3.4
# Script licence : GPL3
# Program licence : Retail
</pre>

=== Enable debugging ===

PlayOnLinux has a script debugging mode that must be enabled through a command. It is mandatory to enable it, even if you have no use for it; if some user experiences a problem with your script, it will allow him to sent a bug report to the PlayOnLinux website.

'''Syntax:'''
<pre class="playonlinux code">
POL_Debug_Init
</pre>

This command should be put right after the command '''POL_SetupWindow_Init'''.

== Some more information ==

Random information that does not fit into previous chapters.

=== It is forbidden to use sudo ===

Commands '''sudo''', '''su''', '''gksudo''', '''kdesu''' and similar are '''forbidden''' for the sake of security. However, if you really need '''sudo''' (for example to display hidden files from hybrid PC/MAC DVDs, using mount command), you can use the following command:

'''Syntax:'''
<pre class="playonlinux code">
POL_Call POL_Function_RootCommand "command using sudo; exit"
</pre>

=== Winetricks forbidden in scripts ===

Winetricks, or a similar script, is forbidden in PlayOnLinux scripts. Instead, you can use the very similar command '''POL_Call'''.

'''Syntax:'''
<pre class="playonlinux code">
POL_Call Script
</pre>

'''Example:'''
<pre class="playonlinux code">
POL_Call POL_Install_vcrun6
</pre>

The list of all the available scripts can be seen on [https://www.playonlinux.com/repository/?cat=100 this page].

== Advanced Standardization ==
=== Setting the software categorie ===
Using the following command allow the GNU/Linux ([https://en.wikipedia.org/wiki/Freedesktop.org freedesktop] compatibles) to sort the icons among the menus.

'''Example:'''
<pre class="playonlinux code">
POL_Shortcut "Space Colony.exe" "$TITLE" "" "" "Game;StrategyGame;"

POL_Shortcut "Photoshop.exe" "$TITLE" "" "" "Graphics;"
</pre>

For details and more categories, read : [https://specifications.freedesktop.org/menu-spec/latest/apa.html Desktop Menu Specification: categories] (see also the [https://specifications.freedesktop.org/menu-spec/latest/apas02.html page Additional Categories]).

Usage: POL_Shortcut [binary] [shortcut name] [playonlinux website icon] [argument] [categories]

=== Adding a changelog (history of changes made to the script) ===

If the script receive many updates, this can help the next developpers to know what was changed and why. Add this between the informations (top) and the script code.

'''Example:'''
<pre class="playonlinux code">
# CHANGELOG
# [MrBean] (2019-05-15 22-40)
# Added some bugs.
# [Dadu042] (2019-05-10 20-36)
# Initial writting.
</pre>

=== Choosing the Wine version ===

When making your script, using the latest Wine version often spare time and bugs. However the Wine version you will put in the script is important, because older POL/POM versions might not support it.

This is why we recommend to chose the latest version supported by the most common POL/POM version currently packaged with GNU/Linux distributions. 
Example: currently (july 2019), Ubuntu 18.04 (Long term support branch) has POL v4.2.12, it support Wine 3.0.3 maximum.

== Scripts translation ==

We're almost done with scripts standardization. The only item left is script translations. This will be the topic of the next chapter.

'''Previous:''' [[Scripting - Chapter 8: My First Real Script|Chapter 8: My First Real Script]]

'''Next:''' [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]

[[Category:Scripting]]

Scripting - Chapter 11: List of Functions

2019-10-28T09:18:50Z

Dadu042: /* Set_OS (4.0+) */

== Legend of colour for the arguments ==
* ''Colours not currently showing up right now. They will be added soon.''

Red: Required argument.

Orange : Required argument if further arguments are present, but can be left empty ("").

Blue : Optional argument, but in some cases required.

Green : Optional argument.

== Start and stop the graphical interface ==

=== POL_GetSetupImages (4.0+) ===

'''Purpose:'''

Download custom images that will be displayed during the installation wizard.

'''Arguments:'''

# Optional --force option to override any cached images
# URL of top image.
# URL of left image.
# Name of the cache directory where to store the images (usually $TITLE).

'''Description:'''

To liven up installations, two images are currently displayed by PlayOnLinux/PlayOnMac installers:

- a 150 by 356 pixels image at the left of "presentation" introductory screen

- a 64 by 64 pixels "icon" image at the upper right corner for the remaining of the installation

Default images are normally displayed, but they can be replaced by custom images of the same resolution using this statement. Both JPEG and PNG file formats are supported, JPEG being the preferred format.

Downloaded images will be stored in a cache to avoid repeated downloads. There's no cache invalidation mechanism, so in case incorrect images may have been put into users' cache, you can:

- either preceed arguments with --force to override any cache content;

- change the name of the cache directory to a different value. Make sure you still use something unique to the script though, say "$TITLE_201510120640", etc.

'''Prerequisite:'''

This statement must be used before '''POL_SetupWindow_Init'''.

'''Example:'''
<pre class="playonlinux code">
POL_GetSetupImages "http://files.playonlinux.com/resources/setups/AC2/top.jpg" "http://files.playonlinux.com/resources/setups/AC2/left.jpg" "$TITLE"
</pre>

=== POL_SetupWindow_Init (4.0+) ===

'''Purpose:'''

Opens the installation wizard window.

'''Arguments:'''

None

'''Description:'''

Open the UI window that will be used by the PlayOnLinux installation wizard script.

While few initialization statements must be run before '''POL_SetupWindow_Init''', most statements expect the installation window to be opened to either display some progression feedback, or report error cases; So this statement should be used very near the beginning of scripts.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_Init
</pre>

=== POL_SetupWindow_Close (4.0+) ===

'''Purpose:'''

Closes the installation wizard window.

'''Arguments:'''

None

'''Description:'''

Close the UI window; Well behaved installation scripts should use this statement before exiting. Since most statements expect the installation window to be opened to either display some progression feedback, so it is recommended to use '''POL_SetupWindow_Close''' as late as possible in the scripts.

If some error has been detected during the execution of the script by the embedded debugger (see "Debugging Commands" below), at this point PlayOnLinux/PlayOnMac will offer the user to send an automated bug report, containing a log of the script execution, and any comments (s)he wants to add about the issue.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_Close
</pre>

== PlayOnLinux graphical interface ==

{{Warning|All the functions below need the command POL_SetupWindow_Init to be executed beforehand.}}

=== POL_SetupWindow_presentation (4.0+) ===

'''Purpose:'''

Display a standard introductory screen for the install script and the software it's about to install.

'''Arguments:'''

# Software name (often $TITLE).
# Software publisher.
# Site of the publisher.
# Script author.
# Prefix name (usually $PREFIX).

'''Description:'''

This statement will display the name of the software the install script is about to install, along with basic informations about it, and the name of the script author, in a standardized format. If some "left image" has been setup with '''POL_GetSetupImages''', it will be displayed at the same time.

This can be used right before the installation starts, so the user has one more chance to check what is about to be installed, and eventually cancel the installation.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_presentation "$TITLE" "Mozilla" "http://www.mozilla.com" "SuperPlumus and NSLW" "$PREFIX"
</pre>

=== POL_SetupWindow_free_presentation (4.0+) ===

'''Purpuse:'''

Display a free format introductory screen.

'''Arguments:'''

# Software name (often $TITLE).
# Message.

'''Description:'''

In case the standardized format of '''POL_SetupWindow_presentation''' introductory screen does not fit the needs of the install script, this statement let you use any text you want instead. If some "left image" has been defined with '''POL_GetSetupImages''' statement, it will be displayed at the same time.

This can be used right before the installation starts, so the user has one more chance to check what is about to be installed, and eventually cancel the installation.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_free_presentation "$TITLE" "Welcome to Mozilla Firefox installation wizard."
</pre>

=== POL_SetupWindow_message (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).

'''Description:'''

Display a message.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_message "Hello world!" "$TITLE"
</pre>

=== check_one - POL_SetupWindow_missing (4.0-4.1.1) ===

'''Arguments for check_one:'''

# Program that must be present.
# Package that contains this program.

'''Description:'''

Check the availability of one or more programs required by the script.

Call check_one as many times as needed (once per program), then use POL_SetupWindow_missing.

'''Example:'''
<pre class="playonlinux code">
check_one "p7zip" "p7zip"
POL_SetupWindow_missing
</pre>

=== POL_SetupWindow_file (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# File to display.

'''Description:'''

Display the content of a file.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_file "Changelog" "$TITLE" "$POL_System_TmpDir/changelog.txt"
</pre>

=== POL_SetupWindow_licence (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# File to display.

'''Description:'''

Similar to the command POL_SetupWindow_file, but adds an "I agree" checkbox.

Useful for displaying licenses.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_licence "Licence:" "$TITLE" "$POL_System_TmpDir/licence.txt"
</pre>

=== POL_SetupWindow_pulsebar - POL_SetupWindow_pulse - POL_SetupWindow_set_text (4.0+) ===

'''Arguments for POL_SetupWindow_pulsebar:'''

# Message.
# Title (often $TITLE).

'''Arguments for POL_SetupWindow_pulse:'''

# Percentage.

'''Arguments for POL_SetupWindow_set_text:'''

# Current text.

'''Description:'''

Display a progression bar, from 0 to 100%.

POL_SetupWindow_pulsebar display the progression bar.

POL_SetupWindow_pulse changes the progression value, from 0 to 100%.

POL_SetupWindow_set_text modifies the current message (different from POL_SetupWindow_pulsebar message).

Useful for displaying licenses.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_pulsebar "Installing patchs 1 to 5." "$TITLE"

POL_SetupWindow_set_text "Installation of patch 1 in progress"
POL_Wine "$POL_System_TmpDir/patch1.exe"
POL_SetupWindow_pulse "20" # meaning 20%

POL_SetupWindow_set_text "Installation of patch 2 in progress"
POL_Wine "$POL_System_TmpDir/patch2.exe"
POL_SetupWindow_pulse "40"

POL_SetupWindow_set_text "Installation of patch 3 in progress"
POL_Wine "$POL_System_TmpDir/patch3.exe"
POL_SetupWindow_pulse "60"

POL_SetupWindow_set_text "Installation of patch 4 in progress"
POL_Wine "$POL_System_TmpDir/patch4.exe"
POL_SetupWindow_pulse "80"

POL_SetupWindow_set_text "Installation of patch 5 in progress"
POL_Wine "$POL_System_TmpDir/patch5.exe"
POL_SetupWindow_pulse "100"
</pre>

=== POL_SetupWindow_wait (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).

'''Description:'''

Display an indeterminate progress bar.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_wait "Please wait" "$TITLE"
</pre>

=== POL_SetupWindow_textbox (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Default value.

'''Description:'''

Display some window asking the user to type in something.

'''Return:'''

What the user typed is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_textbox "Votre pseudo :" "$TITLE"
</pre>

=== POL_SetupWindow_textbox_multiline (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Default value.

'''Description:'''

Similar to POL_SetupWindow_textbox, but typing happens on several lines.

'''Return:'''

What the user typed is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_textbox_multiline "Enter a description for the program" "$TITLE"
</pre>

=== POL_SetupWindow_browse (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Default value.

'''Description:'''

Ask the user to select a file.

'''Return:'''

The path of the file selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_browse "Please select the program." "$TITLE"
</pre>

=== POL_SetupWindow_question (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).

'''Description:'''

Ask a question to the user (that can be answered by Yes or No).

'''Return:'''

Answer is returned in the $APP_ANSWER variable (TRUE for Yes, FALSE for No).

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_question "Message" "Title"
</pre>

=== POL_SetupWindow_menu (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).

'''Description:'''

Display a menu to the user, asking him to select one entry among the choices provided.

'''Return:'''

The choice selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_menu "What's your favorite color?" "$TITLE" "Red~Green~Blue" "~"
</pre>

=== POL_SetupWindow_menu_num (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).

'''Description:'''

Similar to the command POL_SetupWindow_menu except that instead of returning the name of the selected choice (Red for example), it returns the position of the selected choice in the list, as a number (0 being the 1st choice).

'''Return:'''

The choice selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_menu_num "What's your favorite color?" "$TITLE" "Red~Green~Blue" "~"
</pre>

$APP_ANSWER will contain 0 if the user selected Red, 1 for Green, or 2 for Blue.

=== POL_SetupWindow_menu_list (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).
# Default choice.

'''Description:'''

Similar to the command POL_SetupWindow_menu but displays a drop-down list.

'''Return:'''

The choice selected by the user is returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_menu_list "What's your favorite color?" "$TITLE" "Red~Green~Blue" "~"
</pre>

=== POL_SetupWindow_checkbox_list (4.0+) ===

'''Arguments:'''

# Message.
# Title (often $TITLE).
# Available choices.
# Separator character (often ~ or -).

'''Description:'''

Show a list of options and checkboxen to the user, asking him to select the option(s) he wants.

'''Return:'''

The option(s) selected by the user are returned in the $APP_ANSWER variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_checkbox_list "What are your favorite colors?" "$TITLE" "Red~Green~Blue" "~"
if [ "$(echo $APP_ANSWER | grep -o "Red")" != "" ]
then
# Red was selected
fi
if [ "$(echo $APP_ANSWER | grep -o "Green")" != "" ]
then
# Green was selected
fi
if [ "$(echo $APP_ANSWER | grep -o "Blue")" != "" ]
then
# Blue was selected
fi
</pre>

=== POL_SetupWindow_cdrom (4.0+) ===

'''Description:'''

Ask the user to select a loaded CD/DVD.

'''Return:'''

The path to the drive selected by the user is returned in the $CDROM variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_cdrom
</pre>

=== POL_SetupWindow_check_cdrom (4.0+) ===

'''Arguments:'''

# 1, 2, etc. List of files that should be present.

'''Description:'''

Check, in order, if the files specified exist on the CD/DVD. If one is found, $CDROM_SETUP is set to the file path, and the script continues;

Otherwise, execute POL_SetupWindow_cdrom again.

'''Return:'''

Should be used right after POL_SetupWindow_cdrom.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_check_cdrom "Data/32_icon.ico"
</pre>

=== POL_SetupWindow_InstallMethod (4.0+) ===

'''Arguments:'''

# Comma separated list of installation methods available.

'''Description:'''

Ask the user want installation method he wants, among the available choices.

'''Available installation methods:'''

'''LOCAL, CD, DVD, DOWNLOAD, STEAM, STEAM_DEMO.'''

'''Return:'''

The choice selected by the user is returned in the $INSTALL_METHOD variable.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_InstallMethod "LOCAL,CD,STEAM"
</pre>

== POL_RequiredVersion (4.0.15+) ==

'''Arguments:'''

# Minimum version.

'''Description:'''

Checks that the user is running a version of PlayOnLinux/PlayOnMac that is at least equal to the version provided as argument; If not, stops the script execution while alerting the user that (s)he needs to upgrade to run the script.

This is very useful to put near the top of scripts that use statements of features that only appeared in a relatively version of PlayOnLinux/PlayOnMac.

Remarks:
* The sweet spot to place POL_RequiredVersion is between POL_SetupWindow_Init (the interface must be ready to display a user warning) and POL_Debug_Init (so that the usage of an old version of PlayOnLinux/PlayOnMac does not trigger all the embedded debugger/bug reporting workflow);
* While POL_RequiredVersion can display warnings on its own, it itself only appeared in PlayOnLinux 4.0.15, and PlayOnLinux 4.0.14 is still the default in some distributions; So for the time being, it is recommended to complement it with a check that the statement itself exists, as shown in the example below.
'''Prerequisite:'''

The command POL_SetupWindow_Init must have been used beforehand.

'''Example:'''
POL_RequiredVersion 4.0.18 || POL_Debug_Fatal "$TITLE won't work with $APPLICATION_TITLE $VERSION\nPlease update"

== POL_AdvisedVersion (4.0.15+) ==

'''Arguments:'''

# Minimum version.

'''Description:'''

Very similar to POL_RequiredVersion (see POL_RequiredVersion), but do not stop the script execution after having alerted the user.

The script should be able to run on older versions of PlayOnLinux/PlayOnMac, even if in some kind of degraded mode.

All remarks about POL_RequiredVersion apply; If you use both in the same script, put POL_RequiredVersion first.

'''Prerequisite:'''

The command POL_SetupWindow_Init must have been used beforehand.

'''Example:'''
NEEDED=4.0.18
POL_AdvisedVersion $NEEDED || POL_Debug_Message "$TITLE works better with $APPLICATION_TITLE $NEEDED\nPlease update"

== POL_Shortcut (4.0+) ==

'''Arguments:'''

# Executable filename.
# Launcher name (often $TITLE).
# Optional name of the icon to download from PlayOnLinux website.
# Optional executable arguments.
# Optional list of categories the program belongs to (4.2+)

'''Description:'''

Create a launcher in PlayOnLinux. If some path is specified before the executable filename, it will be interpreted relative to the "drive_c" subdirectory of the prefix. Note that Wine, like Windows, translates the name of the "Program Files" directory according to the user locale, so you should always use the special variable $PROGRAMFILES instead of its name in your own locale.

If no path is specified (recommended), the executable filename is looked up using a case insensitive [http://linux.die.net/man/7/glob glob] search, so you can use wildcards as needed; On the other hand if the program filename contains special characters they may require quoting to avoid being interpreted as wildcards.

PlayOnLinux can also create entries in system menus, but only if category(ies) is(are) provided. The list of valid categories can be found on freedesktop.org site (see [http://standards.freedesktop.org/menu-spec/latest/apa.html main] and [http://standards.freedesktop.org/menu-spec/latest/apas02.html additional] categories). More than one category can be provided, the list separated (and optionally terminated) by semicolons (;).

'''Prerequisite:'''

The command POL_Wine_SelectPrefix must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Shortcut "firefox.exe" "$TITLE"
</pre>

== POL_Shortcut_InsertBeforeWine (4.0+) ==

'''Arguments:'''

# Launcher name (often $TITLE).
# Command to add.

'''Description:'''

Allows to run an extra command each time a program will be about to start.

'''Example:'''
<pre class="playonlinux code">
POL_Shortcut_InsertBeforeWine "Jedi Knight II" "export __GL_ExtensionStringVersion=17700"
</pre>

== POL_Shortcut_QuietDebug (4.0.17+) ==
'''Arguments:'''

# Launcher name (often $TITLE).

'''Description:'''

Avoid displaying "This program may have crashed" dialog box when the program launched by a shortcut exits with a non-zero exitcode.

This is a bandaid for programs exiting with meaningless exitcodes, as it sometimes happens since it's of little consequence under Windows.

'''Example:'''
POL_Shortcut_QuietDebug "Sam and Max S2E1: Ice Station Santa"

== POL_Shortcut_Document (4.0.15+) ==
'''Arguments:'''
# Launcher name (often $TITLE).
# Path to some documentation file

'''Description:'''

Link some documentation file to an existing PlayOnLinux shortcut; The documentation will be available using Right-click on shortcut > Read the manual.

Document file is looked up using the same rules POL_Shortcut uses to find executables.

'''Prerequisite:'''

The command POL_Wine_SelectPrefix must have been used beforehand.

'''Example:'''
POL_Shortcut_Document "$TITLE" "README.txt"

== POL_Browser (4.0+) ==

'''Arguments:'''

# URL to open.

'''Description:'''

Opens a URL in the user's default Internet browser.

'''Example:'''
<pre class="playonlinux code">
POL_Browser "http://www.playonlinux.com"
</pre>

== POL_Download (4.0+) ==

'''Arguments:'''

# URL to download.
# (Optional) Expected MD5 digest of the downloaded file

'''Description:'''

Download a URL to a local file. The file will be created in the current directory, named after the last component of the URL.

If an expected MD5 digest is provided (recommended), the downloaded file will then be run thru the MD5 digest algorithm, and the result compared to the expected value. If they differ, it will be assumed the download broke and the user will be asked if (s)he wants the download to be reattempted.

This is a very effective way to ensure that the downloaded content is the expected one, however some URLs lead to resources that are very often updated, in which case providing an up-to-date MD5 digest can be impractical.

'''Example:'''
POL_Download "http://repository.playonlinux.com/divers/QuickTime.qtp" "417f9bf5ec52d3bfa5826b4905658dac"

== POL_Download_Resource (4.0+) ==

'''Arguments:'''

# URL to download.
# Expected MD5 digest of the downloaded file
# (Optional) Subfolder to download the file to

'''Description:'''

Download a URL to the local file cache, if not already present. The file will be created in $POL_USER_ROOT/ressources directory (unless some subfolder is provided, in which case it will be created under $POL_USER_ROOT/ressources/<subfolder>, creating the subfolder if needed), and named after the last component of the URL.

Contrary to POL_Download, '''the MD5 digest is mandatory''' for POL_Download_Resource, as it will not only be used to validate the download (see POL_Download), but is also used, if some file already exists in the cache, to check that it has the expected content.

Beware that files stored in the cache will potentially stay there for a very long time, since PlayOnLinux never does any kind of cache cleanup, based on time or size; So you should only use POL_Download_Resource for files that are likely to be reused, possibly because they're necessary for several install scripts.

'''Example:'''
POL_Download_Resource "http://downloads.sourceforge.net/ffdshow-tryout/ffdshow_beta7_rev3154_20091209.exe" "c3f75f29521f749f9c9fc5489544cb04"

== POL_System_TmpCreate (4.0+) ==

'''Arguments:'''

# Name of the temporary directory (often $PREFIX).

'''Description:'''

Creates the temporary directory dedicated to the script.

'''Return:'''

$POL_System_TmpDir will contain the path of the created temporary directory.

'''Example:'''
<pre class="playonlinux code">
POL_System_TmpCreate "$PREFIX"
</pre>

== POL_System_TmpDelete (4.0+) ==

'''Description:'''

Removes the script's temporary directory.

'''Example:'''
<pre class="playonlinux code">
POL_System_TmpDelete
</pre>

== POL_System_SetArch (4.0+) ==

'''Arguments:'''

# Supported architectures (see below).

'''Description:'''

Set the (Wine) architectures supported by the script.

'''Allowed values:'''

* '''auto''': Use the version of Wine matching the system architecture (Wine x86 on x86 and Wine x64 on amd64).

* '''x86''': Use the x86 version of Wine for installation (useful if the program doesn't work well with the x64 version).

* '''amd64''': Use the x64 version of Wine for installation (if the system architecture is x86, the script stops).

'''Example:'''
<pre class="playonlinux code">
POL_System_SetArch "auto"
</pre>

'''Prerequisite:'''

The command POL_Wine_PrefixCreate must be located after.

== POL_Call (4.0+) ==

'''Arguments:'''

# Function name.
# 2, 3, etc.: Function arguments, if necessary (very few functions take arguments).

'''Description:'''

Download and execute a script from the Functions category (the list of functions and their basic information for each can be found here: [[Components and Functions|Components and Functions]]).

'''Prerequisite:'''

For most functions, the commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Call POL_Install_vcrun6
</pre>

== Wine-related functions ==

=== POL_Wine_SelectPrefix (4.0+) ===

'''Arguments:'''

# Prefix name (often $PREFIX).

'''Description:'''

Select the prefix that will be used by Wine (mandatory, even if the prefix hasn't been created yet).

'''Example:'''
<pre class="playonlinux code">
POL_Wine_SelectPrefix "$PREFIX"
</pre>

=== POL_Wine_PrefixExists (4.0+) ===

'''Arguments:'''

# Prefix name (often $PREFIX).

'''Description:'''

Check if a prefix exists (useful for game extensions and patches).

'''Return:'''

The function displays True if the prefix exists, and False otherwise.

'''Example:'''
<pre class="playonlinux code">
if [ "$(POL_Wine_PrefixExists "$PREFIX")" = "False" ]
then
# The préfixe doesn't exist
fi
</pre>

=== POL_Wine_PrefixCreate (4.0+) ===

'''Arguments:'''

# Wine version.

'''Description:'''

Creates or updates a prefix. It is possible to use a version of Wine different from the one installed system wide on user's computer, by specifying this version as first argument.

'''Prerequisite:'''

The command POL_Wine_SelectPrefix must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_PrefixCreate "1.3.4"
</pre>

=== POL_Wine (4.0+) ===
'''Arguments:'''
* Program pathname.
* 2, 3, etc.: program arguments, if any.
'''Description:'''

This command will run the given program; It works exactly like the "wine" command, but uses the Wine versions management and logging facilities of PlayOnLinux.

While most programs started that way will behave synchronously (in other words, will block the script until they're finished), some don't and the POL_Command will need to be followed by a POL_Wine_WaitExit command to prevent the rest of the script from being executed before the program has finished.

See POL_Wine_WaitBefore and POL_Wine_WaitExit.

Note: Using '''start /unix''' before the program name can fix issues of access and installation paths with several CD/DVD. However, the use of start /unix makes POL_Wine asynchronous, and since asynchronous programs are not automatically killed if the script is aborted from PlayOnLinux side, it should only be used when necessary.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

=== POL_SetupWindow_VMS (4.0+) ===
'''Arguments:'''

# Minimum amount of onboard video memory required, in MB.

'''Description:'''

Ask the user how much (dedicated) RAM his videocard has, since it is actually very difficult to determine this value in a portable way.

If the value is lower than the minimum argument value, the user is warned that the program being installed is likely not to work correctly. In all cases, the script goes on and the value is written in the Wine registry.

The user reply is cached so that it doesn't need to be asked again during the next installations. In case of mistake, or if the amount of video memory changes, the cached value can be erased by opening the PlayOnLinux console, and typing "POL_Config_Delete VMS" (for a lack of GUI support at the moment).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_SetupWindow_VMS "128"
</pre>

=== Set_OS (4.0+) ===

'''Arguments:'''

# Windows version to emulate.
# Service pack.

'''Description:'''

Modifies the Windows version emulated by Wine.

'''Default value:''' winxp (Windows XP).

'''Allowed values:'''

'''Windows versions''': win7, vista, win2003, winxp, win2k, winnt, winme, nt40, win98, win95, win31.

'''Services packs''': sp1, sp2, sp3.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_OS "winxp"
</pre>

=== Set_Managed (4.0+) ===

'''Arguments:'''

# On/Off.

'''Description:'''

Set if the window manager will be allowed to manage Wine windows.

'''Default value''': On.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_Managed "Off"
</pre>

=== Set_SoundDriver (4.0+) ===

'''Arguments:'''

# alsa/oss/esd.

'''Description:'''

Set the audio driver Wine will use.

{{Info|This command does nothing under PlayOnMac, since it is useless in that environment.}}

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_SoundDriver "alsa"
</pre>

=== POL_Wine_Direct3D (4.0+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\Direct3D].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_Direct3D "UseGLSL" "disabled"
</pre>

=== POL_Wine_X11Drv (4.0.14+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\X11 Driver].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_X11Drv "DXGrab" "Y"
</pre>

=== POL_Wine_DirectSound (4.0+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\DirectSound].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_DirectSound "HardwareAcceleration" "Emulation"
</pre>

=== POL_Wine_DirectInput (4.0+) ===

'''Arguments:'''

# Setting to create/modify.
# New setting value.

'''Description:'''

Creates or modifies a registry setting below key [HKEY_CURRENT_USER\Software\Wine\DirectInput].

'''Allowed values:'''

See [http://wiki.winehq.org/UsefulRegistryKeys WineHQ's Wiki].

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_DirectInput "MouseWarpOverride" "force"
</pre>

=== POL_Wine_GetRegValue (4.0+) ===

'''Arguments:'''

# Setting to read (the key is not required).

'''Description:'''

This function returns the value of a setting from the registry.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Return:'''

The function displays the value of the specified setting.

'''Example:'''
<pre class="playonlinux code">
VALUE="$(POL_Wine_GetRegValue "MouseWarpOverride")"
</pre>

=== Set_Desktop (4.0+) ===

'''Arguments:'''

# On/Off.
# Virtual desktop width (if it is enabled).
# Virtual desktop height (if it is enabled).

'''Description:'''

Sets the Wine virtual desktop settings.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_Desktop "On" "1024" "768"
</pre>

=== Set_WineWindowTitle (4.0+) ===

'''Arguments:'''

# Virtual desktop name.

'''Description:'''

Set the title of the virtual desktop window (purely aesthetic effect).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
Set_WineWindowTitle "$TITLE"
</pre>

=== POL_Wine_InstallFonts (4.0+) ===

'''Description:'''

This command installs standard (but not installed by default) fonts into the prefix.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_InstallFonts
</pre>

=== POL_Wine_SetVideoDriver (4.0+) ===

'''Description:'''

Set correct video driver (when Wine fails to do it properly).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_SetVideoDriver
</pre>

=== POL_Wine_OverrideDLL (4.0+) ===

'''Arguments:'''

# Mode of override.
# 3, 4, etc.: DLL names (without .dll suffix).

'''Description:'''

Set the override mode for one or more dynamic library(ies).

'''Allowed override modes:'''

"native", "builtin", "native,builtin", "builtin,native", or empty value ("") to disable the DLL(s).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_OverrideDLL "native" "msvcrt"
POL_Wine_OverrideDLL "" "msvcrt" # To disable the DLL
</pre>

=== POL_Wine_OverrideDLL_App (4.0+) ===

'''Arguments:'''

# Executable name.
# Mode of override.
# 3, 4, etc.: DLL names (without .dll suffix).

'''Description:'''

Set the override mode for one or more dynamic library(ies), but only for a specific program.

'''Allowed override modes:'''

"native", "builtin", "native,builtin", "builtin,native", or empty value ("") to disable the DLL(s).

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_OverrideDLL_App "firefox.exe" "native" "msvcrt"
POL_Wine_OverrideDLL_App "firefox.exe" "" "msvcrt" # To disable the DLL
</pre>

=== POL_Wine_WaitBefore (4.0.15+) ===

'''Arguments:'''

# Program name.

'''Description:'''

Placed before a POL_Wine command that starts a program synchronously (ie a "blocking" POL_Wine command), it will display a standard wait message while it runs.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
POL_Wine_WaitBefore "$TITLE"

=== POL_Wine_WaitExit (4.0+) ===

'''Arguments:'''

# Program name.

'''Description:'''

Placed after a POL_Wine command that starts a program asynchronously (ie a "non-blocking" POL_Wine command), it will display a standard wait message while it runs and wait for its completion.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_WaitExit "$TITLE"
</pre>

=== POL_Wine_reboot (4.0+) ===

'''Description:'''

Emulate a Windows reboot.

'''Prerequisite:'''

The commands POL_Wine_SelectPrefix and POL_Wine_PrefixCreate must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Wine_reboot
</pre>

== Debugging commands ==

=== POL_Debug_Init (4.0+) ===

'''Description:'''

Start debugging system.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Init
</pre>

=== POL_Debug_Message (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Write a message to the installation log (not shown to the user).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Message "Modifying config.cfg file."
</pre>

=== POL_Debug_Warning (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Write a warning message to the installation log (not shown to the user).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Warning "File config.cfg did not exist, creating one."
</pre>

=== POL_Debug_Error (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Write an error message to the installation log (not shown to the user).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Error "Error while modifying config.cfg file"
</pre>

=== POL_Debug_Fatal (4.0+) ===

'''Arguments:'''

# Message.

'''Description:'''

Raises a fatal error (the script is immediately aborted).

'''Prerequisite:'''

The command POL_Debug_Init must have been used beforehand.

'''Example:'''
<pre class="playonlinux code">
POL_Debug_Fatal "Error while modifying config.cfg file"
</pre>

'''Previous:''' [[Scripting - Chapter 10: Script Translation|Chapter 10: Script Translation]]

[[Category:Scripting]]

How to Read Debug Logs

2019-10-24T12:58:20Z

Dadu042: /* Debug flags */

== Get the debug log (from POL v4) ==
To access the debug log of a POL compatible software, in the main GUI click on the name of the software, then on the left side click the 'Debug' button.

On the right side appears the debug of the last uses. You may copy/paste the latest one to show it to someone else.

== Debug mode ==

=== Folders location ===
There is two folders where you can find POL/POM log files:
* /home/you/.PlayOnLinux/logs/game_name/ is the place where is store the installation log when the game (or any software) is installed the first time.
* /home/you/PlayOnLinux's virtual drives/game_name/ is the place where is store the Log of the game when launched (ie: Wine debugs). Note: you can delete this file, it will be recreated automatically.

=== Debug flags ===
It is possible to hide all Wine errors: "Debug Flags: -all". This avoid the size of the log file to increase, and (sometimes) avoid some slowness for the storage device.

Examples:
* "fixme-all"
* "-all,fixme-all"
* "-d3d"

See also: [https://wiki.winehq.org/Debug_Channels Debug flags listed on the Wiki of winehq.org].

== Read the debug log ==

=== Error related to Wine ('wine: Unhandled page fault on read access ...') ===
Example:
{{Console|
wine: Unhandled page fault on read access to 0x00000008 at address 0x43adae (thread 0009), starting debugger...

Unhandled exception: page fault on read access to 0x00000008 in 32-bit code (0x0043adae).

Register dump:

CS:0023 SS:002b DS:002b ES:002b FS:0063 GS:006b

EIP:0043adae ESP:0032fd40 EBP:00b90004 EFLAGS:00210202( R- -- I - - - )

EAX:00000032 EBX:00000000 ECX:00000000 EDX:0000fffe

ESI:00a8df82 EDI:00a8df9e

Stack dump:

0x0032fd40: 00439cf4 00a8df9e 00b9cccc 00000000

0x0032fd50: 00439bb4 0032fd88 00abceca 00000102

0x0032fd60: 0000013c 00000020 0043778c 00437848

0x0032fd70: 00000000 00000001 10042134 10042130

0x0032fd80: 00000001 0032fd90 00000006 00416611

0x0032fd90: 004452d6 00000000 00000001 00000001

Backtrace:

...
}}

For this kind of error log, the issue (it's a internal crash) is related to Wine not to POL.

Here are the best steps to follow:
# Try to use a newer Wine version inside POL (try up to the latest stable available in POL).
# If the issue occurs when installing the software you want, you may try to use a newer Wine version but this need some manual operations: copy the script (if from our website, find it into 'supported software') into a '.pol' (text) file. Edit it with a [https://en.wikipedia.org/wiki/Text_editor text editor] software in order to change the Wine version, save it. From POL, do load the script as a file (Menu 'Tools' -> 'Run a local script').
# After the tests above, you may search for help at https://winehq.org Note: the Playonlinux log will '''not be accepted''' there. You will have to reproduce the issue with Wine only (with a recent Wine version), in order to get a clean log.

=== Error related to Microsoft Dotnet ===

The entry point method could not be loaded due to Could not load file or assembly 'PresentationFramework, Version=4.0.0.0, ...' or one of its dependencies.

This error message in the log mean that installation of Microsoft DotNet 4.0 is required.

=== X3DAudio ===
{{Console|
002c:err:module:load_builtin_dll failed to load .so lib for builtin L"X3DAudio1_7.dll": libFAudio.so.0:
}}

Should (POL v4, 2019) be fixable by installing: [https://www.playonlinux.com/fr/app-635-POL_Install_xact.html POL_Install_xact]

=== Missing files ===

File(s) missing in your OS:

{{Console|
DOSBox: error while loading shared libraries: libpng12.so.0: cannot open shared object file: No such file or directory
}}

In this example DOS is missing the file 'libpng12.so.0' in your OS (for this file, look: [[Troubleshooting Common Problems]]).

== See also ==
* [[Troubleshooting Common Problems]]

How to Post in the Forums

2019-10-23T17:45:36Z

Dadu042:

== The different forum areas ==

All messages '''concerning a program in supported software list''' (whatever it is: bug, feedback) must be posted in the following forum:

* http://www.playonlinux.com/en/forum-22-Application_tests.html

All messages regarding '''PlayOnLinux''' specifically:

* https://www.playonlinux.com/en/forum-72-PlayOnLinux.html

All messages regarding '''PlayOnMac''' specifically:

* https://www.playonlinux.com/en/forum-73-PlayOnMac.html

All messages concerning unsupported apps must be posting in the "manual installation" section:

* http://www.playonlinux.com/en/forum-24-Manual_installations.html

Writing a script and needing help?:

* http://www.playonlinux.com/en/forum-25-Your_creations.html

Questions about the website:

* http://www.playonlinux.com/en/forum-71-Website.html

For everything else:

* http://www.playonlinux.com/en/forum-74-General_discussion.html

== What NOT to do ==
This example of message will not be accepted:

<pre>
Hi, I have a big problem with POL, when I try to run it, it doesn't work.
Please help, it is urgent, I'm new in linux, I don't understand anything! Please help!
</pre>

Topics like this, or without the required information will be locked.

== What information is needed in my post? ==

There are few rules to respect. To start, you have to be polite and write fluently (SMS language is forbidden; those messages are immediately deleted). Then, try to provide as much information as you can:
* '''Linux version''': You OS distribution, architecture (32-bit or 64-bit Linux), and version.
* '''Version of POL''': PlayOnLinux version (you can get it in the help menu: '''Help -> About PlayOnLinux''').
* '''Full computer specs''': CPU, RAM, graphics card type and installed drivers, etc..
* '''All''' error message you can find (preferably from the debug logs available in '''Tools -> PlayOnLinux/PlayOnMac debugger''')
* Log of the installation script: '''if the error occurs when installing a POL script''', you will find the log file there: ~./.PlayOnLinux/logs/name/name.log

== How do I properly paste a log? ==

That is really easy; copy and paste it, and give it the ''console'' style '''(Styles -> Console)'''

'''Example:'''

https://www.playonlinux.com/images/uploads/238.jpg

== How do I properly paste a script? ==

Exactly the same, but instead of ''Console'', choose ''PlayOnLinux script'' style. Once posted the code will be '''coloured like that''' :

<pre class="playonlinux code">
#!/bin/bash
# Date : (2014-06-09 20:00)
# Last revision : (2014-06-09 20:00)
# Wine version used : 1.7.12
# Distribution used to test : Ubuntu 14.04 - 64 bit (KDE)
# Author : Tutul & Rashintawak
# License : GNU/GPL v3

## Beta script ##

[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"

TITLE="The mighty quest for epic loot"
PREFIX="TheMightyQuest"
EDITOR="Ubisoft"
GAME_URL="https://www.themightyquest.com"
AUTHOR="Tutul & Rashintawak"
GAME_VMS="512"

# Starting the script
#POL_GetSetupImages "" "" "$TITLE" No image uploaded for now
POL_SetupWindow_Init
# POL_SetupWindow_SetID Not now

# Starting debugging API
POL_Debug_Init

POL_SetupWindow_presentation "$TITLE" "$EDITOR" "$GAME_URL" "$AUTHOR" "$PREFIX"
</pre>

How to Post in the Forums

2019-10-23T17:43:45Z

Dadu042: /* What information is needed in my post? */

== The different forum areas ==

All messages '''concerning a program in supported software list''' (whatever it is: bug, feedback) must be posted in the following forum:

* http://www.playonlinux.com/en/forum-22-Application_tests.html

All messages regarding '''PlayOnLinux''' specifically:

* https://www.playonlinux.com/en/forum-72-PlayOnLinux.html

All messages regarding '''PlayOnMac''' specifically:

* https://www.playonlinux.com/en/forum-73-PlayOnMac.html

All messages concerning unsupported apps must be posting in the "manual installation" section:

* http://www.playonlinux.com/en/forum-24-Manual_installations.html

Writing a script and needing help?:

* http://www.playonlinux.com/en/forum-25-Your_creations.html

Questions about the website:

* http://www.playonlinux.com/en/forum-71-Website.html

For everything else:

* http://www.playonlinux.com/en/forum-74-General_discussion.html

== What information is needed in my post? ==

There are few rules to respect. To start, you have to be polite and write fluently (SMS language is forbidden; those messages are immediately deleted). Then, try to provide as much information as you can:
* '''Linux version''': You OS distribution, architecture (32-bit or 64-bit Linux), and version.
* '''Version of POL''': PlayOnLinux version (you can get it in the help menu: '''Help -> About PlayOnLinux''').
* '''Full computer specs''': CPU, RAM, graphics card type and installed drivers, etc..
* '''All''' error message you can find (preferably from the debug logs available in '''Tools -> PlayOnLinux/PlayOnMac debugger''')
* Log of the installation script: '''if the error occurs when installing a POL script''', you will find the log file there: ~./.PlayOnLinux/logs/name/name.log

For example, this kind of message won't be accepted:

<pre>
Hi, I have a big problem with POL, when I try to run it, it doesn't work.
Please help, it is urgent, I'm new in linux, I don't understand anything! Please help!
</pre>

Topics like this, or without the required information will be locked.

== How do I properly paste a log? ==

That is really easy; copy and paste it, and give it the ''console'' style '''(Styles -> Console)'''

'''Example:'''

https://www.playonlinux.com/images/uploads/238.jpg

== How do I properly paste a script? ==

Exactly the same, but instead of ''Console'', choose ''PlayOnLinux script'' style. Once posted the code will be '''coloured like that''' :

<pre class="playonlinux code">
#!/bin/bash
# Date : (2014-06-09 20:00)
# Last revision : (2014-06-09 20:00)
# Wine version used : 1.7.12
# Distribution used to test : Ubuntu 14.04 - 64 bit (KDE)
# Author : Tutul & Rashintawak
# License : GNU/GPL v3

## Beta script ##

[ "$PLAYONLINUX" = "" ] && exit 0
source "$PLAYONLINUX/lib/sources"

TITLE="The mighty quest for epic loot"
PREFIX="TheMightyQuest"
EDITOR="Ubisoft"
GAME_URL="https://www.themightyquest.com"
AUTHOR="Tutul & Rashintawak"
GAME_VMS="512"

# Starting the script
#POL_GetSetupImages "" "" "$TITLE" No image uploaded for now
POL_SetupWindow_Init
# POL_SetupWindow_SetID Not now

# Starting debugging API
POL_Debug_Init

POL_SetupWindow_presentation "$TITLE" "$EDITOR" "$GAME_URL" "$AUTHOR" "$PREFIX"
</pre>