Original: Wine User Guide
Translation: Alexey Dmitriev, [email protected]
Transfer date: May 2008

Chapter 3 Setting Up Wine (Configuration)

The vast majority of customization is done through the Winecfg tool. We will go through a simple step by step introduction to Winecfg and look at available options. In the next section, we'll look at more advanced changes that can be made when regedit help. We will also do a full review of all Wine configuration settings. And finally, we'll look at tweaks (which you might want to make) that are not available through Winecfg and regedit.

3.1. Winecfg program

In the past, Wine used a special configuration file located in ~/.wine/config. If you are still using a version of Wine dealing with this file (older than June 2005), then you need to upgrade before doing anything else. All settings are now collected directly in the registry (registry) and available to Wine at startup.

The Winecfg program should be installed on your computer along with the rest of the Wine programs. If you don't understand how to run it, try the command:

$ /usr/local/bin/winecfg

or simply

When the program starts, you will see the following tabs at the top of the window:

• Applications
• Libraries
• Graphics
• Desktop Integration
• drives
• Audio
• About

Making changes to the Applications and Libraries tabs will be critical to the ability to run applications. The rest of the settings are there to make the Wine program itself work the way you want it to.

Warning: The Applications, Libraries and Graphics tabs are linked! If you select Default Settings in the Applications tab, any changes made in the Libraries and Graphics tabs will be changed for all applications. If you have configured an application in the Applications tab and selected it, then the settings made in the Libraries or Graphics tabs will apply only to this selected application. This allows you to selectively customize certain applications.

3.1.1. Application Settings

Wine has the ability to mimic behavior various versions Windows. In general, the behaviors of the Win9x versions and the NT versions are the most different. Some applications require specific behavior in order to function properly, and changing this setting may cause a failed application to work. Windows 2000 was recently chosen as the default version of Wine. Many applications are known to work better if you choose Windows 98.

Inside the tab, you will notice the Default Settings line. If you select this line, then all applications will run on the default version of Windows. A problematic application is best configured separately from the default settings. For this:

1. Click the Add application button.
2. Find the desired .exe file.
3. After you add this application, you will be able to choose the version of Windows that Wine will emulate specifically for this application.

3.1.2. Setting up Libraries

Likewise, some applications require special libraries. Wine reproduces the Windows library system (so-called "native" DLLs), creating versions of the libraries that do not need a Microsoft license and work exactly like the "native" ones. Wine lacks such recreated versions of the libraries, but they work quite satisfactorily. Using only recreated DLLs ensures that your system is independent of Microsoft. However, Wine has the ability to load native Windows DLLs.

3.1.2.1. DLL Replacement

It is not always possible to run an application using built-in Wine DLL. Sometimes native DLLs just work better. After you have spotted the native DLL in Windows system, you have to put it in a place where Wine finds it, and then set it up to work. Typically, this location is the directory that you assigned to the c:\windows\system32 role. There are 4 DLLs whose native versions should never be used: kernel32.dll, gdi32.dll, user32.dll, and ntdll.dll. These libraries require low-level access to Windows kernel, which simply does not exist in the Wine structure.

With that in mind, if you've already copied the DLL, then you need to tell Wine to use it. You can configure Wine to choose between native and built-in DLLs on two various levels. If you have Default Settings set in the Applications tab, then the changes you make will affect all applications. Or you can change global settings at the individual application level by adding that application and selecting it in the Applications tab.

To add a replacement file FOO.DLL, type "FOO" in the box titled New override for library and click the Add button. To change the behavior of a DLL, select it from the Existing overrides: field and click Edit. By default, the "native" Windows will be loaded first, the second - the built-in Wine ( Native then Builtin). You can also select only native, only built-in, or disable both.

3.1.2.2. About system DLLs

The Wine team decided that it was necessary to create fake DLLs to fool many programs that only check for the presence of a file to make sure that a certain property (such as Winsock and its TCP/IP networking) is theoretically available. If this is a problem for you, create appropriately named empty files in the configured c:\windows\system32 directory so that the program thinks they are there, and the built-in Wine DLLs will be loaded when the program actually requests them. (Unfortunately, the wineinstall tool does not create such empty files on its own).

