

TurboIDE
Local-Bus IDE Disk Interface
Manual & Software Driver Users Guide

June 1993


************************************************************************
******                    About TurboIDE:                         ******
************************************************************************

      The TurboIDE card enables implementation of a fully compa-
      tible with the VESA VL-BUS IDE Interface and ISA M/IO
      interface.


************************************************************************
******                 Performance Features                       ******
************************************************************************

      The TurboIDE provides a variety of features to enable high
      performance data transfers.  At the host CPU connection the
      TurboIDE provides 50MHz zero wait-state operation, 32-bit
      data transfers, write-posting, drive data read-ahead, and
      system level concurrency.

      At the drive connection, the TurboIDE generates read and
      write command cycles independently from the host.  Modem IDE
      disk drive can often operate with IOR# and IOW# signals that
      are faster than the ISA bus allows.  The TurboIDE allow pro-
      gramming of the drives command pulse width to timing that is
      optimum for the performance of each drive.  Each of the 2
      possible IDE drives may have different timming, 8-bit cycles
      may be programmed for different timing than the 16-bit data
      cycles, read cycles may be different from write cycles, and
      even the recovery time between command pulses may be controlled.
      This level of configurability means that the TurboIDE has the
      flexibility to meet your needs today and adapt to your future
      requirements too.

      The TurboIDE features system level concurrency during read
      operations from disk as another performance enhancement. Data
      commnication with the host is throgh a buffer. As one double-
      word is read from the buffer, the TurboIDE begins to assemble
      the next double word, without waiting for a host request.
      When the CPU requests the next data it can already be in the
      TurboIDE's internal buffer, ready and waiting for a zero wait-
      state transfer to the CPU. This concurrent pipelined operation
      where it is most important.

      The posted-write capability also supports concurrent system
      operations; while one double-word is being transfered from
      the TurboIDE's internal buffer to the drive at the drive's
      data transfer rate, the CPU can be fetching the next double-
      word from memory.  The data pipeline that is created can
      significantly increase dat through-put.

      System performance of modern hard disk drives is dependant
      upon a number of interrelated factors that can make benchmarks
      difficult to interpret. Parameters such as media data transfer
      rate, host data transfer rate, track-to-track and average seek
      times, rotational latency, read-ahead capability, disk buffer/
      cache size, caching controller cards, and software caching
      techniques each contribute to set the "time to data" access.
      To futher complicate benchmark interpretation many of these
      parameters are variable, and will produce different results
      for sutbly varying setup conditions.

      Older drives, especially those with slow hos data transfer
      rate, no caching or data buffering, and large latencies will
      show little or performance improvement from a TurboIDE local
      bus interface.


************************************************************************
******                      Features                              ******
************************************************************************

      1.  Fully VESA VL-BUS compatible
      2.  IDE Interface to 486DX/DX2 CPU buses
      3.  32 bit host data interface
      4.  0 wait-state 50MHz operation
      5.  Support read-ahead and posted-writes for concurrent
          system operation
      6.  Programmable command ative and recovery times
      7.  Independent timing for 2 IDE drivers
      8.  Support two RS232 ports
      9.  Support one PRINTER port
      10. Support one GAME port
      11. Support 360KB,1.2MB,720KB and 1.44MB floppy disk drivers
      12. Hardware address select and enable/disable for all I/O
          port


