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
56 It can also be one of the Windows executables shipped with Wine, in
57 which case specifying the full path is not mandatory, e.g. \fIwine
58 explorer\fR or \fIwine notepad\fR.
62 makes the environment variables of the shell from which it
63 is started accessible to the Windows/DOS processes started. So use the
64 appropriate syntax for your shell to enter environment variables you need.
67 If set, the contents of this variable is taken as the name of the directory where
68 Wine stores its data (the default is
70 This directory is also used to identify the socket which is used to
75 processes using the same
77 (i.e.: same user) share certain things like registry, shared memory,
81 to different values for different
83 processes, it is possible to run a number of truly independent
88 Specifies the path and name of the
90 binary. If not set, Wine will try to load
91 .IR @bindir@/wineserver ,
92 and if this doesn't exist it will then look for a file named
93 "wineserver" in the path and in a few other likely locations.
96 Specifies the path and name of the
98 binary to use to launch new Windows processes. If not set, Wine will
101 and if this doesn't exist it will then look for a file named "wine" in
102 the path and in a few other likely locations.
105 Turns debugging messages on or off. The syntax of the variable is
107 .RI [ class ][\fB+\fR|\fB-\fR] channel [,[ class2 ][\fB+\fR|\fB-\fR] channel2 ]
111 is optional and can be one of the following:
119 is not specified, all debugging messages for the specified
120 channel are turned on. Each channel will print messages about a particular
122 The following character can be either \fB+\fR or \fB-\fR to switch the specified
123 channel on or off respectively. If there is no
125 part before it, a leading \fB+\fR\fR can be omitted. Note that spaces are not
126 allowed anywhere in the string.
131 will turn on all warning messages (recommended for debugging).
134 WINEDEBUG=warn+dll,+heap
135 will turn on DLL warning messages and all heap messages.
138 WINEDEBUG=fixme-all,warn+cursor,+relay
139 will turn off all FIXME messages, turn on cursor warning messages, and turn
140 on all relay messages (API calls).
144 will turn on all relay messages. For more control on including or excluding
145 functions and dlls from the relay trace, look into the
146 .B HKEY_CURRENT_USER\\\\Software\\\\Wine\\\\Debug
149 For more information on debugging messages, see the
151 chapter of the Wine User Guide.
155 Specifies the path(s) in which to search for builtin dlls and Winelib
156 applications. This is a list of directories separated by ":". In
157 addition to any directory specified in
159 Wine will also look in
163 Defines the override type and load order of dlls used in the loading
164 process for any dll. There are currently two types of libraries that can be loaded
165 into a process address space: native windows dlls
166 .RI ( native ") and Wine internal dlls (" builtin ).
167 The type may be abbreviated with the first letter of the type
169 The library may also be disabled (''). Each sequence of orders must be separated by commas.
172 Each dll may have its own specific load order. The load order
173 determines which version of the dll is attempted to be loaded into the
174 address space. If the first fails, then the next is tried and so
175 on. Multiple libraries with the same load order can be separated with
176 commas. It is also possible to use specify different loadorders for
177 different libraries by separating the entries by ";".
179 The load order for a 16-bit dll is always defined by the load order of
180 the 32-bit dll that contains it (which can be identified by looking at
181 the symbolic link of the 16-bit .dll.so file). For instance if
182 \fIole32.dll\fR is configured as builtin, \fIstorage.dll\fR will be loaded as
183 builtin too, since the 32-bit \fIole32.dll\fR contains the 16-bit
188 WINEDLLOVERRIDES="comdlg32,shell32=n,b"
190 Try to load comdlg32 and shell32 as native windows dll first and try
191 the builtin version if the native load fails.
193 WINEDLLOVERRIDES="comdlg32,shell32=n;c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b"
195 Try to load the libraries comdlg32 and shell32 as native windows dlls. Furthermore, if
196 an application request to load \fIc:\(rsfoo\(rsbar\(rsbaz.dll\fR load the builtin library \fIbaz\fR.
198 WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32="
200 Try to load comdlg32 as builtin first and try the native version if
201 the builtin load fails; load shell32 always as builtin and comctl32
202 always as native; oleaut32 will be disabled.
206 Specifies the Windows architecture to support. It can be set either to
208 (support only 32-bit applications), or to
210 (support both 64-bit applications and 32-bit ones in WoW64 mode).
212 The architecture supported by a given Wine prefix is set at prefix
213 creation time and cannot be changed afterwards. When running with an
214 existing prefix, Wine will refuse to start if
216 doesn't match the prefix architecture.
219 Specifies the X11 display to use.
221 OSS sound driver configuration variables:
224 Set the device for audio input / output. Default
228 Set the device for mixer controls. Default
232 Set the MIDI (sequencer) device. Default
237 The Wine program loader.
239 .I @bindir@/wineconsole
240 The Wine program loader for CUI (console) applications.
242 .I @bindir@/wineserver
249 Directory containing Wine shared libraries
251 .I $WINEPREFIX/dosdevices
252 Directory containing the DOS device mappings. Each file in that
253 directory is a symlink to the Unix device file implementing a given
254 device. For instance, if COM1 is mapped to \fI/dev/ttyS0\fR you'd have a
255 symlink of the form \fI$WINEPREFIX/dosdevices/com1\fR -> \fI/dev/ttyS0\fR.
257 DOS drives are also specified with symlinks; for instance if drive D:
258 corresponds to the CDROM mounted at \fI/mnt/cdrom\fR, you'd have a symlink
259 \fI$WINEPREFIX/dosdevices/d:\fR -> \fI/mnt/cdrom\fR. The Unix device corresponding
260 to a DOS drive can be specified the same way, except with '::' instead
261 of ':'. So for the previous example, if the CDROM device is mounted
262 from \fI/dev/hdc\fR, the corresponding symlink would be
263 \fI$WINEPREFIX/dosdevices/d::\fR -> \fI/dev/hdc\fR.
265 Wine is available thanks to the work of many developers. For a listing
266 of the authors, please see the file
268 in the top-level directory of the source distribution.
270 Wine can be distributed under the terms of the LGPL license. A copy of the
271 license is in the file
273 in the top-level directory of the source distribution.
276 A status report on many applications is available from the
277 .UR http://appdb.winehq.org
278 .B Wine Application Database
280 Please add entries to this list for applications you currently run, if
283 Bugs can be reported on the
284 .UR http://bugs.winehq.org
288 The most recent public version of
290 is available through WineHQ, the
291 .UR http://www.winehq.org/
292 .B Wine development headquarters
298 .UR http://www.winehq.org/help
299 .B Wine documentation and support