Wine regedit .reg file

Capturing the displays disables hot corners. Some programs react badly, usually by scrolling too far, when they get many small scroll wheel events. Set to "none" to prevent windows from floating when in the background. This is useful for web pages that work better in legacy compatibility modes.

You can also create subkeys to set compatibility mode of specific host name. If key name starts with '. To limit compatibility mode to IE10 for all Wine web pages, create. This is also useful when a Windows program has disabled the "Redirect to File" option in the Print dialog. Set this to "0" to let applications handle exceptions themselves. Set this to "0" to disable the GUI crash dialog. The value is used as is if not "n", "f" or "0" for the X11 geometry.

If this key does not exist, the default refresh rate will be used. Set them to "6. Set it to " It is needed if you install the gecko engine. Ports not mapped here will be automatically assigned in some order. Used to enable various internal diagnostics, such as heap checking. Some dialogs resize themselves according to this value. Default: 96 decimal. The most common reason is to get debug output when your program does not run properly.

You might also want to use utilities such as regedit that do not have menu shortcuts note that you can create them using whatever tools your DE provides. This does not hold true for Mac OS X Wine usage, which is all command line currently, unless you use a third party application. Thousands of applications work well. As a general rule, simpler or older applications tend to work well, and the latest versions of complex applications or games tend to not work well yet. See the Wine Application Database for details on individual applications.

If your application is rated Silver, Gold or Platinum, you're probably okay; if it's rated Bronze or Garbage, Wine isn't really ready to run it for most users. If there aren't any reports using a recent version of Wine, however, your best bet is to simply try and see.

If it doesn't work, it probably isn't your fault, Wine is not yet complete. Ask for help on the forum if you get stuck. 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 followup questions that they may have about your bug.

It is impossible and impractical for a developer to have a copy of every program on the market, so we need your help even after your 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. If the patch works and then makes its way into our main development tree, the bug report will be closed, your help will be appreciated by everyone and your problem will be fixed. For a list of ideas of how you can help, please consult the Contribute section of the main page.

Bug reports should be submitted to our online Bugzilla system. To increase developer productivity and facilitate a resolution to submitted bugs, please read the Wiki article on Bugs.

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. In addition to this wiki , check the Wine HQ Documentation and the users forum. If you're an ISV looking at porting an application with Winelib you can also try wine-devel.

For help with a specific application, search the Application Database , a place where users share their experiences by submitting test data, tips and tricks, and asking questions. Knowledgeable Wine users hang out there, and often developers will lurk there too. See IRC for more important information. 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. Ideally, if an application runs fine in Windows, it should run fine on the same hardware using Wine, provided native drivers for your hardware are installed and equivalent to the Windows drivers.

Open source Linux graphics drivers in particular are often inadequate to run games that work fine on the same hardware in Windows. If there is no native driver for your hardware, Wine will not be able to use it. One example is that the ntfsv3 drivers do not support shared-write mmap, a feature that cannot be emulated and is used by applications such as Steam. One other point is that Wine is a weird application in ways and some programs work better on case-insensitive filesystems see Case Insensitive Filenames for more details.

Until recently with projects such as Wayland, serious alternatives to x11drv weren't even on the horizon so development has focused on X.

However, Wine's interface with the graphics driver is designed to be abstract so supporting future graphics systems will hopefully be straight-forward. Short answer: Use the version that works best with the particular applications you want to run. In most cases, this will be the latest development version; however, in some cases it may take some experimenting to find it. Longer answer: Wine development is rapid, with new releases in the development branch every two weeks or so. Functionality will usually be best with the most recent development version, however, there are cases where changes to existing code in Wine cause applications that worked well in older versions to not work in the new one these are called regressions , as well as problems caused by the introduction of new, but as-yet-incomplete and untested, functions.

A good rule of thumb is to start with the version of Wine installed with your distro and see if that works with the applications you want to use. If it does, good! If it doesn't, upgrade. If you find an existing bug marked STAGED, this means there is a patch for the problem in wine-staging the experimental branch , and you should try the latest version in that branch. If there are known bugs without a STAGED patch or easy workaround, upgrade to the most recent version of Wine known to work for your application.

While Wine does have a "stable" branch, the term "stable" refers to the branch as a whole, which is infrequently updated, and for the minor stable releases only with bugfixes promised not to break functionality. Users of a development or staging release can achieve the same degree of stability by simply not upgrading. Note that user support for the stable branch is limited to the ability to file AppDB test reports.

The current stable, development, and staging releases are listed on the WineHQ home page. If your package manager complains about unmet dependencies when trying to install Wine, work your way backwards. Try installing whatever package your package manager complains has unmet dependencies, see what your it complains about, then try to install that.

