1 <chapter id=
"configuring">
2 <title>Configuring Wine
</title>
3 <para>Setting up config files, etc.
</para>
6 <title>General Configuration
</title>
8 Copyright
1999 &name-adam-sacarny;
<email>&email-adam-sacarny;
</email>
11 (Extracted from
<filename>wine/documentation/config
</filename>)
15 <title>The Wine Config File
</title>
17 The Wine config file stores various settings for Wine. These include:
21 Drives and Information about them
36 The Wine look and feel
46 Wine's Multimedia drivers and DLL configuration
54 <title>How Do I Make One?
</title>
56 This section will guide you through the process of making a
57 config file. Take a look at the file
<filename><dirs to
58 wine
>/documentation/samples/config
</filename>. It is organized by section.
61 <informaltable frame=
"all">
65 <entry>Section Name
</entry>
66 <entry>Needed?
</entry>
67 <entry>What it Does
</entry>
72 <entry>[Drive X]
</entry>
74 <entry>Sets up drives recognized by wine
</entry>
79 <entry>Settings for wine directories
</entry>
82 <entry>[DllDefaults]
</entry>
84 <entry>Defaults for loading DLL's
</entry>
87 <entry>[DllPairs]
</entry>
89 <entry>Sanity checkers for DLL's
</entry>
92 <entry>[DllOverrides]
</entry>
94 <entry>Overides defaults for DLL loading
</entry>
97 <entry>[x11drv]
</entry>
99 <entry>Graphic driver settings
</entry>
102 <entry>[fonts]
</entry>
104 <entry>Font appearance and recognition
</entry>
107 <entry>[serialports]
</entry>
109 <entry>COM ports seen by wine
</entry>
112 <entry>[parallelports]
</entry>
114 <entry>LPT ports seen by wine
</entry>
117 <entry>[ppdev]
</entry>
119 <entry>Parallelport emulation
</entry>
122 <entry>[spooler]
</entry>
124 <entry>Print spooling
</entry>
127 <entry>[ports]
</entry>
129 <entry>Direct port access
</entry>
134 <entry>What to do with certain debug messages
</entry>
137 <entry>[Registry]
</entry>
139 <entry>Specifies locations of windows registry files
</entry>
142 <entry>[tweak.layout]
</entry>
144 <entry>Appearance of wine
</entry>
147 <entry>[programs]
</entry>
149 <entry>Programs to be run automatically
</entry>
152 <entry>[Console]
</entry>
154 <entry>Console settings
</entry>
157 <entry>[Clipboard]
</entry>
159 <entry>Interaction for wine and X11 clipboard
</entry>
162 <entry>[afmdirs]
</entry>
164 <entry>Postscript driver settings
</entry>
167 <entry>[WinMM]
</entry>
169 <entry>Multimedia settings
</entry>
172 <entry>[AppDefaults]
</entry>
174 <entry>Overwrite the settings of previous sections for special programs
</entry>
181 <title>The [Drive X] Section
</title>
183 It should be pretty self explanatory, but here is an
184 in-depth tutorial about them. There are up to
6 lines for
188 <programlisting>[Drive X]
</programlisting>
189 The above line begins the section for a drive whose letter is X.
192 <programlisting>Path=/dir/to/path
</programlisting> This
193 path is where the drive will begin. When Wine is browsing
194 in drive X, it will see the files that are in the
195 directory
<filename>/dir/to/path
</filename>. Don't forget
196 to leave off the trailing slash!
199 <programlisting>"Type" =
"floppy|hd|cdrom|network"</programlisting>
200 Sets up the type of drive Wine will see it as. Type must
201 equal one of the four
<literal>floppy
</literal>,
202 <literal>hd
</literal>,
<literal>cdrom
</literal>, or
203 <literal>network
</literal>. They are self-explanatory.
204 (The |'s mean
"Type = '<one of the options>'".)
207 <programlisting>"Label" =
"blah"</programlisting> Defines the
208 drive label. Generally only needed for programs that look
209 for a special CD-ROM. Info on finding the lable is in
210 <literal><dirs to wine
>/documentation/cdrom-labels
</literal>.
211 The label may be up to
11 characters.
214 <programlisting>"Serial" =
"deadbeef"</programlisting>
215 Tells Wine the serial number of the drive. A few programs with
216 intense protection for pirating might need this, but otherwise
217 don't use it. Up to
8 characters and hexadecimal.
220 <programlisting>"Filesystem" =
"msdos|win95|unix"</programlisting>
221 Sets up the way Wine looks at files on the drive.
226 <term><literal>msdos
</literal></term>
229 Case insensitive filesystem. Alike to DOS and
230 Windows
3.x.
<literal>8.3</literal> is the maximum
231 length of files (eightdot
.123) - longer ones will be
232 truncated. (NOTE: this is a very bad choice if you
233 plan on running apps that use long filenames. win95
234 should work fine with apps that were designed to run
235 under the msdos system. In other words, you might
236 not want to use this.)
241 <term><literal>win95
</literal></term>
244 Case insensitive. Alike to Windows
9x/NT
4. This is
245 the long filename filesystem you are probably used
246 to working with. The filesystem of choice for most
247 applications to be run under wine. PROBABLY THE ONE
253 <term><literal>unix
</literal></term>
256 Case sensitive. This filesystem has almost no use
257 (Windows apps expect case insensitive filenames).
258 Try it if you dare, but win95 is a much better
265 <programlisting>"Device" =
"/dev/xx"</programlisting>
267 Use this ONLY for floppy and cdrom devices. Using it on
268 Extended2 partitions can have dire results (when a windows
269 app tries to do a lowlevel write, they do it in a FAT way
270 -- FAT does not mix with Extended2).
274 This setting is not really important; almost all apps
275 will have no problem if it remains unspecified. For
276 CD-ROMs you might want to add it to get automatic label
277 detection, though. If you are unsure about specifying
278 device names, just leave out this setting for your
283 Here is a setup for Drive X, a generic hard drive:
288 "Label" =
"Hard Drive"
289 "Filesystem" =
"win95"
290 This is a setup for Drive X, a generic CD-ROM drive:
294 "Label" =
"Total Annihilation"
295 "Filesystem" =
"win95"
296 "Device" =
"/dev/hdc"
297 And here is a setup for Drive X, a generic floppy drive:
300 "Path" =
"/mnt/floppy"
301 "Label" =
"Floppy Drive"
302 "Serial" =
"87654321"
303 "Filesystem" =
"win95"
304 "Device" =
"/dev/fd0"
310 <title>The [wine] Section
</title>
312 The [wine] section of the configuration file contains all kinds
313 of general settings for Wine. When specifying the directories
314 for the directory related settings, make them as they would
315 appear in wine. If your drive
<medialabel>C
</medialabel>
316 has a path of
<filename>/dos
</filename>, and your
317 <filename>windows
</filename> directory is located in
318 <filename>/dos/windows
</filename>, then use:
319 <programlisting>"Windows" =
"c:\\windows"</programlisting>
322 This sets up the
<filename>windows
</filename> directory.
323 Make one if you don't already have one. NO TRAILING SLASH
324 (NOT
<filename>C:\\windows\
</filename>)!
327 <programlisting>"System" =
"c:\\windows\\system"</programlisting>
328 This sets up where the windows system files are. Should
329 reside in the directory used for the
330 <literal>Windows
</literal> setting. If you don't have
331 <filename>windows
</filename> then this is where the system
332 files will go. Again, NO TRAILING SLASH!
335 <programlisting>"Temp" =
"c:\\temp"</programlisting> This should
336 be the directory you want your temp files stored in. YOU
337 MUST HAVE WRITE ACCESS TO IT.
341 "Path" =
"c:\\windows;c:\\windows\\system;c:\\blanco"
345 Behaves like the
<envar>PATH
</envar> setting on UNIX
346 boxes. When wine is run like
<userinput>wine
347 sol.exe
</userinput>, if
<filename>sol.exe
</filename>
348 resides in a directory specified in the
349 <literal>Path
</literal> setting, wine will run it (Of
350 course, if
<filename>sol.exe
</filename> resides in the
351 current directory, wine will run that one). Make sure it
352 always has your
<filename>windows
</filename> directory and
353 system directory (For this setup, it must have
354 <filename>"c:\\windows;c:\\windows\\system"</filename>).
357 <programlisting>"GraphicsDriver" =
"x11drv|ttydrv"</programlisting>
358 Sets the graphics driver to use for Wine output.
359 x11drv is for X11 output, ttydrv is for text console output.
360 WARNING: if you use ttydrv here, then you won't be able to run
361 any Windows GUI programs. Thus this option is mainly interesting
362 for e.g. embedded use of Wine in web server scripts.
365 <programlisting>"Printer" =
"off|on"</programlisting> Tells wine
366 whether to allow printing via printer drivers to work.
367 This option isn't needed for our builtin psdrv printer driver
369 Using these things are pretty alpha, so you might want to
370 watch out. Some people might find it useful, however. If
371 you're not planning on working on printing via windows printer
372 drivers, don't even add this to your wine config file
373 (It probably isn't already in it).
374 Check out the [spooler] and [parallelports] sections too.
377 <programlisting>"ShellLinker" =
"wineshelllink"</programlisting>
378 This setting specifies the shell linker script to use for setting
379 up Windows icons in e.g. KDE or Gnome that are given by programs
380 making use of appropriate shell32.dll functionality to create
381 icons on the desktop/start menu during installation.
384 <programlisting>"ShowDirSymlinks" =
"1"</programlisting>
385 Wine doesn't pass directory symlinks to Windows programs by
386 default, as doing so may crash some programs that do
387 recursive lookups of whole subdirectory trees
388 whenever a directory symlink points back to itself or one of its
390 That's why we disallowed the use of directory symlinks
391 and added this setting to reenable (
"1") this functionality.
394 <programlisting>"SymbolTableFile" =
"wine.sym"</programlisting>
395 Sets up the symbol table file for the wine debugger. You
396 probably don't need to fiddle with this. May be useful if
397 your wine is stripped.
402 <title>Introduction To DLL Sections
</title>
404 There are a few things you will need to know before
405 configuring the DLL sections in your wine configuration
409 <title>Windows DLL Pairs
</title>
411 Most windows DLL's have a win16 (Windows
3.x) and win32
412 (Windows
9x/NT) form. The combination of the win16 and
413 win32 DLL versions are called the
"DLL pair". This is a
414 list of the most common pairs:
427 Is it possible to use native dll with wine?
436 <entry>KERNEL
</entry>
437 <entry>KERNEL32
</entry>
442 <entry>USER32
</entry>
447 <entry>SHELL32
</entry>
456 <entry>COMMDLG
</entry>
457 <entry>COMDLG32
</entry>
462 <entry>VERSION
</entry>
471 <title>Different Forms Of DLL's
</title>
473 There are a few different forms of DLL's wine can load:
478 The DLL's that are included with windows. Many
479 windows DLL's can be loaded in their native
480 form. Many times these native versions work
481 better than their non-Microsoft equivalent --
482 other times they don't.
488 ELF encapsulated windows DLL's. This is currently
489 experimental (Not working yet).
495 Native ELF libraries. Will not work yet.
501 The most common form of DLL loading. This is
502 what you will use if the DLL is error-prone in
503 native form (KERNEL for example), you don't have
504 the native DLL, or you just want to be
514 <title>The [DllDefaults] Section
</title>
516 These settings provide wine's default handling of DLL loading.
519 <programlisting>"DefaultLoadOrder" =
" native, so, builtin"</programlisting>
522 This setting is a comma-delimited list of the order in
523 which to attempt loading DLLs. If the first option fails,
524 it will try the second, and so on. The order specified
525 above is probably the best in most conditions.
530 <title>The [DllPairs] Section
</title>
532 At one time, there was a section called [DllPairs] in the
533 default configuration file, but this has been obsoleted
534 because the pairing information has now been embedded into
535 Wine itself. (The purpose of this section was merely to be
536 able to issue warnings if the user attempted to pair
537 codependent
16-bit/
32-bit DLLs of different types.) If you
538 still have this in your
<filename>wine.conf
</filename> or
539 <filename>~/.wine/config
</filename>, you may safely delete it.
544 <title>The [DllOverrides] Section
</title>
546 The format for this section is the same for each line:
548 <DLL
>{,
<DLL
>,
<DLL
>...} =
<FORM
>{,
<FORM
>,
<FORM
>...}
552 For example, to load builtin KERNEL pair (case doesn't
555 "kernel,kernel32" =
"builtin"
559 To load the native COMMDLG pair, but if that doesn't work
562 "commdlg,comdlg32" =
"native,builtin"
566 To load the native COMCTL32:
568 "comctl32" =
"native"
572 Here is a good generic setup (As it is defined in config
573 that was included with your wine package):
576 "commdlg" =
"builtin, native"
577 "comdlg32" =
"builtin, native"
578 "ver" =
"builtin, native"
579 "version" =
"builtin, native"
580 "shell" =
"builtin, native"
581 "shell32" =
"builtin, native"
582 "lzexpand" =
"builtin, native"
583 "lz32" =
"builtin, native"
584 "comctl32" =
"builtin, native"
585 "commctrl" =
"builtin, native"
586 "wsock32" =
"builtin"
587 "winsock" =
"builtin"
588 "advapi32" =
"builtin, native"
589 "crtdll" =
"builtin, native"
590 "mpr" =
"builtin, native"
591 "winspool.drv" =
"builtin, native"
592 "ddraw" =
"builtin, native"
593 "dinput" =
"builtin, native"
594 "dsound" =
"builtin, native"
595 "mmsystem" =
"builtin"
597 "msvcrt" =
"native, builtin"
598 "msvideo" =
"builtin, native"
599 "msvfw32" =
"builtin, native"
600 "mcicda.drv" =
"builtin, native"
601 "mciseq.drv" =
"builtin, native"
602 "mciwave.drv" =
"builtin, native"
603 "mciavi.drv" =
"native, builtin"
604 "mcianim.drv" =
"native, builtin"
605 "msacm.drv" =
"builtin, native"
606 "msacm" =
"builtin, native"
607 "msacm32" =
"builtin, native"
608 "midimap.drv" =
"builtin, native"
609 "wnaspi32" =
"builtin"
615 You see that elfdll or so is the first option for a few
616 of these dll's. This will fail for you, but you won't
617 notice it as wine will just use the second or third
624 <title>The [fonts] Section
</title>
626 This section sets up wine's font handling.
629 <programlisting>"Resolution" =
"96"</programlisting>
632 Since the way X handles fonts is different from the way
633 Windows does, wine uses a special mechanism to deal with
634 them. It must scale them using the number defined in the
635 "Resolution" setting.
60-
120 are reasonable values,
96 is
636 a nice in the middle one. If you have the real windows
637 fonts available (
<filename><dirs to
638 wine
>/documentation/ttfserver
</filename> and
639 <filename>fonts
</filename>), this parameter will not be as
640 important. Of course, it's always good to get your X fonts
641 working acceptably in wine.
644 <programlisting>"Default" =
"-adobe-times-"</programlisting>
645 The default font wine uses. Fool around with it if you'd like.
651 The
<literal>Alias
</literal> setting allows you to map an X font to a font
652 used in wine. This is good for apps that need a special font you don't have,
653 but a good replacement exists. The syntax is like so:
655 "AliasX" =
"[Fake windows name],[Real X name]"<,optional
"masking" section
>
659 Pretty straightforward. Replace
"AliasX" with
"Alias0",
660 then
"Alias1" and so on. The fake windows name is the name
661 that the font will be under a windows app in wine. The
662 real X name is the font name as seen by X (Run
663 "xfontsel"). The optional
"masking" section allows you to
664 utilize the fake windows name you define. If it is not
665 used, then wine will just try to extract the fake windows
666 name itself and not use the value you enter.
669 Here is an example of an alias without masking. The font will show up in windows
670 apps as
"Google". When defining an alias in a config file, forget about my
671 comment text (The
"<-- blah" stuff)
673 "Alias0" =
"Foo,--google-" <
677 Here is an example with masking enabled. The font will show up as
"Foo" in
680 "Alias1" =
"Foo,--google-,subst"
684 For more info check out
<filename><dirs to wine
>/documentation/fonts
</filename>
689 <title>The [serialports], [parallelports], [spooler], and [ports] Sections
</title>
691 Even though it sounds like a lot of sections, these are
692 all closely related. They are all for communications and
696 The [serialports] section tells wine what serial ports it
698 <programlisting>"ComX" =
"/dev/cuaY"</programlisting>
701 Replace
<literal>X
</literal> with the number of the COM
702 port in Windows (
1-
8) and
<literal>Y
</literal> with the
703 number of it in
<literal>X
</literal> (Usually the number
704 of the port in Windows minus
1).
<literal>ComX
</literal>
705 can actually equal any device
706 (
<medialabel>/dev/modem
</medialabel> is acceptable). It is
707 not always necessary to define any COM ports (An optional
708 setting). Here is an example:
709 <programlisting>"Com1" =
"/dev/cua0"</programlisting>
712 Use as many of these as you like in the section to define
713 all of the COM ports you need.
716 The [parallelports] section sets up any parallel ports
717 that will be allowed access under wine.
718 <programlisting>"LptX" =
"/dev/lpY"</programlisting>
721 Sounds familiar? Syntax is just like the COM port setting.
722 Replace
<literal>X
</literal> with a value from
1-
4 as it
723 is in Windows and
<literal>Y
</literal> with a value from
724 0-
3 (
<literal>Y
</literal> is usually the value in windows
725 minus
1, just like for COM ports). You don't always need
726 to define a parallel port (AKA, it's optional). As with
727 the other section, LptX can equal any device (Maybe
728 <medialabel>/dev/printer
</medialabel>). Here is an
729 example:
<programlisting>"Lpt1" =
"/dev/lp0"</programlisting>
732 The [spooler] section will inform wine where to spool
733 print jobs. Use this if you want to try printing. Wine
734 docs claim that spooling is
"rather primitive" at this
735 time, so it won't work perfectly. IT IS OPTIONAL. The only
736 setting you use in this section works to map a port (LPT1,
737 for example) to a file or a command. Here is an example,
738 mapping LPT1 to the file
<filename>out.ps
</filename>:
739 <programlisting>"LPT1:" =
"out.ps"</programlisting>
742 The following command maps printing jobs to LPT1 to the
743 command
<command>lpr
</command>. Notice the |:
744 <programlisting>"LPT1:" =
"|lpr"</programlisting>
747 The [ports] section is usually useful only for people who
748 need direct port access for programs requiring dongles or
749 scanners. IF YOU DON'T NEED IT, DON'T USE IT!
752 <programlisting>"read" =
"0x779,0x379,0x280-0x2a0"</programlisting>
753 Gives direct read access to those IO's.
756 <programlisting>"write" =
"0x779,0x379,0x280-0x2a0"</programlisting>
757 Gives direct write access to those IO's. It's probably a
758 good idea to keep the values of the
759 <literal>read
</literal> and
<literal>write
</literal>
760 settings the same. This stuff will only work when you're
766 <title>The [spy], [Registry], [tweak.layout], and [programs] Sections
</title>
768 [spy] is used to include or exclude debug messages, and to
769 output them to a file. The latter is rarely used. THESE
770 ARE ALL OPTIONAL AND YOU PROBABLY DON'T NEED TO ADD OR
771 REMOVE ANYTHING IN THIS SECTION TO YOUR CONFIG.
774 <programlisting>"File" =
"/blanco"</programlisting>
775 Sets the logfile for wine. Set to CON to log to standard out.
779 <programlisting>"Exclude" =
"WM_SIZE;WM_TIMER;"</programlisting>
780 Excludes debug messages about
<constant>WM_SIZE
</constant>
781 and
<constant>WM_TIMER
</constant> in the logfile.
784 <programlisting>"Include" =
"WM_SIZE;WM_TIMER;"</programlisting>
785 Includes debug messages about
<constant>WM_SIZE
</constant>
786 and
<constant>WM_TIMER
</constant> in the logfile.
789 [Registry] can be used to tell wine where your old windows
790 registry files exist. This section is completely optional
791 and useless to people using wine without an existing
792 windows installation.
795 <programlisting>"UserFileName" =
"/dirs/to/user.reg"</programlisting>
796 The location of your old
<filename>user.reg
</filename> file.
799 [tweak.layout] is devoted to wine's look. There is only
803 <programlisting>"WineLook" =
"win31|win95|win98"</programlisting>
804 Will change the look of wine from Windows
3.1 to Windows
95.
805 The
<literal>win98
</literal> setting behaves
806 just like
<literal>win95
</literal> most of the time.
809 [programs] can be used to say what programs run under
813 <programlisting>"Default" =
"/program/to/execute.exe"</programlisting>
814 Sets the program to be run if wine is started without specifying a program.
817 <programlisting>"Startup" =
"/program/to/execute.exe"</programlisting>
818 Sets the program to automatically be run at startup every time.
823 <title>The [WinMM] Section
</title>
825 [WinMM] is used to define which multimedia drivers have to be loaded. Since
826 those drivers may depend on the multimedia interfaces available on your sustem
827 (OSS, Alsa... to name a few), it's needed to be able to configure which driver
832 The content of the section looks like:
835 "Drivers" =
"wineoss.drv"
836 "WaveMapper" =
"msacm.drv"
837 "MidiMapper" =
"midimap.drv"
839 All the keys must be defined:
843 The
"Drivers" key is a ';' separated list of modules name, each of
844 them containing a low level driver. All those drivers will be loaded
845 when MMSYSTEM/WINMM is started and will provide their inner features.
850 The
"WaveMapper" represents the name of the module containing the Wave
851 Mapper driver. Only one wave mapper can be defined in the system.
856 The
"MidiMapper" represents the name of the module containing the Midi
857 Mapper driver. Only one Midi mapper can be defined in the system.
865 <title>The [AppDefaults] Section
</title>
867 The section is used to overwrite the setting of this file for a
868 special program with different settings.
869 [AppDefaults] is not the real name of the section. The real name
870 consists of the leading word AppDefaults followed by the name
871 of the executable the section is valid for. The end of the section
872 name is the name of the section of the configuration file its
873 values should be overwritten with different settings. The three
874 parts of the section name are separated by two backslashes.
877 Currently wine supports only overwriting the sections
878 [DllOverrides] and [x11drv].
881 Here is an example that overwrites the normal settings for a
889 ;; run install in desktop mode
890 [AppDefaults\\install.exe\\x11drv]
892 "Desktop" =
"800x600"
899 <title>Where Do I Put It?
</title>
901 The wine config file can go in two places.
905 <term><filename>/usr/local/etc/wine.conf
</filename></term>
907 A systemwide config file, used for anyone who doesn't
908 have their own. NOTE: this file is currently unused as a
909 new global configuration mechanism is not in place at this
914 <term><filename>$HOME/.wine/config
</filename></term>
916 Your own config file, that only is used for your user.
921 So copy your version of the
<filename>wine.conf
</filename> file to
922 <filename>/usr/local/etc/wine.conf
</filename> or
923 <filename>$HOME/.wine/config
</filename> for wine to recognize
929 <title>What If It Doesn't Work?
</title>
931 There is always a chance that things will go wrong. If the
932 unthinkable happens, try the newsgroup,
933 <systemitem>comp.emulators.ms-windows.wine
</systemitem>,
934 or the IRCnet channel
<systemitem>#WineHQ
</systemitem> found on
935 irc.stealth.net:
6668, or connected servers.
936 Make sure that you have looked over this document thoroughly,
941 <para><filename>README
</filename></para>
945 <filename>http://www.la-sorciere.de/wine/index.html
</filename>
946 (optional but recommended)
951 If indeed it looks like you've done your research, be
952 prepared for helpful suggestions. If you haven't, brace
953 yourself for heaving flaming.
958 <sect1 id=
"win95look">
959 <title>Win95/
98 Look
</title>
961 Written by &name-david-cuthbert;
<email>&email-david-cuthbert;
</email>
964 (Extracted from
<filename>wine/documentation/win95look
</filename>)
967 Win95/Win98 interface code is being introduced.
970 Instead of compiling Wine for Win3.1 vs. Win95 using
971 <constant>#define
</constant> switches, the code now looks in a
972 special [Tweak.Layout] section of
973 <filename>~/.wine/config
</filename> for a
974 <literal>"WineLook" =
"Win95"</literal> or
975 <literal>"WineLook" =
"Win98"</literal> entry.
978 A few new sections and a number of entries have been added to
979 the
<filename>~/.wine/config
</filename> file -- these are for
980 debugging the Win95 tweaks only and may be removed in a future
981 release! These entries/sections are:
985 "System.Height" =
"<point size>" # Sets the height of the system typeface
986 "System.Bold" =
"[true|false]" # Whether the system font should be boldfaced
987 "System.Italic" =
"[true|false]" # Whether the system font should be italicized
988 "System.Underline" =
"[true|false]" # Whether the system font should be underlined
989 "System.StrikeOut" =
"[true|false]" # Whether the system font should be struck out
990 "OEMFixed.xxx" # Same parameters for the OEM fixed typeface
991 "AnsiFixed.xxx" # Same parameters for the Ansi fixed typeface
992 "AnsiVar.xxx" # Same parameters for the Ansi variable typeface
993 "SystemFixed.xxx" # Same parameters for the System fixed typeface
996 "WineLook" =
"[Win31|Win95|Win98]" # Changes Wine's look and feel
1001 <title>Configuring the x11drv Driver
</title>
1004 Written by &name-ove-kaaven;
<email>&email-ove-kaaven;
</email>
1007 (Extracted from
<filename>wine/documentation/x11drv
</filename>)
1011 Most Wine users run Wine under the windowing system known as
1012 X11. During most of Wine's history, this was the only display
1013 driver available, but in recent years, parts of Wine has been
1014 reorganized to allow for other display drivers (although the
1015 only alternative currently available is Patrik Stridvall's
1016 ncurses-based ttydrv, which he claims works for displaying
1017 calc.exe). The display driver is chosen with the
1018 <literal>GraphicsDriver
</literal> option in the [wine] section
1019 of
<filename>~/.wine/config
</filename>, but I will only cover the
1020 x11drv driver in this article.
1024 <title>x11drv modes of operation
</title>
1027 <!-- FIXME: This is outdated -->
1028 Note: This is now all done in the config file. Needs an update...
1032 The x11drv driver consists of two conceptually distinct
1033 pieces, the graphics driver (GDI part), and the windowing
1034 driver (USER part). Both of these are linked into the
1035 <filename>libx11drv.so
</filename> module, though (which you
1036 load with the
<literal>GraphicsDriver
</literal> option). In
1037 Wine, running on X11, the graphics driver must draw on
1038 drawables (window interiors) provided by the windowing
1039 driver. This differs a bit from the Windows model, where the
1040 windowing system creates and configures device contexts
1041 controlled by the graphics driver, and applications are
1042 allowed to hook into this relationship anywhere they like.
1043 Thus, to provide any reasonable tradeoff between
1044 compatibility and usability, the x11drv has three different
1050 <term>Unmanaged/Normal
</term>
1053 The default. Window-manager-independent (any running
1054 window manager is ignored completely). Window
1055 decorations (title bars, borders, etc) are drawn by
1056 Wine to look and feel like the real Windows. This is
1057 compatible with applications that depend on being able
1058 to compute the exact sizes of any such decorations, or
1059 that want to draw their own.
1064 <term>Managed
</term>
1067 Specified by using the
1068 <parameter>--managed
</parameter> command-line option
1069 or the
<literal>Managed
</literal>
1070 <filename>wine.conf
</filename> option (see below).
1071 Ordinary top-level frame windows with thick borders,
1072 title bars, and system menus will be managed by your
1073 window manager. This lets these applications integrate
1074 better with the rest of your desktop, but may not
1075 always work perfectly. (A rewrite of this mode of
1076 operation, to make it more robust and less patchy, is
1077 highly desirable, though, and is planned to be done
1078 before the Wine
1.0 release.)
1083 <term>Desktop-in-a-Box
</term>
1086 Specified by using the
1087 <parameter>--desktop
</parameter> command-line option
1088 (with a geometry, e.g.
<parameter>--desktop
1089 800x600
</parameter> for a such-sized desktop, or
1090 even
<parameter>--desktop
800x600+
0+
0</parameter> to
1091 automatically position the desktop at the upper-left
1092 corner of the display). This is the mode most
1093 compatible with the Windows model. All application
1094 windows will just be Wine-drawn windows inside the
1095 Wine-provided desktop window (which will itself be
1096 managed by your window manager), and Windows
1097 applications can roam freely within this virtual
1098 workspace and think they own it all, without
1099 disturbing your other X apps.
1107 <title>The [x11drv] section
</title>
1111 <term>AllocSystemColors
</term>
1114 Applies only if you have a palette-based display, i.e.
1115 if your X server is set to a depth of
8bpp, and if you
1116 haven't requested a private color map. It specifies
1117 the maximum number of shared colormap cells (palette
1118 entries) Wine should occupy. The higher this value,
1119 the less colors will be available to other
1125 <term>PrivateColorMap
</term>
1128 Applies only if you have a palette-based display, i.e.
1129 if your X server is set to a depth of
8bpp. It
1130 specifies that you don't want to use the shared color
1131 map, but a private color map, where all
256 colors are
1132 available. The disadvantage is that Wine's private
1133 color map is only seen while the mouse pointer is
1134 inside a Wine window, so psychedelic flashing and
1135 funky colors will become routine if you use the mouse
1141 <term>PerfectGraphics
</term>
1144 This option only determines whether fast X11 routines
1145 or exact Wine routines will be used for certain ROP
1146 codes in blit operations. Most users won't notice any
1152 <term>ScreenDepth
</term>
1155 Applies only to multi-depth displays. It specifies
1156 which of the available depths Wine should use (and
1157 tell Windows apps about).
1162 <term>Display
</term>
1165 This specifies which X11 display to use, and if
1166 specified, will override both the
1167 <envar>DISPLAY
</envar> environment variable and the
1168 <parameter>--display
</parameter> command-line option.
1173 <term>Managed
</term>
1176 Wine can let frame windows be managed by your window
1177 manager. This option specifies whether you want that
1186 This specifies whether you want DirectDraw to use
1187 XFree86's
<firstterm>Direct Graphics
1188 Architecture
</firstterm> (DGA), which is able to
1189 take over the entire display and run the game
1190 full-screen at maximum speed. (With DGA1 (XFree86
1191 3.x), you still have to configure the X server to the
1192 game's requested bpp first, but with DGA2 (XFree86
1193 4.x), runtime depth-switching may be possible,
1194 depending on your driver's capabilities.) But be aware
1195 that if Wine crashes while in DGA mode, it may not be
1196 possible to regain control over your computer without
1197 rebooting. DGA normally requires either root
1198 privileges or read/write access to
1199 <filename>/dev/mem
</filename>.
1204 <term>UseXShm
</term>
1207 If you don't want DirectX to use DGA, you can at least
1208 use X Shared Memory extensions (XShm). It is much
1209 slower than DGA, since the app doesn't have direct
1210 access to the physical frame buffer, but using shared
1211 memory to draw the frame is at least faster than
1212 sending the data through the standard X11 socket, even
1213 though Wine's XShm support is still known to crash
1222 If you don't use DGA, you may want an alternative
1223 means to convince the mouse cursor to stay within the
1224 game window. This option does that. Of course, as with
1225 DGA, if Wine crashes, you're in trouble (although not
1226 as badly as in the DGA case, since you can still use
1227 the keyboard to get out of X).
1232 <term>DesktopDoubleBuffered
</term>
1235 Applies only if you use the
1236 <parameter>--desktop
</parameter> command-line option
1237 to run in a desktop window. Specifies whether to
1238 create the desktop window with a double-buffered
1239 visual, something most OpenGL games need to run
1248 <!-- FIXME: To be documented -->
1254 <term>XVideoPort
</term>
1257 <!-- FIXME: To be documented -->
1263 <term>Synchronous
</term>
1266 <!-- FIXME: To be documented -->
1277 <sect1 id=
"cdrom-labels">
1281 <firstname>Petr
</firstname>
1282 <surname>Tomasek
</surname>
1284 <address><email>&email-petr-tomasek;
</email></address>
1286 <contrib>Nov
14 1999</contrib>
1289 <firstname>Andreas
</firstname>
1290 <surname>Mohr
</surname>
1292 <address><email>&email-andreas-mohr;
</email></address>
1294 <contrib>Jan
25 2000</contrib>
1299 <title>Drive labels and serial numbers with wine
</title>
1301 Written by &name-petr-tomasek;
<email>&email-petr-tomasek;
</email>
1305 Changes by &name-andreas-mohr;
<email>&email-andreas-mohr;
</email>
1309 (Extracted from
<filename>wine/documentation/cdrom-labels
</filename>)
1312 Until now, your only possibility of specifying drive volume
1313 labels and serial numbers was to set them manually in the wine
1314 config file. By now, wine can read them directly from the
1315 device as well. This may be useful for many Win
9x games or
1316 for setup programs distributed on CD-ROMs that check for
1321 <title>What's Supported?
</title>
1323 <informaltable frame=
"all">
1327 <entry>File System
</entry>
1328 <entry>Types
</entry>
1329 <entry>Comment
</entry>
1334 <entry>FAT systems
</entry>
1335 <entry>hd, floppy
</entry>
1336 <entry>reads labels and serial numbers
</entry>
1339 <entry>ISO9660
</entry>
1340 <entry>cdrom
</entry>
1341 <entry>reads labels and serial numbers (not mixed-mode CDs yet !)
</entry>
1350 <title>How To Set Up?
</title>
1352 Reading labels and serial numbers just works automagically
1353 if you specify a
<literal>Device=
</literal> line in the
1354 [Drive X] section in your
<filename>~/.wine/config
</filename>.
1355 Note that the device has to exist and must be accessible if
1356 you do this, though.
1359 If you don't do that, then you should give fixed
1360 <literal>"Label" =
</literal> or
<literal>"Serial" =
</literal>
1361 entries in
<filename>~./wine/config
</filename>, as Wine returns
1362 these entries instead if no device is given. If they don't
1363 exist, then Wine will return default values (label
1364 <literal>Drive X
</literal> and serial
1365 <literal>12345678</literal>).
1368 If you want to give a
<literal>"Device" =
</literal> entry
1369 <emphasis>only
</emphasis> for drive raw sector accesses,
1370 but not for reading the volume info from the device (i.e. you want
1371 a
<emphasis>fixed
</emphasis>, preconfigured label), you need
1372 to specify
<literal>"ReadVolInfo" =
"0"</literal> to tell Wine
1373 to skip the volume reading.
1378 <title>EXAMPLES
</title>
1380 Here's a simple example of cdrom and floppy; labels will be
1381 read from the device on both cdrom and floppy; serial
1382 numbers on floppy only:
1386 "Path" =
"/mnt/floppy"
1388 "Device" =
"/dev/fd0"
1389 "Filesystem" =
"msdos"
1392 "Path" =
"/mnt/cdrom"
1394 "Device" =
"/dev/hda1"
1395 "Filesystem" =
"win95"
1398 Here's an example of overriding the CD-ROM label:
1402 "Path" =
"/mnt/cdrom"
1404 "Label" =
"X234GCDSE"
1405 ; note that the device isn't really needed here as we have a fixed label
1406 "Device" =
"/dev/cdrom"
1407 "Filesystem" =
"msdos"
1412 <title>Todo / Open Issues
</title>
1415 The cdrom label can be read only if the data track of
1416 the disk resides in the first track and the cdrom is
1420 Better checking for FAT superblock (it now checks only
1424 Support for labels/serial nums WRITING.
1427 Can the label be longer than
11 chars? (iso9660 has
32
1431 What about reading ext2 volume label? ....
1437 <sect1 id=
"dll-overrides">
1438 <title>Dll Overrides
</title>
1441 Written by &name-ove-kaaven;
<email>&email-ove-kaaven;
</email>
1444 (Extracted from
<filename>wine/documentation/dll-overrides
</filename>)
1448 The
<filename>wine.conf
</filename> directives [DllDefaults]
1449 and [DllOverrides] are the subject of some confusion. The
1450 overall purpose of most of these directives are clear enough,
1451 though - given a choice, should Wine use its own built-in
1452 DLLs, or should it use
<filename>.DLL
</filename> files found
1453 in an existing Windows installation? This document explains
1454 how this feature works.
1458 <title>DLL types
</title>
1463 A
"native" DLL is a
<filename>.DLL
</filename> file
1464 written for the real Microsoft Windows.
1468 <term>builtin
</term>
1470 A
"builtin" DLL is a Wine DLL. These can either be a
1471 part of
<filename>libwine.so
</filename>, or more
1472 recently, in a special
<filename>.so
</filename> file
1473 that Wine is able to load on demand.
1479 An
"elfdll" is a Wine
<filename>.so
</filename> file
1480 with a special Windows-like file structure that is as
1481 close to Windows as possible, and that can also
1482 seamlessly link dynamically with
"native" DLLs, by
1483 using special ELF loader and linker tricks. Bertho
1484 Stultiens did some work on this, but this feature has
1485 not yet been merged back into Wine (because of
1486 political reasons and lack of time), so this DLL type
1487 does not exist in the official Wine at this time. In
1488 the meantime, the
"builtin" DLL type gained some of
1489 the features of elfdlls (such as dynamic loading), so
1490 it's possible that
"elfdll" functionality will be
1491 folded into
"builtin" at some point.
1497 A native Unix
<filename>.so
</filename> file, with
1498 calling convention conversion thunks generated on the
1499 fly as the library is loaded. This is mostly useful
1500 for libraries such as
"glide" that have exactly the
1501 same API on both Windows and Unix.
1508 <title>The [DllDefaults] section
</title>
1511 <term>DefaultLoadOrder
</term>
1513 This specifies in what order Wine should search for
1514 available DLL types, if the DLL in question was not
1515 found in the [DllOverrides] section.
1522 <title>The [DllPairs] section
</title>
1524 At one time, there was a section called [DllPairs] in the
1525 default configuration file, but this has been obsoleted
1526 because the pairing information has now been embedded into
1527 Wine itself. (The purpose of this section was merely to be
1528 able to issue warnings if the user attempted to pair
1529 codependent
16-bit/
32-bit DLLs of different types.) If you
1530 still have this in your
<filename>wine.conf
</filename> or
1531 <filename>~/.wine/config
</filename>, you may safely delete it.
1536 <title>The [DllOverrides] section
</title>
1538 This section specifies how you want specific DLLs to be
1539 handled, in particular whether you want to use
"native" DLLs
1540 or not, if you have some from a real Windows configuration.
1541 Because builtins do not mix seamlessly with native DLLs yet,
1542 certain DLL dependencies may be problematic, but workarounds
1543 exist in Wine for many popular DLL configurations. Also see
1544 WWN's [
16]Status Page to figure out how well your favorite
1545 DLL is implemented in Wine.
1548 It is of course also possible to override these settings by
1549 explictly using Wine's
<parameter>--dll
</parameter>
1550 command-line option (see the man page for details). Some
1551 hints for choosing your optimal configuration (listed by
1552 16/
32-bit DLL pair):
1556 <term>krnl386, kernel32
</term>
1558 Native versions of these will never work, so don't try. Leave
1559 at
<literal>builtin
</literal>.
1563 <term>gdi, gdi32
</term>
1565 Graphics Device Interface. No effort has been made at trying to
1566 run native GDI. Leave at
<literal>builtin
</literal>.
1570 <term>user, user32
</term>
1572 Window management and standard controls. It was
1573 possible to use Win95's
<literal>native
</literal>
1574 versions at some point (if all other DLLs that depend
1575 on it, such as comctl32 and comdlg32, were also run
1576 <literal>native
</literal>). However, this is no longer
1577 possible after the Address Space Separation, so leave
1578 at
<literal>builtin
</literal>.
1584 NT kernel API. Although badly documented, the
1585 <literal>native
</literal> version of this will never
1586 work. Leave at
<literal>builtin
</literal>.
1590 <term>w32skrnl
</term>
1592 Win32s (for Win3.x). The
<literal>native
</literal>
1593 version will probably never work. Leave at
1594 <literal>builtin
</literal>.
1600 Win16 support library for NT. The
1601 <literal>native
</literal> version will probably never
1602 work. Leave at
<literal>builtin
</literal>.
1608 Win16 kernel stuff. Will never work
1609 <literal>native
</literal>. Leave at
1610 <literal>builtin
</literal>.
1614 <term>display
</term>
1616 Display driver. Definitely leave at
<literal>builtin
</literal>.
1620 <term>toolhelp
</term>
1622 Tool helper routines. This is rarely a source of problems.
1623 Leave at
<literal>builtin
</literal>.
1627 <term>ver, version
</term>
1629 Versioning. Seldom useful to mess with.
1633 <term>advapi32
</term>
1635 Registry and security features. Trying the
1636 <literal>native
</literal> version of this may or may
1641 <term>commdlg, comdlg32
</term>
1643 Common Dialogs, such as color picker, font dialog,
1644 print dialog, open/save dialog, etc. It is safe to try
1645 <literal>native
</literal>.
1649 <term>commctrl, comctl32
</term>
1651 Common Controls. This is toolbars, status bars, list controls,
1652 the works. It is safe to try
<literal>native
</literal>.
1656 <term>shell, shell32
</term>
1658 Shell interface (desktop, filesystem, etc). Being one of the
1659 most undocumented pieces of Windows, you may have luck with the
1660 <literal>native
</literal> version, should you need it.
1664 <term>winsock, wsock32
</term>
1666 Windows Sockets. The
<literal>native
</literal> version
1667 will not work under Wine, so leave at
1668 <literal>builtin
</literal>.
1674 ICMP routines for wsock32. As with wsock32, leave at
1675 <literal>builtin
</literal>.
1681 The
<literal>native
</literal> version may not work due
1682 to thunking issues. Leave at
1683 <literal>builtin
</literal>.
1687 <term>lzexpand, lz32
</term>
1689 Lempel-Ziv decompression. Wine's
1690 <literal>builtin
</literal> version ought to work fine.
1694 <term>winaspi, wnaspi32
</term>
1696 Advanced SCSI Peripheral Interface. The
1697 <literal>native
</literal> version will probably never
1698 work. Leave at
<literal>builtin
</literal>.
1704 C Runtime library. The
<literal>native
</literal>
1705 version will easily work better than Wine's on this
1710 <term>winspool.drv
</term>
1712 Printer spooler. You are not likely to have more luck
1713 with the
<literal>native
</literal> version.
1719 DirectDraw/Direct3D. Since Wine does not implement the
1720 DirectX HAL, the
<literal>native
</literal> version
1721 will not work at this time.
1727 DirectInput. Running this
<literal>native
</literal>
1728 may or may not work.
1734 DirectSound. It may be possible to run this
1735 <literal>native
</literal>, but don't count on it.
1739 <term>dplay/dplayx
</term>
1741 DirectPlay. The
<literal>native
</literal> version
1742 ought to work best on this, if at all.
1746 <term>mmsystem, winmm
</term>
1748 Multimedia system. The
<literal>native
</literal>
1749 version is not likely to work. Leave at
1750 <literal>builtin
</literal>.
1754 <term>msacm, msacm32
</term>
1756 Audio Compression Manager. The
1757 <literal>builtin
</literal> version works best, if you
1758 set msacm.drv to the same.
1762 <term>msvideo, msvfw32
</term>
1764 Video for Windows. It is safe (and recommended) to try
1765 <literal>native
</literal>.
1769 <term>mcicda.drv
</term>
1771 CD Audio MCI driver.
1775 <term>mciseq.drv
</term>
1777 MIDI Sequencer MCI driver (
<filename>.MID
</filename>
1782 <term>mciwave.drv
</term>
1784 Wave audio MCI driver (
<filename>.WAV
</filename> playback).
1788 <term>mciavi.drv
</term>
1790 AVI MCI driver (
<filename>.AVI
</filename> video
1791 playback). Best to use
<literal>native
</literal>.
1795 <term>mcianim.drv
</term>
1797 Animation MCI driver.
1801 <term>msacm.drv
</term>
1803 Audio Compression Manager. Set to same as msacm32.
1807 <term>midimap.drv
</term>
1815 This is a pseudo-DLL used by Wine for thunking
1816 purposes. A
<literal>native
</literal> version of this
1824 <sect1 id=
"keyboard">
1825 <title>Keyboard
</title>
1828 Written by &name-ove-kaaven;
<email>&email-ove-kaaven;
</email>
1831 (Extracted from
<filename>wine/documentation/keyboard
</filename>)
1835 Wine now needs to know about your keyboard layout. This
1836 requirement comes from a need from many apps to have the
1837 correct scancodes available, since they read these directly,
1838 instead of just taking the characters returned by the X
1839 server. This means that Wine now needs to have a mapping from
1840 X keys to the scancodes these applications expect.
1843 On startup, Wine will try to recognize the active X layout by
1844 seeing if it matches any of the defined tables. If it does,
1845 everything is alright. If not, you need to define it.
1848 To do this, open the file
1849 <filename>windows/x11drv/keyboard.c
</filename> and take a look
1850 at the existing tables. Make a backup copy of it, especially
1851 if you don't use CVS.
1854 What you really would need to do, is find out which scancode
1855 each key needs to generate. Find it in the
1856 <function>main_key_scan
</function> table, which looks like
1860 static const int main_key_scan[MAIN_LEN] =
1862 /* this is my (
102-key) keyboard layout, sorry if it doesn't quite match yours */
1863 0x29,
0x02,
0x03,
0x04,
0x05,
0x06,
0x07,
0x08,
0x09,
0x0A,
0x0B,
0x0C,
0x0D,
1864 0x10,
0x11,
0x12,
0x13,
0x14,
0x15,
0x16,
0x17,
0x18,
0x19,
0x1A,
0x1B,
1865 0x1E,
0x1F,
0x20,
0x21,
0x22,
0x23,
0x24,
0x25,
0x26,
0x27,
0x28,
0x2B,
1866 0x2C,
0x2D,
0x2E,
0x2F,
0x30,
0x31,
0x32,
0x33,
0x34,
0x35,
1867 0x56 /* the
102nd key (actually to the right of l-shift) */
1871 Next, assign each scancode the characters imprinted on the
1872 keycaps. This was done (sort of) for the US
101-key keyboard,
1873 which you can find near the top in
1874 <filename>keyboard.c
</filename>. It also shows that if there
1875 is no
102nd key, you can skip that.
1878 However, for most international
102-key keyboards, we have
1879 done it easy for you. The scancode layout for these already
1880 pretty much matches the physical layout in the
1881 <function>main_key_scan
</function>, so all you need to do is
1882 to go through all the keys that generate characters on your
1883 main keyboard (except spacebar), and stuff those into an
1884 appropriate table. The only exception is that the
102nd key,
1885 which is usually to the left of the first key of the last line
1886 (usually
<keycap>Z
</keycap>), must be placed on a separate
1887 line after the last line.
1890 For example, my Norwegian keyboard looks like this
1893 § !
" # ¤ % & / ( ) = ? ` Back-
1894 | 1 2@ 3£ 4$ 5 6 7{ 8[ 9] 0} + \´ space
1896 Tab Q W E R T Y U I O P Å ^
1899 Caps A S D F G H J K L Ø Æ *
1902 Sh- > Z X C V B N M ; : _ Shift
1905 Ctrl Alt Spacebar AltGr Ctrl
1908 Note the 102nd key, which is the <keycap><></keycap> key, to
1909 the left of <keycap>Z</keycap>. The character to the right of
1910 the main character is the character generated by
1911 <keycap>AltGr</keycap>.
1914 This keyboard is defined as follows:
1917 static const char main_key_NO[MAIN_LEN][4] =
1919 "|§
","1!
","2\
"@",
"3#£",
"4¤$",
"5%",
"6&",
"7/{",
"8([",
"9)]",
"0=}",
"+?",
"\\´",
1920 "qQ",
"wW",
"eE",
"rR",
"tT",
"yY",
"uU",
"iI",
"oO",
"pP",
"åÅ",
"¨^~",
1921 "aA",
"sS",
"dD",
"fF",
"gG",
"hH",
"jJ",
"kK",
"lL",
"øØ",
"æÆ",
"'*",
1922 "zZ",
"xX",
"cC",
"vV",
"bB",
"nN",
"mM",
",;",
".:",
"-_",
1927 Except that
" and \ needs to be quoted with a backslash, and
1928 that the 102nd key is on a separate line, it's pretty
1932 After you have written such a table, you need to add it to the
1933 <function>main_key_tab[]</function> layout index table. This
1934 will look like this:
1938 WORD lang, ansi_codepage, oem_codepage;
1939 const char (*key)[MAIN_LEN][4];
1943 {MAKELANGID(LANG_NORWEGIAN,SUBLANG_DEFAULT), 1252, 865, &main_key_NO},
1947 After you have added your table, recompile Wine and test that
1948 it works. If it fails to detect your table, try running
1951 wine --debugmsg +key,+keyboard >& key.log
1954 and look in the resulting <filename>key.log</filename> file to
1955 find the error messages it gives for your layout.
1958 Note that the <constant>LANG_*</constant> and
1959 <constant>SUBLANG_*</constant> definitions are in
1960 <filename>include/winnls.h</filename>, which you might need to
1961 know to find out which numbers your language is assigned, and
1962 find it in the debugmsg output. The numbers will be
1963 <literal>(SUBLANG * 0x400 + LANG)</literal>, so, for example
1964 the combination <literal>LANG_NORWEGIAN (0x14)</literal> and
1965 <literal>SUBLANG_DEFAULT (0x1)</literal> will be (in hex)
1966 <literal>14 + 1*400 = 414</literal>, so since I'm Norwegian, I
1967 could look for <literal>0414</literal> in the debugmsg output
1968 to find out why my keyboard won't detect.
1971 Once it works, submit it to the Wine project. If you use CVS,
1972 you will just have to do
1975 cvs -z3 diff -u windows/x11drv/keyboard.c > layout.diff
1978 from your main Wine directory, then submit
1979 <filename>layout.diff</filename> to
1980 <email>wine-patches@winehq.com</email> along with a brief note
1984 If you don't use CVS, you need to do
1987 diff -u the_backup_file_you_made windows/x11drv/keyboard.c > layout.diff
1990 and submit it as explained above.
1993 If you did it right, it will be included in the next Wine
1994 release, and all the troublesome applications (especially
1995 remote-control applications) and games that use scancodes will
1996 be happily using your keyboard layout, and you won't get those
1997 annoying fixme messages either.
2009 <!-- Keep this comment at the end of the file
2012 sgml-parent-document:("wine-doc.sgml
" "set
" "book
" "chapter
" "")