4.1.2.1. The [Drive X] Section

These sections are supposed to make certain Unix directory locations accessible to Wine as a DOS/Windows drive (drive 'X:') and thus accessible to Windows programs under the drive name you specified. Every DOS/Windows program sort of expects at least a C: drive (and sometimes also an A: floppy drive), so your config file should at least contain the corresponding sections, [Drive C] and [Drive A]. You need to decide on whether you want to use an existing Windows partition as the C drive or whether you want to create your own Wine drive C directory tree somewhere (take care about permissions !). Each drive section may specify up to 6 different settings as explained below.

[Drive X]

The above line begins the section for a drive whose letter is X (DOS notation: drive 'X:'). You could e.g. create an equivalent to a drive 'C:' under DOS/Windows by using a [Drive C] section name.

"Path" = "/dir/to/path"

This specifies the directory where the drive will begin. When Wine is browsing in drive X, it will be able to see the files that are in the directory /dir/to/path and below. (note that symlinks to directories won't get included ! see "ShowDirSymlinks" config setting) You can also make use of environment variables like $HOME here, an example for using a mywinedrive directory in your home dir would be "Path" = "${HOME}/mywinedrive" Don't forget to leave off the trailing slash!

"Type" = "hd|cdrom|network|floppy"

Sets up the type of drive Wine will see it as. Type must equal one of the four floppy, hd, cdrom, or network. They are self-explanatory. (The |'s mean "Type = '<one of the options>'".) Usually, you choose "hd" for a drive ("hd" is default anyway).

"Label" = "blah"

Defines the drive label. Generally only needed for programs that look for a special CD-ROM. The label may be up to 11 characters. Note that the preferred way of managing labels and serial numbers of CD-ROMs and floppies is to give Wine raw device access for reading these on a per-CD case (see "Device" below) instead of hardcoding one specific "Label".

"Serial" = "deadbeef"

Tells Wine the serial number of the drive. A few programs with intense protection for pirating might need this, but otherwise it's not needed. Up to 8 characters and hexadecimal. Using a "Device" entry instead of hardcoding the "Serial" probably is a smarter choice.

"Filesystem" = "win95|unix|msdos"

Sets up the way Wine looks at files on the drive.

"Device" = "/dev/xx"

Needed for raw device access and label and serial number reading. Use this ONLY for floppy and cdrom devices. Using it on Extended2 or other Unix file systems can have dire results (when a windows app tries to do a lowlevel write, they do it in a FAT way -- FAT format is completely different from any Unix file system). Also, make sure that you have proper permissions to this device file.

Here are a few sample entries:

Here is a setup for Drive C, a generic hard drive: [Drive C] "Path" = "/dosc" "Type" = "hd" "Label" = "Hard Drive" "Filesystem" = "win95" This is a setup for Drive E, a generic CD-ROM drive: [Drive E] "Path" = "/mnt/cdrom" "Type" = "cdrom" "Label" = "Total Annihilation" "Filesystem" = "win95" "Device" = "/dev/cdrom" And here is a setup for Drive A, a generic floppy drive: [Drive A] "Type" = "floppy" "Path" = "/mnt/floppy" "Label" = "Floppy Drive" "Serial" = "87654321" "Filesystem" = "win95" "Device" = "/dev/fd0"

4.1.2.2. The [wine] Section

The [wine] section of the configuration file contains all kinds of general settings for Wine.

"Windows" = "c:\\windows"

This tells Wine and Windows programs where the Windows directory is. It is recommended to have this directory somewhere on your configured C drive, and it's also recommended to just call the directory "windows" (this is the default setup on Windows, and some stupid applications might rely on this). So in case you chose a "Windows" setting of "c:\\windows" and you chose to set up a drive C e.g. at /usr/local/wine_c, the corresponding directory would be /usr/local/wine_c/windows. Make one if you don't already have one. NO TRAILING SLASH (NOT C:\\windows\)! Write access strongly recommended!

"System" = "c:\\windows\\system"

This sets up where the windows system files are. The Windows system directory should reside below the directory used for the Windows setting. Thus when using the example above, the system directory would be /usr/local/wine_c/windows/system. Again, no trailing slash, and write access!

"Temp" = "c:\\temp"

This should be the directory you want your temp files stored in, /usr/local/wine_c/temp in our example. Again, no trailing slash, and WRITE ACCESS!!

"Path" = "c:\\windows;c:\\windows\\system;c:\\blanco"

Behaves like the PATH setting on UNIX boxes. When wine is run like wine sol.exe, if sol.exe resides in a directory specified in the Path setting, wine will run it (Of course, if sol.exe resides in the current directory, wine will run that one). Make sure it always has your windows directory and system directory (For this setup, it must have "c:\\windows;c:\\windows\\system").

"GraphicsDriver" = "x11drv|ttydrv"

Sets the graphics driver to use for Wine output. x11drv is for X11 output, ttydrv is for text console output. WARNING: if you use ttydrv here, then you won't be able to run any Windows GUI programs. Thus this option is mainly interesting for e.g. embedded use of Wine in web server scripts. Note that ttydrv is still very lacking, so if it doesn't work, resort to using "xvfb", a virtual X11 server.

"Printer" = "off|on"

Tells wine whether to allow printing via printer drivers to work. This option isn't needed for our builtin psdrv printer driver at all. Using these things are pretty alpha, so you might want to watch out. Some people might find it useful, however. If you're not planning to work on printing via windows printer drivers, don't even add this to your wine config file (It probably isn't already in it). Check out the [spooler] and [parallelports] sections too.

"ShellLinker" = "wineshelllink"

This setting specifies the shell linker script to use for setting up Windows icons in e.g. KDE or Gnome that are given by programs making use of appropriate shell32.dll functionality to create icons on the desktop/start menu during installation.

"ShowDirSymlinks" = "1"

Wine doesn't pass directory symlinks to Windows programs by default, as doing so may crash some programs that do recursive lookups of whole subdirectory trees whenever a directory symlink points back to itself or one of its parent directories. That's why we disallowed the use of directory symlinks and added this setting to reenable ("1") this functionality.

"SymbolTableFile" = "wine.sym"

Sets up the symbol table file for the wine debugger. You probably don't need to fiddle with this. May be useful if your wine is stripped.

4.1.2.3. Introduction To DLL Sections

There are a few things you will need to know before configuring the DLL sections in your wine configuration file.

4.1.2.4. The [DllDefaults] Section

These settings provide wine's default handling of DLL loading.

"DefaultLoadOrder" =" native, so, builtin"

This setting is a comma-delimited list of the order in which to attempt loading DLLs. If the first option fails, it will try the second, and so on. The order specified above is probably the best in most conditions.

4.1.2.5. The [DllPairs] Section

At one time, there was a section called [DllPairs] in the default configuration file, but this has been obsoleted because the pairing information has now been embedded into Wine itself. (The purpose of this section was merely to be able to issue warnings if the user attempted to pair codependent 16-bit/32-bit DLLs of different types.) If you still have this in your ~/.wine/.config or wine.conf, you may safely delete it.

4.1.2.6. The [DllOverrides] Section

The format for this section is the same for each line:

<DLL>{,<DLL>,<DLL>...} = <FORM>{,<FORM>,<FORM>...}

For example, to load builtin KERNEL pair (case doesn't matter here):

"kernel,kernel32" = "builtin"

To load the native COMMDLG pair, but if that doesn't work try builtin:

"commdlg,comdlg32" = "native,builtin"

To load the native COMCTL32:

"comctl32" = "native"

Here is a good generic setup (As it is defined in config that was included with your wine package):

[DllOverrides] "rpcrt4" = "builtin, native" "oleaut32" = "builtin, native" "ole32" = "builtin, native" "commdlg" = "builtin, native" "comdlg32" = "builtin, native" "ver" = "builtin, native" "version" = "builtin, native" "shell" = "builtin, native" "shell32" = "builtin, native" "shfolder" = "builtin, native" "shlwapi" = "builtin, native" "shdocvw" = "builtin, native" "lzexpand" = "builtin, native" "lz32" = "builtin, native" "comctl32" = "builtin, native" "commctrl" = "builtin, native" "advapi32" = "builtin, native" "crtdll" = "builtin, native" "mpr" = "builtin, native" "winspool.drv" = "builtin, native" "ddraw" = "builtin, native" "dinput" = "builtin, native" "dsound" = "builtin, native" "opengl32" = "builtin, native" "msvcrt" = "native, builtin" "msvideo" = "builtin, native" "msvfw32" = "builtin, native" "mcicda.drv" = "builtin, native" "mciseq.drv" = "builtin, native" "mciwave.drv" = "builtin, native" "mciavi.drv" = "native, builtin" "mcianim.drv" = "native, builtin" "msacm.drv" = "builtin, native" "msacm" = "builtin, native" "msacm32" = "builtin, native" "midimap.drv" = "builtin, native" ; you can specify applications too "notepad.exe" = "native, builtin" ; default for all other dlls "*" = "native, builtin"

4.1.2.7. The [fonts] Section

This section sets up wine's font handling.

"Resolution" = "96"

Since the way X handles fonts is different from the way Windows does, wine uses a special mechanism to deal with them. It must scale them using the number defined in the "Resolution" setting. 60-120 are reasonable values, 96 is a nice in the middle one. If you have the real windows fonts available (<dirs to wine>/documentation/ttfserver and fonts), this parameter will not be as important. Of course, it's always good to get your X fonts working acceptably in wine.

"Default" = "-adobe-times-"

The default font wine uses. Fool around with it if you'd like.

OPTIONAL:

The Alias setting allows you to map an X font to a font used in wine. This is good for apps that need a special font you don't have, but a good replacement exists. The syntax is like so:

"AliasX" = "[Fake windows name],[Real X name]"<,optional "masking" section>

Pretty straightforward. Replace "AliasX" with "Alias0", then "Alias1" and so on. The fake windows name is the name that the font will be under a windows app in wine. The real X name is the font name as seen by X (Run "xfontsel"). The optional "masking" section allows you to utilize the fake windows name you define. If it is not used, then wine will just try to extract the fake windows name itself and not use the value you enter.

Here is an example of an alias without masking. The font will show up in windows apps as "Google".

"Alias0" = "Foo,--google-"

Here is an example with masking enabled. The font will show up as "Foo" in windows apps.

"Alias1" = "Foo,--google-,subst"

For more info check out the Fonts chapter.

4.1.2.8. The [serialports], [parallelports], [spooler], and [ports] Sections

Even though it sounds like a lot of sections, these are all closely related. They are all for communications and parallel ports.

The [serialports] section tells wine what serial ports it is allowed to use.

"ComX" = "/dev/ttySY"

Replace X with the number of the COM port in Windows (1-8) and Y with the number of it in X (Usually the number of the port in Windows minus 1). ComX can actually equal any device (/dev/modem is acceptable). It is not always necessary to define any COM ports (An optional setting). Here is an example:

"Com1" = "/dev/ttyS0"

Use as many of these as you like in the section to define all of the COM ports you need.

The [parallelports] section sets up any parallel ports that will be allowed access under wine.

"LptX" = "/dev/lpY"

Sounds familiar? Syntax is just like the COM port setting. Replace X with a value from 1-4 as it is in Windows and Y with a value from 0-3 (Y is usually the value in windows minus 1, just like for COM ports). You don't always need to define a parallel port (AKA, it's optional). As with the other section, LptX can equal any device (Maybe /dev/printer). Here is an example:

"Lpt1" = "/dev/lp0"

The [spooler] section will inform wine where to spool print jobs. Use this if you want to try printing. Wine docs claim that spooling is "rather primitive" at this time, so it won't work perfectly. IT IS OPTIONAL. The only setting you use in this section works to map a port (LPT1, for example) to a file or a command. Here is an example, mapping LPT1 to the file out.ps:

"LPT1:" = "out.ps"

The following command maps printing jobs to LPT1 to the command lpr. Notice the |:

"LPT1:" = "|lpr"

The [ports] section is usually useful only for people who need direct port access for programs requiring dongles or scanners. IF YOU DON'T NEED IT, DON'T USE IT!

"read" = "0x779,0x379,0x280-0x2a0"

Gives direct read access to those IO's.

"write" = "0x779,0x379,0x280-0x2a0"

Gives direct write access to those IO's. It's probably a good idea to keep the values of the read and write settings the same. This stuff will only work when you're root.

4.1.2.9. The [Debug], [Registry], [tweak.layout], and [programs] Sections

[Debug] is used to include or exclude debug messages, and to output them to a file. The latter is rarely used. THESE ARE ALL OPTIONAL AND YOU PROBABLY DON'T NEED TO ADD OR REMOVE ANYTHING IN THIS SECTION TO YOUR CONFIG. (In extreme cases you may want to use these options to manage the amount of information generated by the --debugmsg +relay option.)

"File" = "/blanco"

Sets the logfile for wine. Set to CON to log to standard out. THIS IS RARELY USED.

"SpyExclude" = "WM_SIZE;WM_TIMER;"

Excludes debug messages about WM_SIZE and WM_TIMER in the logfile.

"SpyInclude" = "WM_SIZE;WM_TIMER;"

Includes debug messages about WM_SIZE and WM_TIMER in the logfile.

"RelayInclude" = "user32.CreateWindowA;comctl32.*"

Include only the listed functions in a --debugmsg +relay trace. This entry is ignored if there is a RelayExclude entry.

"RelayExclude" = "RtlEnterCriticalSection;RtlLeaveCriticalSection"

Exclude the listed functions in a --debugmsg +relay trace. This entry overrides any settings in a RelayInclude entry. If neither entry is present then the trace includes everything.

In both entries the functions may be specified either as a function name or as a module and function. In this latter case specify an asterisk for the function name to include/exclude all functions in the module.

[Registry] can be used to tell wine where your old windows registry files exist. This section is completely optional and useless to people using wine without an existing windows installation.

"UserFileName" = "/dirs/to/user.reg"

The location of your old user.reg file.

[tweak.layout] is devoted to wine's look. There is only one setting for it.

"WineLook" = "win31|win95|win98"

Will change the look of wine from Windows 3.1 to Windows 95. The win98 setting behaves just like win95 most of the time.

[programs] can be used to say what programs run under special conditions.

"Default" = "/program/to/execute.exe"

Sets the program to be run if wine is started without specifying a program.

"Startup" = "/program/to/execute.exe"

Sets the program to automatically be run at startup every time.

4.1.2.10. The [WinMM] Section

[WinMM] is used to define which multimedia drivers have to be loaded. Since those drivers may depend on the multimedia interfaces available on your system (OSS, ALSA... to name a few), it's needed to be able to configure which driver has to be loaded.

The content of the section looks like:

[WinMM] "Drivers" = "wineoss.drv" "WaveMapper" = "msacm.drv" "MidiMapper" = "midimap.drv"

All the keys must be defined:

• The "Drivers" key is a ';' separated list of modules name, each of them containing a low level driver. All those drivers will be loaded when MMSYSTEM/WINMM is started and will provide their inner features.

• The "WaveMapper" represents the name of the module containing the Wave Mapper driver. Only one wave mapper can be defined in the system.

• The "MidiMapper" represents the name of the module containing the MIDI Mapper driver. Only one MIDI mapper can be defined in the system.

4.1.2.11. The [Network] Section

[Network] contains settings related to networking. Currently there is only one value that can be set.

4.1.2.12. The [AppDefaults] Section

The section is used to overwrite certain settings of this file for a special program with different settings. [AppDefaults] is not the real name of the section. The real name consists of the leading word AppDefaults followed by the name of the executable the section is valid for. The end of the section name is the name of the corresponding "standard" section of the configuration file that should have some of its settings overwritten with the application specific settings you define. The three parts of the section name are separated by two backslashes.

Currently wine supports overriding selected settings within the sections [DllOverrides], [x11drv], [version] and [dsound] only.

Here is an example that overrides the normal settings for a program:

;; default settings [x11drv] "Managed" = "Y" "Desktop" = "N" ;; run install in desktop mode [AppDefaults\\install.exe\\x11drv] "Managed" = "N" "Desktop" = "800x600"