home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 4 Drivers
/
04-Drivers.zip
/
adi2drv.zip
/
README.TXT
< prev
Wrap
Text File
|
1994-07-28
|
25KB
|
587 lines
Appian ADI/2
Local-Bus IDE Disk Interface
Software Driver Users Guide
June 1993
***********************************************************
***** Installation Procedure *****
***********************************************************
To install the DOS and Windows 3.1 ADI/2 Disk Accelerator
driver software from a floppy disk inserted in the A drive:
Note: Before beginning installation of the ADI/2 software it is
recommended that you have a bootable DOS floppy system
diskette available. In the unlikely event of a serious
installation or operation problem it may be necessary to boot
your system from the floppy drive and remove or 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 driver 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 ADI/2 Disk Accelerator 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 then automatically copy the driver file(s) to your hard disk.
It will configure the disk sub-system for optimum performance
dependent upon 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 (if Windows 3.1 is installed).
Step 4: Type Y or N in response to the question:
"Do you want to install the ADI/2 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 ADI/2 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 directory. CONFIG.ADI can be later renamed to
CONFIG.SYS to make the ADI/2 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 ADI/2 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 ADI/2 optimization. You may want to rename your
existing SYSTEM.INI file and save it as a backup.
Last Step: The ADI/2 driver installation is now complete
and you will be prompted to reboot the system to make the
changes active. Remove the ADI/2 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 ADI/2 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 ----
******************************************************
***** Introduction *****
******************************************************
Congratulations on your decision to purchase this product
which includes the ADI/2 local-bus IDE disk interface. The
ADI/2 will enhance disk sub-system performance when used
with modern IDE disk drives.
The ADI/2 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.SYS
ADI2W1xx.386
README.TXT
The software driver is used to enable the high performance
modes offered by the ADI/2. This Users Guide details the use
of the ADI/2 Release 1.0 software drivers.
*********************************************************
***** Software Driver Description *****
*********************************************************
The complete ADI/2 DOS driver includes memory resident and
non-memory resident (in system memory) code sections. The
non-resident portion configures the ADI/2 registers for
optimum operation dependent upon your system configuration
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 ADI/2 installation routine will add the file ADI2C1xx.SYS
to into the C: root directory. It may also automatically 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 the ADI/2 IC. This information is used in programming
the ADI/2 registers. Some systems vary the clock rate
between "turbo" and slow operation modes. The system
should be switched to "turbo mode" during startup so that the
ADI/2 software can determine the maximum clock rate. The
ADI/2 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 displayed.
************************************************************
***** DOS Driver Command Line Switches *****
************************************************************
The ADI/2 DOS driver provides a number of command 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 {io16|io32}
{initonly|noinit}{c=m|c=s}{d=m|d=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 ADI/2 controller. This mode
must be used with 16-bit VL-bus systems designed around the
IBM or Cyrix 486SLC or 486SLC2 processors. These
processors feature a 16-bit external data path and cannot
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 ADI/2 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 ADI/2 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 ADI/2 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 installed 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
configuration). The "m" or "s" parameters select multiple
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 of 16-bit data transfer cycles. Example "b" will
only initialize the ADI/2 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:\ADI2c1xx.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 ADI/2 software package includes a 32-bit driver for
Windows 3.1. Please note that this driver is NOT suitable for
use with Windows versions 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 ADI/2 Installation utility will scan the SYSTEM.INI file
and make the changes required for the ADI/2. 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 ADI/2 installation utility was
unable to find the Windows directory and files. 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 ADI/2 Windows driver installed, if the ADI/2 32-bit DOS
memory resident driver is also installed. The Windows
supplied 32-bit driver is not compatible with the
ADI2C1xx.SYS DOS driver. To restate this another way, with
the ADI/2 32-bit DOS memory resident driver installed,
Windows may only be run in its native 16-bit mode unless the
ADI/2 Windows driver is installed.
*********************************************************
***** Adding A Disk *****
*********************************************************
Adding a second physical disk drive into your system generally
requires no effort with respect to the ADI/2 driver software.
When loading, the ADI/2 software will automatically detect the
presence of the new disk drive and configure appropriately.
Just remember to first set the disks jumpers for master slave
operation according to the disk drive manuals, and add the new
disk's physical parameters into the system BIOS configuration.
*********************************************************
***** DOS Compatibility *****
*********************************************************
The ADI/2 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 ADI/2 software has been tested to work properly with
popular data compression software including Stackertm
(versions 3.0 and 2.0), Superstor and MS DOS 6.0
Doublespace compression.
*********************************************************
***** Troubleshooting *****
*********************************************************
Extensive testing has been done to insure that the installation
and operation 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 ADI/2 software may not have installed
properly. Using a system diskette reboot the system. Edit the
CONFIG.SYS file to verify and then delete the ADI/2
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 ADI/2 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 motherboards
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 settings. Using a system diskette reboot the system.
Edit the CONFIG.SYS file and add a remark preface to the
ADI/2 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 ADI/2 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 ADI/2 command line in the CONFIG.SYS file. This
time enable the disks for single mode operation so that the
command line reads:
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 command 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.
ADI/2 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 installation 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 ADI/2 command line (ex:
device=c:\ADI2c1xx.sys) after any memory or disk
management utility commands.
The ADI/2 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
ADI/2 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 ADI/2 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. Verify 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 ADI/2 software.
If both drives work together without the ADI/2 driver enabled
then re-install the ADI/2 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 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.
Suggested fix b: Refer to the section entitled "Windows 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 ADI/2 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.386 driver 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 are missing
re-install the ADI/2 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
configuration.
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
interrupt is used for each sector (512 bytes) transferred.
Slave Drive: The secondary drive (typically, logical drive D)
in a dual drive system.
*********************************************************
Trademarks: ADI/2 - 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, to update the information contained herein.