************************************************************************
******                  Jumper Setting                            ******
************************************************************************

      1.  IDE Drive Port Configuration: IO, ID1, ID2, IDE

          IO:  IDE IO port address

                   * 1-2:  0 0 B x H         2-3:  0 0 3 x H

          ID2, ID1:  Chipset ID

          Ŀ
            ID2     ID1      Chipset ID     
          Ĵ
            1-2     1-2      30H (default)  
          Ĵ
            1-2     2-3      31H            
          Ĵ
            2-3     1-2      32H            
          Ĵ
            2-3     2-3      33H            
          

          IDE      * 2-3:  Enable            1-2:  Disable

      2.  Parallel Port Configuration :  LPT, LPT2/3

          LPT      * 1-2:  Enable            2-3:  Disable
          LPT2/3   * 1-2:  378-37FH (LPT2)   2-3:  278-27FH (LPT3)

      3.  FDD Port Enable / Disable: FDC

          FDC      * 1-2:  Enable            2-3:  Disable

      4.  GAME Port Enable / Disable: GAME

          GAME     * 1-2:  Enable            2-3:  Disable

      5.  Serial Port #1 Configuration: COM1, COM1/3

          COM1     * 1-2:  Enable            2-3:  Disalbe
          COM1/3   * 1-2:  3F8-3FFH (COM1)   2-3:  3E8-3EFH (COM3)

      6.  Serial Port #2 Configuration: COM2, COM2/4

          COM2     * 1-2:  Enable            2-3:  Disable
          COM2/4   * 1-2:  2F8-2FFH (COM2)   2-3:  2E8-2EFH (COM4)


      * represent factory default


************************************************************************
******           TurboIDE Driver Installation Procedure           ******
************************************************************************

      To install the DOS and Windows 3.1 TurboIDE Disk Accelerator
      driver software from a floppy disk inserted in the A drive:

      Note: Before beginning installation of the TurboIDE software
      it is recommended that you have a bootable DOS floppy system
      diskette available. In the unlikely event of a serious insta-
      llationor operation problem it may be necessary to boot your
      system from the floppy drive and remove oro change the
      CONFIG.SYS file.

      Also, when upgrading to local-bus disk hardware with a disk
      drive already containing important data it is recommended
      that a backup copy of the data be prepared prior to changing
      hardware and installing the drive software.

      Step 1:  Boot your system (floppy not inserted) and verify
               that your hard disk(s) is active (execute a DIR,
               CHKDSK, etc. command to test that the disk is
               active).  Get to a DOS prompt such as C:. Switch
               the system into "turbo mode" if it has this option
               and is not active.  It is recommended that the
               installation-software not be executed while Windows
               or any other shell environment is in operation.

      Step 2:  Insert the TurboIDE driver diskette into the floppy
               drive.  Switch to the A floppy drive by typing:  a:
               <enter>.  Using any text editor, such as MS-DOS 5
               or 6 EDIT, review the README.TXT file for any update
               information. The README.TXT file is in ASCII format,
               includes most of this manual, and may be printed
               under DOS by typing:

                  print readme.txt <enter>

      Step 3:  At the a: prompt type:  install <enter>

      Note:  You may exit the installation procedure at any time
             by typing: Ctrl-C.

      The installation utility will ask a number of simple
      questions and thenautmatically copy the driver file(s) to
      your hard disk. It will configure the disk sub-system for
      optimum performance dependent the system CPU type, speed and
      disk drive type(s). It can also modify your CONFIG.SYS file
      and the Windows 3.1 SYSTEM.INI file file (if Windows 3.1 is
      installed).

      Step 4:  Type Y or N in response to the question:
      "Do you want to install the TurboIDE DOS driver (Y/N)?"

      Typing Y for yes, is confirmation of your intent to install,
      and the installation utility will copy the ADI2c1xx.sys file
      to the C: root directory. Typing N for no, will end the
      installation procedure with no effect to your system or hard
      disk.

      Step 5:  Type Y or N in response to the question:
      "Do you want to install the TurboIDE Windows 3.1 driver
      (Y/N)?"

      Typing Y for yes, will cause the ADI2w1xx.386 Windows
      version 3.1 driver file to be copied into the C:\WINDOWS\
      SYSTEM directory on your hard disk,if this directory exists.
      Typing N for no, will skip the Windows installation procedure
      and all related following questions.  Type N if you are not
      a Windows user, or you use Windows version 3.0, or you want
      to run Windows 3.1 with 16-bit data transfers.

      If the C:WINDOWS\SYSTEM directory cannot be found, you will
      be prompted to supply the Windows directory name:

        "Cannot open C:\WINDOWS\SYSTEM.INI
        Please enter the directory in which Windows is installed
        >>______________

      Type the full path name to the Windows directory, for
      example:

        C:\WIN

      For this example the driver will be copied into the
      C:WIN\SYSTEM directory.

      Step 6:  Type Y or N in response to the question:
      "Do you want to update your CONFIG.SYS file (Y/N)?"

      Typing Y for yes will result in the command device=
      C:ADI2c1xx.sys being added to your C:CONFIG.SYS file. If
      this line already exists from a previous installation the
      old line will be replaced. Typing N for no, will result in
      a file called CONFIG.ADI being added to the C: root
      diretory. CONFIG.ADI can be later renamed to CONFIG.SYS to
      make the TurboIDE driver active.

      Step 7:  Type Y or N in response to the question:
      "Do you want to update your SYSTEM.INI file (Y/N)?"

      Typing Y for yes, will result in the Windows 3.1 SYSTEM.INI
      file being updated for 32-bit TurboIDE disk operation.

      Typing N for No will result in a new file named SYSTEM.ADI
      being added into the C: directory.  This file will contain
      the necessary changes for optimizing Windows disk operation.
      Copying C:\SYSTEM.ADI to C:\WINDOWS\SYSTEM.INI and restarting
      Windows (if Windows was running) will enable the TurboIDE
      optimization. You may want to rename your existing SYSTEM.INI
      file and save it as a backup.

      Last Step:  The TurboIDE driver installation is now complete
      and you will be prompted to reboot the sytem to make the
      changes active. Remove the TurboIDE driver diskette and type
      Y or N in response to the question:
        "Press Y to restart your system now or
         press N to return to DOS. (Y/N)?"

      After restarting your system the TurboIDE driver should
      become active as reported by a screen similar to that shown
      below.  If you experience any problems with installation or
      operation please refer to the section of this user's guide
      titled Troubleshooting.  If changes to your system are made
      later to support a new disk drive or operating environment
      this installation procedure can be repeated at any time.


      __________ Appian Disk Accelerator Device Driver ____________

      Your system uses the Appian ADI/2 Fast IDE Interface Chip

                ADI/2 data port transfers are 32 bits wide
              Hard disk 1 utilizes Multiple MOde data transfers.

              Copyright (c) 1992, 1993, Appian Technology, Inc.

      _________ Successfully initialized, Version 1.xx ___________


