5.2. How do I install Windows in Wine under Linux?
Simple answer: you CAN'T. Windows demands direct access to the hardware and cannot get it with Wine and UNIX in the way
Wine is supposed to be primarily used WITHOUT Windows. If you want to use a Windows installation, then use an existing installation alongside the UNIX installation (see the dual-boot HOWTO for your OS for more details). Or alternatively use the cabextract utility to extract Windows install archives to a directory that you want to use as Wine's Windows tree.
5.3. How do I configure Wine to run on my system?
As of Wine release 20050725 the config file has been disabled and the values are now stored instead in registry files in your .wine directory. The preferred method to configure Wine is with winecfg, winecfg is a tool to make it easy for new users to edit some of the contents of there registry files.
5.4. How do I upgrade Wine without losing my working configuration?
Upgrading the wine installation does not affect the existing wine registry settings. So after upgrading wine you still have the old (working ) wine registry configuration.
5.5. If I want to use a Windows install, which versions are OK?
Either use a classic no-windows install (Wine is getting better all the time) or use a Win9x install (Win95, 98, 98SE, ME). DON'T configure Wine to use an NT-based Windows install (NT, Win2K, WinXP, Win2K3).
In general, most Windows installations contain vast quantities of garbage that can confuse Wine and make it less reliable. If you can, it's best to install the programs you want into Wine's fake windows drive.
5.6. If I use a Windows install with Wine, which one works best?
As of 09/2005:
I'd say Win98SE is the best version to use with Wine, as it's fairly widespread amongst developers and relatively old. Using Win2K files is definitely worse than a plain no-windows Wine install, and Win ME is said to be problematic, too (as probably no developer uses it). In short: all Win9x <= W98SE are good.
5.7. Installing applications generated by Visual Basic won't run. What should I do?
Make sure you have all the VB run time libraries installed. You can get the latest version from the Microsoft web site.
5.8. When I click on *.exe file in my file Manager, nothing happens.
The normal Wine releases don't have .exe extensions registered for Wine in KDE/Gnome yet. You have to open a terminal window instead (often an icon showing a "black screen") and type something like: cd /my/windows/program/directory
wine myprogram.exe
5.9. bash says "wine: Command not found" What can I do?
Try to logout and login again into bash. That might fix it.
If it doesn't, then make sure the wine binary is in your PATH.
Run as root: find / -name "wine" -type f -perm +111
to find the path where the wine binary is in. Then check whether PATH includes it: echo $PATH
If not, add that e.g. to /etc/profile by doing: export PATH=$PATH:/path/to/wine/binary
That should help.
For complete packages, use http://rpmseek.com/ or the Download section.
5.10. How do I remove Wine from my Computer?
It depends on how you installed. If you used an RPM, the right command is this: rpm -e wine (as root)
If you installed from source (the .tar.gz file), the right way to do it is to change to the root of the source tree (the directory with the configure script, readme etc) then run as root: make uninstall
6.1. How do I run an MS Windows program under Wine?
When invoking Wine, you must specify the entire path to the executable, or by file name only. For example to run Windows' solitaire, type any of the following:
wine sol or wine sol.exe (using the search path to locate the file).
wine c:\\windows\\sol.exe (using a DOS file name).
wine /usr/windows/sol.exe (using a UNIX file name).
wine "c:\windows\sol.exe" (using quoted DOS file name).
The path of the file will also be added to the path when a full name is supplied on the command line.
6.2. I have installed and configured Wine, but Wine cannot find MS Windows on my drive. Where did I go wrong?
If you have a DOS partition, first make sure that you have mounted it, either by putting the entry into /etc/fstab, or by manually mounting it.
Remember too that unless your version of UNIX can see through it, or you are running a utility that can see through it, your DOS partition must not be located on a Drivespaced, Doublespaced or Stackered partition, as neither Linux, FreeBSD, NetBSD or Wine can natively 'see' files located in these compressed DOS partitions.
Check your path statements in the wine.conf file. No capital letters may be used in paths, as they are automatically converted to lowercase.
6.3. I was able to get various MS Windows programs to run, but parts of them do not work. What is wrong?
Wine is not complete at this time, so some of each programs' features may not work. They will in time as more of the MS Windows API calls are included in Wine.
6.4. I have run various MS Windows programs, but since the program menus do not work, how can I exit these programs?
Menus should be working correctly, if for some reason your applications menus stops responding. You can kill the xterm shell window that you called up to run your MS Windows program, and the X window that appeared with the program will be killed too. If you started the application from a shortcut you can open a terminal and start xkill and just click on the application to kill it.
6.5. My program doesn't work, what can I do?
If you are a programmer and know C, then start debugging Wine and help us make it better! If you can't, then you will have to either convince a Wine developer to try and make your program work (there must be a downloadable version or demo for that).
You can submit your application to the Wine Application DB and gather tips on ways to get your app to work its best.
You can also submit your application to the CodeWeavers CrossOver Compatibility Center. Where you can pledge/vote toward future support of your favorite application.
We recommend that you try builtin dlls first and report any errors that you may run across to wine-devel or to our Bugzilla. If you report problems they can be verified and fixed by the development team and this helps everyone over the long run by not covering up bugs with the use of native dlls.
Alternatively, you may be able to get the app working by taking native DLLs from a Microsoft Windows install, and using them (set the dlls to native with winecgf). Not all DLLs can be replaced that way - in particular DirectX cannot be, nor can some core system DLLs like gdi32, user, ntdll, kernel32, etc.
6.6. Can I use Wine with SUSE, RedHat or other Linux Distro's?
You can use Wine on any sufficiently recent Linux installation. The amount of work getting Wine up and running depends on whether you install a binary packages or do a source install.
6.7. Does Wine work with AMD Processors?
Yes, it does. Wine should work on any processor compatible with the Pentium or greater.
6.8. Can I launch a Unix program from a Windows program?
Sure, Wine supports that. Just enter the unix program name wherever a program has something that it's supposed to execute, and it should just work.
6.9. I get "Error installing iKernel.exe: (0x1400)" when running an InstallShield 6 installer.
If you get the error "Error installing iKernel.exe: (0x1400)" at any point, it's probably because there are leftover processes from a previous try. You can verify this with the command
$ ps augxw grep wine
If that command shows old copies of wine running your setup, you need to kill them before you can run the setup program. If there are no other Wine programs running, you can kill them all with the command
$ killall wine
If you're also running Wine programs you care about, you'll have to kill off the old Setup instances one by one using kill and the individual PIDs (or perhaps Wine's spiffy Task Manager, which doesn't exist yet).
You should repeat the ps to make sure all of the old Wine processes are gone.
