Wine emulate windows xp

However, if you are using an 64bit installation of Ubuntu, you will need to run these additional commands:. This will add 32bit architecture support on your distro which will benefit you in installing specific software. There is a large number of Windows applications that are currently fully supported by Wine. They will run without any hassle. However, new Windows applications are being developed every day.

But the development pace of Wine is also rapid, support for new applications is being added all the time. Wine Application Database has almost 24, applications rated with different status depending upon how well that applications run in Wine. If you want to quickly check the rating of the application you want to use in Wine, you can take a look there.

Here are the meaning of those ratings:. Reviews, Installation Procedure, which Wine version it was tested against and various useful data are also available for each application here.

Of course, Wine Application Database is mostly user-generated data, so you are always welcome to try running an application with a different version of Wine and share your result with rest of the community. Go to Wine Application Database. Click Browse Apps from the left sidebar. There will be a list of various versions with their compatibility rating with a specific Wine version. This is the main page you need to check.

There will be detailed information about that specific version. Also, the installation procedure will be included here if any additional tasks are needed for installation.

Before we go on installing and running applications in Wine, we should have clear idea about a few things and about how to configure Wine for usage:. Windows applications need a C: drive. Wine uses a virtual C: drive for this purpose. The directory of this virtual C: drive is called wineprefix. First of all, we need to create a wineprefix. For doing that, fire up a terminal and enter this command:.

This will create a wineprefix and open the configuration window for Wine. You can change the configuration options if you want or let it be as is for time being and close it.

Now, you can locate the virtual C: drive at. The general rule is to install each new application into a fresh wineprefix. We can create and maintain multiple wineprefix manually. But that task would seem rather tedious for the beginners. So, we will skip that part for now. Installing a supported application in Wine is generally as easy as double-clicking on the installation file. However, we are now going to see a step-by-step guide for installing 7-zip on Wine.

First of all, check for 7-zip rating on Wine Application Database. It has Platinum rating, so we are good to go. Open Wine configuration winecfg and set the Windows Version to Windows 7.

See that destination folder path? Such emulation is almost always much slower than execution of the same code by the processor for which the code was compiled. In Wine, the Windows app's compiled x86 code runs at full native speed on the computer's x86 processor, just as it does when running under Windows.

And Windows API calls and services also are not emulated, but rather substituted with Linux equivalents that are compiled for x86 and run at full, native speed. I think your article is just fine as is. I can give two more cases where an USB device doesn't work with a program through wine. Good point gtriderxc! Mako Guest. Tutorial is OK. Everything went fine until I can do nothing with this EULA. There is an OK on its end, but I can do nothing with it. So I didn't reach the configuration.

What can I do? Mako said:. I'm a brand new user of linux mint When I wanted to close terminal, it said it was a process running. Thank you for helping. YakAttack Guest. When the EULA appears, press tab. Hit space. I was stumped at the same spot for awhile, there is an answer on the Ubuntu forums.

While I think there are bigger things to worry about in the world, ATeal is probably correct about the naming of this thread, in that, if you're going to write these types of articles, it's important that they're factually correct, not your perceived version of correct. The title is incorrect - irrespective of what people think. If you want to write good articles, then you should not just feed into "what people think", but instead post the facts.

Currently it is used mainly for internet surfing and playing wizard by my son. Which linux system would you recommend to use with WINE for the best results to run as close to XP as possible my husband suffers from issues figuring out changes with regard to computers. You must log in or register to reply here.

Total: members: 8, guests: Latest posts L. Wine increases the usefulness of Linux, makes it easier for users to switch to free operating systems, and for Windows developers to make applications that work on them.

This greatly raises Linux marketshare, drawing more commercial and community developers to Linux. There is a lot of confusion about this, particularly caused by people getting Wine's name wrong and calling it WINdows Emulator. When users think of an emulator, they tend to think of things like game console emulators or virtualization software. However, Wine is a compatibility layer - it runs Windows applications in much 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. That said, Wine can be thought of as a Windows emulator in much the same way that Windows Vista can be thought of as a Windows XP emulator: both allow you to run the same applications by translating system calls in much the same way.

Thinking of Wine as just an emulator is really forgetting about the other things it is. Wine's "emulator" is really just a binary loader that allows Windows applications to interface with the Wine API replacement. Wine is the base of the project, where most of the work is being done. Wine is not perfect, but tens of thousands of people nevertheless use "vanilla" Wine successfully to run a large number of Windows programs. 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 proportion 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 formerly WineX is a product from a company called TransGaming.

TransGaming based their product on Wine back in when Wine had a different license, closed their source code, and rebranded their version as specialized for gamers. In the years since Cedega was originally created from Wine, development on Wine and Cedega have continued mostly independently.

TransGaming currently gives back very little code to Wine. Cedega is not "Wine with more gaming support" - because Wine has had years of development since Cedega was made, and many games actually run better under Wine than under 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 the license differences between Cedega and Wine.

Normally you do not have to use the command line to use Wine in Linux. You can use a graphical interface for most things, much like on Windows. In many cases you can right-click an installer and select "Open with Wine", or just double-click it.

You can start installed programs using the shortcut icon or menu. However, there are several situations when you might need to use the command line. 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. You can check by running:. If the amount of space you need is less than 1 GB, and df reports you have more than 1 GB available, try setting the Windows version to Windows This will work around bugs in some old Windows 98 era installers that could not cope with large drives.

If you want to use a different partition that has more free space, use a wineprefix that is located on the other partition. See How can I run two programs as if they were on different computers?

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 let them know there's a problem.