2007-01-04 17:29:39 +01:00
|
|
|
Violation of existing windows:
|
|
|
|
------------------------------
|
2007-10-05 00:39:47 +02:00
|
|
|
Wine can corrupt MS Windows installation.
|
2007-01-04 17:29:39 +01:00
|
|
|
|
|
|
|
It is recommended to copy whole of windows to another destination
|
|
|
|
and to configure wine for this copy.
|
|
|
|
|
|
|
|
|
2007-10-05 00:39:47 +02:00
|
|
|
1. All configuration data is in the registry, and can be accessed
|
|
|
|
directly by editing system.reg or user.reg, "wine regedit.exe" or
|
|
|
|
with the graphical configuration frontend "winecfg".
|
2007-01-04 17:29:39 +01:00
|
|
|
|
2007-10-05 00:39:47 +02:00
|
|
|
2. Drives are configured by symlinking in ~/.wine/dosdevices/
|
2007-01-04 17:29:39 +01:00
|
|
|
|
2008-05-06 01:44:08 +02:00
|
|
|
3. You have to set the WINEPREFIX variable to the wine base dir,
|
|
|
|
if it is different than ~/.wine.
|
2007-01-04 17:29:39 +01:00
|
|
|
|
2007-10-05 00:39:47 +02:00
|
|
|
4. Running "wineprefixcreate" will update or create such a wine base
|
|
|
|
directory.
|
2007-01-04 17:29:39 +01:00
|
|
|
|
|
|
|
There usually is no need for additionaly configuring wine.
|
|
|
|
|
|
|
|
If no ~/.wine is present, it will setup a fake windows
|
|
|
|
environment in ~/.wine by itself, including all necessary config
|
|
|
|
file and registry settings by running "wineprefixcreate".
|
|
|
|
|
|
|
|
Start wine:
|
|
|
|
-----------
|
2007-10-05 00:39:47 +02:00
|
|
|
Check whether wine runs by entering (e.g.) 'wine sol.exe' or
|
2007-01-04 17:29:39 +01:00
|
|
|
'wine progman'.
|
|
|
|
|
|
|
|
|
|
|
|
Error and warning messages:
|
|
|
|
---------------------------
|
2008-06-26 01:10:51 +02:00
|
|
|
Wine is intensively developed but always isn't complete.
|
|
|
|
Therefore things might not work and wine prints lots of error and
|
|
|
|
warning messages.
|