Keep working your way backwards until you solve whatever is blocking everything else. A common problem on Ubuntu-based system is having installed a PPA version of a library that is newer than what is available in the standard repository. The solution is to either change the installed version of the library back to the one from the standard repository so you can install both the 32 and 64 bit packages, or find an i package whose version exactly matches the one already installed.

Consult your distro's support channels for help using your package manager and interpreting any error messages you may be receiving if you're having problems with distro packages.

Yes, but you will have to build Wine yourself see Building Wine , as it is not possible to have multiple distro packages installed. The easiest way to do this is to run Wine from the build directory don't do make install. If you want to actually install multiple versions, use --prefix when building Wine to designate a different install directory for each version, e.

Note that regardless of whether you install multiple versions or run them from the build directory, you will still have to designate which version of Wine you wish to use when running applications. It is also recommended that applications being run with different Wine versions be installed into separate wineprefixes.

WineHQ binary packages are available for 64 bit, and most major distros package it for users. Normally, installation should be as simple as installing the Wine package for your distribution through your package manager. Check the Download page. If you are building Wine from source, see Building Wine for instructions on how to build 32 bit Wine on a 64 bit system and instructions on how to build 64 bit Wine in a shared WoW64 setup.

If you have replaced the customized distro that came preinstalled on your netbook Xandros, Linpus, etc. If you are still using Xandros eeePC , Linpus Acer Aspire One or any other customized distro, you will have to ask on your netbook's support forum. Only other users of those distros can advise you on what, if any, binary packages will work on your system, where to find them, and how to install them.

You can also try building Wine from source following the instructions in Building Wine , but you will still need to consult your netbook's support forum regarding satisfying dependencies on your particular system. No, not even in Linux. The Darwine project was an effort to do just that, but it has not been maintained in many years. Uninstalling Wine itself will not revert your Wine settings or uninstall your Windows apps, which are permanently stored in your user's home directory.

Do not uninstall Wine if you only wish to remove all of your settings and apps. For instructions on removing your Wine settings and apps, see How do I wipe the virtual Windows installation?

To uninstall 64 bit applications, including wine-mono, you need to run it with wine The uninstaller should remove menu and desktop entries To clean Open With List , please carefully paste the following commands into a terminal:. You can remove your virtual Windows installation and start from scratch by deleting the hidden.

This will remove all of your Wine settings and Windows applications. The simplest and safest way to do this is through your file manager. Simply set your file manager to show hidden files, browse to your home directory, and delete.

If you want to keep it as a backup, you can rename or move it instead. To the host system, a wineprefix is just another directory that can be deleted, moved, renamed, etc.

If you prefer to do it from the command line, carefully paste the following commands into a terminal:. To remove these leftover menu entries, carefully paste the following commands into a terminal:.

Alternatively, you can stop Wine from creating menu entries in the first place. Short answer: you have to install them in Wine just like you did in Windows. Applications usually have a setup or installer program.

Long answer: some applications can be copied from Windows to Wine and still work, but don't try this unless you like tinkering under the hood of your car while it's running. Wine is not designed to interact with an existing Windows installation.

If you have any data you need from a Windows installation, browse your Windows filesystems in your normal file manager and copy the data to another location.

This will break Windows and require a Windows reinstall. We have tried to make this hard to do, so you probably cannot do it by accident. The only way to fix Windows after this has happened is to reinstall it. See Wine User's Guide Running. Use winetricks to install whatever version of. NET the program requires, cd to the directory containing the. Note that this change will have to be made every time you upgrade Wine, as it will be reverted whenever the wineprefix is updated.

You can then start native applications using wine cmd if you specify the full path or use the shell, e. You might also need winepath to translate the filename from Windows format to Linux format see How do I associate a native program with a file type in Wine? Usually, you really don't have enough free disk space.

Wine's C: drive is located in your home directory. Optionally configure Wine using the winecfg command. Wine should work without any additional configuration options. To test your installation run the Wine notepad clone using the wine notepad command. Check the Wine AppDB for specific instructions or steps required to install or run your application.

The first command you will run will be to install an application. Different software programs are designed for different operating systems, and most won't work on systems that they weren't designed for. Windows programs, for example, won't run in Linux because they contain instructions that the system can't understand until they're translated by the Windows environment. Linux programs, likewise, won't run under the Windows operating system because Windows is unable to interpret all of their instructions.

This situation presents a fundamental problem for anyone who wants to run software for both Windows and Linux. When a Windows program is needed, the user boots the machine into Windows to run it; when a Linux program is then needed, the user then reboots the machine into Linux.

This option presents great difficulty: not only must the user endure the frustration of frequent rebooting, but programs for both platforms can't be run simultaneously. Having Windows on a system also creates an added burden: the software is expensive, requires a separate disk partition, and is unable to read most filesystem formats, making the sharing of data between operating systems difficult.