************************************************************************
******                   Introdudction                            ******
************************************************************************

      Congratulations on your decision to purchase this product
      which includes the TurboIDE local-bus IDE disk interface. The
      TurboIDE will enhancedisk sub-system performance when used
      with modem IDE disk drives.

      The TurboIDE software supplied on the floppy disk includes a
      DOS driver and installation utility, a Windows 32-bit driver,
      and the update information file as listed below.  Please note
      that the "xx" in the file names below is a two digit number
      representing the software revision, for example; ADI2C100.SYS.

        INSTALL.EXE
        ADI2C1xx.386
        ADI2W1xx.386
        README.TXT

      The software driver is used to enable the high performance
      modes offered by the TurboIDE.  This Users Guide details the
      use of TurboIDE Release 1.0 software drivers.


************************************************************************
******            Software driver Description                     ******
************************************************************************

      The complete TurboIDE DOS driver includes memory resident
      and non-memory resident (in system memory) code sections.
      The non-resident portion configures the TurboIDE registers
      for optimum operation dependent upon your system configu-
      ration and disk drive. The memory resident portion is used
      when operating a disk drive in multiple mode and/or with
      32-bit data transfers enabled.  The complete driver is
      approximately 80Kbytes, while the memory resident portion
      occupies only about 2.4Kbytes of system memory.

