wine
run Windows programs on Unix
see also :
wineserver - winedbg
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.
add an example, a script, a trick and tips
examples
source
Can I replace Windows with Wine?
I would first check to see if the games that you are playing have
a Linux port already. This way you could avoid using Wine or
Parallels in order to play them.
I haven't had great experience running newer windows games
(especially newer FPS titles) through an emulator such as Wine.
As far as partitioning your HDD to dual boot windows and linux,
if you are going to be in windows most of the time playing games,
I would devote about 60% of the HDD space to windows and the
other 40% to your linux installation.
Windows cannot read ext4 partitions AFAIK. Although I do believe
that there are a few programs out there that will let you browse
the partitions from within windows.
source
Is it possible to run NXT-G software under Linux using Wine?
Here's what I would try. You can start an MS Windows Micro
instance (virtual machine/VM) on Amazon Web Services (AWS). An AWS micro VM
cost nothing if you have Linux on it but since you need Windows
it's $0.03 per hours. The price list is on this page. If
the micro instance is too small or too slow, you can use a bigger
one (an Extra Large is $0.96/hour).
You can install the LEGO software on it and work remotely. To
avoid installing the LEGO software each time you can even create
your own VM an relaunch it whenever you need.
The only downside I see is the IO between the VM and the physical
LEGO NXT brick. This could probably be solved by creating a proxy
port on your home computer through which the LEGO software on the
VM could communicate with the brick. This need to be tested since
I don't have an NXT. If this part is too complicated (or
impossible) you could look for other ways to upload the code on
the NXT from the Windows VM.
If you never played with AWS, I suggest to start with a Linux
micro instance (e.g. Ubuntu). Since it cost nothing it's a good
way to experiment on how the whole thing works.
source
Why is wine "not an emulator"?
For practical purposes Wine is an emulator, or at least
it does what most people would expect an emulator to do, even if
technically it isn't just an emulator. See the FAQ for a good explanation. This also
follows great traditions in Unix naming, cf. GNU's Not
Unix. :-)
source
Extracting msi files using Linux
You can try software called cabextract -
atleast Ubuntu has packages for it, I would expect it to be found
from other popular distros as well.
source
Ubuntu: how to get audio to work in both Spotify (under Wine) and Flash (in Firefox)?
That's a really old link, you shouldn't need
alsa-oss for sound in Flash if you are using a
recent Flash plugin.
Either consider upgrading Hardy to a newer Ubuntu, upgrading the
Flash package to one from backports or roll your own Flash
package based on the latest version.
source
Is there any equivalent to wine for running Mac applications?
I have never come across a thing, but a quick google on it
yielded interesting things, here's one such results here. Other
than that, it would be interesting to see how such an emulation
for a pre-Mac Intel era i.e. PowerPC can be achieved, let alone
binaries for powerpc running on a x86 processor. However, since
MacOSX is a derivative of BSD, why not get the sources for the
macosx program that you wish to run and recompile it targeting
your system?
Hope this helps, Best regards, Tom.
source
Is there a Wine-like program, but for Windows?
It really depends on the app. You can accomplish a lot with
Cygwin, for
instance. Especially if the app is command line.
I usually keep a Virtual Machine of Xubuntu (using VirtualBox or
VMware) around for just such purposes though. Easier, more
features and full compatibility.
[Edit] You might also have a look at andLinux. Runs a
bit more integrated than the VM options.
source
Does installing licensed Windows software (e.g. CS5) on WINE contravene EULA
It depends completely on the EULA. If it reads something along
the line of "must be installed within a properly-licensed copy of
a Microsoft Windows operating system" then yes, it would be a
violation of the EULA to install it under wine. But very few
EULAs are likely to say this, since the operating system is not
their problem beyond a certain minimum spec.
description
wine
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 instead.
For running CUI
executables (Windows console programs), use
wineconsole instead of wine. This will display
all the output in a separate windows (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.
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 GIT. For
information on how to do this, please see
http://www.winehq.org/site/git
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 subscribe to the wine mailing lists at
http://www.winehq.org/forums
copyright
wine can be distributed under the terms of the LGPL
license. A copy of the license is in the file COPYING.LIB
in the top-level directory of the source distribution.
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 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/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/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.
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 messages 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 debugging).
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
HKEY_CURRENT_USER\Software\Wine\Debug registry key.
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/lib/x86_64-linux-gnu/wine.
WINEDLLOVERRIDES
Defines the override type and load order of dlls used in the
loading process for any dll. 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 abbreviated with the first
letter of the type (n, b). The library may also be
disabled (’’). 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 specify
different loadorders for different libraries by separating the
entries by ";".
The load order for a 16-bit dll is always defined by the load
order of the 32-bit dll that contains it (which can be identified
by looking at the symbolic link of the 16-bit .dll.so file). For
instance if ole32.dll is configured as builtin, storage.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 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;oleaut32="
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. Oleaut32 will be disabled.
WINEARCH
Specifies the Windows architecture to support. It can be set
either to win32 (support only 32-bit applications), or to
win64 (support both 64-bit applications and 32-bit ones in
WoW64 mode).
The architecture supported by a given Wine prefix is set at
prefix creation time and cannot be changed afterwards. When
running with an existing prefix, Wine will refuse to start if
WINEARCH doesn’t match the prefix architecture.
DISPLAY
Specifies the X11 display to use.
OSS sound driver configuration variables
AUDIODEV
Set the device for audio input / output. Default /dev/dsp.
MIXERDEV
Set the device for mixer controls. Default /dev/mixer.
MIDIDEV
Set the MIDI (sequencer) device. Default /dev/sequencer.
files
/usr/bin/wine
The wine program loader.
/usr/bin/wineconsole
The wine program loader for CUI (console) applications.
/usr/bin/wineserver
The wine server
/usr/bin/winedbg
The wine debugger
/usr/lib/x86_64-linux-gnu/wine
Directory containing wine’s shared libraries
$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 device corresponding to a DOS drive can be specified the
same way, except with ’::’ instead of ’:’. So for the previous
example, if the CDROM device is mounted from /dev/hdc, the
corresponding symlink would be $WINEPREFIX/dosdevices/d:: ->
/dev/hdc.
program
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 invoking Wine via a shell, e.g.
wine C:\\Program\ Files\\MyPrg\\test.exe
bugs
A status report
on many applications is available from
http://appdb.winehq.org. Please add entries to this
list for applications you currently run, if there is no
entry for this application.
Bug reports may
be posted to Wine Bugzilla http://bugs.winehq.org If
you want to post a bug report, please see
http://wiki.winehq.org/Bugs in the wine source
to see what information is necessary
Problems and
suggestions with this manpage please also report to
http://bugs.winehq.org
see also
wineserver ,
winedbg
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.