<PGUP - Up>                    DOS Help File              <PGDN - Down>

                            Table of Contents


1.   Introduction to PowerSCSI!
1.1  Keyboard and Mouse Support
2.   Introduction to SCSI
2.1  Controller Cards
2.2  SCSI Bus
2.3  SCSI Device Types
2.4  SCSI ID
2.5  Logical Unit Number (LUN)
2.6  SCSI Termination
2.7  Terminating a SCSI bus with external devices only
2.8  Terminating a SCSI bus with internal devices only
2.9  Terminating a SCSI bus with internal and external devices:
2.10 Disconnect/Reconnect
3.   Introduction to the CAM Interface
4.   Future/CAM 32-Bit Multitasking CAM
5.   Future/CAM 16-Bit Singletasking CAM
6.   Future/CAM 16-Bit Multitasking CAM
7.   Future/CAM 16-Bit Windows CAM
8.   Future/CAM 8-Bit Singletasking CAM
9.   Future/CAM 8-Bit Multitasking CAM
10.  Future/CAM 8-Bit Windows CAM
11.  Future Domain ASPI Manager
12.  Int 4Bh Support
13.  Future Domain CD ROM Support
14.  Windows 32 Bit Disk Access Support
15.  Future Domain Int 13h Support




1.   Introduction to PowerSCSI!

PowerSCSI! provides full support for fixed disks and CD-ROM, and 
provides SCSI interfaces for every major SCSI interface, allowing 
you to use hundreds of SCSI drivers and applications to support 
devices.

PowerSCSI! also lets you configure your system for optimum performace, 
taking advantage of Fast Synchronous data tranfer and multitasking 
SCSI I/O requests.  When installing other applications that will use 
PowerSCSI!, you must install PowerSCSI! first.  This is because 
PowerSCSI! provides interface layer between SCSI applications (like 
tape and scanner programs) and drivers (like CD-ROM or magneto optical 
drivers).


1.1  Keyboard and Mouse Support

Mouse support is available.  To use the mouse run MOUSE.COM.

Keyboard support is as follows:

   Left Arrow:    Moves the active item to the left within a control group
   Right Arrow:   Moves the active item to the right within a control group
   Tab Left:      Moves the active item to the left within a control group, 
                  or to a previous control group 
   Tab Right:     Moves the active item to the right within a control group,
                  or to a the next control group
   Enter Key:     Selects active item
   

2.   Introduction to SCSI

SCSI (Small Computer Systems Interface) is an intelligent interface 
that allows computers to communicate with various types of devices.  
A SCSI system is usually composed of a SCSI controller card, a SCSI 
bus,one or more devices located at different IDs, and termination.

2.1  Controller Cards

The SCSI controller card is usually an ISA, MicroChannel, or EISA 
card that fits into a slot in the computer.  It provides the SCSI 
interface to the computer and any drivers or applications that use 
SCSI. SCSI may also be provided on a system motherboard, in which 
case a connector is provided to attach SCSI devices to the system.

2.2  SCSI Bus

A SCSI bus is a cable that connects SCSI devices with a SCSI 
controller card.  It is through this cable that a SCSI 
controller card controls SCSI devices.

2.3  SCSI Device Types

SCSI supports a wide variety of devices.  Devices defined by SCSI 
include fixed disks, tape drives, printers, processors, WORMs, 
CD-ROMs, scanners, medium-changers (jukeboxes), magneto optical 
devices,  and communication devices.

2.4  SCSI ID

A SCSI bus can support up to eight devices.  Each device on the 
SCSI bus is addressed by a unique number between zero and seven, 
called the SCSI (or Target) ID.  The SCSI controller is located at 
SCSI ID 7, leaving IDs ranging from zero to six free.  When the 
SCSI controller initializes, it scans for devices at each SCSI ID, 
starting at six and ending at zero.

2.5  Logical Unit Number (LUN)

Up to 8 devices may exist at each SCSI ID.  These devices are addressed 
by their Logical Unit Number (LUN).  Typically only one device is 
present at each ID, and is assigned a logical unit number of 0.

2.6  SCSI Termination

For SCSI to work properly the SCSI bus must be terminated.  To 
terminate a SCSI bus, you must put terminating resistors at each 
end of the bus.  A bus may have three configurations:  external 
devices only, internal devices only, or external and internal devices.

