    ====================================================================
    Release Notes
        IntelliPort(tm) II Driver
        for Novell(R) NetWare(tm)


        July 14, 1993                                   P/N 9-01113
    ====================================================================

    ------------
    Introduction
    ------------

    The IntelliPort II Driver for Novell NetWare is a Novell-certified
    product that runs on Novell's NetWare Server, version 3.11.  The
    IntelliPort II driver conforms to Novell's Asynchronous I/O ser-
    vices (AIO) and is compatible with all AIO-compliant applications,
    including NACS.

    This release note assumes you have some experience in administering
    a NetWare network.

    We recommend that you install the IntelliPort II hardware before
    the IntelliPort II software.

     +--------------------------------------------------------------+
     | Important!  To avoid damage to hardware, always turn off the |
     | power to the system before you plug or unplug IntelliPort II |
     | cables or components.                                        |
     +--------------------------------------------------------------+


    ---------------------
    Hardware Installation
    ---------------------

    This section provides a brief version of the IntelliPort II hard-
    ware installation procedures.  For more information, see the
    IntelliPort II Hardware Reference Guide.


    System Dependencies

	The IntelliPort II driver for Novell NetWare imposes the
	following dependencies:

	    - One IntelliPort II controller may be installed in a
	      single NetWare server.

	    - Only the IntelliPort II EXpandable ISA controller is
	      certified for use in a NetWare server.  However,
	      Computone has successfully tested all IntelliPort II
	      hardware with these drivers.

	The NetWare Server software imposes other restrictions, as
	follows:

	    - Applications may impose further restrictions; for
	      example, NACS provides support for 2, 8, or 32 ports.
	      Ports not used by one application are available to other
	      applications.


    Installing in an ISA System

	To install an IntelliPort II controller in an ISA host, follow
	these steps:

	    1. Disconnect the power to the ISA host system and any
	       connected peripheral devices.  Remove the system cover
	       and expansion slot cover.

	    2. Set the base I/O address DIP switches on the IntelliPort
	       II controller, as described in Chapter 2 and Appendix B
	       of the IntelliPort II Hardware Reference Guide, to a
	       block of currently free I/O addresses.  Write down the
	       chosen I/O address range, in hexadecimal, in the Hard-
	       ware Configuration Log in the IntelliPort II Hardware
               Reference Guide.

	    3. Secure the controller in a 16-bit expansion slot.  Write
	       down the slot number in the Hardware Configuration Log
	       in the IntelliPort II Hardware Reference Guide.

	    4. Replace the system cover.

	    5. Connect external interface modules to the IntelliPort
	       II controller, if any.

	    6. Reconnect any other peripheral devices disconnected in
	       step 1.

	    7. Power on the system and any attached devices.

	Proceed to the section "Software Installation" for instructions
	on installing the driver software on the NetWare server.
    
    
    ---------------------
    Software Installation
    ---------------------

    To install the IntelliPort II software drivers on the NetWare
    server, follow these steps:

	1. Log in as Supervisor to the NetWare server that has the
	   IntelliPort II controller installed.

	2. Insert the IntelliPort II software driver diskette in
	   any available floppy drive.

	3. Copy the aioctone.nlm file from the driver diskette to
	   any directory in the path for the NetWare LOAD command.
	   We recommend the directory sys:system.

    Proceed to the next section, "Starting the Driver," for informa-
    tion on running the driver and configuring the server to automat-
    ically start the driver.

    -------------------
    Starting the Driver
    -------------------

    You can start the IntelliPort II software driver either manually
    from the server console, or automatically by placing a command in
    the autoexec.ncf file.  You may want to start the driver manually
    first, to verify proper operation before changing the autoexec.ncf
    file.


    Manual Startup Procedure

	To start the IntelliPort II software driver manually from the
	server console, follow these steps:

	    1. Log in to the NetWare Server console.

	    2. Type the following command at the Server console:

		    load aioctone.nlm

	       port= specifies the base I/O address, in hexadecimal,
	       from the Hardware Configuration Log in the IntelliPort
	       II Hardware Reference Guide.  If you omit the port=
	       parameter, the driver prompts you for the base I/O ad-
	       dress.  The I/O address must agree with the DIP switch
	       settings on the IntelliPort II controller.

	       int= specifies the interrupt, as a single hex digit,
	       assigned to the IntelliPort II controllers (IRQ A is
	       usually available).  If you omit the int= parameter,
	       the driver prompts you for the IRQ.


    Automatically Starting the IntelliPort II Driver

        To set up the NetWare server to automatically start the Intelli-
        Port II drivers, add the following line to your autoexec.ncf
        file:

    	    load aioctone.nlm port=I/O_addr int=IRQ

	port= specifies the base I/O address, in hexadecimal, of the
	controller.  Use the I/O address from the Hardware Configura-
	tion Log in the IntelliPort II Hardware Reference Guide.  If
	you omit the port= parameter, the driver prompts you for the
	base I/O address.  The I/O address specified must agree with
	the DIP switch settings on the IntelliPort II controller.

	int= specifies the interrupt, as a single hex digit, assigned
	to the IntelliPort II controller.  If you omit the int= para-
	meter, the driver prompts you for the IRQ.


    Example autoexec.ncf File

        The following listing shows an example autoexec.ncf file that
        contains commands to load the Computone drivers.
    
        ; standard for NetWare servers
        server name CENTRAL
        ipx internal net 426
        mount all
        ;
        ; the following command is required if using NACS security
        set allow unencrypted passwords=on
        ;
        ; the following commands are required for commexec
        load nmagent
        load clib
        load spxs
        load btrieve -P=4096 -F=20 -H=60 -L=20 -C
        ;
        ; load the AIO and Computone drivers
        ; (replace the port and int values as needed)
        load aio
        load aioctone port=0308 int=a
        ;
        ; load LAN drivers, etc. at this point as needed
        ;
        ; start the Communication Executive
        ; (this can automatically load NACS or other applications)
        load commexec
    
	The system assigns port 0 to the controller, and continues in a
	contiguous block of port addresses.  For example, if you are
	installing a 16-port controller, the system assigns ports 0
	through 15 to the IntelliPort II.


    Assigning Ports to Applications

	To assign IntelliPort II ports to an AIO application, see the
	documentation for that application.  Note that some applica-
	tions, such as NACS, limit the number of accessible ports.  You
	can assign unused ports to other AIO applications.


    -----------------
    Application Notes
    -----------------

    If you are using a terminal emulation application that expects a
    host system to echo typed characters, echo delays are based on
    factors such as network loading and host loading.  Heavy load
    conditions result in noticeable delays before echoed characters are
    displayed.

    If delays become intolerable, you can configure some PC applica-
    tions to echo characters locally.  However, this causes problems
    with interactive programs such as screen-oriented editors which
    assume the host controls character echo.


    -----------------
    Known Limitations
    -----------------

    The following are known limitations of the IntelliPort II driver
    for Novell NetWare:

    - Under extremely heavy load conditions, high speed input (e.g.,
      115,200 bps) may occasionally lose characters regardless of flow
      control settings.

    - If you install an eight-port IntelliPort II-EX expansion module,
      the driver reports sixteen ports with eight ports unavailable or
      down.


    ---------------
    Troubleshooting
    ---------------

    If you are having a problem, check the following items before
    calling Computone Technical Support:


    - Server hangs at startup after installing the controller.
    
      This is usually the result of an I/O address conflict between the
      IntelliPort II controller and some other hardware in the system.
      Shut down the system, remove the IntelliPort II controller,
      select a new base I/O address, then re-install the controller and
      start the server again.


    - Server displays the message "Interrupt number is ALREADY in use"
      when you try to start the driver.
    
      This means you have assigned an IRQ to the IntelliPort II driver
      that conflicts with another driver.  Change the IRQ assigned to
      one of the drivers.


    - Server displays the message "Failed to allocate resource tags" or
      "Failed to register driver" when you try to start the driver.
    
      This usually indicates a tight-memory situation.  Remove other
      load modules from server memory or add more memory to the
      server.
    

    - Driver displays the message "Board not found" or "iiSet Address
      failed" when you try to start the driver.
    
      If you have installed the IntelliPort II controller, make sure
      you have specified the right I/O address.
    
      If the I/O address is set properly, make sure the controller is
      properly seated in its slot.


    - Character echo is unreliable.
    
      Some versions of NACS have bugs that can cause this problem.
      Upgrade to the latest version of NACS.
    
