Click OK, the following window appears:


Click OK again, a window opens with a choice of components and DLLs to install, check the boxes that I indicated:
d3dx9, d3dx9_26, d3dx9_28, d3dx9_31, d3dx9_35, d3dx9_36, d3dx9_42, d3dx10, d3dx11_42, d3dx11_43, d3dxof, devenum, dinput8, dirac, directmusic, directplay, directx9, dmsynth, do tnet11, dotnet20, dotnet30, dxdiagn, gecko110, gecko120, gfw, mfc40, mfc42, msasn1, msxml6, physx, quartz, vcrun2003, vcrun2005, vcrun2008, vcrun6, vcrun6sp6, wmp10, wsh56vb, wsh57, xact, xact_jun2010, xinput, adobeair.
OK. Be patient, wait until it's all installed, sometimes you will need to confirm the license agreement, so don't go too far :)
It would be better, I would recommend that you install not everything at once, but two or three components at a time - in this case, if some kind of failure occurs (God forbid), you will at least know on which component it happened.

For extreme sports enthusiasts and the especially lazy, there is another way:

!!!I advise you, before you start experimenting with games, to create backup copy folders.Wine: " Go->Home folder->Ctrl+H" and copy the entire .Wine folder to another location. It does not weigh much (about 1GB), with the installed components, and if your working .Wine crashes, you can replace it!!!

Recently Wine has changed for the better, Mono has been improved and now it works well.

I hope you will install Wine x64 without instructions, via Add or Remove Programs.

Wine transition from 64 to 32

After installation, you need to find the Wine Settings icon in the application or run the command in the console

Wine will offer to install the Mono package - we agree (OK), after the Gecko x64 and Gecko x32 package - we agree (OK), the Wine settings window will open, you can close it - it is not needed yet. You can configure everything through the graphical interface, but it takes a long time and if there is a failure, you won’t understand where it happened. Let's install via the console (terminal).
Let's install the fonts.

Winetricks corefonts

The first long one command (copied, pasted into the console, press Enter). It will download the necessary libraries, installers will appear, we agree to the license agreements and install. If a failure occurs (error mfc40) or the installation freezes, press Ctrl+C in the console (stop the process) and run this command again. Everything should be installed (checked). The speed of installation depends on your Internet connection speed.

Winetricks directx9 d3dx9 d3dx9_26 d3dx9_28 d3dx9_31 d3dx9_35 d3dx9_36 d3dx9_42 d3dx9_43 d3dx10 d3dx10_43 d3dx11_42 d3dx11_43 d3dxof devenum dinput8 dinput dirac directmusic direct play dmsynth dsound

Second team

Third

Fourth

Next, select change settings and set

Choose to run winecfg

Set the Wine version (from the drop-down list) to Windows-7 or higher.
On the tab - Libraries - in the existing values, look for - dinput - select and click.
Change, in the drop-down menu set - built-in, then third-party, repeat the action and with -dinput8- eliminates mouse problems in games.

If you have problems with sound, you can change the parameter - dsound - to built-in.

Profix wine

WINEARCH=win32 WINEPREFIX=~/prefix_name winecfg
WINEPREFIX=~/prefix_name C:/path/to/program

It turned out that not all the subtleties are there. Therefore, I wrote this post as an addition to that.

This post is mostly a free translation of. documentation, as well as several of our own and others’ tricks when working with Vine.
Most likely, this post will be of interest to beginners and ordinary GNU\Linux users. Nevertheless, good advice from experts will not be superfluous.

I think there is no point in explaining what a vine is. I just want to show you a few tricks when working with it.

Prefixes

That is, each prefix you create can be considered a separate wine - it is independent of other prefixes. Or, for even greater simplicity, treat each created prefix as a separate installation of Windows.

Now a little practice:
Now we will create a Gamez folder, in it we will create a lib prefix in which we will install several libraries. These libraries will still be useful later, so let them be cached.

Mkdir ./Gamez

env WINEPREFIX=$HOME/Gamez/lib winetricks directx9 vcrun2005 vcrun2008 vcrun6
env WINEPREFIX=$HOME/Gamez/lib wine winecfg

With the last command we again called up the wine configurator window. Just go to the Libraries tab and make sure everything is installed. After this do:

Wine winecfg - the wine configurator will open (not from the prefix), check the same tab. See! There are no libraries here. So he is safe and sound.

How to install several different versions of wine?

./configure prefix=/path/to/install/directory && make
sudo make install

AppDB

Cleaning up your home directory

Replace the standard path to my documents with the desired location for storing saves. For example, this path leads to the game folder.

Using the latest versions of wine

Sudo add-apt-repository ppa:ubuntu-wine/ppa
sudo apt-get update

After running these commands, look for the latest version of wine in synaptic.

Installing winetricks

Wget winetricks.org/winetricks
sudo cp winetricks /usr/bin
sudo chmod +x /usr/bin/winetricks

