2 .TH WINE 1 "May 2002" "@PACKAGE_STRING@" "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
23 For running CUI executables (Windows console programs), use
27 . This will display all the output in a separate windows (this requires X11 to
30 for CUI programs will only provide very limited console support, and your
31 program might not function properly.
34 currently runs a growing list of applications written for all kinds of
35 Windows versions >= Win2.0, e.g. Win3.1, Win95/98, NT.
36 Older, simpler applications work better than newer, more complex ones.
37 Using Windows ME or Win2000 components with Wine is more problematic than
38 using none at all or the ones from older Windows versions.
39 A large percentage of the API has been implemented,
40 although there are still several major pieces of work left to do.
41 .SH REQUIREMENTS AND INSTALLATION
42 Read the README file in the Wine source distribution and the wine.conf
43 man page to know what Wine requires and how it is installed from source.
46 .I --debugmsg [xxx]#name[,[xxx1]#name1][,<+|->relay=yyy1[:yyy2]]
47 Turn debugging messages on or off.
50 xxx is optional and can be one of the following:
56 If xxx is not specified, all debugging messages for the specified
57 channel are turned on. Each channel will print messages about a particular
60 # is required and can be either + or -. Note that
61 there is not a space after the comma between names. yyy are either the
62 name of a whole DLL or a single API entry by name you either
63 want to include or exclude from the relay listing. Case doesn't matter
64 for these. You can do the same for snoop.
68 .I --debugmsg warn+all
69 will turn on all warning messages (recommended for debugging)
71 .I --debugmsg warn+dll,+heap
72 will turn on DLL warning messages and all heap messages.
74 .I --debugmsg fixme-all,warn+cursor,+relay
75 will turn off all FIXME messages, turn on cursor warning messages, and turn
76 on all relay messages (API calls).
78 .I --debugmsg -relay=rtlleavecriticalsection:RtlEnterCriticalSection
79 will turn on all relay messages except for RtlLeaveCriticalSection and
80 RtlEnterCriticalSection.
82 .I --debugmsg +relay=advapi32
83 will only turn on relay messages into the ADVAPI32 code.
84 Never ever use simply --debugmsg +all ! Way too much info, and it crashes
85 way too easily, thus confusing unexperienced users.
87 The full list of names is:
88 all, accel, advapi, animate, aspi, atom, avifile, bitblt, bitmap, caret,
89 cdrom, class, clipboard, clipping, combo, comboex, comm, commctrl, commdlg,
90 console, crtdll, cursor, datetime, dc, ddeml, ddraw, debug, debugstr,
91 delayhlp, dialog, dinput, dll, dosfs, dosmem, dplay, driver, dsound, edit,
92 elfdll, enhmetafile, event, exec, file, fixup, font, gdi, global, graphics,
93 header, heap, hook, hotkey, icmp, icon, imagehlp, imagelist, imm, int, int10,
94 int16, int17, int19, int21, int31, io, ipaddress, joystick, key, keyboard,
95 loaddll, ldt, listbox, listview, local, mci, mcianim, mciavi, mcicda, mcimidi,
96 mciwave, mdi, menu, message, metafile, midi, mmaux, mmio, mmsys, mmtime,
97 module, monthcal, mpr, msacm, msg, msvideo, nativefont, nonclient, ntdll,
98 odbc, ole, opengl, pager, palette, pidl, print, process, profile, progress,
99 prop, propsheet, psapi, psdrv, ras, rebar, reg, region, relay, resource,
100 richedit, scroll, segment, seh, selector, sendmsg, server, setupapi,
101 setupx, shell, snoop, sound, static, statusbar, storage, stress, string,
102 syscolor, system, tab, tape, tapi, task, text, thread, thunk, timer, toolbar,
103 toolhelp, tooltips, trackbar, treeview, ttydrv, tweak, typelib, updown, ver,
104 virtual, vxd, wave, win, win16drv, win32, winedbg, wing, wininet, winsock,
105 winspool, wnet, x11 and x11drv.
108 For more information on debugging messages, see the file
109 .I documentation/running.sgml
110 in the source distribution (FIXME: outdated).
113 .I --dll name[,name[,...]]={native|so|builtin}[,{n|s|b}[,...]]
114 Selects the override type and load order of dll used in the loading
115 process for any dll. The default is set in the configuration
116 file. There are currently three types of libraries that can be loaded
117 into a process' address space: Native windows dlls (
119 ), native ELF libraries (
125 ). The type may be abbreviated with the first letter of the type (
127 ). Each sequence of orders must be separated by commas.
129 Each dll may have its own specific load order. The load order
130 determines which version of the dll is attempted to be loaded into the
131 address space. If the first fails, then the next is tried and so
132 on. Multiple libraries with the same load order can be separated with
133 commas. It is also possible to use the --dll option several times, to
134 specify different loadorders for different libraries
138 .I --dll comdlg32,commdlg=n,b
140 Try to load comdlg32 and commdlg as native windows dll first and try
141 the builtin version if the native load fails.
143 .I --dll shell,shell32=n --dll c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b
145 Try to load the libraries shell and shell32 as native windows dlls. Furthermore, if
146 an application request to load c:\(rsfoo\(rsbar\(rsbaz.dll load the builtin library baz.
148 .I --dll comdlg32,commdlg=b,n --dll shell,shell32=b --dll comctl32,commctrl=n
150 Try to load comdlg32 and commdlg as builtin first and try the native version
151 if the builtin load fails; load shell32/shell always as builtin and
152 comctl32/commctrl always as native.
154 Note: It is wise to keep dll pairs (comdlg32/commdlg, shell/shell32, etc.)
155 having exactly the same load order. This will prevent mismatches at runtime.
156 See also configuration file format below.
158 .SH PROGRAM/ARGUMENTS
159 The program name may be specified in DOS format (
161 C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE)
163 .I /msdos/windows/sol.exe
164 ). You may pass arguments to the program being executed by adding them
165 to the end of the command line invoking
167 (such as: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT).
168 Note that you need to '\(rs' escape special characters (and spaces) when invoking Wine via
171 wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe
173 Command line processing goes as
176 checks whether one or more of the above mentioned
178 options have been specified. These
179 are removed from the command line, which is passed to the windows program. You can use
184 should stop command line processing. This is needed in case a windows program understands
185 an option that is usually interpreted (and thus removed from the command line)
188 For example, if you want to execute
194 should run the program
197 .I --display 3d somefile
198 , then you could use the following command line to invoke
201 .I wine --dll riched32=n -- myapp.exe --display 3d somefile
203 Note that in contrast to previous versions of
206 program name and program option in one argument to
209 than one windows program, just execute
211 once with the name of each program as argument.
212 .SH ENVIRONMENT VARIABLES
214 makes the environment variables of the shell from which
216 is started accessible to the windows/dos processes started. So use the
217 appropriate syntax for your shell to enter environment variables you need.
220 If set, the content of this variable is taken as the name of the directory where
222 stores its data (the default is
224 ). This directory contains also the socket, which is used to communicate with the
228 processes using the same
230 (i.e.: same user) share certain things like registry, shared memory,
234 to different values for different
236 processes, it is possible to run a number of truly independent
241 Specifies the path and name of the
243 binary. If not set, Wine will try to load
244 .B @bindir@/wineserver,
245 and if this doesn't exist it will then look for a file named
246 "wineserver" in the path and in a few other likely locations.
249 Specifies the path and name of the
251 binary to use to launch new Windows processes. If not set, Wine will
254 and if this doesn't exist it will then look for a file named "wine" in
255 the path and in a few other likely locations.
258 Specifies the path(s) in which to search for builtin dlls and Winelib
259 applications. This is a list of directories separated by ":". In
260 addition to any directory specified in
262 Wine will also look in
266 Specifies the X11 display to use.
267 .SH CONFIGURATION FILE
269 expects a configuration file (
270 .I $WINEPREFIX/config
272 ), which must conform to the format specified in the
274 man page. A sample configuration file is documentation/samples/config in the
279 is available thanks to the work of many developers. For a listing
280 of the authors, please see the file
282 in the top-level directory of the source distribution.
285 can be distributed under the terms of the LGPL license. A copy of the
286 license is in the file
288 in the top-level directory of the source distribution.
291 A status report on many applications is available from
292 .I http://www.winehq.com/Apps.
293 Please add entries to this list for applications you currently run.
295 Bug reports may be posted to Wine Bugzilla
296 .I http://bugs.winehq.com
297 If you want to post a bug report, please read the file
298 .I documentation/bugs.sgml
301 source to see what information is necessary
303 Problems and suggestions with this manpage please also report to
304 .I http://bugs.winehq.com
306 The most recent public version of
308 can be obtained via FTP from ibiblio.org in the
309 /pub/Linux/ALPHA/Wine/development directory. The releases are in the
310 format 'Wine-yyyymmdd.tar.gz', or 'Wine-yyyymmdd.diff.gz' for the
311 diff's from the previous release. The same directory holds the
312 pre-built contents of the documentation in various formats
315 The latest snapshot of the code may be obtained via CVS. For information
316 on how to do this, please see
318 http://www.winehq.com/development/
322 development headquarters, is at
323 .I http://www.winehq.com/.
324 This website contains a great deal of information about
330 .I comp.emulators.ms-windows.wine.
331 It is used for discussion of various
332 .B wine end user aspects/help.
334 For further information about
336 development, you might want to subscribe to the
339 .I http://www.winehq.com/development/#ml
348 .I @bindir@/wineconsole
351 program loader for CUI (console) applications.
353 .I @bindir@/wineserver
363 .I @bindir@/wineclipsrv
374 User-specific configuration file
377 Directory containing user specific data managed by
projects / wine / blob