2 .TH WINE 1 "February 3, 1999" "Version 990131" "Windows On Unix"
4 wine \- run Windows programs on Unix
6 .BI "wine " "[wine_options] " "program1 " "[program2 ... ]"
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,
19 currently runs a growing list of applications written for both Win3.1 and
20 Win95. Older, simpler applications work better than newer, more complex
21 ones. A large percentage of the API has been implemented, although there
22 are still several major pieces of work left to do.
26 will run under any Linux kernel more recent than 0.99.13, or
27 under recent releases of NetBSD/i386, FreeBSD and OpenBSD/i386. Some bugs
28 were fixed and additional features were added late in the Linux 2.0.x
29 series, so if you have an old Linux kernel, you may want to upgrade to the
30 latest 2.0.x release. If you have FreeBSD, make sure you have the USER_LDT,
31 SYSVSHM, SYSVSEM, and SYSVMSG options turned on in your kernel. If you
32 are building Wine on Solaris, you will most likely need to build Wine
33 with the GNU toolchain (gcc, gas, etc.)
35 The current support for multithreaded applications relies on the
37 system call, which is currently only available on Linux. It should be
38 possible to implement this for other operating systems, however.
41 must be installed. To use Wine's support for multithreaded applications,
42 your X libraries must be reentrant. If you have libc6 (glibc2), or you
43 compiled the X libraries yourself, they were probably compiled with the
44 reentrant option enabled.
47 must be installed. If you're using Red Hat, make sure the following
48 packages are installed: XFree86-devel, xpm, and xpm-devel. If you're
49 using Debian, the packages you need are xpm4g and xpm4g-dev. If you
50 have some other distribution, please send a list of packages required
51 to the address listed in the
54 section to get it included in this man page.
57 2.7.x or later is required to build
59 Versions earlier than 2.7.2.3 may have problems when certain files are
60 compiled with optimization.
63 currently doesn't work with wine. The cause of this problem is unknown.
68 are required. Bison can be used in replace of yacc. If you have Redhat,
69 make sure the bison and flex packages are installed.
73 run "./configure" in the top-level directory of the source, which will
74 detect your specific setup and create the Makefiles. You can run
75 "./configure --help" to see the available configuration options. Then do
76 "make depend; make" to build the
78 executable, and then "make install" to install it. By default,
80 is installed in the /usr/local/ heirarchy; you can specify a different path with
81 the --prefix option when running
84 For more information, see the
86 file contained in the source distribution.
93 Use the named configuration file rather than the default
94 (/usr/local/etc/wine.conf or ~/.winerc).
97 Enter the debugger before starting application
99 .I -debugmsg [xxx]#name[,[xxx1]#name1][,<+|->relay=yyy1[:yyy2]]
100 Turn debugging messages on or off.
103 xxx is optional and can be one of the following:
109 If xxx is not specified, all debugging messages for the specified
110 channel are turned on. Each channel will print messages about a particular
111 component of Wine. # is required and can be either + or -. Note that
112 there is not a space after the comma between names. yyy are either the
113 name of a whole DLL or a single API entry by Name you either
114 want to include or exclude from the relay listing. These names must be in
115 the case as names used in the relaylisting. You can do the same for snoop.
119 .I -debugmsg warn+dll,+heap
120 will turn on DLL warning messages and all heap messages.
122 .I -debugmsg fixme-all,warn+cursor,+relay
123 will turn off all FIXME messages, turn on cursor warning messages, and turn
124 on all relay messages (API calls).
126 .I -debugmsg -relay=LeaveCriticalSection:EnterCriticalSection
127 will turn on all relay messages except for LeaveCriticalSection and
128 EnterCriticalSection.
130 .I -debugmsg +relay=ADVAPI32
131 will only turn on relay messages into the ADVAPI32 code.
133 The full list of names is: all, accel, advapi, animate, aspi, atom,
134 bitblt, bitmap, caret, cd, cdaudio, class, clipboard, clipping, combo,
135 comboex, comm, commctrl, commdlg, console, crtdll, cursor, datetime, dc,
136 dde, ddeml, ddraw, debug, dialog, dinput, dll, dosfs, dosmem, dplay, driver,
137 dsound, edit, event, exec, file, fixup, font, gdi, global, graphics, header,
138 heap, hook, hotkey, icon, imagehlp, imagelist, imm, int, int10, int16, int17,
139 int19, int21, int31, io, ipaddress, key, keyboard, ldt, listbox, listview,
140 local, mci, mcianim, mciwave, mdi, menu, message, metafile, midi, mmaux, mmio,
141 mmsys, mmtime, module, monthcal, mpr, msacm, msg, nativefont, nonclient, ntdll,
142 ole, pager, palette, pidl, print, process, profile, progress, prop, psapi,
143 psdrv, rebar, reg, region, relay, resource, s, scroll, security, segment,
144 selector, sem, sendmsg, server, shell, shm, snoop, sound, static, statusbar,
145 stress, string, syscolor, system, tab, task, text, thread, thunk, timer,
146 toolbar, toolhelp, tooltips, trackbar, treeview, tweak, uitools, updown, ver,
147 virtual, vxd, win, win16drv, win32, wing, winsock, wnet, x11, x11drv.
149 For more information on debugging messages, see the file
150 .I documentation/debug-msgs
151 in the source distribution.
155 Change the depth to use for multiple-depth screens
158 Use a desktop window of the given geometry
161 Use the specified display
164 Enables/disables built-in DLL's - starting wine with
166 is probably a good idea.
167 The full list of DLLs modifiable by this is:
168 ADVAPI32, AVIFILE, COMCTL32, COMDLG32, COMM, COMMDLG, COMPOBJ, CRTDLL,
169 DCIMAN32, DDEML, DDRAW, DINPUT, DISPLAY, DPLAY, DPLAYX, DSOUND, GDI, GDI32,
170 IMAGEHLP, IMM32, KEYBOARD, LZ32, LZEXPAND, MMSYSTEM, MOUSE, MPR, MSACM,
171 MSACM32, MSNET32, MSVFW32, MSVIDEO, OLE2, OLE32, OLE2CONV, OLE2DISP, OLE2NLS,
172 OLE2PROX, OLE2THK, OLEAUT32, OLECLI, OLECLI32, OLEDLG, OLESVR, OLESVR32,
173 PSAPI, RASAPI16, RASAPI32, SHELL, SHELL32, SOUND, STORAGE, STRESS, SYSTEM,
174 TAPI32, TOOLHELP, TYPELIB, USER, USER32, VER, VERSION, W32SKRNL, W32SYS,
175 WIN32S16, WIN87EM, WINASPI, WINDEBUG, WINEPS, WINMM, WING, WINSOCK, WINSPOOL,
176 WNASPI32, WOW32, WPROCS, WSOCK32
179 Read only files may not be opened in write mode (the default is to
180 allow opening read-only files for writing, because most Windows
181 programs always request read-write access, even on CD-ROM drives...).
184 Use a "standard" color map.
192 (one of En, Es, De, No, Fr, Fi, Da, Cz, Eo, It, Ko, Hu, Pl, Po, Sw, Ca, Ru)
195 Create each top-level window as a properly managed X window
198 Determines the mode in which
200 is started. Possible mode names are
204 Enhanced mode is the default (when no -mode option is specified).
207 Set the application name
210 Use a private color map
213 Turn on synchronous display mode
216 Specify which Windows version WINE should imitate.
217 Possible arguments are: win31, win95, nt351, and nt40.
219 .SH PROGRAM/ARGUMENTS
220 The program name may be specified in DOS format (
222 C:\\WINDOWS\\SOL.EXE)
224 .I /msdos/windows/sol.exe
225 ). The program being executed may be passed arguments by adding them on
226 to the end of the command line invoking
228 (such as: wine "notepad C:\\TEMP\\README.TXT"). Note that
229 the program name and its arguments
231 be passed as a single parameter, which is usually accomplished by placing
232 them together in quotation marks. Multiple applications may be started
233 by placing all of them on the command line (such as: wine notepad clock).
234 .SH CONFIGURATION FILE
236 expects a configuration file (
237 .I /usr/local/etc/wine.conf
239 conform to the following rules (the format is just like a Windows .ini
240 file). The actual file name may be specified during the execution of
243 script with the --sysconfdir option. Alternatively, you may have a
245 file of this format in your home directory or have the environment variable
247 pointing to a configuration file, or use the -config option on the command
249 .SH ENVIRONMENT VARIABLES
251 makes the environment variables of the shell from which
253 is started accesible to the windows/dos processes started. So use the
254 appropriate syntax for your shell to enter environment variables you need.
255 .SH CONFIGURATION FILE FORMAT
256 All entries are grouped in sections; a section begins with the line
260 and continues until the next section starts. Individual entries
261 consist of lines of the form
265 The value can be any text string, optionally included in single or
266 double quotes; it can also contain references to environment variables
269 Supported section names and entries are listed below.
273 This section is used to specify the root directory and type of each
275 drive, since most Windows applications require a DOS/MS-Windows based
276 disk drive & directory scheme. There is one such section for every
277 drive you want to configure.
279 .I format: Path = <rootdirectory>
283 If you mounted your dos partition as
285 and installed Microsoft Windows in
286 C:\\WINDOWS then you should specify
292 .I format: Type = <type>
296 Used to specify the drive type; supported types are floppy, hd, cdrom
299 .I format: Label = <label>
303 Used to specify the drive label; limited to 11 characters.
305 .I format: Serial = <serial>
309 Used to specify the drive serial number, as an 8-character hexadecimal
312 .I format: Filesystem = <fstype>
316 Used to specify the type of the file system Wine should emulate on a given
317 directory structure/underlying file system.
319 Supported types are msdos (or fat), win95 (or vfat), unix.
323 win95 for ext2fs, VFAT and FAT32
325 msdos for FAT16 (ugly)
327 You definitely don't want to use "unix" unless you intend to port programs using Winelib.
329 Always try to avoid using FAT16. Use VFAT/FAT32 OS file system driver instead !
333 .I format: windows = <directory>
337 Used to specify a different Windows directory
339 .I format: system = <directory>
341 default: C:\\WINDOWS\\SYSTEM
343 Used to specify a different system directory
345 .I format: temp = <directory>
349 Used to specify a directory where Windows applications can store
352 .I format: path = <directories separated by semi-colons>
354 default: C:\\WINDOWS;C:\\WINDOWS\\SYSTEM
356 Used to specify the path which will be used to find executables and .DLL's.
358 .I format: symboltablefile = <filename>
362 Used to specify the path and file name of the symbol table used by the built-in
367 .I format: com[12345678] = <devicename>
371 Used to specify the devices which are used as com1 - com8.
375 .I format: lpt[12345678] = <devicename>
379 Used to specify the devices which are used as lpt1 - lpt8.
383 .I format: file = <filename or CON when logging to stdout>
387 Used to specify the file which will be used as
390 .I format: exclude = <message names separated by semicolons>
394 Used to specify which messages will be excluded from the logfile.
396 .I format: include = <message names separated by semicolons>
399 .br Used to specify which messages will be included in the logfile.
403 .I format: WineLook=<Win31|Win95|Win98>
407 Use Win95-like window displays or Win3.1-like window displays.
408 .SH SAMPLE CONFIGURATION FILE
409 A sample configuration file is distributed as
411 in the top-level directory of the source distribution.
414 is available thanks to the work of many developers. For a listing
415 of the authors, please see the file
417 in the top-level directory of the source distribution.
420 A status report on many appplications is available from
421 .I http://www.winehq.com/Apps.
422 Please add entries to this list for applications you currently run.
424 Bug reports and successes may be posted to
425 .I comp.emulators.ms-windows.wine.
426 If you want to post a bug report, please read the file
427 .I documentation/bugreports
428 in the Wine source to see what information is necessary.
430 For problems and suggestions with this manpage, please send a note to
431 James Juran <jrj120@psu.edu>.
433 The most recent public version of
435 can be obtained via FTP from metalab.unc.edu or tsx-11.mit.edu in the
436 /pub/linux/ALPHA/Wine/development directory. The releases are in the
437 format 'Wine-yymmdd.tar.gz', or 'Wine-yymmdd.diff.gz' for the diff's
438 from the previous release.
440 The latest snapshot of the code may be obtained via CVS. For information
441 on how to do this, please see
443 http://www.winehq.com/dev.html
447 development headquarters, is at
448 .I http://www.winehq.com/.
449 This website contains a great deal of information about
451 as well as a collection of unofficial patches against the current release.
456 .I comp.emulators.ms-windows.wine.
457 All discussions about the project take place in this forum.
461 .I /usr/local/bin/wine
462 The Wine program loader.
464 .I /usr/local/bin/dosmod
465 The DOS program loader.
467 .I /usr/local/etc/wine.conf
468 Global configuration file for wine.
471 User-specific configuration file
473 .I /usr/local/lib/wine.sym
474 Global symbol table (used in debugger)