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.
156 .I format: """ShowDirSymlinks""=""<0|1>"""
160 Wine doesn't pass directory symlinks to Windows programs by default.
161 Enabling this may crash some programs that do recursive lookups of a whole
162 subdir tree in case of a symlink pointing back to itself.
164 .I format: """ShowDotFiles""=""<0|1>"""
168 Under Unix, files starting with a dot, are considered hidden,
169 and should not be shown in directory listing (unless explicitly asked for),
170 just like DOS-style hidden files. If you want them treated as regular
171 files, set this value to 1.
175 .I format: """Windows""=""<version string>"""
177 default: none; chosen by semi-intelligent detection mechanism based on DLL environment
179 Used to specify which Windows version to return to programs (forced value,
180 overrides standard detection mechanism !).
181 Valid settings are e.g. "win31", "win95", "win98", "win2k", "winxp".
182 Also valid as an AppDefaults setting (recommended/preferred use).
184 .I format: """DOS""=""<version string>"""
186 default: "<Windows version specific>"
188 Used to specify the DOS version that should be returned to programs.
189 Only takes effect in case Wine acts as "win31" Windows version !
190 Common DOS version settings include 6.22, 6.20, 6.00, 5.00, 4.00, 3.30, 3.10.
191 Also valid as an AppDefaults setting (recommended/preferred use).
195 .I format: """modulename""=""native,so,builtin"""
198 can be any valid DLL module name. If no extension is specified .dll is
199 assumed. The specified value is a comma separated list of module-types
200 to try to load in that specific order. Case is not important and only
201 the first letter of each type is enough to identify the type n[ative],
202 s[o], b[uiltin]. Also whitespace is ignored. See also commandline
205 for details about the allowable types.
209 specifies the load order to use for modules not explicitly
210 mentioned. If the wildcard entry is not found, then the order
211 "native,builtin,so" is used.
215 .I """kernel32""=""builtin"""
217 .I """kernel""=""builtin"""
219 .I """comdlg32""=""native,builtin"""
221 .I """*""=""builtin,native"""
223 When the specified module name does not contain a path, it matches
224 only dlls loaded from the Windows system directory. If the application
225 explicitly loads a dll from a different directory, it has to be
226 configured separately. This can be done either by specifying the full
227 path in the module name, or by using a path wildcard of the form
228 .I """*modulename""".
230 For instance, the following will load the native shell32 when loaded
231 from C:\\Program Files, and the builtin when loaded from any other
234 .I """C:\\\\\\\\Program Files\\\\\\\\shell32"" = ""native"""
236 .I """*shell32"" = ""builtin"""
238 Changing the load order of low-level dlls like kernel32, gdi32 or
239 user32 to anything other than builtin will cause wine to fail because
240 wine cannot use native versions for these libraries.
242 Always make sure that you have some kind of strategy in mind when you start
243 fiddling with the current defaults and needless to say that you must know
245 --debugmsg +loaddll might come in handy for experimenting with that stuff.
249 .I format: """com[12345678]""=""<devicename>"""
253 Used to specify the devices which are used as COM1 - COM8.
257 .I format: """lpt[12345678]""=""<devicename>"""
261 Used to specify the devices which are used as LPT1 - LPT8.
265 .I format: """exclude""=""<message names separated by semicolons>"""
269 Used to specify which messages will be excluded from the logfile.
271 .I format: """include""=""<message names separated by semicolons>"""
274 .br Used to specify which messages will be included in the logfile.
278 .I format: """WineLook""=""<Win31|Win95|Win98>"""
282 Use Win95-like window displays or Win3.1-like window displays.
286 .I format: """LoadGlobalRegistryFiles""=""<boolean>"""
288 Global registries (stored in /etc)
290 .I format: """LoadHomeRegistryFiles""=""<boolean>"""
292 Home registries (stored in ~user/.wine/)
294 .I format: """WritetoHomeRegistryFiles""=""<boolean>"""
296 TRY to write all changes to the home registry files
298 .I format: """LoadWindowsRegistryFiles""=""<boolean>"""
300 Load Windows registry from the current Windows directory.
302 booleans: Y/y/T/t/1 are true, N/n/F/f/0 are false.
304 Defaults are read all, write to home files.
306 .B [AppDefaults\\\\\\\\<appname>\\\\\\\\...]
308 This section allows specifying application-specific values for
309 the other sections described above.
311 is the name of the application exe file, without path. The "..."
312 should be replaced by the name of one of the above configuration
317 .I [AppDefaults\\\\\\\\sol.exe\\\\\\\\DllOverrides]
319 .I """shell32""" = """native"""
321 means that Solitaire will use "native" load order for the shell32
322 dll. All other applications will continue to use what was specified in
327 The only sections that support application-specific information at the
333 Make sure to use double backslashes in the section name.
335 .SH SAMPLE CONFIGURATION FILE
336 A sample configuration file is distributed as
337 .B documentation/samples/config
338 in the Wine source distribution.
342 User-specific configuration file
343 .SH ENVIRONMENT VARIABLES
346 Specifies the directory that contains the per-user
348 file, the registry files, and the wineserver socket. The default is
projects / wine / blob