3.4 Installing Under SCO OpenServer 5

Note: Install your AG Connect boards in your system before installing the software. (See Chapter 2 to learn how to do this.) Make a note of the base I/O addresses at which you installed the boards. The installation program will prompt you for these addresses.

1. If you are installing over earlier versions of AG Connect or AG Connect With Ringing driver software, remove the earlier version and rebuild the kernel before you install the new software.
   See section 3.4.2 to learn how to remove driver software from your system.

2. If you plan to install SwitchPath, do so now before installing the AG Connect board driver software.
   To learn how to install SwitchPath, see your SwitchPath documentation.

3. Access a command prompt, and log in as root.

4. Insert the AG Connect board installation diskette into your floppy disk drive.

5. Invoke the pkgadd utility by entering a command of the form:

     pkgadd -d devicename
   

   ...where devicename is the name of the floppy disk drive from which you are installing. For example:

     pkgadd -d /dev/rdsk/f03h
   

   pkgadd starts up, and displays a list of software packages available for installation.

6. Select the "agcx" package, and press Enter.
   pkgadd copies the driver software from the disk onto your system.

7. When pkgadd has finished copying files, it displays the following message:

   You will now provide the base addresses of the agcx
   Boards you are installing in your system.  When you are prompted for
   a base address, a list of possible choices will be given.
   
   If installing more than one board into your system,
   the choices already selected during this installation will be
   marked, and the device node name that will be used to access the
   agcx board is listed.
   
   Enter c to continue or enter q to quit:
   

8. Enter "c".
   pkgadd displays a menu of base I/O addresses.

9. Mark the addresses of the AG Connect boards in your system.
   To select an address, type its number. The menu reappears with the address marked.
   As you select addresses, make a note of the order in which you select them. The install program assigns device numbers to your boards based on the order in which they are selected. When you create your application using SwitchPath or the SW Utility, you will use these numbers to refer to your boards in software.
   For example, if you mark address 0x0640 first and then address 0x2140, the board at address 0x0640 is assigned device number 0. The board at address 0x2140 is assigned device number 1.

10. When you have selected the addresses of all of your boards, enter 0.
    pkgadd displays this message:

    1.  MU-law
    2.  A-law
    Please select idle code, q to quit.
    

    pkgadd is asking you to select an encoding scheme. The encoding law you select applies to every AG Connect board in the system.

11. Enter "1" or "2" to select the encoding scheme to use.
    pkgadd displays this message:

    Rebuild the kernel with the AG Connect Board device driver now? (y/n)
    

12. Enter "y".
    pkgadd prepares to rebuild the kernel. It displays this message:

    Do you want this kernel to boot by default? (y/n)
    

13. Enter "y".
    pkgadd causes the kernel to be rebuilt.
    Note: pkgadd may warn you that it is about to overwrite newer versions of files on your system with older ones. This warning may appear even if the files you are installing are actually newer than the ones on your system. This is because files installed with earlier versions of the install script were marked with the installation date, not their creation dates. Later versions of the script preserve the creation date.
    
    This warning may appear particularly if you have installed SwitchPath. If you have SwitchPath 1.1 or earlier, direct pkgadd to overwrite the "newer" files. If you have a later version of SwitchPath, do not overwrite files.
14. When pkgadd has finished rebuilding the kernel, it displays this message:

    Do you want the kernel environment rebuilt? (y/n)
    

15. Enter "y".
    pkgadd sets up the new kernel environment.

16. Shut down your system, and reboot.
    The driver will not be available until you reboot.

1. Access a command prompt, and log in as root.

2. Execute the confdrvr shell script by entering this command:

   sh /opt/nms/agcx/drv/confdrvr
   

   confdrvr starts up. The following message appears:

   You will now provide the base addresses of the agcx
   Boards you are installing in your system.  When you are prompted for
   a base address, a list of possible choices will be given.
   
   If installing more than one board into your system,
   the choices already selected during this installation will be
   marked, and the device node name that will be used to access the
   agcx board is listed.
   
   Enter c to continue or enter q to quit:
   

3. Enter "c".
   confdrvr displays a menu of base I/O addresses.

4. Mark the base I/O addresses of ALL boards in your system, just as you did during the initial install procedure. (See section 3.4 for more information.)
   Note: Even if you are adding a new board to a system which already includes AG Connect boards, you must specify the base addresses of all boards. Remember the order in which you select the addresses, so you know what device number each board is given.

5. When you have selected the addresses of all of your boards, enter 0.

6. Now follow steps 11 through 16 in section 3.4 above to select a coding scheme, rebuild the kernel and reboot the system.

1. Access a command prompt, and log in as root.

2. Direct the pkgrm utility to remove the "agcx" package. To do so, enter:

   pkgrm agcx
   

   pkgrm removes the package. The following message appears:

   Rebuild the kernel now? (y/n)
   

3. Enter "y".
   The kernel build proceeds. The following message appears:

   Do you want this kernel to boot by default? (y/n)
   

4. Enter "y".
   The following message appears:

   Do you want the kernel environment rebuilt? (y/n)
   

5. Enter "y".
   pkgrm completes its tasks, and terminates.

6. When pkgrm terminates, shut down your system, and reboot.