
SAPList V1 displays Novell IPX transmitted SAP information.


SAPList V1 is a utility which displays SAP information from a Novell based
network.  All services are logged & displayed, then aged with color-coding
to indicate the status of the SAP entry.  The entries may be sorted in several
ways, and the display may be restricted to SAP entries of a particular
status.  The only limit to the number of entries is the available memory
of the machine.





SAPList is written in Visual Basic 3 & Microsoft Visual C 1.5.  It requires
the usual VB .DLL and Netware .DLL files present in the normal manner.

If you put SAPLIST.DLL in the same directory as SAPLIST.EXE, be sure 
your icon makes the current directory the one in which the files are stored.
Otherwise, SAPLIST.DLL should be put in your PATH somewhere (Windows
directory is fine).

SAPList requires  VBRUN300.DLL and a Novell 3.X Windows client
(must include NWIPXSPX.DLL) to run.  If you have both, simply 
run SAPLIST.EXE.  If not, install them, then simply run SAPLIST.EXE.

SAPList is pretty self-explanatory, each SAP will be displayed as it is
received.  As the SAP ages, its color will change.  From 0 to 60 seconds, 
the SAP entry will be green, yellow from 65 to 120, and red from 120 on.
These times are a little off from Novell specs but not too much.  SAPs are
never removed from the list.

You can change the sort order at any time.  The Show option 
will filter the display of SAP entries by their age.  You may notice some
inconsistencies in the operation of the scroll bar when using any of the
restrictive Show settings.  This is because SAPLIST has to plow through
the SAP entries finding ones to display given the Show criteria.  Since the 
display is not showing each SAP, a given Scroll bar change won't
necessarily mean an equal movement down the SAP list.  The Scroll bar limits
are functions of the total number of services in the list, consequently, 
large scroll bar changes may cause funcky scrolling.



There are two configuration items;

1. The # of receive ECBs.  Generally, 10 or so is OK.  Please refer to Novell
   IPX Programming docs for information on ECBs.

2. The number of packet buffers.  This should be pretty high, 300+ on a big
   network.  These buffers queue received SAPs untill SAPLIST has a chance to 
   read them.  Since Windows does such a wonderful job (ack!) of handling
   real-time activity, there needs to be quite a few of these to buffer
   heavy SAP loads while Windows is busy elsewhere.

If you change these items, restart SAPLIST to have them take effect.


SAPList can soak up quite a bit of memory; > 4megs on a busy network!


Although I haven't run it on anything but Win 3.X, SAPLIST <might> run
on 95 or NT.  Good luck!


There are still a few rough edges in the software, but nothing fatal.  The
source is included, so please tweak...



SAPList is fully public domain, and may be distributed in any form.



I wrote this program as an excercise with the Novell SDK & thought is was
useful enough to upload.  I am not going to assume a support, bug-fix 
or maintenance role.  However if you have a cool idea or find problems, 
send a note & I'll put in your fix if/when I have time.  



Greg Menke

(301)903-3692

Greg.Menke@hq.doe.gov

