This FAQ, or Frequently Asked Questions, covers general topics about Wine. For questions related to Wine software development, see DeveloperFaq

General Questions

How do I run Wine?

Wine is not something you run, you run applications with it. Simply open your applications and Wine should be loaded to run them automatically. You can configure your wine environment by running winecfg, and you can browse your fake windows drive at ~/.wine/drive_c

If you would like a general overview and tutorial about using Wine, you can read the User Guide. For the most part, however, Wine should be as straightforward as clicking the application you'd like to run from your Gnome/KDE/Whatever menu.

When using the terminal there are two valid methods of running applications. The first method is to chdir into the program's folder and then run the application directly, e.g.

cd "~/.wine/drive_c/Games/Tron" && wine tron.exe

The second method should ONLY be used if you are intending to install from something which has multiple CDs (you need to use this method to allow you to swap discs) as it doesn't always work. It consists in using the full Windows path like so...

wine "C:\Games\Tron\tron.exe"

Do NOT run with the full Linux path i.e. "wine /stuff/mygame.exe" or by double clicking icons from your file manager (sometimes this works but more often it will fail with errors of some sort).

This is because Wine passes this path as-is to the windows program in argv[0]. This is exactly what cmd.exe does and Wine has extensive tests for that. However some programs expect fully qualified windows path in argv[0], and break if they don't get it. Lots of programs written with Borland tools will have that problem because Borland mistakenly stated in the manuals that argv[0] will always be set to fully qualified path of the executable. Which is not the case.

If you use Gnome, KDE or XFCE4, then after you have installed some applications in Wine you should notice a Wine subfolder in your main desktop menu with menu entries for all your installed Wine programs (as long as you told them to make Start Menu shortcuts). If any apps seem to be missing try running "wineboot" and looking again.

What is the difference between Wine, CrossOver Linux, and Cedega?

Wine is the base of the project, where most of the work is being done. Wine is currently a beta software project, intended mainly for developers, testers, and early adopters at the moment. Despite Wine's beta limitations, tens of thousands of people nevertheless use "vanilla" Wine successfully to run a large number of Windows programs.

CrossOver Linux is a product made by CodeWeavers that is based directly on Wine with a few proprietary add-ons. Unlike the biweekly Wine releases, CrossOver releases are rigorously tested for compatibility with CodeWeavers' supported applications in order to prevent regressions. CodeWeavers employs a large portion of the Wine developers and provides a great deal of leadership for the project. All improvements to Wine eventually work their way into CrossOver.

Cedega is a product from TransGaming. TransGaming forked Wine back in 2002 when Wine had a different license, closed their source code, and rebranded their version as specialized for gamers. TransGaming currently gives back very little code to Wine. Cedega is not just "Wine with more gaming support" - many games run better under Wine than Cedega. Currently, Wine has more advanced Direct3D support than Cedega, but Cedega still has more advanced copy protection support due to TransGaming's licensing of (closed source) code from a handful of copy protection companies. Unlike CrossOver, most improvements to Wine don't get into Cedega due to Cedega's proprietary licensing.

For more information on how this happened, see Wine History

Why do some people write WINE and not Wine?

They are using the acronym "Wine Is Not an Emulator", the original name for the project. While recursive acronyms are clever, there really is no point to the capital letters. They look ugly, so please use the simpler, current name of the project: Wine. It's what we use.

Is Wine an emulator? There seems to be an argument.

When users think of an emulator, they tend to think of things like Super Nintendo emulators or virtualization software. This is the wrong way to think about Wine - Wine runs Windows applications in essentially the same way Windows does. There is no inherent loss of speed due to "emulation" when using Wine, nor is there a need to open Wine before running your application.

When will Wine-1.0 be released?

See WineReleasePlan for a schedule. See WineReleaseCriteria for our goals for 1.0.

Does Wine hurt Linux?

Wine increases the usefulness of Linux, makes it easier for users to switch to Linux, and makes it easier for Windows developers to make applications that work on Linux. See the Debunking Wine Myths article for a fuller answer.