Sometimes applications try to figure out the version of a resource directly from a physical file (say, to find out the DirectX version). Dummy files won't help in this case. In this case, you must install the files with the full version code. This issue has already been resolved for many files. If not, then you again have to copy the native DLL file to fool the program.

Naturally, there are DLLs that Wine has not yet implemented properly (or at all). If you don't have a real Windows handy to copy the DLL from, you can always get the file from sites containing Windows archives DLLs that you can find with search engines. Please follow the licensing rules for the DLLs you choose; some are distributed without restrictions, some are not.

3.1.2.3 Missing DLLs

In case Wine complains about missing DLL, you need to check if this file is an "official" DLL, or belongs to the program you are trying to run. This can be done by searching the Internet for the file name. After you've spotted the DLL, you also need to make sure that Wine can use it. The DLL search is usually done in the following order:

1. Directory where the program was launched from.

2.Current (working) directory.

3.Windows system folder.

4 Windows folder.

5 PATH variable directories.

In short: either place the desired DLL in your program directory (may be inconvenient) or place it in the system Windows folder. If possible, avoid native NT-based DLLs, as Wine's support for the NT API is much weaker than that for the Win9x API (sometimes leading to poorer compatibility with NT DLLs than even non-Windows schemas!).

3.1.3 Graphics Settings

There are five different basic settings that can be configured. For most people, the default settings are sufficient.

The first few settings are related mainly to games and are self-explanatory. It is possible to prevent the mouse cursor from leaving the window DirectX programs(i.e. games). This option is enabled by default. There are many reasons to do this, not the least of which is the fact that it is easier to play when the cursor is enclosed in a smaller area. Another reason to enable this option is for better mouse control. Wine distorts mouse position to mimic Windows work. Similarly, "desktop double buffering" produces smoother screen updates that make games look better; again, the option is enabled by default. This is a compromise to increased memory consumption.

It may be useful to emulate a virtual desktop. In this case, all programs will run in a separate window. This can help identify buggy games that change the screen resolution (probably not). Enclosing them in a window may result in better control over them, perhaps at the cost of less convenience. You can try 640x480 (default) or 800x600.

Lastly, you can change some of the Direct3D settings. For the most part, these settings are determined automatically, but you can make them behave in a certain way. Some games try to check the system for support for certain features. By turning off this behavior, Wine will not report the ability to render an image in a certain way. This can lead to increased game speed at the cost of graphics quality; Or maybe the game won't work at all.

3.1.4. Disk settings

Windows has a rather rigid drive naming scheme that Wine mimics. Most people are familiar with the standard layout: "A:" represents the floppy disk, "C:" represents the primary system disk, etc. Wine uses the same concept and partitions drives according to the underlying native file system.

Partitioning disks in Wine is relatively simple. In Winecfg, in the Drives tab, you see buttons for adding and removing the desired drives. When you select "add disk" is created new line and the default drive naming scheme appears. You can change the address pointed to by this disc by making changes to the Path field. If you are in doubt about the correct Path, click the "Browse" button to find the correct Path. You can remove a disk by highlighting the desired one and clicking "Remove".

Winecfg can automatically detect the drives available on your system. It is recommended to try the automatic method before attempting to manually partition disks. With a simple click on the Autodetect button, you have Wine search for disks on your system.

It's very interesting to set up disks without resorting to Winecfg, it's remarkably simple. All disk settings are located in the ~/.wine/dosdevices directory. Each disk is just a symlink to where it actually is. Wine automatically installs two disks during the first run:

$ ls -la ~/.wine/dosdevices/
lrwxrwxrwx 1 wineuser wineuser 10 Jul 23 15:12 c: ->../drive_c
lrwxrwxrwx 1 wineuser wineuser 1 Jul 23 15:12 z: -> /

To add another drive, such as a CD-ROM, simply create another link pointing to it:

$ ln -s /mnt/cdrom ~/.wine/dosdevices/d:

Note that the links use the DOS naming convention for drives, a letter followed by a colon, such as "a:". So if your c: drive link points to ~/.wine/drive_c, you can understand c:\windows\system32 links as ~/.wine/drive_c/windows/system32.

