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/config</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/config</filename> to where you want
 239             <filename>C:</filename> to be. Refer to the Wine man page
 240             for more information. Remember to use
 241             <userinput>"Filesystem" = "win95"</userinput>!
 242           </para>
 243         </listitem>
 244         <listitem>
 245           <para>
 246             Use <filename>tools/wineinstall</filename> to compile Wine
 247             and install the default registry. Or if you prefer to do
 248             it yourself, compile <filename>programs/regapi</filename>,
 249             and run:   <command>programs/regapi/regapi setValue &lt;
 250             winedefault.reg</command>
 251           </para>
 252         </listitem>
 253         <listitem>
 254           <para>
 255             Run and/or install your applications.
 256           </para>
 257         </listitem>
 258       </orderedlist>
 259
 260       <para>
 261         Because Wine is not yet complete, some programs will work
 262         better with native Windows DLLs than with Wine's
 263         replacements. Wine has been designed to make this possible.
 264         Here are some tips by Juergen Schmied (and others) on how to
 265         proceed. This assumes that your
 266         <filename>C:\windows</filename> directory in the configuration
 267         file does not point to a native Windows installation but is in
 268         a separate Unix file system. (For instance, <quote>C:\windows</quote> is
 269         really subdirectory <quote>windows</quote> located in
 270         <quote>/home/ego/wine/drives/c</quote>).
 271       </para>
 272
 273       <itemizedlist>
 274         <listitem>
 275           <para>
 276             Run the application with <parameter>--debugmsg
 277               +module,+file</parameter> to find out which files are
 278             needed. Copy the required DLLs one by one to the
 279             <filename>C:\windows\system</filename> directory. Do not
 280             copy KERNEL/KERNEL32, GDI/GDI32, or USER/USER32. These
 281             implement the core functionality of the Windows API, and
 282             the Wine internal versions must be used.
 283           </para>
 284         </listitem>
 285         <listitem>
 286           <para>
 287             Edit the <quote>[DllOverrides]</quote> section of
 288             <filename>~/.wine/config</filename> to specify
 289             <quote>native</quote> before <quote>builtin</quote> for
 290             the Windows DLLs you want to use. For more information
 291             about this, see the Wine manpage.
 292           </para>
 293         </listitem>
 294         <listitem>
 295           <para>
 296             Note that some network DLLs are not needed even though
 297             Wine is looking for them. The Windows
 298             <filename>MPR.DLL</filename> currently does not work; you
 299             must use the internal implementation.
 300           </para>
 301         </listitem>
 302         <listitem>
 303           <para>
 304             Copy SHELL/SHELL32 and COMDLG/COMDLG32 COMMCTRL/COMCTL32
 305             only as pairs to your Wine directory (these DLLs are
 306             <quote>clean</quote> to use).  Make sure you have these
 307             specified in the <quote>[DllPairs]</quote> section of
 308             <filename>~/.wine/config</filename>.
 309           </para>
 310         </listitem>
 311         <listitem>
 312           <para>
 313             Be consistent: Use only DLLs from the same Windows version
 314             together.
 315           </para>
 316         </listitem>
 317         <listitem>
 318           <para>
 319             Put <filename>regedit.exe</filename> in the
 320             <filename>C:\windows</filename> directory.
 321             (<application>Office 95</application> imports a
 322             <filename>*.reg</filename> file when it runs with an empty
 323             registry, don't know about
 324             <application>Office 97</application>).
 325           </para>
 326         </listitem>
 327         <listitem>
 328           <para>
 329             Also add <filename>winhelp.exe</filename> and
 330             <filename>winhlp32.exe</filename> if you want to be able
 331             to browse through your programs' help function.
 332           </para>
 333         </listitem>
 334       </itemizedlist>
 335     </sect1>
 336
 337     <sect1 id="vfat">
 338       <title>Dealing With FAT/VFAT Partitions</title>
 339       <para>
 340         Written by &name-steven-elliott; <email>&email-steven-elliott;</email>
 341       </para>
 342       <para>
 343         (Extracted from <filename>wine/documentation/linux-fat-permissions</filename>)
 344       </para>
 345       <para>
 346         This document describes how FAT and
 347         VFAT file system permissions work in Linux
 348         with a focus on configuring them for Wine.
 349       </para>
 350
 351       <sect2>
 352         <title>Introduction</title>
 353         <para>
 354           Linux is able to access DOS and Windows file systems using
 355           either the FAT (older 8.3 DOS filesystems) or VFAT (newer
 356           Windows 95 or later long filename filesystems) modules.
 357           Mounted FAT or VFAT filesystems provide the primary means
 358           for which existing applications and their data are accessed
 359           through Wine for dual boot (Linux + Windows) systems.
 360         </para>
 361         <para>
 362           Wine maps mounted FAT filesystems, such as
 363           <filename>/c</filename>, to driver letters, such as
 364           <quote>c:</quote>, as indicated by the
 365           <filename>~/.wine/config</filename> file.  The following excerpt
 366           from a <filename>~/.wine/config</filename> file does this:
 367         </para>
 368         <programlisting>
 369 [Drive C]
 370 "Path" = "/c"
 371 "Type" = "hd"
 372         </programlisting>
 373         <para>
 374           Although VFAT filesystems are preferable to FAT filesystems
 375           for their long filename support the term <quote>FAT</quote>
 376           will be used throughout the remainder of this document to
 377           refer to FAT filesystems and their derivatives. Also,
 378           <quote>/c</quote> will be used as the FAT mount point in
 379           examples throughout this document.
 380         </para>
 381         <para>
 382           Most modern Linux distributions either detect or allow
 383           existing FAT file systems to be configured so that they can be
 384           mounted, in a location such as <filename>/c</filename>,
 385           either persistently (on bootup) or on an as needed basis. In
 386           either case, by default, the permissions will probably be
 387           configured so that they look like:
 388         </para>
 389         <screen>
 390 <prompt>~></prompt><userinput>cd /c</userinput>
 391 <prompt>/c></prompt><userinput>ls -l</userinput>
 392 <computeroutput>-rwxr-xr-x   1 root     root           91 Oct 10 17:58 autoexec.bat
 393 -rwxr-xr-x   1 root     root          245 Oct 10 17:58 config.sys
 394 drwxr-xr-x  41 root     root        16384 Dec 30  1998 windows</computeroutput>
 395         </screen>
 396         <para>
 397           where all the files are owned by "root", are in the "root"
 398           group and are only writable by "root"
 399           (<literal>755</literal> permissions). This is restrictive in
 400           that it requires that Wine be run as root in order for
 401           applications to be able to write to any part of the
 402           filesystem.
 403         </para>
 404         <para>
 405           There are three major approaches to overcoming the restrictive
 406           permissions mentioned in the previous paragraph:
 407         </para>
 408         <orderedlist>
 409           <listitem>
 410             <para>
 411               Run <application>Wine</application> as root
 412             </para>
 413           </listitem>
 414           <listitem>
 415             <para>
 416               Mount the FAT filesystem with less restrictive
 417               permissions
 418             </para>
 419           </listitem>
 420           <listitem>
 421             <para>
 422               Shadow the FAT filesystem by completely or partially
 423               copying it
 424             </para>
 425           </listitem>
 426         </orderedlist>
 427         <para>
 428           Each approach will be discussed in the following sections.
 429         </para>
 430       </sect2>
 431
 432       <sect2>
 433         <title>Running Wine as root</title>
 434         <para>
 435           Running Wine as root is the easiest and most thorough way of giving
 436           applications that Wine runs unrestricted access to FAT files systems.
 437           Running wine as root also allows applications to do things unrelated
 438           to FAT filesystems, such as listening to ports that are less than
 439           1024.  Running Wine as root is dangerous since there is no limit to
 440           what the application can do to the system.
 441         </para>
 442       </sect2>
 443
 444       <sect2>
 445         <title>Mounting FAT filesystems</title>
 446         <para>
 447           The FAT filesystem can be mounted with permissions less restrictive
 448           than the default.  This can be done by either changing the user that
 449           mounts the FAT filesystem or by explicitly changing the permissions
 450           that the FAT filesystem is mounted with.  The permissions are
 451           inherited from the process that mounts the FAT filesystem.  Since the
 452           process that mounts the FAT filesystem is usually a startup script
 453           running as root the FAT filesystem inherits root's permissions.  This
 454           results in the files on the FAT filesystem having permissions similar
 455           to files created by root.  For example:
 456         </para>
 457         <screen>
 458 <prompt>~></prompt><userinput>whoami</userinput>
 459 <computeroutput>root</computeroutput>
 460 <prompt>~></prompt><userinput>touch root_file</userinput>
 461 <prompt>~></prompt><userinput>ls -l root_file</userinput>
 462 <computeroutput></computeroutput>-rw-r--r--   1 root     root            0 Dec 10 00:20 root_file
 463         </screen>
 464         <para>
 465           which matches the owner, group and permissions of files seen
 466           on the FAT filesystem except for the missing 'x's.  The
 467           permissions on the FAT filesystem can be changed by changing
 468           root's umask (unset permissions bits).  For example:
 469         </para>
 470         <screen>
 471 <prompt>~></prompt><userinput>umount /c</userinput>
 472 <prompt>~></prompt><userinput>umask</userinput>
 473 <computeroutput>022</computeroutput>
 474 <prompt>~></prompt><userinput>umask 073</userinput>
 475 <prompt>~></prompt><userinput>mount /c</userinput>
 476 <prompt>~></prompt><userinput>cd /c</userinput>
 477 <prompt>/c></prompt><userinput>ls -l</userinput>
 478 <computeroutput>-rwx---r--   1 root     root           91 Oct 10 17:58 autoexec.bat
 479 -rwx---r--   1 root     root          245 Oct 10 17:58 config.sys
 480 drwx---r--  41 root     root        16384 Dec 30  1998 windows</computeroutput>
 481         </screen>
 482         <para>
 483           Mounting the FAT filesystem with a umask of
 484           <literal>000</literal> gives all users complete control over
 485           it. Explicitly specifying the permissions of the FAT
 486           filesystem when it is mounted provides additional control.
 487           There are three mount options that are relevant to FAT
 488           permissions: <literal>uid</literal>, <literal>gid</literal>
 489           and <literal>umask</literal>.  They can each be specified
 490           when the filesystem is manually mounted.  For example:
 491         </para>
 492         <screen>
 493 <prompt>~></prompt><userinput>umount /c</userinput>
 494 <prompt>~></prompt><userinput>mount -o uid=500 -o gid=500 -o umask=002 /c</userinput>
 495 <prompt>~></prompt><userinput>cd /c</userinput>
 496 <prompt>/c></prompt><userinput>ls -l</userinput>
 497 <computeroutput>-rwxrwxr-x   1 sle      sle            91 Oct 10 17:58 autoexec.bat
 498 -rwxrwxr-x   1 sle      sle           245 Oct 10 17:58 config.sys
 499 drwxrwxr-x  41 sle      sle         16384 Dec 30  1998 windows</computeroutput>
 500         </screen>
 501         <para>
 502           which gives "sle" complete control over
 503           <filename>/c</filename>.  The options listed above can be
 504           made permanent by adding them to the
 505           <filename>/etc/fstab</filename> file:
 506         </para>
 507         <screen>
 508 <prompt>~></prompt><userinput>grep /c /etc/fstab</userinput>
 509 <computeroutput>/dev/hda1  /c  vfat  uid=500,gid=500,umask=002,exec,dev,suid,rw 1 1</computeroutput>
 510         </screen>
 511         <para>
 512           Note that the umask of <literal>002</literal> is common in
 513           the user private group file permission scheme.  On FAT file
 514           systems this umask assures that all files are fully
 515           accessible by all users in the specified group
 516           (<literal>gid</literal>).
 517         </para>
 518       </sect2>
 519
 520       <sect2>
 521         <title>Shadowing FAT filesystems</title>
 522         <para>
 523           Shadowing provides a finer granularity of control.  Parts of
 524           the original FAT filesystem can be copied so that the
 525           application can safely work with those copied parts while
 526           the application continues to directly read the remaining
 527           parts.  This is done with symbolic links. For example,
 528           consider a system where an application named
 529           <application>AnApp</application> must be able to read and
 530           write to the <filename>c:\windows</filename> and
 531           <filename>c:\AnApp</filename> directories as well as have
 532           read access to the entire FAT filesystem.  On this system
 533           the FAT filesystem has default permissions which should not
 534           be changed for security reasons or can not be changed due to
 535           lack of root access.  On this system a shadow directory
 536           might be set up in the following manner:
 537         </para>
 538         <screen>
 539 <prompt>~></prompt><userinput>cd /</userinput>
 540 <prompt>/></prompt><userinput>mkdir c_shadow</userinput>
 541 <prompt>/></prompt><userinput>cd c_shadow</userinput>
 542 <prompt>/c_shadow></prompt><userinput>ln -s /c_/* .</userinput>
 543 <prompt>/c_shadow></prompt><userinput>rm windows AnApp</userinput>
 544 <prompt>/c_shadow></prompt><userinput>cp -R /c_/{windows,AnApp} .</userinput>
 545 <prompt>/c_shadow></prompt><userinput>chmod -R 777 windows AnApp</userinput>
 546 <prompt>/c_shadow></prompt><userinput>perl -p -i -e 's|/c$|/c_shadow|g' /usr/local/etc/wine.conf</userinput>
 547         </screen>
 548         <para>
 549           The above gives everyone complete read and write access to
 550           the <filename>windows</filename> and
 551           <filename>AnApp</filename> directories while only root has
 552           write access to all other directories.
 553         </para>
 554       </sect2>
 555     </sect1>
 556
 557     <sect1 id="scsi-support">
 558       <title>SCSI Support</title>
 559       <para>
 560         Written by &name-bruce-milner; <email>&email-bruce-milner;</email>;
 561         Additions by &name-andreas-mohr; <email>&email-andreas-mohr;</email>
 562       </para>
 563       <para>
 564         (Extracted from <filename>wine/documentation/aspi</filename>)
 565       </para>
 566
 567       <para>
 568         This file describes setting up the Windows ASPI interface.
 569       </para>
 570
 571       <para>
 572         <warning>
 573           <title>Warning/Warning/Warning!!!!!!</title>
 574           <para>
 575             <screen>
 576 THIS MAY TRASH YOUR SYSTEM IF USED INCORRECTLY
 577 THIS MAY TRASH YOUR SYSTEM IF USED CORRECTLY
 578             </screen>
 579           </para>
 580         </warning>
 581       </para>
 582
 583       <para>
 584         Now that I have said that. ASPI is a direct link to SCSI devices from
 585         windows programs. ASPI just forwards the SCSI commands that programs send
 586         to it to the SCSI bus.
 587       </para>
 588       <para>
 589         If you use the wrong SCSI device in your setup file, you can send
 590         completely bogus commands to the wrong device - An example would be
 591         formatting your hard drives (assuming the device gave you permission -
 592         if you're running as root, all bets are off).
 593       </para>
 594       <para>
 595         So please make sure that <emphasis>all</emphasis> SCSI devices not needed by the program
 596         have their permissions set as restricted as possible !
 597       </para>
 598
 599       <para>
 600         Cookbook for setting up scanner: (At least how mine is to work)
 601         (well, for other devices such as CD burners, MO drives, ..., too)
 602       </para>
 603
 604       <sect2>
 605         <title>Windows requirements</title>
 606         <orderedlist>
 607           <listitem>
 608             <para>
 609               The scanner software needs to use the "Adaptec"
 610               compatible drivers (ASPI). At least with Mustek, they
 611               allow you the choice of using the builtin card or the
 612               "Adaptec (AHA)" compatible drivers. This will not work
 613               any other way. Software that accesses the scanner via a
 614               DOS ASPI driver (e.g. ASPI2DOS) is supported, too. [AM]
 615             </para>
 616           </listitem>
 617           <listitem>
 618             <para>
 619               You probably need a real windows install of the software
 620               to set the LUN's/SCSI id's up correctly. I'm not exactly
 621               sure.
 622             </para>
 623           </listitem>
 624         </orderedlist>
 625       </sect2>
 626
 627       <sect2>
 628         <title>LINUX requirements:</title>
 629         <orderedlist>
 630           <listitem>
 631             <para>
 632               Your SCSI card must be supported under linux. This will
 633               not work with an unknown SCSI card. Even for cheap'n
 634               crappy "scanner only" controllers some special Linux
 635               drivers exist on the net.
 636               If you intend to use your IDE device, you need to use the
 637               ide-scsi emulation.
 638               Read
 639               <ulink url="http://www.linuxdoc.org/HOWTO/CD-Writing-HOWTO.html">
 640                           http://www.linuxdoc.org/HOWTO/CD-Writing-HOWTO.html</ulink>
 641               for ide-scsi setup instructions.
 642             </para>
 643           </listitem>
 644           <listitem>
 645             <para>
 646               Compile generic SCSI drivers into your kernel.
 647             </para>
 648           </listitem>
 649           <listitem>
 650             <para>
 651               This seems to be not required any more for newer (2.2.x) kernels:
 652               Linux by default uses smaller SCSI buffers than Windows.
 653               There is a kernel build define <literal>SG_BIG_BUFF</literal> (in
 654               <filename>sg.h</filename>) that is by default set too
 655               low. The SANE project recommends
 656               <literal>130560</literal> and this seems to work just
 657               fine. This does require a kernel rebuild.
 658             </para>
 659           </listitem>
 660           <listitem>
 661             <para>
 662               Make the devices for the scanner (generic SCSI devices)
 663               - look at the SCSI programming HOWTO at
 664               <ulink url="http://www.linuxdoc.org/HOWTO/SCSI-Programming-HOWTO.html">
 665                           http://www.linuxdoc.org/HOWTO/SCSI-Programming-HOWTO.html</ulink>
 666               for device numbering.
 667             </para>
 668           </listitem>
 669           <listitem>
 670             <para>
 671               I would recommend making the scanner device writable by
 672               a group. I made a group called
 673               <literal>scanner</literal> and added myself to it.
 674               Running as root increases your risk of sending bad SCSI
 675               commands to the wrong device. With a regular user, you
 676               are better protected.
 677             </para>
 678           </listitem>
 679           <listitem>
 680             <para>
 681               For Win32 software (WNASPI32), Wine has auto-detection in place.
 682               For Win16 software (WINASPI), you need to add a SCSI device entry
 683               for your particular scanner to ~/.wine/config. The format is
 684               <literal>[scsi cCtTdD]</literal> where
 685               <literal>"C" = "controller"</literal>,
 686               <literal>"T" = "target"</literal>, <literal>D=LUN</literal>
 687             </para>
 688             <para>
 689               For example, I set mine up as  controller <literal>0</literal>,
 690               Target <literal>6</literal>, LUN <literal>0</literal>.
 691               <programlisting>
 692 [scsi c0t6d0]
 693 "Device" = "/dev/sgi"
 694               </programlisting>
 695               Yours will vary with your particular SCSI setup.
 696             </para>
 697           </listitem>
 698         </orderedlist>
 699       </sect2>
 700
 701       <sect2>
 702         <title>General Information</title>
 703         <para>
 704           The mustek scanner I have was shipped with a package
 705           "ipplus". This program uses the TWAIN driver specification
 706           to access scanners.
 707         </para>
 708         <para>
 709           (TWAIN MANAGER)
 710         </para>
 711         <para>
 712           <programlisting>
 713 ipplus.exe &lt;---> (TWAIN INTERFACE) &lt;---> (TWAIN DATA SOURCE . ASPI) -> WINASPI
 714           </programlisting>
 715         </para>
 716       </sect2>
 717
 718       <sect2>
 719         <title>NOTES/BUGS</title>
 720         <para>
 721           The biggest is that it only works under linux at the moment.
 722         </para>
 723         <para>
 724           The ASPI code has only been tested with:
 725         </para>
 726         <itemizedlist>
 727           <listitem>
 728             <para>
 729               a Mustek 800SP with a Buslogic controller under Linux [BM]
 730             </para>
 731           </listitem>
 732           <listitem>
 733             <para>
 734               a Siemens Nixdorf 9036 with Adaptec AVA-1505 under Linux
 735               accessed via DOSASPI. Note that I had color problems,
 736               though (barely readable result) [AM]
 737             </para>
 738           </listitem>
 739           <listitem>
 740             <para>
 741               a Fujitsu M2513A MO drive (640MB) using generic SCSI
 742               drivers. Formatting and ejecting worked perfectly.
 743               Thanks to Uwe Bonnes for access to the hardware ! [AM]
 744             </para>
 745           </listitem>
 746         </itemizedlist>
 747         <para>
 748           I make no warranty to the ASPI code. It makes my scanner
 749           work. Your devices may explode. I have no way of determining
 750           this. I take zero responsibility!
 751         </para>
 752       </sect2>
 753     </sect1>
 754
 755 </chapter>
 756
 757 <!-- Keep this comment at the end of the file
 758 Local variables:
 759 mode: sgml
 760 sgml-parent-document:("wine-doc.sgml" "set" "book" "chapter" "")
 761 End:
 762 -->