documentation/installing.sgml

   1   <chapter id="installing">
   2     <title>Installing/compiling Wine</title>
   3     <para>How to install Wine...</para>
   4
   5     <sect1 id="replace-windows" xreflabel="--Installing Section--">
   6       <title>WWN #52 Feature: Replacing Windows</title>
   7
   8       <para>
   9         Written by &name-ove-kaaven; <email>&email-ove-kaaven;</email>
  10
  11       </para>
  12
  13       <sect2>
  14         <title>Installation Overview</title>
  15
  16         <para>
  17           A Windows installation consists of many different parts.
  18         </para>
  19
  20         <itemizedlist>
  21           <listitem>
  22             <para>
  23               Registry. Many keys are supposed to exist and contain
  24               meaningful data, even in a newly-installed Windows.
  25             </para>
  26           </listitem>
  27           <listitem>
  28             <para>
  29               Directory structure. Applications expect to find and/or
  30               install things in specific predetermined locations. Most
  31               of these directories are expected to exist. But unlike
  32               Unix directory structures, most of these locations are
  33               not hardcoded, and can be queried via the Windows API
  34               and the registry. This places additional requirements on
  35               a Wine installation.
  36             </para>
  37           </listitem>
  38           <listitem>
  39             <para>
  40               System DLLs. In Windows, these usually reside in the
  41               <filename>system</filename> (or
  42               <filename>system32</filename>) directories. Some Windows
  43               applications check for their existence in these
  44               directories before attempting to load them. While Wine
  45               is able to load its own internal DLLs
  46               (<filename>.so</filename> files) when the application
  47               asks for a DLL, Wine does not simulate the existence of
  48               nonexisting files.
  49             </para>
  50           </listitem>
  51         </itemizedlist>
  52
  53         <para>
  54           While the users are of course free to set up everything
  55           themselves, the Wine team will make the automated Wine
  56           installation script, <filename>tools/wineinstall</filename>,
  57           do everything we find necessary to do; running the
  58           conventional <command>configure && make depend && make && make
  59             install</command> cycle is thus not recommended, unless
  60           you know what you're doing. At the moment,
  61           <filename>tools/wineinstall</filename> is able to create a
  62           configuration file, install the registry, and create the
  63           directory structure itself.
  64         </para>
  65       </sect2>
  66
  67       <sect2>
  68         <title>The Registry</title>
  69         <para>
  70           The default registry is in the file
  71           <filename>winedefault.reg</filename>. It contains directory
  72           paths, class IDs, and more; it must be installed before most
  73           <filename>INSTALL.EXE</filename> or
  74           <filename>SETUP.EXE</filename> applications will work. The
  75           registry is covered in more detail in an earlier article.
  76         </para>
  77       </sect2>
  78
  79       <sect2>
  80         <title>Directory Structure</title>
  81         <para>
  82           Here's the fundamental layout that Windows applications and
  83           installers expect. Without it, they seldom operate
  84           correctly.
  85         </para>
  86
  87         <informaltable frame="none">
  88           <tgroup cols="5">
  89             <tbody>
  90               <row>
  91                 <entry>C:\</entry>
  92                 <entry></entry><entry></entry><entry></entry>
  93                 <entry>Root directory of primary disk drive</entry>
  94               </row>
  95               <row>
  96                 <entry></entry>
  97                 <entry>Windows\</entry>
  98                 <entry></entry><entry></entry>
  99                 <entry>Windows directory, containing .INI files, accessories, etc</entry>
 100               </row>
 101               <row>
 102                 <entry></entry><entry></entry>
 103                 <entry valign="middle">System\</entry>
 104                 <entry></entry>
 105                 <entry><literallayout>Win3.x/95/98/ME directory for common DLLs
 106 WinNT/2000 directory for common 16-bit DLLs</literallayout></entry>
 107               </row>
 108               <row>
 109                 <entry></entry><entry></entry>
 110                 <entry>System32\</entry>
 111                 <entry></entry>
 112                 <entry>WinNT/2000 directory for common 32-bit DLLs</entry>
 113               </row>
 114               <row>
 115                 <entry></entry><entry></entry>
 116                 <entry>Start Menu\</entry>
 117                 <entry></entry>
 118                 <entry>Program launcher directory structure</entry>
 119               </row>
 120               <row>
 121                 <entry></entry><entry></entry><entry></entry>
 122                 <entry>Programs\</entry>
 123                 <entry>Program launcher links (.LNK files) to applications</entry>
 124               </row>
 125               <row>
 126                 <entry></entry>
 127                 <entry>Program Files\</entry>
 128                 <entry></entry><entry></entry>
 129                 <entry>Application binaries (.EXE and .DLL files)</entry>
 130               </row>
 131             </tbody>
 132           </tgroup>
 133         </informaltable>
 134
 135         <para>
 136           Wine emulates drives by placing their virtual drive roots to
 137           user-configurable points in the Unix filesystem, so it's
 138           your choice where <medialabel>C:</medialabel>'s root should
 139           be (<filename>tools/wineinstall</filename> will even ask
 140           you). If you choose, say, <filename>/var/wine</filename>, as
 141           the root of your virtual drive <medialabel>C</medialabel>,
 142           then you'd put this in your <filename>wine.conf</filename>:
 143         </para>
 144
 145         <programlisting>
 146 [Drive C]
 147 Path=/var/wine
 148 Type=hd
 149 Label=MS-DOS
 150 Filesystem=win95
 151         </programlisting>
 152
 153         <para>
 154           With this configuration, what windows apps think of as
 155           "c:\windows\system" would map to
 156           <filename>/var/wine/windows/system</filename> in the UNIX
 157           filesystem. Note that you need to specify
 158           <literal>Filesystem=win95</literal>, NOT
 159           <literal>Filesystem=unix</literal>, to make Wine simulate a
 160           Windows-compatible (case-insensitive) filesystem, otherwise
 161           most apps won't work.
 162         </para>
 163       </sect2>
 164
 165       <sect2>
 166         <title>System DLLs</title>
 167         <para>
 168           The Wine team has determined that it is necessary to create
 169           fake DLL files to trick many applications that check for
 170           file existence to determine whether a particular feature
 171           (such as Winsock and its TCP/IP networking) is available. If
 172           this is a problem for you, you can create empty files in the
 173           <filename>system</filename> directory to make the
 174           application think it's there, and Wine's built-in DLL will
 175           be loaded when the application actually asks for it.
 176           (Unfortunately, <filename>tools/wineinstall</filename> does
 177           not create such empty files itself.)
 178         </para>
 179         <para>
 180           Applications sometimes also try to inspect the version
 181           resources from the physical files (for example, to determine
 182           the DirectX version). Empty files will not do in this case,
 183           it is rather necessary to install files with complete
 184           version resources. This problem is currently being worked
 185           on. In the meantime, you may still need to grab some real
 186           DLL files to fool these apps with.
 187         </para>
 188         <para>
 189           And there are of course DLLs that wine does not currently
 190           implement very well (or at all). If you do not have a real
 191           Windows you can steal necessary DLLs from, you can always
 192           get some from a DLL archive such as
 193           <ulink url="http://solo.abac.com/dllarchive/">http://solo.abac.com/dllarchive/</ulink>.
 194         </para>
 195       </sect2>
 196     </sect1>
 197
 198     <sect1 id="no-windows">
 199       <title>Installing Wine Without Windows</title>
 200       <para>
 201         Written by &name-james-juran; <email>&email-james-juran;</email>
 202       </para>
 203       <para>
 204         (Extracted from <filename>wine/documentation/no-windows</filename>)
 205       </para>
 206
 207       <para>
 208         A major goal of Wine is to allow users to run Windows programs
 209         without having to install Windows on their machine. Wine
 210         implements the functionality of the main DLLs usually
 211         provided with Windows. Therefore, once Wine is finished, you
 212         will not need to have windows installed to use Wine.
 213       </para>
 214       <para>
 215         Wine has already made enough progress that it may be possible
 216         to run your target applications without Windows installed. If
 217         you want to try it, follow these steps:
 218       </para>
 219
 220       <orderedlist>
 221         <listitem>
 222           <para>
 223             Create empty <filename>C:\windows</filename>,
 224             <filename>C:\windows\system</filename>,
 225             <filename>C:\windows\Start Menu</filename>, and
 226             <filename>C:\windows\Start Menu\Programs</filename>
 227             directories. Do not point Wine to a
 228             <filename>Windows</filename> directory full of old
 229             installations and a messy registry. (Wine creates a
 230             special registry in your <filename >home</filename>
 231             directory, in <filename>$HOME/.wine/*.reg</filename>.
 232             Perhaps you have to remove these files).
 233           </para>
 234         </listitem>
 235         <listitem>
 236           <para>
 237             Point <medialabel>[Drive C]</medialabel> in
 238             <filename>wine.conf</filename> or
 239             <filename>.winerc</filename> to where you want
 240             <filename>C:</filename> to be. Refer to the Wine man page
 241             for more information. Remember to use
 242             <userinput>filesystem=win95</userinput>!
 243           </para>
 244         </listitem>
 245         <listitem>
 246           <para>
 247             Use <filename>tools/wineinstall</filename> to compile Wine
 248             and install the default registry. Or if you prefer to do
 249             it yourself, compile <filename>programs/regapi</filename>,
 250             and run:   <command>programs/regapi/regapi setValue &lt;
 251             winedefault.reg</command>
 252           </para>
 253         </listitem>
 254         <listitem>
 255           <para>
 256             Run and/or install your applications.
 257           </para>
 258         </listitem>
 259       </orderedlist>
 260
 261       <para>
 262         Because Wine is not yet complete, some programs will work
 263         better with native Windows DLLs than with Wine's
 264         replacements. Wine has been designed to make this possible.
 265         Here are some tips by Juergen Schmied (and others) on how to
 266         proceed. This assumes that your
 267         <filename>C:\windows</filename> directory in the configuration
 268         file does not point to a native Windows installation but is in
 269         a separate Unix file system. (For instance, <quote>C:\windows</quote> is
 270         really subdirectory <quote>windows</quote> located in
 271         <quote>/home/ego/wine/drives/c</quote>).
 272       </para>
 273
 274       <itemizedlist>
 275         <listitem>
 276           <para>
 277             Run the application with <parameter>--debugmsg
 278               +module,+file</parameter> to find out which files are
 279             needed. Copy the required DLLs one by one to the
 280             <filename>C:\windows\system</filename> directory. Do not
 281             copy KERNEL/KERNEL32, GDI/GDI32, or USER/USER32. These
 282             implement the core functionality of the Windows API, and
 283             the Wine internal versions must be used.
 284           </para>
 285         </listitem>
 286         <listitem>
 287           <para>
 288             Edit the <quote>[DllOverrides]</quote> section of
 289             <filename>wine.conf</filename> or
 290             <filename>.winerc</filename> to specify
 291             <quote>native</quote> before <quote>builtin</quote> for
 292             the Windows DLLs you want to use. For more information
 293             about this, see the Wine manpage.
 294           </para>
 295         </listitem>
 296         <listitem>
 297           <para>
 298             Note that some network DLLs are not needed even though
 299             Wine is looking for them. The Windows
 300             <filename>MPR.DLL</filename> currently does not work; you
 301             must use the internal implementation.
 302           </para>
 303         </listitem>
 304         <listitem>
 305           <para>
 306             Copy SHELL/SHELL32 and COMDLG/COMDLG32 COMMCTRL/COMCTL32
 307             only as pairs to your Wine directory (these DLLs are
 308             <quote>clean</quote> to use).  Make sure you have these
 309             specified in the <quote>[DllPairs]</quote> section of
 310             <filename>wine.conf</filename> or .winerc.
 311           </para>
 312         </listitem>
 313         <listitem>
 314           <para>
 315             Be consistent: Use only DLLs from the same Windows version
 316             together.
 317           </para>
 318         </listitem>
 319         <listitem>
 320           <para>
 321             Put <filename>regedit.exe</filename> in the
 322             <filename>C:\windows</filename> directory.
 323             (<application>Office 95</application> imports a
 324             <filename>*.reg</filename> file when it runs with an empty
 325             registry, don't know about
 326             <application>Office 97</application>).
 327           </para>
 328         </listitem>
 329         <listitem>
 330           <para>
 331             Also add <filename>winhelp.exe</filename> and
 332             <filename>winhlp32.exe</filename> if you want to be able
 333             to browse through your programs' help function.
 334           </para>
 335         </listitem>
 336       </itemizedlist>
 337     </sect1>
 338
 339     <sect1 id="vfat">
 340       <title>Dealing With FAT/VFAT Partitions</title>
 341       <para>
 342         Written by &name-steven-elliott; <email>&email-steven-elliott;</email>
 343       </para>
 344       <para>
 345         (Extracted from <filename>wine/documentation/linux-fat-permissions</filename>)
 346       </para>
 347       <para>
 348         This document describes how FAT and
 349         VFAT file system permissions work in Linux
 350         with a focus on configuring them for Wine.
 351       </para>
 352
 353       <sect2>
 354         <title>Introduction</title>
 355         <para>
 356           Linux is able to access DOS and Windows file systems using
 357           either the FAT (older 8.3 DOS filesystems) or VFAT (newer
 358           Windows 95 or later long filename filesystems) modules.
 359           Mounted FAT or VFAT filesystems provide the primary means
 360           for which existing applications and their data are accessed
 361           through Wine for dual boot (Linux + Windows) systems.
 362         </para>
 363         <para>
 364           Wine maps mounted FAT filesystems, such as
 365           <filename>/c</filename>, to driver letters, such as
 366           <quote>c:</quote>, as indicated by the
 367           <filename>wine.conf</filename> file.  The following excerpt
 368           from a <filename>wine.conf</filename> file does this:
 369         </para>
 370         <programlisting>
 371 [Drive C]
 372 Path=/c
 373 Type=hd
 374         </programlisting>
 375         <para>
 376           Although VFAT filesystems are preferable to FAT filesystems
 377           for their long filename support the term <quote>FAT</quote>
 378           will be used throughout the remainder of this document to
 379           refer to FAT filesystems and their derivatives. Also,
 380           <quote>/c</quote> will be used as the FAT mount point in
 381           examples throughout this document.
 382         </para>
 383         <para>
 384           Most modern Linux distributions either detect or allow
 385           existing FAT file systems to be configured so that they can be
 386           mounted, in a location such as <filename>/c</filename>,
 387           either persistently (on bootup) or on an as needed basis. In
 388           either case, by default, the permissions will probably be
 389           configured so that they look like:
 390         </para>
 391         <screen>
 392 <prompt>~></prompt><userinput>cd /c</userinput>
 393 <prompt>/c></prompt><userinput>ls -l</userinput>
 394 <computeroutput>-rwxr-xr-x   1 root     root           91 Oct 10 17:58 autoexec.bat
 395 -rwxr-xr-x   1 root     root          245 Oct 10 17:58 config.sys
 396 drwxr-xr-x  41 root     root        16384 Dec 30  1998 windows</computeroutput>
 397         </screen>
 398         <para>
 399           where all the files are owned by "root", are in the "root"
 400           group and are only writable by "root"
 401           (<literal>755</literal> permissions). This is restrictive in
 402           that it requires that Wine be run as root in order for
 403           applications to be able to write to any part of the
 404           filesystem.
 405         </para>
 406         <para>
 407           There are three major approaches to overcoming the restrictive
 408           permissions mentioned in the previous paragraph:
 409         </para>
 410         <orderedlist>
 411           <listitem>
 412             <para>
 413               Run <application>Wine</application> as root
 414             </para>
 415           </listitem>
 416           <listitem>
 417             <para>
 418               Mount the FAT filesystem with less restrictive
 419               permissions
 420             </para>
 421           </listitem>
 422           <listitem>
 423             <para>
 424               Shadow the FAT filesystem by completely or partially
 425               copying it
 426             </para>
 427           </listitem>
 428         </orderedlist>
 429         <para>
 430           Each approach will be discussed in the following sections.
 431         </para>
 432       </sect2>
 433
 434       <sect2>
 435         <title>Running Wine as root</title>
 436         <para>
 437           Running Wine as root is the easiest and most thorough way of giving
 438           applications that Wine runs unrestricted access to FAT files systems.
 439           Running wine as root also allows applications to do things unrelated
 440           to FAT filesystems, such as listening to ports that are less than
 441           1024.  Running Wine as root is dangerous since there is no limit to
 442           what the application can do to the system.
 443         </para>
 444       </sect2>
 445
 446       <sect2>
 447         <title>Mounting FAT filesystems</title>
 448         <para>
 449           The FAT filesystem can be mounted with permissions less restrictive
 450           than the default.  This can be done by either changing the user that
 451           mounts the FAT filesystem or by explicitly changing the permissions
 452           that the FAT filesystem is mounted with.  The permissions are
 453           inherited from the process that mounts the FAT filesystem.  Since the
 454           process that mounts the FAT filesystem is usually a startup script
 455           running as root the FAT filesystem inherits root's permissions.  This
 456           results in the files on the FAT filesystem having permissions similar
 457           to files created by root.  For example:
 458         </para>
 459         <screen>
 460 <prompt>~></prompt><userinput>whoami</userinput>
 461 <computeroutput>root</computeroutput>
 462 <prompt>~></prompt><userinput>touch root_file</userinput>
 463 <prompt>~></prompt><userinput>ls -l root_file</userinput>
 464 <computeroutput></computeroutput>-rw-r--r--   1 root     root            0 Dec 10 00:20 root_file
 465         </screen>
 466         <para>
 467           which matches the owner, group and permissions of files seen
 468           on the FAT filesystem except for the missing 'x's.  The
 469           permissions on the FAT filesystem can be changed by changing
 470           root's umask (unset permissions bits).  For example:
 471         </para>
 472         <screen>
 473 <prompt>~></prompt><userinput>umount /c</userinput>
 474 <prompt>~></prompt><userinput>umask</userinput>
 475 <computeroutput>022</computeroutput>
 476 <prompt>~></prompt><userinput>umask 073</userinput>
 477 <prompt>~></prompt><userinput>mount /c</userinput>
 478 <prompt>~></prompt><userinput>cd /c</userinput>
 479 <prompt>/c></prompt><userinput>ls -l</userinput>
 480 <computeroutput>-rwx---r--   1 root     root           91 Oct 10 17:58 autoexec.bat
 481 -rwx---r--   1 root     root          245 Oct 10 17:58 config.sys
 482 drwx---r--  41 root     root        16384 Dec 30  1998 windows</computeroutput>
 483         </screen>
 484         <para>
 485           Mounting the FAT filesystem with a umask of
 486           <literal>000</literal> gives all users complete control over
 487           it. Explicitly specifying the permissions of the FAT
 488           filesystem when it is mounted provides additional control.
 489           There are three mount options that are relevant to FAT
 490           permissions: <literal>uid</literal>, <literal>gid</literal>
 491           and <literal>umask</literal>.  They can each be specified
 492           when the filesystem is manually mounted.  For example:
 493         </para>
 494         <screen>
 495 <prompt>~></prompt><userinput>umount /c</userinput>
 496 <prompt>~></prompt><userinput>mount -o uid=500 -o gid=500 -o umask=002 /c</userinput>
 497 <prompt>~></prompt><userinput>cd /c</userinput>
 498 <prompt>/c></prompt><userinput>ls -l</userinput>
 499 <computeroutput>-rwxrwxr-x   1 sle      sle            91 Oct 10 17:58 autoexec.bat
 500 -rwxrwxr-x   1 sle      sle           245 Oct 10 17:58 config.sys
 501 drwxrwxr-x  41 sle      sle         16384 Dec 30  1998 windows</computeroutput>
 502         </screen>
 503         <para>
 504           which gives "sle" complete control over
 505           <filename>/c</filename>.  The options listed above can be
 506           made permanent by adding them to the
 507           <filename>/etc/fstab</filename> file:
 508         </para>
 509         <screen>
 510 <prompt>~></prompt><userinput>grep /c /etc/fstab</userinput>
 511 <computeroutput>/dev/hda1  /c  vfat  uid=500,gid=500,umask=002,exec,dev,suid,rw 1 1</computeroutput>
 512         </screen>
 513         <para>
 514           Note that the umask of <literal>002</literal> is common in
 515           the user private group file permission scheme.  On FAT file
 516           systems this umask assures that all files are fully
 517           accessible by all users in the specified group
 518           (<literal>gid</literal>).
 519         </para>
 520       </sect2>
 521
 522       <sect2>
 523         <title>Shadowing FAT filesystems</title>
 524         <para>
 525           Shadowing provides a finer granularity of control.  Parts of
 526           the original FAT filesystem can be copied so that the
 527           application can safely work with those copied parts while
 528           the application continues to directly read the remaining
 529           parts.  This is done with symbolic links. For example,
 530           consider a system where an application named
 531           <application>AnApp</application> must be able to read and
 532           write to the <filename>c:\windows</filename> and
 533           <filename>c:\AnApp</filename> directories as well as have
 534           read access to the entire FAT filesystem.  On this system
 535           the FAT filesystem has default permissions which should not
 536           be changed for security reasons or can not be changed due to
 537           lack of root access.  On this system a shadow directory
 538           might be set up in the following manner:
 539         </para>
 540         <screen>
 541 <prompt>~></prompt><userinput>cd /</userinput>
 542 <prompt>/></prompt><userinput>mkdir c_shadow</userinput>
 543 <prompt>/></prompt><userinput>cd c_shadow</userinput>
 544 <prompt>/c_shadow></prompt><userinput>ln -s /c_/* .</userinput>
 545 <prompt>/c_shadow></prompt><userinput>rm windows AnApp</userinput>
 546 <prompt>/c_shadow></prompt><userinput>cp -R /c_/{windows,AnApp} .</userinput>
 547 <prompt>/c_shadow></prompt><userinput>chmod -R 777 windows AnApp</userinput>
 548 <prompt>/c_shadow></prompt><userinput>perl -p -i -e 's|/c$|/c_shadow|g' /usr/local/etc/wine.conf</userinput>
 549         </screen>
 550         <para>
 551           The above gives everyone complete read and write access to
 552           the <filename>windows</filename> and
 553           <filename>AnApp</filename> directories while only root has
 554           write access to all other directories.
 555         </para>
 556       </sect2>
 557     </sect1>
 558
 559     <sect1 id="scsi-support">
 560       <title>SCSI Support</title>
 561       <para>
 562         Written by &name-bruce-milner; <email>&email-bruce-milner;</email>;
 563         Additions by &name-andreas-mohr; <email>&email-andreas-mohr;</email>
 564       </para>
 565       <para>
 566         (Extracted from <filename>wine/documentation/aspi</filename>)
 567       </para>
 568
 569       <para>
 570         This file describes setting up the Windows ASPI interface.
 571       </para>
 572
 573       <para>
 574         <warning>
 575           <title>Warning/Warning/Warning!!!!!!</title>
 576           <para>
 577             <screen>
 578 THIS MAY TRASH YOUR SYSTEM IF USED INCORRECTLY
 579 THIS MAY TRASH YOUR SYSTEM IF USED CORRECTLY
 580             </screen>
 581           </para>
 582         </warning>
 583       </para>
 584
 585       <para>
 586         Now that I have said that. ASPI is a direct link to SCSI devices from
 587         windows programs. ASPI just forwards the SCSI commands that programs send
 588         to it to the SCSI bus.
 589       </para>
 590       <para>
 591         If you use the wrong SCSI device in your setup file, you can send
 592         completely bogus commands to the wrong device - An example would be
 593         formatting your hard drives (assuming the device gave you permission -
 594         if you're running as root, all bets are off).
 595       </para>
 596       <para>
 597         So please make sure that <emphasis>all</emphasis> SCSI devices not needed by the program
 598         have their permissions set as restricted as possible !
 599       </para>
 600
 601       <para>
 602         Cookbook for setting up scanner: (At least how mine is to work)
 603         (well, for other devices such as CD burners, MO drives, ..., too)
 604       </para>
 605
 606       <sect2>
 607         <title>Windows requirements</title>
 608         <orderedlist>
 609           <listitem>
 610             <para>
 611               The scanner software needs to use the "Adaptec"
 612               compatible drivers (ASPI). At least with Mustek, they
 613               allow you the choice of using the builtin card or the
 614               "Adaptec (AHA)" compatible drivers. This will not work
 615               any other way. Software that accesses the scanner via a
 616               DOS ASPI driver (e.g. ASPI2DOS) is supported, too. [AM]
 617             </para>
 618           </listitem>
 619           <listitem>
 620             <para>
 621               You probably need a real windows install of the software
 622               to set the LUN's/SCSI id's up correctly. I'm not exactly
 623               sure.
 624             </para>
 625           </listitem>
 626         </orderedlist>
 627       </sect2>
 628
 629       <sect2>
 630         <title>LINUX requirements:</title>
 631         <orderedlist>
 632           <listitem>
 633             <para>
 634               Your SCSI card must be supported under linux. This will
 635               not work with an unknown SCSI card. Even for cheap'n
 636               crappy "scanner only" controllers some special Linux
 637               drivers exist on the net.
 638               If you intend to use your IDE device, you need to use the
 639               ide-scsi emulation.
 640               Read
 641               <ulink url="http://www.linuxdoc.org/HOWTO/CD-Writing-HOWTO.html">
 642                           http://www.linuxdoc.org/HOWTO/CD-Writing-HOWTO.html</ulink>
 643               for ide-scsi setup instructions.
 644             </para>
 645           </listitem>
 646           <listitem>
 647             <para>
 648               Compile generic SCSI drivers into your kernel.
 649             </para>
 650           </listitem>
 651           <listitem>
 652             <para>
 653               This seems to be not required any more for newer (2.2.x) kernels:
 654               Linux by default uses smaller SCSI buffers than Windows.
 655               There is a kernel build define <literal>SG_BIG_BUFF</literal> (in
 656               <filename>sg.h</filename>) that is by default set too
 657               low. The SANE project recommends
 658               <literal>130560</literal> and this seems to work just
 659               fine. This does require a kernel rebuild.
 660             </para>
 661           </listitem>
 662           <listitem>
 663             <para>
 664               Make the devices for the scanner (generic SCSI devices)
 665               - look at the SCSI programming HOWTO at
 666               <ulink url="http://www.linuxdoc.org/HOWTO/SCSI-Programming-HOWTO.html">
 667                           http://www.linuxdoc.org/HOWTO/SCSI-Programming-HOWTO.html</ulink>
 668               for device numbering.
 669             </para>
 670           </listitem>
 671           <listitem>
 672             <para>
 673               I would recommend making the scanner device writable by
 674               a group. I made a group called
 675               <literal>scanner</literal> and added myself to it.
 676               Running as root increases your risk of sending bad SCSI
 677               commands to the wrong device. With a regular user, you
 678               are better protected.
 679             </para>
 680           </listitem>
 681           <listitem>
 682             <para>
 683               For Win32 software (WNASPI32), Wine has auto-detection in place.
 684               For Win16 software (WINASPI), you need to add a SCSI device entry
 685               for your particular scanner to wine.conf. The format is
 686               <literal>[scsi cCtTdD]</literal> where
 687               <literal>C=controller</literal>,
 688               <literal>T=target</literal>, <literal>D=LUN</literal>
 689             </para>
 690             <para>
 691               For example, I set mine up as  controller <literal>0</literal>,
 692               Target <literal>6</literal>, LUN <literal>0</literal>.
 693               <programlisting>
 694 [scsi c0t6d0]
 695 Device=/dev/sgi
 696               </programlisting>
 697               Yours will vary with your particular SCSI setup.
 698             </para>
 699           </listitem>
 700         </orderedlist>
 701       </sect2>
 702
 703       <sect2>
 704         <title>General Information</title>
 705         <para>
 706           The mustek scanner I have was shipped with a package
 707           "ipplus". This program uses the TWAIN driver specification
 708           to access scanners.
 709         </para>
 710         <para>
 711           (TWAIN MANAGER)
 712         </para>
 713         <para>
 714           <programlisting>
 715 ipplus.exe &lt;---> (TWAIN INTERFACE) &lt;---> (TWAIN DATA SOURCE . ASPI) -> WINASPI
 716           </programlisting>
 717         </para>
 718       </sect2>
 719
 720       <sect2>
 721         <title>NOTES/BUGS</title>
 722         <para>
 723           The biggest is that it only works under linux at the moment.
 724         </para>
 725         <para>
 726           The ASPI code has only been tested with:
 727         </para>
 728         <itemizedlist>
 729           <listitem>
 730             <para>
 731               a Mustek 800SP with a Buslogic controller under Linux [BM]
 732             </para>
 733           </listitem>
 734           <listitem>
 735             <para>
 736               a Siemens Nixdorf 9036 with Adaptec AVA-1505 under Linux
 737               accessed via DOSASPI. Note that I had color problems,
 738               though (barely readable result) [AM]
 739             </para>
 740           </listitem>
 741           <listitem>
 742             <para>
 743               a Fujitsu M2513A MO drive (640MB) using generic SCSI
 744               drivers. Formatting and ejecting worked perfectly.
 745               Thanks to Uwe Bonnes for access to the hardware ! [AM]
 746             </para>
 747           </listitem>
 748         </itemizedlist>
 749         <para>
 750           I make no warranty to the ASPI code. It makes my scanner
 751           work. Your devices may explode. I have no way of determining
 752           this. I take zero responsibility!
 753         </para>
 754       </sect2>
 755     </sect1>
 756
 757 </chapter>
 758
 759 <!-- Keep this comment at the end of the file
 760 Local variables:
 761 mode: sgml
 762 sgml-parent-document:("wine-doc.sgml" "set" "book" "chapter" "")
 763 End:
 764 -->