How to install MSI file?

Alternative way: wine start whatever.msi

The file foo.exe is not marked as executable… - What does this mean?

Chmod a+x ./patch/you/exe.file

If the file is on disk, then this command should help:

Mount -o remount,mode=0777,exec /media/cdrom

How to output debug contents to a separate file?

How to disable the "crash" dialog?

After launching the application/game, wine complains and does not launch anything. What to do?

MFC40.DLL: Install mfc40 (Microsoft Foundation Classes from Visual C++ 4) via winetricks.
MFC42.DLL, MSVCP60.DLL: Install vcrun6 via winetricks (MS Visual C++ 6 sp4 libraries: mfc42, msvcp60, msvcrt).
MFC71.DLL, MSVCP71.DLL: Install vcrun2003 via winetricks (MS Visual C++ 2003 libraries: mfc71,msvcp71,msvcr71).
MFC80.DLL, MSVCP80.DLL: Install vcrun2005 via winetricks (MS Visual C++ 2005 libraries: mfc80,msvcp80,msvcr80).
MFC90.DLL, MSVCP90.DLL: Install vcrun2008 via winetricks (MS Visual C++ 2008 libraries: mfc90,msvcp90,msvcr90).
MDAC: Install mdac27 (MS MDAC 2.7) via winetricks.

My app is working but the text fields are behaving strangely

After launch, fixme messages are displayed in the console. What is this?

What to do if the application requires the .NET framework?

The game I'm trying to install is protected from distribution, is it possible to install it?

What to do if the application requires IE?

If this does not help, try changing the windows version to win2k and installing ie6, ie7 or ie8 via winetricks.

How to enable font smoothing in wine?

Screen resolution is not restored after exiting the game

How to get into the wine registry?

Does wine require a separate driver installation?

Is it safe to run wine as root?

If this has already happened, change the owner of the ~./wine directory.

CD ~
sudo chown -R $USER:$USER .wine

Safety precautions when using wine

• Never run programs from suspicious sites
• Never use root user to run applications!
• Use a virus scanner for startup applications, such as ClamAV. Or at least check the exe files on virustotal
• Try removing the wine drive Z:, which points to the root directory by default. As a workaround, run programs from the ~/.wine/drive_c directory.
• Use virtual machine to launch and scan suspicious applications.

The file.xsession-errors clogs up the entire disk space with garbage!!! What to do? (recipe from --=XliN=--)

Add it to startup, and install the following package (it is necessary for the script to work).
apt-get install inotify-tools

Making a “sandbox” for wine (recipe from drBatty)

For most games to work correctly, it is necessary to configure the registry of our pseudo Windows. To do this, we will use the Winetricks utility, which was installed along with Wine.
Perform the following manipulations: Applications->Wine->Winetricks. In the window that opens, check: Select the default wineprefix. OK

In the next window, mark: Change Settings. OK

You will have access to the basic settings of your Ubuntu-Wine-Windows combination.

Here check the following options:
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 the address - Home\Username\.Wine and they can be edited in any text editor (try this in real Windows?! ). To edit, you can also use the more familiar Windows method - the registry editor: type wine regedit OK in the terminal

the editing program will start

As you can see, everything we did in Winetricks was displayed in the registry settings.

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

Chapter 3: Setting up Wine (Configuration)

3.1. Winecfg program

Winecfg must 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 being able to launch applications. The remaining settings are used to make the Wine program itself work the way you would like it to.

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

3.1.1. Application Settings

Inside the tab, you will notice a line called Default Settings. If you select this line, then all applications will run on the default version of Windows. It is better to configure the problematic application separately from the default settings. For this:

1. Click the Add application button.
2. Find the required .exe file.
3. Once you add this application, you will be able to choose Windows version, which Wine will emulate specifically for this application.

3.1.2. Setting up Libraries

3.1.2.1. DLL replacement

With this in mind, if you have already copied the DLL, you need to tell Wine that you can use it. You can configure Wine to choose between a native and built-in DLL at two different levels. If you have Default Settings installed 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 this application and selecting it in the Applications tab.

To add an override FOO.DLL file, enter "FOO" in the field labeled New override for library and click the Add button. To change the behavior of a DLL, you need to select it from the Existing overrides: field and click Edit. By default, the “native” Windows will be loaded first, the second will be the built-in Wine one ( Native then Built). You can also choose native only, built-in only, or disable both.

3.1.2.2. Regarding system DLLs

Sometimes applications try to figure out the version of a resource directly from a physical file (say, to find out the version of DirectX). Dummy files will not help in this case. In this case, you need to install files with the full version code. This problem has already been resolved for many files. If not, then again you 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 that contain Windows DLL archives, which you can find using search engines. Please follow the licensing rules for the DLL files you select; some are distributed without restrictions, some are not.

3.1.2.3 Missing DLLs