2.7  Terminating a SCSI bus with external devices only:

Termination must be supplied on the last external device on the 
chain, and on the SCSI controller 
card.

2.8  Terminating a SCSI bus with internal devices only:

Termination is must be supplied to the last device on the chain, and 
on the SCSI controller card.

2.9  Terminating a SCSI bus with internal and external devices:

Termination must be supplied to the last internal device on the 
internal chain, and to the last external device on the external 
chain. Also, termination on the SCSI controller card must be removed.

2.10 Disconnect/Reconnect

Not all SCSI transactions can be processed immediately.  For example, 
rewinding a tape or scanning a document can take a long time, as can 
seeking to a sector on a CD-ROM or fixed disk.  It is wasteful to 
consume CPU resources waiting on operations like these.  In these 
cases, the SCSI specification has defined a way for a device to 
disconnect from the SCSI  bus, thus freeing the SCSI bus for other SCSI 
transactions or freeing the CPU from being tied to the SCSI bus 
waiting for the operation to complete.

When the disconnected device completes its operation it can reconnect 
to the bus, causing a hardware interrupt.  When this interrupt occurs, 
control is returned back to that SCSI transaction, and the transaction 
is completed.


The disconnect/reconnect mechanism provides overlapped I/O functionality 
by allowing multiple outstanding SCSI requests with different devices 
to be in transaction at the same time.


3.   Introduction to the CAM Interface

Future Domain's Future/CAM manages all SCSI transactions on the SCSI bus.  
All driver and application SCSI I/O requests are eventually processed by 
Future/CAM.  Future/CAM drivers are provided for each adapter type.

For 8-bit and 16-bit adapters, two versions of CAM are provided: 
Singletasking and Multitasking. Singletasking CAM issues requests to 
the SCSI bus, and does not disconnect. This means that each transaction 
on the SCSI bus begins and ends, and no outstanding requests are 
generated. 

Multitasking CAM, on the other hand, allows disconnect/reconnect.  This 
means that while a device is busy fetching data, it can disconnect from 
the SCSI bus.  This frees CPU time for the system, thus optimizing CPU 
cycles.  In addition, while a device is disconnected from the SCSI bus, 
other SCSI requests can be issued to other SCSI devices on the bus.  The
condition of overlapped I/O where several outstanding requests may be 
in process on the SCSI bus.

All Future/CAM Window drivers are multitasking versions of CAM.


4.   Future/CAM 32-Bit Multitasking CAM

32-Bit CAM provides multitasking CAM support for Future Domain's 32-Bit
7000EX product.  32-Bit CAM negotiates the fastest possible data transfer
rate, as supported by each device on the SCSI bus, and supports disconnect/
reconnect.  

Syntax:
device=[drive:][path]DCAM7EX.EXE 


5.    Future/CAM 16-Bit Singletasking CAM

By default Future/CAM negotatiates the fastest data transfer possible 
for each device.  Although this works with all SCSI 2 devices, some 
early SCSI 1 devices have problems supporting speeds they negotiate 
at.  To solve this problem, from the Custom Install for the 18XX CAM
you can select the Asynchronous data transfer option, which will force 
Future/CAM to default to the lowest data transfer rate allowed.

Syntax:
device=[drive:][path]MCAM18XX.SYS [/A0] [/A1] [/A2] [/A3]

Parameters:
/An:   Set adapter n to Asynchronous negotiation


6.    Future/CAM 16-Bit Multitasking CAM

By default Future/CAM negotatiates the fastest data transfer possible 
for each device.  Although this works with all SCSI 2 devices, some 
early SCSI 1 devices have problems supporting speeds they negotiate 
at.  To solve this problem, from the Custom Install for the 18XX CAM
you can select the Asynchronous data transfer option, which will force 
Future/CAM to default to the lowest data transfer rate allowed.

