

    Notes on CONCORD adapter software installation.

        Concord Communications provides an installation utility for
        their OPP (OSI Programmer's Package) software that includes
        installation of the NDIS driver and other files that are
        required for the NDIS driver to function correctly with the
        Concord adapters.  This utility is incompatible with the LAN
        Manager Setup program.
        
        It is not possible to produce a diskette that will be totally
        compatible with Setup at this time.  If the additional files
        are made ancillary in the xxx.NIF file, Setup only copies the
        first 9 files to the specified directories.

        In an attempt to generate a somewhat acceptable OEM Supplemental
        Driver Diskette, I have made only the NDIS driver installable
        by Setup.  The other files needed to run the NDIS driver on
        Concord adapters are provided on a separate diskette. 

        The files on the separate diskette for OS/2 are:

           Files required to work with the NDIS driver:
                \CONCORD.OS2\BIN\PTNA.SYS
                   - the hardware interface driver
                \CONCORD.OS2\CONFIG\OPP.CNF
                   - configuration file used by PTNA.SYS
                \CONCORD.OS2\CMD\OPPSTART.CMD
                   - batch file to start up Concord software
                \CONCORD.OS2\BIN\BOOTPTNA.EXE
                   - program to download code to the controller
                \CONCORD.OS2\CONFIG\PTNA.DLD 
                   - file containing data to be downloaded to the adapter
                \CONCORD.OS2\DLL\PTNABDS.DLL
                \CONCORD.OS2\DLL\CRTLIB.DLL
                   - libraries used by BOOTPTNA.EXE
                \CONCORD.OS2\LOG\.
                   - BOOTPTNA.EXE needs this directory for output

           Files required to reconfigure the adapter:
                \CONCORD.OS2\CMD\OPPCNFG.CMD
                   - batch file to run the adapter configuration program
                \CONCORD.OS2\BIN\TBXCNFG.EXE
                   - program that allows adapter configuration
                   - by modifying OPP.CNF
                \CONCORD.OS2\CONFIG\CCCUHLP.MSG
                \CONCORD.OS2\CONFIG\CCCUHLP.NDX
                   - screen files used by TBXCNFG.EXE    
        
        I suggest this diskette be "XCOPY"ied to the hard drive as is.

        ---------------------------------------------------------------
        
     OS/2 INSTALLATION
     -----------------

        The Concord NDIS driver running under OS/2 requires an 
        intermediate driver between it and the hardware (PTNA.SYS).  
        You will need to include the lines

            SET OPPDIR=C:\CONCORD.OS2
            DEVICE=C:\CONCORD.OS2\BIN\PTNA.SYS /F=\CONFIG\OPP.CNF

        before the line that loads the NDIS driver.

        Also, add
 
                "C:\CONCORD.OS2\DLL" 

        to the LIBPATH in CONFIG.SYS.

        ---------------------------------------------------------------

        In order to run the configuration utility to change the IO base
        address, DMA channel, Slot Number etc., add

                "C:\CONCORD.OS2\CMD;C:\CONCORD.OS2\BIN"

        to the PATH in CONFIG.SYS.

        The OPP.CNF configuration file included on the diskette is set
        for:

                Receive Buffer Size   = 256
                PC Interrupt          = 3
                Base Memory Address   = 0x300
                DMA Channel           = 5
                Local Network Address = 01 01 01 01 01

        These are the default settings.  
        All of the supplied boards are set with the default hardware
        settings (PC Interrupt, Base Memory Address, and DMA Channel).

        Each adapter on the network should have a unique Local Network
        Address.  So you will need to run the configuration utility
        (the OPPCNFG batch file or TBXCNFG.EXE) to modify these
        values for each adapter.

        Note: If the configuration utility should prompt you for
              PS/2 values on a non-PS/2 machine (i.e. Slot Number),
              then run the program with a -1 option.

              For example:   TBXCNFG -1

        ---------------------------------------------------------------

        The OPPSTART.CMD command file must be run before attempting to
        communicate with the adapter.  You can put the line
        
                "START /FS OPPSTART" in STARTUP.CMD
        
        or run

                "OPPSTART" from the command line.

        This command file takes approximately 30 seconds to run with
        no indication of its completion except that all 3 indicator
        lights on the adapter should be lit.  Any attempt to OPEN the
        adapter prior to this time will fail.