Why does Wine have a Windows version on the download page?

The Windows version allows Wine developers to test out the completeness of Wine DLLs by replacing those on Windows. At least for now, this is mainly for developers. However, in the future once we finish our DirectX 10 implementation, we may be able to implement Direct3D 10 in Windows XP the same way it runs in Wine: by translating DirectX calls to OpenGL ones.

Does Wine run on 64-bit?

Yes. Normally, installation should be the same as with 32-bit: simply install the Wine package for your distribution. Check the Downloads page. If you need to build Wine from source, see WineOn64bit for further details.

Note that Wine for 64-bit actually runs in 32-bit mode. This is necessary, as virtually all Windows applications are 32-bit. Simultaneous support for 64-bit Windows applications is planned for the distant future, after Wine's 1.0 release.

• Wine is currently offered in 32-bit. 16-bit and 32-bit Windows applications work with it. 64-bit Linux installations will work with the 32-bit Wine
• Wine will be offered in 64-bit. 64-bit Windows applications will work with it. Some 16-bit applications will not work with it.

Can I use Wine to install drivers for my hardware?

No. With the possible future exception of some printer drivers, Wine requires your hardware to already be working on your operating system. The technical reason for this is that Wine, like most applications, runs in user mode and not kernel mode.

Where can I get further help?

In addition to this Wiki, the Wine HQ Documentation and mailing lists are excellent resources. You'll most likely want the wine-users mailing list, however if you're an ISV looking at porting an application with Winelib you can also try wine-devel.

If you are looking for help with a specific application, you may want to search the Application DB. The AppDB is a place where users can share their experiences by submitting test data, sharing tips and tricks, and asking questions.

The IRC channel: #WineHQ on irc.freenode.net. Usually several knowledgeable Wine users hang out there, and often developers will lurk there too. See IRC for more important information.

There's also a Usenet newsgroup, but you really should use the mailing list instead. The mailing lists are what the developers use and monitor, so you're more likely to get help. Anyway, the newsgroup is comp.emulators.ms-windows.wine.

Who is responsible for Wine?

Wine is available thanks to the work of many people around the world. Some companies that are or have been involved with Wine development are CodeWeavers, TransGaming, Corel, Macadamian, and Google. Please see the Acknowledgements, and WineHistory pages for more information.

How can I help contribute to the Wine project, and in what ways?

You can contribute programming or documentation skills, or monetary or equipment donations, to aid the Wine developers in reaching their goals.

One area where every Wine user can contribute to this project is by sending high quality bug reports to our Bugzilla and helping the developers with any follow up questions that they may have about a bug that you have come across. It is not only impossible but also impractical for a developers to have a copy of every program on the market. This is why we need your help even after you have sent in the initial bug report. If a developer has a good idea what might be causing the bug he or she may ask if you can try a patch and see if it fixes the problem. After this patch makes its way into our main development tree the bug report will be closed and your help will be appreciated by everyone.

For a list of ideas of how you can help, please consult the helping Wine page.

I think I've found a bug. How do I report this bug to the Wine programming team?

