SCSI CD-ROM Driver README Contents
==================================

This document provides information you should know before 
installing the SCSI CD-ROM Driver software. Last minute product 
and device information is also documented.

If you have any comments or questions about this product that
your distributor can't answer, contact Gear Technical Support:


    Gear Technical Support
    10 North Presidential Blvd. 
    Suite 125
    Bala Cynwyd, PA
    USA, 19004

    Telephone:   (610) 617-0850. 
    FAX:         (610) 617-0856. 
    BBS:         (610) 617-0857.

    CompuServe:  Log into CompuServe and access the Gear forum 
                 by entering GO GEAR.

    Internet:    Support@Elektroson.com


Table of Contents
=================

1.  Installing ASPI Managers
2.  Loading Corel's Device Drivers
3.  Using Memory Managers
4.  CorelCDX for Windows and DOS
5.  Undocumented Commands
6.  Support for Kodak Photo CDs

The following topics are relevant only if you're using
the named hardware:

7.  Using the Pioneer DRM604X in SCSI-1 Mode
8.  Using Future Domain Host Adapters
9.  Using Always AL-7000 Host Adapters
10. Using the IBM ThinkPad SCSI Docking Stations


1.  Installing ASPI Managers
----------------------------

For your convenience, ASPI managers for many host adapters
have been included, which you can install during the 
installation.

If the ASPI manager for your card isn't provided, you must 
install the ASPI manager and load it in your CONFIG.SYS file 
before installing this software. If you have problems with any 
ASPI manager, contact the manufacturer of your host adapter
card.

CorelSCSI provides the following ASPI managers:
   
Card Type                      ASPI Version    File Name
---------                      ------------    -------------
Corel Generic ASPI for         1.22c           ASPIDRV.SYS
BusLogic and Adaptec
(154x, 164x) host adapters

Corel Generic ASPI for the     1.00a           ASPIMED.SYS
Pro Audio Studio 16 card

Corel 'LS2000' ASPI Manager    1.10            ASPILS_D.SYS

Corel Generic ASPI for IBM     1.00a           ASPIIBM.SYS
MCA host adapters

IBM 3550 ThinkPad Docking      1.00a           ASPIIBM.SYS
Station ASPI Manager

IBM 3545 ThinkPad Docking      4.0             DCAM950.EXE
Station ASPI Manager           4.0             ASPIFCAM.SYS

IBM 16-Bit AT Fast SCSI        4.0             DCAM18XX.SYS
Adapter ASPI Manager           4.0             ASPIFCAM.SYS

Acculogic ASPI Interface       3.01.01         ASPICAM.SYS

Acculogic CAM driver           3.00.05         DOSCAM.SYS

Always 'AL-500' ASPI Manager   1.10            ASPILS_D.SYS

Always 'AL-1000' ASPI Manager  1.00            ASPISHT.SYS

Always 'AL-7000' ASPI Manager  837-13.13       AL7ASPI.SYS

Always 'IN-2000' ASPI Manager  461-12          ASPIDRVR.SYS
 
American Megatrends Fast Disk  1.1             ASPIKERN.SYS

CoComp 'SCSICable Plus'        2.602           WBSASPI.SYS
ASPI Manager

DPT ASPI for SCSI BIOS         001.K           DPTDDL.SYS
ROM\SMARTROM V.001.K

DPT ASPI for SCSI BIOS         002.B           DPTDDL.SYS
ROM\SMARTROM V.002.B

DTC '3X80/3X50' ASPI Manager   1.5A            ASPI3X80.SYS

New Media 'Visual Media'       2.03            ASPIMGR.SYS
ASPI Manager

New Media 'Bus Toaster'        1.00            BTASPI.SYS
ASPI Manager

P.E. Logic 'SCSI-Link EPP'     2.52            PWBSASPI.SYS
Host Adapter

P.E. Logic 'PEL-8xx Series     2.00            PEL800.SYS
8-bit' Host Adapter

