

ABOUT POWERSCSI! FOR NETWARE 386 
================================



FILES DESCRIPTION
-----------------

    README.NOW   - This file
    INSTALL.EXE  - Installation Program    
    FUTD_3.DSK   - Netware 386 V3.1X Disk Level Driver
    FUTD_4.DSK   - NetWare 386 V4.X Disk Level Driver
    FUTXPT.DSK   - Netware Transport Level Driver
    FUTASPI.DSK  - NetWare ASPI Manager for Future Domain Controllers    
    311/CDROM.NLM- NetWare 386 V3.11 CDROM Netware Loadable Module
    4X/CDROM.NLM - NetWare 386 V4.X CDROM Netware Loadable Module

   SCSI I/O MODULES:

    SIM950_3.DSK - NetWare 386 V3.1X 950 SCSI I/O Module 
    SIM950_4.DSK - NetWare 386 V4.X 950 SCSI I/O Module 
    SIM18_3.DSK	 - NetWare 386 V3.1X 1800/18C50 SCSI I/O Module 
    SIM18_4.DSK	 - NetWare 386 V4.X 1800/18C50 SCSI I/O Module 
    SIM7000E.DSK - NetWare 386 V3.1X/4.X 7000EX SCSI I/O Module 



INSTALLATION
------------

    An installation program (INSTALL.EXE) is provided in this diskette to 
    copy the necessary NetWare drivers that work with your Future Domain 
    controller to your NetWare path. The program installs for both 
    NetWare Version 4.X and Version 3.1X.


    NetWare 386 Version 4.X
    -----------------------
    
    1) Loading

        The NetWare 386 SCSI driver is actually three NLMs: one is a SCSI I/O
        module (SIMXXXX.DSK), a transport module (FUTXPT.DSK- autoloaded by 
        the SIM), and the disk module (FUTD_4.DSK). The module FUTD_4.DSK 
        accepts requests from NetWare and passes them to the transport module 
        which in turn routes the request to the appropriate SCSI I/O module 
        (SIMXXXX.DSK).  All three drivers need to be loaded before you can 
        access your SCSI drives.  FUTASPI.DSK is Future Domain's ASPI Manager 
        for NetWare 386 V3.1X/4.X.  You do not need to load this driver if 
        you do not have any NLMs that interfaces via ASPI (Advanced SCSI 
        Programming Interface).

        The installation program of NetWare 386 V4.X can load the Future
        Domain drivers. These drivers have to be in the root directory of the
        diskette or on the directory where the file SERVER.EXE resides. 
        Depending on which controller you have, copy the required files
        to the path where the server files reside or use the INSTALL.EXE
        to do this for you.  

        To load the drivers you need to type the following at the Novell 
        prompt:

        (a) Files for 8-bit Controller (e.g. TMC-850M)

        :load sim950_4
        :load futd_4
        :load futaspi

        (b) For 16-bit Controllers (e.g. TMC-1650/1660/1670/1680/1790/1795
                                         MCS-600/700)       

        :load sim18_4
        :load futd_4
        :load futaspi

        (c) For 32-bit Controller (e.g. TMC-7000EX)

        :load sim7000e
        :load futd_4
        :load futaspi

    2) Unloading

        To unload the drivers you need to unload the FUTASPI.DSK first (if
        it was loaded), then unload the FUTD_4.DSK. Finally, unload the
        SIMXXXX.DSK module. For example you had a TMC-850M in your system,
        to unload the NetWare/386 drivers, type the following at the Novell 
        prompt:

        :unload futaspi
        :unload futd_4
        :unload sim950_4



    NetWare 386 Version 3.1X
    ------------------------

    1) Loading

        The NetWare 386 SCSI driver is actually three NLMs: one is a SCSI I/O
        module (SIMXXXX.DSK), a transport module (FUTXPT.DSK- autoloaded by 
        the SIM) and the disk module (FUTD_3.DSK). The module FUTD_3.DSK 
        accepts requests from NetWare and passes them to the transport module 
        which in turn routes the request to the appropriate SCSI I/O module 
        (SIMXXXX.DSK).  All three drivers need to be loaded before you can 
        access your SCSI drives. 

        The install program copies the correct SIMXXXX.DSK for your controller. 
        It also copies FUTD_3.DSK, FUTXPT.DSK and FUTASPI.DSK to your Novell 
        subdirectory.  FUTASPI.DSK is Future Domain's ASPI Manager for NetWare 
        386 V3.1X/4.X.  You do not need to load this driver if you do not have 
        any NLMs that interfaces via ASPI (Advanced SCSI Programming Interface).

        To load the drivers you need to type the following at the Novell 
        prompt:

        (a) For 8-bit Controller (e.g. TMC-850M)

        :load sim950_3 
        :load futd_3
        :load futaspi
        
        (b) For 16-bit Controllers (e.g. TMC-1650/1660/1670/1680/1790/1795
                                         MCS-600/700)       

        :load sim18_3
        :load futd_3
        :load futaspi

        (c) For 32-bit Controller (e.g. TMC-7000EX)

        :load sim7000e
        :load futd_3
        :load futaspi

    2) Unloading

        To unload the drivers you need to unload the FUTASPI.DSK first (if
        it was loaded), then unload the FUTD_3.DSK. Finally, unload the
        SIMXXXX.DSK module. For example you had a TMC-850M in your system,
        to unload the NetWare/386 drivers, type the following at the Novell 
        prompt:

        :unload futaspi
        :unload futd_3
        :unload sim950_3



