home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
_10NODE.ZIP
/
SYSOP.DOC
< prev
Wrap
Text File
|
1995-06-18
|
11KB
|
265 lines
═══ ══ ═════ ══════ ═══════ ═════ ═════ ═════ ═══ ══
════ ══ ══ ══ ══ ══ ══ ══ ══ ══ ══ ══ ════ ══
══ ══ ══ ═══ ═══ ══ ═══ ═════ ═════ ═══ ═══════ ══ ══ ══
══ ════ ══ ══ ══ ══ ══ ══ ══ ══ ══ ══ ══ ════
══ ═══ ═════ ══════ ═══════ ══════ ═════ ══ ══ ══ ═══
S y s o p D o c u m e n t a t i o n
Introduction to NodeScan
-----------------------------
Every Fido-style mail network offers a great resource to its users: the
nodelist. Containing vital information about every system in the net, this
list can be extremely useful in a variety of ways. However, a nodelist in its
native form is not exceptionally user-friendly, thus the need for a nodelist
browser such as NodeScan. NodeScan is the most full-featured nodelist browser
available, and supports any standard FTSC nodelist. Every system carrying one
or more networks should have a nodelist browser available, and with a
registration cost of only five dollars, NodeScan is the ideal choice.
Features
-------------
> Assembly language serial I/O
> Supports speeds up to 115.2k and 16550 UARTs
> Internal ANSI emulation
> Multitasker aware (DESQview, Windows, OS/2)
> FOSSIL support
> Split-screen chat with word wrap
> Multi-node capable
> Support for up to 16 nodelists
Configuring NodeScan
-------------------------
Setting up NodeScan for use with your nodelists is quick and easy; simply load
the file LISTS.CFG into a text editor and follow the on-screen instructions.
As you will see, for each list you must specify two things: the name of the
nodelist, and the path of the nodelist. When specifying the path, omit the
extension of the nodelist's filename if it is subject to change (as are most
nodelists). For example, for the FidoNet Nodelist you might specify:
C:\RA\FD\NODELIST
This way, NodeScan will automatically adjust as the filename changes with each
week's nodediff. If you do specify an extension, NodeScan will always look
for that specific file. If a nonexistent nodelist is specified, that entry
will be ignored.
After you've customized LISTS.CFG for your system, NodeScan is ready to run.
Whenever a nodelist is updated or LISTS.CFG is modified, NodeScan will detect
this and update its data files accordingly. NodeScan keeps track of certain
values for each nodelist to enhance its power and performance.
Running NodeScan
---------------------
The syntax for executing NODE.EXE is: NODE <config file> [local] [/N=x]
The config file is a 7-line text file:
Line 1: Dropfile type [RA,WC2,WC3,SF]
Line 2: Dropfile path/name
Line 3: BBS name
Line 4: Sysop first name
Line 5: Sysop last name
Line 6: COM port interrupt [1-7, 0 for FOSSIL]
Line 7: Use error log? [TRUE/FALSE]
Included is the utility MAKECFG.EXE, which will request this information and
create a configuration file:
Name of config file to be created? Name the file. Ex: NODE.CFG.
Dropfile type? Enter one of the following codes: RA - DORINFO.DEF
WC2 - CALLINFO.BBS
WC3 - DOOR.SYS
SF - SFDOORS.DAT
Path/name of dropfile? Where the previously designated dropfile is created.
BBS name? Self-explanatory.
Sysop name? Self-explanatory.
COM port interrupt? The interrupt of the COM port given in the dropfile.
Valid interrupts are values 1-7. Enter 0 to use FOSSIL.
(Note that this is asking for the INTERRUPT number, not
the COM port number.)
If you are unsure of what this value should be, here
are the typical interrupts:
COM1 - IRQ4
COM2 - IRQ3
COM3 - IRQ4
COM4 - IRQ3
Log errors? Enter TRUE to write all errors encountered to a log. Enter
FALSE not to log errors.
Here is a sample config file:
WC3
C:\RA\DOOR.SYS
Temples of Syrinx
Scott
Stuart
3
FALSE
NodeScan must be run from the directory in which all its files are located; it
is recommended you run NodeScan from a batch file such as this:
@ECHO OFF
C:
CD \NODE
NODE.EXE NODE.CFG /N=1
To run NodeScan locally from the command line, add the parameter LOCAL after
the config file specification.
Multinode Usage
--------------------
NodeScan supports nodelist sharing and should not conflict with any other
software you use (i.e., FrontDoor) which reads the nodelist. When running
NodeScan on a multinode system, specify the node number on the command line
using the /N=x switch. When no node number is specified, x defaults to 0 for
local usage, and 1 for remote. There should be no need to specify a node when
running NodeScan locally, as the default of 0 is reserved for local mode.
If a user enters NodeScan and triggers nodelist maintenance, no other users
may use the program until maintenance is complete. If a user attempts to
enter NodeScan while maintenance is being performed, he will receive a message
informing him of this and will be given the option to press ESC to return to
the BBS; if the user opts to remain in the door, NodeScan will proceed
normally as soon as maintenance is finished. If no maintenance is running,
yet users are still disallowed entrance into the door, delete the INIT.SEM
file from your NodeScan directory; this situation may occur if NodeScan
maintenance is interrupted, such as in the case of a system lock-up.
Using NodeScan
-------------------
NodeScan is very intuitive; any user with reason to use a nodelist browser in
the first place should have no problem navigating the program. For reference
purposes, provided is a quick rundown of NodeScan's options:
String Search Nodelist
Allows the user to search the nodelist based on one of several different
categories. After a search, the matching systems will be listed on the
bottom half of the screen; multiple-page lists can be scrolled by pressing
the < and > keys. Pressing a number 1-5 will bring up a window with more
detailed information on the corresponding system.
Change Nodelist
Shows all available nodelists and prompts the user to select one.
Download Search Results
Time permitting, allows the user to download the results of the most
recent search in a neatly formatted list. Used locally, this option
writes the report to disk. (Please see the section below on file
transfers.)
Info on Nodelist
Displays some nodelist statistics.
Node Number Search
Allows the user to search the nodelist based on net address. Wildcarding
greatly increases search flexibility.
Verify Node
Searches the nodelist for one particular address; if the system is found,
an information window on the node is automatically displayed.
Print Search Results
Available to local users only, this option allows the search report
to be printed. Includes an option to take advantage of the features of HP
DeskJet and compatible printers, and an option to print in standard ASCII
for those printers which do not support high ASCII.
Get Nodelist
Time permitting, allows the user to download the currently selected
nodelist. A very convenient way to have nodelists available for download,
without having to update your file areas every week! (Please see the
section below on file transfers.)
Read Comments
Displays the general-interest comment lines in the nodelist.
File Transfers
-------------------
NodeScan features internal support for Omen Technology's GSZ file transfer
utility; you must have a copy of GSZ for NodeScan to be able to perform file
transfers.
If you do not have and are unable to locate a copy of GSZ, you can obtain it
from the NodeScan support BBS either by calling and downloading it, or file
requesting "GSZ". Information on the support BBS is listed at the end of this
document.
Upon startup, NodeScan will search all PATHed directories for GSZ.EXE; make
sure that your copy of GSZ resides in such a directory.
It is suggested that you set the following environment variable so the
NodeScan status bar remains visible while GSZ is in use:
SET GSZWINDOW=24
Please remember that you must reboot for this setting to take effect.
Registering NodeScan
-------------------------
The unregistered version of NodeScan has all features available, allowing you
to fully evaluate it before registering. For the low price of $5.00, you can
register NodeScan, thus eliminating the unregistered annoyances.
Registration entitles you to free minor and major upgrades. To register
NodeScan, print out REGISTER.TXT and send it to the address listed. If your
BBS is a member of FidoNet, your registration key will be conveniently sent to
you. If not, you can call the NodeScan support BBS to download it:
Temples of Syrinx
908/914-9807
FidoNet 1:107/751
RemoteAccess v2.02+
USR Courier HST V.34+
Logon using the exact name and password specified on the order form, and
your registration key will be waiting as an EMail file attach.
To use your registration key, simply place it in the directory with all of the
other NodeScan files and rename it to NODE.KEY.
NodeScan support can also be obtained through the beta testing site:
Paul's Boutique
609/242-0295
FidoNet 1:2623/51
TriBBS v5.11/255
USR Courier HST V.34+
The latest version of NodeScan is available on both systems; it can be
obtained by calling the board and downloading it, or FREQing the magic name
"NODESCAN".
And if you don't already have it, FREQ "SAD" to get Search and Destroy, the
popular Battleship-style door game by the same author. Also by Scott Stuart
is Another Brick In The Wall, the ultimate graffiti wall door! FREQ "WALL".
NodeScan was written using URDoor comm routines (c) 1995 Kenneth Bledsoe.
NodeScan (c) 1995 Scott Stuart.
Distribution of NodeScan is permissible and encouraged, providing that no fee
be assessed for its distribution other than any normal fee that may be
associated with the medium by which it is distributed. NodeScan must be
distributed in its original archive form, unaltered and with no registration
keys.