ReceiveTempSMS/Sweden-Number
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Updated for the new 'dosdevices' directory system.

Browse Source
This commit is contained in:
Richard Stonehouse 2004-07-06 21:03:57 +00:00 committed by Alexandre Julliard
parent f8dba77dc8
commit 73c23f4958
1 changed files with 115 additions and 206 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

317
documentation/configuring.sgml
View File

@ -208,11 +208,6 @@
<para> <para>
The settings available in the configuration file include: The settings available in the configuration file include:
<itemizedlist> <itemizedlist>
<listitem>
<para>
Drives and information about them
</para>
</listitem>
<listitem> <listitem>
<para> <para>
Directory settings Directory settings
@ -301,11 +296,6 @@
</row> </row>
</thead> </thead>
<tbody> <tbody>
<row>
<entry>[Drive x]</entry>
<entry>yes</entry>
<entry>Sets up drive mappings to be used by Wine</entry>
</row>
<row> <row>
<entry>[wine]</entry> <entry>[wine]</entry>
<entry>yes</entry> <entry>yes</entry>
@ -326,16 +316,6 @@
<entry>yes</entry> <entry>yes</entry>
<entry>Font appearance and recognition</entry> <entry>Font appearance and recognition</entry>
</row> </row>
<row>
<entry>[serialports]</entry>
<entry>no</entry>
<entry>COM ports seen by Wine</entry>
</row>
<row>
<entry>[parallelports]</entry>
<entry>no</entry>
<entry>LPT ports seen by Wine</entry>
</row>
<row> <row>
<entry>[ppdev]</entry> <entry>[ppdev]</entry>
<entry>no</entry> <entry>no</entry>
@ -400,17 +380,6 @@
detailed way. detailed way.
</para> </para>
<sect3>
<title>The [Drive x] Sections</title>
<para>
For a detailed description of these configuration file
sections which are used to set up DOS drive mappings to Unix
directory space, please look at the <link
linkend="config-drive-sections">Wine file system layer
configuration section</link>.
</para>
</sect3>
<sect3 id="config-wine"> <sect3 id="config-wine">
<title>The [wine] Section </title> <title>The [wine] Section </title>
<para> <para>
@ -427,8 +396,8 @@
</programlisting> </programlisting>
For a detailed description of drive layer configuration and For a detailed description of drive layer configuration and
the meaning of these parameters, please look at the <link the meaning of these parameters, please look at the <link
linkend="config-drive-main">Wine file system layer linkend="config-drive-main">Disc Drives, Serial and Parallel
configuration section</link>. Ports section</link>.
</para> </para>
<para> <para>
<programlisting>"GraphicsDriver" = "x11drv|ttydrv"</programlisting> <programlisting>"GraphicsDriver" = "x11drv|ttydrv"</programlisting>
@ -589,41 +558,8 @@
</sect3> </sect3>
<sect3 id="config-io"> <sect3 id="config-io">
<title>The [serialports], [parallelports], [spooler], and [ports] Sections</title> <title>The [spooler] and [ports] Sections</title>
<para> <para>
Even though it sounds like a lot of sections, these are
all closely related. They are all for communications and
parallel ports.
</para>
<para>
The [serialports] section tells wine what serial ports it
is allowed to use.
<programlisting>"ComX" = "/dev/ttySY"</programlisting>
Replace <literal>X</literal> with the number of the COM
port in Windows (1-8) and <literal>Y</literal> with the
number of it in <literal>X</literal> (Usually the number
of the port in Windows minus 1). <literal>ComX</literal>
can actually equal any device
(<medialabel>/dev/modem</medialabel> is acceptable). It is
not always necessary to define any COM ports (An optional
setting). Here is an example:
<programlisting>"Com1" = "/dev/ttyS0"</programlisting>
Use as many of these as you like in the section to define
all of the COM ports you need.
</para>
<para>
The [parallelports] section sets up any parallel ports
that will be allowed access under wine.
<programlisting>"LptX" = "/dev/lpY"</programlisting>
Sounds familiar? Syntax is just like the COM port setting.
Replace <literal>X</literal> with a value from 1-4 as it
is in Windows and <literal>Y</literal> with a value from
0-3 (<literal>Y</literal> 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
<medialabel>/dev/printer</medialabel>). Here is an
example: <programlisting>"Lpt1" = "/dev/lp0"</programlisting>
The [spooler] section will inform wine where to spool The [spooler] section will inform wine where to spool
print jobs. Use this if you want to try printing. Wine print jobs. Use this if you want to try printing. Wine
docs claim that spooling is "rather primitive" at this docs claim that spooling is "rather primitive" at this
@ -873,7 +809,7 @@
</sect1> </sect1>
<sect1 id="config-drive-main"> <sect1 id="config-drive-main">
<title>The Wine File System And Drive Layer</title> <title>Disc Drives, Serial and Parallel Ports</title>
<sect2> <sect2>
<title>Extremely Important Prerequisites</title> <title>Extremely Important Prerequisites</title>
<para> <para>
@ -898,29 +834,54 @@
<sect2> <sect2>
<title>Short Introduction</title> <title>Short Introduction</title>
<para> <para>
Wine emulates drives by placing their virtual drive roots to Windows applications refer to disc drives by letters such as
user-configurable points in the Unix filesystem, so it's your <filename>A:</filename>, <filename>B:</filename> and
choice where <medialabel>C:</medialabel>'s root should be <filename>C:</filename>, and to serial and parallel ports by names
(<filename>tools/wineinstall</filename> will even ask you). If such as <filename>COM1</filename>: and <filename>LPT1:</filename>.
you choose, say, <filename>~/wine</filename> (or, in other
words, <filename>/home/user/wine</filename>, since "~"
indicates the home directory of a user), as the root of your
virtual drive <medialabel>C:</medialabel>, then you'd put this
into your Wine configuration file:
</para> </para>
<programlisting>
[Drive C]
"Path" = "%HOME%/wine"
"Type" = "hd"
</programlisting>
<para> <para>
With this configuration, what windows apps think of as You need to tell Wine how to interpret these. You do so by
"c:\windows\system" would map to specifying the Unix file system nodes and devices that Wine
<filename>/home/user/wine/windows/system</filename> in the UNIX should map them onto, as described later in this section.
filesystem.
</para> </para>
<para>
You can map a Windows fixed disc drive onto any node in your
Unix file system - this need not be the root node of a drive.
For example, you could map your Windows drive <filename>C:</filename>
onto your Unix directory <filename>/usr/share/wine-C</filename>.
Then the Windows folder <filename>C:\Windows\Fonts</filename> would
be at <filename>/usr/share/wine-C/Windows/Fonts</filename> in your
Unix file system.
</para>
<para>
Make sure that you have assigned drive letters for directories
that will cover all the items Wine needs to access. These include
the programs that you run, the data files they need and the Wine
debugger (in case anything goes wrong).
</para>
<para>
It is best to use a number of drive letters, and map them onto
directories that cover small sections of the file system containing
the files that Wine will need to access. This is safer than simply
assigning a single drive letter to the Unix root directory
<filename></filename>/, which would allow Windows applications to
access the whole of your Unix file system (subject, of course,
to Unix permissions). If one of them misbehaved, or if you
accidentally installed a virus, this might leave you vulnerable.
</para>
<para>
For replaceable media, such as floppy discs and CD-ROMs, you should
map Windows drive letters onto the mount points for these drives in
your Unix file system - for example <filename>/mnt/floppy</filename>
or <filename>/mnt/cdrom</filename>.
</para>
<para>
If your applications access serial and parallel ports directly,
you should map these onto the corresponding Unix devices
- for example <filename>/dev/ttyS0</filename> and
<filename>/dev/lp0</filename>.
</para>
</sect2> </sect2>
<sect2 id="config-drive-dir"> <sect2 id="config-drive-dir">
@ -951,100 +912,51 @@ C:\ Root directory of primary disk drive
</sect2> </sect2>
<sect2 id="config-drive-sections"> <sect2 id="config-drive-sections">
<title>The [Drive x] Sections</title> <title>The dosdevices Directory</title>
<para> <para>
These sections are supposed to make certain Unix The <filename>dosdevices</filename> directory contains the entries
directory locations accessible to Wine as a DOS/Windows drive that tell Wine how to map Windows disc drive letters onto Unix file
(drive 'x:') and thus accessible to Windows programs system nodes, and how to map Windows serial and parallel ports onto
under the drive name you specified. Unix devices. It is located in the <filename>.wine</filename>
Every DOS/Windows program sort of expects at least a C: sub-directory of your home directory,
drive (and sometimes also an A: floppy drive), so your i.e. <filename>~/.wine/dosdevices</filename>.
configuration 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.
</para> </para>
<para> <para>
<programlisting>[Drive x]</programlisting> The entries in the <filename>dosdevices</filename> directory are
The above line begins the section for a drive whose letter is x symbolic links to Unix file system nodes and devices. You can
(DOS notation: drive 'x:'). create them by using the <command>ln</command> command in a Unix
You could e.g. create an equivalent to a drive 'C:' terminal. Alternatively, many File Managers have the capability of
under DOS/Windows by using a [Drive C] section name. creating symbolic links.
Note that the drive letter is case insensitive.
</para> </para>
<para> <para>
<programlisting>"Path" = "/dir/to/path"</programlisting> For example, if you have decided to map your Windows
This specifies the directory where the drive will begin. <filename>C:</filename> drive onto
When Wine is browsing in drive x, it will be able <filename>/usr/share/wine-c</filename>, you could type the
to see the files that are in the directory following (after changing to your <filename>dosdevices</filename>
<filename>/dir/to/path</filename> and below. directory):
(note that symlinks to directories won't get included!
see "<link linkend="dirsymlinks">ShowDirSymlinks</link>"
configuration setting)
You can also make use of environment variables like $HOME here,
an example for using a <filename>mywinedrive</filename>
directory in your home dir would be
<programlisting>"Path" = "%HOME%/mywinedrive"</programlisting>,
but don't forget to put it as a DOS environment variable,
ie surrounded by '%' signs rather than preceded by a '$'.
Don't forget to leave off the trailing slash!
</para>
<para>
<programlisting>"Type" = "hd|cdrom|network|floppy"</programlisting>
Sets up the type of drive Wine will see it as. Type must
equal one of the four <literal>floppy</literal>,
<literal>hd</literal>, <literal>cdrom</literal>, or
<literal>network</literal>. They are self-explanatory.
(The |'s mean "Type = '&lt;one of the options&gt;'".)
Usually, you choose "hd" for a drive ("hd" is default anyway).
For a home directory entry, it makes sense to choose
"network" sometimes, since some home directories are being
exported over the network via NFS and thus can have slow response
times.
</para>
<programlisting>"Device" = "/dev/xx"</programlisting>
<para>
Needed for raw device access and <link linkend="config-drive-cdrom-labels">label and serial number reading</link>.
Use this <emphasis>only</emphasis> 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.
</para>
<note>
<para>
This setting is not really important; almost all apps
will have no problem if it remains unspecified. For
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.
</para>
</note>
<para>
Here are a few sample entries:
<programlisting> <programlisting>
Here is a setup for Drive C, a generic hard drive: ln -s /usr/share/wine-c c:
[Drive C] </programlisting>
"Path" = "/dosc" </para>
"Type" = "hd" <para>
This is a setup for Drive E, a generic CD-ROM drive: Replaceable media are a little more complicated. In addition to
[Drive E] creating a link for the file system on the medium, for example:
"Path" = "/mnt/cdrom" <programlisting>
"Type" = "cdrom" ln -s /mnt/floppy a:
"Device" = "/dev/cdrom" </programlisting>
And here is a setup for Drive A, a generic floppy drive: you also need to create a link for the device itself. Notice that
[Drive A] this has a double colon after the drive letter:
"Type" = "floppy" <programlisting>
"Path" = "/mnt/floppy" ln -s /dev/fd0 a::
"Device" = "/dev/fd0" </programlisting>
</para>
<para>
For serial and parallel ports, you simply create a link to
the device; notice that no colon is required after the Windows
device name:
<programlisting>
ln -s /dev/ttyS0 com1
ln -s /dev/lp0 lpt1
</programlisting> </programlisting>
</para> </para>
</sect2> </sect2>
@ -1228,11 +1140,11 @@ And here is a setup for Drive A, a generic floppy drive:
<orderedlist> <orderedlist>
<listitem> <listitem>
<para> <para>
Point <medialabel>[Drive C]</medialabel> in Make a symbolic link in <filename>~/.wine/dosdevices</filename>
<filename>~/.wine/config</filename> to the directory where you want to the directory where you want
<filename>C:</filename> to be. Refer to the wine.conf man page <filename>C:</filename> to be. Refer to the wine man page
for more information. for more information. The directory to be used for emulating
The directory to be used for emulating a C: drive will be a <filename>C:</filename> drive will be
the base directory for some Windows specific directories the base directory for some Windows specific directories
created below. created below.
</para> </para>
@ -1389,17 +1301,16 @@ And here is a setup for Drive A, a generic floppy drive:
through Wine for dual boot (Linux + Windows) systems. through Wine for dual boot (Linux + Windows) systems.
</para> </para>
<para> <para>
Wine maps mounted FAT filesystems, such as Wine maps mounted FAT file systems, such as
<filename>/c</filename>, to driver letters, such as <filename>/c</filename>, to drive letters, such as
<quote>c:</quote>, as indicated by the <quote>c:</quote>, by means of symbolic links in the
<filename>~/.wine/config</filename> file. The following excerpt <link linkend="config-drive-sections"><filename>dosdevices</filename></link>
from a <filename>~/.wine/config</filename> file does this: directory. Thus, in your dosdevices directory, you could type
</para> the command:
<programlisting> <programlisting>
[Drive C] ln -s /c c:
"Path" = "/c"
"Type" = "hd"
</programlisting> </programlisting>
</para>
<para> <para>
Although VFAT filesystems are preferable to FAT filesystems Although VFAT filesystems are preferable to FAT filesystems
for their long filename support, the term <quote>FAT</quote> for their long filename support, the term <quote>FAT</quote>
@ -1588,10 +1499,8 @@ And here is a setup for Drive A, a generic floppy drive:
<title>Drive labels and serial numbers</title> <title>Drive labels and serial numbers</title>
<para> <para>
Until now, your only possibility of specifying drive volume Wine can read drive volume labels and serial numbers directly
labels and serial numbers was to set them manually in the wine from the device. This may be useful for many Win 9x games or
configuration file. By now, wine can read them directly from the
device as well. This may be useful for many Win 9x games or
for setup programs distributed on CD-ROMs that check for for setup programs distributed on CD-ROMs that check for
volume label. volume label.
</para> </para>
@ -1629,8 +1538,10 @@ And here is a setup for Drive A, a generic floppy drive:
<title>How To Set Up?</title> <title>How To Set Up?</title>
<para> <para>
Reading labels and serial numbers just works automatically Reading labels and serial numbers just works automatically
if you specify a <literal>"Device" =</literal> line in the if you specify the correct symbolic links for the devices
[Drive x] section in your <filename>~/.wine/config</filename>. (with double colons after the drive letters) in your
<link linkend="config-drive-sections"><filename>dosdevices</filename></link>
directory.
Note that the device has to exist and must be accessible by the user Note that the device has to exist and must be accessible by the user
running Wine if you do this, though. running Wine if you do this, though.
</para> </para>
@ -1651,15 +1562,13 @@ And here is a setup for Drive A, a generic floppy drive:
Here's a simple example of CD-ROM and floppy: Here's a simple example of CD-ROM and floppy:
</para> </para>
<programlisting> <programlisting>
[Drive A] cd ~/.wine/dosdevices
"Path" = "/mnt/floppy"
"Type" = "floppy"
"Device" = "/dev/fd0"
[Drive R] ln -s /mnt/floppy a:
"Path" = "/mnt/cdrom" ln -s /dev/fd0 a::
"Type" = "cdrom"
"Device" = "/dev/hda1" ln -s /mnt/cdrom r:
ln -s /dev/hda1 r::
</programlisting> </programlisting>
</sect3> </sect3>