The Appian ADI/2 Fast (Local Bus) IDE Interface Chip,
the enabling drivers for the chip for MS-DOS, MS-Windows, and OS/2,
the documentation files, readme files, historical notes and version lists,
and representation of screen shots produced by invocation of said drviers
is all copyright Appian Technology, Inc. and Cirrus Logic, Inc.

All other products are copyright of their respective owners.


This is an all inclusive ad-hoc discourse on the ADI2 Local-Bus IDE 
Interface chip and associated drivers.  The intent of this file is to 
provide tips and hints for the use and tweaking of the ADI2 interface 
controller.  I am not associated with Appian or CL. But these drivers 
implement a nice performance improvement in my existing system.  I can 
answer some questions, but I'm only an end user.


DISCLAIMER: All of this information is based on personal experience, and
is not warranted by me for any reason at all whatsoever.  Good Luck.  
Make sure your data is backed up.  If something blows up, ce la vie.

Table of Contents:

     All Operating Systems

     MS-DOS
	   Current Driver
	   During Installation
	   Tweaks

     MS-Windows
	       Current Driver
	       During Installation

     OS/2
	 STRONG ADVICE
	 Preparation
	 During Installation
	 Tweaks

     What Happened to Appian Technology, Inc.

     Do You Have An ADI2 EIDE Interface Chip In Your Computer ?

     Points of Contact


Here are a few tips on the files.

|

All Operating Systems :

  Before you begin working with the adi2abbb.ccc drivers:

     FULLY BACK UP DATA YOU DON'T WANT TO LOSE.  Yes, these drivers were
     written by corporations that develop chips for a living, but your 
     system may be the rare one that has a problem.  I've seen too many
     emailed comments about lost files and munged disks to say it never
     happens.

     Fully understand the capabilities of your disks.  Many older disks
     will not provide Multiple Mode Data Transfer capabilities, support 
     Logical Block Addressing Mode, or EIDE Mode 3 protocals.  If either
     of these options are not supported, DON'T FORCE IT.

  To energize 32-bit fast data modes, you may need to go into the BIOS
  setup and change the Hard Disk Timing (or the equivalent) from 
  Compatible (or similar) to Fast (or similar).  However, I haven't done
  any timing tests to verify whether or not this makes any difference.

  The screen shot during boot up will show the BIOS has been configured:

	    ADI2 Local Bus Disk Interface Initialized for 33 MHz
	     Setup code (c) 1992,1993  Appian Technology, Inc.

|

MS-DOS :

  Current driver     ADI2C149 SYS        25,316 10-14-94   4:32p

During installation:

  Always use the /V parameter. 
  Watch the banner to see what has been invoked.
  Read the DOSPARM.TXT file to see what your options are.

Tweaks:

  DO NO ATTEMPT to load this driver with a DEVICEHIGH=  in config.sys.
  
  If you are using memmaker, you will have to select a Custom Install,
  and Specify which drivers and TSRs to include in Optimization - YES,
  and when device=adi2c149.sys /V 
       Include this driver or program in the optimization process - NO !

  Watch the boot sequence to verify proper loading. A full banner is:

      IMMMMMMMMMMMM  Appian Disk Accelerator Device Driver  MMMMMMMMM;
      GDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD6
      :   Your system uses the APPIAN ADI2 Fast IDE Interface Chip   :
      :           ADI2 Data Port Transfers are 32 bits wide          :
      :                Measured system speed is 33 MHz               :
      :                                                              :
      :   Hard disk 1 and 2 utilize MULTIPLE MODE DATA TRANSFERS     :
      :               Hard disk 1 uses MODE 3 protocol               :
      :               Hard disk 2 uses MODE 3 protocol               :
      :          Hard disks 1 and 2 using Logical Block Mode         :      
      :                                                              :
      :         Copyright (C) 1992,93,94 Appian Technology           :
      GDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD6
      HMMMMM Successfully Initialized  Ver 1.49 MMMMMM DT: 10/13/94 M<


  You will find that other disk handlers may interfere with this driver.
  This includes Disk Manager, Drive Rocket, and any device driver which
  is hooking int13h.  You may also find that a windows disk accelerator
  may be confused by the ADI2C149.SYS. 

  Be sure that you thoroughly read the available information.

  Use the ALT_IDE=ON if you have more than one disk controller, EITHER 
  IDE or SCSI.  It seemed to help my system.

  I have found the driver does enhance performance with Western Digital 
  AC2540 disks, which are supposedly EIDE. Your mileage may vary.

|

Windows:

  Current driver     ADI2W107 386        16,244 10-18-94  10:28a

During installation:

  There isn't any real indication that the driver has been loaded.
  It will work with WFWG , including 32-bit disk and 32-bit file access.

  The install WILL comment out some other lines.  Enableing 32-bit disk 
  access does seem to substantially increase benchmark data.

  You may wish to experiment with some of the EIDE drivers for Windows
  now being developed by Western Digital, Seagate, etc. For example,
  for Western Digital drives, you may wish to try the Win31 EIDE device 
  driver, win31.exe. It installs like any other application, and has some  
  nice graphics.  Other names for these drviers are FastDisk, etc.
  Lots of information is provided at initialization. HOWEVER, it will NOT 
  run if you have loaded the adi2cxxx.sys driver at boot. 
  No doubt, your milage WILL vary.


