home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Elysian Archive
/
AmigaElysianArchive.iso
/
comm
/
olss2rl.lha
/
Docs
/
OLSS.DOC
< prev
next >
Wrap
Text File
|
1992-08-23
|
8KB
|
174 lines
/------------------------------\
| OLSS Off Line Soft Scan |
| |
| Version 2.00Rl by Tim Walls |
\------------------------------/
INTRODUCTION:
OLSS is a utility designed specifically for Falcon CBCS BBS systems, but
which could be used on other systems (eg. DLG). OLSS is designed to allow
users of a BBS access to the sysops library of software held offline, on
floppy disks, which would not normally be available for download. This is
achieved through an online database system, with the ability to generate
file requests. The sysop then copies the requested files from disk to a BBS
download area at a convenient time, ready for the user to download on the
next login.
Read OLSSysop.DOC for details of installing the OLSSysop program.
COPYRIGHT & DISTRIBUTION:
The following copyright & distribution notice applies to all the programs
supplied in the OLSS distribution, specifically OLSS, OLSSysop, OLSS.scr,
ADDPROG and all related files. This group of programs will be referred to as
"OLSS".
OLSS was written by Tim Walls, and is (c) 1992. These programs'
executable code is freely distributable. The source code to these
programs is NOT public domain, and attempts to reverse engineer,
disassemble or otherwise obtain the source to these programs will
be deemed breach of copyright.
GMacro is not guaranteed in any way. The author of these programs
accepts no liability, in whole or in part, for damage incurred
as a result of this software, either direct, indirect, incidental
or consequential. If your state/country prohibits such exclusions
of liability, YOU MAY NOT USE THESE PROGRAMS. The entire risk as to
the program's quality and performace is with the user.
INSTALLATION:
Once OLSS is installed, its use is pretty much self explanatory (& fully
documented through online help files), so the rest of this document will
explain the installation process itself:
OLSS must be run in a RAW: console environment, and must also be run via a
script file to ensure that the stack is an appropriate size! Step-by-step
installation is as follows:
1) Make a directory doors:OffLineSoft
2) Make a directory doors:OffLineSoft/Users
3) Copy OLSS doors:OLSS
4) copy OLSS.scr doors:OLSS.scr
5) Add a menu item to your menus.bbs as follows (you may use any key
you want for the menu option, obviously!!):
TWIT * RAW C "execute doors:OLSS.scr doors:OffLineSoft/OLSS.cfg
«FULLNAME» «LEVEL» «IBMCHARS»«IBM»«NOIBM» «HEIGHT» 2400"
note that this is all one line!! Note also the last number (2400):
This is a dummy entry. In reality it is meant to indicate the baud
rate at which the user is logged on, but until Falcon can actually
send that information it is useless :-( (DLG users will no doubt be
laughing!). It is relates to the BACKDROP config file keyword.
5) Create the configuration file, doors:OffLineSoft/OLSS.cfg
This may be done by modifying the supplied OLSS.cfg file; it is
fairly self explanatory methinks. Note, though, that paths, filenames,
directory names etc. _MUST_ be surrounded by "'s.
6) Initialise the databases. This is (quite!!) simple. Use Falcon in
the local terminal and use your new OLSS option. If your data file
OLSS.data was set up correctly you should see two menu options, one
for each database. Select the first. You will be asked if you want
to initialise the database. Answer Y)es. The program will then ask
you to input 12 "flag names" for the database. Once this is done, the
datafile is initialised and the program will exit. To access the
database rerun the program.
Do this for each of your databases.
7) Add some database items. This may be performed "online". Select the
flags you wish the program to be identified with by hitting the
appropriate letter keys (A to L). When you are satisfied, hit "*"
to add a program. You will be asked some fairly self explanatory
questions and then the program will be added to the database.
NOTE THAT YOU MUST SET THE FLAGS _BEFORE_ HITTING THE * KEY TO ADD
A PROGRAM TO THE DATABASE.
Items may also be added from the CLI using the ADDPROG program; See
accompanying documentation.
-------------------------* IMPORTANT NOTE *-----------------------------
A new function in version 1.72sr of OLSS is the "Long Description"
system. Whilst adding a new program to the database, you are asked for a one
line description. This may not be enough, however. So, if you prefix the
description with a #, the following text will be assumed to be a filename and
path. So, for example:
DESCRIPTION: Dead good file.
is a standard oneline description. However,
DESCRIPTION: #doors:OLSS/Longdesc.dat
would tell OLSS to go and look for a file of that name and to use the contents
of that file for its description. Note: This file HAS A SPECIAL FORMAT.
7a) LONG HELP FILE FORMAT
The long help file has a special format which can neatly be summed up
as follows:
Catalogue entry
{
Keys
}
Text
CATALOGUE ENTRY:
The catalogue entry may be up to 80 characters long, and is the description
which will appear in the "Catalogue" option of OLSS.
Note the { and } delimeters. THESE ARE ESSENTIAL. THEY _MUST_ BE THE FIRST
AND ONLY CHARACTER ON A LINE.
KEYS:
Between the { and } characters is a list of keys. You may have up to 20 keys,
each of up to 20 letters. The keys should basically be a set of words which
you feel neatly sum up the program entry. It is these keys which will be
searched on (using the "Search text" entry) during a "Begin Scan" or
"Catalogue" call. The actual text content of the message is NOT searched (to
do so would be far too slooooooow). Each key must be on a seperate line.
TEXT:
Here you should put your description of the program entry. The text may be
COMPLETELY free-form, with lines of any length etc. It should be borne in
mind, however, that no word-wrap is performed by the viewer, and thus you
should justify your text for a 75 COLUMN screen (to take into account borders
etc.). Nothing drastic will happen if you don't, just text split over lines
etc.
USES FOR THE LONG DESC FUNTION
The primary concern when installing this function was to make it easier
for sysops to include disk-based libraries in the system. A single program
entry may cater for an entire disk, for example, and by using a "Long desc"
entry you can still detail ALL the software on the disk.
It may, of course, simply be used for more detailed descriptions of
ordinary individual files.
---------------------------------------------------------------------------
All other options have online help to explain them (use # from the main menu
to access the online help).
ONE LAST THING...
You must remember to check your request file (using OLSSysop) regularly.
You may also wish to set up a seperate file area for OLSS
requested files.
The best way to achieve this first aim is to make sure that running the
OLSSysop program is in your login stack.
THATS ALL FOLKS...
Good luck!! Any questions, comments, bug reports etc. may be directed
towards...
Tim Walls @ 2:253/513 Fidonet
Tim Walls @ 39:133/1 Amiganet
twalls@ncc1701d.demon.co.uk Internet