Wine makes it possible to run Windows programs alongside any Unix-like operating system, particularly Linux. Think of Wine as a compatibility layer, when a Windows program tries to perform a function that Linux doesn't normally understand, Wine will translate that program's instruction into one supported by the system.

For example, if a program asks the system to create a Windows pushbutton or text-edit field, Wine will convert that instruction into its Linux equivalent in the form of a command to the window manager using the standard X11 protocol. If you have access to the Windows program source code, Wine can also be used to recompile a program into a format that Linux can understand more easily.

Wine is still needed to launch the program in its recompiled form, however there are many advantages to compiling a Windows program natively within Linux. For more information, see the Winelib User Guide. Throughout the course of its development, Wine has continually grown in the features it carries and the programs it can run.

A partial list of these features follows:. Wine is an open source project, and there are accordingly many different versions of Wine for you to choose from. WineHQ currently offers time-based releases in two branches: stable and development. In addition, you can install the most up-to-date development version of Wine by using the latest available source code from the Git repository generally updated 5 days per week.

Each version of Wine has a release tag. Beginning with Wine 2. If you are using git , the tag will be generated by the git-describe command, and looks like:.

Examples: wine There are a number of programs that are derived from the standard Wine codebase in some way or another. Some of these are commercial products from companies that actively contribute to the Wine project.

These products try to stand out or distinguish themselves from the standard version of Wine by offering greater compatibility, easier configuration, and commercial support.

If you require such things, it is a good idea to consider purchasing these products. There are many ways to run software other than through Wine.

If you are considering using Wine to run an application you might want to think about the viability of these approaches if you encounter difficulty. Instead of running a particular Windows application with Wine, one frequently viable alternative is to simply run a different application. Many Windows applications, particularly more commonly used ones such as media players, instant messengers, and filesharing programs have very good open source equivalents.

Furthermore, a sizeable number of Windows programs have been ported to Linux directly, eliminating the need for Wine or Windows entirely. These alternatives should be found through your system package management facilities. Probably the most obvious method of getting a Windows application to run is to simply run it on Windows.

However, security, license cost, backward-compatibility, and machine efficiency issues can make this a difficult proposition, which is why Wine is so useful in the first place. Another alternative is to use ReactOS , which is a fully open source alternative to Windows. ReactOS shares code heavily with the Wine project, but rather than running Windows applications on top of Linux they are instead run on top of the ReactOS kernel.

ReactOS also offers compatibility with Windows driver files, allowing the use of hardware without functional Linux drivers. Rather than installing an entirely new operating system on your machine, you can instead run a virtual machine at the software level and install a different operating system on it.

Thus, you could run a Linux system and at the same time run Windows along with your application in a virtual machine simultaneously on the same hardware. Virtual machines allow you to install and run not only different versions of Windows on the same hardware, but also other operating systems, including ReactOS. There are several different virtual machine offerings out there, and some are also able to emulate x86 hardware on different platforms.

There are significant drawbacks to using virtual machines, however. Unlike Wine, such programs are emulators, so there is an inevitable speed decrease which can be quite substantial.

Furthermore, running an application inside a virtual machine prevents fully integrating the application within the current environment. You won't, for example, be able to have windows system tray icons or program shortcuts sitting alongside your desktop Linux ones, since instead the Windows applications must reside completely within the virtual machine. Once you've decided that Wine is right for your needs, the next step is to decide how you want to install it. There are three methods for installing Wine from WineHQ, each with their own advantages and disadvantages.

By far the easiest method for installing Wine is to use a prepackaged version of Wine. These packages contain ready-to-run Wine binary files specifically compiled for your distribution, and they are tested regularly by the packagers for both functionality and completeness. Packages are the recommended method for installing Wine. We make them easily available at the WineHQ downloads page , and these are always the latest packages available.

Being popular, Wine packages can also be found elsewhere in official distribution repositories. These can, however, sometimes be out of date, depending on the distribution.

Packages are easily upgradable as well, and many distributions can upgrade Wine seamlessly with a few clicks. Building your own installable binary package from a source package is also possible, although it is beyond the scope of this guide.

Sometimes the Wine packages don't fit your needs exactly. Perhaps they're not available for your architecture or distribution, or perhaps you want to build Wine using your own compiler optimizations or with some options disabled, or perhaps you need to modify a specific part of the source code before compilation.

Being an open source project, you are free to do all of these things with Wine source code, which is provided with every Wine release. This method of installation can be done by downloading a Wine source archive and compiling from the command line.

If you are comfortable with such things and have special needs, this option may be for you. Getting Wine source archives is simple.

