This is a first crack at a Beholder II, The Next Generation FAQ.
-------------------------------------------------------------------
Q1: Where can I get btng?

A1: via anonymous ftp to dnpap.et.tudelft.nl.  Look in the directory
    /pub/btng. The main files you need are:

    	. btngexe.zip		btng executables
	. btngsrc.zip		btng source code
	. btng.faq		this file
-------------------------------------------------------------------
Q2: What is btng?

A2: bntg stands for 'Beholder - The Next Generation'. It is the latest
    member of the family of network measurement software
    created by the DNPAP group of the Technical University Delft, the
    Netherlands.

    btng consists of 

		- beholder.exe, an RMON compliant network monitor
    		  running on an OS/2 platform. This monitor
		  includes its own UDP/IP stack and SNMP
		  software.
		- neus.os2, an NDIS interface required by
		  beholder.exe
		- stat.exe and info.exe, two OS/2 Presentation
		  Manager applications that display information
		  collected from a running beholder.exe.
		  The SNMP data can be collected trough UDP and
		  through named pipes.
		- the tricklet library consisting of snmp-get.exe,
		  snmp-set.exe and snmp-tbl.exe. This SNMP tools
		  can collect data from SNMP devices such as
		  a running beholder.exe.
		- cfg2ini.exe and ini2cfg.exe, two utilities
		  needed to created the .ini files needed by
		  the other btng programs.

		  
    The beholder.exe program currently can only collect data from
    an Ethernet network.
-------------------------------------------------------------------
Q3: Can I get the source code?

A3: Yes you can. As of btng, the DNPAP group has descided to
    distribute source code with the programs it releases for
    public use. 

    We put no restrictions on the use of the source code, except 
    for the requirement that every product or service that
    uses the btng or (part of) its source code should include
    a visible reference to the DNPAP group, Technical University
    Delft.

    We do not accept responsibility for the use of the btng
    executables or its source code.
-------------------------------------------------------------------
Q4: On what platforms does btng run?

A4: btng runs on any PC that runs OS/2 (version 1.3 or 2.x) and
    a communication package like IBM TCP/IP 1.2, IBM Communication
    Manager or Microsoft Lanmanager.
    Since btng includes its own UDP/IP and SNMP software, no
    other communication software is required, except for
    the NDIS interface.

    To operate correctly, btng needs its own network interface card,
    it can not share this card with an other communication package
    like TCP/IP 1.2, the Communication manager or Lan Manager.
    If you want your OS/2 station to run you such a package at the
    same time as btng, you will need two  network interfaces in
    your PC.

    The tools included in the btng package (cfg2ini, ini2cfg, snmp-get
    snmp-set, snmp-tbl) can also be compiled in a UNIX environment
    using the latest GCC compiler. This has been tested in a SUNOS
    environment.

-------------------------------------------------------------------

Q5: OK, I have the btngexe.zip file, what do I do now?

A5: unpack it and read doc/install
-------------------------------------------------------------------
Q6: Do you have a Gopher server?

A6: Yes, we do. dnpap.et.tudelft.nl, port 70

-------------------------------------------------------------------
Q7: I have set mibdf.mibhome in global.ini but the MIB conversion
    routines in cfg2ini don't recognize it. Doesn't cfg2ini use config 
    variables in INI files?

    
A7: No, it doesn't. The config library that was developed
    is strongly oriented towards applications. To make a working 
    utility like cfg2ini you have to bend some rules. If cfg2ini
    would read INI files, the resulting INI files would also
    include variables that were defined for cfg2ini itself.
    As a consequence, you always have to set MIBHOME to get
    cfg2ini working.
-------------------------------------------------------------------
Q8: I have set mgmt.community to my 'private' community name for
    setting MIB variables. The Tricklet utilities don't seem to
    recognize it, though. What's wrong?

A8: A common mistake is to type: mgmt.community = (STRING) dnpap .
    There are 2 problems with this line, however. (1) community
    names are byte strings and (2) strings should stand between 
    quotes otherwise the cfg2ini interpreter will try to read it
    as a byte string (ala 0x10:0x88).
    The right line should therefore be: 

                mgmt.community = (BYTES) "dnpap".
-------------------------------------------------------------------
Q9: I get 'corrupted ZIP file' if I try to unzip the distribution
    files with PKUNZIP. PKZIPFIX also doesn't help. What am I
    doing wrong?

A9: The files were ZIPped with the publicly available PKZIP clone, ZIP.
    Use the also publicly available UNZIP to unpack the distribution
    files.
-------------------------------------------------------------------
