2 .TH WINE 1 "Feb 13, 2001" "Version 20010112" "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.
31 .SH REQUIREMENTS AND INSTALLATION
32 Read the README file in the Wine source distribution to know what Wine
33 requires and how it is installed from source.
36 .I --debugmsg [xxx]#name[,[xxx1]#name1][,<+|->relay=yyy1[:yyy2]]
37 Turn debugging messages on or off.
40 xxx is optional and can be one of the following:
46 If xxx is not specified, all debugging messages for the specified
47 channel are turned on. Each channel will print messages about a particular
50 # is required and can be either + or -. Note that
51 there is not a space after the comma between names. yyy are either the
52 name of a whole DLL or a single API entry by name you either
53 want to include or exclude from the relay listing. Case doesn't matter
54 for these. You can do the same for snoop.
58 .I --debugmsg warn+all
59 will turn on all warning messages (recommended for debugging)
61 .I --debugmsg warn+dll,+heap
62 will turn on DLL warning messages and all heap messages.
64 .I --debugmsg fixme-all,warn+cursor,+relay
65 will turn off all FIXME messages, turn on cursor warning messages, and turn
66 on all relay messages (API calls).
68 .I --debugmsg -relay=rtlleavecriticalsection:RtlEnterCriticalSection
69 will turn on all relay messages except for RtlLeaveCriticalSection and
70 RtlEnterCriticalSection.
72 .I --debugmsg +relay=advapi32
73 will only turn on relay messages into the ADVAPI32 code.
75 The full list of names is:
76 all, accel, advapi, animate, aspi, atom, avifile, bitblt, bitmap, caret,
77 cdrom, class, clipboard, clipping, combo, comboex, comm, commctrl, commdlg,
78 console, crtdll, cursor, datetime, dc, ddeml, ddraw, debug, debugstr,
79 delayhlp, dialog, dinput, dll, dosfs, dosmem, dplay, driver, dsound, edit,
80 elfdll, enhmetafile, event, exec, file, fixup, font, gdi, global, graphics,
81 header, heap, hook, hotkey, icmp, icon, imagehlp, imagelist, imm, int, int10,
82 int16, int17, int19, int21, int31, io, ipaddress, joystick, key, keyboard,
83 ldt, listbox, listview, local, mci, mcianim, mciavi, mcicda, mcimidi,
84 mciwave, mdi, menu, message, metafile, midi, mmaux, mmio, mmsys, mmtime,
85 module, monthcal, mpr, msacm, msg, msvideo, nativefont, nonclient, ntdll,
86 odbc, ole, pager, palette, pidl, print, process, profile, progress, prop,
87 propsheet, psapi, psdrv, ras, rebar, reg, region, relay, resource, scroll,
88 segment, seh, selector, sendmsg, server, setupx, shell, snoop, sound,
89 static, statusbar, storage, stress, string, syscolor, system, tab, tape,
90 tapi, task, text, thread, thunk, timer, toolbar, toolhelp, tooltips,
91 trackbar, treeview, ttydrv, tweak, typelib, updown, ver, virtual, vxd, wave,
92 win, win16drv, win32, winedbg, wing, winsock, winspool, wnet, x11 and x11drv.
95 For more information on debugging messages, see the file
96 .I documentation/debug-msgs
97 in the source distribution (FIXME: outdated).
101 Use a desktop window of the given geometry, e.g. "640x480"
104 Use the specified X display
106 .I --dll name[,name[,...]]={native|so|builtin}[,{n|s|b}[,...]][+...]
107 Selects the override type and load order of dll used in the loading
108 process for any dll. The default is set in the configuration
109 file. There are currently three types of libraries that can be loaded
110 into a process' address space: Native windows dlls (
112 ), native ELF libraries (
118 ). The type may be abbreviated with the first letter of the type (
120 ). Each sequence of orders must be separated by commas.
122 Each dll may have its own specific load order. The load order determines
123 which version of the dll is attempted to be loaded into the address space. If
124 the first fails, then the next is tried and so on. Different load orders can
125 be specified by separating the entries with a plus sign. Multiple libraries
126 with the same load order can be separated with commas. It is also possible to
127 use the --dll option several times, to specify different loadorders for different
132 .I --dll comdlg32,commdlg=n,b
134 Try to load comdlg32 and commdlg as native windows dll first and try
135 the builtin version if the native load fails.
137 .I --dll shell,shell32=n --dll c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b
139 Try to load the libraries shell and shell32 as native windows dlls. Furthermore, if
140 an application request to load c:\(rsfoo\(rsbar\(rsbaz.dll load the builtin library baz.
142 .I --dll comdlg32,commdlg=b,n:shell,shell32=b+comctl32,commctrl=n
144 Try to load comdlg32 and commdlg as builtin first and try the native version
145 if the builtin load fails; load shell32/shell always as builtin and
146 comctl32/commctrl always as native.
148 Note: It is wise to keep dll pairs (comdlg32/commdlg, shell/shell32, etc.)
149 having exactly the same load order. This will prevent mismatches at runtime.
150 See also configuration file format below.
153 Specify the DOS version
155 should imitate (e.g. 6.22) This option
156 is only valid when used in conjunction with --winver win31.
161 (one of Br, Ca, Cs, Cy, Da, De, En, Eo, Es, Fi, Fr, Ga, Gd, Gv, Hr,
162 Hu, It, Ko, Kw, No, Pl, Pt, Ru, Sk, Sv, Wa)
165 Create each top-level window as a properly managed X window instead of
166 creating our own "sticky" window.
169 Turn on synchronous display mode. Useful for debugging X11 graphics problems.
172 Specify which Windows version
175 Possible arguments are: win95, nt40, win31, win2000, win98, nt351, win30
178 .SH PROGRAM/ARGUMENTS
179 The program name may be specified in DOS format (
181 C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE)
183 .I /msdos/windows/sol.exe
184 ). You may pass arguments to the program being executed by adding them
185 to the end of the command line invoking
187 (such as: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT). Command line processing goes as
190 checks whether one or more of the above mentioned
192 options have been specified. These
193 are removed from the command line, which is passed to the windows program. You can use
198 should stop command line processing. This is needed in case a windows program understands
199 an option that is usually interpreted (and thus removed from the command line)
202 For example, if you want to execute
205 .I --managed --display :0.2
208 should run the program
211 .I --display 3d somefile
212 , then you could use the following command line to invoke
215 .I wine --managed --display :0.2 -- myapp.exe --display 3d somefile
217 Note that in contrast to previous versions of
220 program name and program option in one argument to
223 than one windows program, just execute
225 once with the name of each program as argument.
226 .SH ENVIRONMENT VARIABLES
228 makes the environment variables of the shell from which
230 is started accessible to the windows/dos processes started. So use the
231 appropriate syntax for your shell to enter environment variables you need.
234 If set, the content of this variable is taken as the name of the directory where
236 stores its data (the default is
238 ). This directory contains also the socket, which is used to communicate with the
242 processes using the same
244 (i.e.: same user) share certain things like registry and shared memory.
247 to different values for different
249 processes, it is possible to run a number of truly independent
254 Specifies the path and name of the
256 binary. If not set, a file named "wineserver" is searched in the
257 path and in a few other likely locations.
260 Specifies the path and name of the
262 binary to use to launch new Windows processes. If not set, a binary
263 named "wine" is searched in the path and in a few other likely
267 Specifies the path(s) in which to search for builtin dll files. This
268 is a list of directories separated by ":". Builtin dlls are also
269 searched in the directories specified by the standard
271 if they are not found in the directories listed in
274 .SH CONFIGURATION FILE
276 expects a configuration file (
277 .I @sysconfdir@/wine.conf
278 ), which must conform to the format specified in the
280 man page. A sample configuration file is documentation/samples/config in the
282 source archive. Alternatively a configuration file with the name
284 in the ~/.wine directory of the user running
289 is available thanks to the work of many developers. For a listing
290 of the authors, please see the file
292 in the top-level directory of the source distribution.
295 can be distributed under the terms of the X11 license. A copy of the
296 license is in the file
298 in the top-level directory of the source distribution.
301 A status report on many applications is available from
302 .I http://www.winehq.com/Apps.
303 Please add entries to this list for applications you currently run.
305 Bug reports and successes may be posted to
306 .I comp.emulators.ms-windows.wine.
307 If you want to post a bug report, please read the file
308 .I documentation/bugreports
311 source to see what information is necessary (FIXME: outdated).
313 For problems and suggestions with this manpage, please send a note to
314 James Juran <jrj120@psu.edu>.
316 The most recent public version of
318 can be obtained via FTP from ibiblio.org in the
319 /pub/Linux/ALPHA/Wine/development directory. The releases are in the
320 format 'Wine-yyyymmdd.tar.gz', or 'Wine-yyyymmdd.diff.gz' for the
321 diff's from the previous release. The same directory holds the
322 pre-built contents of the documentation in various formats
325 The latest snapshot of the code may be obtained via CVS. For information
326 on how to do this, please see
328 http://www.winehq.com/dev.html
332 development headquarters, is at
333 .I http://www.winehq.com/.
334 This website contains a great deal of information about
340 .I comp.emulators.ms-windows.wine.
341 It is used for discussion of various
342 .B wine end user aspects/help.
344 For further information about
346 development, you might want to subscribe to the
348 "cvs", "devel" and "patches" mailing lists at
349 .I http://www.winehq.com/dev.html#ml.
358 .I @prefix@/bin/dosmod
359 The DOS program loader.
361 .I @prefix@/bin/wineserver
366 .I @prefix@/bin/winedbg
371 .I @prefix@/bin/wineclpsrv
381 .I @sysconfdir@/wine.conf
382 Global configuration file for
386 User-specific configuration file
389 Directory containing user specific data managed by