P.E. Logic 'PEL-16xx Series    2.00            PEL1600.SYS
16-bit' Host Adapter

Procomp 'Pro-Val'              1.0a            PVALASPI.SYS
ASPI Manager

Future Domain ASPI Manager     4.0             ASPIFCAM.SYS

(TMC-950) Future/CAM 8-Bit     4.0             DCAM950.EXE
Multi-tasking CAM driver

(TMC-18XX) Future/CAM 16-Bit   4.0             DCAM18XX.EXE
Multi- tasking CAM driver 

(TMC-950)Future/CAM 8-Bit      4.0             MCAM950.SYS
Single tasking CAM driver 

(TMC-18XX) Future/CAM 16-Bit   4.0             MCAM18XX.SYS
Single-tasking CAM driver 

QLogic ASPI Manager            2.17            QLASPI.SYS

QLogic SCSI RAM BIOS           2.17            QL406DOS.SYS

UltraStor 'Ultra 14F/34F'      2.03            USPI14.SYS 

UltraStor 'Ultra 14N'          1.01            USPI14N.SYS

UltraStor 'Ultra 24FA'         2.02            USPI24.SYS
 
NOTE: To help distinguish between the revisions of the DPT 
      ASPI managers, which both use the name DPTDDL.SYS, two
      different file names are used. However, the installation
      renames the selected ASPI manager to DPTDDL.SYS. 

      The DPT ASPI for SCSI BIOS ROM\SMARTROM Version:

        * V.001.K is in the file DPTDDL1K.SYS
        * V.002.B is in the file DPTDDL2B.SYS

To install an ASPI manager that isn't provided with CorelSCSI
  
1.  Copy the ASPI manager from the disk provided with your 
    SCSI card to your hard drive.

2.  Add the device driver line to the CONFIG.SYS file using 
    the following syntax:

      DEVICE=C:\xxxx.SYS

      where xxxx indicates the name of your ASPI manager.

3. Reboot the system before you start the CorelSCSI 
   installation.

    While the system is rebooting, you should look for 
    status messages from the ASPI manager. If the status 
    indicates an unsuccessful installation, the CorelSCSI 
    device driver won't function.
    
  
2.  Loading Corel's Device Drivers
----------------------------------

During the installation, you're prompted to choose whether to
load the Corel CD-ROM device driver into high memory. If you 
choose this option and not enough memory is available, 
the driver won't load.

To correct this problem, edit the CONFIG.SYS file. For
each device driver command, replace the DEVICEHIGH 
keyword with DEVICE.


3.  Using Memory Managers
-------------------------

If you're using a memory manager, you may need to uninstall 
it before installing CorelSCSI and then reinstall the memory
manager.  In rare cases, systems may hang if CorelSCSI is 
installed while a memory manager is loaded.


4. CorelCDX (Windows and DOS)
-----------------------------

To work with your CD-ROM drives, you require a CD-ROM 
extensions program, such as CorelCDX, which interprets the 
CD-ROM file system format. CorelCDX also provides several 
types of caches, including a path table, directory, and data 
cache. These caches are discussed in detail in the Users' 
Manual. As an extension to CorelCDX, CDXCACHE provides an 
extended memory data cache.

CDXCACHE, if enabled, is loaded at the same time as 
CorelCDX.  This cache stores information recently read from 
CD-ROM drives in extended memory. When information requested 
by an application is located in the cache, the information 
can be accessed more quickly than re-reading the information 
from the drive.

CDXCACHE uses a least recently used (LRU) algorithm: 
frequently used data remains in the cache and infrequently 
used data is discarded from the cache. CDXCACHE works best 
with database type applications, which repeatedly read 
information from the same areas of a CD.

CDXCACHE can cache the first 16 CD-ROM drives connected to 
your system. The cache page size affects the maximum 
cacheable sector address.

