1WINE(1) Windows On Unix WINE(1)
2
6 wine - run Windows programs on Unix
7
9 wine program [arguments ... ]
10 wine --help
11 wine --version
12 For instructions on passing arguments to Windows programs, please see
14 the PROGRAM/ARGUMENTS section of the man page.
15
17 wine loads and runs the given program, where the program is a DOS, Win‐
18 dows 3.x, or Win32 executable (x86 binaries only).
19 For debugging wine, use winedbg instead.
21 For running CUI executables (Windows console programs), use wineconsole
23 instead of wine. This will display all the output in a separate win‐
24 dows (this requires X11 to run). Not using wineconsole for CUI programs
25 will only provide very limited console support, and your program might
26 not function properly.
27 When invoked with --help or --version as the only argument, wine will
29 simply print a small help message or its version respectively and exit.
30
32 The program name may be specified in DOS format (C:\\WINDOWS\\SOL.EXE)
33 or in Unix format (/msdos/windows/sol.exe). You may pass arguments to
34 the program being executed by adding them to the end of the command
35 line invoking wine (such as: wine notepad C:\\TEMP\\README.TXT). Note
36 that you need to '\' escape special characters (and spaces) when invok‐
37 ing Wine via a shell, e.g.
38 wine C:\\Program\ Files\\MyPrg\\test.exe
40
42 wine makes the environment variables of the shell from which wine is
43 started accessible to the windows/dos processes started. So use the
44 appropriate syntax for your shell to enter environment variables you
45 need.
46 WINEPREFIX
48 If set, the content of this variable is taken as the name of the
49 directory where wine stores its data (the default is
50 $HOME/.wine). This directory is also used to identify the
51 socket which is used to communicate with the wineserver. All
52 wine processes using the same wineserver (i.e.: same user) share
53 certain things like registry, shared memory, and config file.
54 By setting WINEPREFIX to different values for different wine
55 processes, it is possible to run a number of truly independent
56 wine processes.
57 WINESERVER
59 Specifies the path and name of the wineserver binary. If not
60 set, Wine will try to load /usr/bin/wineserver, and if this
61 doesn't exist it will then look for a file named "wineserver" in
62 the path and in a few other likely locations.
63 WINELOADER
65 Specifies the path and name of the wine binary to use to launch
66 new Windows processes. If not set, Wine will try to load
67 /usr/bin/wine, and if this doesn't exist it will then look for a
68 file named "wine" in the path and in a few other likely loca‐
69 tions.
70 WINEDEBUG
72 Turns debugging messages on or off. The syntax of the variable
73 is of the form [class][+/-]channel[,[class2][+/-]channel2].
74 class is optional and can be one of the following: err, warn,
76 fixme, or trace. If class is not specified, all debugging mes‐
77 sages for the specified channel are turned on. Each channel
78 will print messages about a particular component of wine. The
79 following character can be either + or - to switch the specified
80 channel on or off respectively. If there is no class part
81 before it, a leading + can be omitted. Note that spaces are not
82 allowed anywhere in the string.
83 Examples:
85 WINEDEBUG=warn+all
87 will turn on all warning messages (recommended for debug‐
88 ging).
89 WINEDEBUG=warn+dll,+heap
91 will turn on DLL warning messages and all heap messages.
92 WINEDEBUG=fixme-all,warn+cursor,+relay
94 will turn off all FIXME messages, turn on cursor warning
95 messages, and turn on all relay messages (API calls).
96 WINEDEBUG=relay
98 will turn on all relay messages. For more control on
99 including or excluding functions and dlls from the relay
100 trace, look into the HKEY_CURRENT_USER\Soft‐
101 ware\Wine\Debug registry key.
102 For more information on debugging messages, see the Running Wine
104 chapter of the Wine User Guide.
105 WINEDLLPATH
107 Specifies the path(s) in which to search for builtin dlls and
108 Winelib applications. This is a list of directories separated by
109 ":". In addition to any directory specified in WINEDLLPATH, Wine
110 will also look in /usr/lib64/wine.
111 WINEDLLOVERRIDES
113 Defines the override type and load order of dlls used in the
114 loading process for any dll. There are currently two types of
115 libraries that can be loaded into a process' address space:
116 native windows dlls (native), wine internal dlls (builtin). The
117 type may be abbreviated with the first letter of the type (n,
118 b). The library may also be disabled (''). Each sequence of
119 orders must be separated by commas.
120 Each dll may have its own specific load order. The load order
122 determines which version of the dll is attempted to be loaded
123 into the address space. If the first fails, then the next is
124 tried and so on. Multiple libraries with the same load order can
125 be separated with commas. It is also possible to use specify
126 different loadorders for different libraries by separating the
127 entries by ";".
128 The load order for a 16-bit dll is always defined by the load
130 order of the 32-bit dll that contains it (which can be identi‐
131 fied by looking at the symbolic link of the 16-bit .dll.so
132 file). For instance if ole32.dll is configured as builtin, stor‐
133 age.dll will be loaded as builtin too, since the 32-bit
134 ole32.dll contains the 16-bit storage.dll.
135 Examples:
137 WINEDLLOVERRIDES="comdlg32,shell32=n,b"
139 Try to load comdlg32 and shell32 as native windows dll
140 first and try the builtin version if the native load
141 fails.
142 WINEDLLOVERRIDES="comdlg32,shell32=n;c:\\foo\\bar\\baz=b"
144 Try to load the libraries comdlg32 and shell32 as native
145 windows dlls. Furthermore, if an application request to
146 load c:\foo\bar\baz.dll load the builtin library baz.
147 WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32="
149 Try to load comdlg32 as builtin first and try the native
150 version if the builtin load fails; load shell32 always as
151 builtin and comctl32 always as native. Oleaut32 will be
152 disabled.
153 WINEARCH
155 Specifies the Windows architecture to support. It can be set
156 either to win32 (support only 32-bit applications), or to win64
157 (support both 64-bit applications and 32-bit ones in WoW64
158 mode).
159 The architecture supported by a given Wine prefix is set at pre‐
160 fix creation time and cannot be changed afterwards. When running
161 with an existing prefix, Wine will refuse to start if WINEARCH
162 doesn't match the prefix architecture.
163 DISPLAY
165 Specifies the X11 display to use.
166 OSS sound driver configuration variables
168 AUDIODEV
170 Set the device for audio input / output. Default /dev/dsp.
171 MIXERDEV
173 Set the device for mixer controls. Default /dev/mixer.
174 MIDIDEV
176 Set the MIDI (sequencer) device. Default /dev/sequencer.
177
179 /usr/bin/wine
180 The wine program loader.
181 /usr/bin/wineconsole
183 The wine program loader for CUI (console) applications.
184 /usr/bin/wineserver
186 The wine server
187 /usr/bin/winedbg
189 The wine debugger
190 /usr/lib64/wine
192 Directory containing wine's shared libraries
193 $WINEPREFIX/dosdevices
195 Directory containing the DOS device mappings. Each file in that
196 directory is a symlink to the Unix device file implementing a
197 given device. For instance, if COM1 is mapped to /dev/ttyS0
198 you'd have a symlink of the form $WINEPREFIX/dosdevices/com1 ->
199 /dev/ttyS0.
200 DOS drives are also specified with symlinks; for instance if
201 drive D: corresponds to the CDROM mounted at /mnt/cdrom, you'd
202 have a symlink $WINEPREFIX/dosdevices/d: -> /mnt/cdrom. The Unix
203 device corresponding to a DOS drive can be specified the same
204 way, except with '::' instead of ':'. So for the previous exam‐
205 ple, if the CDROM device is mounted from /dev/hdc, the corre‐
206 sponding symlink would be $WINEPREFIX/dosdevices/d:: ->
207 /dev/hdc.
208
210 wine is available thanks to the work of many developers. For a listing
211 of the authors, please see the file AUTHORS in the top-level directory
212 of the source distribution.
213
215 wine can be distributed under the terms of the LGPL license. A copy of
216 the license is in the file COPYING.LIB in the top-level directory of
217 the source distribution.
218
220 A status report on many applications is available from
221 http://appdb.winehq.org. Please add entries to this list for applica‐
222 tions you currently run, if there is no entry for this application.
223 Bug reports may be posted to Wine Bugzilla http://bugs.winehq.org If
225 you want to post a bug report, please see http://wiki.winehq.org/Bugs
226 in the wine source to see what information is necessary
227 Problems and suggestions with this manpage please also report to
229 http://bugs.winehq.org
230
232 The most recent public version of wine can be downloaded from
233 http://www.winehq.org/download
234 The latest snapshot of the code may be obtained via GIT. For informa‐
236 tion on how to do this, please see http://www.winehq.org/site/git
237 WineHQ, the wine development headquarters, is at http://www.winehq.org.
239 This website contains a great deal of information about wine.
240 For further information about wine development, you might want to sub‐
242 scribe to the wine mailing lists at http://www.winehq.org/forums
243
246 wineserver(1), winedbg(1)
247Wine 1.3.24 October 2005 WINE(1)