************************************************************************
******               DOS 32-bit Driver                            ******
************************************************************************

      The TurboIDE installation routine will add the file
      ADI2C1xx.SYS to into the C:root directory. It may also auto-
      matically add the following command line to your CONFIG.SYS
      file:

          device=c:\ADI2c1xx.sys

      This line will be located at, or near, the end of the
      CONFIG.SYS file.  It should always appear after any memory or
      disk management software command lines.

      When loading, the DOS driver determines the system bus clock
      rate at theTurboIDE IC. This information is used in
      programming the TurboIDE registers.  Some systems vary the
      clock rate between "turbo" and slow operation mode.  The
      system should be switched to "turbo mode" during startup so
      that the TurboIDE software can determine the maximum clock
      rate.  The TurboIDE software will sense clock rates between
      20 and 50 megahertz (MHz).  If a clock rate below 20MHz is
      detected an error message requesting that the system be placed
      in turbo mode is display.


************************************************************************
******         DOS Driver Command Line Switches                   ******
************************************************************************

      The TurboIDE DOS driver provides a number of coommand line
      switches which will alter the automatic default operation.
      Note that these switches are provided for system testing and
      debug and should not be used except by a knowledgeable
      technician.

      The complete format of the command line is:

      device=c:\ADI2c1xx.sys {io16io32}
                     {initonlynoinit} {c=mc=s} {d=md=s}

      Command line options are shown in parentheses { }.  Mutually
      exclusive switch options are divided by the bar .

      The optional switch "io16" will force the driver to only use
      16-bit data transfer cycles with the TurboIDE controller.
      This mode must be used with 16-bit VL-bus systems designed
      around the IBM oor Cyrix 486SLC or 486SLC2 processors. These
      processors feature a 16-bit external data path and connot
      support 32-bit transfers.  The memory resident "multiple"
      mode driver may still be enabled when this switch is used.
      This switch may not be used together with the io32 switch.

      The optional switch "io32" will force the driver to only use
      32-bit data transfer cycles with the TurboIDE controller.
      This mode is the default for most VL-bus systems and is
      recommended for use with all 32-bit CPU based systems such as
      the 486SX, 486DX and 486DX2.  The memory resident 32-bit
      driver will not be enabled when this switch is used.  This
      switch may not be used together with the io16 switch.

      The optional switch "initonly" will force the driver to only
      configure the registers of the TurboIDE IC.  Neither the
      memory resident 32-bit nor multiple mode driver features will
      be installed when this switch is used.  This switch may not
      be used together with the noinit, c= or d= switches.

      The optional switch "noinit" will force the driver to not
      program the TurboIDE timing registers and instead will leave
      them at their power-on setting.  Neither the memory resident
      32-bit nor multiple mode driver features will be installe
      when this switch is used. This switch may not be used together
      with the initonly switch.

      The optional "c=" and "d=" switches allow drive specific
      control of the memory resident driver features.  The "c="
      switch sets parameters for drive 0.  The "d=" switch sets
      parameters for drive 1 (the slave drive in a dual drive confi-
      guration).  The "m" or "s" parameters select multiple mode
      transfers of single mode transfers or single mode transfers
      respectively, for the specified drive.  Note that the "c="
      and "d=" switches may not be used together with the "initonly"
      switch.  The "initonly" switch has precedence and will
      prevent the memory resident driver from being installed and
      the c=/d= switches from being useful.

      Command line parsing requires a space character before each
      switch Additional spaces between switches will be ignored.
      Spaces within  an switch are not allowed, for example; c= s

      Examples of the command line usage are below.  Example "a"
      forces the use of16-bit data transfer cycles.  Example "b"
      will only initialize the the TurboIDE registers, without 32-
      bit or multiple mode memory resident code.  Example "c"
      forces drive 0 into single transfer mode, while example "d"
      forces the master drive to multiple transfers and the slave
      drive to single transfers.

       a.  device=c:\ADI2clxx.sys io16
       b.  device=c:\ADI2c1xx.sys initonly
       c.  device=c:\ADI2c1xx.sys c=s
       d.  device=c:\ADI2c1xx.sys c=m d=s


