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]
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).
79 will turn on all relay messages. For more control on including or excluding
80 functions and dlls look into the [Debug] section of the wine configuration file.
82 The full list of names is:
83 all, accel, advapi, animate, aspi, atom, avifile, bitblt, bitmap, caret,
84 cdrom, class, clipboard, clipping, combo, comboex, comm, commctrl, commdlg,
85 console, crtdll, cursor, datetime, dc, ddeml, ddraw, debug, debugstr,
86 delayhlp, dialog, dinput, dll, dosfs, dosmem, dplay, driver, dsound, edit,
87 elfdll, enhmetafile, event, exec, file, fixup, font, gdi, global, graphics,
88 header, heap, hook, hotkey, icmp, icon, imagehlp, imagelist, imm, int, int10,
89 int16, int17, int19, int21, int31, io, ipaddress, joystick, key, keyboard,
90 loaddll, ldt, listbox, listview, local, mci, mcianim, mciavi, mcicda, mcimidi,
91 mciwave, mdi, menu, message, metafile, midi, mmaux, mmio, mmsys, mmtime,
92 module, monthcal, mpr, msacm, msg, msvideo, nativefont, nonclient, ntdll,
93 odbc, ole, opengl, pager, palette, pidl, print, process, profile, progress,
94 prop, propsheet, psapi, psdrv, ras, rebar, reg, region, relay, resource,
95 richedit, scroll, segment, seh, selector, sendmsg, server, setupapi,
96 setupx, shell, snoop, sound, static, statusbar, storage, stress, string,
97 syscolor, system, tab, tape, tapi, task, text, thread, thunk, timer, toolbar,
98 toolhelp, tooltips, trackbar, treeview, ttydrv, tweak, typelib, updown, ver,
99 virtual, vxd, wave, win, win16drv, win32, winedbg, wing, wininet, winsock,
100 winspool, wnet, x11 and x11drv.
103 For more information on debugging messages, see the file
104 .I documentation/running.sgml
105 in the source distribution (FIXME: outdated).
108 .I --dll name[,name[,...]]={native|so|builtin}[,{n|s|b}[,...]]
109 Selects the override type and load order of dll used in the loading
110 process for any dll. The default is set in the configuration
111 file. There are currently three types of libraries that can be loaded
112 into a process' address space: Native windows dlls (
114 ), native ELF libraries (
120 ). The type may be abbreviated with the first letter of the type (
122 ). Each sequence of orders must be separated by commas.
124 Each dll may have its own specific load order. The load order
125 determines which version of the dll is attempted to be loaded into the
126 address space. If the first fails, then the next is tried and so
127 on. Multiple libraries with the same load order can be separated with
128 commas. It is also possible to use the --dll option several times, to
129 specify different loadorders for different libraries
133 .I --dll comdlg32,commdlg=n,b
135 Try to load comdlg32 and commdlg as native windows dll first and try
136 the builtin version if the native load fails.
138 .I --dll shell,shell32=n --dll c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b
140 Try to load the libraries shell and shell32 as native windows dlls. Furthermore, if
141 an application request to load c:\(rsfoo\(rsbar\(rsbaz.dll load the builtin library baz.
143 .I --dll comdlg32,commdlg=b,n --dll shell,shell32=b --dll comctl32,commctrl=n
145 Try to load comdlg32 and commdlg as builtin first and try the native version
146 if the builtin load fails; load shell32/shell always as builtin and
147 comctl32/commctrl always as native.
149 Note: It is wise to keep dll pairs (comdlg32/commdlg, shell/shell32, etc.)
150 having exactly the same load order. This will prevent mismatches at runtime.
151 See also configuration file format below.
153 .SH PROGRAM/ARGUMENTS
154 The program name may be specified in DOS format (
156 C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE)
158 .I /msdos/windows/sol.exe
159 ). You may pass arguments to the program being executed by adding them
160 to the end of the command line invoking
162 (such as: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT).
163 Note that you need to '\(rs' escape special characters (and spaces) when invoking Wine via
166 wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe
168 Command line processing goes as
171 checks whether one or more of the above mentioned
173 options have been specified. These
174 are removed from the command line, which is passed to the windows program. You can use
179 should stop command line processing. This is needed in case a windows program understands
180 an option that is usually interpreted (and thus removed from the command line)
183 For example, if you want to execute
189 should run the program
192 .I --display 3d somefile
193 , then you could use the following command line to invoke
196 .I wine --dll riched32=n -- myapp.exe --display 3d somefile
198 Note that in contrast to previous versions of
201 program name and program option in one argument to
204 than one windows program, just execute
206 once with the name of each program as argument.
207 .SH ENVIRONMENT VARIABLES
209 makes the environment variables of the shell from which
211 is started accessible to the windows/dos processes started. So use the
212 appropriate syntax for your shell to enter environment variables you need.
215 If set, the content of this variable is taken as the name of the directory where
217 stores its data (the default is
219 ). This directory contains also the socket, which is used to communicate with the
223 processes using the same
225 (i.e.: same user) share certain things like registry, shared memory,
229 to different values for different
231 processes, it is possible to run a number of truly independent
236 Specifies the path and name of the
238 binary. If not set, Wine will try to load
239 .B @bindir@/wineserver,
240 and if this doesn't exist it will then look for a file named
241 "wineserver" in the path and in a few other likely locations.
244 Specifies the path and name of the
246 binary to use to launch new Windows processes. If not set, Wine will
249 and if this doesn't exist it will then look for a file named "wine" in
250 the path and in a few other likely locations.
253 Specifies the path(s) in which to search for builtin dlls and Winelib
254 applications. This is a list of directories separated by ":". In
255 addition to any directory specified in
257 Wine will also look in
261 Specifies the X11 display to use.
262 .SH CONFIGURATION FILE
264 expects a configuration file (
265 .I $WINEPREFIX/config
267 ), which must conform to the format specified in the
269 man page. A sample configuration file is documentation/samples/config in the
274 is available thanks to the work of many developers. For a listing
275 of the authors, please see the file
277 in the top-level directory of the source distribution.
280 can be distributed under the terms of the LGPL license. A copy of the
281 license is in the file
283 in the top-level directory of the source distribution.
286 A status report on many applications is available from
287 .I http://www.winehq.com/Apps.
288 Please add entries to this list for applications you currently run.
290 Bug reports may be posted to Wine Bugzilla
291 .I http://bugs.winehq.com
292 If you want to post a bug report, please read the file
293 .I documentation/bugs.sgml
296 source to see what information is necessary
298 Problems and suggestions with this manpage please also report to
299 .I http://bugs.winehq.com
301 The most recent public version of
303 can be obtained via FTP from ibiblio.org in the
304 /pub/Linux/ALPHA/Wine/development directory. The releases are in the
305 format 'Wine-yyyymmdd.tar.gz', or 'Wine-yyyymmdd.diff.gz' for the
306 diff's from the previous release. The same directory holds the
307 pre-built contents of the documentation in various formats
310 The latest snapshot of the code may be obtained via CVS. For information
311 on how to do this, please see
313 http://www.winehq.com/development/
317 development headquarters, is at
318 .I http://www.winehq.com/.
319 This website contains a great deal of information about
325 .I comp.emulators.ms-windows.wine.
326 It is used for discussion of various
327 .B wine end user aspects/help.
329 For further information about
331 development, you might want to subscribe to the
334 .I http://www.winehq.com/development/#ml
343 .I @bindir@/wineconsole
346 program loader for CUI (console) applications.
348 .I @bindir@/wineserver
358 .I @bindir@/wineclipsrv
369 User-specific configuration file
372 Directory containing user specific data managed by