SNMPc 4.0 Software Development Kit
August 3, 1995
The SNMPc SDK is a collection of documents, libraries and source
code samples that can be used to create SNMPc application programs.
In addition to these interfaces there are a number of customization
features that are described in "Chapter 7, Customizing SNMPc",
in the SNMPc 4.0 Reference Guide.
General information on customizing SNMPc and developing SNMPc
applications is provided in docs/intro.doc. The following options
are available for SNMPc application development:
1. Vendor Snap-In Installation (install.txt)
-----------------------------------------
The SNMPc 4.0 installation program can install third party
"vendor application" disks.
2. WinSock DLL for TCP/IP-only requirements (winsock.doc)
------------------------------------------------------
Applications developed for WinSock will work with most TCP/IP
stacks, including those supplied by Windows/95 and Windows/NT.
SNMPc 4.0 includes the Distinct WinSock DLL.
The evmail directory contains a sample WinSock program that
forwards mail messages to a TCP/IP POPD (email) server.
3. WinSNMP DLL for SNMP-only requirements (winsnmp.doc)
----------------------------------------------------
Applications developed for WinSNMP will work with WinSNMP
stacks supplied by many TCP/IP and some Manager products,
including HP OpenView, PC/TCP, and Distinct. SNMPc 4.0
includes a WinSNMP DLL.
The testsnmp directory contains a sample WinSNMP test program
that requests device system info and receives traps.
4. Windows DDE Messages for SNMPc access (dde.doc)
-----------------------------------------------
SNMPc operates as a Windows DDE server. It has a full set of
DDE functions for SNMP operations, MIB lookup, SNMPc map and
other configuration changes, and SNMPc menu execution.
The ddetest directory contains a sample program that allows
you to execute any DDE function.
The bridge directory contains a sample program that downloads,
edits, and uploads a bridge forwarding database.
5. Castle Rock DDELINK DLL for SNMPc access (dde.doc)
--------------------------------------------------
The DDELINK DLL is a function call interface to SNMPc DDE.
it is much simpler to use than DDE messages and allows multiple
outstanding DDE requests.
The linktest directory contains a sample program that allows
you to execute any DDE function. This program is functionally
the same as ddetest, but is significantly shorter and simpler.
The rmon directory contains sample programs that create, edit,
and delete entries in the RMON MIB alarm group.
6. Excel macros (dde.doc)
----------------------
The SNMPc DDE messages can be accessed using Microsoft Excel
and other DDE aware programs.
The excel directory contains a sample Excel macro for displaying
SNMP tables and graphs.
7. Event processing programs (dde.doc)
-----------------------------------
SNMPc can execute a program when an event occurs. SNMPc passes
the node name and event log message as program arguments.
The pager directory contains a sample program that forwards the
SNMPc node name from an event to a numeric pager device.
8. HubView device GUI script language (bitview.doc)
------------------------------------------------
The SNMPc HubView program uses HubView Device Definition files
to display an image of an SNMP device and custom menus specific
to the MIBs (standard or private) implemented by the device.
HubView can display any kind of device, including single or
multi-slot hubs, bridges, and routers. Menus operate on the
selected port or slot and can display MIB tables, graphs,
or charts; edit tables; set variables; run programs; etc.
HubView displays a fairly generic image of the device, with
a limited number of built-in port types, and a generic
device background image.
There are numerous sample HubView scripts in the SNMPc 4.0
hubview directory.
9. BitView device GUI script language (bitview.doc)
------------------------------------------------
The SNMPc BitView program uses BitView Device Definition files
to display an image of an SNMP device and custom menus specific
to the MIBs (standard or private) implemented by the device.
BitView can display any kind of device, including single or
multi-slot hubs, bridges, and routers. Menus operate on the
selected port or slot and can display MIB tables, graphs,
or charts; edit tables; set variables; run programs; etc.
BitView is much like HubView, but it can display a detailed
bitmapped image of the device. Every element of the view is
specified by bitmaps in the definition file. BitView can
also have any number of changing images (e.g., LED's, meters).
BitView menus are context-sensitive to allow a different set
of menus for different port or slot types. BitView also
has command "hot-spots" that can be double clicked to perform
an action.
There are numerous sample BitView scripts in the SNMPc 4.0
hubview directory.
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.