************************************************************************
******                   Windows 32-bit Driver                    ******
************************************************************************

      The TurboIDE software package includes a 32-bit driver for
      Windows 3.1.  Please note that this driver is NOT suitable
      for use with Windows versins 3.0 and before.

      The installation utility will automatically search for a
      C:\WINDOWS directory with the SYSTEM.INI file.  If this
      directory and/or file cannot be located you are prompted to
      provide a path name to the Windows directory.  The
      ADI2W1xx.386 file will be automatically copied into the
      Windows directory by the installation utility.

      The TurboIDE Installation utility will scan the SYSTEM.INI
      file and make the changes required for the TurboIDE.  In the
      SYSTEM.INI file under the [386Enh] group the command line for
      32 bit disk access will be set to "on", i.e.; 32BitDiskAccess
      =on, and the device driver will be changed by commenting
      "device=*wdctrl" with a preceding semi-colon (;device=*wdctrl)
      and adding the line: "device=ADI2w1xx.386". These changes may
      be added manually with a text editor if the TurboIDE insta-
      llation utility was unable to  find the Windows directory
      and file.  Alternatively these changes can be reversed to
      disable 32-bit operation.  Remember that Windows must be
      restarted for any changes to take effect.

      Note that Windows 3.1 will ONLY operate in 32-bit mode with
      the TurboIDE Windows ddrive installed, if the TurboIDE 32-bit
      DOS memory resident driver is als installed.  The Windows
      supplied 32-bit driver is not compatible with the ADI2C1xx.SYS
      DOS driver.  To restate this another way, with the TurboIDE
      32-bit DOS memory resident driver installed, Windows may only
      be run in its native 16-bit mode unless the TurboIDE Windows
      driver is installed.


************************************************************************
******                   Adding A Disk                            ******
************************************************************************

      Adding a second physical disk drive into your system
      generally requires no effort with respect to the TurboIDE
      driver software.  When loading, the TurboIDE software will
      automatically detect the presence of the new disk drive and
      configure appropriately. Just remember to first set the disk
      jumpers for master slave operation accroding to the disk
      drive manuals, and add the new disk's physical parameters
      into the system BIOS configuration.


************************************************************************
******                  DOS Compatibility                         ******
************************************************************************

      The TurboIDE DOS driver has been tested for compatibility
      with Microsoft DOS versions 3.3 and above, including DOS 6.0.
      In Addition the driver has been tested with Digital Research
      DOS 6.0.


************************************************************************
******             Data Compression Compatibility                 ******
************************************************************************

      The TurboIDE software has been tested to work properly with
      popular data compression software including Stacker (version
      3.0 and 2.0), Superstor and MS DOS 6.0 Doublespace compre-
      ssion.


************************************************************************
******                     Troubleshooting                        ******
************************************************************************

      Extensive testing has been done to insure that the installa-
      tion and doperation of this software is as easy and error
      free as possible. However, the infinite variety of PC
      hardware and software configurations may occasionally produce
      unwanted results.  The following paragraphs should provide
      some assistance if you experience any difficulties.

      Please note that the wording of any of the system error
      messages given below may vary depending upon the system BIOS
      supplier and revision and/or application and revision, and
      therefore may not be exactly as shown.

