Wine Man Page
From Wine-Wiki
Contents |
SYNOPSIS
wine program [arguments ... ]
wine --help
wine --version
For instructions on passing arguments to Windows programs, please see
the PROGRAM/ARGUMENTS section of the man page.
DESCRIPTION
wine 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, use winedbg instead.
For running CUI executables (Windows console programs), use wineconsole
instead of wine. This will display all the output in a separate win-
dows (this requires X11 to run). Not using wineconsole for CUI programs
will only provide very limited console support, and your program might
not function properly.
When invoked with --help or --version as the only argument, wine will
simply print a small help message or its version respectively and exit.
REQUIREMENTS AND INSTALLATION
Read the README file in the Wine source distribution and the
wine.conf(5) man page to know what Wine requires and how it is
installed from source.
PROGRAM/ARGUMENTS
The program name may be specified in DOS format ( C:\\WINDOWS\\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 invok-
ing Wine via a shell, e.g.
wine C:\\Program\ Files\\MyPrg\\test.exe
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 is also used to identify 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
locations.
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 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 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 look into the [Debug] section of the wine 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 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/local/lib/wine.
WINEDLLOVERRIDES
Defines the override type and load order of dlls used in the
loading process for any dll. The default is set in 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 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.
Examples:
WINEDLLOVERRIDES="comdlg32,shell32=n,b"
Try to load comdlg32 and shell32 as native windows dll
first and try the builtin version if the native load
fails.
WINEDLLOVERRIDES="comdlg32,shell32=n;c:\\foo\\bar\\baz=b"
Try to load the libraries comdlg32 and shell32 as native
windows dlls. Furthermore, if an application request to
load c:\foo\bar\baz.dll load the builtin library baz.
WINEDLLOVERRIDES="comdlg32=b,n;shell32=b;comctl32=n"
Try to load comdlg32 as builtin first and try the native
version if the builtin load fails; load shell32 always as
builtin and comctl32 always as native.
DISPLAY
Specifies the X11 display to use.
FILES
/usr/local/bin/wine
The wine program loader.
/usr/local/bin/wineconsole
The wine program loader for CUI (console) applications.
/usr/local/bin/wineserver
The wine server
/usr/local/bin/winedbg
The wine debugger
/usr/local/lib/wine
Directory containing wine's shared libraries
$WINEPREFIX/config
User-specific configuration file, which must conform to the for-
mat specified in the wine.conf(5) man page. A sample configura-
tion file is documentation/samples/config in the wine source
archive.
$WINEPREFIX/dosdevices
Directory containing the DOS device mappings. Each file in that
directory is a symlink to the Unix device file implementing a
given device. For instance, if 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
drive D: corresponds to the CDROM mounted at /mnt/cdrom, you'd
have a symlink $WINEPREFIX/dosdevices/d: -> /mnt/cdrom. The Unix
the source distribution.
BUGS
A status report on many applications is available from
http://appdb.winehq.org. Please add entries to this list for applica-
tions 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 the file documenta- tion/bugs.sgml in the wine 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 of wine 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
WineHQ, the wine development headquarters, is at http://www.winehq.org. This website contains a great deal of information about wine.
For further information about wine development, you might want to sub-
scribe to the wine mailing lists at http://www.winehq.org/forums
SEE ALSO
wine.conf(5)
Wine 20041201 May 2004 WINE(1)