|

OS/2:

  Current driver     ADI2O100 ADD        31,119 05-11-94   2:52p

During installation:

  STRONG ADVICE :

  Start by fully experimenting with and exploiting the IBM1S506.ADD driver.
  Become familiar with the available parameter switches available for your
  version of OS/2.

  For OS/2 2.11 , the switches are:

     In the majority of cases, the IBM1S506.ADD driver will determine 
     parameters automatically. The following parameters are provided in 
     case it is necessary to override the default parameter selection. 

     In the case of ESDI drives formatted with sector sparing, it might be 
     necessary to use the /!R parameter.  Refer to the discussion of the 
     /!R parameter below. 

    Examples: 

       BASEDEV=IBM1S506.ADD /V /A:0 /U:0 /T:10 /GEO:(1314,7,26,-1) /A:1 /I
       BASEDEV=IBM1S506.ADD /V /A:1 /P:120 /IRQ:11 /U:0 /T:10
       BASEDEV=IBM1S506.ADD /V /A:1 /U:0 /GEO:20
       BASEDEV=IBM1S506.ADD /V /A:0 /U:0 /SMS
       BASEDEV=IBM1S506.ADD /V /A:0 /!R
 
      Parameter Definitions: 

       /V  Verbose Mode.  Displays controller status and drive geometry 
	   information during OS/2 initialization. 

       /A:0  Adapter number.  /A:0 indicates that the parameters that follow 
	     apply to the primary disk controller.  /A:1 indicates that the 
	     parameters that follow apply to the secondary disk controller. 

       /I    Ignore adapter.  The driver automatically attempts to locate
	     and initialize both the primary and secondary adapters.  In 
	     some cases, other DASD controllers might appear between the 
	     primary and secondary IDE controllers.  In these cases, the 
	     system should be configured as follows: 

		BASEDEV=IBM1S506.ADD /V /A:1 /I
		BASEDEV=MOREDASD.ADD
		BASEDEV=IBM1S506.ADD /V /A:0 /I
		      
       /!R   Disable adapter resets.  In most cases, resets assist in 
	     recovering from transient hardware problems such as lost 
	     interrupts, timeouts, and unsupported commands.  However, for 
	     some ESDI adapters, options set by vendor unique commands such 
	     as sector sparing might be lost after a reset.  Setting this 
	     parameter is recommended for ESDI adapters with disks formatted 
	     using sector sparing. 
 
       /P:120 or /PORT:120  Base port address (hex).  Overrides the default 
			    base port address for this adapter.  Ports are 
			    still assigned and in this case would be 120-127 
			    and 326. The default port addresses for 
			    Adapter 0 is 1F0 and for Adapter 1 is 170. 

       /IRQ:11  IRQ level (dec).  Overrides the default IRQ level for this
		adapter. The default IRQ level for Adapter 0 is (14) and 
		for Adapter 1 is (15). 

       /U:0   Unit Id. 
	      Unit 0 indicates parameters that follow apply to Drive 0.  
	      Unit 1 indicates parameters that follow apply to Drive 1. 

       /T:10  Error retry time in seconds (dec).  Indicates the total 
	      allowable error recovery time for a request.  Error recovery 
	      times less than 5 seconds will be ignored.  This parameter 
	      defaults to 30 seconds.  A shorter interval might be 
	      desirable for fault tolerant applications. 

       /GEO:(1314,7,26,-1) or /GEO:20   Drive geometry override (dec).  
	      Indicates the Cylinder/Head/Sector geometry for the drive.
	      This parameter is the Write Precompensation Cylinder which 
	      can be omitted for drives which do not require precompensation. 

	      As an alternate format, standard BIOS drive types can be used.  
	      Types 0-47 are supported.  User defined types 48 and 49 should 
	      be entered directly in the previous format.  When specified, 
	      this parameter overrides other geometry sources.  If this 
	      parameter is absent, other geometry sources discussed above 
	      will be used. 

       /SMS   Enable Set Multiple Support.  This parameter enables Set 
	      Multiple Support which improves performance of some IDE drives.  
	      If the drive does not have this feature, this parameter will 
	      be ignored.  The /V - (Verbose) parameter will indicate whether 
	      this feature has been enabled on a particular drive. 
   
  For OS/2 WARP , the switches are:

     This device driver provides support for MFM, RLL, ESDI, and IDE hard 
     disk controllers on non-Micro Channel industry standard devices. 

     In the majority of cases, the IBM1S506.ADD driver will determine 
     parameters automatically.  The following parameters are provided 
     in case it is necessary to override the default parameter selection. 
 
						     Ŀ
						                 
       BASEDEV=  IBM1S506.ADD  /A:n 
				   /V             /!R Ĵ 
						      /P:hhh Ĵ 
						      /IRQ:n  
						     /I 
 
       Ĵ
		         Ŀ 
		                                   
		  /U:n 
			    /T:n Ĵ
			    /GEO:(n,n,n,n) Ĵ
			    /!SMS Ĵ
			    /LBA Ĵ
			    /!DM 
 
     THE ONLY PARAMETERS DESCRIBED ARE THOSE WHICH HAVE CHANGED 
     FROM OS/2 2.11  :

       /!SMS  Disable Set Multiple Support (Block Mode). The IBM1S506 driver 
	      will automatically enable Set Multiple Support if a drive 
	      indicates it supports this feature.  The /V parameter indicates 
	      whether Block Mode support has been enabled for a particular 
	      drive. This feature improves performance of some IDE drives by 
	      allowing the drive to transfer more than 512 bytes of data per 
	      interrupt to the host CPU. Some older IDE drives and caching 
	      IDE controllers may not support this feature properly.  In this 
	      case specifying the /!SMS switch will disable this support. 

 
       /!DM   is used to prevent the OS2DASD.DMD device driver from managing 
	      the hard disk drive indicated by the /U parameter. 

