WINE(1) Windows On Unix WINE(1)
NAME
wine(1,5) - run Windows programs on Unix
SYNOPSIS
wine(1,5) [wine_options] [--] program [arguments ... ]
For instructions on passing arguments to Windows programs, please see
the PROGRAM/ARGUMENTS section of the man(1,5,7) page.
DESCRIPTION
wine(1,5) loads and runs the given program, where the program is a DOS, Win-
dows 3.x, or Win32 executable (x86 binaries only).
For debugging wine(1,5), use winedbg instead.
For running CUI executables (Windows console(4,n) programs), use wineconsole
instead of wine. This will display all the output in(1,8) a separate win-
dows (this requires X11 to run). Not using wineconsole for CUI programs
will only provide very limited console(4,n) support, and your program might
not function properly.
wine(1,5) 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(1,n) in(1,8) the Wine source distribution and the
wine.conf(5) man(1,5,7) 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. This option is deprecated,
you should use the WINEDEBUG environment variable instead (see
below).
PROGRAM/ARGUMENTS
The program name may be specified in(1,8) DOS format ( C:\\WINDOWS\\SOL.EXE)
or in(1,8) 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(1,5) (such as: wine(1,5) notepad C:\\TEMP\\README.TXT). Note
that you need to '\' escape special characters (and spaces) when invok-
ing Wine via a shell, e.g.
wine(1,5) C:\\Program\ Files\\MyPrg\\test.exe
Command line processing goes as follows: first wine(1,5) checks whether one
or more of the above mentioned wine(1,5) options have been specified. These
are removed from the command line, which is passed to the windows pro-
gram. You can use the parameter -- to indicate that wine(1,5) should stop
command line processing. This is needed in(1,8) case a windows program
understands an option that is usually interpreted (and thus removed
from the command line) by wine. For example, if(3,n) you want to execute
wine(1,5) with the options --debugmsg +module and if(3,n) wine(1,5) should run the
program myapp.exe with the arguments --display 3d somefile , then you
could use the following command line to invoke wine:
wine(1,5) --debugmsg +module -- myapp.exe --display 3d somefile
Note that in(1,8) contrast to previous versions of wine(1,5), you must not pass
program name and program option in(1,8) one argument to wine. To run more
than one windows program, just execute wine(1,5) once with the name of each
program as argument.
ENVIRONMENT VARIABLES
wine(1,5) makes the environment variables of the shell from which wine(1,5) 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(7,n,1 builtins), the content of this variable is taken as the name of the
directory where wine(1,5) stores its data (the default is $HOME/.wine
). This directory is also used to identify the socket(2,7,n) which is
used to communicate with the wineserver. All wine(1,5) processes
using the same wineserver (i.e.: same user) share certain things
like registry, shared memory, and config(1,5) file. By setting
WINEPREFIX to different values for different wine(1,5) processes, it
is possible to run a number of truly independent wine(1,5) processes.
WINESERVER
Specifies the path and name of the wineserver binary. If not
set(7,n,1 builtins), Wine will try to load(7,n) /usr/bin/wineserver, and if(3,n) this
doesn't exist it will then look(1,8,3 Search::Dict) for a file(1,n) named(5,8) "wineserver" in(1,8)
the path and in(1,8) a few other likely locations.
WINELOADER
Specifies the path and name of the wine(1,5) binary to use to launch
new Windows processes. If not set(7,n,1 builtins), Wine will try to load(7,n)
/usr/bin/wine(1,5), and if(3,n) this doesn't exist it will then look(1,8,3 Search::Dict) for a
file(1,n) named(5,8) "wine(1,5)" in(1,8) the path and in(1,8) a few other likely loca-
tions.
WINEDEBUG
Turns debugging messages on or off. The syntax of the variable
is of the form [class][+/-]channel[,[class2][+/-]channel2].
class is optional and can be one of the following: err, warn,
fixme, or trace. If class is not specified, all debugging mes-
sages for the specified channel are turned on. Each channel
will print messages about a particular component of wine. The
following character can be either + or - to switch(1,n) the specified
channel on or off respectively. If there is no class part
before it, a leading + can be omitted. Note that spaces are not
allowed anywhere in(1,8) the string.
Examples:
WINEDEBUG=warn+all
will turn on all warning messages (recommended for debug-
ging).
WINEDEBUG=warn+dll,+heap
will turn on DLL warning messages and all heap messages.
WINEDEBUG=fixme-all,warn+cursor,+relay
will turn off all FIXME messages, turn on cursor warning
messages, and turn on all relay messages (API calls).
WINEDEBUG=relay
will turn on all relay messages. For more control on
including or excluding functions and dlls from the relay
trace(3x,n,3x _nc_tracebits) look(1,8,3 Search::Dict) into the [Debug] section of the wine(1,5) configu-
ration file.
For more information on debugging messages, see the Running Wine
chapter of the Wine User Guide.
WINEDLLPATH
Specifies the path(s) in(1,8) which to search for builtin dlls and
Winelib applications. This is a list of directories separated by
":". In addition to any directory specified in(1,8) WINEDLLPATH, Wine
will also look(1,8,3 Search::Dict) in(1,8) /usr/lib/wine.
WINEDLLOVERRIDES
Defines the override type and load(7,n) order of dlls used in(1,8) the
loading process for any dll. The default is set(7,n,1 builtins) in(1,8) the configu-
ration file. There are currently two types of libraries that can
be loaded into a process' address space: Native windows dlls (
native ), wine(1,5) internal dlls ( builtin ). The type may be abbre-
viated 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(7,n) order. The load(7,n) order
determines which version(1,3,5) 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(7,n) order can
be separated with commas. It is also possible to use specify
different loadorders for different libraries by separating the
entries by ";".
The load(7,n) order for a 16-bit dll is always defined by the load(7,n)
order of the 32-bit dll that contains it (which can be identi-
fied by looking at the symbolic link(1,2) of the 16-bit .dll.so
file(1,n)). For instance if(3,n) ole32.dll is configured as builtin, stor-
age.dll will be loaded as builtin too, since the 32-bit
ole32.dll contains the 16-bit storage.dll.
Examples:
WINEDLLOVERRIDES="comdlg32,shell32=n,b"
Try to load(7,n) comdlg32 and shell32 as native windows dll
first and try the builtin version(1,3,5) if(3,n) the native load(7,n)
fails.
WINEDLLOVERRIDES="comdlg32,shell32=n;c:\\foo\\bar\\baz=b"
Try to load(7,n) the libraries comdlg32 and shell32 as native
windows dlls. Furthermore, if(3,n) an application request to
load(7,n) c:\foo\bar\baz.dll load(7,n) the builtin library baz.
WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n"
Try to load(7,n) comdlg32 as builtin first and try the native
version(1,3,5) if(3,n) the builtin load(7,n) fails; load(7,n) shell32 always as
builtin and comctl32 always as native.
DISPLAY
Specifies the X11 display to use.
FILES
/usr/bin/wine(1,5)
The wine(1,5) program loader.
/usr/bin/wineconsole
The wine(1,5) program loader for CUI (console(4,n)) applications.
/usr/bin/wineserver
The wine(1,5) server
/usr/bin/winedbg
The wine(1,5) debugger
/usr/bin/wineclipsrv
The wine(1,5) clipboard server
/usr/lib/wine(1,5)
Directory containing wine(1,5)'s shared libraries
$WINEPREFIX/config(1,5)
User-specific configuration file(1,n), which must conform to the for-
mat specified in(1,8) the wine.conf(5) man(1,5,7) page. A sample configura-
tion file(1,n) is documentation/samples/config(1,5) in(1,8) the wine(1,5) source ar-
chive.
$WINEPREFIX/dosdevices
Directory containing the DOS device mappings. Each file(1,n) in(1,8) that
directory is a symlink to the Unix device file(1,n) implementing a
given device. For instance, if(3,n) COM1 is mapped to /dev/ttyS0
you'd have a symlink of the form $WINEPREFIX/dosdevices/com1 ->
/dev/ttyS0.
DOS drives are also specified with symlinks; for instance if(3,n)
drive D: corresponds to the CDROM mounted at /mnt/cdrom, you'd
have a symlink $WINEPREFIX/dosdevices/d: -> /mnt/cdrom. The Unix
device corresponding to a DOS drive can be specified the same
way, except with '::' instead of ':'. So for the previous exam-
ple, if(3,n) the CDROM device is mounted from /dev/hdc, the corre-
sponding symlink would be $WINEPREFIX/dosdevices/d:: ->
/dev/hdc.
AUTHORS
wine(1,5) is available thanks to the work of many developers. For a listing
of the authors, please see the file(1,n) AUTHORS in(1,8) the top-level directory
of the source distribution.
COPYRIGHT
wine(1,5) can be distributed under the terms of the LGPL license. A copy of
the license is in(1,8) the file(1,n) COPYING.LIB in(1,8) the top-level directory of
the source distribution.
BUGS
A status report on many applications is available from
http://www.winehq.org/Apps. Please add entries to this list for appli-
cations you currently run.
Bug reports may be posted to Wine Bugzilla http://bugs.winehq.org If
you want to post a bug report, please read(2,n,1 builtins) the file(1,n) documenta-
tion/bugs.sgml in(1,8) the wine(1,5) source to see what information is necessary
Problems and suggestions with this manpage please also report to
http://bugs.winehq.org
AVAILABILITY
The most recent public version(1,3,5) of wine(1,5) can be downloaded from
http://www.winehq.org/download
The latest snapshot of the code may be obtained via CVS. For informa-
tion on how to do this, please see http://www.winehq.org/cvs(1,5)
WineHQ, the wine(1,5) development headquarters, is at
http://www.winehq.org/. This website contains a great deal of informa-
tion about wine.
The wine(1,5) newsgroup is comp.emulators.ms-windows.wine. It is used for
discussion of various wine(1,5) end user aspects/help.
For further information about wine(1,5) development, you might want to sub-
scribe to the wine(1,5) mailing lists at http://www.winehq.org/forums
SEE ALSO
wine.conf(5)
Wine 20040505 May 2002 WINE(1)