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, which can be a DOS, Windows 3.x,
18 Win32 or Win64 executable (on 64-bit systems).
19 For debugging wine, use winedbg instead.
21 For running CUI executables (Windows console programs), use wineconsole
23 instead of wine. This will display the output in a separate window.
24 Not using wineconsole for CUI programs will only provide very limited
25 console support, and your program might not function properly.
26 When invoked with --help or --version as the only argument, wine will
28 simply print a small help message or its version respectively and exit.
29
31 The program name may be specified in DOS format (C:\\WINDOWS\\SOL.EXE)
32 or in Unix format (/msdos/windows/sol.exe). You may pass arguments to
33 the program being executed by adding them to the end of the command
34 line invoking wine (such as: wine notepad C:\\TEMP\\README.TXT). Note
35 that you need to '\' escape special characters (and spaces) when invok‐
36 ing Wine via a shell, e.g.
37 wine C:\\Program\ Files\\MyPrg\\test.exe
39 It can also be one of the Windows executables shipped with Wine, in
41 which case specifying the full path is not mandatory, e.g. wine ex‐
42 plorer or wine notepad.
43
45 wine makes the environment variables of the shell from which it is
46 started accessible to the Windows/DOS processes started. So use the ap‐
47 propriate syntax for your shell to enter environment variables you
48 need.
49 WINEPREFIX
51 If set, the contents of this variable is taken as the name of
52 the directory where Wine stores its data (the default is
53 $HOME/.wine). This directory is also used to identify the
54 socket which is used to communicate with the wineserver. All
55 wine processes using the same wineserver (i.e.: same user) share
56 certain things like registry, shared memory, and config file.
57 By setting WINEPREFIX to different values for different wine
58 processes, it is possible to run a number of truly independent
59 wine processes.
60 WINESERVER
62 Specifies the path and name of the wineserver binary. If not
63 set, Wine will try to load /usr/bin/wineserver, and if this
64 doesn't exist it will then look for a file named "wineserver" in
65 the path and in a few other likely locations.
66 WINELOADER
68 Specifies the path and name of the wine binary to use to launch
69 new Windows processes. If not set, Wine will try to load
70 /usr/bin/wine, and if this doesn't exist it will then look for a
71 file named "wine" in the path and in a few other likely loca‐
72 tions.
73 WINEDEBUG
75 Turns debugging messages on or off. The syntax of the variable
76 is of the form [class][+|-]channel[,[class2][+|-]channel2]
77 class is optional and can be one of the following: err, warn,
79 fixme, or trace. If class is not specified, all debugging mes‐
80 sages for the specified channel are turned on. Each channel
81 will print messages about a particular component of Wine. The
82 following character can be either + or - to switch the specified
83 channel on or off respectively. If there is no class part be‐
84 fore it, a leading + can be omitted. Note that spaces are not
85 allowed anywhere in the string.
86 Examples:
88 WINEDEBUG=warn+all
90 will turn on all warning messages (recommended for debug‐
91 ging).
92 WINEDEBUG=warn+dll,+heap
94 will turn on DLL warning messages and all heap messages.
95 WINEDEBUG=fixme-all,warn+cursor,+relay
97 will turn off all FIXME messages, turn on cursor warning
98 messages, and turn on all relay messages (API calls).
99 WINEDEBUG=relay
101 will turn on all relay messages. For more control on in‐
102 cluding or excluding functions and dlls from the relay
103 trace, look into the HKEY_CURRENT_USER\Software\Wine\De‐
104 bug registry key.
105 For more information on debugging messages, see the Running Wine
107 chapter of the Wine User Guide.
108 WINEDLLPATH
110 Specifies the path(s) in which to search for builtin dlls and
111 Winelib applications. This is a list of directories separated by
112 ":". In addition to any directory specified in WINEDLLPATH, Wine
113 will also look in /usr/lib/wine.
114 WINEDLLOVERRIDES
116 Defines the override type and load order of dlls used in the
117 loading process for any dll. There are currently two types of
118 libraries that can be loaded into a process address space: na‐
119 tive windows dlls (native) and Wine internal dlls (builtin).
120 The type may be abbreviated with the first letter of the type (n
121 or b). The library may also be disabled (''). Each sequence of
122 orders must be separated by commas.
123 Each dll may have its own specific load order. The load order
125 determines which version of the dll is attempted to be loaded
126 into the address space. If the first fails, then the next is
127 tried and so on. Multiple libraries with the same load order can
128 be separated with commas. It is also possible to use specify
129 different loadorders for different libraries by separating the
130 entries by ";".
131 The load order for a 16-bit dll is always defined by the load
133 order of the 32-bit dll that contains it (which can be identi‐
134 fied by looking at the symbolic link of the 16-bit .dll.so
135 file). For instance if ole32.dll is configured as builtin, stor‐
136 age.dll will be loaded as builtin too, since the 32-bit
137 ole32.dll contains the 16-bit storage.dll.
138 Examples:
140 WINEDLLOVERRIDES="comdlg32,shell32=n,b"
142 Try to load comdlg32 and shell32 as native windows dll
143 first and try the builtin version if the native load
144 fails.
145 WINEDLLOVERRIDES="comdlg32,shell32=n;c:\\foo\\bar\\baz=b"
147 Try to load the libraries comdlg32 and shell32 as native
148 windows dlls. Furthermore, if an application request to
149 load c:\foo\bar\baz.dll load the builtin library baz.
150 WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n;oleaut32="
152 Try to load comdlg32 as builtin first and try the native
153 version if the builtin load fails; load shell32 always as
154 builtin and comctl32 always as native; oleaut32 will be
155 disabled.
156 WINEPATH
158 Specifies additional path(s) to be prepended to the default Win‐
159 dows PATH environment variable. This is a list of Windows-style
160 directories separated by ";".
161 For a permanent alternative, edit (create if needed) the PATH
163 value under the HKEY_CURRENT_USER\Environment registry key.
164 WINEARCH
166 Specifies the Windows architecture to support. It can be set ei‐
167 ther to win32 (support only 32-bit applications), or to win64
168 (support both 64-bit applications and 32-bit ones in WoW64
169 mode).
170 The architecture supported by a given Wine prefix is set at pre‐
171 fix creation time and cannot be changed afterwards. When running
172 with an existing prefix, Wine will refuse to start if WINEARCH
173 doesn't match the prefix architecture.
174 WINE_D3D_CONFIG
176 Specifies Direct3D configuration options. It can be used instead
177 of modifying the HKEY_CURRENT_USER\Software\Wine\Direct3D reg‐
178 istry key. The value is a comma- or semicolon-separated list of
179 key-value pairs. For example:
180 WINE_D3D_CONFIG="renderer=vulkan;VideoPciVendorID=0xc0de"
182 If an individual setting is specified in both the environment
184 variable and the registry, the former takes precedence.
185 DISPLAY
187 Specifies the X11 display to use.
188 OSS sound driver configuration variables:
190 AUDIODEV
192 Set the device for audio input / output. Default /dev/dsp.
193 MIXERDEV
195 Set the device for mixer controls. Default /dev/mixer.
196 MIDIDEV
198 Set the MIDI (sequencer) device. Default /dev/sequencer.
199
201 /usr/bin/wine
202 The Wine program loader.
203 /usr/bin/wineconsole
205 The Wine program loader for CUI (console) applications.
206 /usr/bin/wineserver
208 The Wine server
209 /usr/bin/winedbg
211 The Wine debugger
212 /usr/lib/wine
214 Directory containing Wine shared libraries
215 $WINEPREFIX/dosdevices
217 Directory containing the DOS device mappings. Each file in that
218 directory is a symlink to the Unix device file implementing a
219 given device. For instance, if COM1 is mapped to /dev/ttyS0
220 you'd have a symlink of the form $WINEPREFIX/dosdevices/com1 ->
221 /dev/ttyS0.
222 DOS drives are also specified with symlinks; for instance if
223 drive D: corresponds to the CDROM mounted at /mnt/cdrom, you'd
224 have a symlink $WINEPREFIX/dosdevices/d: -> /mnt/cdrom. The Unix
225 device corresponding to a DOS drive can be specified the same
226 way, except with '::' instead of ':'. So for the previous exam‐
227 ple, if the CDROM device is mounted from /dev/hdc, the corre‐
228 sponding symlink would be $WINEPREFIX/dosdevices/d:: ->
229 /dev/hdc.
230
232 Wine is available thanks to the work of many developers. For a listing
233 of the authors, please see the file AUTHORS in the top-level directory
234 of the source distribution.
235
237 Wine can be distributed under the terms of the LGPL license. A copy of
238 the license is in the file COPYING.LIB in the top-level directory of
239 the source distribution.
240
242 A status report on many applications is available from the Wine
243 Application Database ⟨https://appdb.winehq.org⟩. Please add entries to
244 this list for applications you currently run, if necessary.
245 Bugs can be reported on the Wine bug tracker ⟨https://bugs.winehq.org⟩.
247
249 The most recent public version of wine is available through WineHQ, the
250 Wine development headquarters ⟨https://www.winehq.org/⟩.
251
253 wineserver(1), winedbg(1),
254 Wine documentation and support ⟨https://www.winehq.org/help⟩.
255Wine 8.19 July 2013 WINE(1)