###############################################################################
# This file is the part of WineSetupTk and stores the help messages and 
# tooltips for all the screens.
# Copyright 2003 Vincent Bron
# Copyright 2003 Alex Pasadyn
#
# Text in section with same name as class will appear after "help" button
# press on that screen. The first line is a "blue" title of help screen.
#
# Names of classes which implements screens:
#
# Welcome screen                     - CScrFileLoc
# Windows installation location      - CScrWinLoc
# Look & feel                        - CScrLook
# Window mode                        - CScrWindowMode
# Drives                             - CScrDrives
# Paths                              - CScrPaths
# Advanced Look & feel               - CScrMoreLook
# DLLs                               - CScrDLL
# Ports                              - CScrPorts
# Registry                           - CScrRegistry
# Finish                             - CScrFinish
###############################################################################

[ApplyTo-OptionMenu]
Choose an application profile the setting is related to

[CScrFileLoc]
File Location
Here you can choose the location of the file you would like to create
or edit.  File names with a '~' prefix store your wine configuration
in a user-specific place, and will not affect other users.  Other
prefixes store the Wine configuration as global data, which may affect
other users.  You must have root privileges to edit the global
configuration.

By default, Wine will load the configuration from the ~/.wine/config
file.  If a ~/.wine/config file does not exist for a particular user,
Wine will use the global defaults instead.  

If the file you wish to open isn't listed, use the "Other" field to
specify the path to the file.

Files that are not writable can be viewed in READ-ONLY mode.

[CScrWinLoc]
Location of Windows Files
Wine can be run whether or not Windows has been installed on the system.
When Windows is present, and its location is specified, Wine can load
registry settings and DLLs from it.

Usually, you will not have to modify anything on this screen.  If
Windows has been installed, the Wine Configuration Wizard will attempt to
autodetect its location.  As long as there is some entry for it in the
/etc/fstab file and the partition is mounted, the autodetect process ought
to find your existing Windows partition and react appropriately.

The wizard will also automatically detect a default Windows user.  Wine
will load some of the registry settings from either the user.dat or the
ntuser.dat file for the selected user.

If you do not have a Windows installation, the wizard will create a set
of empty directories for you.  Wine will then use its own default registry
and all of its own builtin DLLs.  When you install applications with Wine,
they will end up in this path.

[CScrWinLoc-rbUseExists-Tooltip]
If Windows has been installed on this system and the wizard was able to
autodetect its location, you can select it from the following list.

[CScrWinLoc-omAutoDetect-Tooltip]
Select one of the autodetected Windows partitions.  If the wizard 
failed to autodetect your Windows partition, choose "Other" and
specify its location.

[CScrWinLoc-omUser-Tooltip]
Wine will load some of the registry settings for this user

[CScrWinLoc-eOtherExistWinRootDir-Tooltip]
When it necessary to explicitly specify the location of the Windows
partition, be sure to fill in the fields on the "Drives" and "Paths"
pages in the Advanced section that follows. 

[CScrWinLoc-rbCreateFake-Tooltip]
Select this if you would like to use Wine without Windows.  An empty
Windows directory structure will be created at the path specified.

[CScrLook]
Look and Feel
Here you can choose look and feel for Windows programs running under
Wine.  There are three possibilities: Windows 3.1, Windows 95 and
Windows 98.  Note that at the present time, the differences between
the Windows 95 and the Windows 98 look and feel under Wine are slight. 

Note that this setting is related to look and feel only: it does not affect
Windows version Wine will emulate (--winver switch).

[CScrLook-Preview-Tooltip]
Preview

[CScrWindowMode]
Window Mode
Wine has three different modes for managing the windows of an
application: Managed, Unmanaged, and Desktop.  

  Managed Window Mode

In managed mode, Wine allows the X Window Manager to manage the
windows of the application, integrating it into the X Window System 
desktop.  This allows the windows of the application to be behave as
though they were native to the X environment, and not necessarily as
they would under Windows.  One such case is an application that attempts
to draw on a window's title bar.  In the X Window System, only the window
manager is able to draw on the title bar, so any such attempts would be
ignored.

  Unmanaged Window Mode

Alternatively, in unmanaged mode, Wine presents the application with the
selected Windows look and feel.  The application windows have borders and
a title bar that are similar to that in the Windows environment.  The
trade-off to this is that in unmanaged mode, these windows are not
integrated into the X Window System desktop, so the window manager knows
nothing about them.  A Wine application running in this mode will not appear
in your task bar, for instance.  This mode is compatible with applications
that manipulate their own window decorations.

  Desktop Window Mode

Desktop mode will create a virtual Windows desktop inside of a fully
managed X window.  The size of the desktop may also be specified.

