SYSOP.TXT - information for sysop use with GHOST 3.30

The GHOST.INI file in your ASPECT directory contains all of the data 
for running GHOST. Some of this is set either through running 
GHSTUTIL.WAX, or through the basic GHOST.WAX set up of times, etc.

However, a fair amount of the data here will require the sysop to edit 
the INI himself, if he wants anything other than a basic set up.

[Security1]

In this section you will find an entry for each GHOST security level, 
with a matching "description", set, by default, at simply "* Level x 
*" where x is the security number. You may edit these to whatever you 
wish. This information will be displayed to the user at log on, and in 
the Y)our settings screen. Try not to get too wordy, as the display at 
log on will wrap funny if you do <GG>


[Protocols]

This section provides a descriptive name for each of the transfer 
protocols allowed in GHOST. BE CAREFUL! The name must match that used 
by Wasp to identify the protocols, so DO NOT CHANGE any of the 
pre-defined ones.

It is in this section that you may add "external" DLP protocols, such 
as HS-Link. To add HSLINK.DLP, edit the two protocol menu files 
(default names, GHOSTP.MNU and GHOSTTP.MNU) to include HS-Link as say, 
protocol "H". Then edit this section of the ini to include the line :

h=hslink

Normally, when adding a protocol such as this, if it allows batch file 
transfers, you would also need to add a letter to the list of transfer 
keys in the line :

batch_down=

However, I have put it into the default entry for GHOST already. 
However, if any new DLPs are published and you wish to support that 
protocol, and it allows batch transfers, you will need to add the menu 
key to the above line.


[Libraries]

This handles telling GHOST how to handle bulletins and file libraries. 
The upload path is set via GHSTUTIL.WAX, and the line

Download1=

will contain your old GHOST default download directory. If you 
upgraded from the GHOST 2.14 or 2.20 beta, then your download libraries 
will also be set already. Most of the other settings here can be 
edited via the GHSTUTIL.WAX file...


[Lib1]
Dnl0=
Dnl1=
Nws0=
Nws1=

Thse lines allow you to give a name and location for the bulletin and 
library files themselves. In this and any following sections, a 
certain naming convention for various lies is used. Whenever you see a 
line with a 0 in it (such as Dnl0=), this is the line indicating a 
non-ANSI (0 = FALSE) file, while a 1 (as in Dnl1=) indicates an ANSI 
(1 = TRUE) file. 

This section does NOT use an extension. What it requires is something 
like "c:\ghost\libs\text", where the last few characters are, of 
course, part of the actual file name. When you "name" the bulletin and 
download list files, make sure to allow enough room in the eight 
characters for GHOST to add a number up to whatever the maximum you 
have set. Thus, if your maximum number of bulletins is 32,767, the 
"name" for a bulletin file could not exceed 3 characters, since the 
number could take up the last five.


[Run Files]

This section allows you to define the location and name of the various 
files which GHOST uses. Be a little careful here, but in future, GHOST 
upgrade utilities will read these locations to find out what name to 
use for various files. I have not run into any problems renaming any 
of these or the following files, but, if you wish, you can test it out 
for me <GG>


[Menus1]

This section lists the location and names of the various menu files 
which GHOST uses, main, bulletin, library and protocol. Perhaps the 
only thing needing explanation here is the fact that there are 6 
"main" menus, ANSI and non-ANSI of each of : Regular Main, Sysop Local 
Main, and Sysop Remote Main. Based upon security level, and modem 
status, GHOST will pick the appropriate menu to show the user.


[Mail]

This is the listing of various data and temporary files used by the 
mail section of GHOST.


[Base1]

This section locates and names the various help, new user, goodbye and 
welcome screens used by GHOST.



PLEASE, simply exercise a little caution when renaming any of these 
files. So far, I have had absolutely no difficulty with moving them to 
different directories, nor with renaming them, but one never knows. 
Experiment if you will, so that I can find out how the various 
routines in GHOST work, but remember these are filenames, and should 
include a full path, root, and extension for proper operation (except 
the entries in [Libraries] mentioned above, whcih do NOT require the 
full name/extension).

Gregg