Preparation:

	The current ADI2O100.ADD driver uses the OS/2 2.11 switches. As such,
	if you want to use multiple sector support you will have to use the
	/SMS parameter, even if you are using the ADI2O100.ADD driver while
	using OS/2 WARP.

	Hopefully, the further evolution of this driver will create a set of
	parameters which is equivalent to those available for the MS-DOS
	driver.

During installation:

   OS/2 2.11     
	
	Using the install.cmd in an OS/2 command line window should properly
	install the driver.  What should happen is that the IBM1S506.ADD 
	driver is commented out and immediately below it the ADI2O100.ADD
	driver is inserted in your config.sys.  The ADI2O100.ADD driver
	will be copied to the same directory as the IBM1S506.ADD driver.

	Find the IBM1S506.ADD driver in your config.sys  ( /OS2 ), and 
	verify the ADI2O100.ADD driver was copied into the same directory.

      Always use the /V parameter. 
      Watch the banner to see what has been invoked.
  
   OS/2 WARP VERY IMPORTANT !
	
	Using the install.cmd in an OS/2 command line window will not
	properly install the driver.  What should happen is that the 
	IBM1S506.ADD driver is commented out and immediately below it the 
	ADI2O100.ADD driver is inserted in your config.sys.  But the 
	ADI2O100.ADD driver will not be copied to the same directory 
	as the IBM1S506.ADD driver.  So prior to running install.cmd, find
	the IBM1S506.ADD driver (/os2/boot), copy the ADI2O100.ADD into the
	same subdirectory, and then run install.

      Always use the /V parameter. 
      Watch the banner to see what has been invoked.
  
Tweaks:

   I have been unable to document a statisically significant improvement in
   the performance of Western Digital WDC2540 hard drives when comparing
   the ADI2O100.ADD driver to the IBM1S506.ADD driver, regardless of the
   variety of parameters specified.  When checking the drive and controller
   information using SysInfo, a 16-bit controller is still registered. So
   I have no good tweaks for OS/2.  Scan the notes on the IBM driver. 
   I do not see any way to force 32-bit access through the interface similar 
   to the DOS device driver.


|

What Happened to Appian Technologies.

In fast moving business such as this, Appian is to some extext no longer 
in existence.  The Appian Renegade Video Cards were sold to an oufit called
ETMA. And Cirrus Logic has picked up the ADI interface technology. This 
included rights to manufacture and further develop the ADI2 chip, including 
drivers MS-DOS, Windows, and OS/2.

Cirrus Logic has changed the name of the chip. It's now the PD7220.In 
addition, CL will be further developing the chip family. CL has hired 
the driver writer from Appian, and is looking for someone familiar with 
writing OS/2 drivers.  (i hope they think about Linux too)


|

Do you have an ADI2 chip in your computer ?

The Acculogic sIDE4-VL IDE ADapter card is ADI2 based.

Some motherboards (like mine) have them plugged right in. The way I 
know this (other than just looking at the motherboard) is to set the 
IDE controller speed in the BIOS setup from "compatible" to "fast". A 
reference to the ADI2 chip pops right up.

I have seen an I/O interface card with fans and a VL-bus connector which
uses the ADI2 chip at CompUSA.

There are probably other implementations as well.

|

Points of Contact

You should always start by trying to get support from your vendor
or supplier.  I have listed those vendors who I am aware of that
have products that incorporate the ADI2 EIDE Interface Chip.


The Appian Technologies BBS  WAS    408.730.5403     Disconnected

The Cirrus Logic BBS                510.440.9080     9600 baud 
     Conference 20 - CL-7220 (IDE)

The Cirrus Logic FTP Site           ftp.cirrus.com   
     Drivers Not Available When This Document Wac Created


For the Acculogic sIDE4-VL

The Acculogic BBS                    714.470.1759    9600 baud   -  4 nodes
     File Area [5]  Acculogic IDE Files
     SIDE4VL.EXE contains ADI2C143.SYS, ADI2W104.386, ADI2O010.ADD


On Compu$erve ,  in the Graphics Vendor B Forum , Section ETMA/Appian
     Older versions of these same files.



End of File.

This file is copyright awl (c) 1995.  
Corrections and additions are encouraged.

awl
1/10/95

