diff --git a/README b/README index 7ce9cc5a7ce..44e5dd9da22 100644 --- a/README +++ b/README @@ -52,7 +52,7 @@ FreeBSD info: Solaris info: You will most likely need to build Wine with the GNU toolchain (gcc, gas, etc.). Warning : installing gas does *not* ensure that it - will be used by gcc. Recompiling gcc after installing gas or + will be used by gcc. Recompiling gcc after installing gas or symlinking cc, as and ld to the gnu tools is said to be necessary. NetBSD info: @@ -86,10 +86,15 @@ are compiled with optimization, often due to problems with header file management. pgcc currently doesn't work with Wine. The cause of this problem is unknown. +Of course you also need "make" (most likely GNU make). + You also need flex version 2.5 or later and yacc. Bison will work as a replacement for yacc. If you are using RedHat or Debian, install the flex and bison packages. +For the automatic processing of the test suite scripts, you also need +libperl development header support (libperl-dev package on Debian). + For requirements in case you intend to build the documentation yourself, see "DOCUMENTATION" section. @@ -102,7 +107,7 @@ to build Wine: make depend make -This will build the program "wine" and numerous support libraries/binaries. +This will build the program "wine" and numerous support libraries/binaries. The program "wine" will load and run Windows executables. The library "libwine" ("Winelib") can be used to compile and link Windows source code under Unix. @@ -217,16 +222,13 @@ Bugs: Report bugs to Wine Bugzilla at http://bugs.winehq.com/. Please read the file documentation/bugs.sgml to see what information is required. -HOWTO: The Wine HOWTO (outdated !) is available at - http://www.westfalen.de/witch/wine-HOWTO.txt . - IRC: Online help is available at channel #WineHQ on irc.openprojects.net. CVS: The current Wine development tree is available through CVS. Go to http://www.winehq.com/development/ for more information. Mailing lists: - There are several mailing lists for Wine developers; see + There are several mailing lists for Wine developers; see http://www.winehq.com/development/#ml for more information. If you add something, or fix a bug, please send a patch (in 'diff -u' diff --git a/documentation/configuring.sgml b/documentation/configuring.sgml index 5a684eecb29..44d47c6ddb7 100644 --- a/documentation/configuring.sgml +++ b/documentation/configuring.sgml @@ -180,63 +180,76 @@ The [Drive X] Section - It should be pretty self explanatory, but here is an - in-depth tutorial about them. There are up to 6 lines for - each drive in Wine. + 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. + 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 - path is where the drive will begin. When Wine is browsing - in drive X, it will see the files that are in the - directory /dir/to/path. Don't forget - to leave off the trailing slash! + "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" = "floppy|hd|cdrom|network" + "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. Info on finding the lable is in - <dirs to wine>/documentation/cdrom-labels. + "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 - don't use it. Up to 8 characters and hexadecimal. + 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" = "msdos|win95|unix" + "Filesystem" = "win95|unix|msdos" Sets up the way Wine looks at files on the drive. - - msdos - - - Case insensitive filesystem. Alike to DOS and - Windows 3.x. 8.3 is the maximum - length of files (eightdot.123) - longer ones will be - truncated. (NOTE: this is a very bad choice if you - plan on running apps that use long filenames. win95 - should work fine with apps that were designed to run - under the msdos system. In other words, you might - not want to use this.) - - - win95 @@ -260,42 +273,62 @@ + + msdos + + + Case insensitive filesystem. Alike to DOS and + Windows 3.x. 8.3 is the maximum + length of files (eightdot.123) - longer ones will be + truncated. (NOTE: this is a very bad choice if you + plan on running apps that use long filenames. win95 + should work fine with apps that were designed to run + under the msdos system. In other words, you might + not want to use this.) + + + "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 partitions can have dire results (when a windows - app tries to do a lowlevel write, they do it in a FAT way - -- FAT does not mix with Extended2). + 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. This setting is not really important; almost all apps will have no problem if it remains unspecified. For - CD-ROMs you might want to add it to get automatic label + CD-ROMs it's quite useful in order to get automatic label detection, though. If you are unsure about specifying device names, just leave out this setting for your drives. - Here is a setup for Drive X, a generic hard drive: + Here are a few sample entries: -[Drive X] -"Path" = "/dos-a" +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 X, a generic CD-ROM drive: -[Drive X] -"Path" = "/dos-d" +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/hdc" -And here is a setup for Drive X, a generic floppy drive: -[Drive X] +"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" @@ -310,31 +343,39 @@ And here is a setup for Drive X, a generic floppy drive: The [wine] Section The [wine] section of the configuration file contains all kinds - of general settings for Wine. When specifying the directories - for the directory related settings, make them as they would - appear in wine. If your drive C - has a path of /dos, and your - windows directory is located in - /dos/windows, then use: - "Windows" = "c:\\windows" - + of general settings for Wine. + - This sets up the windows directory. - Make one if you don't already have one. NO TRAILING SLASH - (NOT C:\\windows\)! + "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. Should - reside in the directory used for the - Windows setting. If you don't have - windows then this is where the system - files will go. Again, NO TRAILING SLASH! + 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. YOU - MUST HAVE WRITE ACCESS TO IT. + 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!! @@ -380,7 +421,7 @@ And here is a setup for Drive X, a generic floppy drive: 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 @@ -957,48 +998,6 @@ OPTIONAL: - - Win95/98 Look - - Written by &name-david-cuthbert; &email-david-cuthbert; - - - (Extracted from wine/documentation/win95look) - - - Win95/Win98 interface code is being introduced. - - - Instead of compiling Wine for Win3.1 vs. Win95 using - #define switches, the code now looks in a - special [Tweak.Layout] section of - ~/.wine/config for a - "WineLook" = "Win95" or - "WineLook" = "Win98" entry. - - - A few new sections and a number of entries have been added to - the ~/.wine/config file -- these are for - debugging the Win95 tweaks only and may be removed in a future - release! These entries/sections are: - - -[Tweak.Fonts] -"System.Height" = "<point size>" # Sets the height of the system typeface -"System.Bold" = "[true|false]" # Whether the system font should be boldfaced -"System.Italic" = "[true|false]" # Whether the system font should be italicized -"System.Underline" = "[true|false]" # Whether the system font should be underlined -"System.StrikeOut" = "[true|false]" # Whether the system font should be struck out -"OEMFixed.xxx" # Same parameters for the OEM fixed typeface -"AnsiFixed.xxx" # Same parameters for the Ansi fixed typeface -"AnsiVar.xxx" # Same parameters for the Ansi variable typeface -"SystemFixed.xxx" # Same parameters for the System fixed typeface - -[Tweak.Layout] -"WineLook" = "[Win31|Win95|Win98]" # Changes Wine's look and feel - - - Configuring the x11drv Driver @@ -1856,6 +1855,51 @@ OPTIONAL: + &fonts; + &printing; + + + Win95/98 Look + + Written by &name-david-cuthbert; &email-david-cuthbert; + + + (Extracted from wine/documentation/win95look) + + + Win95/Win98 interface code is being introduced. + + + Instead of compiling Wine for Win3.1 vs. Win95 using + #define switches, the code now looks in a + special [Tweak.Layout] section of + ~/.wine/config for a + "WineLook" = "Win95" or + "WineLook" = "Win98" entry. + + + A few new sections and a number of entries have been added to + the ~/.wine/config file -- these are for + debugging the Win95 tweaks only and may be removed in a future + release! These entries/sections are: + + +[Tweak.Fonts] +"System.Height" = "<point size>" # Sets the height of the system typeface +"System.Bold" = "[true|false]" # Whether the system font should be boldfaced +"System.Italic" = "[true|false]" # Whether the system font should be italicized +"System.Underline" = "[true|false]" # Whether the system font should be underlined +"System.StrikeOut" = "[true|false]" # Whether the system font should be struck out +"OEMFixed.xxx" # Same parameters for the OEM fixed typeface +"AnsiFixed.xxx" # Same parameters for the Ansi fixed typeface +"AnsiVar.xxx" # Same parameters for the Ansi variable typeface +"SystemFixed.xxx" # Same parameters for the System fixed typeface + +[Tweak.Layout] +"WineLook" = "[Win31|Win95|Win98]" # Changes Wine's look and feel + + + Keyboard @@ -2036,9 +2080,6 @@ diff -u the_backup_file_you_made dlls/x11drv/keyboard.c > layout.diff - &fonts; - &printing; -