The following CDXCACHE options may appear in the CorelCDX 
section of the CRLSCSI.INI file:

    * XMSSIZE indicates the cache size in kilobytes. You can 
      set XMSSIZE to 0 to disable the XMS cache. Note that 
      the number of tracks created on a CD by CDCOPY is 
      affected by the amount of available XMS memory, you 
      should disable the extended XMS cache when using 
      CDCOPY.

      You can set XMSSIZE to -1 to use a default cache size, 
      which is equal to one-quarter of the free XMS memory.

      You can also set XMSSIZE to  a specific size from 64K 
      to 16384K.

    * XMSPAGE configures the number of sectors per cache 
      page, which determines the read-ahead operations. The 
      value of 4 is recommended for smaller cache sizes; 
      it's more important to cache separate disk reads than 
      to perform read aheads. Use the value 8 for larger 
      cache sizes; more data is stored in one operation. The 
      default setting is 4 sectors per cache page.

    * XMSBLOCK represents the maximum size of read request 
      in sectors that will be cached. The cache performance 
      may benefit from larger values. However, the cache may 
      fill up more quickly. The default setting is 4 
      sectors.

Both CDXCACHE and Microsoft's SmartDrive program use 
extended memory caching. If you're using SmartDrive version 
5.0, provided with MS-DOS 6.2, you can use SmartDrive rather 
than CDXCACHE. However, CDXCACHE has smaller overhead and 
operates faster then SmartDrive. 

SMARTDRV.EXE 5.0 is designed to work exclusively with 
Microsoft's MSCDEX CD-ROM driver. However, Corel's 
PATCH_SD.COM modifies SMARTDRV.EXE to recognize CorelCDX as 
a valid CD-ROM driver.

PATCH_SD creates a copy of the existing SMARTDRV.EXE program 
and stores the copy as SMARTDRV.MSC. If you've made changes 
to SMARTDRV.EXE version 5.0 that change its size, such as 
compressing the file, from 45145 bytes, PATCH_SD won't work.

To modify SmartDrive to recognize CorelCDX

1.  At the command prompt, enter PATCH_SD.
   
2.  Check your AUTOEXEC.BAT file to ensure that CorelCDX is 
    loaded before SmartDrive; otherwise, SmartDrive won't 
    find, and therefore cache, CD-ROM drives. Since 
    SmartDrive is loaded after CorelCDX, you can't use the 
    CorelCDX /UNLOAD command.
   
3.  Use the CorelCDX section of Configuration to set the XMS 
    Cache Size option to Disable. The CDXCACHE is enabled, 
    by default. If you don't disable the cache, both 
    CDXCACHE  and SmartDrive will cache data, using twice 
    the necessary  amount of extended memory.
   
4.  Reboot your system to reinstall SMARTDRV.EXE.

Miscellaneous Information:

If you're using DOS 5.0, Norton Shell 6.0, and CDXCACHE, 
Windows won't run. Remove or upgrade any one of the three 
programs to resolve this problem.

The DRIVERNAME option of the CRLSCSI.INI file provides the 
required name of the CD-ROM device driver, which should be 
the same as the value of the DRIVERNAME option in the [CD-
ROM Drivers] section of this file. CD-ROM device drivers are 
numbered starting from MSCD001.

If CorelCDX can't find driver names in the CRLSCSI.INI file 
or if the CRLSCSI.INI file is missing, CorelCDX will try to 
locate and initialize the CD-ROM device drivers named, by 
default, 'MSCD001' and 'MSCD099'.


5. Undocumented Commands
------------------------

The following commands are not documented in the Users' Manual: 

CDXINFO
Provide summary information about CorelCDX.

SS
Displays a menu from which you can select a host adapter. 
CorelSCSI scans the selected host adapter and lists the 
SCSI devices detected.


6. Support for Kodak Photo CDs
------------------------------

