2 .TH WINE 1 "October 2005" "@PACKAGE_STRING@" "Windows On Unix"
4 wine \- run Windows programs on Unix
6 .BI "wine " "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, where the program is a DOS, Windows
19 3.x, or Win32 executable (x86 binaries only).
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 (
45 C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE)
47 .I /msdos/windows/sol.exe
48 ). You may pass arguments to the program being executed by adding them
49 to the end of the command line invoking
51 (such as: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT).
52 Note that you need to '\(rs' escape special characters (and spaces) when invoking Wine via
55 wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe
57 .SH ENVIRONMENT VARIABLES
59 makes the environment variables of the shell from which
61 is started accessible to the windows/dos processes started. So use the
62 appropriate syntax for your shell to enter environment variables you need.
65 If set, the content of this variable is taken as the name of the directory where
67 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 try to load
90 .B @bindir@/wineserver,
91 and if this doesn't exist it will then look for a file named
92 "wineserver" in the path and in a few other likely locations.
95 Specifies the path and name of the
97 binary to use to launch new Windows processes. If not set, Wine will
100 and if this doesn't exist it will then look for a file named "wine" in
101 the path and in a few other likely locations.
104 Turns debugging messages on or off. The syntax of the variable is
106 .RI [ class ][+/-] channel [,[ class2 ][+/-] channel2 ].
110 is optional and can be one of the following:
116 is not specified, all debugging messages for the specified
117 channel are turned on. Each channel will print messages about a particular
120 The following character can be either + or - to switch the specified
121 channel on or off respectively. If there is no
123 part before it, a leading + can be omitted. Note that spaces are not
124 allowed anywhere in the string.
129 will turn on all warning messages (recommended for debugging).
132 WINEDEBUG=warn+dll,+heap
133 will turn on DLL warning messages and all heap messages.
136 WINEDEBUG=fixme-all,warn+cursor,+relay
137 will turn off all FIXME messages, turn on cursor warning messages, and turn
138 on all relay messages (API calls).
142 will turn on all relay messages. For more control on including or excluding
143 functions and dlls from the relay trace look into the [Debug] section
144 of the wine configuration file.
146 For more information on debugging messages, see the
148 chapter of the Wine User Guide.
152 Specifies the path(s) in which to search for builtin dlls and Winelib
153 applications. This is a list of directories separated by ":". In
154 addition to any directory specified in
156 Wine will also look in
160 Defines the override type and load order of dlls used in the loading
161 process for any dll. The default is set in the configuration
162 file. There are currently two types of libraries that can be loaded
163 into a process' address space: Native windows dlls (
169 ). The type may be abbreviated with the first letter of the type (
171 ). The library may also be disabled (''). Each sequence of orders must be separated by commas.
174 Each dll may have its own specific load order. The load order
175 determines which version of the dll is attempted to be loaded into the
176 address space. If the first fails, then the next is tried and so
177 on. Multiple libraries with the same load order can be separated with
178 commas. It is also possible to use specify different loadorders for
179 different libraries by separating the entries by ";".
181 The load order for a 16-bit dll is always defined by the load order of
182 the 32-bit dll that contains it (which can be identified by looking at
183 the symbolic link of the 16-bit .dll.so file). For instance if
184 ole32.dll is configured as builtin, storage.dll will be loaded as
185 builtin too, since the 32-bit ole32.dll contains the 16-bit
190 WINEDLLOVERRIDES="comdlg32,shell32=n,b"
192 Try to load comdlg32 and shell32 as native windows dll first and try
193 the builtin version if the native load fails.
195 WINEDLLOVERRIDES="comdlg32,shell32=n;c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b"
197 Try to load the libraries comdlg32 and shell32 as native windows dlls. Furthermore, if
198 an application request to load c:\(rsfoo\(rsbar\(rsbaz.dll load the builtin library baz.
200 WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32="
202 Try to load comdlg32 as builtin first and try the native version if
203 the builtin load fails; load shell32 always as builtin and comctl32
204 always as native. Oleaut32 will be disabled.
208 Specifies the X11 display to use.
210 OSS sound driver configuration variables
213 Set the device for audio input / output. Default
217 Set the device for mixer controls. Default
221 Set the MIDI (sequencer) device. Default
230 .I @bindir@/wineconsole
233 program loader for CUI (console) applications.
235 .I @bindir@/wineserver
250 .I $WINEPREFIX/dosdevices
251 Directory containing the DOS device mappings. Each file in that
252 directory is a symlink to the Unix device file implementing a given
253 device. For instance, if COM1 is mapped to /dev/ttyS0 you'd have a
254 symlink of the form $WINEPREFIX/dosdevices/com1 -> /dev/ttyS0.
256 DOS drives are also specified with symlinks; for instance if drive D:
257 corresponds to the CDROM mounted at /mnt/cdrom, you'd have a symlink
258 $WINEPREFIX/dosdevices/d: -> /mnt/cdrom. The Unix device corresponding
259 to a DOS drive can be specified the same way, except with '::' instead
260 of ':'. So for the previous example, if the CDROM device is mounted
261 from /dev/hdc, the corresponding symlink would be
262 $WINEPREFIX/dosdevices/d:: -> /dev/hdc.
265 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.
271 can be distributed under the terms of the LGPL license. A copy of the
272 license is in the file
274 in the top-level directory of the source distribution.
277 A status report on many applications is available from
278 .I http://appdb.winehq.org.
279 Please add entries to this list for applications you currently run, if
280 there is no entry for this application.
282 Bug reports may be posted to Wine Bugzilla
283 .I http://bugs.winehq.org
284 If you want to post a bug report, please read the file
285 .I documentation/bugs.sgml
288 source to see what information is necessary
290 Problems and suggestions with this manpage please also report to
291 .I http://bugs.winehq.org
293 The most recent public version of
295 can be downloaded from
296 .I http://www.winehq.org/download
298 The latest snapshot of the code may be obtained via GIT. For information
299 on how to do this, please see
301 http://www.winehq.org/site/git
305 development headquarters, is at
306 .I http://www.winehq.org.
307 This website contains a great deal of information about
310 For further information about
312 development, you might want to subscribe to the
315 .I http://www.winehq.org/forums
318 .BR wineserver (1),\ winedbg (1)