SNMPc Network Manager		Version 4.1	     July 26, 1995

Castle Rock Computing, Inc.
20863 Stevens Creek Blvd., #530
Cupertino, CA 95014 USA

Phone:  (408) 366-6540           Fax:    (408) 252-2379
BBS:    (408) 252-2670           e-mail: support@castlerock.com 
WWW:    http://castlerock.com/   FTP:    castlerock.com/198.92.129.1


======================================================================
CONTENTS

1.  TCP/IP PACKAGES
2.  SNMPC.INI options
3.  KNOWN PROBLEMS

======================================================================
1.  TCP/IP PACKAGES

The following summarizes our testing with various TCP/IP packages.
This is an indication of how SNMPc and the TCP/IP packages operate
together and does not imply any analysis of the vendor's apps.

Vendor            Low Mem   Stability  IP Ping

NetManage         OK        OK         Yes
Distinct          OK        OK         Yes
MS 32 bit TCP/IP  OK        OK         No
Windows/NT        N/A       OK         No
WRQ Reflections	  OK	    OK	       Yes  - requires WRQ patch

Novell            Poor      Poor       yes
Wollongong        Poor      OK         No
Trumpet           Poor      Poor       No

MS 16 bit TCP/IP: Crashes with SNMPc - not useable
Sun PC/NFS, FTP, PC/TCP, Frontier:  Not tested

======================================================================
2.  SNMPC.INI

The following snmpc.ini entries in the [SNMPcConfig] section can be 
changed using a text editor.

	; allow use of IPX network
	UseIPX=Yes	;  or No

	; start TrendWatch application
	StartTrendWatch=Yes  ; or No

	; poll overides for MIB table displays
	TablePoll=10	; 0 means prompt
	GraphPoll=1	; for graphs & charts. 0 means prompt

	;
	; time to do automatic erase/backup of history log file
	; when using this feature, set Max History Bytes to 0
	;
	BackupLogFileTime=11:30:00	; hh:mm:ss

The following snmpc.ini entries in the [AutoDiscovery] section can be
changed with a text editor:

	;
	; allow sequential polling for 'N' addresses around each 
	; discovered address.
	;
	NumSequentialSteps=N

======================================================================
3.  KNOWN PROBLEMS

    1.  Distinct TCP/IP is included FREE.  We have limited support 
        capabilities for Distinct TCP/IP and Distinct will not support
        this FREE software supplied by us.  

        If you have installation or configuration problems with Distinct,
        AND you are using Windows for Workgroups, we suggest you download 
        the Microsoft 32 bit TCP/IP stack from the Microsoft FTP or WEB
        sites.  The MS TCP/IP stack is also free, but it is supported by
        Microsoft.

        We also highly recommend the NetManage Chameleon product.  While
        this is not a free product, it performs well and is very easy
        to install.

    2.  Sometimes the message "Can't start TRAPRX" is displayed when 
        starting SNMPc.  Stop SNMPc, wait 20 seconds and restart SNMPc.

    3.  TrendView does not exit automatically when SNMPc exits.

    4.  The external IPX subsystem uses about 43K of low memory.  If 
        you do not need to use IPX with SNMPc then do not set the
        "Discover IPX Nodes" check box in the Discovery Setup dialog box.

    5.  Performance and low memory usage is very poor with Novell LAN
        Workplace, Wollongong, and Trumpet TCP/IP stacks.  We do not
        recommend these stacks.

    6.  IP Ping polling does not work with some TCP/IP stacks (including
        Windows/NT and Windows MS TCP/IP).  Even though you can use the
        built-in "ping" command, these stacks do not provide a program
        API for Ping requests (RAW sockets).

    7.  In many cases Discovery will not find all nodes on your network.
        You can enable sequential polling to discover more nodes by 
        setting the following variable in the [AutoDiscovery] section
        of SNMPC.INI:

                ; 
                NumSequentialSteps=5

        In this case Discovery will sequentially poll nodes with IP 
        addresses up to 5 less than and 5 more than any discovered node.

        WARNING: you should not set this number too high.  Also, sequential
        polling works very poorly on Novell and Distinct TCP/IP stacks 
        because of delays induced during ARP requests to bad addresses.
        We do not recommend you use sequential polling on these stacks.
