2 .TH WINE 1 "July 16, 1999" "Version 20000326" "Windows On Unix"
4 wine \- run Windows programs on Unix
6 .BI "wine " "[wine_options] " "program1 " "[program2 ... ]"
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).
19 currently runs a growing list of applications written for Win3.1,
20 Win95, Win95, and Windows NT. Older, simpler applications work better than
21 newer, more complex ones. A large percentage of the API has been implemented,
22 although there are still several major pieces of work left to do.
25 requires kernel-level threads to run. Currently, only Linux version 2.0
26 or later, FreeBSD-current or FreeBSD 3.0 or later, and Solaris x86
27 version 2.5 or later are supported. Other operating systems which support
28 kernel threads may be supported in the future.
30 Although Linux version 2.0 will mostly work, certain features (specifically
31 LDT sharing) required for properly supporting Win32 threads were not
32 implemented until kernel version 2.2. If you get consistent thread-related
33 crashes, you may want to upgrade to 2.2. Also, some bugs were fixed and
34 additional features were added late in the Linux 2.0.x series, so if you have
35 a very old Linux kernel, you may want to upgrade to at least the latest 2.0.x
38 If you have FreeBSD, make sure you have the USER_LDT,
39 SYSVSHM, SYSVSEM, and SYSVMSG options turned on in your kernel. If you
42 on Solaris, you will most likely need to build Wine with the GNU toolchain
46 must be installed. To use
48 support for multithreaded applications, your X libraries must be reentrant.
49 If you have libc6 (glibc2), or you
50 compiled the X libraries yourself, they were probably compiled with the
51 reentrant option enabled.
54 must be installed. If you're using Red Hat, make sure the following
55 packages are installed: XFree86-devel, xpm, and xpm-devel. If you're
56 using Debian, the packages you need are xpm4g and xpm4g-dev. If you
57 have some other distribution, please send a list of packages required
58 to the address listed in the
61 section to get it included in this man page.
64 2.7.2 or later is required to build
66 Versions earlier than 2.7.2.3 may have problems when certain files are
67 compiled with optimization, often due to problems with header file
71 currently doesn't work with
73 The cause of this problem is unknown.
76 version 2.5 or later and
78 are required. Bison can be used in replace of yacc. If you have Redhat
79 or Debian, make sure the bison and flex packages are installed.
83 run "./configure" in the top-level directory of the source, which will
84 detect your specific setup and create the Makefiles. You can run
85 "./configure --help" to see the available configuration options. Then do
86 "make depend && make" to build the
88 executable, and then "make install" to install it. By default,
90 is installed in the /usr/local/ hierarchy (current configuration has it in
91 the @prefix@ hierarchy); you can specify a different path with
92 the --prefix or --sysconfdir options when running
95 For more information, see the
97 file contained in the source distribution.
101 Use the named configuration file rather than the default
102 (@sysconfdir@/wine.conf or ~/.winerc).
105 Enter the debugger before starting application.
107 .I --debugmsg [xxx]#name[,[xxx1]#name1][,<+|->relay=yyy1[:yyy2]]
108 Turn debugging messages on or off.
111 xxx is optional and can be one of the following:
117 If xxx is not specified, all debugging messages for the specified
118 channel are turned on. Each channel will print messages about a particular
121 # is required and can be either + or -. Note that
122 there is not a space after the comma between names. yyy are either the
123 name of a whole DLL or a single API entry by Name you either
124 want to include or exclude from the relay listing. These names must be in
125 the case as names used in the relaylisting. You can do the same for snoop.
129 .I --debugmsg warn+dll,+heap
130 will turn on DLL warning messages and all heap messages.
132 .I --debugmsg fixme-all,warn+cursor,+relay
133 will turn off all FIXME messages, turn on cursor warning messages, and turn
134 on all relay messages (API calls).
136 .I --debugmsg -relay=LeaveCriticalSection:EnterCriticalSection
137 will turn on all relay messages except for LeaveCriticalSection and
138 EnterCriticalSection.
140 .I --debugmsg +relay=ADVAPI32
141 will only turn on relay messages into the ADVAPI32 code.
143 The full list of names is: all, accel, advapi, animate, aspi, atom, avifile, bitblt,
144 bitmap, caret, cdrom, class, clipboard, clipping, combo, comboex, comm, commctrl,
145 commdlg, console, crtdll, cursor, datetime, dc, ddeml, ddraw, debug, debugstr, delayhlp,
146 dialog, dinput, dll, dosfs, dosmem, dplay, driver, dsound, edit, elfdll, enhmetafile,
147 event, exec, file, fixup, font, gdi, global, graphics, header, heap, hook, hotkey,
148 icmp, icon, imagehlp, imagelist, imm, int, int10, int16, int17, int19, int21, int31,
149 io, ipaddress, joystick, key, keyboard, ldt, listbox, listview, local, mci, mcianim,
150 mciavi, mcicda, mcimidi, mciwave, mdi, menu, message, metafile, midi, mmaux, mmio,
151 mmsys, mmtime, module, monthcal, mpr, msacm, msg, msvideo, nativefont, nonclientntdll,
152 odbc, ole, pager, palette, pidl, print, process, profile, progress, prop, propsheet,
153 psapi, psdrv, ras, rebar, reg, region, relay, resource, scroll, segment, seh, selector,
154 sendmsg, server, setupx, shell, snoop, sound, static, statusbar, storage, stress, string,
155 syscolor, system, tab, tape, tapi, task, text, thread, thunk, timer, toolbar, toolhelp,
156 tooltips, trackbar, treeview, ttydrv, tweak, typelib, updown, ver, virtual, vxd, wave,
157 win, win16drv, win32, winedbg, wing, winsock, winspool, wnet, x11 and x11drv.
160 For more information on debugging messages, see the file
161 .I documentation/debug-msgs
162 in the source distribution.
166 Use a desktop window of the given geometry, e.g. "640x480"
169 Use the specified X display
171 .I --dll name[,name[,...]]={native|elfdll|so|builtin}[,{n|e|s|b}[,...]][:...]
172 Selects the override type and load order of dll used in the loading process
173 for any dll. The default is set in @sysconfdir@/wine.conf or ~/.winerc. There
174 are currently four types of libraries that can be loaded into a process' address
175 space: Native windows dlls (
177 ), ELF encapsulated windows dlls (
179 ), native ELF libraries (
185 ). The type may be abbreviated with the first letter of the type (
187 ). Each sequence of orders must be separated by commas.
189 Each dll may have its own specific load order. The load order determines
190 which verion of the dll is attempted to be loaded into the address space. If
191 the first fails, then the next is tried and so on. Different load orders can
192 be specified by separating the entries with a colon. Multiple libraries
193 with the same load order can be separated with commas.
197 .I --dll comdlg32,commdlg=n,b
199 Try to load comdlg32 and commdlg as native windows dll first and try
200 the builtin version if the native load fails.
202 .I --dll comdlg32,commdlg=e,n:shell,shell32=b:comctl32,commctrl=n
204 Try to load comdlg32 and commdlg as elfdll first and try the native version
205 if the elfdll load fails; load shell32/shell always as builtin and
206 comctl32/commctrl always as native.
208 Note: It is wise to keep dll pairs (comdlg32/commdlg, shell/shell32, etc.)
209 having exactly the same load order. This will prevent mismatches at runtime.
210 See also configuration file format below.
213 Specify the DOS version
215 should imitate (e.g. 6.22) This option
216 is only valid when used in conjunction with --winver win31.
221 (one of Br, Ca, Cs, Cy, Da, De, En, Eo, Es, Fi, Fr, Ga, Gd, Gv, Hu,
222 It, Ko, Kw, No, Pl, Pt, Ru, Sk, Sv, Wa)
225 Create each top-level window as a properly managed X window instead of
226 creating our own "sticky" window.
229 Turn on synchronous display mode. Useful for debugging X11 graphics problems.
232 Specify which Windows version
235 Possible arguments are: win31, win95, nt351, and nt40.
237 .SH PROGRAM/ARGUMENTS
238 The program name may be specified in DOS format (
240 C:\\WINDOWS\\SOL.EXE)
242 .I /msdos/windows/sol.exe
243 ). The program being executed may be passed arguments by adding them on
244 to the end of the command line invoking
246 (such as: wine "notepad C:\\TEMP\\README.TXT"). Note that
247 the program name and its arguments
249 be passed as a single parameter, which is usually accomplished by placing
250 them together in quotation marks. Multiple applications may be started
251 by placing all of them on the command line (such as:
254 .SH ENVIRONMENT VARIABLES
256 makes the environment variables of the shell from which
258 is started accessible to the windows/dos processes started. So use the
259 appropriate syntax for your shell to enter environment variables you need.
260 .SH CONFIGURATION FILE
262 expects a configuration file (
263 .I @sysconfdir@/wine.conf
264 ), which must conform to the format specified in the
266 man page. A sample configuration file is wine.ini in the home directory of the
267 .B wine source archive.
270 is available thanks to the work of many developers. For a listing
271 of the authors, please see the file
273 in the top-level directory of the source distribution.
276 A status report on many appplications is available from
277 .I http://www.winehq.com/Apps.
278 Please add entries to this list for applications you currently run.
280 Bug reports and successes may be posted to
281 .I comp.emulators.ms-windows.wine.
282 If you want to post a bug report, please read the file
283 .I documentation/bugreports
286 source to see what information is necessary.
288 For problems and suggestions with this manpage, please send a note to
289 James Juran <jrj120@psu.edu>.
291 The most recent public version of
293 can be obtained via FTP from metalab.unc.edu or tsx-11.mit.edu in the
294 /pub/linux/ALPHA/Wine/development directory. The releases are in the
295 format 'Wine-yymmdd.tar.gz', or 'Wine-yymmdd.diff.gz' for the diff's
296 from the previous release.
298 The latest snapshot of the code may be obtained via CVS. For information
299 on how to do this, please see
301 http://www.winehq.com/dev.html
305 development headquarters, is at
306 .I http://www.winehq.com/.
307 This website contains a great deal of information about
313 .I comp.emulators.ms-windows.wine.
314 It is used for discussion of various
315 .B wine end user aspects/help.
317 For further information about
318 .B wine development, you might want to
321 "cvs", "devel" and "patches" mailing lists at
322 .I http://www.winehq.com/dev.html#ml.
331 .I @prefix@/bin/dosmod
332 The DOS program loader.
334 .I @prefix@/bin/wineserver
339 .I @prefix@/bin/wineclpsrv
349 .I @sysconfdir@/wine.conf
350 Global configuration file for
354 User-specific configuration file
357 Directory containing user specific data managed by
360 .I @prefix@/lib/wine.sym
361 Global symbol table (used in debugger)
projects / wine / blob