So called "Application profile" ("Apply to" option) allows you to define
settings described above for specific application only. Application is
identified by its executable name. For example you can define application
profile named "notepad.exe". Then in case "notepad.exe" program is executed
under Wine setting from associated application profile is used rather than
"General" one. Only in case it's not found there then the "General" value
is used.

Note that if you define application profile on this screen, profile with
the same name will appear at "Look and Feel (Advanced)" screen also. It's
because both these screens are projected into the same section in Wine 
configuration file.

[CScrWindowMode-rbManaged-Tooltip]
Managed mode provides the best integration of Wine windows
into your X Window System.  However, under some conditions
this may change the look and feel of an application.

[CScrWindowMode-rbUnmanaged-Tooltip]
Unmanaged mode provides the default Windows look and feel, without 
integrating the application into the X Window System desktop.

[CScrWindowMode-rbDesktop-Tooltip]
Desktop mode will create a virtual Windows desktop inside of a fully
managed X window.  The size of the desktop may also be specified.

[CScrWindowMode-Preview-Tooltip]
Preview

[CScrDrives]
Drives
Paths listed here will be available to Wine programs under the letters
you assign them. You can use these settings in Wine to map Windows drives
to UNIX paths.  For example, if you set the E drive to path /tmp, Wine
will display the files in /tmp whenever a Wine application tries to
display the E: drive.

Usually it's a good idea to at least setup your floppy drive, your
CD-ROM drive, and the path to your Windows installation. The wizard
will also scan your /etc/fstab file for other possible mappings. Feel
free to customize the default list to your tastes, although you should
be careful about changing the provided A: and C: drives.

[CScrDrives-Listbox-Tooltip]
Assign letters to drive paths you would like Wine to use.  
The autodetected drives that could be useful are provided by default.

[CScrDrives-Edit-Letter-Tooltip]
Drive letter to be assigned

[CScrDrives-Edit-Path-Tooltip]
The UNIX path that Wine should map this drive to

[CScrDrives-Edit-Type-Tooltip]
The type of drive

[CScrDrives-Edit-Device-Tooltip]
The device path for the drives that Wine should have raw
access to.  Usually floppy drives require something like
"/dev/fd0", and CD-ROM drives something like "/dev/cdrom".
It is not necessary to set this if the drive is a hard-disk.

[CScrPaths]
Paths
These paths are needed in order to run Wine correctly.
Note that these paths are in Windows format.

  Windows

Path to the Windows directory (e.g. c:\windows)

  System

Path to the Windows System directory (e.g. c:\windows\system)

  Profile

The directory where the user specific registry file is stored 
(ntuser.dat for Windows NT and user.dat for Windows 95/98/ME).
A valid path might be "c:\winnt\Profiles\Default User".

  Temp

The value of the environment variable $TEMP for an application
running under Wine.

  Path

The value of the environment variable $PATH for an application
running under Wine.

[CScrPaths-Windows-Tooltip]
Path to the Windows directory
(e.g. c:\windows)

[CScrPaths-System-Tooltip]
Path to the Windows System directory
(e.g. c:\windows\system)

[CScrPaths-Profile-Tooltip]
Path to a Windows Profile directory
(e.g. "c:\winnt\Profiles\Default User")

[CScrPaths-Temp-Tooltip]
The value of the environment variable $TEMP
for an application running under Wine

[CScrPaths-Path-Tooltip]
The value of the environment variable $PATH
for an application running under Wine

[CScrMoreLook]
Look and Feel (Advanced)
These are more advanced settings related to Look and Feel.

  Use DGA

This specifies whether you want DirectDraw to use XFree86's Direct
Graphics Architecture (DGA), which is able to take over the entire
display and run the program full-screen at maximum speed.

With DGA1 (XFree86 3.x), you still have to configure the X server to
the game's requested bpp first, but with DGA2 (XFree86 4.x), runtime
depth-switching may be possible, depending on your driver's capabilities.
Be aware that if Wine crashes while in DGA mode, it may not be possible
to regain control of your computer without rebooting.

DGA normally requires either root privileges or read/write access
to /dev/mem. 

  Use X shared memory
(X shared memory is now an obsolete Wine option which doesn't
have any effet)

If you don't want DirectX to use DGA, you can at least use X Shared
Memory extensions (XShm). It is much slower than DGA, since the app
doesn't have direct access to the physical frame buffer, but using
shared memory to draw the frame is at least faster than sending the
data through the standard X11 socket, even though Wine's XShm support
is still known to crash sometimes.

  DX Grab

If you don't use DGA, you may want an alternative means to convince
the mouse cursor to stay within the program window. This option does
that. Of course, as with DGA, if Wine crashes, you're in trouble
(although not as badly as in the DGA case, since you can still use the
keyboard to get out of X).

  Double-buffered desktop

Applies only if you use the Wine desktop mode to run in a
desktop window. Specifies whether to create the desktop window with a
double-buffered visual, something most OpenGL games need to run
correctly.