Syntax:
device=[drive:][path]}{\f6 DCAM1800.EXE [/A0] [/A1] [/A2] [/A3]

Parameters:
/An:  Set adapter n to Asynchronous negotiation.


7.    Future/CAM 16-Bit Windows CAM

Future Domain's 16-Bit Windows CAM is a fully featured multitasking CAM
that allows Windows to take full advantage of SCSI.  This virtual driver
must be installed in Windows' SYSTEM.INI file in the [386Enh] section.

Syntax:
device=[drive:][path]V18FCAMD.386

Parameters: None


8.    Future/CAM 8-Bit Singletasking CAM

Future Domains 8-Bit Singletasking CAM provides CAM support for all 
8-bit SCSI controller cards.

Syntax:
device=[drive:][path]MCAM950.SYS

Parameters: None


9.    Future/CAM 8-Bit Multitasking CAM

Future Domains 8-Bit Multitasking CAM provides CAM support for all 
8-bit SCSI controller cards.

Syntax:
device=[drive:][path]DCAM950.EXE /Memory_address IRQ

Parameters:
For each adapter DCAM950.EXE must support the memory address and IRQ 
must be supplied on the command line.  Valid memory addresses include 
C800, CA00, CE00, DE00, E800, and EC00.  Valid IRQs include 3, 4, 5, 
10, 11, 12, 14, and 15.  Each 8-bit adapter must be installed with it's 
own unique memory address and IRQ.


10.    Future/CAM 8-Bit Windows CAM

Future Domain's  8-Bit Windows CAM is a fully featured multitasking CAM
that allows Windows to take full advantage of SCSI. This virtual driver 
must be installed in Windows' SYSTEM.INI file in the [386Enh] section.

Syntax:
device=[drive:][path]V9FCAMD.386

Parameters:
An addition line must be added to the SYSTEM.INI file in the [386Enh] 
section with the format:

FDC950=Memory_Address, IRQ ... 

Where Memory_Address is the memory address of the 8-bit adapter, and IRQ 
is the IRQ on set on the adapter.  Valid memory addresses include C800, 
CA00, CE00, DE00, E800, and EC00.  Valid IRQs include 3, 4, 5, 10, 11, 
12, 14, and 15.


11.   Future Domain ASPI Manager

Future Domain's ASPI Manager is a driver that converts ASPI requests to 
CAM requests.  This driver must be loaded in the CONFIG.SYS file after 
any CAM drivers have been loaded.

Syntax:
device=[drive:][path]ASPIFCAM.SYS [/D] [/O]

Parameters:
/D:    enables disconnect/reconnect support
/O:    enables overlapped I/O}


12.   Int 4Bh Support

Future Domain's Int 4Bh support converts all Int 4Bh requests to 
CAM requests. This driver must be loaded in the CONFIG.SYS file 
after any CAM drivers have been loaded.

Syntax:
device=[drive:][path]INT4BCAM.SYS


13.   Future Domain CD ROM Support

Future Domain's CD ROM driver provides CD ROM support for CD ROM 
extensions for almost all drives on the market today.  To enable 
CD ROM support, FDCD.SYS must be loaded in the CONFIG.SYS and 
CD ROM extensions must be loaded in the AUTOEXEC.BAT file.

Syntax:
device=[drive:][path]fdcd.sys [/D:MSCD000] [/Nn] [/I] [/R] [/Z]

Parameters:
/D:????????: Identification string to CD-ROM extensions
/Nn:         Support first n drives
/I:          Inhibit invalid disk change status
/R:          Force SCSI bus reset upon driver initilization
/Z:          Display drive size

Note: If your system is attached to a network, you must add the 
LASTDRIVE line to the end of your CONFIG.SYS file.  For example,
if the last drive letter allocated is drive E:, then you should 
add 

   LASTDRIVE=E:

to your CONFIG.SYS file.  In this case, network drive letters will 
be added starting at drive F:.


14.   Windows 32 Bit Disk Access Support

Future Domain's 32 Bit Disk Access Support for Microsoft Windows 
increases disk performance by bypassing the Int-13h BIOS interface, 
allowing Windows to directly control fixed disks.

Syntax:
device=[drive:][path]fdscsi.386


15.   Future Domain Int 13h Support

The DOS Int 13 disk support captures all Int 13 calls to fixed disks
on the SCSI controller and converts them to CAM requests.  This driver 
should not be used with Future Domain's 32 Bit Disk Access support.

Syntax:
device=[drive:][path]FDBIOS.SYS 


