| blob | 43263dc2d7bea3e132340fc9ddb2b8cd5b83901f |
1 .\" -*- nroff -*-
2 .TH WINE.CONF 5 "September 1, 2001" "Version 20010824" "Wine Configuration File"
3 .SH NAME
4 wine.conf \- Wine configuration file
5 .SH DESCRIPTION
6 .B wine
7 expects a configuration file (
8 .I $WINEPREFIX/config
9 (~/.wine/config)
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
16 .br
17 .I [section name]
18 .br
19 and continues until the next section starts. Individual entries
20 consist of lines of the form
21 .br
22 .I """entry""=""value"""
23 .br
24 The entry and value can be any text strings, included in double
25 quotes; it can also contain references to environment variables
26 surrounded by
27 .I ${}.
28 Inside the double quotes, special characters, backslashes and quotes
29 must be escaped with backslashes. Supported section names and entries
30 are listed below.
31 .PP
32 .B [Drive X]
33 .br
34 This section is used to specify the root directory and type of each emulated
35 .B DOS
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.
41 .PP
42 .I format: """Path""=""<rootdirectory>"""
43 .br
44 default: none
45 .br
46 If you mounted your dos partition as
47 .I /dos
48 and installed Microsoft Windows in
49 C:\\WINDOWS (thus it shows up as /dos/WINDOWS), then you should specify
50 .I """Path""=""/dos"""
51 in the
52 .I [Drive C]
53 section in order to configure /dos as the drive root of drive C:.
54 .PP
55 .I format: """Type""=""<type>"""
56 .br
57 default: "hd"
58 .br
59 Used to specify the drive type this drive appears as in Windows
60 or DOS programs; supported types are "floppy", "hd", "cdrom"
61 and "network".
62 .PP
63 .I format: """Label""=""<label>"""
64 .br
65 default: "Drive X"
66 .br
67 Used to specify the drive label; limited to 11 characters.
68 .PP
69 .I format: """Serial""=""<serial>"""
70 .br
71 default: "12345678"
72 .br
73 Used to specify the drive serial number, as an 8-character hexadecimal
74 number.
75 .PP
76 .I format: """Filesystem""=""<fstype>"""
77 .br
78 default: "win95"
79 .br
80 Used to specify the type of the file system Wine should emulate on a given
81 directory structure/underlying file system.
82 .br
83 Supported types are "msdos" (or "fat"), "win95" (or "vfat"), "unix".
84 .br
85 Recommended:
86 .br
87 "win95" for ext2fs, ReiserFS, ..., VFAT and FAT32
88 .br
89 "msdos" for FAT16 file systems (ugly, 8.3 naming)
90 .br
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.
94 .PP
95 .I format: """FailReadOnly""=""<boolean>"""
96 .br
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...).
100 .PP
101 .B [wine]
102 .br
103 .I format: """windows""=""<directory>"""
104 .br
105 default: "C:\\\\WINDOWS"
106 .br
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
109 the backslashes.
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
112 this.
113 .PP
114 .I format: """system""=""<directory>"""
115 .br
116 default: "C:\\\\WINDOWS\\\\System"
117 .br
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.
123 .PP
124 .I format: """temp""=""<directory>"""
125 .br
126 default: "C:\\\\TEMP"
127 .br
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.
131 .PP
132 .I format: """profile""=""<directory>"""
133 .br
134 default: nothing
135 .br
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.
140 .PP
141 .I format: """path""=""<directories separated by semi-colons>"""
142 .br
143 default: "C:\\\\WINDOWS;C:\\\\WINDOWS\\\\SYSTEM"
144 .br
145 Used to specify the path which will be used to find executables and
146 dlls. Make sure to double the backslashes.
147 .PP
148 .B [DllOverrides]
149 .br
150 .I format: """modulename""=""native,so,builtin"""
151 .br
152 .I modulename
153 can be any valid DLL module name, without extension. The specified value
154 is a comma separated list of module-types to try to load in that
155 specific order. Case is not important and only the first letter of
156 each type is enough to identify the type n[ative], s[o],
157 b[uiltin]. Also whitespace is ignored. See also commandline option
158 .I --dll
159 for details about the allowable types.
160 .br
161 The wildcard entry
162 .I """*"""
163 specifies the load order to use for modules not explicitly
164 mentioned. If the wildcard entry is not found, then the order
165 "native,builtin,so" is used.
166 .br
167 Examples:
168 .br
169 .I """kernel32""=""builtin"""
170 .br
171 .I """kernel""=""builtin"""
172 .br
173 .I """comdlg32""=""native,builtin"""
174 .br
175 .I """*""=""builtin,native"""
176 .br
177 Changing the load order of kernel/kernel32 and gdi/gdi32 to
178 anything other than builtin will cause wine to fail because wine cannot
179 use native versions for these libraries.
180 .br
181 Always make sure that you have some kind of strategy in mind when you start
182 fiddling with the current defaults and needless to say that you must know
183 what you are doing.
184 --debugmsg +loaddll might come in handy for experimenting with that stuff.
185 .PP
186 .B [serialports]
187 .br
188 .I format: """com[12345678]""=""<devicename>"""
189 .br
190 default: none
191 .br
192 Used to specify the devices which are used as COM1 - COM8.
193 .PP
194 .B [parallelports]
195 .br
196 .I format: """lpt[12345678]""=""<devicename>"""
197 .br
198 default: none
199 .br
200 Used to specify the devices which are used as LPT1 - LPT8.
201 .PP
202 .B [spy]
203 .br
204 .I format: """exclude""=""<message names separated by semicolons>"""
205 .br
206 default: none
207 .br
208 Used to specify which messages will be excluded from the logfile.
209 .PP
210 .I format: """include""=""<message names separated by semicolons>"""
211 .br
212 default: none
213 .br Used to specify which messages will be included in the logfile.
214 .PP
215 .B [Tweak.Layout]
216 .br
217 .I format: """WineLook""=""<Win31|Win95|Win98>"""
218 .br
219 default: "Win31"
220 .br
221 Use Win95-like window displays or Win3.1-like window displays.
222 .PP
223 .B [Registry]
224 .br
225 .I format: """LoadGlobalRegistryFiles""=""<boolean>"""
226 .br
227 Global registries (stored in /etc)
228 .PP
229 .I format: """LoadHomeRegistryFiles""=""<boolean>"""
230 .br
231 Home registries (stored in ~user/.wine/)
232 .PP
233 .I format: """WritetoHomeRegistryFiles""=""<boolean>"""
234 .br
235 TRY to write all changes to the home registry files
236 .PP
237 .I format: """LoadWindowsRegistryFiles""=""<boolean>"""
238 .br
239 Load Windows registry from the current Windows directory.
240 .PP
241 booleans: Y/y/T/t/1 are true, N/n/F/f/0 are false.
242 .br
243 Defaults are read all, write to home files.
244 .PP
245 .B [AppDefaults\\\\\\\\<appname>\\\\\\\\...]
246 .PP
247 This section allows specifying application-specific values for
248 the other sections described above.
249 .I <appname>
250 is the name of the application exe file, without path. The "..."
251 should be replaced by the name of one of the above configuration
252 sections.
253 .br
254 Example:
255 .br
256 .I [AppDefaults\\\\\\\\sol.exe\\\\\\\\DllOverrides]
257 .br
258 .I """shell32""" = """native"""
259 .br
260 means that Solitaire will use "native" load order for the shell32
261 dll. All other applications will continue to use what was specified in
262 the general
263 .I DllOverrides
264 section.
265 .br
266 The only sections that support application-specific information at the
267 moment are
268 .I DllOverrides
269 and
270 .I x11drv.
271 .br
272 Make sure to use double backslashes in the section name.
273 .PP
274 .SH SAMPLE CONFIGURATION FILE
275 A sample configuration file is distributed as
276 .B documentation/samples/config
277 in the Wine source distribution.
278 .SH FILES
279 .TP
280 .I ~/.wine/config
281 User-specific configuration file
282 .SH ENVIRONMENT VARIABLES
283 .TP
284 .I WINEPREFIX
285 Specifies the directory that contains the per-user
286 .I config
287 file, the registry files, and the wineserver socket. The default is
288 .I $HOME/.wine.
289 .SH "SEE ALSO"
290 .BR wine (1)