************************************************************************
      1.  System hangs during start up after software installation.

      Suggested fix a:  The TurboIDE software may not have installed
      properly. Using a system diskette reboot the system. Edit the
      CONFIG.SYS file to verify and the delete the TurboIDE command
      line device=c:\ADI2c1xx.sys.  Then remove the floppy and
      restart the system and reinstall the software.

      Suggested fix b:  This system may only support 16-bit
      operation with a 486SLC or 486SLC2 CPU.  Using a system
      diskette reboot the system.  Edit the CONFIG.SYS file and add
      the io16 switch to the TurboIDE command line so that it reads
      as follows: device= c:\ADI2c1xx.sys io16.  Then remove the
      floppy and restart the system.

      Suggested fix c:  There may be a conflict with an existing
      local bus disk controller. For example, some VL-bus mother-
      boards feature a local bus IDE controller which cannot be
      disabled.  Installing an alternate IDE controller into the
      VL-bus will cause a variety of operation and/or reliability
      problems.  Review the motherboard documentation for a way to
      disable the existing  controller.

      Suggested fix d: The software may have incorrectly identified
      the type of disk drive or system speed resulting in incorrect
      register setting.  Using a system diskette reboot the system.
      Edit the CONFIG.SYS file and add a remark preface to the
      TurboIDE command line so that it reads:
         Rem device=c:\ADI2c1xx.sys

      Remove the floppy and restart the system.  This should verify
      that the basic hardware is functional.  If the system works
      properly then modify the TurboIDE command line in the
      CONFIG.SYS file for the initialization only option so it
      reads:
         device=c:\ADI2c1xx.sys initonly

      Once again reboot the system and verify operation. This
      should improve disk operation for performance.  If the system
      doesn't work, remark the command line as shown previously for
      normal operation.  If the system works properly once again
      edit the TurboIDE command line in the CONFIG.SYS file.  This
      time enable the disks for single mode operation so that the
      command line read:

         device=c:\ADI2c1xx.sys c=s d=s

      Once again reboot the system and verify operation. This should
      again improve disk operation for performance.  If the system
      doesn't work, remark the commandd line as shown previously for
      initialization only operation.  If the system works properly
      you have the optimum software settings.

************************************************************************
      2.  Disk Performance Seems Unchanged After Installation

      Suggested fix:  Verify that the command line device=
      c:\ADI2c1xx.sys appears in the CONFIG.SYS file by typing the
      following command at the DOS C: prompt:

       TYPE CONFIG.SYS  <enter>

      Next, verify that the ADI2C1xx.SYS file is located in the C:
      directory using the DIR <enter> command. If either of these
      items are missing re-install the driver from the floppy as
      described under Installation Procedure.

      TurboIDE software installation must be executed from the
      floppy disk for correct operation.  Simply copying the driver
      from the floppy to the hard disk does not allow the installa-
      tion utility to evaluate your system configuration and set
      the appropriate driver features.

      Also note that significant performance gains will only be
      obtained from modern high performance disk drives.  Older
      slower drives cannot benefit from the local bus connection.

************************************************************************
      3.  System reports "Disk allocation problem" (or equivalent)
      on bootup.

      Suggested fix a:  Boot your system from a floppy disk.  In
      the CONFIG.SYS file move the TurboIDE command line (ex:
      device=c:\ADI2c1xx.sys) after any memory or disk management
      utility commands.

      The TurboIDE driver may conflict with some versions of memory
      and disk management utilities. Typically this type of problem
      is easily solved by changing the order of the commands.  The
      TurboIDE driver installation utility does place the command
      after any recognized memory or disk management commands.

      Suggested fix b:  The physical disk drive parameters as set
      in the BIOS are incorrect.  Please cross-check the disk drive
      parameters against the programmed BIOS values and make any
      necessary corrections.

************************************************************************
      4.  Problems Adding Second Drive

      Suggested fix a:  Verify that the second or new disk drive
      works without the TurboIDE software optimization by removing
      the device=c:\ADI2c1xx.sys command in the CONFIG.SYS file.
      This can be done easily by placing a REM before the command
      with a text editor.  For example:

          REM device=c:\ADI2c1xx.sys

      Both drives should work without the driver active unless
      there is a hardware or system related problem.  Verkfy that
      the physical disk drive parameters as set in the BIOS are
      correct.  Cross-check the disk drive parameters against the
      programmed BIOS values and make any necessary corrections.
      Also, verify that both drives have the correct master-slave
      jumper settings.

      Suggested fix b:  Re-install the TurboIDE software.

      If both drives work together without the TurboIDE driver
      enabled then re-install the TurboIDE software from the floppy
      disk.