1.The directory from where the program was launched.

2.Current (working) directory.

3.Windows system folder.

4 Windows folder.

5 PATH variable directories.

In short: either place the DLL you need in your program's directory (can 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 the Win9x API's (sometimes resulting in poorer compatibility with NT DLLs than even with non-Windows schemes!).

3.1.3 Graphics Settings

The first few settings are mostly related to gaming and are self-explanatory. It is possible to prevent the mouse cursor from leaving the DirectX program window (i.e. the game). By default this option is enabled. There are many reasons to do this, not the least of which is the fact that it's easier to play when the cursor is contained in a smaller area. Another reason to enable this option is better control over the mouse. Wine distorts mouse position to simulate Windows operation. Likewise, "desktop double buffering" produces smoother screen updates, making games look better; again, the option is enabled by default. This is a trade-off for 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 glitchy games that change screen resolution (possibly unsuccessfully). Confining them to a window may result in greater control over them, perhaps at the cost of less convenience. You can try sizes 640x480 (default) or 800x600.

Lastly, you can change some Direct3D settings. For the most part, these settings are determined automatically, but you can force them to behave in certain ways. Some games try to check the system to see if it supports certain features. By turning off this behavior, Wine will not report its ability to render an image in a certain way. This may result in increased game speed at the expense of graphics quality; or maybe the game won't work at all.

3.1.4. Drive settings

Partitioning disks in Wine is relatively simple. In Winecfg, in the Drives tab, you see buttons for adding and removing the required drives. When you select "add drive" a new row is created and the default drive naming scheme appears. You can change the address it points to this disk 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 that you try the automatic method before attempting to partition the drives manually. By simply clicking the Autodetect button you force Wine to search for drives on your system.

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

$ 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 disk, such as a CD-ROM, simply create another link pointing to it:

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

Please note that the links use the DOS drive naming system - a letter followed by a colon, for example, "a:". So if the link to your c: drive points to ~/.wine/drive_c, you can understand links to c:\windows\system32 to mean ~/.wine/drive_c/windows/system32.

3.1.5 Audio settings

DirectSound settings are mainly used in games. You can choose how much hardware acceleration you want, but "Full" will work just fine for most.

3.1.6 Desktop layout

1. Download the Windows XP theme. Make sure there is a .msstyles file.

2. Create a chain of directories in your fake Windows disk:

$ 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 a new theme.

3.2 Using the Registry and Regedit

The very fact that Wine uses the Registry to save settings is debatable. Some argue that it's too similar to Windows. To counter this, there are a few things to consider. Firstly, it is impossible to do without the Registry simply because applications “expect” to save 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 the same thing as the Win32 API, which is what Wine does. Finally, unlike Windows, the Wine Registry is written in plain text and can be modified in any text editor. And so, although most normal system administrators (and Wine developers) swear like mad at the confusing Windows Registry, it is still necessary for Wine to support it somehow.

3.2.1 Registry structure

HKEY_LOCAL_MACHINE

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

This fundamental root key (in win9x it is stored in a hidden file user.dat) 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, that is, to your personal configuration.

3.2.2. Wine Registry Files

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

3.2.3. How to use Regedit

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 place 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 thing is to right-click on the key or value.

Of particular interest to Wine users are the settings in HKEY_CURRENT_USER\Software\Wine. Most of the settings you made using winecfg are written to this section of the registry.

3.2.4. System Administrator Tips

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 thing 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 disk layout. If you share the system.reg file, you must ensure that the registry settings are compatible with the drive layouts in each user's ~/.wine/dosdevices files. Make it a rule that the more closely 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 the applications. Some applications require the ability to write certain settings to disk, especially Windows 95/98/ME applications.

Please note: if you installed Wine from source as root, the tools/wineinstall script you used during installation no longer works.

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

3.2.5. Complete list of registry keys

3.3. Other configurable aspects

3.3.1. Serial and parallel ports

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

3.3.2. Collaborative networks

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

3.3.4. Printers

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

All printers in the /etc/printcap file are automatically installed in Wine.

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

To print a document, run the lpr command.

3.3.5. Scanners

3.3.6. ODBC Databases

3.3.6.1. Setting up ODBC on Unix

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

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

If so environment variable is not installed, then it looks for a library called libodbc.so, and you can set a symbolic link to equate it to 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 final configuration step is to ensure that Wine is set to run the built-in version of the odbc32.dll file by changing the DLL configuration. This built-in DLL typically 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 website, which has a section on using unixODBC with Wine.

3.3.6.2. Using Windows ODBC Drivers

To establish MSSQL support, you must first download and run the mdac_typ.exe installer from microsoft.com. To form ODBC connections, 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 a real Windows machine. Some things, such as protocols, may be missing because they may be installed with operating system. If this is the case, then you can copy the missing items from your existing Windows installation along with any necessary registry values. A 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 tested with Wine.