2 .TH WINE 1 "Apr 19, 2001" "Version 20010418" "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).
100 .I --dll name[,name[,...]]={native|so|builtin}[,{n|s|b}[,...]]
101 Selects the override type and load order of dll used in the loading
102 process for any dll. The default is set in the configuration
103 file. There are currently three types of libraries that can be loaded
104 into a process' address space: Native windows dlls (
106 ), native ELF libraries (
112 ). The type may be abbreviated with the first letter of the type (
114 ). Each sequence of orders must be separated by commas.
116 Each dll may have its own specific load order. The load order
117 determines which version of the dll is attempted to be loaded into the
118 address space. If the first fails, then the next is tried and so
119 on. Multiple libraries with the same load order can be separated with
120 commas. It is also possible to use the --dll option several times, to
121 specify different loadorders for different libraries
125 .I --dll comdlg32,commdlg=n,b
127 Try to load comdlg32 and commdlg as native windows dll first and try
128 the builtin version if the native load fails.
130 .I --dll shell,shell32=n --dll c:\(rs\(rsfoo\(rs\(rsbar\(rs\(rsbaz=b
132 Try to load the libraries shell and shell32 as native windows dlls. Furthermore, if
133 an application request to load c:\(rsfoo\(rsbar\(rsbaz.dll load the builtin library baz.
135 .I --dll comdlg32,commdlg=b,n --dll shell,shell32=b --dll comctl32,commctrl=n
137 Try to load comdlg32 and commdlg as builtin first and try the native version
138 if the builtin load fails; load shell32/shell always as builtin and
139 comctl32/commctrl always as native.
141 Note: It is wise to keep dll pairs (comdlg32/commdlg, shell/shell32, etc.)
142 having exactly the same load order. This will prevent mismatches at runtime.
143 See also configuration file format below.
146 Specify the DOS version
148 should imitate (e.g. 6.22) This option
149 is only valid when used in conjunction with --winver win31.
152 Create each top-level window as a properly managed X window instead of
153 creating our own "sticky" window.
156 Specify which Windows version
159 Possible arguments are: win95, nt40, win31, win2000, win98, nt351, win30
162 .SH PROGRAM/ARGUMENTS
163 The program name may be specified in DOS format (
165 C:\(rs\(rsWINDOWS\(rs\(rsSOL.EXE)
167 .I /msdos/windows/sol.exe
168 ). You may pass arguments to the program being executed by adding them
169 to the end of the command line invoking
171 (such as: wine notepad C:\(rs\(rsTEMP\(rs\(rsREADME.TXT). Command line processing goes as
174 checks whether one or more of the above mentioned
176 options have been specified. These
177 are removed from the command line, which is passed to the windows program. You can use
182 should stop command line processing. This is needed in case a windows program understands
183 an option that is usually interpreted (and thus removed from the command line)
186 For example, if you want to execute
189 .I --managed --dll riched32=n
192 should run the program
195 .I --display 3d somefile
196 , then you could use the following command line to invoke
199 .I wine --managed --dll riched32=n -- myapp.exe --display 3d somefile
201 Note that in contrast to previous versions of
204 program name and program option in one argument to
207 than one windows program, just execute
209 once with the name of each program as argument.
210 .SH ENVIRONMENT VARIABLES
212 makes the environment variables of the shell from which
214 is started accessible to the windows/dos processes started. So use the
215 appropriate syntax for your shell to enter environment variables you need.
218 If set, the content of this variable is taken as the name of the directory where
220 stores its data (the default is
222 ). This directory contains also the socket, which is used to communicate with the
226 processes using the same
228 (i.e.: same user) share certain things like registry and shared memory.
231 to different values for different
233 processes, it is possible to run a number of truly independent
238 If set, specifies the full name of a shared library that
240 loads and runs as a Winelib application.
243 Specifies the path and name of the
245 binary. If not set, a file named "wineserver" is searched in the
246 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, a binary
252 named "wine" is searched in the path and in a few other likely
256 Specifies the path(s) in which to search for builtin dll files. This
257 is a list of directories separated by ":". Builtin dlls are also
258 searched in the directories specified by the standard
260 if they are not found in the directories listed in
264 Specifies the X11 display to use.
265 .SH CONFIGURATION FILE
267 expects a configuration file (
268 .I @sysconfdir@/wine.conf
269 ), which must conform to the format specified in the
271 man page. A sample configuration file is documentation/samples/config in the
273 source archive. Alternatively a configuration file with the name
275 in the ~/.wine directory of the user running
280 is available thanks to the work of many developers. For a listing
281 of the authors, please see the file
283 in the top-level directory of the source distribution.
286 can be distributed under the terms of the X11 license. A copy of the
287 license is in the file
289 in the top-level directory of the source distribution.
292 A status report on many applications is available from
293 .I http://www.winehq.com/Apps.
294 Please add entries to this list for applications you currently run.
296 Bug reports and successes may be posted to
297 .I comp.emulators.ms-windows.wine.
298 If you want to post a bug report, please read the file
299 .I documentation/bugreports
302 source to see what information is necessary (FIXME: outdated).
304 For problems and suggestions with this manpage, please send a note to
305 James Juran <jrj120@psu.edu>.
307 The most recent public version of
309 can be obtained via FTP from ibiblio.org in the
310 /pub/Linux/ALPHA/Wine/development directory. The releases are in the
311 format 'Wine-yyyymmdd.tar.gz', or 'Wine-yyyymmdd.diff.gz' for the
312 diff's from the previous release. The same directory holds the
313 pre-built contents of the documentation in various formats
316 The latest snapshot of the code may be obtained via CVS. For information
317 on how to do this, please see
319 http://www.winehq.com/dev.html
323 development headquarters, is at
324 .I http://www.winehq.com/.
325 This website contains a great deal of information about
331 .I comp.emulators.ms-windows.wine.
332 It is used for discussion of various
333 .B wine end user aspects/help.
335 For further information about
337 development, you might want to subscribe to the
339 "cvs", "devel" and "patches" mailing lists at
340 .I http://www.winehq.com/dev.html#ml.
349 .I @prefix@/bin/dosmod
350 The DOS program loader.
352 .I @prefix@/bin/wineserver
357 .I @prefix@/bin/winedbg
362 .I @prefix@/bin/wineclpsrv
372 .I @sysconfdir@/wine.conf
373 Global configuration file for
377 User-specific configuration file
380 Directory containing user specific data managed by
projects / wine / blob