Bug reports should be submitted to our online Bugzilla system (http://bugs.winehq.org/). To increase developer productivity and facilitate a resolution to submitted bugs, please read the Wiki article on Bugs. A poor bug report may be marked INVALID and closed, leaving you no closer to resolving your problem. High quality bug reports are an essential part of making Wine better.

Please note that you should generally avoid submitting bug reports if you have used any third party applications or native DLL overrides.

Using Wine

When I double-click on a .exe file in my File Manager, nothing happens.

Note: If you can, start applications by clicking on the application's icon in the Applications / Wine menu or desktop instead. Double-clicking .exe's is typically only needed for applications that aren't installed yet, e.g. to run the setup.exe on a cd-rom game, or a downloaded installer.

If double-clicking doesn't work, you might need to right-click the file and choose "Run with Wine". It depends on your file manager. If that also doesn't work, contact whoever built your wine packages and complain.

You can work around this problem by using the commandline instead of your File Manager. To do this, open a terminal window, navigate to the folder where your application is, and run it by typing wine (program).exe. Running wine in this fashion will also let you see Wine's debugging log. This may not be the friendliest way to use Wine, but at the moment it is the most effective, and it's how wine developers usually do it.

I want to pass command line arguments to my program

If you're using a program with switches on Windows, for instance:

quake.exe -map e1m1

Then you can do the equivalent in Wine by running:

wine quake.exe -map e1m1

That is, the command line is identical, except with a wine in front. Note, however, that you may need to escape certain special characters with backslashes due to the way they're handled in the Linux shell. For instance:

quake.exe -map C:\Quake\e1m1.bsp

Becomes:

wine quake.exe -map C:\\Quake\\e1m1.bsp

For more information on using backslashes, see: http://www.tuxfiles.org/linuxhelp/weirdchars.html

Can I run applications directly off of a Windows installation without reinstalling them?

Generally, no. Unless you know otherwise, you should leave your Windows installation alone and install things "fresh" into Wine. Wine is not designed to interact with an existing Windows installation.

Moreover, Wine has no way of accessing the registry of a Windows installation. Since many applications store configuration data in the registry, they cannot be "shared" and need to be installed under Wine in order to be used with Wine. This isn't unique to Wine: you'll run into a similar problem under Windows itself if you try and run applications from another Windows installation. Wine (or the other Windows installation) has no way of seeing this data unless it was written into Wine's registry by the program installer.

Some applications are not so tightly coupled with the registry and are instead self-contained within a folder. It may be possible to share these "portable" applications between Windows and Wine. However, this almost always complicates the support process. Please run the installation software which came with the application under a clean Wine configuration before seeking help.

WARNING: Do not change the symlink ~/.wine/dosdevices/c: (or any other WINEPREFIX) to point to an actual Windows installation. Do not use winecfg to do this either. Doing so can render your Windows installation unusable if write access is enabled/permitted. Note that the default symlinks created by Wine are safe and most users don't find a reason to change them.

My program froze up, how do I close it?

If you ran the program from a terminal window by typing wine (program).exe, you can usually just go back to that terminal window and press ctrl+c. If you ran the application some other way, such as from a launcher shortcut, then you can open up a terminal and forcibly kill the process:

killall -9 Application.exe

If you want to kill all Wine programs at once, you can run:

wineserver -k

You can also open up a Wine version of the Windows task manager by running "wine taskmgr" in a terminal. This will allow you to cancel individual Wine processes.

If you are getting a complete deadlock and are unable to even use your mouse after running Wine, it's probably not a specific problem with the Wine software. Wine is a user-level process, and shouldn't be able to completely hang the operating system under any circumstances. Instead, Wine is likely exposing a deeper problem with the system, such as a defective hardware driver.

How do I get Wine to launch an individual application inside of a virtual desktop?

For wine-0.9.61 and newer, you can do this with winecfg. Add the application in the Applications tab and then, in the graphics tab, enable "Emulate a virtual desktop."

For Wine-0.9.60 and older winecfg does not allow the setting of virtual desktops for individual applications. However, you can work around this by using the following command:

wine explorer /desktop=name,1024x768 program.exe

Of course, replace program.exe with what your program's name is, and change the resolution to the size of the virtual desktop you want.

My application complains about being unable to change the resolution or color depth.

You generally need to edit the Screen section of your /etc/X11/xorg.conf to support additional color depths and resolutions. There may also be a problem with Xrandr.

The application I am trying to run complains that it needs 256 colors but I have millions of colors.

This is a bug in Wine. See http://bugs.winehq.org/show_bug.cgi?id=7334

For now, there are a few workarounds you can try. See 256ColorsWorkarounds

My X screen won't go back to its normal resolution after running a game fullscreen.

You can often work around this by changing the screen resolution and then changing it back again under the system preferences.

Alternatively, you can run this terminal command to restore your X settings:

xrandr -s 0

I'm using Beryl/XGL/Compiz and get poor performance/odd messages/broken applications

Using composite display managers in Linux tends to cripple OpenGL performance or break OpenGL entirely which is why we recommend that you disable them and remove composite from XOrg entirely before trying to use Wine. If you are using one and experiencing slow performance then DO NOT FILE BUGS as this is not a Wine bug. Just because TuxRacer runs fine doesn't mean it is Wine's fault, Windows games normally require a little more umph than basic Linux native games. Also to make sure, run glxinfo and make sure that it says "Direct Rendering : Yes".

How do I know what version of Wine I have?

Open up a terminal and run wine --version. It will say something like "wine-0.9.36" or if you are using GIT (it's like CVS or SVN) then you will have a version along the lines of "wine-0.9.36-139-ge79a94d".

TIP: You can find out what the latest release of Wine is from WineHQ's main page. Currently, Wine releases come out every two weeks. Your Operating System may ship with an out of date (obsolete) version of Wine. Depending on what OS you use, you may be able to add an update source to your package management system to keep up to date. Check the downloads page for details.

Should I run Wine as root?

NEVER run Wine as root! Doing so gives Windows programs (and viruses) full access to your computer and every piece of media attached to it. Running with sudo also has these same risks but with the added bonus of breaking the permission on the users ~/.wine folder in the process. If you have run Wine with sudo you need to sudo rm -rf ~/.wine and then run winecfg to set wine back up. You should run Wine as the normal user you use to login.

For Linux Systems all ideas that wine needs root can be solved through Posix Capabilities http://www.linuxjournal.com/article/5737 or Posix File Capabilities http://www.ibm.com/developerworks/library/l-posixcap.html or correcting other security settings.

So, I ran wine with sudo or as root, how do I fix my permission errors?

You need to delete your ~/.wine directory, this is where all wine state, configuration and any important data you might have such as installed programs, saved data within wine programs etc. Once you delete or move this directory, rerun wine as a regular user always! Run the following to delete your ~/.wine directory if it now has root permissions.

sudo rm -rvf ~/.wine

How do I uninstall Wine? How do I wipe the virtual Windows installation?

You can remove your virtual Windows installation and start from scratch by eliminating (or renaming) the hidden .wine directory in your home folder, such as with rm -rf ~/.wine

If you want to remove Wine entirely after you installed it with your distribution's package manager, you can generally uninstall in the same way. Note, however, that uninstalling Wine will not eliminate the virtual Windows installation - to do that you must follow the instructions above.

Since Wine is beta software, periodically we may update the default configuration generated when you first use Wine. Sometimes users have success getting an application to work by wiping (or moving) their ~/.wine folder, rerunning winecfg with the new Wine version, and reinstalling the application.

Which sound driver should I select in winecfg?

As of Wine 0.9.47 you shouldn't need to configure it any more, defaults should work just fine. For wine 0.9.46 alsa and oss should work equally well. For wine versions before 0.9.42 oss works best, after that alsa is slightly behind oss since it might miss some voice chat capability.

I'm using OSS in Wine and I have no sound.

Unless you're using a sound card with an emu10k1/2 chipset (SB Live!/Audigy) or another type of card that supports "Hardware Mixing" then you can only ever have one application using sound at the same time. If you have aRts (KDE sound system), ESD (Gnome sound system) or any music apps open then you simply wont hear anything from Wine. You need to kill or close all these programs before being able to get sound from Wine. To work out if anything has locked your sound-card already you can do "cat /dev/urandom >> /dev/dsp". If you get an error message it means that something is using it. If you get loud static this means that your sound card is clear and ready for use.

Running winecfg seems to hang or complain about files when I click the audio tab

The hang is caused by the "NAS" sound driver. This causes it to pause for a while but it should respond eventually. The only way to get around this is to remove NAS from your system and/or build Wine without NAS support in the first place. If you see messages about JACK in the terminal they can be ignored unless you intend to use the JACK driver. If you wish to use the JACK driver then you need to install JACK's libraries onto your machine before JACK will work.

Running winecfg has No text or damaged text displayed

or

Using wine over remote X11 sessions and No text or damaged text displayed

Please make sure not have added any fonts to wine. Font conflicts can sometimes cause a similar issue. If a fresh wine prefix.(A copy of wine that nothing has been done to yet) Is having this problem. Try setting following in registry

[HKEY_CURRENT_USER\Software\Wine\X11 Driver]
"ClientSideWithRender"="N"

Place above in text file and it can be inserted into registry by "regedit settings.txt".

This was report as been required of OS X on the 1 Dec 2007. This may change. Please apply only as required.

How do I change font size / DPI ?

First, you should try editing with winecfg. Go to the Graphics tab, and slide the "Screen Resolution" slider accordingly. Changes will not effect the winecfg window until you restart it.

If the window is currently too big for you to use winecfg, then you'll have to change the registry value:

sed -i 's@"LogPixels"=.*@"LogPixels"=dword:00000060@g' ~/.wine/system.reg

How do I edit the Wine registry?

The Wine registry is the .reg files in ~/.wine, however you should not edit these files by hand due to the encoding that they use. Always use the regedit program that comes with Wine. This can be run by typing regedit in the terminal. Wine's regedit is virtually identical to the Windows version of regedit and also supports importing and exporting of registry files. NEVER try and import your entire Windows registry, this will just break Wine.

See also: UsefulRegistryKeys

I have an MSI file, how do I install/run it?

MSI files cannot be run directly, you need to use the msiexec program. MSI files can be installed in Wine from the terminal like this

wine msiexec /i whatever.msi

That will then run the MSI program the same as if you had double-clicked it in Windows.

My CD or DVD disc won't eject

Try wine eject. It is a function to free up, unlock, and eject the drive.

My program fails to do networking, but Linux can get online

You need to make sure that your hostname resolves to the IP address of your network interface. To set this up correctly, you can type the following from a terminal:

hostname

This will return your hostname the way your computer sees it. Now, you need to open an editor with system administrator privileges, how you do this will depend on the distribution you are using. Open the file /etc/hosts and see if there is an entry for your hostname. Assuming your hostname is "yourhost" and your network IP address is 192.168.0.23, the entry might look like this:

127.0.0.1      yourhost.yourdomain.com      yourhost

Change this to (or add, if there is no such line):

192.168.0.23   yourhost.yourdomain.com      yourhost

For most Windows games with networking problems, this is all you need to get networking to work.

How do I configure a proxy?

Use regedit to add the following values to the [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Internet Settings] key:

"ProxyEnable"=dword:00000001
"ProxyServer"="proxy-server-address:port"

How do I get a debug trace?

When filing bugs, it is often necessary to get a trace (generally +relay, but specific DLLs have their own debug channels). To retrieve a trace, run:

$ WINEDEBUG=+trace1,+trace2,-trace3 wine your_program.exe &> /tmp/output.txt

Then ATTACH /tmp/output.txt to the bug. If the resulting file is larger than 1 MB, compress it with 'bzip2 -9' or 'rzip -9' before attaching.

For a list of debug channels that are available in Wine, see DebugChannels

Applications

How do I uninstall Windows applications?

Wine has its own built-in uninstaller - equivalent of Windows "add/remove programs" function for running standardized uninstallers. In recent version, a shortcut has been added in Wine's menu, along with a shortcut to winecfg.

The uninstaller does not remove menu entries. To remove all Wine created menu entries run the following commands

rm -f $HOME/.config/menus/applications-merged/wine*
rm -rf $HOME/.local/share/applications/wine
rm -f $HOME/.local/share/desktop-directories/wine*
rm -f $HOME/.local/share/icons/????_*.xpm

Will Wine work with my application?

Probably. If your application is remotely popular, you can find other user reports in the Application Database. If there aren't any reports using a recent version of Wine, however, your best bet is to simply try and see.

Does Wine support DirectX? Can I install Microsoft's DirectX under Wine?

Wine itself provides a DirectX implementation that, although it has a few bugs left, should run fine. Wine supports DirectX 9.0c at this time. Plans for DirectX 10 are underway.

If you attempt to install Microsoft's DirectX, you will run into problems. It is not recommended nor supported by Wine HQ to attempt this. You can install the runtime, but it will not run. The runtime needs access to the Windows drivers, and Wine cannot access them for obvious reasons. The only native Microsoft DLLs that could be useful anyway are the d3dx9_xx.dll type ones, and these require you to accept Microsoft's license. Additionally these DLLs are now part of the Wine tree. So, as Wine improves these DLLs will only become less relevant.

That said, there are some guides out there which describe how you can install Microsoft's DirectX. I reiterate: It is not recommended nor supported by Wine HQ to attempt this. Furthermore it is considered off topic in Wine HQ support mediums (such as the forums). Please use a clean Wine configuration folder before seeking help. (You may need to rm -rf ~/.wine and re-install your Windows applications.)

How can I get a copy of some runtime library?

Applications should come with all the necessary runtime libraries not provided with Windows itself. However some applications still ship without them. These runtimes can be obtained by

1. downloading them from the original creators of the runtime (eg. Microsoft) or
2. installing other applications which do include them.

It is not recommended (even on Windows) to get these files by any other means. Do not trust some random download site to provide safe or real copies of them.

To aid Wine users with downloading and installing common runtime libraries, the winetricks shell script was created. Please try it first if you run into an application which requires them.

My app won't run, and says it needs MFC40.DLL

See "How can I get a copy of some runtime library?" above. You can install MFC40.DLL by running winetricks and selecting mfc40.

My app won't run, and says it needs MFC42.DLL or MSVCP60.DLL

See "How can I get a copy of some runtime library?" above. You can install MFC42.DLL, MSVCP60.DLL, and friends by running winetricks and selecting vcrun6.

My app won't run, and says it needs MDAC

See "How can I get a copy of some runtime library?" above. You can install MDAC by running winetricks and selecting mdac 2.7.

My app won't run, and says it needs .NET

You're probably out of luck, but if you're brave, you can still try running it.

See "How can I get a copy of some runtime library?" above. You can install .net 2.0 by running winetricks and selecting dotnet20. This is not yet supported, and few .NET applications actually work. See the .NET AppDB pages for more information on installing these runtimes.

Alternately, you can install Mono, an open source implementation of .net 2.0, by running winetricks and selecting mono19. This is not yet supported, and very few .NET applications actually work with it under Wine. See the Mono Project AppDB page for more information.

My app won't run, and says it needs Internet Explorer

Wine uses the core of Firefox (called Gecko) to implement its own Internet Explorer.

In some cases, you can make applications which think they need IE happier by running winetricks and selecting gecko and/or fakeie6.

How do I install Internet Explorer in Wine?

The Wine project does not support this, as Internet Explorer requires a huge number of native DLLs, which is hard to configure.

If for some reason you really, really need to run the real IE, see ies4linux, which is a script that does the neccessary Wine configuration for you. (But please don't ask the Wine project for help if you run into trouble, ask the author of ies4linux.)

My app runs, but text areas act strangely (e.g. lines don't wrap, double clicking doesn't select words)

You may have run into a bug in Wine's RICHED20.DLL. You can try using Microsoft's RICHED20.DLL by running winetricks and selecting riched20. This may let you work around the problem until the Wine developers fix the bug.

How come Wine doesn't work well with copy protection?

Copy protection uses several "dirty" methods to detect if discs are "real" or not. Some of these methods work in Wine but most do not, such as the extremely invasive StarForce system. Wine would need to be altered to allow for almost rootkit-like functionality of programs to get some of these copy protection schemes to work, so support is likely to be a long time off if ever. (Some people use illegally modified or "cracked" games with the copy protection removed, but the Wine project cannot advocate that.)

See also our page on copy protection

My application worked with an older version of Wine, but now it's broken!

These are called regressions. Please file a bug and tag it "regression" - we'll pay special attention to it, since they're a lot easier to fix when caught early. In the future, once we start making "stable" releases, we'll make great effort to ensure that there are no regressions from one stable release to the next.

I really need this particular application to work. How can I go about making this happen?

We're glad you asked. Please see our Helping Wine page for some suggestions.

Briefly, you can improve Wine yourself, convince someone else to do it for you, or try some complicated hacks involving native Windows DLLs rather than Wine's unfinished ones.

Performance

What are the system requirements for Wine?

The rule of thumb is that if your application runs fine in Windows, it should run fine on the same system using Wine. Wine, along with the operating system you use to run it, generally requires less disk space and memory than Windows itself. If you're not currently running a Windows application, Wine won't consume any resources at all other than about 20 megabytes of disk space.

Is Wine slower than just using Windows?

Actually, Wine is sometimes faster. The speed of an application depends on a lot of factors: the available hardware and their drivers, the quality of the code in the APIs the application uses, and the quality of the code in the underlying operating system.

Driver code matters a lot. If you're running a graphics-heavy application using a video card with very poor drivers such as an ATI card under Linux, performance will degrade substantially. On the other hand, Linux has superior memory management, and comes out ahead of Windows in many CPU-related tasks; see benchmarks for more information.

Sometimes, bugs in Wine can make applications excessively slow; see Performance-related bugs.

I get lots of "fixme:" messages in the terminal and Wine runs a bit slow.

Ignore them. Generally speaking, a fixme message will not make much sense to someone unfamiliar with Wine development. They are for Wine developers. Also, it's important to understand that fixme messages often do not indicate a show stopping problem. Many applications will work fine even though Wine prints a few fixme messages. That said, they can still sometimes provide insight into how a particular application works (or doesn't work).

If there are a very large number of these messages scrolling repeatedly, you can sometimes speed Wine up a little by turning them off altogether. You can do so by setting the WINEDEBUG environment variable to -all. For example, your command line could look something like:

WINEDEBUG=-all wine program.exe

More advanced users and programmers interested in debugging Wine should see DebugChannels and the Developer Documentation wiki pages.

ISSUE: "preloader: Warning: failed to reserve range 00000000-60000000"

http://bugs.winehq.org/show_bug.cgi?id=12516 is the bug following this issue.

This issue is appearing due to a kernel setting. cat /proc/sys/vm/mmap_min_addr as root, if it does not equal 0 then "sysctl -w vm.mmap_min_addr=0" as root can be used to temporary fix issue or for every reboot after adding the line vm.mmap_min_addr=0 to /etc/sysctl.conf can be done. Please record if you do this alteration the area Wine needs may change.

See PreloaderPageZeroProblem

Apple

How do I install Wine on my Mac?

If you are running Linux on your Mac, installing Wine is as simple as installing it under Linux. Simply visit the downloads page.

If you are running OS X there are no official builds yet. The main reason is that Apple X11 is badly broken, and Wine doesn't run well with it. We don't like giving users a bad impression of Wine.

But if you are truly adventurous and want to try it no matter what, you can find unofficial darwine *Intel* builds here. Its installation is simple and straightforward as any other dmg image: open it and drag its Darwine folder to your Applications folder. Be warned again that many applications do not run because of Apple's faulty X11 implementation and not because of Wine itself. DirectDraw and Direct3D applications do not run at all, but many GDI applications will run surprisingly well, including DirectSound ones. Be sure to read the MacOSX/FAQs.

Tip: Audio output will only be enabled after you run winecfg to configure it. This can be done by double-clicking "Sample WineLib Applications->winecfg.exe".

Can I use Wine on an older Mac without an Intel chip?

No, not even in Linux. Older Macs used PowerPC processors, which are incompatible with code compiled for x86 (Intel and AMD) processors unless the code is run under CPU emulation. Wine Is Not a (CPU) Emulator, nor does it include one. The Darwine project, however, is an effort to do just that.