******************************************************************** MIBVIEW Installation Notes for the Microdyne NE10/100 ISA Adapter Updated February 1997 ******************************************************************** Introduction ============ NODEAGNT and MIBVIEW are companion programs that implement Simple Network Management Protocol (SNMP) for the NE10/100 ISA adapter in a DOS or Windows 3.1 environment. NODEAGNT is a Terminate and Stay Resident (TSR) program that is loaded with the network protocol stack to provide an SNMP agent. MIBVIEW is a DOS/WINDOWS program that allows the Management Information Base (MIB) information for the NE10/100 ISA adapter to be displayed. Applicable Hardware ======================= NODEAGNT and MIBVIEW are designed to work with the NE10/100 ISA adapters only. NODEAGNT will not load without an NE10/100 ISA in the PC, and MIBVIEW will not work without NODEAGNT resident. Installation and Setup ====================== The following sections will set up the "user" information for SNMP, and will allow NODEAGNT to be loaded and execute correctly. First copy all of the files in this directory to a directory on your PC. The NODEAGNT and MIBVIEW programs share information, and will not execute properly if they exist in different directories. SNMP - TCP/IP information ------------------------- Start MIBVIEW from the DOS command line, or through the WINDOWS program manager. Select CONTINUE in response to the MIBVIEW COULD NOT EXECUTE... alert. Enter the information in the Create/Modify Configuration File window. The Host ID addr, Subnet Mask, and Gateway TCP/IP addresses are required, all other information is optional. After all relevant information has been entered (contact your network administrator if you have any questions), select SET to save the information, and select OK in the confirmation window. Select either Reboot or Continue in the Rebooting under... window. When Continue is selected, exit MIBVIEW through the close button (select the upper left '-' button, then select close. Network configuration files --------------------------- Determine which Network Configuration file must be modified. If Novell ODI protocol is being used, the configuration file is NET.CFG. If Microsoft NDIS protocol is being used, the configuration file is PROTOCOL.INI. A. NET.CFG - NETWARE configuration file Edit NET.CFG to ensure that "FRAME ETHERNET_II" is listed under the "LINK DRIVER NE100I" section. Add a section "Protocol NS_SNMP" with the single line "bind #n" where 'n' is the "logical board" number of the "FRAME ETHERNET_II" line (The first FRAME... line is logical board 1, the second FRAME... is logical board 2 etc.). To Enable NODEAGNT, it must be loaded after LSL and NE100I, in the batch file that loads the network protocol stack. Edit the network start batch file to add a line with the full path name to NODEAGNT (e.g. C:\MIBVIEW\NODEAGNT). B. PROTOCOL.INI NETBIOS configuration file Edit PROTOCOL.INI to add the following lines [NODEAGNT] Drivername=NS_SNMP$ BINDINGS=NE100I If WINDOWS 3.10 is being used, add the following line to the [protman] section (or create one should it not exist). DYNAMIC=YES If WINDOWS 3.11 is being used, remove the 'DYNAMIC=YES' line from the [protman] section if it exists. If there is an existing TCP/IP protocol stack (such as PC/TCP or Chameleon NFS), the following entries are also required in the protman section before the DYNAMIC=YES line (WINDOWS 3.10 only). Drivername=PROTMAN$ PRIORITY=NODEAGNT If another protocol stack is already initialized as 'PRIORITY' the Node Agent must be given priority by adding it to the PRIORITY command before the other protocol. To enable NODEAGNT, it must be loaded from your network startup batch file (normally AUTOEXEC.BAT). For WINDOWS 3.10, NODEAGNT must be loaded before the "NETBIND" command. For WINDOWS 3.11, NODEAGNT must be invoked after the "net init" command, and before the "net start" command. Add a line to the batch file with the full path name to NODEAGNT (e.g. C:\MIBVIEW\NODEAGNT).Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.