WINE(E) Windows On Unix WINE(E) NAME wine - run Windows programs on Unix SYNOPSIS wine [wine_options] [--] program [arguments ... ] For instructions on passing arguments to Windows programs, please see the PROGRAM/ARGUMENTS section of the man page. DESCRIPTION wine program loads and runs the given program, where the program is a DOS, Windows 3.x, or Win32 executable (x86 binaries only). For debugging wine, use winedbg program instead. For running CUI executables (Windows console programs), use wineconsole instead of wine run). Not using winecon- sole for CUI programs will only provide very limited con- sole support, and your program might not function prop- erly. wine currently runs a growing list of applications written for all kinds of Windows versions >= Win2.0, e.g. Win3.1, Win95/98, NT. Older, simpler applications work better than newer, more complex ones. Using Windows ME or Win2000 components with Wine is more problematic than using none at all or the ones from older Windows versions. A large percentage of the API has been implemented, although there are still several major pieces of work left to do. REQUIREMENTS AND INSTALLATION Read the README file in the Wine source distribution to know what Wine requires and how it is installed from source. OPTIONS --debugmsg [xxx]#name[,[xxx1]#name1][,<+|->relay=yyy1[:yyy2]] Turn debugging messages on or off. xxx is optional and can be one of the following: err, warn, fixme, or trace. If xxx is not speci- fied, all debugging messages for the specified channel are turned on. Each channel will print messages about a particular component of wine. # is required and can be either + or -. Note that there is not a space after the comma between names. yyy are either the name of a whole DLL or a single API entry by name you either want to include or exclude from the relay listing. Case doesn't mat- ter for these. You can do the same for snoop. For instance: --debugmsg warn+all will turn on all warning mes- sages (recommended for debugging) --debugmsg warn+dll,+heap will turn on DLL warning messages and all heap messages. --debugmsg fixme-all,warn+cursor,+relay will turn off all FIXME messages, turn on cursor warning messages, and turn on all relay messages (API calls). --debugmsg -relay=rtlleavecriticalsection:RtlEnter- CriticalSection will turn on all relay messages except for RtlLeaveCriticalSection and RtlEnter- CriticalSection. --debugmsg +relay=advapi32 will only turn on relay messages into the ADVAPI32 code. Never ever use simply --debugmsg +all ! Way too much info, and it crashes way too easily, thus confusing unexperi- enced users. The full list of names is: all, accel, advapi, ani- mate, aspi, atom, avifile, bitblt, bitmap, caret, cdrom, class, clipboard, clipping, combo, comboex, comm, commctrl, commdlg, console, crtdll, cursor, datetime, dc, ddeml, ddraw, debug, debugstr, delayhlp, dialog, dinput, dll, dosfs, dosmem, dplay, driver, dsound, edit, elfdll, enhmetafile, event, exec, file, fixup, font, gdi, global, graph- ics, header, heap, hook, hotkey, icmp, icon, imagehlp, imagelist, imm, int, int10, int16, int17, int19, int21, int31, io, ipaddress, joystick, key, keyboard, ldt, listbox, listview, local, mci, mcianim, mciavi, mcicda, mcimidi, mciwave, mdi, menu, message, metafile, midi, mmaux, mmio, mmsys, mmtime, module, monthcal, mpr, msacm, msg, msvideo, nativefont, nonclient, ntdll, odbc, ole, pager, palette, pidl, print, process, profile, progress, prop, propsheet, psapi, psdrv, ras, rebar, reg, region, relay, resource, scroll, segment, seh, selector, sendmsg, server, setupx, shell, snoop, sound, static, statusbar, storage, stress, string, syscolor, system, tab, tape, tapi, task, text, thread, thunk, timer, toolbar, toolhelp, tooltips, trackbar, treeview, ttydrv, tweak, typelib, updown, ver, virtual, vxd, wave, win, win16drv, win32, winedbg, wing, winsock, winspool, wnet, x11 and x11drv. For more information on debugging messages, see the file documentation/debug-msgs in the source distri- bution (FIXME: outdated). --dll name[,name[,...]]={native|so|builtin}[,{n|s|b}[,...]] Selects the override type and load order of dll used in the loading process for any dll. The default is set in the configuration file. There are currently three types of libraries that can be loaded into a process' address space: Native win- dows dlls ( native ), native ELF libraries ( so )and wine internal dlls ( builtin ). The type may be abbreviated with the first letter of the type ( n, s, b ). Each sequence of orders must be sepa- rated by commas. Each dll may have its own specific load order. The load order determines which version of the dll is attempted to be loaded into the address space. If the first fails, then the next is tried and so on. Multiple libraries with the same load order can be separated with commas. It is also possible to use the --dll option several times, to specify differ- ent loadorders for different libraries Examples: --dll comdlg32,commdlg=n,b Try to load comdlg32 and commdlg as native windows dll first and try the builtin version if the native load fails. --dll shell,shell32=n --dll c:\\foo\\bar\\baz=b Try to load the libraries shell and shell32 as native windows dlls. Furthermore, if an application request to load c:\foo\bar\baz.dll load the builtin library baz. --dll comdlg32,commdlg=b,n --dll shell,shell32=b --dll comctl32,commctrl=n Try to load comdlg32 and commdlg as builtin first and try the native version if the builtin load fails; load shell32/shell always as builtin and comctl32/commctrl always as native. Note: It is wise to keep dll pairs (comdlg32/com- mdlg, shell/shell32, etc.) having exactly the same load order. This will prevent mismatches at run- time. See also configuration file format below. --dosver version Specify the DOS version wine should imitate (e.g. 6.22) This option is only valid when used in con- junction with --winver win31. --managed Create each top-level window as a properly managed X window instead of creating our own "sticky" win- dow. --winver version Specify which Windows version wine should imitate. Possible arguments are: win95, win98, winme, nt351, nt40, win2000, winxp, win20, win30 and win31. PROGRAM/ARGUMENTS The program name may be specified in DOS format ( C:\\WIN- DOWS\\SOL.EXE) or in Unix format ( /msdos/windows/sol.exe ). You may pass arguments to the program being executed by adding them to the end of the command line invoking wine (such as: wine notepad C:\\TEMP\\README.TXT). Note that you need to '\' escape special characters (and spaces) when invoking Wine via a shell, e.g. wine C:\\Program\ Files\\MyPrg\\test.exe Command line processing goes as follows: first wine checks whether one or more of the above mentioned wine options have been specified. These are removed from the command line, which is passed to the windows program. You can use the parameter -- to indicate that wine should stop command line processing. This is needed in case a windows program understands an option that is usually interpreted (and thus removed from the command line) by wine. For example, if you want to execute wine with the options --managed --dll riched32=n and if wine should run the program myapp.exe with the arguments --display 3d somefile , then you could use the following command line to invoke wine: wine --managed --dll riched32=n -- myapp.exe --display 3d somefile Note that in contrast to previous versions of wine, you must not pass program name and program option in one argu- ment to wine. To run more than one windows program, just execute wine once with the name of each program as argument. ENVIRONMENT VARIABLES wine makes the environment variables of the shell from which wine is started accessible to the windows/dos pro- cesses started. So use the appropriate syntax for your shell to enter environment variables you need. WINEPREFIX If set, the content of this variable is taken as the name of the directory where wine stores its data (the default is $HOME/.wine ). This directory contains also the socket, which is used to communi- cate with the wineserver. All wine processes using the same wineserver (i.e.: same user) share certain things like registry, shared memory, and config file. By setting WINEPREFIX to different values for different wine processes, it is possible to run a number of truly independent wine processes. WINEPRELOAD If set, specifies the full name of a shared library that wine loads and runs as a Winelib application. WINESERVER Specifies the path and name of the wineserver binary. If not set, a file named "wineserver" is searched in the path and in a few other likely locations. WINELOADER Specifies the path and name of the wine binary to use to launch new Windows processes. If not set, a binary named "wine" is searched in the path and in a few other likely locations. WINEDLLPATH Specifies the path(h) in which to search for builtin dll files. This is a list of directories separated by ":". Builtin dlls are also searched in the directories specified by the standard LD_LIBRARY_PATH if they are not found in the direc- tories listed in WINEDLLPATH. DISPLAY Specifies the X11 display to use. CONFIGURATION FILE wine expects a configuration file ( $WINEPREFIX/config (~/.wine/config) ), which must conform to the format spec- ified in the wine.conf(f) man page. A sample configuration file is documentation/samples/config in the wine source archive. AUTHORS wine is available thanks to the work of many developers. For a listing of the authors, please see the file AUTHORS in the top-level directory of the source distribution. COPYRIGHT wine can be distributed under the terms of the X11 license. A copy of the license is in the file LICENSE in the top-level directory of the source distribution. BUGS A status report on many applications is available from http://www.winehq.com/Apps. Please add entries to this list for applications you currently run. Bug reports and successes may be posted to comp.emula- tors.ms-windows.wine. If you want to post a bug report, please read the file documentation/bugreports in the wine source to see what information is necessary (FIXME: out- dated). For problems and suggestions with this manpage, please send a note to James Juran <jrj120@psu.edu>. AVAILABILITY The most recent public version of wine can be obtained via FTP from ibiblio.org in the /pub/Linux/ALPHA/Wine/develop- ment directory. The releases are in the format 'Wine- yyyymmdd.tar.gz', or 'Wine-yyyymmdd.diff.gz' for the diff's from the previous release. The same directory holds the pre-built contents of the documentation in various formats (wine-doc.xxx.gz). The latest snapshot of the code may be obtained via CVS. For information on how to do this, please see http://www.winehq.com/dev.html WineHQ, the wine development headquarters, is at http://www.winehq.com/. This website contains a great deal of information about wine. The wine newsgroup is comp.emulators.ms-windows.wine. It is used for discussion of various wine end user aspects/help. For further information about wine development, you might want to subscribe to the wine "cvs", "devel" and "patches" mailing lists at http://www.winehq.com/dev.html#ml. FILES /home/ovek/dev/wine-0.0.20020411/debian/tmp/usr/bin/wine The wine program loader. /home/ovek/dev/wine-0.0.20020411/debian/tmp/usr/bin/winecon- sole The wine program loader for CUI (console) applica- tions. /home/ovek/dev/wine-0.0.20020411/debian/tmp/usr/bin/wine- server The wine server /home/ovek/dev/wine-0.0.20020411/debian/tmp/usr/bin/winedbg The wine debugger /home/ovek/dev/wine-0.0.20020411/debian/tmp/usr/bin/wineclp- srv The wine clipboard server /home/ovek/dev/wine-0.0.20020411/debian/tmp/usr/lib Directory containing wine's shared libraries ~/.wine/config User-specific configuration file ~/.wine Directory containing user specific data managed by wine. SEE ALSO wine.conf(f) Version 20011004 Oct 13, 2001 WINE(E)