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 wineconsole for CUI programs will only provide very limited console support, and your program might not function properly.
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 and the wine.conf man page to know what Wine requires and how it is installed from source.
OPTIONS
--debugmsg [xxx]#name[,[xxx1]#name1]
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 specified, 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 matter for these. You can do the same for snoop.
For instance:
--debugmsg warn+all will turn on all warning messages (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 will turn on all relay messages. For more control on including or excluding functions and dlls look into the [Debug] section of the wine configuration file.
The full list of names is: all, accel, advapi, animate, 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, graphics, header, heap, hook, hotkey, icmp, icon, imagehlp, imagelist, imm, int, int10, int16, int17, int19, int21, int31, io, ipaddress, joystick, key, keyboard, loaddll, 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, opengl, pager, palette, pidl, print, process, profile, progress, prop, propsheet, psapi, psdrv, ras, rebar, reg, region, relay, resource, richedit, scroll, segment, seh, selector, sendmsg, server, setupapi, 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, wininet, winsock, winspool, wnet, x11 and x11drv.
For more information on debugging messages, see the file documentation/running.sgml in the source distribution (FIXME: outdated).
--dll name[,name[,...]]={native|builtin}[,{n|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 windows dlls ( native ), wine internal dlls ( builtin ). The type may be abbreviated with the first letter of the type ( n, b ). Each sequence of orders must be separated 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 different 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:rsrsfoorsrsbarrsrsbaz=b
Try to load the libraries shell and shell32 as native windows dlls. Furthermore, if an application request to load c:rsfoorsbarrsbaz.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/commdlg, shell/shell32, etc.) having exactly the same load order. This will prevent mismatches at runtime. See also configuration file format below.
PROGRAM/ARGUMENTS
The program name may be specified in DOS format ( C:rsrsWINDOWSrsrsSOL.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:rsrsTEMPrsrsREADME.TXT). Note that you need to 'rs' escape special characters (and spaces) when invoking Wine via a shell, e.g.
wine C:rsrsProgramrs FilesrsrsMyPrgrsrstest.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 --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 --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 argument 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 processes 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 communicate 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.
WINESERVER
Specifies the path and name of the wineserver binary. If not set, Wine will try to load /usr/lib/wine/bin/wineserver, and if this doesn't exist it will then look for a file named "wineserver" 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, Wine will try to load /usr/lib/wine/bin/wine, and if this doesn't exist it will then look for a file named "wine" in the path and in a few other likely locations.
WINEDLLPATH
Specifies the path(s) in which to search for builtin dlls and Winelib applications. This is a list of directories separated by ":". In addition to any directory specified in WINEDLLPATH, Wine will also look in /usr/lib/wine/lib/wine.
DISPLAY
Specifies the X11 display to use.
CONFIGURATION FILE
wine expects a configuration file ( $WINEPREFIX/config (~/.wine/config) ), which must conform to the format specified in the wine.conf(5) 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 LGPL license. A copy of the license is in the file LICENSE in the top-level directory of the source distribution.
ion of wine can be obtained via FTP from ibiblio.org in the /pub/Linux/ALPHA/Wine/development 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).
