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 all the output in a separate windows (this requires X11 to
32 for CUI programs will only provide very limited console support, and your
33 program might not function properly.
41 will simply print a small help message or its version respectively and exit.
43 The program name may be specified in DOS format
44 .RI ( C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE )
46 .RI ( /msdos/windows/sol.exe ).
47 You may pass arguments to the program being executed by adding them to the
48 end of the command line invoking
50 (such as: \fIwine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT\fR).
51 Note that you need to '\(rs' escape special characters (and spaces) when invoking Wine via
54 wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe
58 makes the environment variables of the shell from which it
59 is started accessible to the Windows/DOS processes started. So use the
60 appropriate syntax for your shell to enter environment variables you need.
63 If set, the contents of this variable is taken as the name of the directory where
64 Wine stores its data (the default is
66 This directory is also used to identify the socket which is used to
71 processes using the same
73 (i.e.: same user) share certain things like registry, shared memory,
77 to different values for different
79 processes, it is possible to run a number of truly independent
84 Specifies the path and name of the
86 binary. If not set, Wine will try to load
87 .IR @bindir@/wineserver ,
88 and if this doesn't exist it will then look for a file named
89 "wineserver" in the path and in a few other likely locations.
92 Specifies the path and name of the
94 binary to use to launch new Windows processes. If not set, Wine will
97 and if this doesn't exist it will then look for a file named "wine" in
98 the path and in a few other likely locations.
101 Turns debugging messages on or off. The syntax of the variable is
103 .RI [ class ][\fB+\fR|\fB-\fR] channel [,[ class2 ][\fB+\fR|\fB-\fR] channel2 ]
107 is optional and can be one of the following:
115 is not specified, all debugging messages for the specified
116 channel are turned on. Each channel will print messages about a particular
118 The following character can be either \fB+\fR or \fB-\fR to switch the specified
119 channel on or off respectively. If there is no
121 part before it, a leading \fB+\fR\fR can be omitted. Note that spaces are not
122 allowed anywhere in the string.
127 will turn on all warning messages (recommended for debugging).
130 WINEDEBUG=warn+dll,+heap
131 will turn on DLL warning messages and all heap messages.
134 WINEDEBUG=fixme-all,warn+cursor,+relay
135 will turn off all FIXME messages, turn on cursor warning messages, and turn
136 on all relay messages (API calls).
140 will turn on all relay messages. For more control on including or excluding
141 functions and dlls from the relay trace, look into the
142 .B HKEY_CURRENT_USER\\\\Software\\\\Wine\\\\Debug
145 For more information on debugging messages, see the
147 chapter of the Wine User Guide.
151 Specifies the path(s) in which to search for builtin dlls and Winelib
152 applications. This is a list of directories separated by ":". In
153 addition to any directory specified in
155 Wine will also look in
159 Defines the override type and load order of dlls used in the loading
160 process for any dll. There are currently two types of libraries that can be loaded
161 into a process address space: native windows dlls
162 .RI ( native ") and Wine internal dlls (" builtin ).
163 The type may be abbreviated with the first letter of the type
165 The library may also be disabled (''). Each sequence of orders must be separated by commas.
168 Each dll may have its own specific load order. The load order
169 determines which version of the dll is attempted to be loaded into the
170 address space. If the first fails, then the next is tried and so
171 on. Multiple libraries with the same load order can be separated with
172 commas. It is also possible to use specify different loadorders for
173 different libraries by separating the entries by ";".
175 The load order for a 16-bit dll is always defined by the load order of
176 the 32-bit dll that contains it (which can be identified by looking at
177 the symbolic link of the 16-bit .dll.so file). For instance if
178 \fIole32.dll\fR is configured as builtin, \fIstorage.dll\fR will be loaded as
179 builtin too, since the 32-bit \fIole32.dll\fR contains the 16-bit
184 WINEDLLOVERRIDES="comdlg32,shell32=n,b"
186 Try to load comdlg32 and shell32 as native windows dll first and try
187 the builtin version if the native load fails.
189 WINEDLLOVERRIDES="comdlg32,shell32=n;c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b"
191 Try to load the libraries comdlg32 and shell32 as native windows dlls. Furthermore, if
192 an application request to load \fIc:\(rsfoo\(rsbar\(rsbaz.dll\fR load the builtin library \fIbaz\fR.
194 WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32="
196 Try to load comdlg32 as builtin first and try the native version if
197 the builtin load fails; load shell32 always as builtin and comctl32
198 always as native; oleaut32 will be disabled.
202 Specifies the Windows architecture to support. It can be set either to
204 (support only 32-bit applications), or to
206 (support both 64-bit applications and 32-bit ones in WoW64 mode).
208 The architecture supported by a given Wine prefix is set at prefix
209 creation time and cannot be changed afterwards. When running with an
210 existing prefix, Wine will refuse to start if
212 doesn't match the prefix architecture.
215 Specifies the X11 display to use.
217 OSS sound driver configuration variables:
220 Set the device for audio input / output. Default
224 Set the device for mixer controls. Default
228 Set the MIDI (sequencer) device. Default
233 The Wine program loader.
235 .I @bindir@/wineconsole
236 The Wine program loader for CUI (console) applications.
238 .I @bindir@/wineserver
245 Directory containing Wine shared libraries
247 .I $WINEPREFIX/dosdevices
248 Directory containing the DOS device mappings. Each file in that
249 directory is a symlink to the Unix device file implementing a given
250 device. For instance, if COM1 is mapped to \fI/dev/ttyS0\fR you'd have a
251 symlink of the form \fI$WINEPREFIX/dosdevices/com1\fR -> \fI/dev/ttyS0\fR.
253 DOS drives are also specified with symlinks; for instance if drive D:
254 corresponds to the CDROM mounted at \fI/mnt/cdrom\fR, you'd have a symlink
255 \fI$WINEPREFIX/dosdevices/d:\fR -> \fI/mnt/cdrom\fR. The Unix device corresponding
256 to a DOS drive can be specified the same way, except with '::' instead
257 of ':'. So for the previous example, if the CDROM device is mounted
258 from \fI/dev/hdc\fR, the corresponding symlink would be
259 \fI$WINEPREFIX/dosdevices/d::\fR -> \fI/dev/hdc\fR.
261 Wine is available thanks to the work of many developers. For a listing
262 of the authors, please see the file
264 in the top-level directory of the source distribution.
266 Wine can be distributed under the terms of the LGPL license. A copy of the
267 license is in the file
269 in the top-level directory of the source distribution.
272 A status report on many applications is available from the
273 .UR http://appdb.winehq.org
274 .B Wine Application Database
276 Please add entries to this list for applications you currently run, if
279 Bugs can be reported on the
280 .UR http://bugs.winehq.org
284 The most recent public version of
286 is available through WineHQ, the
287 .UR http://www.winehq.org/
288 .B Wine development headquarters
294 .UR http://www.winehq.org/help
295 .B Wine documentation and support