3.1.5 Audio settings

Wine can work with very few audio subsystems, which you can select from the "Audio" tab. Winecfg will detect all available drivers, but you can choose which one to use manually. Old Linux distributions that used the 2.4 kernel usually used the "OSS" driver. The 2.6 kernels switched, in most cases, to "ALSA". The "aRts" driver was recently retired due to a general lack of support for the "aRts" subsystem. If you are using GNOME, you can try EsounD. OSS and ALSA audio drivers are the most tested, so it is recommended that you opt for them if possible. If you need "Jack", "NAS" or "CoreAudio", then you probably know why.

DirectSound settings are mainly used in games. You can choose the amount of hardware acceleration, but "Full" is fine for most.

3.1.6 Desktop layout

Wine can load Windows themes if you have them. While not necessary in terms of running Wine or applications, it allows you to create a familiar look and feel for the program. Wine supports the new MSStyles themes. Unlike the old Microsoft Plus! style themes, the uxtheme engine supports special .msstyles files that can change everything windows settings. This is about the same thing that most Linux desktops have been able to do for many years. If you want to try, then do this:

1. Download Windows theme xp. Make sure the .msstyles file is present.

2. Create a directory chain in your fake Windows drive:

$ mkdir -p ~/.wine/drive_c/windows/Resources/themes/theme_name

3. Move the .msstyles file to the /name-of-your-theme directory

4. Using the Desktop Integration tab in winecfg, select new topic.

3.2 Using the Registry and Regedit

