Wine-Conf Man Page

From Wine-Wiki

[edit] DESCRIPTION

      wine expects a configuration file ( $WINEPREFIX/config (~/.wine/config)
      ), which should conform to the following rules.  A sample configuration
      file  is  available  as documentation/samples/config in the Wine source
      distribution.

[edit] CONFIGURATION FILE FORMAT

      The config file needs to start with the header line
      WINE REGISTRY Version 2
      to be recognized by Wine.

      All entries (excepting the header) are grouped in sections;  a  section
      begins with the line
      [section name]
      and continues until the next section starts. Individual entries consist
      of lines of the form
      "entry"="value"
      The entry and value can be any text strings, included in double quotes;
      it can also contain references to environment variables surrounded by %
      signs.  Inside the double quotes, special characters,  backslashes  and
      quotes  must  be  escaped with backslashes. Supported section names and
      entries are listed below.

      [wine]
      format: "windows"="<directory>"
      default: "C:\\WINDOWS"
      Used to specify where Wine is supposed to have  its  Windows  directory
      (which  is  an  essential  part of a Windows environment); make sure to
      double the backslashes.  In case of  e.g.  C:\WINDOWS,  with  drive  C:
      being  configured  as  /home/user/wine_c, the /home/user/wine_c/WINDOWS
      directory would be used for this.

      format: "GraphicsDriver"="<x11drv|ttydrv>"
      default: "x11drv"
      Tells Wine which graphics driver to use. Normally  you'd  want  to  use
      x11drv  (for X11). In case you want to run programs as text console/TTY
      only without having Wine rely on X11 support, then use ttydrv.

      format: "ShowDirSymlinks"="<0|1>"
      default: "0"
      Wine doesn't pass directory symlinks to Windows  programs  by  default.
      Enabling  this  may  crash some programs that do recursive lookups of a
      whole subdir tree in case of a symlink pointing back to itself.

      format: "ShowDotFiles"="<0|1>"
      default: "0"
      Under Unix, files starting with  a  dot,  are  considered  hidden,  and
      should not be shown in directory listing (unless explicitly asked for),
      just like DOS-style hidden files. If you want them treated  as  regular
      files, set this value to 1.

      [Version]
      use).

      [DllOverrides]
      format: "modulename"="native,builtin"
      modulename  can be any valid DLL module name. If no extension is speci-
      fied .dll is assumed. The specified value is a comma separated list  of
      module-types  to try to load in that specific order. Case is not impor-
      tant and only the first letter of each type is enough to  identify  the
      type  n[ative]  or  b[uiltin]. Also whitespace is ignored. See also the
      description of the WINEDLLOVERRIDES environment variable in wine(1) for
      details about the allowed types.
      The  wildcard entry "*" specifies the load order to use for modules not
      explicitly mentioned. If the wildcard entry  is  not  found,  then  the
      order "native,builtin" is used.
      Examples:
      "kernel32"="builtin"
      "comdlg32"="native,builtin"
      "*"="builtin,native"
      When the specified module name does not contain a path, it matches only
      dlls loaded from the  Windows  system  directory.  If  the  application
      explicitly loads a dll from a different directory, it has to be config-
      ured separately. This can be done either by specifying the full path in
      the  module name, or by using a path wildcard of the form "*modulename"
      .
      For instance, the following will load the native  shell32  when  loaded
      from  C:\Program  Files,  and  the  builtin  when loaded from any other
      directory:
      "C:\\Program Files\\shell32" = "native"
      "*shell32" = "builtin"
      Changing the load order of  low-level  dlls  like  kernel32,  gdi32  or
      user32  to  anything other than builtin will cause wine to fail because
      wine cannot use native versions for these libraries.
      Always make sure that you have some kind of strategy in mind  when  you
      start  fiddling  with the current defaults and needless to say that you
      must know what you are doing.  WINEDEBUG=loaddll might  come  in  handy
      for experimenting with that stuff.

      [Debug]
      format: "SpyExclude"="<message names separated by semicolons>"
      default: none
      Used to specify which messages will be excluded from the logfile.

      format: "SpyInclude"="<message names separated by semicolons>"
      default: none

      format: "RelayFromExclude"="<module names separated by semicolons>"
      default: none
      Used  to specify a set of modules whose calls are excluded from a relay
      debug log.

      format: "RelayFromInclude"="<module names separated by semicolons>"
      default: include all modules
      format:  "SnoopExclude"="<functions or dll.functions separated by semi-
      colons>"
      default: none
      Used to specify which functions will be excluded from the  snoop  debug
      log.

      format:  "SnoopInclude"="<functions or dll.functions separated by semi-
      colons>"
      default: include all functions
      Used to specify which functions will be included  in  the  snoop  debug
      log.

      For  Relay  and  Snoop  <dllname>.* includes or excludes the whole dll.
      Exclude entries have priority over Include entries.

      [Registry]
      format: "LoadGlobalRegistryFiles"="<boolean>"
      Global registries (stored in /etc)

      format: "LoadHomeRegistryFiles"="<boolean>"
      Home registries (stored in ~user/.wine/)

      format: "WritetoHomeRegistryFiles"="<boolean>"
      TRY to write all changes to the home registry files

      format: "LoadWindowsRegistryFiles"="<boolean>"
      Load Windows registry from the current Windows directory.

      booleans: Y/y/T/t/1 are true, N/n/F/f/0 are false.
      Defaults are read all, write to home files.

      [Network]
      format: "UseDnsComputerName"="<boolean>"
      If Y, always override the registry setting for  ComputerName  with  the
      Unix hostname.

      [AppDefaults\\<appname>\\...]

      This  section  allows  specifying  application-specific  values for the
      other sections described above.  <appname> is the name of the  applica-
      tion  exe file, without path. The "..."  should be replaced by the name
      of one of the above configuration sections.
      Example:
      [AppDefaults\\sol.exe\\DllOverrides]
      "shell32" = "native"
      means that Solitaire will use "native" load order for the shell32  dll.
      All  other  applications will continue to use what was specified in the
      general DllOverrides section.
      The only sections that support application-specific information at  the
      moment are DllOverrides, dsound, Version and x11drv.
      Make sure to use double backslashes in the section name.