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