************************************************************************
      5.  Windows 3.1 Doesn't Load

      For correct operation the Windows driver requires that the
      DOS Driver be previously loaded.  If during installation the
      SYSTEM.INI file was updated but not the CONFIG.SYS file
      Windows won't load.  Also, if the device=c:\ADI2c1xx.sys
      command in the CONFIG.SYS is later removed or commented out
      the loading of Windows will also  fail.

      Suggested fix a:  Verify that the command line device=
      c:\ADI2c1xx.sys appears in the CONFIG.SYS file by typing the
      following command at the DOS C:prompt:

          TYPE CONFIG.SYS  <enter>

      Next, verify that the ADI2C1xx.SYS file is loacated in the C:
      directory using the DIR <enter> command.  If either of these
      items are missing re-install the driver from the floppy as
      described under Installation Procedure.

      Suggested fix b:  Refer to the section entitled "Widnows 32-
      bit Driver" and verify that the required changes have been
      made to the SYSTEM.INI file.

      If Windows 3.1 will not load after the TurboIDE driver
      software has been installed, but disk performance under DOS
      is good, then the most probable cause is that modification of
      the Windows SYSTEM.INI file was for some reason not completed
      correctly.

      If the changes are correct as described, and Windows still
      doesn't load properly then edit the SYSTEM.INI file and
      reverse the changes to re-enable the standard Windows
      operating mode.

************************************************************************
      6.  Loading Windows Gives "Insufficient Memory" Error

      For correct 32-bit disk operation Windows requires that the
      ADI2W1xx.386 driver be active.  During installation, if for
      some reason the CONFIG.SYS file was updated with the device=
      c:\ADI2c1xx.sys command, but the SYSTEM.INI file wasn't
      updated with the ADI2W1xx.386driver then Windows will report
      this failure.

      Suggested fix a:  Verify that the ADI2W1xx.386 file is located
      in the C:\WINDOWS directory (or alternate) using the DIR
      <enter> command.  Next verify that the command line device=C:\
      ADI2w1xx.386 appears in the windows SYSTEM.INI file in the
      386-enhanced group, together with 32BitDiskAccess=on, as
      explained in the earlier section Windows 32-bit Driver".  If
      either of these items aremissing re-install the TurboIDE
      drivers from the floppy as described under Installation
      Procedure or make the necessary changes with a text editor.

      Suggested fix b:  Windows will operate properly with its
      standard 16-bit driver.  To set this mode change the disk
      access control to off, i.e.; 32BitDiskAccess=off


************************************************************************
******                      Definitions                           ******
************************************************************************

      Drive 0 or 1:  Drive 0 is the boot drive (typically, logical
      drive C) in a single or dual drive configuration.  Drive 1 is
      the slave drive in a dual drive configuration.

      Master Drive:  The boot drive in a dual disk drive configu-
      ration.

      Multiple Mode:  A fast data transfer protocol in which only 1
      CPU interrupt is used for multiple sectors transferred.

      Single Mode:  A data transfer protocol in which a CPU
      interruptis used for each sector (512 bytes) transferred.

      Slave Drive:  The secondary drive (typically, logical drive D
      in a dual dirve system.



      

      Trademarks:  TurboIDE               -  Appian Technology
                   MS-DOS, Windows        -  Microsoft
                   DR-DOS                 -  Digital Research
                   Stacker                -  Stac Electronics
                   Superstor              -  Addstor

      No responsibility is assumed for errors which may appear
      in this document, nor is there any commitment, implied or
      otherwise, update the information contained herein.