Every release, we put a source package in compressed tar. Compiling and installing Wine from source is slightly more difficult than using a package, however we will cover it in depth and attempt to hold your hand along the way.

If you wish to try out the bleeding edge of Wine development, or would even like to help develop Wine yourself, you can download the very latest source code from our Git repository. Please take note that the usual warnings for using a developmental version still apply. The source code on the Git repository is largely untested and may not even compile properly. It is, however, the best way to test out how Wine will work in the next release, and if you're modifying source code it's best to get the latest copy.

The Git repository is also useful for application maintainers interested in testing if an application will still work right for the next release, or if a recent patch actually improves things. If you're interested in helping us to get an application working in Wine, see the Wine Installation and Configuration guide. Installing a package on a fresh system is remarkably straightforward.

Simply download and install the package using whatever utility your distribution provides. There is usually no need to explicitly remove old packages before installing, as modern Linux distributions should upgrade and replace them automatically.

If you installed Wine from source code, however, you should remove it before installing a Wine package. See the section on uninstalling Wine from source for proper instructions. Wine works on a huge amount of different Linux distributions, as well other Unix-like systems such as Solaris and FreeBSD, each with their own specific way of installing and managing packages.

Fortunately, however, the same general ideas apply to all of them, and installing Wine should be no more difficult than installing any other software, no matter what distribution you use. Uninstalling Wine packages is simple as well, and in modern Linux distributions is usually done through the same easy interface as package installation.

We won't cover the specifics of installing or uninstalling Wine packages among the various systems' methods of packaging and package management in this guide, however, up to date installation notes for particular distributions can be found at the WineHQ website in Category:Distributions. If you need further help figuring out how to simply install a Wine package, we suggest consulting your distribution's documentation, support forums, or IRC channels.

Before installing Wine from source, make sure you uninstall any Wine binary packages you may have on your system. Installing from source requires use of the terminal window as well as a full copy of the Wine source code.

Once having downloaded the source from Git or extracted it from an archive, navigate to it using the terminal and then follow the remaining steps. Wine makes use of many open source libraries during its operation. While Wine is not strictly dependent on these libraries and will compile without most of them, much of Wine functionality is improved by having them available at compile time.

In the past, many user problems were caused by people not having the necessary development libraries when they built Wine from source; because of this reason and others, we highly recommend installing via binary packages or by building source packages which can automatically satisfy their build dependencies.

If you wish to install build dependencies by hand, there are several ways to see if you're missing some useful development libraries. The most straightforward approach is to watch the output of configure before you compile Wine and see if anything important is missing; if it is, simply install what's missing and rerun configure before compiling.

Once you've installed the build dependencies you need, you're ready to compile the package. In the terminal window, after having navigated to the Wine source tree, run the following commands:. Since Wine can be run from the build directory, it is not necessary to install it.

If you do wish to install it, after the wine build is complete, run. This command requires root privileges. Although you should never run Wine as root, you will need to install it this way. To uninstall Wine from source, once again navigate to the same source folder that you used to install Wine using the terminal. Then, run the following command:. This command will require root privileges, and should remove all of the Wine files from your system. It will not, however, remove your Wine configuration and applications located in your user home directory, so you are free to install another version of Wine or delete that configuration by hand.

This chapter will describe all aspects of using Wine, such as basic Wine invocation, installing and running Windows executables, command line parameters of various Wine support programs, etc. The first argument should be the name of the file you want wine to execute.

If the executable is in the Path environment variable, you can simply give the executable file name. However, if the executable is not in Path , you must give the full path to the executable. See How to run Windows programs from the command line for more information. Most binary Wine packages will associate Wine with.

If that is the case, you should be able to simply double-click on the. DataTypex is the data type for the registry value and immediately follows the equal sign.

In this case, Regedit. The following table lists the typical registry data types:. For more information about registry data types, click the following article number to view the article in the Microsoft Knowledge Base:. Use hexadecimal format for binary data items. Note You can enter several data item lines for the same registry path. Note the registry file should contain a blank line at the bottom of the file.

To add a registry subkey or add or change a registry value, make the appropriate changes in the registry, and then export the appropriate subkey or subkeys. Exported registry subkeys are automatically saved as. To make changes to the registry and export your changes to a. Click File , and then click Export. This step backs up the subkey before you make any changes.

You can import this file back into the registry later if your changes cause a problem. In the File name box, type a file name to use to save the. Note Use a file name that reminds you of the contents, such as a reference to the name of the subkey.

Repeat steps 3 and 4 to export the subkey again, but use a different file name for the. You can use this. Test your changes on the local computer. If they cause a problem, double-click the file that holds the backup of the original registry data to return the registry to its original state. If the changes work as expected, you can distribute the. To delete a registry key with a.