2 .TH WINE.CONF 5 "September 2003" "Version 20030911" "Wine Configuration File"
4 wine.conf \- Wine configuration file
7 expects a configuration file (
10 ), which should conform to the following rules.
11 A sample configuration file is available as
12 .I documentation/samples/config
13 in the Wine source distribution.
14 .SH CONFIGURATION FILE FORMAT
15 All entries are grouped in sections; a section begins with the line
19 and continues until the next section starts. Individual entries
20 consist of lines of the form
22 .I """entry""=""value"""
24 The entry and value can be any text strings, included in double
25 quotes; it can also contain references to environment variables
28 Inside the double quotes, special characters, backslashes and quotes
29 must be escaped with backslashes. Supported section names and entries
34 This section is used to specify the root directory and type of each emulated
36 drive, since most Windows applications require a DOS/MS-Windows based
37 disk drive & directory scheme, which is either provided by a real
38 DOS partition mounted somewhere or by some carefully crafted directory layout
39 on a Unix file system ("no-windows fake installation").
40 There is one such section for every drive you want to configure.
42 .I format: """Path""=""<rootdirectory>"""
46 If you mounted your dos partition as
48 and installed Microsoft Windows in
49 C:\\WINDOWS (thus it shows up as /dos/WINDOWS), then you should specify
50 .I """Path""=""/dos"""
53 section in order to configure /dos as the drive root of drive C:.
55 .I format: """Type""=""<type>"""
59 Used to specify the drive type this drive appears as in Windows
60 or DOS programs; supported types are "floppy", "hd", "cdrom"
65 .I format: """windows""=""<directory>"""
67 default: "C:\\\\WINDOWS"
69 Used to specify where Wine is supposed to have its Windows directory
70 (which is an essential part of a Windows environment); make sure to double
72 In case of e.g. C:\\WINDOWS, with drive C: being configured as
73 /home/user/wine_c, the /home/user/wine_c/WINDOWS directory would be used for
76 .I format: """system""=""<directory>"""
78 default: "C:\\\\WINDOWS\\\\System"
80 Used to specify where Wine is supposed to have its Windows system directory
81 (again, essential part of Windows environment); make sure to double the backslashes.
82 Given a setting of C:\\WINDOWS\\System (the standard setting on Windows)
83 and a C: drive again at /home/user/wine_c, the /home/user/wine_c/WINDOWS/System
84 directory would be used for this.
86 .I format: """temp""=""<directory>"""
90 Used to specify a directory where Windows applications can store
91 temporary files. E.g. with a C: drive at /home/user/wine_c, this would be
92 the /home/user/wine_c/TEMP directory.
94 .I format: """profile""=""<directory>"""
98 Used to specify a directory where Windows stores special folders and
99 the user-registry files (user.dat or ntuser.dat). Mapped to
100 environment variable %USERPROFILE%. Set this value when running with
101 a native NT or a native win95 directory with per-user settings.
103 .I format: """path""=""<directories separated by semi-colons>"""
105 default: "C:\\\\WINDOWS;C:\\\\WINDOWS\\\\SYSTEM"
107 Used to specify the path which will be used to find executables and
108 dlls. Make sure to double the backslashes.
110 .I format: """GraphicsDriver""=""<x11drv|ttydrv>"""
114 Tells Wine which graphics driver to use. Normally you'd want to use
115 x11drv (for X11). In case you want to run programs as text console/TTY only
116 without having Wine rely on X11 support, then use ttydrv.
118 .I format: """ShowDirSymlinks""=""<0|1>"""
122 Wine doesn't pass directory symlinks to Windows programs by default.
123 Enabling this may crash some programs that do recursive lookups of a whole
124 subdir tree in case of a symlink pointing back to itself.
126 .I format: """ShowDotFiles""=""<0|1>"""
130 Under Unix, files starting with a dot, are considered hidden,
131 and should not be shown in directory listing (unless explicitly asked for),
132 just like DOS-style hidden files. If you want them treated as regular
133 files, set this value to 1.
137 .I format: """Windows""=""<version string>"""
139 default: none; chosen by semi-intelligent detection mechanism based on DLL environment
141 Used to specify which Windows version to return to programs (forced value,
142 overrides standard detection mechanism !).
143 Valid settings are e.g. "win31", "win95", "win98", "win2k", "winxp".
144 Also valid as an AppDefaults setting (recommended/preferred use).
146 .I format: """DOS""=""<version string>"""
148 default: "<Windows version specific>"
150 Used to specify the DOS version that should be returned to programs.
151 Only takes effect in case Wine acts as "win31" Windows version !
152 Common DOS version settings include 6.22, 6.20, 6.00, 5.00, 4.00, 3.30, 3.10.
153 Also valid as an AppDefaults setting (recommended/preferred use).
157 .I format: """modulename""=""native,builtin"""
160 can be any valid DLL module name. If no extension is specified .dll is
161 assumed. The specified value is a comma separated list of module-types
162 to try to load in that specific order. Case is not important and only
163 the first letter of each type is enough to identify the type n[ative]
164 or b[uiltin]. Also whitespace is ignored. See also the description of
167 environment variable in
169 for details about the allowed types.
173 specifies the load order to use for modules not explicitly
174 mentioned. If the wildcard entry is not found, then the order
175 "native,builtin" is used.
179 .I """kernel32""=""builtin"""
181 .I """comdlg32""=""native,builtin"""
183 .I """*""=""builtin,native"""
185 When the specified module name does not contain a path, it matches
186 only dlls loaded from the Windows system directory. If the application
187 explicitly loads a dll from a different directory, it has to be
188 configured separately. This can be done either by specifying the full
189 path in the module name, or by using a path wildcard of the form
190 .I """*modulename""".
192 For instance, the following will load the native shell32 when loaded
193 from C:\\Program Files, and the builtin when loaded from any other
196 .I """C:\\\\\\\\Program Files\\\\\\\\shell32"" = ""native"""
198 .I """*shell32"" = ""builtin"""
200 Changing the load order of low-level dlls like kernel32, gdi32 or
201 user32 to anything other than builtin will cause wine to fail because
202 wine cannot use native versions for these libraries.
204 Always make sure that you have some kind of strategy in mind when you start
205 fiddling with the current defaults and needless to say that you must know
207 --debugmsg +loaddll might come in handy for experimenting with that stuff.
211 .I format: """SpyExclude""=""<message names separated by semicolons>"""
215 Used to specify which messages will be excluded from the logfile.
217 .I format: """SpyInclude""=""<message names separated by semicolons>"""
220 .br Used to specify which messages will be included in the logfile.
222 .I format: """RelayFromExclude""=""<module names separated by semicolons>"""
226 Used to specify a set of modules whose calls are excluded from a relay debug log.
228 .I format: """RelayFromInclude""=""<module names separated by semicolons>"""
230 default: include all modules
232 Used to specify the set of modules whose calls are included in a relay debug log.
234 .I format: """RelayExclude""=""<functions or dll.functions separated by semicolons>"""
238 Used to specify which functions will be excluded from a relay debug log.
240 .I format: """RelayInclude""=""<functions or dll.functions separated by semicolons>"""
242 default: include all functions
244 Used to specify which functions will be included in a relay debug log.
246 .I format: """SnoopExclude""=""<functions or dll.functions separated by semicolons>"""
250 Used to specify which functions will be excluded from the snoop debug log.
252 .I format: """SnoopInclude""=""<functions or dll.functions separated by semicolons>"""
254 default: include all functions
256 Used to specify which functions will be included in the snoop debug log.
258 For Relay and Snoop <dllname>.* includes or excludes the whole dll. Exclude
259 entries have priority over Include entries.
263 .I format: """LoadGlobalRegistryFiles""=""<boolean>"""
265 Global registries (stored in /etc)
267 .I format: """LoadHomeRegistryFiles""=""<boolean>"""
269 Home registries (stored in ~user/.wine/)
271 .I format: """WritetoHomeRegistryFiles""=""<boolean>"""
273 TRY to write all changes to the home registry files
275 .I format: """LoadWindowsRegistryFiles""=""<boolean>"""
277 Load Windows registry from the current Windows directory.
279 booleans: Y/y/T/t/1 are true, N/n/F/f/0 are false.
281 Defaults are read all, write to home files.
285 .I format: """UseDnsComputerName""=""<boolean>"""
287 If Y, always override the registry setting for ComputerName
288 with the Unix hostname.
290 .B [AppDefaults\\\\\\\\<appname>\\\\\\\\...]
292 This section allows specifying application-specific values for
293 the other sections described above.
295 is the name of the application exe file, without path. The "..."
296 should be replaced by the name of one of the above configuration
301 .I [AppDefaults\\\\\\\\sol.exe\\\\\\\\DllOverrides]
303 .I """shell32""" = """native"""
305 means that Solitaire will use "native" load order for the shell32
306 dll. All other applications will continue to use what was specified in
311 The only sections that support application-specific information at the
313 .I DllOverrides, dsound, Version
317 Make sure to use double backslashes in the section name.
319 .SH SAMPLE CONFIGURATION FILE
320 A sample configuration file is distributed as
321 .B documentation/samples/config
322 in the Wine source distribution.
323 .SH ENVIRONMENT VARIABLES
326 Specifies the directory that contains the per-user
328 file, the registry files, and the DOS device mappings. The default is
332 .I $WINEPREFIX/config
333 User-specific configuration file
335 .I $WINEPREFIX/dosdevices
336 Directory containing the DOS device mappings. Each file in that
337 directory is a symlink to the Unix device file implementing a given
338 device. For instance, if COM1 is mapped to /dev/ttyS0 you'd have a
339 symlink of the form $WINEPREFIX/dosdevices/com1 -> /dev/ttyS0.