2 .TH WINE.CONF 5 "September 1, 2001" "Version 20010824" "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"
63 .I format: """Label""=""<label>"""
67 Used to specify the drive label; limited to 11 characters.
69 .I format: """Serial""=""<serial>"""
73 Used to specify the drive serial number, as an 8-character hexadecimal
76 .I format: """Filesystem""=""<fstype>"""
80 Used to specify the type of the file system Wine should emulate on a given
81 directory structure/underlying file system.
83 Supported types are "msdos" (or "fat"), "win95" (or "vfat"), "unix".
87 "win95" for ext2fs, ReiserFS, ..., VFAT and FAT32
89 "msdos" for FAT16 file systems (ugly, 8.3 naming)
91 You definitely do not want to use "unix" unless you intend to port
92 programs using Winelib. Always try to avoid using a FAT16 FS. Use the
93 VFAT/FAT32 OS file system driver instead.
95 .I format: """FailReadOnly""=""<boolean>"""
97 Read-only files may not be opened in write mode (the default is to
98 allow opening read-only files for writing, because most Windows
99 programs always request read-write access, even on CD-ROM drives...).
103 .I format: """windows""=""<directory>"""
105 default: "C:\\\\WINDOWS"
107 Used to specify where Wine is supposed to have its Windows directory
108 (which is an essential part of a Windows environment); make sure to double
110 In case of e.g. C:\\WINDOWS, with drive C: being configured as
111 /home/user/wine_c, the /home/user/wine_c/WINDOWS directory would be used for
114 .I format: """system""=""<directory>"""
116 default: "C:\\\\WINDOWS\\\\System"
118 Used to specify where Wine is supposed to have its Windows system directory
119 (again, essential part of Windows environment); make sure to double the backslashes.
120 Given a setting of C:\\WINDOWS\\System (the standard setting on Windows)
121 and a C: drive again at /home/user/wine_c, the /home/user/wine_c/WINDOWS/System
122 directory would be used for this.
124 .I format: """temp""=""<directory>"""
126 default: "C:\\\\TEMP"
128 Used to specify a directory where Windows applications can store
129 temporary files. E.g. with a C: drive at /home/user/wine_c, this would be
130 the /home/user/wine_c/TEMP directory.
132 .I format: """profile""=""<directory>"""
136 Used to specify a directory where Windows stores special folders and
137 the user-registry files (user.dat or ntuser.dat). Mapped to
138 environment variable %USERPROFILE%. Set this value when running with
139 a native NT or a native win95 directory with per-user settings.
141 .I format: """path""=""<directories separated by semi-colons>"""
143 default: "C:\\\\WINDOWS;C:\\\\WINDOWS\\\\SYSTEM"
145 Used to specify the path which will be used to find executables and
146 dlls. Make sure to double the backslashes.
148 .I format: """GraphicsDriver""=""<x11drv|ttydrv>"""
152 Tells Wine which graphics driver to use. Normally you'd want to use
153 x11drv (for X11). In case you want to run programs as text console/TTY only
154 without having Wine rely on X11 support, then use ttydrv.
158 .I format: """Windows""=""<version string>"""
160 default: none; chosen by semi-intelligent detection mechanism based on DLL environment
162 Used to specify which Windows version to return to programs (forced value,
163 overrides standard detection mechanism !).
164 Valid settings are e.g. "win31", "win95", "win98", "win2k", "winxp".
165 Also valid as an AppDefaults setting (recommended/preferred use).
167 .I format: """DOS""=""<version string>"""
169 default: "<Windows version specific>"
171 Used to specify the DOS version that should be returned to programs.
172 Only takes effect in case Wine acts as "win31" Windows version !
173 Common DOS version settings include 6.22, 6.20, 6.00, 5.00, 4.00, 3.30, 3.10.
174 Also valid as an AppDefaults setting (recommended/preferred use).
178 .I format: """modulename""=""native,so,builtin"""
181 can be any valid DLL module name. If no extension is specified .dll is
182 assumed. The specified value is a comma separated list of module-types
183 to try to load in that specific order. Case is not important and only
184 the first letter of each type is enough to identify the type n[ative],
185 s[o], b[uiltin]. Also whitespace is ignored. See also commandline
188 for details about the allowable types.
192 specifies the load order to use for modules not explicitly
193 mentioned. If the wildcard entry is not found, then the order
194 "native,builtin,so" is used.
198 .I """kernel32""=""builtin"""
200 .I """kernel""=""builtin"""
202 .I """comdlg32""=""native,builtin"""
204 .I """*""=""builtin,native"""
206 When the specified module name does not contain a path, it matches
207 only dlls loaded from the Windows system directory. If the application
208 explicitly loads a dll from a different directory, it has to be
209 configured separately. This can be done either by specifying the full
210 path in the module name, or by using a path wildcard of the form
211 .I """*modulename""".
213 For instance, the following will load the native shell32 when loaded
214 from C:\\Program Files, and the builtin when loaded from any other
217 .I """C:\\\\\\\\Program Files\\\\\\\\shell32"" = ""native"""
219 .I """*shell32"" = ""builtin"""
221 Changing the load order of low-level dlls like kernel32, gdi32 or
222 user32 to anything other than builtin will cause wine to fail because
223 wine cannot use native versions for these libraries.
225 Always make sure that you have some kind of strategy in mind when you start
226 fiddling with the current defaults and needless to say that you must know
228 --debugmsg +loaddll might come in handy for experimenting with that stuff.
232 .I format: """com[12345678]""=""<devicename>"""
236 Used to specify the devices which are used as COM1 - COM8.
240 .I format: """lpt[12345678]""=""<devicename>"""
244 Used to specify the devices which are used as LPT1 - LPT8.
248 .I format: """exclude""=""<message names separated by semicolons>"""
252 Used to specify which messages will be excluded from the logfile.
254 .I format: """include""=""<message names separated by semicolons>"""
257 .br Used to specify which messages will be included in the logfile.
261 .I format: """WineLook""=""<Win31|Win95|Win98>"""
265 Use Win95-like window displays or Win3.1-like window displays.
269 .I format: """LoadGlobalRegistryFiles""=""<boolean>"""
271 Global registries (stored in /etc)
273 .I format: """LoadHomeRegistryFiles""=""<boolean>"""
275 Home registries (stored in ~user/.wine/)
277 .I format: """WritetoHomeRegistryFiles""=""<boolean>"""
279 TRY to write all changes to the home registry files
281 .I format: """LoadWindowsRegistryFiles""=""<boolean>"""
283 Load Windows registry from the current Windows directory.
285 booleans: Y/y/T/t/1 are true, N/n/F/f/0 are false.
287 Defaults are read all, write to home files.
289 .B [AppDefaults\\\\\\\\<appname>\\\\\\\\...]
291 This section allows specifying application-specific values for
292 the other sections described above.
294 is the name of the application exe file, without path. The "..."
295 should be replaced by the name of one of the above configuration
300 .I [AppDefaults\\\\\\\\sol.exe\\\\\\\\DllOverrides]
302 .I """shell32""" = """native"""
304 means that Solitaire will use "native" load order for the shell32
305 dll. All other applications will continue to use what was specified in
310 The only sections that support application-specific information at the
316 Make sure to use double backslashes in the section name.
318 .SH SAMPLE CONFIGURATION FILE
319 A sample configuration file is distributed as
320 .B documentation/samples/config
321 in the Wine source distribution.
325 User-specific configuration file
326 .SH ENVIRONMENT VARIABLES
329 Specifies the directory that contains the per-user
331 file, the registry files, and the wineserver socket. The default is