The Corel CD-ROM device driver, which is named CUNI_ASP.SYS 
currently supports Kodak Photo CDs. Although other drives 
may read the Photo CD format, the following drives have been 
tested by Corel:

   Single session      Multi session
   --------------      ------------------------------------------------
   Chinon CDS435       Chinon CDS535                Teac CD-50
   NEC CDR73           GoldStar GCD-R322            Texel DM-3024K
   NEC CDR73M          Hitachi CDR-3750/CDR-6750    Texel DM-5024K
   NEC CDR74           Matsushita CR-533B           Toshiba XM3301 (with 
   NEC CDR83           NEC CDR74-1                   multi session upgrade)
   NEC CDR83M          NEC CDR84-1                  Toshiba XM3401
   NEC CDR84           NEC 3x CDR-600
   Sony CDU-541        NEC 4x CDR-900
   Sony CDU-6211       Panasonic CR-532
   Texel DM-5024       Philips CDD-521
   Texel DM-3024       Smart & Friendly HS-2200 i/e
   Toshiba XM3301      Sony CDU-561

7. Using the Pioneer DRM604X in SCSI-1 Mode
-------------------------------------------

If you're using a Pioneer DRM604X in SCSI-1 mode with 
multi-session discs, the driver may time-out while waiting 
for the disc to mount and display a "Not ready reading drive...
" error. If this error occurs, use Configuration to set the 
CD-ROM device driver TIMEOUT option to a value 
between 30 to 45.

8. About Future Domain Host Adapters   
------------------------------------    
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.     
   
For 8-bit and 16-bit adapters, two versions of CAM are provided:   
singletasking and multitasking.    
   
Multitasking CAM allows SCSI devices to disconnect/reconnect.   
This means that devices can disconnect from the SCSI bus while   
accessing data.  The disconnection makes CPU time available to   
the system, which optimizes 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.   
   
   
(TMC-950) Future/CAM 8-Bit Multitasking CAM   
-------------------------------------------   
Future Domain's 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.   
   
   
(TMC-18XX) Future/CAM 16-Bit Multitasking CAM   
---------------------------------------------   
By default, Future/CAM negotiates 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]DCAM18XX.EXE [/A0] [/A1] [/A2] [/A3]   
   
 Parameters:   
    /An:  Set adapter n to Asynchronous negotiation.   
   
   
About Future Domain's 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}   
   
   
9. Using Always AL-7000 ASPI Managers   
-------------------------------------   
If your SCSI CD-ROM drive doesn't support SCSI disconnects, you    
can add a switch to the AL-7000 ASPI Manager to disable   
SCSI disconnects:   
   
    DEVICE=[path]AL7ASPI.SYS [/d]   
   
    where   
    [path] is the directory path to the device driver. For   
    example, C:\DOS\.   
   
    [/d] disables SCSI disconnects.   
   
If you haven't attached any SCSI hard drives to the host adapter,   
the ASPI driver displays the following message:   
   
    Always Int 13 handler not loaded   
   
This message indicates that no hard drives were found.   
   
Load any caching software, such as SMARTDRIVE, VCACHE, and PC-  
KWIK, after the ASPI driver. Caching software is related to hard   
disk operation.   
   
Don't use the BIOS diagnostics or low level format functions when   
the ASPI driver is loaded.   


10. Using the IBM ThinkPad SCSI Docking Stations
------------------------------------------------

IBM 3550 ThinkPad Docking Station ASPI Manager
----------------------------------------------
For the IBM 3545 ThinkPad Docking Station SCSI controller 
to work with the CorelSCSI device drivers, a valid ASPI Manager 
(ASPIIBM.SYS) must be loaded in the CONFIG.SYS.

IBM 3545 ThinkPad Docking Station ASPI Manager
----------------------------------------------
For the IBM 3545 ThinkPad Docking Station SCSI controller
to work with the CorelSCSI device drivers, a valid CAM driver 
(DCAM950.EXE) and ASPI Manager (ASPIFCAM.SYS) must be 
loaded in the CONFIG.SYS.  The CAM driver must be loaded prior 
to the ASPI Manager and a memory address and IRQ must be 
supplied on the command line. The ASPI Manager converts ASPI 
requests to CAM requests.

Syntax for the CAM Driver:

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

Where:
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.

Syntax for the ASPI Manager :

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

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


