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|builtin}[,{n|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 (
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
123 determines which version of the dll is attempted to be loaded into the
124 address space. If the first fails, then the next is tried and so
125 on. Multiple libraries with the same load order can be separated with
126 commas. It is also possible to use the --dll option several times, to
127 specify different loadorders for different libraries
131 .I --dll comdlg32,commdlg=n,b
133 Try to load comdlg32 and commdlg as native windows dll first and try
134 the builtin version if the native load fails.
136 .I --dll shell,shell32=n --dll c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b
138 Try to load the libraries shell and shell32 as native windows dlls. Furthermore, if
139 an application request to load c:\(rsfoo\(rsbar\(rsbaz.dll load the builtin library baz.
141 .I --dll comdlg32,commdlg=b,n --dll shell,shell32=b --dll comctl32,commctrl=n
143 Try to load comdlg32 and commdlg as builtin first and try the native version
144 if the builtin load fails; load shell32/shell always as builtin and
145 comctl32/commctrl always as native.
147 Note: It is wise to keep dll pairs (comdlg32/commdlg, shell/shell32, etc.)
148 having exactly the same load order. This will prevent mismatches at runtime.
149 See also configuration file format below.
151 .SH PROGRAM/ARGUMENTS
152 The program name may be specified in DOS format (
154 C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE)
156 .I /msdos/windows/sol.exe
157 ). You may pass arguments to the program being executed by adding them
158 to the end of the command line invoking
160 (such as: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT).
161 Note that you need to '\(rs' escape special characters (and spaces) when invoking Wine via
164 wine C:\(rs\(rsProgram\(rs Files\(rs\(rsMyPrg\(rs\(rstest.exe
166 Command line processing goes as
169 checks whether one or more of the above mentioned
171 options have been specified. These
172 are removed from the command line, which is passed to the windows program. You can use
177 should stop command line processing. This is needed in case a windows program understands
178 an option that is usually interpreted (and thus removed from the command line)
181 For example, if you want to execute
187 should run the program
190 .I --display 3d somefile
191 , then you could use the following command line to invoke
194 .I wine --dll riched32=n -- myapp.exe --display 3d somefile
196 Note that in contrast to previous versions of
199 program name and program option in one argument to
202 than one windows program, just execute
204 once with the name of each program as argument.
205 .SH ENVIRONMENT VARIABLES
207 makes the environment variables of the shell from which
209 is started accessible to the windows/dos processes started. So use the
210 appropriate syntax for your shell to enter environment variables you need.
213 If set, the content of this variable is taken as the name of the directory where
215 stores its data (the default is
217 ). This directory contains also the socket, which is used to communicate with the
221 processes using the same
223 (i.e.: same user) share certain things like registry, shared memory,
227 to different values for different
229 processes, it is possible to run a number of truly independent
234 Specifies the path and name of the
236 binary. If not set, Wine will try to load
237 .B @bindir@/wineserver,
238 and if this doesn't exist it will then look for a file named
239 "wineserver" in the path and in a few other likely locations.
242 Specifies the path and name of the
244 binary to use to launch new Windows processes. If not set, Wine will
247 and if this doesn't exist it will then look for a file named "wine" in
248 the path and in a few other likely locations.
251 Specifies the path(s) in which to search for builtin dlls and Winelib
252 applications. This is a list of directories separated by ":". In
253 addition to any directory specified in
255 Wine will also look in
259 Specifies the X11 display to use.
260 .SH CONFIGURATION FILE
262 expects a configuration file (
263 .I $WINEPREFIX/config
265 ), which must conform to the format specified in the
267 man page. A sample configuration file is documentation/samples/config in the
272 is available thanks to the work of many developers. For a listing
273 of the authors, please see the file
275 in the top-level directory of the source distribution.
278 can be distributed under the terms of the LGPL license. A copy of the
279 license is in the file
281 in the top-level directory of the source distribution.
284 A status report on many applications is available from
285 .I http://www.winehq.com/Apps.
286 Please add entries to this list for applications you currently run.
288 Bug reports may be posted to Wine Bugzilla
289 .I http://bugs.winehq.com
290 If you want to post a bug report, please read the file
291 .I documentation/bugs.sgml
294 source to see what information is necessary
296 Problems and suggestions with this manpage please also report to
297 .I http://bugs.winehq.com
299 The most recent public version of
301 can be obtained via FTP from ibiblio.org in the
302 /pub/Linux/ALPHA/Wine/development directory. The releases are in the
303 format 'Wine-yyyymmdd.tar.gz', or 'Wine-yyyymmdd.diff.gz' for the
304 diff's from the previous release. The same directory holds the
305 pre-built contents of the documentation in various formats
308 The latest snapshot of the code may be obtained via CVS. For information
309 on how to do this, please see
311 http://www.winehq.com/development/
315 development headquarters, is at
316 .I http://www.winehq.com/.
317 This website contains a great deal of information about
323 .I comp.emulators.ms-windows.wine.
324 It is used for discussion of various
325 .B wine end user aspects/help.
327 For further information about
329 development, you might want to subscribe to the
332 .I http://www.winehq.com/development/#ml
341 .I @bindir@/wineconsole
344 program loader for CUI (console) applications.
346 .I @bindir@/wineserver
356 .I @bindir@/wineclipsrv
367 User-specific configuration file
370 Directory containing user specific data managed by
projects / wine / blob