2 .TH WINE 1 "Nov 27, 2000" "Version 20001026" "Windows On Unix"
4 wine \- run Windows programs on Unix
6 .BI "wine " "[wine_options] " "[--] " "program " "[arguments ... ]"
8 For instructions on passing arguments to Windows programs, please see the
11 section of the man page.
15 loads and runs the given program, where the program is a DOS, Windows 3.x,
16 or Win32 executable (x86 binaries only).
18 For debugging wine, use
24 currently runs a growing list of applications written for all kinds of
25 Windows versions >= Win2.0, e.g. Win3.1, Win95/98, NT.
26 Older, simpler applications work better than newer, more complex ones.
27 Using Windows ME or Win2000 components with Wine is more problematic than
28 using none at all or the ones from older Windows versions.
29 A large percentage of the API has been implemented,
30 although there are still several major pieces of work left to do.
33 requires kernel-level threads to run. Currently, only Linux version 2.0
34 or later, FreeBSD-current or FreeBSD 3.0 or later, and Solaris x86
35 version 2.5 or later are supported. Other operating systems which support
36 kernel threads may be supported in the future.
38 Although Linux version 2.0 will mostly work, certain features (specifically
39 LDT sharing) required for properly supporting Win32 threads were not
40 implemented until kernel version 2.2. If you get consistent thread-related
41 crashes, you may want to upgrade to 2.2. Also, some bugs were fixed and
42 additional features were added late in the Linux 2.0.x series, so if you have
43 a very old Linux kernel, you may want to upgrade to at least the latest 2.0.x
46 If you have FreeBSD, make sure you have the USER_LDT,
47 SYSVSHM, SYSVSEM, and SYSVMSG options turned on in your kernel. If you
50 on Solaris, you will most likely need to build wine with the GNU toolchain
54 must be installed. To use
56 support for multithreaded applications, your X libraries must be reentrant.
57 If you have libc6 (glibc2), or you
58 compiled the X libraries yourself, they were probably compiled with the
59 reentrant option enabled.
62 must be installed. If you're using Red Hat, make sure the following
63 packages are installed: XFree86-devel, xpm, and xpm-devel. If you're
64 using Debian, the packages you need are xpm4g and xpm4g-dev. If you
65 have some other distribution, please send a list of packages required
66 to the address listed in the
69 section to get it included in this man page.
72 2.7.2 or later is required to build
74 Versions earlier than 2.7.2.3 may have problems when certain files are
75 compiled with optimization, often due to problems with header file
79 currently doesn't work with
81 The cause of this problem is unknown.
84 version 2.5 or later and
86 are required. Bison can be used in replace of yacc. If you have Redhat
87 or Debian, make sure the bison and flex packages are installed.
91 run either "tools/wineinstall" (recommended), or do it the hard way:
92 run "./configure" in the top-level directory of the source, which will
93 detect your specific setup and create the Makefiles. You can run
94 "./configure --help" to see the available configuration options. Then do
95 "make depend && make" to build the
97 executable, and then "make install" to install it. By default,
99 is installed in the /usr/local/ hierarchy (current configuration has it in
100 the @prefix@ hierarchy); you can specify a different path with
101 the --prefix or --sysconfdir options when running
104 For more information, see the
106 file contained in the source distribution.
109 .I --debugmsg [xxx]#name[,[xxx1]#name1][,<+|->relay=yyy1[:yyy2]]
110 Turn debugging messages on or off.
113 xxx is optional and can be one of the following:
119 If xxx is not specified, all debugging messages for the specified
120 channel are turned on. Each channel will print messages about a particular
123 # is required and can be either + or -. Note that
124 there is not a space after the comma between names. yyy are either the
125 name of a whole DLL or a single API entry by name you either
126 want to include or exclude from the relay listing. These names must be in
127 the case as names used in the relaylisting. You can do the same for snoop.
131 .I --debugmsg warn+all
132 will turn on all warning messages (recommended for debugging)
134 .I --debugmsg warn+dll,+heap
135 will turn on DLL warning messages and all heap messages.
137 .I --debugmsg fixme-all,warn+cursor,+relay
138 will turn off all FIXME messages, turn on cursor warning messages, and turn
139 on all relay messages (API calls).
141 .I --debugmsg -relay=LeaveCriticalSection:EnterCriticalSection
142 will turn on all relay messages except for LeaveCriticalSection and
143 EnterCriticalSection.
145 .I --debugmsg +relay=ADVAPI32
146 will only turn on relay messages into the ADVAPI32 code.
148 The full list of names is:
149 all, accel, advapi, animate, aspi, atom, avifile, bitblt, bitmap, caret,
150 cdrom, class, clipboard, clipping, combo, comboex, comm, commctrl, commdlg,
151 console, crtdll, cursor, datetime, dc, ddeml, ddraw, debug, debugstr,
152 delayhlp, dialog, dinput, dll, dosfs, dosmem, dplay, driver, dsound, edit,
153 elfdll, enhmetafile, event, exec, file, fixup, font, gdi, global, graphics,
154 header, heap, hook, hotkey, icmp, icon, imagehlp, imagelist, imm, int, int10,
155 int16, int17, int19, int21, int31, io, ipaddress, joystick, key, keyboard,
156 ldt, listbox, listview, local, mci, mcianim, mciavi, mcicda, mcimidi,
157 mciwave, mdi, menu, message, metafile, midi, mmaux, mmio, mmsys, mmtime,
158 module, monthcal, mpr, msacm, msg, msvideo, nativefont, nonclient, ntdll,
159 odbc, ole, pager, palette, pidl, print, process, profile, progress, prop,
160 propsheet, psapi, psdrv, ras, rebar, reg, region, relay, resource, scroll,
161 segment, seh, selector, sendmsg, server, setupx, shell, snoop, sound,
162 static, statusbar, storage, stress, string, syscolor, system, tab, tape,
163 tapi, task, text, thread, thunk, timer, toolbar, toolhelp, tooltips,
164 trackbar, treeview, ttydrv, tweak, typelib, updown, ver, virtual, vxd, wave,
165 win, win16drv, win32, winedbg, wing, winsock, winspool, wnet, x11 and x11drv.
168 For more information on debugging messages, see the file
169 .I documentation/debug-msgs
170 in the source distribution (FIXME: outdated).
174 Use a desktop window of the given geometry, e.g. "640x480"
177 Use the specified X display
179 .I --dll name[,name[,...]]={native|so|builtin}[,{n|s|b}[,...]][+...]
180 Selects the override type and load order of dll used in the loading
181 process for any dll. The default is set in the configuration
182 file. There are currently three types of libraries that can be loaded
183 into a process' address space: Native windows dlls (
185 ), native ELF libraries (
191 ). The type may be abbreviated with the first letter of the type (
193 ). Each sequence of orders must be separated by commas.
195 Each dll may have its own specific load order. The load order determines
196 which version of the dll is attempted to be loaded into the address space. If
197 the first fails, then the next is tried and so on. Different load orders can
198 be specified by separating the entries with a plus sign. Multiple libraries
199 with the same load order can be separated with commas. It is also possible to
200 use the --dll option several times, to specify different loadorders for different
205 .I --dll comdlg32,commdlg=n,b
207 Try to load comdlg32 and commdlg as native windows dll first and try
208 the builtin version if the native load fails.
210 .I --dll shell,shell32=n --dll c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b
212 Try to load the libraries shell and shell32 as native windows dlls. Furthermore, if
213 an application request to load c:\(rsfoo\(rsbar\(rsbaz.dll load the builtin library baz.
215 .I --dll comdlg32,commdlg=b,n:shell,shell32=b+comctl32,commctrl=n
217 Try to load comdlg32 and commdlg as builtin first and try the native version
218 if the builtin load fails; load shell32/shell always as builtin and
219 comctl32/commctrl always as native.
221 Note: It is wise to keep dll pairs (comdlg32/commdlg, shell/shell32, etc.)
222 having exactly the same load order. This will prevent mismatches at runtime.
223 See also configuration file format below.
226 Specify the DOS version
228 should imitate (e.g. 6.22) This option
229 is only valid when used in conjunction with --winver win31.
234 (one of Br, Ca, Cs, Cy, Da, De, En, Eo, Es, Fi, Fr, Ga, Gd, Gv, Hr,
235 Hu, It, Ko, Kw, No, Pl, Pt, Ru, Sk, Sv, Wa)
238 Create each top-level window as a properly managed X window instead of
239 creating our own "sticky" window.
242 Turn on synchronous display mode. Useful for debugging X11 graphics problems.
245 Specify which Windows version
248 Possible arguments are: win95, nt40, win31, win2000, win98, nt351, win30
251 .SH PROGRAM/ARGUMENTS
252 The program name may be specified in DOS format (
254 C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE)
256 .I /msdos/windows/sol.exe
257 ). You may pass arguments to the program being executed by adding them
258 to the end of the command line invoking
260 (such as: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT). Command line processing goes as
263 checks whether one or more of the above mentioned
265 options have been specified. These
266 are removed from the command line, which is passed to the windows program. You can use
271 should stop command line processing. This is needed in case a windows program understands
272 an option that is usually interpreted (and thus removed from the command line)
275 For example, if you want to execute
278 .I --managed --display :0.2
281 should run the program
284 .I --display 3d somefile
285 , then you could use the following command line to invoke
288 .I wine --managed --display :0.2 -- myapp.exe --display 3d somefile
290 Note that in contrast to previous versions of
293 program name and program option in one argument to
296 than one windows program, just execute
298 once with the name of each program as argument.
299 .SH ENVIRONMENT VARIABLES
301 makes the environment variables of the shell from which
303 is started accessible to the windows/dos processes started. So use the
304 appropriate syntax for your shell to enter environment variables you need.
307 If set, the content of this variable is taken as the name of the directory where
309 stores its data (the default is
311 ). This directory contains also the socket, which is used to communicate with the
315 processes using the same
317 (i.e.: same user) share certain things like registry and shared memory.
320 to different values for different
322 processes, it is possible to run a number of truly independent
327 Specifies the path and name of the
329 binary. If not set, a file named "wineserver" is searched in the
330 path and in a few other likely locations.
333 Specifies the path and name of the
335 binary to use to launch new Windows processes. If not set, a binary
336 named "wine" is searched in the path and in a few other likely
340 Specifies the path(s) in which to search for builtin dll files. This
341 is a list of directories separated by ":". Builtin dlls are also
342 searched in the directories specified by the standard
344 if they are not found in the directories listed in
347 .SH CONFIGURATION FILE
349 expects a configuration file (
350 .I @sysconfdir@/wine.conf
351 ), which must conform to the format specified in the
353 man page. A sample configuration file is documentation/samples/config in the
355 source archive. Alternatively a configuration file with the name
357 in the ~/.wine directory of the user running
362 is available thanks to the work of many developers. For a listing
363 of the authors, please see the file
365 in the top-level directory of the source distribution.
368 can be distributed under the terms of the X11 license. A copy of the
369 license is in the file
371 in the top-level directory of the source distribution.
374 A status report on many applications is available from
375 .I http://www.winehq.com/Apps.
376 Please add entries to this list for applications you currently run.
378 Bug reports and successes may be posted to
379 .I comp.emulators.ms-windows.wine.
380 If you want to post a bug report, please read the file
381 .I documentation/bugreports
384 source to see what information is necessary (FIXME: outdated).
386 For problems and suggestions with this manpage, please send a note to
387 James Juran <jrj120@psu.edu>.
389 The most recent public version of
391 can be obtained via FTP from ibiblio.org in the
392 /pub/Linux/ALPHA/Wine/development directory. The releases are in the
393 format 'Wine-yyyymmdd.tar.gz', or 'Wine-yyyymmdd.diff.gz' for the diff's
394 from the previous release.
396 The latest snapshot of the code may be obtained via CVS. For information
397 on how to do this, please see
399 http://www.winehq.com/dev.html
403 development headquarters, is at
404 .I http://www.winehq.com/.
405 This website contains a great deal of information about
411 .I comp.emulators.ms-windows.wine.
412 It is used for discussion of various
413 .B wine end user aspects/help.
415 For further information about
417 development, you might want to subscribe to the
419 "cvs", "devel" and "patches" mailing lists at
420 .I http://www.winehq.com/dev.html#ml.
429 .I @prefix@/bin/dosmod
430 The DOS program loader.
432 .I @prefix@/bin/wineserver
437 .I @prefix@/bin/winedbg
442 .I @prefix@/bin/wineclpsrv
452 .I @sysconfdir@/wine.conf
453 Global configuration file for
457 User-specific configuration file
460 Directory containing user specific data managed by
projects / wine / blob