Application profile ("Apply to" option) allows you to define setting
valid for specific application only (as described in "Window Mode" 
screen help text).

[CScrMoreLook-DGA-Tooltip]
Enables DirectDraw to use XFree86's Direct Graphics
Architecture, which is able to take over the entire
display and run the program full-screen at maximum speed

[CScrMoreLook-XVidMode-Tooltip]
Enables the XVidMode extension, if present.  This extension provides
resolution switching and gamma correction functionality.

[CScrMoreLook-XRandR-Tooltip]
Enables the XRandR extension, if present.  This extenstion provides
resolution switching functionality.

[CScrMoreLook-TakeFocus-Tooltip]
Enables the use of the take focus protocol.

[CScrMoreLook-DXgrab-Tooltip]
Select this to convince the mouse cursor
to stay within the program window

[CScrMoreLook-DblBuffDesk-Tooltip]
Specifies whether to create the desktop window with a double-buffered
visual, something most OpenGL games need to run correctly. Applies only if
you use the Wine desktop mode to run in a desktop window.

[CScrDLL]
DLLs
The defaults are reliable, and should work for most purposes.  Use
extreme caution when changing these settings, as misconfiguration
of the load order can cause Wine to no longer work properly.

  native

A "native" DLL is a .DLL file written for and often distributed with
Microsoft Windows.

  builtin

A "builtin" DLL is a DLL implemented by Wine. These can either be a
part of libwine.so, or a special .so file that Wine is able to load on
demand.

  so

A native Unix .so file, with calling convention conversion thunks 
generated on the fly as the library is loaded. This is useful for 
libraries such as "glide" that has exactly the same API on both
Windows and Unix. 

DLL overrides define how you want specific DLLs to be handled, in
particular whether you want to use "native" DLLs or not, if you have some
from a real Windows configuration. Because builtins do not mix seamlessly
with native DLLs yet, certain DLL dependencies may be problematic, but
workarounds exist in Wine for many popular DLL configurations. Also see
WWN's [16] StatusPage to figure out how well your favorite DLL is implemented
in Wine. 

DLL override named "*" has special meaning. It applies in case no other
override is in effect.

Most often, you will use native or builtin DLLs with Wine.

Application profile ("Apply to" option) allows you to define setting
valid for specific application only (as described in "Window Mode" 
screen help text).

[CScrDLL-Overrides-Tooltip]
Drag and drop entries to modify their order

[CScrDLL-Edit-LeftLB-Tooltip]
Double-click an entry to make it active 

[CScrDLL-Edit-RightLB-Tooltip]
Double-click an entry to remove it
from the active list; drag and drop
entries to modify their order

[CScrPorts]
Ports
You can specify the devices to be used as COM1-COM4 and LPT1-LPT4,
as well as set the spooler entries for the LPT1-LPT4 ports.

[CScrPorts-COM-Tooltip]
Specify the device used for this COM port

[CScrPorts-LPT-Tooltip]
Specify the device used for this LPT port

[CScrPorts-Spooler-Tooltip]
Specify the spooler entry used for this LPT port

[CScrRegistry]
Registry 
After Win3.x, the registry became a fundamental part of Windows, as 
a place where Windows and the applications that run on it can share 
configuration and state data.  While most sane system administrators
(and Wine developers) curse badly at the twisted nature of the Windows
registry, it is still necessary for Wine to support that functionality.

  Load global registry files

When enabled, Wine will attempt to load the global registry files from the
/etc directory.

  Load home registry files

When enabled, Wine will attempt to load the user's registry files from the
user's .wine directory.

  Load windows registry files

When enabled, Wine will attempt to load registry data from an existing
Windows installation on the system. 

  Write to home registry files

When enabled, registry data will be written to the user's registry files.
If this option is disabled, Wine will not save the registry, and any
registry changes made by the application will be lost upon its exit.

  Save only updated keys

This allows incremental changes to the user's registry files.  When 
enabled, only the subkeys that have actually changed will be refreshed.
Considering that the user's registry will override any global registry
files as well as Windows registry files, it usually makes sense to only
save user-modified subkeys.  In this way, changes to the global or
Windows registries will not be overridden by the user registry.

[CScrRegistry-LoadGlobalReg-Tooltip]
Enables loading of the global registry files
(from the /etc directory)

[CScrRegistry-LoadHomeReg-Tooltip]
Enables loading of the user's registry files
(from the ~/.wine directory)

[CScrRegistry-LoadWindowsReg-Tooltip]
Enables loading of the registry data from an
existing Windows installation on the system

[CScrRegistry-WriteToHomeReg-Tooltip]
Enables saving of the user's registry data
(in the ~/.wine directory)

[CScrRegistry-SaveOnlyUpdatedKeys-Tooltip]
Enables saving only the subkeys that changed,
rather than the entire registry

