         ͻ
                                                            
                    Universal 10/100VG LAN Adapter          
            (C) Copyright PDS, 1995. All Rights Reserved.   
                                                            
         ͼ


The Universal NDIS 2.01 drivers are self-configuring, which means no additional
PROTOCOL.INI parameters need to be specified beyond the "Drivername" line.
The driver will locate the adapter and read in its configuration.


To install the Universal NDIS 2.01 driver for DOS, follow the instructions 
below:

1.  Install the networking product onto the PC.

    Completely install the networking product (i.e SUN PC-NFS, FTP PC-TCP,
    etc).

    NOTE: If the product requires that a driver be given and it cannot read
	  the Universal NDIS 2.01 driver off this disk, then pick any other 
	  driver to install.  In steps 3 and 4 below, when editing the files 
	  change all occurances of that driver's name to VGNDIS.


2.  Copy the NDIS 2.01 driver from the Driver Disk.

    Create a directory on the computer.  For example,

	C:
        MKDIR \NDIS

    Copy the NDIS 2.01 driver file from Driver Disk to this directory.
    For DOS computers with the Driver Disk in floppy drive A:

        COPY A:\NDIS2\VGNDIS.DOS C:\NDIS


3.  Edit the PROTOCOL.INI file with a text editor.

    Locate the PROTOCOL.INI file within the networking product's directory
    created in step two.

    The PROTOCOL.INI file must include a section describing the LAN adapter
    (the VGNDIS section) and a section describing each of the network
    products being run.  Each network product section must include a
    a BINDINGS statement.

    The PROTOCOL.INI file included in the NDIS2 directory of the Driver 
    Disk includes all the information describing the LAN Card. Here is
    a copy of the file:

        ; Universal 10/100VG LAN Adapters
            DRIVERNAME = VGNDIS$
        ;    SLOT = 1
        ;    IOADDRESS = 0x300
        ;    PCI=1


    All the PROTOCOL.INI driver parameters except "drivername" have been
    commented out (using the ";" character) and are shown here only to
    illustrate the defaults. Only "DRIVERNAME" is mandatory. All the
    PROTOCOL.INI parameters, and their values, are listed in the
    "PROTOCOL.INI Parameter Definitions" note below.

    The PROTOCOL.INI file must be merged with the networking product's
    PROTOCOL.INI.  BINDINGS statements must be created to identify the
    Universal 10/100VG NDIS 2.01 driver to the networking product's protocol
    modules.

    An example PROTOCOL.INI file that supports FTP PC/TCP might look like
    the following:

	 ; FTP's software
	 [PKTDRV]
	 drivername = PKTDRV$
	 intvec = 0x65
	 bindings = VGNDIS                         <--- Add this line

	; Universal 10/100VG LAN Adapter
	 [VGNDIS]                                  <--- Add this line
	 DRIVERNAME = VGNDIS$                      <--- Add this line


4.  Modify Your CONFIG.SYS File.

    The CONFIG.SYS file must be modified to include DEVICE statements
    for the VGNDIS driver, and each of the drivers for the applications
    you are using, and for the PROTMAN.DOS (or PROTMAN.OS2, as appropriate)
    file.  Here's an example portion of a DOS CONFIG.SYS file that supports
    the LAN Adapter and FTP PC/TCP version 2.2:

	REM************************************************
	REM   FTP software, run startftp after bootup   ***
	REM************************************************
	DEVICE = C:\FTP\PROTMAN.DOS /I:C:\FTP
	DEVICE = c:\FTP\DIS_PKT.GUP
	REM****************************************
	REM  Universal 10/100VG LAN NDIS 2.01 DRIVER  ***
	REM****************************************
	DEVICE = C:\NDIS\VGNDIS.DOS

    Please refer to FTP PC/TCP's Installation Manual for details.

    Notes on the PROTMAN file:

    - PROTMAN must be loaded before the adapter driver and the networking
      drivers; that is, the DEVICE statement for the PROTMAN file must be
      located before the other network DEVICE statement.

    - The "/I:" parameter in the DEVICE statement for the PROTMAN file
      identifies the path to the PROTOCOL.INI file.  In the example above,
      PROTOCOL.INI is located in the directory C:\FTP.


5. Reboot Your Computer and Execute NETBIND.EXE

     To activate your modified PROTOCOL.INI and CONFIG.SYS files, you must
     now reboot your system.  When the boot process is complete, run
     NETBIND.EXE.  This file is included with your networking product
     software.  NETBIND must be run each time your system is booted, so it
     is recommended that you include NETBIND.EXE in your AUTOEXEC.BAT file.



PROTOCOL.INI Parameter Definitions
==================================

Below is an explanation of each PROTOCOL.INI parameter for the Universal
10/100VG LAN Adapter.

The only parameter that must be present is the "DRIVERNAME".

If more than one Universal LAN Card is installed, the location of each must
be specified:

   Universal 10/100VG/EISA use the "SLOT" parameter
   Universal 10/100VG/ISA use the "IOADDRESS" parameter


DRIVERNAME
     range:[VGNDIS$, VGNDIS2$, VGNDIS3$, VGNDIS4$]

   Identifies the LAN adapter driver.  Use a unique value from the range
   indicated for each Universal LAN adapter installed in your computer.  If you
   had two Universal LAN Cards installed, you would use VGNDIS$ for the first one,
   and VGNDIS2$ for the second.


SLOT
   range: [1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]

   This parameter is applicable to the EISA version of 10/100VG only.
   If present, indicates the EISA slot in which the Universal 10/100VG/EISA
   LAN adapter is installed.  If the adpater is not in that slot, the driver 
   will exit with an error.

   If more than one adapter are installed in the computer, this parameter 
   must be set for each EISA adapter installed.

IOADDRESS
   range: [0x200, 0x240, 0x280, 0x2C0, 0x300, 0x340, 0x380]

   This parameter is applicable to the ISA version of 10/100VG only.
   If present, indicates the IO base address in which the 
   Universal 10/100VG/ISA LAN adapter is installed.  If the adpater with 
   this IO address is not present, the driver will exit with an error.

   If more than one adapter are installed in the computer, this parameter 
   must be set for each ISA adapter installed.