DRIVER PARAMETERS
-----------------

    The SCSI I/O module for the 16-bit adapters (i.e., SIM18_3.DSK and
    SIM18_4.DSK) supports a driver parameter that disables the negotiation 
    for synchronous data transfers for a specific SCSI device. This 
    parameter is provided for those devices that cannot handle the SCSI
    synchronous data transfer negotiation properly. The driver parameter 
    is used as follows:

        /!s=hba(target,lun)[,hba(target,lun)...]

        where: hba    = adapter number assigned by SIM18_3.DSK/SIM18_4.DSK	
               target = SCSI ID of device
               lun    = LUN of device

        example:      
            :load sim18_3 /!s=0(1,0)

    The above will disable the negotiation for synchronous data transfer to
    the drive with SCSI ID 1 and LUN 0 on adapter 0. 

    WARNING: The above driver parameter must be used if and only if the SCSI 
    device was not found by the SCSI I/O module during its initialization. 
    If this driver parameter is used for a SCSI device found during 
    initialization, the server may fail.
		


NEW FEATURES
------------

    1)  Support is provided for CDROM drives via Novell's CDROM.NLM,
        CorelSCSI!, or CorelSCSI! Pro.

    2)  An ASPI Interface is provided to support Novell's SBACKUP.NLM
        Cheyenne's Arcserve 4.0 and Corel's CorelSCSI!/CorelSCSI! Pro.

    3)  Support is provided for Removable, Multifunction, and Magneto
        Optical drives (including 1024 byte-per-sector media)



HELPFUL HINTS
-------------

    1)  If you want to have the disk drivers load automatically, you must
        add the appropriate load commands in your STARTUP.NCF file.  Please
        note that the FUTXPT.DSK module is automatically loaded by the SIM
        module.

    2)  CDROM Users: The CDROM.NLM provided on this diskette (supplied by
        Novell, Inc.) must be loaded after the Future Domain disk driver has 
        been loaded and SYS has been mounted.  Type "CD HELP" for a list of 
        available CDROM commands.

    3)  Please note that you do not have to load the FUTASPI.DSK driver
        unless you load an NLM that requires an ASPI interface.  Novell's 
        CDROM.NLM does NOT require an ASPI interface.  However, Novell's
        SBACKUP.NLM and Corel's CorelSCSI!/CorelSCSI! PRO do require an ASPI
        interface.

    4)  On NetWare 386 v3.11 servers, please be sure to unload disk drivers 
        before bringing down the server and starting it back up without 
        rebooting.

    5)  When running NetWare for OS/2 (That is... running a Novell v4.X 
        server under OS/2, NOT the OS/2 Requester), please be sure that the
        OS/2 ADD for the adapter is not loaded.  If both the OS/2 ADD and the
        NetWare SIM are loaded, there will be two drivers attempting to
        utilize the same memory base, I/O base, and/or IRQ.

        Please note that NetWare for OS/2 is only supported for NetWare 386 
        V4.X and OS/2 V2.1.

    6)  Some older 486 processors have a hardware problem.  In order to get 
        around the bug in the chip, Intel recommended a work around to 486 
        system designers.  This workaround, however, will cause the message 
        "lost interrupt dectected by hardware controller" or "spurious 
        interrupt detected by hardware controller" to be displayed when our 
        driver is loaded.  There is nothing wrong with your system, it will 
        run fine.  You can tell NetWare not to complain about these lost 
        interrupts with the SET command from the server console or 
        STARTUP.NCF file. 

            SET DISPLAY LOST INTERRUPT ALERTS = OFF
            SET DISPLAY SPURIOUS INTERRUPT ALTERTS = OFF



LIMITATIONS
-----------

     1024 byte-per-sector media support is NOT provided for the TMC-7000EX
      controller.



CUSTOMER SERVICE
----------------
	
    To contact our Customer Service Department please call :

	Future Domain Corporation
	Customer Service
	2801 McGaw Avenue
	Irvine, CA 92714

	Phone:  (714) 253-0440
	FAX:    (714) 253-0429

	Monday - Friday, 8AM to 5PM PST
