[]INTRO

  ┌──NodeManager───────────────────────────────────────────────────────────┐
  └────────────────────────────────────────────────────────────────────────┘

     What is it?

     ■ NodeManager is a tool that allows a sysop running a multiline BBS
       to handle all of their nodes from a single station.  You can see who
       is online all nodes, or you can view a users actions on a specific
       node.  The most important, and most powerful, feature of NodeManager
       is that, with a network and the IPX protocol you can assume full
       control of a workstation.  This means that your screen and keyboard
       act as the workstations own screen and keyboard.

     ■ Other features include sending users online messages, rebooting
       remote workstations, full system usage charts and graphs.  You can
       also initiate jobs and events based on time of day, file semaphores
       as well as spooled commands.

     ■ NodeManager not only shows you when a user is logged onto the BBS,
       but shows you when the mailer is using a node for either inbound or
       outbound calls.

     Is it hard to setup?

     ■ NodeManager comes with various command line options to help you
       setup the required files.  The default setup will get you to an
       operational point, then you simply enter the finer details.

  ┌────────────────────────────────────────────────────────────────────────┐
  └──────────────────Copyrighted 1995 by Multiboard Communications Centre──┘

[]COMMANDLINEHELP

     System Information

     ■ This is where you define important information regarding the BBS
       paths, or where you enter the registration information.

     Display Information

     ■ This is where you select your mailer (if you have one), the mailer
       paths, and the drives to use for statistics.

     Options

     ■ This is where you define the specifics to NodeManager such as what
       to display, how often to rescan the userson and check for semaphores,
       and other specific information.

     Logging Options

     ■ This is where you decide what where to place the log file, and what
       events you would like to log.

     Page Options

     ■ If you are going to use the replacement paging program then this
       is where you define the settings for the programs.

     Colour Configuration

     ■ This is where you enter to change virtually every color used by
       NodeManager.

     Command line parameters...

     ■ /NOEVENTS, /NOJOBS, /NOFILE, /NA

       By using one or a combination of the first three parameters you will
       disable some of the file executions.  By using the /NA parameter you
       will disable all three of the first parameters ensuring that your
       session will remain uninterrupted.

     ■ /SCAN=#

       This will replace the rescan rate entered in the setup program.  This
       may be useful if you are running more than one copy of NodeManager at
       a time.

     ■ WATCH #, REBOOT #, REBOOT ALL

       These options will load the program and return to a DOS prompt when
       the desired task has been completed.  This simply provides you with
       an automated way to perform key functions.

     ■ SEND #

       This allows you to send a string to a remote node, this is not
       sending a user message, but stuffing the remote keyboard, so that a
       command or series of commands can be executed.  All parameters that
       follow the # parameter will be sent as the input text.

     ■ BUILDSET

       If the paths to each node resemble each other, then this feature
       will automatically build the required NODEMAN.SET file.

       ■ For example...

         NODEMAN BUILDSET PATH=C:\RA\NODE*N LOCAL=3,4

     ■ BUILDLIST

       This will use your mailer's inbound and outbound history files to
       build the lookup files used by NodeManager.

[]BBSHELP

  System and SysOp name

    ■ This is where you enter the system and sysop name of the BBS.

    ■ If the data is not the same as was entered on the registration form,
      then NodeManager will still appear to be unregistered.

  Serial number and registration code

    ■ This is the serial number and the registration code that you received
      for your registration.  Please ensure that the entered numbers are the
      same as they appear on the registration form.

  Semaphore path

    ■ This is the path that the BBS uses for semaphores.  This should be
      the same as the one entered in the BBS package.

  Path to USERS.BBS

    ■ This is where the USERS.BBS file is located, this should be the same
      as the one entered in the BBS package.

  Notes...

    ■ All of the available information is taken from the RemoteAccess
      configuration file if the RA environment variable is set.

[]MAILERINFO

  Display mailer info type

    ■ You can select to display either information from the selected
      mailer's lastcalls, or information regarding drive space.

  Mailer system directory

    ■ This is the where the lastcall, inbound and outbound history files
      are stored.  This path must be the same as the system path defined
      in your mailer.

  Mailer semaphore directory

    ■ This is where the mailer creates the semaphore files.  This path must
      be defined if you want to see mailer activity.  This path must be the
      same as defined in the mailer.

  Display mailer at startup

    ■ If you have one of the compatable mailers, you can decide whether
      to display the mailer's lastcall information or the disk information
      when the program is first launched.  The two information types can be
      toggled from NodeManager.  If you did not pick a mailer then the disk
      information will always be shown.

  Drive 1 and drive 2

    ■ This is where you place the letters of the drives you would like to
      see information on.

[]CONFIGURATIONOPTIONS

  Rescan rate

    ■ This indicates how long to wait before reading the USERON.BBS file
      and checking for mailer and defined semaphores.  If you have a low
      number, then the information displayed will be more accurate than if
      you have a high number.  A high number however will be less task
      intensive on the hard drive.

  Sound if paged

    ■ This will sound three beeps through the PC speaker only if a user has
      attempted to page the Sysop.

  Show password

    ■ When a user record is brought up you have the choice of viewing
      the user's password.

  Last field display

    ■ You have the option of displaying the time that a user has logged
      on/off or the amount of time that has elapsed since log on.

  When idle display

    ■ If a user logs off, by default NodeManager will display where the
      user logged off from.  By selecting "Change action" you can have the
      "Waiting" prompt displayed when the user logs off.  If you choose
      "Clear line" then the line will be entirely blanked, except the action
      field which will say "Waiting"

  Semaphore precidence

    ■ Nodemanager looks for both mailer semaphores and defined semaphores,
      because there is a possibility of two semaphores being defined for one
      node, it is important to know which semaphore should be displayed.

  Create system history file

    ■ If you would like to be able to view yesterday's statistics and
      callers then you will need to create a history file.

  Node reboot method

    ■ If you would like to reboot a remote node, you have the choice to
      send it a hard or a cold reboot.  You can only reboot the remote node
      only if you are able to connect and control the node.

  Time to view tagged nodes

    ■ You can define how many seconds you would like to view a node when
      cycling tagged nodes, or nodes with users on.

[]LOGGINGOPTIONS

  Nodeman's full filename

    ■ This is the path and filename of the log file for NodeManager to log
      its various events.

  Log events, jobs, and file triggers

    ■ These options will log when the executed command began, what the
      command was, and when the command was finished.

  Pager's full filename

    ■ This is the path and filename of the log file for Pager to log its
      page reasons and other pertinent information.

  Page reasons

    ■ These options will log when the executed command began, what the
      command was, and when the command was finished.

[]PAGEINFO

  Music duration

    ■ This is how long to wait if you do not respond to the page.  The
      music will play for this long, unless the PAGE.RA file is missing.

  Page length

    ■ This is how long of an input line there should be for the user.
      The maximum length available is 79 characters.

  Use internal chat

    ■ If you select yes, then you will use the chat within PAGER, however
      if you select no, then PAGER will bomb out and use the RemoteAccess
      chatting program.

  Notes...

    ■ The Pager program is used so that the chat reason can be obtained
      from the user.  If you are using Pager then the chat reason will
      replace the fwd line in the user info screen ("I" from NodeManager).
      If you are not using Pager then the page reason can not be obtained
      and the fwd line will still be displayed.