All settings made with Winecfg, with the exception of disk settings, are eventually stored in the Registry. On Windows, this is the central store of settings, like individual applications as well as the operating system itself. Wine uses the Registry in a similar way, so some settings that are not in Winecfg can be changed in the Registry. (You're much more likely to have to go into the Registry to change some program's settings than to change Wine's settings.)

The very fact that Wine uses the Registry to save settings is debatable. Some argue that this is too similar to Windows. To answer this, several points must be taken into account. First, it is impossible to do without the Registry, simply because applications "expect" to store their settings there. In order for Wine to store and access settings in a separate configuration file, it would require a separate set of programs that basically does what the Win32 API does. And finally, unlike Windows, the Wine Registry is written in plain text and can be changed in any text editor. And so, although most of the normal system administrators(and the developers of Wine), cursing like mad at the confusing Windows Registry, it still needs to be supported by Wine in some way.

3.2.1 Structure of the Register

Although this is not exactly on our way, let's delve a little into the structure of the registry and see how it works. The Windows Registry is an intricate tree structure, and even best Windows programmers don't always know how it's planned, with its various hives and endless links between them; Full description not included in the possibilities this document. But here are the basic Registry keys you should now know:

HKEY_LOCAL_MACHINE

This fundamental root key (in win9x it is stored in hidden file system.dat) contains everything related to this Windows installation. Often shortened to HKLM.

This fundamental root key (in win9x it is stored in a hidden user.dat file) contains information about each user in a given installation.

HKEY_CLASSES_ROOT

This is a link to HKEY_LOCAL_MACHINE\Software\Classes. It stores information describing things like file associations, OLE (Object Linking and Embedding) document management, and COM classes (COM technology is a Microsoft standard).

HKEY_CURRENT_USER

This is a link to HKEY_USERS\your_username, i.e. to your personal configuration.

3.2.2. Wine Registry Files

Now you might be wondering how to translate all this into Wine structures. The registry layout described above resides in three different files in the ~/.wine directory: system.reg This file contains HKEY_LOCAL_MACHINE. user.reg This file contains HKEY_CURRENT_USER. userdef.reg This file contains HKEY_HKEY_USERS\.Default (that is, the default user settings). These files are automatically created by the wineprefixcreate program the first time you start Wine. A set of basic settings is stored in the c:\windows\inf\wine.inf file and processed by the rundll32.exe program. When you first start Wine, the rundll32.exe file goes through a process of being populated with the initial registry data. For details, check out the wineprefixcreate script to see how it's all done. After updating Wine, wineprefixcreate can again be used to update the default registry strings.

As already mentioned, you can edit all these .reg files using any text editor. Just make sure Wine is not running at this point, otherwise all your changes will be lost.

3.2.3. How to use regedit

The easiest way to access and modify the Registry is with the regedit tool. Just like the Windows program of the same name that it replaces, regedit is designed to view the registry at the system level, containing all of its keys. Just run regedit and it will open. You will immediately notice that the mysterious keys presented in the text file are organized in a hierarchical manner.

To navigate the registry, click on the keys on the left side of the panel to "dive" to the next level of depth. To delete a key, click on it and select "Delete" from the Edit menu. To add a key or value, locate where you want to put it and select "New" from the Edit menu. To modify an existing key, select it in the right pane and select "Modify" from the Edit menu. Another way to do the same is to click right click mouse on a key or value.

Of particular interest to Wine users are the settings in HKEY_CURRENT_USER\Software\Wine. Most of the settings you make with winecfg are written to this part of the registry.

3.2.4. Tips for the system administrator

Using the above file structure, it is possible to configure the system so that the system installation of Wine (with applications) can be shared by all users, and at the same time allow each user to have his own configuration. The administrator can, by installing Wine and all necessary for users Windows Applications, then copy the resulting system.reg file and others to the global registry files (which, as we agreed, are located in /usr/local/etc), using the commands:

cd ~root/.wine
cp system.reg /usr/local/etc/wine.systemreg

ln -sf /usr/local/etc/wine.systemreg system.reg

You may have to do the same with the user.reg file, even though this file contains user settings. Each user must have their own copy of this file, along with the rights to modify it.

It is necessary to pay attention to the layout of disks. If you publicize the system.reg file, then you must ensure that the registry settings are compatible with the disk layouts in each user's ~/.wine/dosdevices files. Make it a rule that the more your disk layout matches the default one created by wineprefixcreate, the easier your task will be. You may not be able to share all the "c:" drives where you originally installed applications. Some applications require the ability to write certain settings to disk, especially applications for Windows 95/98/ME.

Be aware that if you installed Wine from source as root, the tools/wineinstall script you used to install Wine no longer works.

One last word of warning: watch what you do with your admin account. If you copy (or link) the admin registry to the global registry, then any user can read the admin settings, which is bad if it contains important information about passwords personal information etc. Use the administrator account only to install programs, not to daily work, it must be done under a regular account.

3.2.5. Full list of registry keys

For the most up-to-date list of commonly used keys and values, see the developer's wiki page.

3.3. Other aspects that can be customized

This section contains all other things that can be customized. It also serves as a collection of tips and tricks to get the most out of using Wine.

3.3.1. Serial and Parallel Ports

Serial and parallel ports are configured almost like disks - just create a symbolic link in the ~/.wine/dosdevices directory with the device name. On Windows serial ports it is customary to call "com" with the addition of a number, for example: com1, com2, etc. Similarly, parallel ports are named "lpt" with a number appended, for example: lpt1. You should link them directly to the appropriate Unix devices, such as /dev/ttyS0 and /dev/lp0. For example, to configure one serial and one parallel port, run the following commands.

ln -s /dev/ttyS0 com1
ln -s /dev/lp0 lpt1

3.3.2. Shared Networks

Windows network resources can be scheduled in the unc/ directory, so that everything that should be in \\myserver\some\file will be in ~/.wine/dosdevices/unc/myserver/some/file/. For example, if you are using Samba to mount \\myserver\some on /mnt/smb/myserver/some then you would run the command:

ln -s /mnt/smb/myserver/some unc/myserver/some

to make them available in Wine (just remember to create the unc directory if it doesn't exist).

3.3.3. Fonts

Font customization, once a major problem, is now much easier to solve. If you have a set of TrueType fonts in Windows, then you just need to copy all the .ttf files to c:\windows\fonts.

3.3.4. Printers

Wine can talk directly to your CUPS (Unix Printing System) printing system and find printers available to the system. Setting up printers in Wine comes down to making sure CUPS works. However, Wine needs the lpr command (from CUPS) when it needs to print a document.

If you are not using CUPS, then the old BSD-Printing printing system is used:

All printers in /etc/printcap are automatically installed by Wine.

Wine requires a PPD-File for each of the printers (generic.ppd is included with Wine)

The lpr command is run to print the document.

3.3.5. Scanners

On Windows, scanners use the TWAIN API to access their respective devices. The built-in Wine TWAIN DLL simply forwards these requests to the Linux SANE libraries. So, in order to use the scanner under Wine, you first need to make sure that you can access it through SANE. After that, you need to make sure you have xscanimage usable. xscanimage is currently included in the sane-frontends package, but may not be installed on your distribution. In general, access to scanners today is replete with problems. If you happen to get the scanner working, please update this section of the Wine User Guide with details on how to use SANE with Wine.

3.3.6. ODBC databases

The Open DataBase Connectivity interface system (an open interface for interacting with databases in Windows), as well as the printing system, is designed to switch to a Unix system on high level. Instead of checking to see if Windows code works under Wine, it uses a suitable Unix ODBC provider such as UnixODBC. Thus, if you have configured Wine to use the built-in odbc32.dll, this Wine DLL will interact with your Unix ODBC package, allowing it to work. If you have configured Wine to use native (Windows) odbc32.dll, it will try to use native ODBC32 drivers and so on.

3.3.6.1. Setting up ODBC on Unix

The first step in using the Unix ODBC system with Wine is, of course, configuring the Unix ODBC system itself. This may require you to install sources or RPM packages. There are several Unix ODBC systems; the one the author is used to is called unixODBC (with the IBM DB2 driver). There is also an ODBC-ODBC bridge that can be used to access the database Microsoft Access. Typically, such systems include a tool, such as isql, that will allow you to access data from command line, so that you can verify that the system is working.

The second step is to switch the Unix ODBC library to Wine's built-in odbc32 DLL. The built-in odbc32 (currently) looks in the environment variable LIB_ODBC_DRIVER_MANAGER for the name of the ODBC library. For example, the author has this line in his .bashrc file:

export LIB_ODBC_DRIVER_MANAGER=/usr/lib/libodbc.so.1.0.0

If such environment variable is not installed then it looks for a library called libodbc.so and you can symlink it to equate it with your own library. For example, as root, you can run the commands:

# ln -s libodbc.so.1.0.0 /usr/lib/libodbc.so
# /sbin/ldconfig

The last configuration step is to make sure Wine is set to run the built-in version of the odbc32.dll file by changing the DLL configuration. This built-in DLL usually acts as a stub between the calling program and the Unix ODBC library.

If you're having trouble, you can use the WINEDEBUG=+odbc32 command before starting Wine to see what's going on. One warning. Some programs cheat a little and bypass the ODBC library. For example, the Crystal Reports engine goes to the registry to check the DSN (Data Source Name). The way to deal with this is described on the unixODBC site, which has a section on using unixODBC with Wine.

3.3.6.2. Usage ODBC drivers Windows

It is said that "native" ODBC drivers work with many types of databases, including MSSQL and Oracle. In fact, only MSSQL can somehow be accessed from Linux through the Winelib application. Instead of just copying DLL files, most ODBC drivers require you to use Windows Installer like to set things up properly, like registry keys.

To set up MSSQL support, you must first download and run the mdac_typ.exe installer from microsoft.com. To form ODBC links, you must then run CLICONFG.EXE and ODBCAD32.EXE under Wine. You can find them in the windows\system directory after mdac_typ has finished running. Compare the output of these programs with the output on the real Windows machine. Some things, such as protocols, may not be present as they may be installed with operating system. If this is the case, then you can copy what is missing from your existing Windows installation, along with any necessary values ​​in the registry. Real Windows installation, prepared to work with Wine, should work on its own no worse than before preparation. Here is a list of databases that have successfully passed testing with Wine.

After you have installed latest version environment for Windows startup WINE programs (how to do this is written), it also needs to be adjusted a little so that programs and games run normally. Sometimes you have to produce for each program own settings, but there are also common actions for all programs. However initial setup WINE is not difficult at all.

Using Winetricks.

Winetricks is a script created so that you can quickly download and install various libraries necessary for some windows programs to work in the wine environment.

Installing it is simple. Start a terminal emulator and create a folder in your home directory like winetricks:

mkdir winetricks

then go to this folder and download the winetricks script from the internet:

cd winetricks wget http://winetricks.org/winetricks

After the script has downloaded, make it executable:

Chmod a+rwx winetricks

And finally run winetricks:

The points:

• Install an App - installation various windows applications.
• Install a benchmark - install a choice of several popular programs for evaluating performance.
• Install a game - allows you to download and install demo versions of some games.
• Select the Default prefix - allows you to install various libraries and fonts.
• Enable Silent Install - enables / disables the "silent" installation. Silent installation does not display installation windows.
• Show brolen Apps - turns on / off the display of "bad" applications (protected by DRM, etc.)

Installing Fonts and DLLs in Wine

First of all, you need to install standard fonts necessary for most windows programs and games. To do this, select the item Select Default prefix

When you first start this menu item, you will be asked if you agree to collect debugging information in order to improve the program:

Feel free to say no if you don't want to help develop the winetricks program.

Without further ado, we select the first item allfonts - this will install all available fonts, but you will need to download 132 megabytes of data from the Internet. Therefore, be patient and have unlimited internet.

If you have not enabled Silent Install, then the download and installation process will be displayed in the window:

Libraries are installed in the same way. Only in the previous step you need to select Install a Windows DLL about component.

Then note necessary components and press the OK button, as in the case of fonts.

For example, in this way you can install the "native" dircetx from Microsoft in the Wine environment, which is necessary for many games. Also here you can find other libraries necessary for games and applications. Necessity is determined in each individual case.

Setting up sound in Wine

For most games and better performance, I switch audio to use ALSA. this is done in the Wine settings (Applications\Wine\Wine Settings or run winecfg in a terminal). On the Audio tab, check the ALSA box.

Also, I've seen significant audio issues with applications running under wine with the PulseAudio sound server installed. By default, Ubuntu plays sound with it, so I remove it.

UPD 2016. In the latest distributions, the need to remove Pulseaudio has practically disappeared. All programs and games work correctly.

This completes the initial setup of WINE in Ubuntu. This is just a basic set of settings that I use to run Windows games on Linux under Wine. If you have something to add, welcome to the comments.

For the correct operation of most games, it is necessary to adjust the registry of our pseudo Windows. To do this, we will use the Winetricks utility, which was installed with Wine.
Do the following manipulations: Applications->Wine->Winetricks. In the opened window check: Select the default wineprefix . OK

In the next window, mark: Change Settings. OK

You will have access to the main settings of your Ubuntu-Wine-Windows bundle.

Check the following options here:
1. DirectDrawRender(ddr) opengl
2. Direct3D Multisampling enabled
3. OffscreenRenderingMode(orm) fbo
4. PixelShaderMode(psm) enabled
5. Render TargetLockMode(rtlm) auto
6. UseGLSL(glsl) enabled (default)
7. VertexShaders(vsm) hardware
8. VideoMemorySize 1024 (select the RAM value of your video card)
9. MouseWarpOverride(mwo) enabled (force)
We confirm our changes - OK.
All registry settings of our system are stored in text files(system.reg; user.reg; userdef.reg) located at Home\Username\.Wine and can be edited in any text editor (try this in real Windows?!). For editing, you can use the more familiar for windows way- registry editor: type in wine terminal regedit OK

the editing program will start

As you can see, everything we did in Winetricks is reflected in the registry settings.

Wine (WINE Is Not an Emulator) - special program, a compatibility layer, for running Win32 applications on UNIX-like systems. Simply put, this thing allows you to run Windows programs and games in your cozy Linux :).
The program is being actively developed, but so far, unfortunately, not all applications work correctly in it (and some do not work at all). With games, it's also sad - full support There is no DirectX 10 and 11, only 9 and younger. (Support for DirectX 10 is being actively improved in the latest test builds). But nevertheless, there are a lot of games on DirectX 9. In this article, we will install and configure Wine, and install the PlayOnLinux application, which is very useful for gaming. The installation will depend on your distribution, but the program setup itself is exactly the same in the vast majority of distributions. There are two branches of Wine - stable and testing. In most cases, it is recommended to use the test one, as the program is actively developing and improving. For now, let's consider installing the stable version (the examples are for the command line, but you can use graphical utilities like Ubuntu Software Center or Yast2 in OpenSUSE):

For Debian/Ubuntu/Mint:

sudo apt-get install wine winetricks

For OpenSUSE:

sudo zypper ar -r http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_13.1/Emulators:Wine.repo
sudo zypper in wine

sudo yum install wine
cd /tmp
wget http://www.kegel.com/wine/winetricks
chmod +x winetricks

Note. If you have a 64-bit system, then for the correct operation of 32-bit programs (and most games are like that), you need to configure Wine for a 32-bit prefix. For this we drive:

WINEARCH=win32 WINEPREFIX=~/.wine winecfg

The settings window will open. You can leave everything as it is.

Now we need to install a set of system libraries for our Windows applications to work. In the program menu, find and run Winetricks(or from the terminal with the command winetricks). In the first window choose ---Select the default wineprefix--- earn OK. In the second ---install a Windows DLL or component---OK

Remember:
It will be necessary to mark with dots, as in the list. It is better to install not all at once, but several pieces at a time. I will separate them for convenience. Do not go far when installing, you need to agree with license agreements and others. Error windows will pop up, click OK. Let's start.

directx9 d3dx9 d3dx9_26 d3dx9_28 d3dx9_31 d3dx9_35 d3dx9_36 d3dx9_42 d3dx9_43 d3dx10 d3dx11_42 d3dx11_43

dotnet20

dotnet30(errors will appear and a window will open in the file manager and in the browser, download from the second link and move to this window file manager. We type in the console winetricks and select dontnet30 again. Before doing this, you need to check the Wine Setup so that it is Windows version XP or Vista.

dxdiagn, gecko120, gfw, mfc40, mfc42, msasn1, msxml6, gdiplus , physx, quartz

vb5run, vb6run, vcrun2003, vcrun2005, vcrun2008, vcrun6, vcrun6sp6

wmp10, wsh56vb, wsh57, xact, xact_jun2010, xinput

Install fonts. Choose Install a Font and indicate

corefonts , fontfix

Registry setting

We open Change Settings and celebrate

1. DirectDrawRender(ddr) -- opengl
2. Multisampling Direct3D -- enabled
3.OffscreenRenderingMode(orm) -- fbo
4. PixelShaderMode(psm) -- enabled
5. Render TargetLockMode(rtlm) -- auto
6. UseGLSL(glsl) -- enabled (default)(For Nvidia graphics cards it is recommended to leave disabled. This can significantly improve the performance of some games).
7.VertexShaders(vsm)--hardware
8. VideoMemorySize 1024 (select the RAM value of your video card)
9. MouseWarpOverride(mwo) -- enabled (force)

We confirm our changes - OK.

That's actually all. Now some notes on installing software and games. Firstly, in no case do not install additional software that the program offers (all sorts of directixes, visual c ++, and so on). Check carefully and, if necessary, uncheck the box. Secondly, at the end of the installation, uncheck "Run the program".

Now for the test version. There is a special repository for Ubuntu/Mint. To connect it and install a test version of Wine, enter in the terminal:

sudo add-apt-repository ppa:ubuntu-wine/ppa
sudo apt-get update
sudo apt install wine 1.7 winetricks

In some distributions (for example, Debian), to install a test version, you need to build it from source code. But this is already beyond the scope of this article. Or you can install , which is also a test but has a few extra features.

P.S. for those who like to see once than read a hundred times - a small video tutorial on installing a test version of Wine on Ubuntu:

Wine (WINE Is Not an Emulator) is a special program, a compatibility layer, for running Win32 applications on UNIX-like systems. Simply put, this thing allows you to run Windows programs and games in your cozy Linux :).
The program is being actively developed, but so far, unfortunately, not all applications work correctly in it (and some do not work at all). So far, it’s also sad with games - there is no full support for DirectX 10 and 11, only 9 and younger. (Support for DirectX 10 is being actively improved in the latest test builds). But nevertheless, there are a lot of games on DirectX 9. In this article, we will install and configure Wine, and install the PlayOnLinux application, which is very useful for gaming. The installation will depend on your distribution, but the program setup itself is exactly the same in the vast majority of distributions. There are two branches of Wine - stable and testing. In most cases, it is recommended to use the test one, as the program is actively developing and improving. For now, let's consider installing the stable version (the examples are for the command line, but you can use graphical utilities like Ubuntu Software Center or Yast2 in OpenSUSE):

For Debian/Ubuntu/Mint:

sudo apt-get install wine winetricks

For OpenSUSE:

sudo zypper ar -r http://download.opensuse.org/repositories/Emulators:/Wine/openSUSE_13.1/Emulators:Wine.repo
sudo zypper in wine

sudo yum install wine
cd /tmp
wget http://www.kegel.com/wine/winetricks
chmod +x winetricks

Note. If you have a 64-bit system, then for the correct operation of 32-bit programs (and most games are like that), you need to configure Wine for a 32-bit prefix. For this we drive:

WINEARCH=win32 WINEPREFIX=~/.wine winecfg

The settings window will open. You can leave everything as it is.

Now we need to install a set of system libraries for our Windows applications to work. In the program menu, find and run Winetricks(or from the terminal with the command winetricks). In the first window choose ---Select the default wineprefix--- earn OK. In the second ---install a Windows DLL or component---OK

Remember:
It will be necessary to mark with dots, as in the list. It is better to install not all at once, but several pieces at a time. I will separate them for convenience. Do not go too far when installing, you need to agree to license agreements and other things. Error windows will pop up, click OK. Let's start.

directx9 d3dx9 d3dx9_26 d3dx9_28 d3dx9_31 d3dx9_35 d3dx9_36 d3dx9_42 d3dx9_43 d3dx10 d3dx11_42 d3dx11_43

dotnet20

dotnet30(errors will appear and a window will open in the file manager and in the browser, download from the second link and move it to this file manager window. We type in the console winetricks and select dontnet30 again. Before doing this, you need to check the Wine Setup so that the version is Windows XP or Vista.

dxdiagn, gecko120, gfw, mfc40, mfc42, msasn1, msxml6, gdiplus , physx, quartz

vb5run, vb6run, vcrun2003, vcrun2005, vcrun2008, vcrun6, vcrun6sp6

wmp10, wsh56vb, wsh57, xact, xact_jun2010, xinput

Install fonts. Choose Install a Font and indicate

corefonts , fontfix

Registry setting

We open Change Settings and celebrate

1. DirectDrawRender(ddr) -- opengl
2. Multisampling Direct3D -- enabled
3.OffscreenRenderingMode(orm) -- fbo
4. PixelShaderMode(psm) -- enabled
5. Render TargetLockMode(rtlm) -- auto
6. UseGLSL(glsl) -- enabled (default) (It is recommended to leave disabled for Nvidia graphics cards. This can significantly increase the performance of some games).
7.VertexShaders(vsm)--hardware
8. VideoMemorySize 1024 (select the RAM value of your video card)
9. MouseWarpOverride(mwo) -- enabled (force)

We confirm our changes - OK.

That's actually all. Now some notes on installing software and games. Firstly, in no case do not install additional software that the program offers (all sorts of directixes, visual c ++, and so on). Check carefully and, if necessary, uncheck the box. Secondly, at the end of the installation, uncheck "Run the program".

Now for the test version. There is a special repository for Ubuntu/Mint. To connect it and install a test version of Wine, enter in the terminal:

sudo add-apt-repository ppa:ubuntu-wine/ppa
sudo apt-get update
sudo apt install wine 1.7 winetricks

In some distributions (eg Debian), to install a test version, it must be built from source. But this is already beyond the scope of this article. Or you can install wine-staging , which is also a test but has a few extra features.

P.S. for those who like to see once than read a hundred times - a small video tutorial on installing a test version of Wine on Ubuntu: