1 .TH WINE 1 "July 2013" "@PACKAGE_STRING@" "Windows On Unix"
3 wine \- run Windows programs on Unix
6 .IR "program " [ arguments ]
12 For instructions on passing arguments to Windows programs, please see the
15 section of the man page.
18 loads and runs the given program, which can be a DOS, Windows
19 3.x, Win32 or Win64 executable (on 64-bit systems).
21 For debugging wine, use
25 For running CUI executables (Windows console programs), use
29 This will display the output in a separate window. Not using
31 for CUI programs will only provide very limited console support, and your
32 program might not function properly.
40 will simply print a small help message or its version respectively and exit.
42 The program name may be specified in DOS format
43 .RI ( C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE )
45 .RI ( /msdos/windows/sol.exe ).
46 You may pass arguments to the program being executed by adding them to the
47 end of the command line invoking
49 (such as: \fIwine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT\fR).
50 Note that you need to '\(rs' escape special characters (and spaces) when invoking Wine via
53 wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe
55 It can also be one of the Windows executables shipped with Wine, in
56 which case specifying the full path is not mandatory, e.g. \fIwine
57 explorer\fR or \fIwine notepad\fR.
61 makes the environment variables of the shell from which it
62 is started accessible to the Windows/DOS processes started. So use the
63 appropriate syntax for your shell to enter environment variables you need.
66 If set, the contents of this variable is taken as the name of the directory where
67 Wine stores its data (the default is
69 This directory is also used to identify the socket which is used to
74 processes using the same
76 (i.e.: same user) share certain things like registry, shared memory,
80 to different values for different
82 processes, it is possible to run a number of truly independent
87 Specifies the path and name of the
89 binary. If not set, Wine will look for a file named "wineserver" in
90 the path and in a few other likely locations.
93 Specifies the path and name of the
95 binary to use to launch new Windows processes. If not set, Wine will
96 look for a file named "wine" in the path and in a few other likely
100 Turns debugging messages on or off. The syntax of the variable is
102 .RI [ class ][\fB+\fR|\fB-\fR] channel [,[ class2 ][\fB+\fR|\fB-\fR] channel2 ]
106 is optional and can be one of the following:
114 is not specified, all debugging messages for the specified
115 channel are turned on. Each channel will print messages about a particular
117 The following character can be either \fB+\fR or \fB-\fR to switch the specified
118 channel on or off respectively. If there is no
120 part before it, a leading \fB+\fR\fR can be omitted. Note that spaces are not
121 allowed anywhere in the string.
126 will turn on all warning messages (recommended for debugging).
129 WINEDEBUG=warn+dll,+heap
130 will turn on DLL warning messages and all heap messages.
133 WINEDEBUG=fixme-all,warn+cursor,+relay
134 will turn off all FIXME messages, turn on cursor warning messages, and turn
135 on all relay messages (API calls).
139 will turn on all relay messages. For more control on including or excluding
140 functions and dlls from the relay trace, look into the
141 .B HKEY_CURRENT_USER\\\\Software\\\\Wine\\\\Debug
144 For more information on debugging messages, see the
146 chapter of the Wine User Guide.
150 Specifies the path(s) in which to search for builtin dlls and Winelib
151 applications. This is a list of directories separated by ":". In
152 addition to any directory specified in
154 Wine will also look in the installation directory.
157 Defines the override type and load order of dlls used in the loading
158 process for any dll. There are currently two types of libraries that can be loaded
159 into a process address space: native windows dlls
160 .RI ( native ") and Wine internal dlls (" builtin ).
161 The type may be abbreviated with the first letter of the type
163 The library may also be disabled (''). Each sequence of orders must be separated by commas.
166 Each dll may have its own specific load order. The load order
167 determines which version of the dll is attempted to be loaded into the
168 address space. If the first fails, then the next is tried and so
169 on. Multiple libraries with the same load order can be separated with
170 commas. It is also possible to use specify different loadorders for
171 different libraries by separating the entries by ";".
173 The load order for a 16-bit dll is always defined by the load order of
174 the 32-bit dll that contains it (which can be identified by looking at
175 the symbolic link of the 16-bit .dll.so file). For instance if
176 \fIole32.dll\fR is configured as builtin, \fIstorage.dll\fR will be loaded as
177 builtin too, since the 32-bit \fIole32.dll\fR contains the 16-bit
182 WINEDLLOVERRIDES="comdlg32,shell32=n,b"
184 Try to load comdlg32 and shell32 as native windows dll first and try
185 the builtin version if the native load fails.
187 WINEDLLOVERRIDES="comdlg32,shell32=n;c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b"
189 Try to load the libraries comdlg32 and shell32 as native windows dlls. Furthermore, if
190 an application request to load \fIc:\(rsfoo\(rsbar\(rsbaz.dll\fR load the builtin library \fIbaz\fR.
192 WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32="
194 Try to load comdlg32 as builtin first and try the native version if
195 the builtin load fails; load shell32 always as builtin and comctl32
196 always as native; oleaut32 will be disabled.
200 Specifies additional path(s) to be prepended to the default Windows
202 environment variable. This is a list of Windows-style directories
206 For a permanent alternative, edit (create if needed) the
209 .B HKEY_CURRENT_USER\\\\Environment
214 Specifies the Windows architecture to support. It can be set either to
216 (support only 32-bit applications), or to
218 (support both 64-bit applications and 32-bit ones in WoW64 mode).
220 The architecture supported by a given Wine prefix is set at prefix
221 creation time and cannot be changed afterwards. When running with an
222 existing prefix, Wine will refuse to start if
224 doesn't match the prefix architecture.
227 Specifies Direct3D configuration options. It can be used instead of
229 .B HKEY_CURRENT_USER\\\\Software\\\\Wine\\\\Direct3D
230 registry key. The value is a comma- or semicolon-separated list
231 of key-value pairs. For example:
233 WINE_D3D_CONFIG="renderer=vulkan;VideoPciVendorID=0xc0de"
235 If an individual setting is specified in both
236 the environment variable and the registry, the former takes precedence.
239 Specifies the X11 display to use.
241 OSS sound driver configuration variables:
244 Set the device for audio input / output. Default
248 Set the device for mixer controls. Default
252 Set the MIDI (sequencer) device. Default
257 The Wine program loader.
260 The Wine program loader for CUI (console) applications.
268 .I $WINEPREFIX/dosdevices
269 Directory containing the DOS device mappings. Each file in that
270 directory is a symlink to the Unix device file implementing a given
271 device. For instance, if COM1 is mapped to \fI/dev/ttyS0\fR you'd have a
272 symlink of the form \fI$WINEPREFIX/dosdevices/com1\fR -> \fI/dev/ttyS0\fR.
274 DOS drives are also specified with symlinks; for instance if drive D:
275 corresponds to the CDROM mounted at \fI/mnt/cdrom\fR, you'd have a symlink
276 \fI$WINEPREFIX/dosdevices/d:\fR -> \fI/mnt/cdrom\fR. The Unix device corresponding
277 to a DOS drive can be specified the same way, except with '::' instead
278 of ':'. So for the previous example, if the CDROM device is mounted
279 from \fI/dev/hdc\fR, the corresponding symlink would be
280 \fI$WINEPREFIX/dosdevices/d::\fR -> \fI/dev/hdc\fR.
282 Wine is available thanks to the work of many developers. For a listing
283 of the authors, please see the file
285 in the top-level directory of the source distribution.
287 Wine can be distributed under the terms of the LGPL license. A copy of the
288 license is in the file
290 in the top-level directory of the source distribution.
293 A status report on many applications is available from the
294 .UR https://appdb.winehq.org
295 .B Wine Application Database
297 Please add entries to this list for applications you currently run, if
300 Bugs can be reported on the
301 .UR https://bugs.winehq.org
305 The most recent public version of
307 is available through WineHQ, the
308 .UR https://www.winehq.org/
309 .B Wine development headquarters
315 .UR https://www.winehq.org/help
316 .B Wine documentation and support