(H0)
You can access the help system from ANYWHERE in SM at ANYTIME by
pressing ALT-H.

The files "Osiris.hlp" and "Osiris.idx" and must be in the current
directory before you can use the help system.

Help is INDEXED by the *FIRST* character of the TOPIC  except for
items relating to SM. Those items are placed at the TOP of the
list and are very easy to identify.

All items relating to SM begin with SM, contain at least one
FORWARD slash, and additional text.

Example: SM/Files/File Area Manager

This means the topic is related to the "SM" program, the primary
menu option "Files", and the SUB menu option "File Area Manager"

Some topics MAY show up in SEVERAL spots under DIFFERENT names. We
tried to use names that YOU might look for when you run into problems
or need information.

As for the topic descriptions, we used what *WE* thought was right
for each topic. However, if you can think of a BETTER description
please let us know.

The HELP system is for YOU, we already know all about Osiris, and
if changing a description or even ADDING a new topic will help YOU,
we'll do it. But, the catch is that you have to TELL us.

To READ a topic, click on it and then click on OK.

Help has two other options, FIND and PRINT.

FIND lets you SEARCH help for anything that matches your search
string. When a match is made, the item is displayed. When you have
finished reading you have the option of continuing the search,
aborting the search, or PRINTING the item to your printer.

PRINT sends the item directly to your printer. TO use this option,
select the topic from the index and  click on it. Then click on
the PRINT button.

You do NOT have to be IN the system manager to use the Help
system.

As long as the HELP files, Osiris.hlp and Osiris.idx, are in the
current directory, you can type "HELP Osiris" or "HELP O" from the
DOS command line.


(H1)
This section is only relevant if you run Osiris *WITHOUT* a
mailer frontend. If you use a MAILER FRONTEND, you'll have to do
all of this yourself.

Again, if you run Osiris in STAND ALONE mode, i.e. Osiris answers
the phone, this is all done AUTOMATICALLY for you.

Osiris handles running CAT once a day, shortly after midnight.
This is done automatically and you don't have to worry about
anything.

Each night shortly after midnight, Osiris will go OFFHOOK and run
a batch file called "MIDNIGHT.BAT".

It is up to you to create this file and you might place commands
in it to do GAME maintenance, export echomail, or newsgroups.

If midnight.bat doesn't exist, it is skipped.

After Osiris runs Midnight.bat, Osiris will run CAT to tidy up.
After CAT, Osiris will run ULINK.

As I said, with the exception of Midnight.bat, you do not have to
do anything and this saves you from having to use Osiris events.

                     Multiple Nodes

When MULTIPLE nodes are involved, only NODE 1 will execute
midnight maintenance. The other nodes will simply go OFFHOOK and
WAIT for node 1 to finish the mintenance and then ALL nodes will
go back ONHOOK.

(H2)
The first time you run SM, you'll be asked to supply the name of
your TEXT editor.

This will be used for posting system bulletins and entering
EXTENDED file descriptions.

Just about everybody has their favorite text editor and we'll not
ask you to learn a new one.

You can use any editor as long as it saves in ASCII format.

You should set your RIGHT margin to no more than 77 characters, 66
is the PREFERRED setting.

Make sure the editor is either in a DOS path or in the current
directory.

You can REDEFINE the editor at any time by

1. Deleting SM.CFG
2. Using the SM/MISC/Define Text Editor Option

(H3)
SM uses FOUR types of CONTROLS; Radio Buttons, Check Boxes,
Push Buttons, and Scroll Bars.

                           Push Buttons

Push buttons are controls that act similar to a key on a keyboard
or a button on a calculator. They are usually used to trigger an
event or send a command to the program.

To activate a button, move the mouse pointer to the button and
press the LEFT mouse button. The button will SINK in to indicate
the program accepted your selection. If the button does NOT sink
in, you may be OUTSIDE the HOTMOUSE area or the button may not be
available at that time.

                           Check Boxes

A checkbox is a control that represents two possible states. At
any given time, the checkbox may be on or off(checked or not
checked).

There are two main parts to the checkbox. The label, a string of
text that indicates the purpose of the checkbox. The box indicates
the current checkbox state.  The box consists of a '[' and a ']'
character. If the checkbox is on, [X], or [ ] if the checkbox is off.

Often, but not always, checkboxes are used in groups. SM may
display a window with 7 checkboxes. You would respond by turning
one or more of the checkboxes ON. You would do this by CLICKING on
the checkbox with the LEFT mouse button.

The example listed below shows DAYS of the weeks. All of the days
are selected EXCEPT Fri

 Mon [X]
 Tue [X]
 Wed [X]
 Thu [X]
 Fri [ ]
 Sat [X]
 Sun [X]

                           Radio Button

A radio button is very similar to a checkbox. Unlike a checkbox,
Radio buttons are always displayed in GROUPS of two or more.

Unlike the checkbox, only ONE of the radio buttons in a group can
be active at any given time.

║                            () Greater Than or Equal To
║                            ( ) Less Than or Equal To
║ Access Level  0            ( ) Equal To
║                            ( ) Less Than
║                            ( ) Greater Than
║

The question above is, HOW do you want to compare the callers access
level to the one defined here?

A small DOT will appear between ( ) to indicate which one you've
selected.

                            Scroll Bar

Scroll bars allow you to shift the window viewport using the
mouse. For a scroll bar to have any effect, the window's viewport
must be smaller than the window. If the viewport is the same size,
the entire window contents are always visible.

A scroll bar consists of three areas. At the top (or left) and the
bottom (right) are forward and backward arrows. If the mouse is
clicked on an arrow, the viewport is moved by one row (column) in
the indicated direction. If the mouse button is held down with the
mouse pointer over an arrow, the movement repeats.

The inside of the scroll bar is filled with a background and
contains a mark character that indicates the current position of
the viewport. If the mouse is clicked within the background area,
the viewport is moved by one page in the indicated direction. If
the mouse button is held down, the scrolling will repeat until the
mark reaches the mouse pointer. If the mouse is clicked ON the
mark, the mark can be moved by holding the mouse button down and
dragging the mark to its new position.

When using a scroll bar, always click on the DOWN arrow or UP arrow
section to make SURE you are at the TOP or BOTTOM of the display.

(H4)
Unlike traditional CBIS or BBS programs, Osiris doesn't have ANY
set functions, operations, or display files.

Some programs will do a new upload search, display a series of
welcome files, or check for new mail.

While having set functions or display files makes it a bit easier
to set-up, it doesn't offer much flexibility.

I use a STARTUP.BBS command file that tells me what you want done
and for WHOM.

You have 24 slots, you can use any or all and I will process each
command starting with slot 1 and work down to slot 24. Empty slots
will, of course, be skipped.

When you select Startup.Bbs, you'll get a screen that looks a bit
like this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌────────────── Startup.bbs ──────────────┐ ║
║ │--- Open Slot ---                         ║
║ │--- Open Slot ---                        ▓ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                         ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║    Add ▄  Del ▄  Edit ▄  Path ▄  Exit ▄     ╟
║    ▀▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀▀▀▀▀     ║
╚═════════════════════════════════════════════╝

The FIRST time you  use this section, you'll need to click on the
PATH button and define a path to the DISPLAY, RIP, and SPL/I
files.

To EXIT this section, press EXIT mouse button. To Add a command,
click on a slot labeled "--- Open Slot ---" and then Click on ADD.

When you do, you'll get another menu that looks something like
this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌────────── Set Startup Option ───────────┐ ║
║ │New Upload Check                         ░ ║
║ │New Bulletin Check                       ░ ║
║ │Display Last Caller Info                 ░ ║
║ │Change Osiris.bbs Cmd File               ░ ║
║ │Change Language File                     ░ ║
║ │Change Blktxt File                       ░ ║
║ │Display Time Left (Subscription System)  ░ ║
║ │Call Back Verification                   ▓ ║
║ │Display Rip File (No ASC/ANSI)            ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║           Ok ▄                   Cancel ▄   ║
║           ▀▀▀▀                   ▀▀▀▀▀▀▀▀   ║
╚═════════════════════════════════════════════╝

Move to the TYPE of function you want and CLICK on it and then
CLICK on the OK button. If you want to CANCEL your selection,
CLICK on the CANCEL button. If you need to SCROLL the display,
use the SCROLL bar on the RIGHT side of the window.

When you SELECT a function, a new screen will open that looks
something like this:

╔══════════════════════════════════════════════════════════════════════════╗
║                            () Greater Than or Equal To                  ║
║                            ( ) Less Than or Equal To                     ║
║ Access Level  0            ( ) Equal To                                  ║
║                            ( ) Less Than                                 ║
║                            ( ) Greater Than                              ║
║                                                                          ║
║ Active On       Node 0     Starting Time  00:00    Ending Time 24:00     ║
║                                                                          ║
║ Mon [X]         Sound File                                               ║
║ Tue [X]                                                                  ║
║ Wed [X]                            SPL/I Flags                           ║
║ Thu [X]                                                                  ║
║ Fri [X]     1   2   3   4   5   6   7   8   9  10  11  12  13  14  15    ║
║ Sat [X]    [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]   ║
║ Sun [X]                                                                  ║
║                                                                          ║
║              Ok ▄                                  Cancel ▄              ║
║              ▀▀▀▀                                  ▀▀▀▀▀▀▀▀              ║
║                                                                          ║
║                                                                          ║
╚══════════════════════════════════════════════════════════════════════════╝

From here you define the access level, access level compare
method, the days the slot is active, the node the slot is active
ON, the time of day in 24 hour format the slot is active, and
finally what, if any, required SPL/I flags.

Once you have everything looking the way you want it, click on the
OK button.

If you click on CANCEL, any changes you may have made will be
discarded.

To keep the Windows GUI looking good and running smooth, I
urge you to place following startup commands first and in in the
following order.

         Ask Icon (or Force)
         Display Last caller
         Display Time Left
         New UPload Search
         New Bulletin Search



Here is a brief run down of all the FUNCTIONS you can define in
your STARTUP.BBS file.

                       Display File

Simply an ASCII, ANSI RIP, or MMU display file that you create.
Keep in mind that if you want ME to strip or display ANSI, based
on your graphics settings, you must use an MMU file.

The display file has to be in the directory you defined for the
startup command sequences. I will also PAUSE after the file has
been display and wait for you to press any key.

I don't display any type of Press any key to continue prompt. If
you want something like that, add it to the bottom of the display
file.

                    SPL/I++ Command File

Run this SPL/I command file. The possibilities. . . unlimited.

The SPL/I command file(s) must be in the directory you defined for
the startup command sequences.

               Display Rip File (NO ASC/ANSI)

Functions almost like the "Display File" but this one is
specifically for RIP screens ONLY. If the caller does NOT support
RIP graphics, this slot is ignored.

I will also PAUSE after the file has been display and wait for you
to press any key.

I don't display any type of Press any key to continue prompt. If
you want something like that, add it to the RIP file.

                        External Program

Execute this external program. The program can be a batch, com, or
exe file and can be located anywhere. Well, DOS has to be able to
find it so it will either have to be in the OSIRIS directory or in
a PATH directory.

I will write DOOR.SYS, DORINFOx.DEF, USERx.QBS, and OUTx.QBS in
the OSIRIS directory, in case your external application needs one
of them.

If the application does, then you'll want to execute a BATCH file
that copies the file to the correct directory and THEN calls the
application instead of trying to call the application directly.

I will also passes several command line switches. Whether or not
you use them is up to you and the program you're calling.

The switches are; Connect Rate, Serial Port, Node Number, UART
Rate, Time Left In Minutes, and finally a 0 or 1 with 1 meaning
LOCAL mode. If you were to process this information with DOS batch
variables, it would be:

%1 = Connect Rate, %2 = Serial Port, %3 = Node Number, %4 = Uart
Rate, %5 = Time left in minutes, and %6 contains 0 or 1.

Keep this in mind if you are a programmer. USERx.QBS is your BBS
user record. ANY and ALL modifications to this file will be
RETAINED.

                     New Upload Check

If you have this option enabled, you can scan for new uploads
since the last time you checked or reset the scan date to
something else. This is important, it scans from the last time you
did a SCAN, not from the last time you called the system.

If I find a new upload, you have the option of tagging it for
downloading or aborting the scan.

The new upload scan is VERY VERY fast. The scan rate is so fast,
I've wasn't able to get an ACCURATE time. A system with 15 file
areas and 5400 odd files running on a 16 mhz SX took less than 3/4
of a second.

                   New Bulletin Check

Check for NEW system bulletins, those posted with Bullgen, since
the LAST time you called.

If there is a NEW bulletin, I'll display the bulletin and you
have to read it.

Let me repeat . . . you have to read it or at least endure the
display. Even if I display the MORE prompt, you cannot break out.

                 Display Last Caller Info

This displays, in a very nice format, the last caller to your
system, the total number of calls, and the total number of system
users.

               Change Osiris.Bbs Cmd File

This allows you to REDEFINE the primary command record you defined
in the NODEx.BBS file.

You might use this to configure different BBS' for different
GROUPS of people and switch formats based on either access level
or SPL/I flags. I'd suggest SPL/I flags.

                  Change Language File

This allows you to swap in a DIFFERENT primary language file. The
language file MUST be in the directory you defined on the final
page of the startup sequences.

                  Change Blktxt File

This allows you to swap in a DIFFERENT secondary language file.
The secondary language file must be in the directory you defined
on the final page of the startup sequences.

         Display Time Left (Subscription System)

If you run a subscription system, you'll want to let people KNOW
when their subscription expires and you'll also want me to CHECK
that subscription date and if it HAS expired, set the access level
to the level you defined in NODEx.BBS.

IMPORTANT: You ** MUST ** define this slot SOMEPLACE in the
Startup.Bbs file before I can CHECK subscription and LOWER,
if needed, the callers access level.

This function will CHECK your expiration date and if the current
date is GREATER than the expiration date, you will be notified
that your subscription has expired and your NEW access level is
so-and-so.

If your subscription has NOT expired, I will show you the date it
DOES expire.

If your access level is equal to the expiration access level, the
expiration access level is 0, or any one of the expiration date
fields is 0, I will skip this function.

                Call Back Verification

Call Back Verification System. See section of CBV for further
details.

                   Force ICON Check

Osiris will SKIP this option if the caller does not SUPPORT RIP
graphics.

As the name implies, this is a FORCED ICON check. The ICON manager
will scan the callers system to make sure he or she has all the
icons, jpeg, wav, etc. files needed to use the system.

                    Ask ICON Check

This is basically the same as the FORCE ICON CHECK only the caller
is ASKED if he or she wants to do the check.

                     Rotating Slot

As many of you know, seeing the same startup display screens every
single time you log-on can get old pretty fast. The solution to
that is to rotate your screens.

There are currently three ways you can do that.

1. Manually redefine the slot every so often, weekly or monthly.

2. Use multiple SLOTS and the DAY of the WEEK the slot is  active.
I.e. setting one slot to only display on MON, another to only
display on TUE, etc.

3. Designing an SPL/I that would show a different screen based on
the day of the month, or week.

All three methods have some draw backs.

Method 1, well some of you purchased Osiris so you wouldn't HAVE
to mess with it.

Method 2, easy enough to do and in most cases, sufficient.
However, it would limit you to 7 display screens and take up 7
display slots.

Method 3, most sysops wouldn't be able to figure out how to do it.

We've come up with a startup command you can plug in that is easy
to use and it's pretty darn flexible.

The new command is an AUTO-ROTATING general purpose slot that will
auto-detect if it is a normal display file, a RIP ONLY display, an
SPL/I program file, or an EXTERNAL program.

Before you can use this slot, you have to create a control file.
The name of the control file is up to you and when you plug in
ROTATING slot, SM will ask you for the name. The control file
should be in the STARTUP.BBS menu directory.

The first line in the control file is a unique (cannot appear in
in other ROTATING slot) ID number between and including 1 and 30.

The remaining lines contain the full drive, path, and name  of a
MMU, ANS, PRG, RIP file, or a .BAT. If it is a .BAT, you can leave
off the DRIVE/PATH if it is in the OSIRIS directory or in a PATH
directory.

Example:

1
C:\OSIRIS\DISPLAYS\WELCOME1.MMU
C:\OSIRIS\DISPLAYS\WELCOME2.ANS
C:\OSIRIS\DISPLAYS\PLAYIT.PRG
C:\OSIRIS\DISPLAYS\WELCOME.PRG
CHCK.BAT

The first line sets the unique ID to 1.
The 2nd and 3rd lines point to display files.
The 4th and 5th lines point to SPL/I applications.
The 6th line runs an external program, CHK.BAT.

The first time you call, you'll get WELCOME1.MMU, the second time
you call you'll get WELCOME2.ANS (An animated ANSI screen), the
3rd time you call you'll get PLAYIT.PRG, the fourth time you call
you'll get WELCOME.PRG, the 5th time you call you'll get whatever
CKCK.BAT brings up, the 6th time you call Osiris will cycle back
to the first and you'll get WELCOME1.MMU.

Notice I said "call". The rotation is based on an individual's
CALLS and not the date. If you called FIVE times in one day, you'd
cycle through all 5. If someone else only called once a day, it
would take them 5 days to cycle through all 5.

If you have a .RIP, the caller must be in RIP mode or it'll skip
the display.

If you leave off the extension, Osiris will treat it just like any
other display file with no extension.

There is no limit to the number of lines in this control file.

(H5)
You notice that during the log-in process, the system will seem
to STOP and you have to press ENTER/RETURN to get it to start
again.

This is caused when you DEFINE a display or RIP file in
STARTUP.BBS but Osiris cannot find the file.

If Osiris cannot find the file, you either used the wrong file
name or failed to move the file into the directory defined in
your STARTUP.BBS record.

Failing to move the file into the correct directory is the
mistake most often made by new and old sysops.
(H6)
If you want to setup a section to deal strickly with NEW users,
first time callers, use this section.

You have 24 slots, you can use any or all and I will process each
command starting with slot 1 and work down to slot 24. Empty slots
will, of course, be skipped.

When you select NewUser.Bbs, you'll get a screen that looks a bit
like this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌────────────── Newuser.bbs ──────────────┐ ║
║ │--- Open Slot ---                         ║
║ │--- Open Slot ---                        ▓ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                         ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║    Add ▄  Del ▄  Edit ▄  Path ▄  Exit ▄     ╟
║    ▀▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀▀▀▀▀     ║
╚═════════════════════════════════════════════╝

The FIRST time you  use this section, you'll need to click on the
PATH button and define a path to the DISPLAY, RIP, and SPL/I
files.

To EXIT this section, press EXIT mouse button. To Add a command,
click on a slot labeled "--- Open Slot ---" and then CLICK on
Add.

When you do, you'll get another menu that looks something like
this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌────────── Set Newuser Option ───────────┐ ║
║ │Display File                             │ ║
║ │SPL/I++ Command File                     │ ║
║ │External Program                         │ ║
║ │Call Back Verification                   │ ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║           Ok ▄                   Cancel ▄   ║
║           ▀▀▀▀                   ▀▀▀▀▀▀▀▀   ║
╚═════════════════════════════════════════════╝

Move to the TYPE of function you want and CLICK on it and then
CLICK on the OK button. If you want to CANCEL your selection,
CLICK on the CANCEL button.

When you SELECT a function, a new screen will open that looks
something like this:

╔══════════════════════════════════════════════════════════════════════════╗
║                            () Greater Than or Equal To                  ║
║                            ( ) Less Than or Equal To                     ║
║ Access Level  0            ( ) Equal To                                  ║
║                            ( ) Less Than                                 ║
║                            ( ) Greater Than                              ║
║                                                                          ║
║ Active On       Node 0     Starting Time  00:00    Ending Time 24:00     ║
║                                                                          ║
║ Mon [X]         Sound File                                               ║
║ Tue [X]                                                                  ║
║ Wed [X]                            SPL/I Flags                           ║
║ Thu [X]                                                                  ║
║ Fri [X]     1   2   3   4   5   6   7   8   9  10  11  12  13  14  15    ║
║ Sat [X]    [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]   ║
║ Sun [X]                                                                  ║
║                                                                          ║
║              Ok ▄                                  Cancel ▄              ║
║              ▀▀▀▀                                  ▀▀▀▀▀▀▀▀              ║
║                                                                          ║
║                                                                          ║
╚══════════════════════════════════════════════════════════════════════════╝

From here you define the access level, access level compare
method, the days the slot is active, the node the slot is active
ON, the time of day in 24 hour format the slot is active, and
finally what, if any, required SPL/I flags.

Once you have everything looking the way you want it, click on the
OK button.

If you click on CANCEL, any changes you may have made will be
discarded.

Here is a brief run down of all the FUNCTIONS you can define in
your NEWUSER.BBS file.

                       Display File

Simply an ASCII, ANSI RIP, or MMU display file that you create.
Keep in mind that if you want ME to strip or display ANSI, based
on your graphics settings, you must use an MMU file.

The display file has to be in the directory you defined for the
startup command sequences. I will also PAUSE after the file has
been display and wait for you to press any key.

I don't display any type of Press any key to continue prompt. If
you want something like that, add it to the bottom of the display
file.

                    SPL/I++ Command File

Run this SPL/I command file. The possibilities. . . unlimited.

The SPL/I command file(s) must be in the directory you defined for
the Newuser.Bbs command sequences.

                        External Program

Execute this external program. The program can be a batch, com, or
exe file and can be located anywhere. Well, DOS has to be able to
find it so it will either have to be in the OSIRIS directory or in
a PATH directory.

I will write DOOR.SYS, DORINFOx.DEF, USERx.QBS, and OUTx.QBS in
the OSIRIS directory, in case your external application needs one
of them.

If the application does, then you'll want to execute a BATCH file
that copies the file to the correct directory and THEN calls the
application instead of trying to call the application directly.

I will also passes several command line switches. Whether or not
you use them is up to you and the program you're calling.

The switches are; Connect Rate, Serial Port, Node Number, UART
Rate, Time Left In Minutes, and finally a 0 or 1 with 1 meaning
LOCAL mode. If you were to process this information with DOS batch
variables, it would be:

%1 = Connect Rate, %2 = Serial Port, %3 = Node Number, %4 = Uart
Rate, %5 = Time left in minutes, and %6 contains 0 or 1.

Keep this in mind if you are a programmer. USERx.QBS is your BBS
user record. ANY and ALL modifications to this file will be
RETAINED.

                Call Back Verification

Call Back Verification System. See section of CBV for further
details.

(H7)
If you want to set-up a section to deal with LOGGING OFF, this is
optional, use this section.

Osiris uses a command file similar to the startup.bbs file,
actually it is almost an exact duplicate except I use the file
name BYEBYE.BBS.

You have 24 slots, you can use any or all and I will process each
command starting with slot 1 and work down to slot 24. Empty slots
will, of course, be skipped.

When you select Byebye.Bbs, you'll get a screen that looks a bit
like this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌────────────── Byebye.bbs ───────────────┐ ║
║ │--- Open Slot ---                         ║
║ │--- Open Slot ---                        ▓ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                         ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║    Add ▄  Del ▄  Edit ▄  Path ▄  Exit ▄     ╟
║    ▀▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀▀▀▀▀     ║
╚═════════════════════════════════════════════╝

The FIRST time you  use this section, you'll need to click on the
PATH button and define a path to the DISPLAY, RIP, and SPL/I
files.

To EXIT this section, press EXIT mouse button. To Add a command,
click on a slot labeled "--- Open Slot ---" and then click on
Add.

When you do, you'll get another menu that looks something like
this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌────────── Set Newuser Option ───────────┐ ║
║ │Display File                             │ ║
║ │SPL/I++ Command File                     │ ║
║ │External Program                         │ ║
║ │Display Rip File (No ASC/ANSI)           │ ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║           Ok ▄                   Cancel ▄   ║
║           ▀▀▀▀                   ▀▀▀▀▀▀▀▀   ║
╚═════════════════════════════════════════════╝

Move to the TYPE of function you want and CLICK on it and then
CLICK on the OK button. If you want to CANCEL your selection,
CLICK on the CANCEL button.

When you SELECT a function, a new screen will open that looks
something like this:

╔══════════════════════════════════════════════════════════════════════════╗
║                            () Greater Than or Equal To                  ║
║                            ( ) Less Than or Equal To                     ║
║ Access Level  0            ( ) Equal To                                  ║
║                            ( ) Less Than                                 ║
║                            ( ) Greater Than                              ║
║                                                                          ║
║ Active On       Node 0     Starting Time  00:00    Ending Time 24:00     ║
║                                                                          ║
║ Mon [X]         Sound File                                               ║
║ Tue [X]                                                                  ║
║ Wed [X]                            SPL/I Flags                           ║
║ Thu [X]                                                                  ║
║ Fri [X]     1   2   3   4   5   6   7   8   9  10  11  12  13  14  15    ║
║ Sat [X]    [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]   ║
║ Sun [X]                                                                  ║
║                                                                          ║
║              Ok ▄                                  Cancel ▄              ║
║              ▀▀▀▀                                  ▀▀▀▀▀▀▀▀              ║
║                                                                          ║
║                                                                          ║
╚══════════════════════════════════════════════════════════════════════════╝

From here you define the access level, access level compare
method, the days the slot is active, the node the slot is active
ON, the time of day in 24 hour format the slot is active, and
finally what, if any, required SPL/I flags.

Once you have everything looking the way you want it, click on the
OK button.

If you click on CANCEL, any changes you may have made will be
discarded.

Here is a brief run down of all the FUNCTIONS you can define in
your NEWUSER.BBS file.

                       Display File

Simply an ASCII, ANSI RIP, or MMU display file that you create.
Keep in mind that if you want ME to strip or display ANSI, based
on your graphics settings, you must use an MMU file.

The display file has to be in the directory you defined for the
startup command sequences. I will also PAUSE after the file has
been display and wait for you to press any key.

I don't display any type of Press any key to continue prompt. If
you want something like that, add it to the bottom of the display
file.

                    SPL/I++ Command File

Run this SPL/I command file. The possibilities. . . unlimited.

The SPL/I command file(s) must be in the directory you defined for
the Newuser.Bbs command sequences.

                        External Program

Execute this external program. The program can be a batch, com, or
exe file and can be located anywhere. Well, DOS has to be able to
find it so it will either have to be in the OSIRIS directory or in
a PATH directory.

I will write DOOR.SYS, DORINFOx.DEF, USERx.QBS, and OUTx.QBS in
the OSIRIS directory, in case your external application needs one
of them.

If the application does, then you'll want to execute a BATCH file
that copies the file to the correct directory and THEN calls the
application instead of trying to call the application directly.

I will also passes several command line switches. Whether or not
you use them is up to you and the program you're calling.

The switches are; Connect Rate, Serial Port, Node Number, UART
Rate, Time Left In Minutes, and finally a 0 or 1 with 1 meaning
LOCAL mode. If you were to process this information with DOS batch
variables, it would be:

%1 = Connect Rate, %2 = Serial Port, %3 = Node Number, %4 = Uart
Rate, %5 = Time left in minutes, and %6 contains 0 or 1.

Keep this in mind if you are a programmer. USERx.QBS is your BBS
user record. ANY and ALL modifications to this file will be
RETAINED.

               Display Rip File (NO ASC/ANSI)

Functions almost like the "Display File" but this one is
specifically for RIP screens ONLY. If the caller does NOT support
RIP graphics, this slot is ignored.

I will also PAUSE after the file has been display and wait for you
to press any key.

I don't display any type of Press any key to continue prompt. If
you want something like that, add it to the RIP file.


(H8)
The file contains 255 ASCII flags set to either ON or OFF.  This
tells me which characters to accept, when getting input  from the
caller.

The purpose is to disallow characters that :

1.  Do not meet Fidonet, RCSA, UUCP, and other network standards.

2. To cut down on the effects of NOISY lines.

I've included a default KEY.BBS that meets the above
requirements.

You  may toggle individual characters on or off from within SM,
Command/Key.Bbs. When you select this option, characters with
a check mark are ON or allowed.

Some languages, French for instances, use accented characters
that do not fall within the accepted standards of international
message formatting. You may turn the accent  characters on, but
you should check to be sure you aren't violating the standards of
any networks you belong to.

(H9)
Unlike other BBS application, Osiris has no FIXED command
structure. Instead, Osiris uses COMMAND records, each with 26
slots that hold commands such as show user list, read messages,
download a file, play a game, show this text file, use this
database, etc.

If it helps to understand exactly what a command record is, think
of each command record as a traditional BBS subsystem like your
Main Menu or your message system.

The installation program installed THREE command records and they
give you a BASIC BBS with commands that are found on most BBS
system. You can have up to 32736 command records each with 26
commands. You can nest command records as deep as you want but I
would suggest that you not go more than three levels deep.

When you select the SM/Command/Osiris.Bbs option you'll get a screen
that looks something like this:

╔════════════════════════════════ osiris.bbs ═════════════════════════════╗
║                                                                         ║
║                                                                        ║
║  Record Name                           Record Number  0               ▓ ║
║                                                                       ░ ║
║  Menu Path                                                            ░ ║
║                                                                       ░ ║
║  Menu Name                  Require Rip  No                           ░ ║
║                                                                       ░ ║
║                                                                       ░ ║
║  Display File Area Info  No        Display Msg Area Info  No          ░ ║
║                                                                       ░ ║
║  Menu Sound File                                                      ░ ║
║                                                                       ░ ║
║                                                                       ░ ║
║  Command                             Hotkey        Access ▄           ░ ║
║                                                    ▀▀▀▀▀▀▀▀           ░ ║
║                                                                       ░ ║
║  Command                             Hotkey        Access ▄            ║
║                                                                         ║
║             First▄ Last▄ Add▄ Del▄ Next▄ Prior▄ Exit▄ Update▄           ║
║              ▀▀▀▀▀  ▀▀▀▀  ▀▀▀  ▀▀▀  ▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀▀▀▀           ║
║                   Click on BLUE field to edit or define.                ║
║                                                                         ║
╚═════════════════════════════════════════════════════════════════════════╝

Data entry field editing and movement commands for this section
are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, UP/DN arrow keys, the SCROLL bar at the BOTTOM of
the screen, PGDN and PGUP.

Each command record has a field labeled "Record Name".

This should CLEARLY explain what the command record is for. When
the callers help level set to SHORT or NO menus, the record name
is displayed to give the caller some idea as to WHERE he or she is
located.

Typical records names might be "Main Menu", "File Area", "Message
Area", "Statistics", or "Games".

The next field on a command record is labeled "Menu Path".  This
is the path to a subdirectory that holds ALL the display files,
menus, SPL/I, and special control files. Special control files
such as those needed by the database retrievel system, the
document retrieval system, and the classified ad system (to name a
few).

Quite often sysops FORGET this and they will not move a new menu
or display file to the proper directory and they can't figure out
WHY it isn't displayed.

The next field on a command record is labeled "Menu Name". This
field should contain the name of the MENU file, minus file
extension, and it will be displayed to the caller when their help
level is set to FULL.

Again, the name should NOT contain any type of file extension.
Osiris will ADD the file extension based on the CALLERS graphic
settings. See the section labeled "Creating Menus" to learn more
about making and NAMING menu files.

The next field is labeled "Require Rip". If this field is set to
"YES", Osiris will NOT allow the caller to select this command
record UNLESS, he or she is using RIP graphics.

The fields "Display File Area Info" and "Display Msg Area Info"
tell Osiris WHEN/IF information such as area name, area number,
file subsystem name, should be displayed. You can toggle one or
the other to YES but never toggle BOTH of them to yes.

The next field is labeled "Menu Sound File". Three guesses what
this field does :) Just enter the name of the sound file you want
played when this command is selected. Place all .WAV sound files
in your ICONS directory.

                         Adding a Command

This is where you PLUG-IN the commands, define the hotkeys for
those commands, and setup access information.

To define a command, click on the BLUE field following the text
"Command".

A small menu will open listing several command cateogires such as;
File Area Commands, Msg Area Commands, General Commands, SPL/I
Command File, Display File,  External Program, Statistics, Chain
Command, and Rip Display File.

The menu will look something like this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌──────────── Select Category ────────────┐ ║
║ │File Area Commands                        ║
║ │Msg Area Commands                        ▓ ║
║ │General Commands                         ░ ║
║ │SPL/I Command File                       ░ ║
║ │Display File                             ░ ║
║ │External Program                         ░ ║
║ │Chain Command                            ░ ║
║ │Statistics                                ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║       Ok ▄      Cancel ▄     Delete ▄       ║
║       ▀▀▀▀      ▀▀▀▀▀▀▀▀     ▀▀▀▀▀▀▀▀       ║
╚═════════════════════════════════════════════╝

To select a category, click on the one you want. It will
be HIGHLIGHTED then click on OK. Click on CANCEL to exit
without selecting anything. Clicking on DELETE will CLEAR
the current definition.

If you select File Area Commands, Msg Area Commands, General
Commands, or Statistics another menu will open listing the
commands available under that category.

The screen display looks and functions the same as the one listed
above.

SPL/I, an Osiris programming language command file, has to be in
the directory defined in the "Menu Path" field.

Display File is an ASCII based text file. If the caller is in RIP
mode, Osiris will use the full screen text VIEWER (has scroll
bars and ICONS) to display the file. The Display file must be in
the directory defined in the "Menu Path" field.

Rip Display File is like the "Display File" but this one is
specifically for RIP screens ONLY. If the caller does NOT support
RIP graphics, they cannot select this slot.

Chain Command, this is how the caller moves from Command record to
Command Record. When you select this command, a menu will open
listing all the command records, select the one you want to CHAIN
to. This is a VERY powerful command and there is a HELP section
devoted exclusively to Chaining. This section is listed as
"Building Roads Between Command Records"

External Program . . .. The program can be a batch, com, or
exe file and can be located anywhere. Well, DOS has to be able to
find it so it will either have to be in the OSIRIS directory or in
a PATH directory.

I will write DOOR.SYS, DORINFOx.DEF, USERx.QBS, and OUTx.QBS in
the OSIRIS directory, in case your external application needs one
of them.

If the application does, then you'll want to execute a BATCH file
that copies the file to the correct directory and THEN calls the
application instead of trying to call the application directly.

I will also passes several command line switches. Whether or not
you use them is up to you and the program you're calling.

The switches are; Connect Rate, Serial Port, Node Number, UART
Rate, Time Left In Minutes, and finally a 0 or 1 with 1 meaning
LOCAL mode. If you were to process this information with DOS batch
variables, it would be:

%1 = Connect Rate, %2 = Serial Port, %3 = Node Number, %4 = Uart
Rate, %5 = Time left in minutes, and %6 contains 0 or 1.

Keep this in mind if you are a programmer. USERx.QBS is your BBS
user record. ANY and ALL modifications to this file will be
RETAINED.

After you select the command, SM will ask you to PRESS the HOTKEY
you want to activate this command. SM will NOT allow you to have
DUPLICATE hotkeys and if you select one already IN-USE, SM will
BEEP at you and make you do it again.

After selecting the HOTKEY, the ACCESS screen will open and this
screen looks something like this:

╔═══════════════════════════════════════════════════════════════════════════╗
║                            () Greater Than or Equal To                   ║
║                            ( ) Less Than or Equal To                      ║
║ Access Level  0            ( ) Equal To                                   ║
║                            ( ) Less Than                                  ║
║                            ( ) Greater Than                               ║
║                                                                           ║
║ Active On       Node 0     Starting Time  00:00    Ending Time 00:00      ║
║                                                                           ║
║ Mon [X]         Sound File                       Cost 0                   ║
║ Tue [X]                                                                   ║
║ Wed [X]                            SPL/I Flags                            ║
║ Thu [X]                                                                   ║
║ Fri [X]     1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16 ║
║ Sat [X]    [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]║
║ Sun [X]                                                                   ║
║                                                                           ║
║              Ok ▄                                  Cancel ▄               ║
║              ▀▀▀▀                                  ▀▀▀▀▀▀▀▀               ║
║                                                                           ║
╚═══════════════════════════════════════════════════════════════════════════╝

From here you set the access level, compare method, time of day, days
of the week, command key flags (if any), which node you have to
be on to use the command (0 = ANY NODE), cost (if any) that Osiris
will subtract from your matrix credit, etc.

Any time you want to CHANGE any of the ACCESS information, click
on the ACCESS button.

To Delete or Remove any command, click on the BLUE field following
the label "Command" and when the CATEGORY menu opens, click on the
DELETE button.

When you are VIEWING a command record, you may notice that some
of the COMMAND boxes have text that includes items enclosed in
brackets, ( ).

             (DBS) : Stands For Database System
             (RIP) : Stands For Rip Display File
             (SPL) : Stands For SPL Command File
             (EXT) : Stands For EXTERNAL Program
             (DRS) : Stands For Document Retrieval System
             (CAS) : Stands For Classified Ad System
             (C)   : Stands For CHAIN Command

Reason: Sometimes a NAME like BOX.CTL doesn't tell you WHAT it
goes to. But, BOX.CTL (DRS) tells you that this is a CONTROL
file for a Document Retrieval System.

(H10)
While you CAN delete a command record, we strongly advise that
you do NOT use this option. You can create all kinds of WORK for
yourself if you do.

Chain uses a command records PHYSICAL record number to identify
WHICH record you want to jump to. If you DELETE a record, every
record number from that record to the END of the file will change
and you'll end up with chain commands linked to the WRONG record.

If you use AUTOxx.PRG and/or AUTOLxx.PRG files, those will be
thrown off.

It is much better to simply UNLINK (remove all CHAIN's to that
record) if you no longer need it. You can REUSE the record later
if you need to expand your system.

(H11)
At the top of the screen you'll find two fields, User List Display
and Phone Number Required.

                        User List Display

You have three ways of handling the display of a user's name when
or if you use the User List Display option in a command record.

If this is set to YES, ALL names will be shown. If set to YES, you
should set the USER LIST DISPLAY access level and access flags so
no one has access to it.

If this is set to NO, NOBODY will show up. If you set this to NO,
you should set the USER LIST DISPLAY access level and access flags
so no one has access to this change command.

If set to OPT, this gives EACH caller the option of having their
name withheld from the user list display.

Names withheld will be replaced with PRIVATE so the user list will
not be BLANK.

                      Phone Number Required

You can REQUIRE a phone number by setting this field to YES. If
you don't care if a user leaves their phone number, set this
option to NO.

(H12)
This section deals with USER RECORD maintenance, in one form or
another and everything is pretty straight forward.

When you select this option, you'll get a screen that looks
something like this:

╔══════════════════════════════ User Records ═══════════════════════════════╗
║                                                                           ║
║ Name   No Name                               Log-on Date  11/29/94       ║
║                                                                         ▓ ║
║ Alias  No Name                               Last Log-on  11/29/94      ░ ║
║                                                                         ░ ║
║ Internet Mailbox Name           System Password                         ░ ║
║                                                                         ░ ║
║ City   My Home Town                Phone 111111111                      ░ ║
║                                                                         ░ ║
║ Access Level  1      Total Calls 1        Time Online Today 0           ░ ║
║                                                                         ░ ║
║ Subscription Expiration Date 00/00/00                                   ░ ║
║                                                                         ░ ║
║ Files Uploaded 0       Bytes Uploaded 0                                 ░ ║
║                                                                         ░ ║
║ Files Dnloaded 0       Bytes Dnloaded 0                                 ░ ║
║                                                                         ░ ║
║ Files Dnloaded Today 0      Bytes Dnloaded Today 0                       ║
║                                                                           ║
║  Find▄ First▄ Last▄ Add▄ Del▄ UnDel▄ Next▄ Prior▄ Menu▄ Exit▄ Update▄     ║
║   ▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀  ▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀▀  ▀▀▀▀▀▀     ║
║                            Record 0 of 0                                  ║
║                                                                           ║
╚═══════════════════════════════════════════════════════════════════════════╝

To edit a field, click on the field using the LEFT mouse button.
Data entry field editing commands for this section are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field


Along the bottom of the screen, you'll find several BUTTONS.
Again, most are pretty straight forward except for the buttons
labeled "FIND" and "MENU".

                               Find

Allows you to do a search for a SPECIFIC user record. The search
will be conducted on the NAME, ALIAS, and Internet MAILBOX name.

                               Menu

This is a MINI-MENU listing several options such as: Delete By
Date, Mass Access Level Change, Mass Change UP/DN Fields, and
Print User Records.

                          Delete By Date

This allows you to delete user records when the user hasn't called
in a certain number of days. You supply the number of days.

                     Mass Access Level Change

Allows you to MASS changes access levels. You can specify SHIFT
UP, SHIFT DN, or Change Specific.

If you shift UP or DN, you give the number of access levels to
shift. For example . . . If you select Shift UP and enter 3,
everyone's access level would be boosted by 3. If you had selected
Shift DN and entered 3, everyone's access level would shift DOWN
3.

                    Mass Change UP/DN Fields

This section allows you to clear the user's upload/download
fields. Sooner or later they will need to be cleared.

                        Print User Records

Creates a TEXT file listing the users by name along with their
access level, telephone number, and last log-on date.

(H13)
Each Osiris system requires a NODEx.Bbs file, x being the node
NUMBER between 1 and 255.

A window will open asking WHICH node number. For MOST of you, 1 is
the correct answer. You would only use 2, 3, 4, etc. if you are
running multiple lines.

The first time you select 1, SM will let you know that this node
file doesn't exist and ask if you would like to create one, answer
Yes.

To edit a field, click on the field using the LEFT mouse button.
Data entry field editing commands for this section are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, PGDN, PGUP, UP ARROW or DOWN ARROW.

If you CLICK On the CANCEL button, any changes you made to the
node configuration will be discarded.

(H14)
This is the MINIMUM access the user must have to send internet e-mail.

You should create a .ANS and .RIP file called NO_EMAIL.(ANS/RIP)
and  place  the  file  in  your   OSIRIS= directory.

I'll  show this file when someone goes to post  internet  e-mail
but doesn't have access.

(H15)
       [ ] Perfect Match On Duplicate Filename Check

When you attempt to upload a file, I will check to see if that
file already exists. If it does, I will reject the attempt and
tell you the file already exists.

Normally, I look for a PERFECT match. In other words, if you
entered "TEST.ARJ" I would LOOK for TEST.ARJ.

However, it is HIGHLY possible the file exists on the system but
with a slightly different name. For example, TEST.ZIP. The files
are the same, but in different archive formats.

If you have this option set to YES, TEST.ARJ would be accepted
even thou it really DOES exist on the system.

If you set this option to NO, I will strip the file extension and
check for anything that matches the first or primary part of the
file name.

For instances, TEST.ARJ. I would strip .ARJ and look for anything
that matched "TEST". TEST.LZH, TEST.EXE, etc. would match because
the primary part of the file name for both is "TEST".

I recommend you set this option to NO, [ ].
(H16)
This sets the INTERNAL (NOT YOUR MODEMS) transmit buffer size for
speeds LESS THAN 9600 baud.

If you are running multiple lines on a single computer, I
recommend that you set this to 512. This allows roughly 2 seconds
of data while other WINDOWS or PARTITIONS are active.

If you are running on a NETWORK, I recommend you set this to 1024.

This is ONLY effective if you use the internal driver or one of
the non-intelligent serial cards. I cannot control the fossil or
the intelligent serial card(s) buffer sizes.

(H17)
This sets the INTERNAL (NOT YOUR MODEMS) transmit buffer size for
speeds GREATER THAN  or EQUAL TO 9600 baud.

If you are running multiple lines on a single computer, I
recommend you set this to 4096.

If you are running on a NETWORK or a single DOS session, I
recommend you set this to 8192.

This is ONLY effective if you use the internal driver or one of
the non-intelligent serial cards. I cannot control the fossil or
the intelligent serial card(s) buffer sizes.

(H18)
When a TX interrupt occurs, this is the number of BYTES sent to
the 16550 Uart. If you are running an XT, slow AT, Windows 3.1,
OS-2, or Desqview, set this to 16. If you are running a single DOS
session on a 386 or 486, then any number between 6 and 16 will
work.

This is ONLY effective if you use the internal driver or one of
the non-intelligent serial cards. I cannot set the 16550 FIFO size
if you use a fossil or one of the intelligent serial cards.

(H19)
This is the maximum amount of time, in minutes, between outbound
call attempts. It is suggested that you go no lower than 5 to avoid
collisions.


(H20)
This deals with the ON-LINE TIME/KILOBYTE banking system and
determines the MAXIMUM amount of TIME you can bank.

Setting this to 0  disables the depositing of time.

(H21)
This deals with the ON-LINE TIME/KILOBYTE banking system and
determines the MAXIMUM KILOBYTES (1024 bytes) you can bank.

Setting this to 0  disables the depositing of kilobytes.

(H22)
This defines the number of minutes of inactivity, you do not type
anything in, before I'll automatically disconnect.

I recommend that you set this to at least 5 minutes but no more
than 10 minutes.

(H23)
This defines the number of minutes you have to enter your name and
password before I'll disconnect.

I recommend you set this to 1 minute and no more.

(H24)
During the input process, I will check the Keyboard for local
input and the system clock to get the current time. Under a
multitasker such as Windows, Desqview, or OS-2 this drags down the
CPU.

If you set this field to 30 or more, but no higher than 90, I will
loop THAT many times waiting for SERIAL input before checking the
clock or the keyboard. This can REALLY make a multitasking system
run a LOT faster.

There is a DOWN SIDE to this. Acting on local keyboard input is
very slow, but well worth it.

(H25)
Because several NETWORKS have the same signature, I want you to
TELL me that Desqview is ACTUALLY being used.

(H26)
This toggles DPMI time slicing on. You may find this
helps under OS/2. Try it WITH DMPI turned ON and
with DMPI turned OFF.
(H27)
If you are running under Windows, toggle Windows Timeslicing
ON.

A word of advice, Windows is VERY sensative to time slicing
and you should set windows to allow OSIRIS to handle all the
time slicing. Otherwise, your system will end up spending
more CPU time "SLICING" than it does running your applications.

(H28)
If this is toggled to YES, [X], and you select to download a file
located on a CD-ROM, Osiris will copy it to the hard drive when
you select the download command. It'll only copy the file to the
hard drive one time. If the download fails and you select to
download again, the file is not copied a second time.

I don't feel this is really needed and we don't do it on our BBS.
But several BBS packages handle CD-ROM's this way and several
customers thought Osiris should do it that way so we added this as
an optional switch.

We timed a download on our system and the total download time with
the COPY set to YES was more than a download with COPY set to NO.
It's your call.

(H29)
You should ALWAYS set this to YES. This tells me to check the file
name you just entered, when uploading, to see if it already exists
on the system.

It is almost redundant to have this field because you can never
REALLY turn it off.

The file indexing system will not index duplicate files.
Therefore, two files with the same name cannot co-exist on the
system. One would be accessible, the other would not.

(H30)
If this on, highly recommended, I will scan any NEW upload for
virus infestation using TBSCAN.EXE before I move the file to the
correct directory. If a file contains a virus, I will delete the
file and you will not get credit for the upload.

Again, I HIGHLY RECOMMEND that you engage this function.

(H31)
Delete Upload If {7} Percent Of The Files Are Older Than {1992}

When someone uploads something, I will check the file dates with
the YEAR you define here. Any file OLDER than this is flagged as
TO OLD.

After all the files have been check, I'll compute a PERCENTAGE of
OLD filed verses the TOTAL number files contained within the
archive. If this percentage exceeds the Percent field, the upload
is rejected and the caller does not get credit for the upload.

Example:

The FILE DATE field contains 1993 and the Percent field contains
10.

Caller uploads a ZIP file containing 50 files. After checking the
archive, I found 15 files created BEFORE 1993.

I checked 50 files so 15 OLD files would equal 30 percent. The
Percent field contains 10, 35 is greater than 10 so the upload is
rejected.

If you don't want to use this, set the FILE DATE to 0.

The purpose, keep callers from cluttering up your system with OLD
outdated files.

If you Do use this, keep in mind that many archives do contain
static files, like ORDER FORMS and DOCUMENTATION. Don't set your
percentage or RATIO to Low or you may find that few files pass the
test.

(H32)
If this on, I will attempt to extract the newly uploaded file, if
it is an archive, to determine if the archive is intact. If I
cannot extract the files, I will delete the archive and you do not
get credit for the upload.

I recommend you turn this option on. It MUST be turned on if you
want to use the virus scan feature.

(H33)
This is the path and file name of the language file. The language
file contains all the colors and text prompts used by Osiris.

The default is LANG.DAT. If you move the file out of the current
directory, you MUST use the full drive, path, and file name. E.g.
C:\OSIRIS\LANG.DAT

Not only does lang.dat contain 98 percent of the text and color,
it also contains command key assignments for certain functions
that requests specific input, like YES/NO prompts.

(H34)
This is the Name of the system operator. It doesn't give anyone
with that name extended access or benefits. It is simply used in
several areas such as messages to the sysop.

(H35)
This is the name of your CBIS. Several DOOR formats require the
name of the BBS. You should make up something if you don't already
have a name for YOUR system.
(H36)
This is the SECONDARY language file used by Osiris. It contains
rarely used text and screen displays.

The secondary language file is actual TWO files, the primary
BLKTXT.BBS and the index file, BLKTXT.IDX.

However, you only enter the name of the primary file. I will strip
the extension and replace  it with .IDX to find the index.

E.g. BLKTXT.BBS

I would look for BLKTXT.IDX

                       Changing Blktxt

Blktxt.bbs contains BLOCKS of text, one entire display per record.

Almost all the displays have TWO records, one for ANSI and one for
those that do NOT support ansi.

E.g. Block.001 and Block.002 (two records) contains the LINE
EDITOR menu. Block.001 is for ANSI and block.002 is for ASCII. You
cannot switch the ORDER. In other words, block.001 MUST contain
the ANSI display and Block.002 MUST contain the ASCII display.

The file BLKTXT.ZIP contains a bunch of individual files,
BLOCK.001 - Block.xxx. These individual files make up the records
found in Blktxt.bbs.

To modify any record, edit the Block.xxx files (keeping in mind
that there are TWO files associated with nearly every display)
that deal with the section you want to change and then recompile
Blktxt.bbs with the program "build.exe". Just run BUILD.EXE and it
will collect the BLOCK.xxx records in the proper order.

There are several records that deal with statistic graphs. I would
recommend that you do NOT tamper with those records. Everything is
POSITION sensitive and if you attempt to modify those records, you
will mess things up.


(H37)
This is the full drive and path to the RIP resource files
Buttons.bbs, Rip.bbs, and Rip.idx. If this field is empty, the
OSIRIS= path is assumed.

(H38)

This is DBASE type picture mask that determines the format of the
PHONE number.

Like Dbase, a mask can contain 9, A, or X. Other characters are
displayed. 9 means only a NUMBER is accepted, A means only an
ALPHA character (A - Z) and X means anything.

Example: (999) 999-9999

This would force you to enter Area code (3 digits), dialing prefix
(3 digits), and a 4 digit suffix.

The number would be stored in the use record without the display
characters ( ) or -. (314) 686-0120 would be stored as 3146860120
to conserve space.

(H39)
You can set-up page hours for each day of the week.

      Start    End      Display This If
      Time     Time     Page Is Not Allowed

 Mon  00:00    00:00    [            ]

 Tue  00:00    00:00    [            ]

 Wed  00:00    00:00    [            ]

 Thu  00:00    00:00    [            ]

 Fri  00:00    00:00    [            ]

 Sat  00:00    00:00    [            ]

 Sun  00:00    00:00    [            ]

The display file, if you define one, must be in the menu directory
defined for the CURRENT command record.

(H40)
The default access assigned to EACH new caller. I recommend that
you use 2 or higher to give yourself a little room to play.

(H41)
The default is to associate the time limits per day and download
limit per day to a 24 HOUR format.

In other words, the limits will be reset at the stroke of
midnight.

If you would rather have the limits based on a 7 day cycle,
toggle this to yes, [X]. The limits will be reset every 7 days
based on the CALLERS first log-on date.
(H42)
Area access flags assigned to NEW callers.
(H43)
Command key access flags assigned to NEW callers.

(H44)
SPL/I general purpose flags assigned to NEW callers. See SPL/I
documentation for more information on these flags and how you
might use them.

(H45)
If you want to run a "PAY AS YOU PLAY" system but would rather
bill the caller by the amount of TIME he or she actually spends on
time then define the cost, in pennies, you want to charge per
minute.

You also have to define the "ACCESS LEVEL WHEN SUBSCRIPTION
EXPIRES". Defining both activates this feature.
(H46)
If you run a "PAY AS YOU PLAY" system, this is the access level
you get when your subscription expires. Enter 0 if you do not plan
on running a PAY system. See PAY SYSTEMS for MORE information.

(H47)
Anyone with an access level greater than or equal to the access
level defined here is excluded from the subscription system, time
and date.
(H48)
Charge 0 Cents Per 0  Kilobytes Dnlded, Exclude Access Level 0

These three fields deal with one of the BILLING systems. See
section on PAY systems for an explanation.

(H49)
If you have a POINT number and you support Network MATRIX mail,
enter the point number HERE. See section on MATRIX mail for
further details.


(H50)
This is the access level required to KILL or DELETE files, in the
file area(s), that you did NOT upload.

Normally I will only allow you to kill a file you uploaded,
mistakenly uploaded wrong file or maybe you need to kill an OLD
version so you can upload the NEWER version. However, co-sysops or
sysops need the ability to delete ALL files.

(H51)
This is the access level required to rename a file even if you did
NOT upload it.

Normally I would only allow you to rename a file providing you
were the one that uploaded it and of course, providing the name
you WANT to use isn't already in-use. But, sysops or co-sysops
need the ability to rename ALL files.

(H52)
You can edit or change the short (80 character) or extended file
description on any file that YOU upload.

This field lets the sysop or co-sysop edit or change the
description on a file they did not upload.

(H53)
If this contains a 0, default, any upload will go into the CURRENT
file area.

Under normal circumstances, this would be desirable and all you
would have to do is FREE the upload  once you have checked it out.

This starts to become a problem if you have MULTIPLE file SYSTEMS.
If the caller is in one of the alternative file systems which
happens to be a CD, they have to go BACK to the primary file
system and find an area to upload.

This doesn't seem like a big deal to us, but some callers seem to
think it is.

You can setup a specific file area (Primary File System) to hold
uploads. You may,  if you like, set the access level so high
nobody will be able to change into that area.

Then you define the file area number in the UPLOAD AREA field.

When someone selects to upload, their upload will automatically go
to this area and it doesn't matter WHICH file systems they happen
to be in.

(H54)
This is the name of the COMMAND control file, something I will get
into a little later, and it MUST be located in the Osiris
directory.

When You created the NODEx.BBS, SM uses the name OSIRIS.BBS and I
recommend that you keep that name.

(H55)
Matrix cost is the AMOUNT to charge for EACH Fido e-mail message
you enter. Generally this is 25 to 30 cents. When you ENTER a
message, that cost is deducted from your user record MATRIX
credit field.

Matrix cost is also used by the Time and Kilobyte billing system.
(H56)
Access level required to flag a Fido e-mail message as CRASH.

(H57)
This is used by the ONLINE store when displaying currency values.

The default is to use a dollar sign, $. You may, if your currency
is not in dollars, need to use something else.

(H58)
This is the modem string that gets you modem ready to answer a
call and it should, in most cases, end with a vertical bar or ^M.

(H59)
If you modem is set to AUTO-ANSWER, do *NOT* use this field.

If you want Osiris to TELL the modem to pick-up, place the modem
commands to do that in this field.

Generally, this would be ATA|

Notice the vertical bar, this means CR/LF. In most cases, the
modem will require this.

Again, if you do use ATA in this field, make SURE you modem does
not attempt to AUTO-ANSWER. If the MODEM trys to answer, ATA will
cancel the answer and the modem will just sit there reporting RING,
RING, RING.... until the caller gives up.

(H60)
Serial port to use for this node, 1 - 99.

(H61)
This is the STARTING serial rate Osiris will use when it sets up
the modem to wait for a call.

This field is IGNORED if you have a LOCKED or FIXED DTE rate.

Valid settings are: 300, 1200, 2400, 4800, 9600, 19200, 38400,
57600, or 115200

Notice that 14400 is not a valid setting. 14400 is a MODEM rate,
not a serial rate. 14400 can ONLY be used if you have a FIXED DTE
rate. A FIXED DTE rate means this field is basically ignored.

(H62)
This is the access level required to MOVE a file even if you
are not the sysop or you were not the one that uploaded the file.

(H63)
You create a file area using SM/Boards/Filboard.Bbs option.
When you select this option, you'll get a screen that looks
something like this:

╔══════════════════════════════ Filboard.Bbs ══════════════════════════════╗
║                                                                          ║
║ Area Name                                                               ║
║                                                                        ▓ ║
║ File Path                                                              ░ ║
║                                                                        ░ ║
║                              () Greater Than Or Equal To              ░ ║
║                              ( ) Less Than Or Equal To                 ░ ║
║ Area Access Level 0          ( ) Equal To                              ░ ║
║                              ( ) Less Than                             ░ ║
║                              ( ) Greater Than                          ░ ║
║                                                                        ░ ║
║                                                                        ░ ║
║ Category                                                               ░ ║
║                                                                        ░ ║
║                     1   2   3   4   5   6   7   8   9  10  11  12  13 4░ ║
║ Area Access Flags  [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] ░ ║
║                                                                        ░ ║
║                     1   2   3   4   5   6   7   8   9  10  11  12  13 4 ║
║▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░  ║
║Auto Add▄ Jump▄  First▄  Last▄  Add▄  Del▄  Next▄  Prior▄  Exit▄  Update▄ ║
║ ▀▀▀▀▀▀▀▀  ▀▀▀▀   ▀▀▀▀▀   ▀▀▀▀   ▀▀▀   ▀▀▀   ▀▀▀▀   ▀▀▀▀▀   ▀▀▀▀   ▀▀▀▀▀▀ ║
║                            Record 1 of 1                                 ║
║                                                                          ║
╚══════════════════════════════════════════════════════════════════════════╝

To edit a field, click on the field using the LEFT mouse button.
Data entry field editing commands for this section are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, PGDN, PGUP, UP ARROW or DOWN ARROW.

The following settings are available.

                            Area Name

This is the NAME of the file area and should be unique.

This name will be displayed when you change area, do a new upload
search, text find, and when you specify that area information
should be displayed when a specific command record is used.

                            [ ] CD-ROM

Toggle this to YES, [X], if this file area is a CD-ROM. This is
VERY important and you MUST do it.

                            File Path

This is the full drive and path to the physical files associated
with this file area.

                        Area Access Level

This is the access level you MUST have to gain access to this
area.

The FIRST file area you define MUST be accessible to ALL callers.
I MUST KNOW that I can switch you to file area one in case of
trouble.

                      Access Compare Method

This mean HOW do you want me to compare the callers access level
with the access level required to enter the area.

You  have FIVE options:

                     ( ) Greater Than Or Equal To
                     ( ) Less Than Or Equal To
                     ( ) Equal To
                     ( ) Less Than
                     ( ) Greater Than.

Your TYPICAL BBS or CBIS program uses Greater Than or Equal To.

                      [ ] Auto Free Uploads

By default, all NEW uploads are held and you can neither see nor
download them until you (or your co-sysop) FREES them. However,
you may want files uploaded in a specific area to be made
available for downloading ASAP. If you do, toggle this to YES.

                        Area Access Flags

You MUST have the SAME EXACT AREA ACCESS FLAGS turned on to gain
access to this area.

This is used to SUB-DIVIDE access levels so two people with the
same access level may or may not have access to the same area,
even if the area access level is the same.

Using this can produce a rather complex system to manage if you
aren't VERY careful. I recommend that you use area access flags
sparingly.

Example:

Assume area 2 has access flags 1, 3, and 15 turned on. For you to
get INTO that area, you must ALSO have area access flags 1, 3, and
15 turned on. It doesn't matter if your access level IS the same
as the area access level, your FLAGS have to match the ones for
the area.

Only the flags need to enter the area are check. That means that
if you also have area flags 5 and 16 on, it isn't going to matter.
They are ignored because only 1, 3, and 15 are needed.

There are 16 flags and that gives you over 32000 different
combination to work with.

Again, using area flags can complicate your system and I recommend
that you don't use them right away and if you DO decide you need
them, use them sparingly.

                        General App. Flags

These are provided for EXTERNAL applications that deal with file
areas. Each application that requires the use of one or more of
these flags will explain what, why, and how.

(H64)
A conference area is a PUBLIC message area. Messages POSTED in this
area can be read and replied to anyone that has access. Use the
SM/Boards/Msgboard.Bbs option to create each message areas.

Again, I wish to stress the word "PUBLIC". Conference areas cannot
by their very nature contain private messages. In fact, Fidonet Echomail
and USENET newsgroups do not allow nor do they make provisions for
PRIVATE posts.

When you select SM/Boards/Msgboard.Bbs you'll get a screen
that looks something like this:

╔═════════════════════════════ Msgboard.Bbs ════════════════════════════════╗
║                                                                           ║
║Area Name                                                                 ║
║                                                                         ▓ ║
║Message Path                                                             ░ ║
║                                                                         ░ ║
║Pack Trigger 0       Pack Level 0                                        ░ ║
║                                                                         ░ ║
║                    () Greater Than Or Equal To                         ░ ║
║                    ( ) Less Than Or Equal To                            ░ ║
║Access Level 0      ( ) Equal To                                         ░ ║
║                    ( ) Less Than                                        ░ ║
║                    ( ) Greater Than                                     ░ ║
║                                                                         ░ ║
║                   1   2   3   4   5   6   7   8   9  10  11  12  13  14 ░ ║
║Area Access Flags [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]░ ║
║                                                                         ░ ║
║Origin                                                                   ░ ║
║                                                                          ║
║▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░  ║
║      Jump▄  First▄  Last▄  Add▄  Del▄  Next▄  Prior▄  Exit▄  Update▄      ║
║       ▀▀▀▀   ▀▀▀▀▀   ▀▀▀▀   ▀▀▀   ▀▀▀   ▀▀▀▀   ▀▀▀▀▀   ▀▀▀▀   ▀▀▀▀▀▀      ║
║                           Record 1 of 1                                   ║
║                                                                           ║
╚═══════════════════════════════════════════════════════════════════════════╝

To edit a field, click on the field using the LEFT mouse button.
Data entry field editing commands for this section are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, PGDN, PGUP, UP ARROW or DOWN ARROW.

The FIRST area you define MUST be accessible to ALL callers. I
must KNOW that I can place you in area ONE if something happens. I
suggest the first area be a GENERAL conversation area.

                            Area Name

This is the name of the area and is displayed when you do an area
change, join a conference, and when you request the display of
message area information from within a command record.

                            Board Type

This determines the TYPE of message area and you must select one
of the following:

[ ] LOCAL, means the messages NEVER leave your system and new
messages are instantly available for reading.

[ ] LOCAL/REV, means the messages NEVER leave your system but they
should NOT be available for reading until you OK them.

[ ] ECHO, means the messages WILL be leaving your system (how
doesn't matter) and the messages should be made available for
exporting OFF the system and reading as soon as they are entered
, NOT RECOMMENDED!.

[ ] ECHO/REV, means the messages WILL be leaving your system (how
doesn't matter) BUT . . . not before you OK them. Recommended for
Fidonet Echomail or RCRElay Echomail areas, can save you a LOT of
headaches.

[ ] Pass Through, means this area's messages will be deleted ASAP
as soon as they leave. You should NOT give ANY caller access to an
area defined as Pass Through.

This type of area is strictly for Echomail (fidonet) processors to
work with and NOT for humans.

[ ] UUCP means the messages are coming from and going to Internet
newsgroup areas and messages are posted as soon as possible.

[ ] UUCP/REV, means the messages are coming from and going to
Internet newsgroup areas and messages posted should be held until
you can review them.

                           Message Path

This is the full drive and path pointing to the directory
containing the messages for THIS area.

Messages are stored in two files, HDRx.BBS and TXTx.BBS with x
being the internal area number. Area numbers start with 1.

The format of stored messages is very efficient and We've been
using it for about 5 YEARS. In fact, several Public Domain BBS'
have made attempts at duplicating my storage format. They are
close, but not as efficient or as reliable.

                           Access Level

This is the access level you have to have before you can get into
this area.

                      Access Compare Method

This mean HOW do you want me to compare the callers access level
with the access level required to enter the area.

You have FIVE options:

                   ( ) Greater Than Or Equal To
                   ( ) Less Than Or Equal To
                   ( ) Equal To
                   ( ) Less Than
                   ( ) Greater Than.

Your TYPICAL BBS or CBIS program uses Greater Than or Equal To.

                        Area Access Flags

You MUST have the SAME EXACT AREA ACCESS FLAGS turned on to gain
access to this area.

This is used to SUB-DIVIDE access levels so two people with the
same access level may or may not have access to the same area,
even if the area access level is the same.

Using this can produce a rather complex system to manage if you
aren't VERY careful. I recommend that you use area access flags
sparingly.

Example:

Assume area 2 has access flags 1, 3, and 15 turned on. For you to
get INTO that area, you must ALSO have area access flags 1, 3, and
15 turned on. It doesn't matter if your access level IS the same
as the area access level, your FLAGS have to match the ones for
the area.

Only the flags need to enter the area are check. That means that
if you also have area flags 5 and 16 on, it isn't going to matter.
They are ignored because only 1, 3, and 15 are needed.

There are 16 flags and that gives you over 32000 different
combination to work with.

Again, using area flags can complicate your system and I recommend
that you don't use them right away and if you DO decide you need
them, use them sparingly.

                           Pack Trigger

This is the MAXIMUM number of messages you want to in THIS area.
This is used by CAT (auto maintenance system).

                            Pack Level

If I have to REMOVE messages because the total number of messages
in the area exceeds the Pack Trigger Level, this is the number of
messages to LEAVE after packing the area. I recommend, to reduce
drive fragmentation, this number should be 1/3 the pack trigger
level.

In other words, if the pack trigger level is 300, the pack level
should be no more than 100.

Never set the PACK level to ZERO. This can cause unpredictable
results.

                              Origin

This field is provided for external applications. If an
application requires the use of this field, it will explain why,
what, and how.

                          [ ] Word Wrap

This tells me that I should END each line of a message, that you
type in, with a HARD carriage return or allows the line to WRAP.

This should ALWAYS be set to YES for message area unless the area
deals with PcRelay.

                        [ ] Alias Allowed

If set to YES, you can (providing you have defined one) use your
alias instead of your REAL name. Most Fidonet echomail areas do
NOT allow an Alias so check before allowing this.

                      [ ] Area Is Invisible

If you want to HIDE an area making it impossible to JOIN using the
normal JOIN command, toggle this flag to YES.

If this flag is set to YES, Osiris will not allow the caller to
JOIN/UNJOIN this area. In fact, the area will never show up.

Osiris will also NOT auto-assign the area to a NEW caller.

The ONLY way the caller can ADD/REMOVE this area is if you add or
remove the area via the SPL/I command "join_area()".

This gives you a great deal of control over WHO gets into which
area based on just about any thing you can think of.

This also lets you create your OWN join/unjoin subsystem and also
lets you personally handle giving new callers message areas.

           Actually Creating The Message Database Files

This is VERY important, Osiris MUST be used (In LOCAL MODE) to
create the actual message database files for CONFERENCE areas.

When you log-on locally, I will validate the message databases and
creates any that are missing.

I will only do it in LOCAL mode because of the amount of time, 15
to 20 seconds, it takes to validate several hundred messages
areas.
                            Templates

The best way to create several like message areas at once is to
create the first area, define all the attributes (fields) and then
use that area as a template when creating others.

Using an existing area as a template means you only need to change
one field, the area name.

To use an existing area as a template, simply JUMP to that record
and hit the ADD button.
(H65)
When you import, with Import.exe, or post a new message to a
message area defined as ECHO or ECHO/REV, Osiris sets a Echo flag
ON and this indicates the message NEEDS to be exported.

If, for some reason, you need to RESCAN an area use this option
before running export.

(H66)
When you import, with Import.exe, or post a new message to a
message area defined as ECHO or ECHO/REV, Osiris sets a Echo flag
ON and this indicates the message NEEDS to be exported.

If, for some reason, you need to STOP export from sending the
messages to the system(s) you feed or to the system you GET the
area from, use this option.


(H67)
Osiris provides you with a method of subdividing or GROUPING like
conference areas under a "CATEGORY". You might do this if you have
a LOT of message areas.

You can define up to 21 different CATEGORIES. Keep in mind that
this was designed to be a BROAD BASED group so pick the categories
carefully so the maximum number of message areas can fit under a
single category. Maximum, but not TOO many.

To define categories, go to the Boards/Message Categories
subsytem.

When you select Message Categories, you'll get a screen that looks
a bit like this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌────────── Message Categories ───────────┐ ║
║ │All Areas                                 ║
║ │--- Open Slot ---                        ▓ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                         ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║          Add ▄  Del ▄  Edit ▄  Exit ▄       ║
║          ▀▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀▀▀▀▀       ║
╚═════════════════════════════════════════════╝

To EXIT this section, press EXIT mouse button. To Add a
category, click on a slot labeled "--- Open Slot ---"
and then Click on ADD.

To PLACE a message area into one of the categories, go to the
Boards/Msgboard.Bbs subsystem. You'll see a field labeled
"Message Category". Just CLICK on the field and SM will present
you with a list of all the categories you have defined.

Osiris only uses the CATEGORY field when the caller goes to ADD or
REMOVE conference areas. He or she is asked to select a CATEGORY
and only those areas falling into that category will be displayed.

The caller can mix and match areas from different categories. That
is to say, you can have five areas selected from category number
1, 3 from category number 2, 9 from category 7, etc.

(H68)
You can define up to 20 external events to be executed at a preset
time on selected days.

Each event has time to execute, errorlevel to exit with, and the
DAYS of the week the event is active.

Time to execute is in 24 hour format, HH:MM. Just CLICK on the
field and enter the time.

Errorlevel, the errorlevel you want me to exit with when the event
is executed. Errorlevels should ALWAYS be higher than 50. We'd
like to reserve 50 and below for internal use.

DAYS of the week are the days the event is active. Click on the
box(s) that bare the label for the day or days you want. You can
select one day, any combination, or all seven.

To DISABLE an event, don't set any days.

To CLEAR an event, set the ERRORLEVEL to 0. 0 will cause the other
fields associated with the event to CLEAR.

It *IS* possible to set the errorlevel to 0 however, I will NOT
execute any event that has an errorlevel of 0.

I will ONLY execute the event ONE time per day and FIVE minutes
prior to the event, I will bring the modem OFF-HOOK.

One question that has been asked numerous times, HOW do you tell
Osiris WHAT to do during an event? The answer is, you don't.
Osiris does NOT care WHAT you do during your event. It simply
exits with the errorlevel, you trap for the errorlevel in your
batch file and do whatever.

Below is a SAMPLE runbbs.bat file that illustrates this.
Errorlevels 51, 52, 53, and 54 were defined as EVENT errorlevels.

By the way, this is a FULL functional Internet HUB batch file that
calls up twice a day to pickup and drop of Internet e-mail and
news. It also handles INCOMING UUCP sessions.

:TOP
C:
CD\OSIRIS
osiris -n1 -w
IF ERRORLEVEL 254 GOTO UUCP
IF ERRORLEVEL 54 GOTO PICKUP2
IF ERRORLEVEL 53 GOTO PICKUP2
IF ERRORLEVEL 52 GOTO MIDNIGHT
IF ERRORLEVEL 51 GOTO PICKUP
IF ERRORLEVEL 50 GOTO END
GOTO TOP
:PICKUP
ghost
scorpion
UUCICO  -V -k4096 -x0 -t60 -r3 -ga -s netcomsv
modem /P4 /B57600 /SATH1M0S0=0
scorpion
ghost
GOTO TOP
:MIDNIGHT
del import.log
cd\osiris
EXPORT /O /A1.296.5.0
viper /E
cat
ulink
ftpmail
list
mail_s
snews
news_s
scorpion
boot
:UUCP
ghost
scorpion
mail_s
list
ftpmail
scorpion
goto TOP
:PICKUP2
ghost
mail_s
ftpmail
scorpion
snews
UUCICO  -V -k4096 -x0 -t60 -r1 -s netcomsv
modem /P4 /B57600 /SATH1M0S0=0
viper
scorpion
ghost
list
snews
scorpion
GOTO TOP
:END

(H69)
This gives you a QUICK way of REMOVING all the
messages in a specific area.

SM will scan the user files and reset the last
read pointer for anyone and everyone that has the
area selected.

(H70)
This option scans the user records and sets everybodies
message categories to 0 or ALL areas.

This option might come in handy if you decide to change
your message categories.
(H71)
This should NOT be confused with defining FILE AREAS. File Systems
CONTAIN file areas. Defining MULTIPLE file systems is OPTIONAL and
the PRIMARY use is to make handling CD-ROM areas EASIER.

Again, since this cannot be stressed too many times, a FILE SYSTEM
is N O T the same as a FILE AREA. FILE SYSTEMS ** CONTAIN ** file
area(s).

Example:

Primary File System
     File Area "Word Processors"
     File Area "Term Programs"
     File Area "Apple Programs"
     etc.
Secondard File System
     File Area "GIF"
     File Area "OS/2 Programs"
     File Area "Unix Programs"
     etc.

Osiris allows you to create multiple file systems. A file system
consists of a several database's used to define file areas and
store information about files that are AVAILABLE for downloading.

You can define a different FILE SYSTEM for each CD-ROM and put the
file areas for that CD in it's OWN  personal FILE SYSTEM. This
makes MAINTENANCE much easier when you swap out an OLD disk with a
NEW one or you have more disks than CD-ROM drives.

Osiris has a DEFAULT file system, the one you are in when you
first log-on. This is labeled "Primary File System" and it is
generally used for file areas on your READ/WRITE drives.

Each file system definition record has 8 fields you HAVE to fill
out and one OPTIONAL field.

Field       What it is
Label
----------------------------------------------------------------
Base Name : This is the NAME of the file system, the one shown to
            the caller.
Files.Bbs : The name of the file used to store information about
            the files available for download and it must be
            UNIQUE.
Files.Idx : The name of the file used to store INDEX information
            about the files and it must be UNIQUE.
Areas.Idx : The name of the file used to store INDEX information
            about the file AREAS and it must be UNIQUE.
Fileboard.Bbs: The name of the file used to store information
               about the FILE BOARDS and it must be UNIQUE.
FileCat.Bbs : The name of the file used to store the names of the
              different categories and it must be UNIQUE. Even if
              you don't plan on using categories, you still have
              to define this file.
Filesbbs.Loc: The name of a special LOCK file used to guard against
              SHARE not working right and it must be UNIQUE.
Desc.Bbs: Name of the file used to hold the EXTENDED descriptions
          and it must be UNIQUE.

You really don't need to know what each file is used for but I've
provided the information "Just in case".

Each file system also has an access level and a compare method
along with access flags and they function the same as the area
access levels and flags.

If the caller doesn't have access to a file system, it simply does
not show up.

Each file system has a field labeled "Validate Using".

This field should contain the FULL drive, path, and filename of a
file that is UNIQUE to the CD. Osiris will use this to verify the
CORRECT CD is in.

If the verification fails, the area will simply not show up.

                      Defining a File System

Step 1> Load SM go to BOARDS/FILEDEF.BBS

Step 2> Add a New Record.

Step 3> Move to the NEW record and change the file names so they
        are TOTALLY unique. You MUST change every single filename.
        The names are LABELED with their BASE or original names.

Step 4> Enter the drive, path, and file name that is FOUND on CD
        in the Validate Using Field. Osiris will use this to verify
        the CORRECT CD is in the drive for this file system.

        If you leave this field empty, Osiris will skip the
        verification process.

Step 5> Select the MISC/Select File Group option and switch to the
        NEW file group. This tells SM which file system it is working
        with when you select any option that deals with the file area.

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
   Skip Steps 6 and 7 if you are going to use the AUTO ADD option.
   See section "CD-ROM, Step By Step Guide".
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Step 6> Go To the BOARDS/Filboard.Bbs option and define your first
        file area.

Step 7> Go to the Files/File Area Manager Section to build the correct
        Files.bbs replacements.

Step 8> Go to COMMAND/Osiris.Bbs section and plug in the Change File
        Systems command. You'll find the command listed under the
        File Area Commands.

One final note, the first RECORD is fixed except for the NAME
field. You can change the name field, if you use a language other
than english or you simply don't like the default name. But,
cannot changes to ANY other field on the first record.

That's pretty much all there is to it. Now, any time you want to
work on this particular file system, just repeat step 5.

                    How This effects Osiris.

If you do a new upload search in a file system other than the
primary system, the search date is based on the LAST time you
called. Since the idea behind this system was to make handling CD-
ROM drives easier, New uploads aren't likely but the command
needed to be available.

If you had files tagged for downloading, Osiris will start you in
the file system THOSE files were in the next time you log-on.
Providing you want to continue with the download, otherwise it'll
start you in the primary file system.

If you DO select to add those files to the download queue and they
were NOT in the PRIMARY file system the new upload search
, providing you had it plugged into a startup.bbs slot, will be
skipped.

Downloads, you cannot have files tagged for downloading in
multiple file systems. All the files you are going to download
must be in the current file system, in fact Osiris will make sure
of that.

*IF* you have files tagged and select to switch file systems,
you'll get a warning message and the option of aborting the
switch.

The primary reason; greatly reduces disk thrashing on carousal
drives.

                         Recommendations

If it were me, I'd set-up my system:

Primary File System : Contains Files on my READ/WRITE drives.

Sub File Systems: 1 For EACH CD-ROM disk. Most CD's have about 50
directories so that would be 50 or so file areas per subsystem.

(H72)
When you enter this section there may be a slight delay, the
actual delay time will vary according to the number of files you
have on your system so don't get alarmed. I'm actually scanning
all your files attempting to find and LOG new uploads, you'll find
out why in a minute.

This section of SM works on GROUPS of TAGGED files. A TAGGED file
is HIGHLIGHTED. To TAG a file, move to the file name and click
using the LEFT mouse button. To UNTAG a file, repeat.

The primary display screen shows 85 files at once, 5 to a row and SM
can handle a maximum of 1500 files PER area. You should NOT exceed
that number and you will not, even if the area is on a CD-ROM.

Pay special attention to the COLOR of the file name. Normally, the
file name is displayed in BLACK.

If it is FLASHING, that file has NOT been freed for downloading.
In other words, it is a NEW upload.

If the file name is displayed in BRIGHT WHITE, it has an EXTENDED
description.

You can SCROLL the display using PGUP, PGDN, UP ARROW, DOWN ARROW
or the SCROLL bar on the right side of the screen.

To VIEW all of the information about any tagged file, Click on the
button labeled INFO.

A screen will open displaying the name of the file, file size,
times downloaded, upload date, last date downloaded, Free file
, the short 80 character description, download password, delete
after download, the access level required to see/download the
file (may or can be different from the area access level or
download command access level), and who uploaded the file.

The display screen will look something like this:

╔════════════════════ Extended File Information ════════════════════╗
║                                                                   ║
║ File  HELP.UC2     Size  590900      Times Downloaded  0          ║
║                                                                   ║
║ Upload Date  12/13/94  Last Downloaded 12/13/94                   ║
║                                                                   ║
║ [ ] Free File    [ ] Delete After Downloading                     ║
║                                                                   ║
║ Download Password             Access Level  0                     ║
║                                                                   ║
║ Uploaded By  Osiris XLT                                           ║
║                                                                   ║
║ Description No Description                                        ║
║             ▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░    ║
║                                                                   ║
║                   Ok ▄     Update ▄      Cancel ▄                 ║
║                   ▀▀▀▀     ▀▀▀▀▀▀▀▀      ▀▀▀▀▀▀▀▀                 ║
╚═══════════════════════════════════════════════════════════════════╝

You can change any field by moving the cursor to that field and
clicking the LEFT mouse button with the exception of the field
labeled "Size".

This field will auto-adjust itself if you click on it. If you do
something that MAY affect the size of the file, you should always
click on this field.

Data entry field editing commands are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Changes made to the file record will ONLY be saved if you click on
the UPDATE button. Click on CANCEL if you want to ABORT the BATCH
view.

You can also VIEW a SINGLE file by CLICKING on it with your MIDDLE
mouse button.

                          Changing Areas

You can change file areas by clicking on the button labeled
"Areas" and selecting the NEW area from the menu.

You can also MOVE using the LEFT/RIGHT arrow keys, HOME, and END.
RIGHT takes you to the NEXT area, LEFT takes you to the previous
area, HOME takes you to the FIRST file area, and END takes you to
the LAST file area.

Most of the operations available to you must be selected from the
OPERATIONS menu which you access by clicking on the button labeled
"MENU", pressing M, or clicking the MIDDLE mouse button.

When you do, a menu will open listing all the available
operations. Keep in mind that most of the operations work on
TAGGED files.

                           Delete Files

Removes the TAGGED files from your FILES.BBS and optionally from
your hard drive.

You have the option of having the files deleted in BATCH mode,
otherwise, I'll ask you to confirm each file before deleting it.
tagged will be deleted without individual confirmation.

The file record is NOT physically removed from FILES.BBS but
removed from the DLL chain which makes it inaccessible. You have
to select the "Remove Deleted Records" option for that to happen.

However, you would only select that option when you are finished
deleting files from ALL areas.

                            Move Files

Move the TAGGED files to a different file area.

You cannot move a file to an Area that has files in it that have
NOT been freed for uploading. You also cannot move a file to or
FROM a CD-ROM area.

When I move the file, I'll reset the UPLOAD date to the CURRENT
date, don't tamper with this date. I will not alter the files
PHYSICAL date/time stamp.

I will also adjusts the files download access level to the access
level required to enter the new file area.

You TWO options when moving files, BATCH mode or SINGLE.

Select BATCH mode if you want ALL the tagged files moved to the
SAME area. Select SINGLE if you want to move a few files to one
area, a few files to another area, and so forth.

After I've moved all the tagged files,  I'll repack files.bbs and
rebuild the indices.

                         Free New Uploads

This frees all the new uploads for the current file area. You do
NOT have to tag these files, I know which files need freeing.

                           Rename File

Lets you rename an existing file. Safe guards are in place to make
sure you can't do something wrong, like using the name of an
existing file.

                     Verify Files Still Exist

This one does not require that you TAG files. It simply CHECKS and
reports on any MISSING files.

                      Change Archive Format

This allows you to change the TYPE of archive from one format to
another.

                       View Archive Content

If the TAGGED file(s) are in archive format, selecting this option
will give you a list of the files INSIDE the archive(s).

The display screen looks something like this:

╔═══════════════════════════════ HELP.UC2 ════════════════════════════╗
║┌──────────────────────────────────────────────────────────────────┐ ║
║│This is a test.                                                    ║
║│                                                                  ▓ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                   ║
║└▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░┘ ║
║                                                                     ║
║                        Ok ▄              Cancel ▄                   ║
║                        ▀▀▀▀              ▀▀▀▀▀▀▀▀                   ║
╚═════════════════════════════════════════════════════════════════════╝


Use the scroll bars to move the display up/dn or left/right.
Clicking on the CANCEL button to abort the batch process.

                       Add Archive Comment

This allows you to ADD ARCHIVE comments to the Tagged files.

ONLY ZIP and ARJ archives support archive comments and if the
archive format isn't one of those two, it will be skipped.

You MUST make a file called "COMMENT.FAM" and place  it  in your
OSIRIS= directory. This file contains the COMMENTS you want added
to the archive.

If I can't find COMMENT.FAM then I'll return you to the main
screen.

WARNING!!!! DO NOT ALTER COMMENT.FAM AFTER YOU HAVE STARTED SM.

The MAXIMUM size of the COMMENT.FAM file  is 2048  bytes, a limit
imposed by the archive programs. If the file size exceeds 2048
bytes, I'm not going to use it.

                    View Extended Description

If the TAGGED file(s) has an extended description, you can view
the extension with this option.

The screen looks something like this:

╔═══════════════════════════════ HELP.UC2 ════════════════════════════╗
║┌──────────────────────────────────────────────────────────────────┐ ║
║│This is a test.                                                    ║
║│                                                                  ▓ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                  ░ ║
║│                                                                   ║
║└▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░┘ ║
║                                                                     ║
║                        Ok ▄              Cancel ▄                   ║
║                        ▀▀▀▀              ▀▀▀▀▀▀▀▀                   ║
╚═════════════════════════════════════════════════════════════════════╝


Use the scroll bars to move the display up, down, left or right.
Click on CANCEL to abort the batchprocess.

                     Add Extended Description

Lets you ADD extended descriptions to TAGGED file(s). If the file
already HAS and extended description, it is replaced with the new
one.

                    Clear Extended Description

Clears the extended description, provided the TAGGED file(s) have
one.

The extended description is not physically moved from the DESC.BBS
file, but the file is no longer associated with it. There is an
option available to physically PACK Desc.Bbs to removed
descriptions that are no longer associated with files.

                      Remove Delete Records

Physically removes deleted records. I would suggest that you only
use this option after you have deleted several files.

                        Rebuild Files.Idx

If you loose your FILES.IDX or it becomes corrupt for some reason,
you can rebuild it with this option.

                          Adopt Orphans

This adopts ORPHAN files, those not listed in FILES.BBS, for the
current file area.

Since it is impossible for anyone to upload something and NOT have
it listed, you would only use this option when you copy files,
from DOS, to this file areas sub-directory.

When Adopting you two options, BATCH mode or SINGLE file.

SINGLE will ask if you want to adopt each individual file as it is
found. BATCH mode does not ask if you want an individual file
adopted, it just automatically adopts everything.

                         Find NEW Uploads

Selecting this option will take you to the NEXT area that contains
NEW uploads, those not freeded for downloading.

This option DOES start looking at the NEXT area. If you want it to
look at areas that are BEHIND you, e.g. you are in area 10 and
you want areas 2 - 9 searched, you must move to the FIRST file
area.

                    Synchronize Access Levels

Because the files themselves have access levels, generally the
same as the area access level, changing the AREAS access level
will not necessarily make files (if you lower the access level)
available. Nor will it keep people from downloading them if you
RAISE that areas access level.

This option adjusts all the files in the current area so the file
access level and the area access level is the same.

                      Synchronize File Sizes

Each file a record contains the SIZE of the file, to reduce disk
access during searches.

If you CHANGE the PHYSICAL size of the files, estimated transfer
times, the number of Kilobytes the caller is charged for download,
etc. will be wrong.

Selecting this option will synchronize the file size in the
FILES.BBS with the files TRUE file size.

                    Scan For DIS Descriptions

Adopted any FILE_ID.DIZ, DESC.DES, or DESC.SDI files contained
within the archive as the extended description. If the SHORT
description if EMPTY, the first line of the Extended description
will be used as the SHORT description.

                        Flag Files As FREE

Gives an easy way to toggle the FREE FILE flag on or off for every
file in the areas. Might be useful if you are using the DOWNLOAD
BILLING SYSTEM and you want to setup entire areas that are exempt
from the billing system.

                        Clear Tagged Files

UN-Tags ALL files. You can also use the - key.

                          Tag All Files

Tags all the files in the area. You can also use the + key.

                         Flag File as NEW

If you change a file and you want it to show up as a NEW upload,
use this option.

                     Adopt From Control File

See the section labeled "CD-ROM, Step By Step Guide" for an
explaination of this command.

(H73)
Recover takes your FILES.BBS and attempts to salvage as many file
records as it possibly can. And in the process, builds a NEW DLL
chain.

Should your files.bbs become corrupt or you get a DLL error (which
is generally, but not ALWAYS, caused by corrupt files.bbs), use
this option.

The process is painfully slow because it does several checks on
each record it reads. The other reason it's so slow is because it
doesn't use the DLL chain. It reads each record, start with the
first, until it reaches the last record.

First, ALL 'C string fields are tested to see if they are NULL
terminated. If it has pulled up a valid record, they will be.

One of the recover option is to IGNORE the fact that a file is
missing *IF* that file is on a CD-ROM.

If you only have ONE CD Drive but have multiple file systems and
you SWAP disks every once in a while, you will HAVE to use this
option. Otherwise, the verification process will fail because SM
cannot find the file.

If you told SM *NOT* to ignore missing files and all the string
fields tested OK, SM will attempt to verify the file.  If the file
exists in the directory defined for that file area, and it passes
the other tests, the record is assumed to be valid and it is kept.

If you told SM to SKIP this check for CD-ROM drives, the record
is assumed to be valid if it passes the other checks.

(H74)
If you want to PACK your extended file descriptions and remove
anything that isn't currently used, select this option.

I don't have much in the way of information to display, offset
addressing is pretty boring, so I'll just display a PLEASE WAIT,
WORKING screen.

(H75)
This takes an SPL/I database and removes deleted records and
balances the btree indices. You would only use this option after
you have deleted several records.

(H76)
Basically, imports records from a TEXT file into an SPL/I
database. The SPL/I documentation explains more about this option
and how/when to use it.

(H77)
This is the function you use to create the SPL/I database
definition file, data file, and index file. The SPL/I
documentation explains more about this option and how/when to use
it.
(H78)
This removes deleted records and balances the btree indices for
database retrieval databases.

SM will ask you for the NAME of the control file, the one that you
setup to define the database.

(H79)
Displays TODAYS callers, when they were on-line and how long they
were on-line.
(H80)
Displays YESTERDAYS callers, when they were on-line and how long
they were on-line.

(H81)
This gives you a list of the files that were download, when, and
by whom. This is quite similar to the download statistics command
in Osiris.

When you select this option, I'll ask you to enter a date.

If you select ALL, output will go to a DISK FILE.

(H82)
This gives you a list of the files that were upload, when, and by
whom. This is quite similar to the upload statistics command in
Osiris.

When you select this option, I'll ask You to enter a date.

If you select ALL, output will go to a DISK FILE.

(H83)
I don't know about you but, there have been times that I wanted to
know what a specific person has downloaded. Ok, so I'm nosy.

Of course, you could just list all the downloads to disk and then
search that, but to be honest about it, I'm to damn lazy for that.

This option asks you for the name of the person and it will
display only the files he or she has downloaded.

(H84)
This is pretty much like "Who Downloaded What" except it tracks
individual files and tells you WHO download the file and when.

(H85)
This uses a VGA Exploding Pie Chart to show connect rates.

(H86)
This uses a VGA Explodying Pie Chart to  show what TYPE of
graphics (ANSI, ASCII, or RIP) your callers are using.

(H87)
This is your TRADITIONAL BBS in-use time chart.

(H88)
This function will generate a list of all your message
areas and tell you exactly how many people have selected
each area.

Useful when it comes to determining if you should keep
an area.

(H89)
This takes the language file, in text format, and turns it into
LANG.DAT, compiled format.

I expect this file to be NAMED LANG.TXT and the finished product
will be LANG.DAT.

If you have MULTIPLE language databases, you'll have to play the
rename game to compile them.

(H90)
When you select SM/MISC/PROTOCOLS, you'll get a screen that looks
something like this:

╔═══════════════════════════════ Protocol.Bbs ══════════════════════════════╗
║                                                                           ║
║ Display Name                           Access Level 0                     ║
║                                                                           ║
║ Protocol                                                                  ║
║                                                                           ║
║ Slow Speed Percentage 0       High Speed Percentage  0                    ║
║                                                                           ║
║ Times Used  0                 [ ] Batch Protocol                          ║
║                                                                           ║
║ Send Cmd                                                                  ║
║                                                                           ║
║ Recv Cmd                                                                  ║
║                                                                           ║
║                  Send/Recv CMD Special Character Sequences                ║
║                                                                           ║
║          *B Place Connect Rate Here     *P Place Port Number Here.        ║
║          *L Place Uart Rate Here        *F Place File Name Here.          ║
║          *U Place Sendx.Ctl Name Here   *N Place Node Number Here.        ║
║          *T Place Path To Bidirectional UPload Directory Here.            ║
║                                                                           ║
║         Jump▄ First▄ Last▄ Add▄ Del▄ Next▄ Prior▄ Exit▄ Update▄           ║
║          ▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀  ▀▀▀  ▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀▀▀▀           ║
║                                Record 1 of 1                              ║
╚═══════════════════════════════════════════════════════════════════════════╝

To edit a field, click on the field using the LEFT mouse button.
Data entry field editing commands for this section are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, PGDN, PGUP, UP ARROW or DOWN ARROW.

Osiris is setup to use a control file called "protocol.bbs" to
define the protocol names, programs to use, and the
command line to send and receive files. I have included a
Protocol.bbs mapped to use my protocol drivers.

This allows, providing you have a suitable protocol driver,
up to 32722 protocols.
                         How It All Works

Osiris uses the protocol.bbs file by assigning a number to each
protocol. The position in the file is the protocols number.
For instances, if the first protocol defined is Zmodem and it
is in the default protocol.bbs file, then Zmodem would be
referenced as protocol number one (1).

I'll take care of formatting a display screen listing your
available protocols.

                           Display Name

The name of the protocol, the one shown to callers. Generally this
is not important to Osiris EXCEPT for you zmodem driver. The
Zmodem driver MUST have the display name: Zmodem

                             Protocol

This field contains the name of the actual protocol driver, e.g.
ZMODEM.EXE.

A file extension, .EXE or .COM, is optional. But, if the protocol
driver is NOT in a PATH directory you MUST include the full drive
and path as well as the name.


NOTE: If you are running MULTIPLE lines under OS/2, make sure you
set all the protocol drivers to READ ONLY.

E.g. C:\OSIRIS\AUXPRGS\ZMODEM.EXE

Had C:\OSIRIS\AUXPRGS been in the DOS Path, then I could have
simply used 'ZMODEM'.

                             Send Cmd

This field should contain the entire command line need to
send a file or group of files and you would use the special
embedded protocol characters, defined later on, to tell me
what to put where.

                             Recv Cmd

This field should contain the entire command line need to
receive a file or group of files and you would use the special
embedded protocol characters, defined later on, to tell me
what to put where.

         Slow Speed Percentage And High Speed Percentage

I'll use these fields for figuring transfer times and they should
contain the AVERAGE percentage, based on 100 percent, of
efficiency. Efficiency is how well the protocol performs at any
given baud rate with 100 percent being perfect.

No protocol drive can give you 100 percent performance but vFAST
is about as close as you can get. vFAST is so close that we figure
it at 100 percent but it is really something like 99.8.

The protocol.bbs file, included in the Osiris package, has already
been set-up with percentage rates. You can use those as a guide
when adding NEW protocols.

                            Times Used

Shows the number of times this protocol has been used for a file
transfer.

                        [ ] Batch Protocol

This field, set to Yes or No, tells me whether or not the
protocol can handle BATCH downloads.

                           Access Level

This is the access level you have to have to USE this protocol.
This is to accent the ANTI-PMS system. If you don't have access to
a specific protocol, I'm not going to bother to HIDE it.

                   Embedded Protocol Characters

You will need a method of passing the com port, baud rate, and the
name(s) of the file(s) to be sent or received. Therefore, 7
special two character sequences have been reserved.

*L : Locked Serial Rate
*P : Com Port
*U : Use File SEND control file (MUST BE LAST ITEM LISTED)
*P : Replaced with the SERIAL port number.
*T : Place full drive and path to the temporary upload directory
     for this node.
*B : I'll place the CONNECT speed here.
*F : means place the file name to SEND or RECEIVE here.
*D : Means place the name of the LOG file here.

If the protocol uses *F, it is assumed to be a NON-BATCH protocol.
All protocol drivers we've tested, to date, support a SEND control
file.

*U means place the names, including drive/path, of the files to
send in a control file and pass the name of the control file to
the protocol driver. I'll generate the name of the control file
and it'll be called SENDxx.CTL with xx being the NODE number the
caller is on.

The control file will be placed in the Osiris system directory and
the full drive, path, and name WILL be passed to the driver.

e.g. Assuming you are using my drivers then

-@*U

would translate to -@C:\OSIRIS\SEND1.CTL

Providing C:\OSIRIS was the Osiris system directory and the caller
was on NODE 1.

You MUST use the *U approach if you're going to allow your callers
to take full advantage of the file queue system. Otherwise they'll
be restricted to downloading only 1 file at a time. *L - SERIAL
LOCK RATE and is primarily for protocol drivers I didn't write but
need to have the serial lock rate passed to them.

                            Logging

Osiris requires all protocols, ours or third party, to report
files sent using the DSZ.LOG format.

Osiris uses this log when it SENDS files to determine which files
were and were not sent. Files that are UPLOADED are handled
differently and a LOG is not needed.

The name of the log file can be supply two ways, with an
environment variable or with a command line switch.

To support the command line approach, there is a variable
available in the protocol.bbs record, *D. *D means replace these
two characters with the name of the log file.

If you were on node 1 and the OSIRIS= directory is C:\XLT, *D
would be replaced with C:\XLT\DSZ1.LOG

If you were on node 2, C:\XLT\DSZ2.LOG

The name of the log file is also supplied by the environment
variable DSZLOG=

You do *NOT*  define this environment variable!

Osiris will define it for you prior to a file transfer and then
remove it AFTER the transfer has been completed.

After a download, the lines in the DSZx.LOG that reference  files
that was actually sent, are appended to the XLTx.LOG and the
DSZx.LOG is deleted.

Any line in the DSZx.LOG that begins with E, S, or L is skipped.

E=Error. Some type of error occured and the file was not sent.

S=Skipped. Simply means the file was SKIPPED. Generally, the
receiver already had it and the caller just forgot.

L=Lost Carrier. Carrier was lost before this file was sent.

This should give  you considerable flexiblity when it comes to
selecting protocol drivers. If you don't like our Zmodem and want
to switch to DSZ, the only thing you'll lose is the name of the
person doing the downloading.

To avoid confusion, I should point out that you do NOT have to do
anything when using *OUR* protocol drivers. They are geared to
work with Osiris and the DSZx.LOG automatically.

                     Bi-directional Protocols

Osiris does have internal support for bi-directional or full
duplex protocols such as Bimodem and HS/Link.

To set-up a protocol as bi-directional, simply include the *T
switch with the appropriate protocol command line argument that
indicates where the upload directory is located.

E.g., HS/Link would use -U*T

If node 1, I would replace that with

-UC:\OSIRIS\UPL1.TMP

When the caller selects the files he wants to download, he may
have HS/Link or Bimodem send the files he wants to upload.

Bi-directional transfers CAN be an asset if you have callers
willing to upload files and they are using 2400 baud modems.

                           Restrictions

Be forewarned, bi-directional transfers are VERY CPU intensive.
Your computer may be able to handle bi-directional transfers at
2400 baud but it may not be able to handle them under v32, v32bis,
or vfast connects.

Bi-directional transfers at speeds higher than 2400 baud RARELY
work under Windows, Desqview, or when Network software is in
memory unless you have an intelligent serial card.

Bi-directional transfers at speeds higher than 2400 baud generally
requires a 16550 highspeed uart.

Bi-directional transfers will not work with USRobotics 14.4, Hayes
9600v series, TeleBit PEP, CompuCom CSP, and several other
highspeed modems.

You will get credit for uploading files, but ONLY the Kilobyte
credit. Since I cannot determine the exact amount of time that was
spent uploading, you will not get TIME BACK credit.

(H91)
This is the main configuration for the CALL BACK VERIFICATION
system. You must configure one of these for EACH node.

To edit a field, click on the field using the LEFT mouse button.
Data entry field editing commands for this section are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, PGDN, PGUP, UP ARROW or DOWN ARROW.

                        Modem Ready String

This field contains commands to READY your modem for dialing.
It should start with AT and would contain something like this:
ATH0M1S7=45

Almost ALL modem ready strings would contain S7=XX with XX
being the number of seconds to wait for carrier to be
established when calling out.

                         Dial Out String

This contains the modem commands that actual DIAL your modem and
generally contain one of two combinations:

ATDT or ATDP

                         Time To Connect

This tells me how long to wait for carrier to be established when
calling out. This should ALWAYS contain the same value as the S7
register.
                           Access Level

This is the access level to assign the caller when verification as
been successful.
                          Dial Attempts

This is the NUMBER of times, 1 - 99, I will try to call back. I
suggest that you keep this low, 3 or 4. If I can't connect within
3 or 4 tries, something is wrong.

(H92)
This section allows you to REDEFINE the Serial port IRQ and BASE
addresses. You might use this section if you have a NON-STANDARD
serial port.

If you don't know what I'm talking about, stay out of this
section.

(H93)
This is used to SWITCH SM to a DIFFERENT file system,
one you defined using the SM/Boards/Filedef.bbs option.

You MUST use this option to work on alternate file systems.

(H94)
This is where you POST new System bulletins. You'll be asked to
supply a SUBJECT for the bulletin and then we'll place you in your
TEXT editor.

Your TEXT editor should be set to for a RIGHT margin of no more
than 78 characters, 66 is the preferred setting.

(H95)
From here you can VIEW and optionally DELETE system bulletins.

To view a bulletin, highlight it with the mouse (click on it) and
then click on the VIEW button.

To delete a bulletin, highlight it with the mouse  and click on
the DELETE button.


(H96)
                            SM/E-MAIL

You have FOUR options available to you: Mailbox, Threaded Reader,
Read Specific, and Moderator.

                             Mailbox

This lists all your private mail.

There will be a short delay when you first enter the Mailbox. SM
is scanning and building the display tables.

All the buttons on this page are pretty plain except for TOGGLE.
This toggles the display between your PERSONAL e-mail and
EVERYBODIES e-mail.

You'll not be able to SEE any replies or new message you may post
while in the Mailbox until you exit and re-enter. They are there
and available to the person or persons they are addressed "TO:"
but they're just not in the display tables SM built when you
entered the Mailbox.

                        Reading a Message

To read a message, click on it. When reading a message, you have
the following HOTKEY options:

[R]eply
[K]ill
Up Arrow
Dn Arrow
PgUp
PgDn
Home
End

You'll also notice an upside down triangle in the upper right
hand corner of the screen. If you CLICK on the triangle, a menu
will drop down listing several options: Print, Save, Forward,
Edit, and Mark Read. Most of these are pretty straight forward.

Print sends the current message to your printer.

Save writes the current message to a text file. You specify the
name of the text file.

Mark Read flags the current message as RECEIVED. No personal
message to YOU will be marked RECEIVED until you use this option.

                         Threaded Reader

SM will take the first conference area you have selected and scan
for new/unread messages and present them to you in THREADED
format. Threaded format means that only one subject is listed per
thread.

You MUST use the BBS to to select and deselect message areas. SM
and Osiris use the same files and tracking method. Meaning Osiris
knows which messages you've read while in SM and SM knows which
messages you read while using Osiris.

The NEXT button will take you to the NEXT area you have selected
to read that has NEW messages. Areas that have NO new messages
will be skipped.

The MARK button works pretty much the same as the NEXT button only
SM marks ALL the messages in the current area as "READ" before it
moves the the next area.

Pickout the thread/topic you want to read and click on it.

While reading the following options are available:

[R]eply
[K]ill
Up Arrow
Dn Arrow
PgUp
PgDn
Home
End
Right Arrow (Next message in thread)
Left Arrow (Previous message in thread)

You'll also notice an upside down triangle in the upper right
hand corner of the screen. If you CLICK on the triangle, a menu
will drop down listing several options: Print, Save, Forward,
Edit, and Mark Read. Most of these are pretty straight forward.

Only PRINT, SAVE, and EDIT will work when you are in the threaded
reader.

Because of all the enbedded control lines in a message that make
it very area specific, forward is not allowed. If you have a
message you want someone else to see, SAVE it to a text file (this
strips all control lines) and then QUOTE that text file in a
message.
                          Read Specific

When you select this option, SM will ask you for a STARTING area
number. Once you have entered that, SM will display the next 100,
including the starting area, message areas. Select which one you
want to read.

Unlink the threaded reader, read specific shows you EVERY SINGLE
message in the area, even if it you have or have not read it.

                  Posting/Replying To A Message

When you post or reply to a message, you'll notice a button
labeled "Address.bok".

Address.bok is a text file listing, one per line, the name of
someone you talk to on a regular bases. The name can be the name
of someone on your BBS or it can be an internet name.

If you click on the Address.bok button, SM will list the contents
of Address.bok and you can select the TO: field from here.


When you post or reply to a message in the Mailbox, Threaded
Reader, or Read Specific you'll get something that looks like
this:

[ ] Add Tagline          OK Button
[ ] Add Signature
[ ] File Attach          Cancel Button

If you click on the CANCEL button, your message is NOT saved.

                             Tag Line

A TAGLINE is a single line witticism that you can have appended to
the end of each message.

To create taglines, make a file in your OSIRIS= directory called
Tagline.ctl. This file can contain an unlimited number of lines
but, each line cannot be any longer than 78 characters.

If you select the tagline option, SM will pull a tagline from this
file and insert it at the end of your message.

SM will CYCLE the taglines starting with the first one and when it
reaches the end of the file, it'll start over at the TOP.

                         Signature Files

A signature file is a simple text file that contains your
signature, the way you want to sign the message.

This generally contains your real name, phone number, fidonet
address, internet address, fax number, etc.

When you enter a message and click on the Signature option, SM
will scan the OSIRIS= directory looking for any file with a .SIG
extension and present you with a file list. Just select the one
you want to use and SM will append it to the end of the message.

You may, if you like, use BOTH taglines and signature files in a
single message.

                           Attach File

The attach file option works differently depending on where you
are at.


If this option is selected and you are in the MAILBOX, SM will
give you a list of all the files in the ATTACH.BBS subdirectory.
Pick the file you want to attach to the message.

Once the message has been received and the file has been
downloaded, Osiris will delete the file.

If this option is selected and you are in the THREADED reader or
READ SPECIFIC, SM will give you a list of all the files in the
GLOBAL.BBS subdirectory. Pick the file you want attached to the
message.

The file attach in this area will *NOT* be deleted after a
download and ANYBODY that has access to the message area has
access to the file attach.

File attaches in echomail or newsgroup areas are pointless. File
attaches are NOT sent out when you export messages.

                       Moderator

This function shows you the messages on HOLD and asks you to approve
or reject each message.

If you reject a message, it is sent back to the person that posted
the message and you are asked to select a reason the message was
rejected.
(H97)
Osiris has an ANSI <Esc> (ASCII 27) filter on the File area Type
command, the archive Contents Command and on all Read Message
displays.

This should prevent someone from uploading a file that contains
ANSI sequences that could reprogram your keyboard to format your
hard drive or to do just about anything else they wished.

(H98)
The first thing you'll need to create, if it doesn't already
exist, is a file called ACCESSx.BBS with x being the node number.
For node 1, you would use the filename ACCESS1.BBS, node 2 would
be ACCESS2.BBS and so forth and so on.

ACCESSx.BBS a text file, located in the Osiris directory,
containing information on access levels and system privileges
associated with each access level.

This is important, you MUST have an access level defined before
you can use it!

ACCESSx.BBS contains EIGHT fields per line, unlimited number of
lines.

Each line contains: Access Level, time limit per day, time Limit
per call, download limit per day, byte give back ratio, time give
back ratio, starting time in minutes, and ending time in minutes.

NOTE: If a Weekly time frame is used, the per day limits are per
week limits.

E.g.

5 120 60 2000 1 1 0 1440

Meaning access Level 5, 120 minutes per day, 60 minutes per call
with a 2000 kilobyte download limit, 1 to 1 give back on kilobytes
uploaded, 1 to 1 give back on time spent uploading, and finally
this access level is available between 00:00 and 24:00 or
midnight.

Example:

32 160 600 7000 1 1 0 1115
32 60 600 7000 1 1 1115 1440

The first definition gives the caller with access level 32 160
minutes PER call between the hours of 00:00 and 18:35 (or 6.35
PM). The second definition gives callers with access level 32 60
minutes per day between the hours of 18:35 and 24:00 (midnight).

The way you figure the MINUTES is fairly easy. Take the HOUR (24
hour format) and multiple it by 60 and add the minutes.

Take 18:35 as the example:

18 * 60 = 1080
1080 + 35 = 1115

If you didn't want to use of this, use the starting time of 0 and
the ending time of 1440

E.g.

32 60 600 7000 1 1 0 1440

The purpose? Lets you lower per call and download limits during
PEAK hours and RAISE per call and download limits during OFF
hours.

(H99)
Unlike other BBS application, Osiris has no FIXED command
structure. Instead, Osiris uses COMMAND records, each with 26
slots that hold commands such as show user list, read messages,
download a file, play a game, show this text file, use this
database, etc.

If it helps to understand exactly what a command record is, think
of each command record as a traditional BBS subsystem like your
Main Menu or your message system.

The installation program installed THREE command records and they
give you a BASIC BBS with commands that are found on most BBS
system. You can have up to 32736 command records each with 26
commands. You can nest command records as deep as you want but I
would suggest that you not go more than three levels deep.

When you select the SM/Command/Osiris.Bbs option you'll get a screen
that looks something like this:

╔════════════════════════════════ osiris.bbs ═════════════════════════════╗
║                                                                         ║
║                                                                        ║
║  Record Name                           Record Number  0               ▓ ║
║                                                                       ░ ║
║  Menu Path                                                            ░ ║
║                                                                       ░ ║
║  Menu Name                  Require Rip  No                           ░ ║
║                                                                       ░ ║
║                                                                       ░ ║
║  Display File Area Info  No        Display Msg Area Info  No          ░ ║
║                                                                       ░ ║
║  Menu Sound File                                                      ░ ║
║                                                                       ░ ║
║                                                                       ░ ║
║  Command                             Hotkey        Access ▄           ░ ║
║                                                    ▀▀▀▀▀▀▀▀           ░ ║
║                                                                       ░ ║
║  Command                             Hotkey        Access ▄            ║
║                                                                         ║
║             First▄ Last▄ Add▄ Del▄ Next▄ Prior▄ Exit▄ Update▄           ║
║              ▀▀▀▀▀  ▀▀▀▀  ▀▀▀  ▀▀▀  ▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀▀▀▀           ║
║                   Click on BLUE field to edit or define.                ║
║                                                                         ║
╚═════════════════════════════════════════════════════════════════════════╝

Data entry field editing and movement commands for this section
are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, UP/DN arrow keys, the SCROLL bar at the BOTTOM of
the screen, PGDN and PGUP.

Each command record has a field labeled "Record Name".

This should CLEARLY explain what the command record is for. When
the callers help level set to SHORT or NO menus, the record name
is displayed to give the caller some idea as to WHERE he or she is
located.

Typical records names might be "Main Menu", "File Area", "Message
Area", "Statistics", or "Games".

The next field on a command record is labeled "Menu Path".  This
is the path to a subdirectory that holds ALL the display files,
menus, SPL/I, and special control files. Special control files
such as those needed by the database retrievel system, the
document retrieval system, and the classified ad system (to name a
few).

Quite often sysops FORGET this and they will not move a new menu
or display file to the proper directory and they can't figure out
WHY it isn't displayed.

The next field on a command record is labeled "Menu Name". This
field should contain the name of the MENU file, minus file
extension, and it will be displayed to the caller when their help
level is set to FULL.

Again, the name should NOT contain any type of file extension.
Osiris will ADD the file extension based on the CALLERS graphic
settings. See the section labeled "Creating Menus" to learn more
about making and NAMING menu files.

The next field is labeled "Require Rip". If this field is set to
"YES", Osiris will NOT allow the caller to select this command
record UNLESS, he or she is using RIP graphics.

The fields "Display File Area Info" and "Display Msg Area Info"
tell Osiris WHEN/IF information such as area name, area number,
file subsystem name, should be displayed. You can toggle one or
the other to YES but never toggle BOTH of them to yes.

The next field is labeled "Menu Sound File". Three guesses what
this field does :) Just enter the name of the sound file you want
played when this command is selected. Place all .WAV sound files
in your ICONS directory.

                         Adding a Command

This is where you PLUG-IN the commands, define the hotkeys for
those commands, and setup access information.

To define a command, click on the BLUE field following the text
"Command".

A small menu will open listing several command cateogires such as;
File Area Commands, Msg Area Commands, General Commands, SPL/I
Command File, Display File,  External Program, Statistics, Chain
Command, and Rip Display File.

The menu will look something like this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌──────────── Select Category ────────────┐ ║
║ │File Area Commands                        ║
║ │Msg Area Commands                        ▓ ║
║ │General Commands                         ░ ║
║ │SPL/I Command File                       ░ ║
║ │Display File                             ░ ║
║ │External Program                         ░ ║
║ │Chain Command                            ░ ║
║ │Statistics                                ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║       Ok ▄      Cancel ▄     Delete ▄       ║
║       ▀▀▀▀      ▀▀▀▀▀▀▀▀     ▀▀▀▀▀▀▀▀       ║
╚═════════════════════════════════════════════╝

To select a category, click on the one you want. It will
be HIGHLIGHTED then click on OK. Click on CANCEL to exit
without selecting anything. Clicking on DELETE will CLEAR
the current definition.

If you select File Area Commands, Msg Area Commands, General
Commands, or Statistics another menu will open listing the
commands available under that category.

The screen display looks and functions the same as the one listed
above.

SPL/I, an Osiris programming language command file, has to be in
the directory defined in the "Menu Path" field.

Display File is an ASCII based text file. If the caller is in RIP
mode, Osiris will use the full screen text VIEWER (has scroll
bars and ICONS) to display the file. The Display file must be in
the directory defined in the "Menu Path" field.

Rip Display File is like the "Display File" but this one is
specifically for RIP screens ONLY. If the caller does NOT support
RIP graphics, they cannot select this slot.

Chain Command, this is how the caller moves from Command record to
Command Record. When you select this command, a menu will open
listing all the command records, select the one you want to CHAIN
to. This is a VERY powerful command and there is a HELP section
devoted exclusively to Chaining. This section is listed as
"Building Roads Between Command Records"

External Program . . .. The program can be a batch, com, or
exe file and can be located anywhere. Well, DOS has to be able to
find it so it will either have to be in the OSIRIS directory or in
a PATH directory.

I will write DOOR.SYS, DORINFOx.DEF, USERx.QBS, and OUTx.QBS in
the OSIRIS directory, in case your external application needs one
of them.

If the application does, then you'll want to execute a BATCH file
that copies the file to the correct directory and THEN calls the
application instead of trying to call the application directly.

I will also passes several command line switches. Whether or not
you use them is up to you and the program you're calling.

The switches are; Connect Rate, Serial Port, Node Number, UART
Rate, Time Left In Minutes, and finally a 0 or 1 with 1 meaning
LOCAL mode. If you were to process this information with DOS batch
variables, it would be:

%1 = Connect Rate, %2 = Serial Port, %3 = Node Number, %4 = Uart
Rate, %5 = Time left in minutes, and %6 contains 0 or 1.

Keep this in mind if you are a programmer. USERx.QBS is your BBS
user record. ANY and ALL modifications to this file will be
RETAINED.

After you select the command, SM will ask you to PRESS the HOTKEY
you want to activate this command. SM will NOT allow you to have
DUPLICATE hotkeys and if you select one already IN-USE, SM will
BEEP at you and make you do it again.

After selecting the HOTKEY, the ACCESS screen will open and this
screen looks something like this:

╔═══════════════════════════════════════════════════════════════════════════╗
║                            () Greater Than or Equal To                   ║
║                            ( ) Less Than or Equal To                      ║
║ Access Level  0            ( ) Equal To                                   ║
║                            ( ) Less Than                                  ║
║                            ( ) Greater Than                               ║
║                                                                           ║
║ Active On       Node 0     Starting Time  00:00    Ending Time 00:00      ║
║                                                                           ║
║ Mon [X]         Sound File                       Cost 0                   ║
║ Tue [X]                                                                   ║
║ Wed [X]                            SPL/I Flags                            ║
║ Thu [X]                                                                   ║
║ Fri [X]     1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16 ║
║ Sat [X]    [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]║
║ Sun [X]                                                                   ║
║                                                                           ║
║              Ok ▄                                  Cancel ▄               ║
║              ▀▀▀▀                                  ▀▀▀▀▀▀▀▀               ║
║                                                                           ║
╚═══════════════════════════════════════════════════════════════════════════╝

From here you set the access level, compare method, time of day, days
of the week, command key flags (if any), which node you have to
be on to use the command (0 = ANY NODE), cost (if any) that Osiris
will subtract from your matrix credit, etc.

Any time you want to CHANGE any of the ACCESS information, click
on the ACCESS button.

To Delete or Remove any command, click on the BLUE field following
the label "Command" and when the CATEGORY menu opens, click on the
DELETE button.

When you are VIEWING a command record, you may notice that some
of the COMMAND boxes have text that includes items enclosed in
brackets, ( ).

             (DBS) : Stands For Database System
             (RIP) : Stands For Rip Display File
             (SPL) : Stands For SPL Command File
             (EXT) : Stands For EXTERNAL Program
             (DRS) : Stands For Document Retrieval System
             (CAS) : Stands For Classified Ad System
             (C)   : Stands For CHAIN Command

Reason: Sometimes a NAME like BOX.CTL doesn't tell you WHAT it
goes to. But, BOX.CTL (DRS) tells you that this is a CONTROL
file for a Document Retrieval System.

(H100)
When you are VIEWING a command record, you may notice that some
of the COMMAND boxes have text that includes items inclosed in
brackets, ( ).

             (DBS) : Stands For Database System
             (RIP) : Stands For Rip Display File
             (SPL) : Stands For SPL Command File
             (EXT) : Stands For EXTERNAL Program
             (DRS) : Stands For Document Retrieval System
             (CAS) : Stands For Classified Ad Control File
             (C)   : Stands For CHAIN Command
             (CDL) : Stands For Custom Download Control File
             (SEP) : Stands For Special Post Control File

Reason: Sometimes a NAME like BOX.CTL doesn't tell you WHAT it
goes to. But, BOX.CTL (DRS) tells you that this is a CONTROL
file for a Document Retrieval System.

(H101)
Items listed under this category have in something to do with
your file system. The only exception being Document Retrieval.

We needed an OPEN object and there was one in this section so
we used it rather than create a whole new object category.

(H102)
A list of available file areas, those you have access to, will be
displayed. You can enter the number of the area you want or press
<Enter> to abort the area change.

NOTE: Under PrimeStar, this is handled in a WINDOW and you just point
      and shoot. The Window will close and the main display menu does
      not have to be redrawn.

(H103)
Displays the files available for downloading in the current File
Area along with file size, descriptions, transfer time, and
extended description (Yes/No).

I will list the files in REVERSE order, NEWER files first.

Under PrimeStar, you'll have a list that you can scroll up
and down.

You have a SELECTOR bar that HIGHLIGHTS the current file and a menu
bar with Download, View, Tag, Finished, and Queue buttons.

To move the selector bar, click on the file you want highlighted.

To Tag a file for downloading, move the selector bar and click on TAG.

You can move the selector bar AND tag a file at the same time by double
clicking on the file.

In the upper righthand corner of the screen, there is a question mark.
Clicking on this will pop-open a HELP screen.

If you click on the DOWNLOAD button and you do *NOT* have ANY files tagged
for downloading, the file currently highlighted will be SUGGESTED.

If the file you have highlighted is a TEXT, clicking on VIEW will use
the text viewer to display that file.

If the file you have highlighted is an ARCHIVE, clicking on VIEW will
bring up the archive manager. See section labeled ARCHIVE MANAGER for
further details.

Clicking on QUEUE will let you view, edit, clear files you have tagged
for downloading.

(H104)
ANSI Mode Only, PrimeStar handles this differently.

The file list also allow a LIST mask. You can enter part of the
file name and ONLY those files matching will be shown. This is a
SLIDE match and wildcard characters, * or ?, will not work.

                        e.g. BA

List only files starting with 'BA'

This can be VERY helpful when it comes to listing a SPECIFIC file
without having to go through ALL the files in that area to get to
it.

(H105)
ANSI Mode Only, PrimeStar handles this differently.

This allows you to TAG files, for downloading, while you are doing
a file list.

TAG asks for the name of the file. You can enter the file's name,
part of the name and the rest using wildcard characters, the
number assigned to the file, or if you support RIP you can CLICK
on the file.

If you enter a file name, without wildcards, you can select any
file in any area, as long as you have access to the file. The file
does NOT have to be in the current area.

If the file name contains wild card characters, ? or *, any file
matching the pattern that is in the CURRENT area will be tagged.

Each file shown during a file list is given a file number. The
file number is displayed BEFORE the file name.

If you use a file number, you can only tag files CURRENTLY visible
on the screen. Files in other areas or files in the current area
that are not currently displayed on the screen cannot be tagged
with a file number.

(H106)
ANSI Mode Only, PrimeStar handles this differently.

View lets you list the contents of an archive. After displaying
the list, I'll ask if you want the file tagged for downloading.
And like TAG, you can enter the archive's name, the file number
associated with it.

(H107)
ANSI Mode Only, PrimeStar handles this differently.

This is functionally the same as the file INFO command. And like
TAG or VIEW, you can enter the filename, the file number, or,
click on the file.

(H108)
The File Queue system lets you edit the files you have tagged for
downloading.

You can LIST files, REMOVE individual files, CLEAR ALL files, and
finally you can HOLD files.

(H109)
When you HOLD a file, it is EXCLUDED when you go to actual
DOWNLOAD. The file REMAINS in the file queue AFTER the download
and you can FREE it at any time and download it.
(H110)
This lets you to kill a specific file, PROVIDING you were the one
that uploaded it.

I suggest that you give ALL your callers access to this command.
It is very helpful when it comes to keeping OLD versions of the
same program off your system.

It is SAFE because only the person that ORIGINALLY uploaded the
file can delete it. And of course anyone with an access level
equal to or greater than the access required to KILL any file,
defined in NODEx.BBS.

(H111)
The functions view text, view archive, extract archive, and view
file inside an archive are INTEGRATED into:

New Upload Search
File List
Text Search
Sysop View New Upload

View Archive, Type File, and Extract file are handled by clicking
on the VIEW button (PrimeStar) or pressing V in ANSI mode.

If the file currently HIGHLIGHTED by the selector bar is an
archive, the archive manager will pop-up listing the contents of
the archive and you can view text files inside the archive,
extract single files from the archive, or tag the entire archive.

If the file is NOT an archive, you will view it using the TEXT
viewer.

You will need the following archive programs:

PAK.EXE, ARJ.EXE, PKUNZIP.EXE, PKZIP.EXE, LHARC.EXE, PKXARC.EXE,
PKARC.EXE, SQZ.EXE, RAR.EXE and UC.EXE

These programs should be in a PATH directory (recommended) or in the
Osiris directory.

(H112)
Lets you enter up to 8 KEY words with AND, OR, or NOT designators.
I will display the area and file name of matching files.

The file search command also supports a LESS than days option.

Example:  harddrive&seagate!conner<60

Means, find any file that has been on the system less than 60 days
that contains the key words harddrive and seagate but not the word
conner.

Notice "on the system less". This is based on the TIME the file
first appeared on the BBS and not the file's creation date.

The search will allow you to TAG any MATCHING files for
downloading.

The search does NOT stop with the first matching file, but it'll
continue to search ALL available areas.

You have a SELECTOR bar that HIGHLIGHTS the current file and a menu
bar with Download, View, Tag, Finished, and Queue buttons.

To move the selector bar, click on the file you want highlighted.

To Tag a file for downloading, move the selector bar and click on TAG.

You can move the selector bar AND tag a file at the same time by double
clicking on the file.

In the upper righthand corner of the screen, there is a question mark.
Clicking on this will pop-open a HELP screen.

If you click on the DOWNLOAD button and you do *NOT* have ANY files tagged
for downloading, the file currently highlighted will be SUGGESTED.

If the file you have highlighted is a TEXT, clicking on VIEW will use
the text viewer to display that file.

If the file you have highlighted is an ARCHIVE, clicking on VIEW will
bring up the archive manager. See section labeled ARCHIVE MANAGER for
further details.

Clicking on QUEUE will let you view, edit, clear files you have tagged
for downloading.


(H113)
Lets the caller pull up information on any file. Information such
as name, size, file create date, upload date, who uploaded it,
description or extended description, last date downloaded, etc.

(H114)
Lets you send a file to the system. The first question is the name
of the file you are about to upload.

I simply will NOT accept any COM, EXE, BAT, or SYS files as valid
uploads.

Once, years ago, it was safe to use these files. However, it is
one of the many methods used to distribute viruses because it is
difficult to scan the files inside the archive. And it is NOT safe
to allow them to auto-extract.

If is possible to have an infected file inside an archive AUTO-RUN
when extracted but ONLY if it is a SELF-EXTRACTING archive.

If you have engaged duplicate upload checking, a quick search will
be made, based on the search TYPE you defined in NODEx.BBS, to see
if that file already exists. If not, I'll ask you if the file
should be password protected.

You CANNOT set a file to KILL after downloading while on-line. You
have to use SM if you want to flag the file as AUTO-DELETE.

You must enter a short, 80 characters or less, description for
EACH file you are about to upload. I want to make sure there is
SOME type of description should carrier be lost.

There is NO limit, within reason, on the number of files you can
upload at any given time.

After you enter ALL the names and descriptions, a start line
consisting of :

RETURN to Start, A to Abort, C to Change Protocols.

The text and commands may vary because you define this in the
language file.

Change protocols can be very useful if there is a clash between
the protocol you are using (term program) and the one defined in
protocol.bbs.

If there is, you can change protocols without having to type in
the upload names and descriptions AGAIN.

Once you give me the "The Go Ahead", I will switch to TUPX.BBS
subdirectory with X being replace by the current node number. You
don't have to CREATE this directory, I will take care of that.

Because I switch directories, it is important that ALL protocol
drivers be in a PATH directory or you include the full drive and
PATH when you specify the name of the protocol driver.

After the upload, I will return to the directory I was originally
in before proceeding.

If the upload was not successful, you can try again without re-
entering file names or descriptions.

If the upload was successful:

If archive integrity checking is on and the file is an archive, I
will attempt to extract the file to the WORK directory for this
node. You do not have create the WORK directory, I will handle
that.

If the archive can be extracted successfully AND you have engaged
VIRUS scanning, I will call TBSCAN.EXE to scan the contents of the
WORK directory.

If the files are OK, you can optionally enter an EXTENDED, up to
99 lines, description for that file providing the file did NOT
contain FILE_ID.DIZ, DESC.DES, or DESC.SDI.

You will be given credit for that upload and providing you are
using this feature, I'll also give you back the amount of time
times specified by the give back ratio.

I will add the time to your BANK account instead of to the current
time on-line. This allows you to use that time when you NEED it
without fear of LOSING it.

I will give you the KILOBYTES times the give back ratio for each
file uploaded.

Like the TIME give back, I will add the KILOBYTE give back to your
BANK account. This allows you to use it when it is NEED.

I hope this method will cause callers to upload files quicker
because they don't need to HOLD back JUST in case they need
something later on.

(H115)
There are those that would like to think that there is some type
of standard for including file descriptions inside of archives.
However, the only OFFICIAL standards committee for
telecommunications has not adopted any type of standards.

There are several "WANT-TO-BE" formats such as FILE_ID.DIZ,
DESC.DES, and DESC.SD, to name a few. I checked some 2000 files
odd files and less than 3 percent contained one of those files.

However since it is possible, although highly unlikely, that one
of these MAY be adopted as a standard, I will LOOK for these files
during an archive integrity check.

If the file is present, I will automatically use the file as an
EXTENDED description.

You should be careful about automatically freeing files that MAY
contain one of these description files. Some BBS sysops like to
include one of these as an AD for their bbs.

(H116)
This displays information about your current file transfer
statistics: Number of bytes and files downloaded for the day and
total files and bytes downloaded.

(H117)
When you upload a file, providing the area isn't set to AUTO-FREE
UPLOADS, it is flagged as NOT ALLOWED TO DOWNLOAD.

You can FREE uploads in the current area by selecting this option.

Because of the way the HYPERSCAN system works, it requires the
files be in a SPECIFIC order. Why isn't important to you, but to
maintain this order you MUST free ALL new uploads in a SINGLE area
at the same time.

If there is a file you don't want made available, commercial
software, then FREE the files and THEN delete the file from the
system.

(H118)
Lets you LIST the NEW uploads, those that have NOT been freed for
downloading, in the CURRENT file area.

Under PrimeStar, you'll have a list that you can scroll up
and down.

You have a SELECTOR bar that HIGHLIGHTS the current file and a menu
bar with Download, View, Tag, Finished, and Queue buttons.

To move the selector bar, click on the file you want highlighted.

To Tag a file for downloading, move the selector bar and click on TAG.

You can move the selector bar AND tag a file at the same time by double
clicking on the file.

In the upper righthand corner of the screen, there is a question mark.
Clicking on this will pop-open a HELP screen.

If you click on the DOWNLOAD button and you do *NOT* have ANY files tagged
for downloading, the file currently highlighted will be SUGGESTED.

If the file you have highlighted is a TEXT, clicking on VIEW will use
the text viewer to display that file.

If the file you have highlighted is an ARCHIVE, clicking on VIEW will
bring up the archive manager. See section labeled ARCHIVE MANAGER for
further details.

Clicking on QUEUE will let you view, edit, clear files you have tagged
for downloading.

(H119)
Lets you reset your default protocol from the file area.

(H120)
Lets you receive file(s) from the system.

All Dos wild card characters, * and ?, are supported and expanded
to match files in the CURRENT file area.

If a PARTICULAR file was NOT downloaded successfully, for what
every reason, I will ask you if you want to KEEP that file in the
QUEUE.

(H121)
Osiris will automatically build and send one additional file,
FILExxx.DES, when you download.

This file contains the name and description of each file you have
selected. There is also a short header that lets you know WHERE
you obtained the files, when you downloaded them, and WHO to
contact if anything is wrong with the file.

(H122)
If you have access to FREE UPLOADS, you also have access to
DOWNLOAD the uploads BEFORE they have been freed.

This allows co-sysops (and sysops) to download the files remotely
and check them out before making them available to the general
PUBLIC.
(H123)
Following each download, I'll check the temporary upload directory
to see if you uploaded anything using a bi-directional protocol.

(H124)
If you are using a NON-BATCH protocol and have multiple files
tagged, there is NO problem.

I will simply CYCLE repeating the download until you have
downloaded ALL files. All the you have to do, press RETURN to
start each transfer.

(H125)
It can, at times, be beneficial to CHANGE the description of an
EXISTING file. Either it was not CLEAR or maybe contained a
misspelled word.

This function allows you, providing you were the one that UPLOADED
it, or your access level is equal to or greater than the GLOBAL
edit access level defined in NODEx.BBS, to change either the SHORT
description or the EXTENDED description.

I suggest that you allow callers to have access to this command.

(H126)
This allows you to RENAME a file. I'm not sure WHY I added this
feature but a few customers asked for it.

You can ONLY rename a file if: You were the one that uploaded it
or your access level is equal to or greater than the GLOBAL rename
access level defined in NODEx.BBS.

(H127)
The new upload search is based on the DATE of your LAST new
uploads search or the current date if this is the first time you
have called the system.

The last search date will be displayed and you do have the option
of changing it. At the end of the search, I'll ask you if it is OK
to log the search date, provided it isn't already set to the
current date.

This lets you forego having the date logged if you do not, for
whatever reason, have time to download the new files. You can say
"No" and the next time you do a new upload search, the same date
will be used.

You also have the option of TAGGING any NEW file for downloading.

Under PrimeStar, you'll have a list that you can scroll up
and down.

You have a SELECTOR bar that HIGHLIGHTS the current file and a menu
bar with Download, View, Tag, Finished, and Queue buttons.

To move the selector bar, click on the file you want highlighted.

To Tag a file for downloading, move the selector bar and click on TAG.

You can move the selector bar AND tag a file at the same time by double
clicking on the file.

In the upper righthand corner of the screen, there is a question mark.
Clicking on this will pop-open a HELP screen.

If you click on the DOWNLOAD button and you do *NOT* have ANY files tagged
for downloading, the file currently highlighted will be SUGGESTED.

If the file you have highlighted is a TEXT, clicking on VIEW will use
the text viewer to display that file.

If the file you have highlighted is an ARCHIVE, clicking on VIEW will
bring up the archive manager. See section labeled ARCHIVE MANAGER for
further details.

Clicking on QUEUE will let you view, edit, clear files you have tagged
for downloading.

(H128)
A dynamic file area is a special directory you can setup  off
the OSIRIS= directory to hold files for download. The  kicker
is, those files are not part of  the normal file system.

When you select the dynamic file command, you get a file list
of  the  CURRENT  files in that directory  along  with  their
sizes  and dates/time stamp. You can view them, tag them  for
downloaded, etc.

If  you copy a new file into the directory, it  automatically
shows up. If you delete a file from the directory, it  simply
disappears from the file list.

Since they are not indexed, they do not show up in new upload
search,  text  file  searches, and of  course  they  have  no
descriptions.

Normal  file areas are defined in SM/Boards/Filboard.bbs  but
dynamic file areas are defined in Osiris.bbs slots.

Create  a  directory under your OSIRIS=  directory  and  then
click on a slot in an Osiris.bbs record and define that  slot
as  a  DYNAMIC  File  Area and enter the  name  of  the  sub-
directory.  You  do  not  enter the  ENTIRE  name,  only  the
subdirectory name.

Example:

Assume OSIRIS= is C:\XLT

I create a subdirectory C:\XLT\SPECIAL

When  I  enter  the name of the  subdirectory,  I'd  type  in
SPECIAL. Osiris will add the C:\XLT part when it attempts  to
access the directory.

Obviously,  you would use something like this when  you  have
files  that  change on a daily or semi-daily  bases.

Another  use, BBSnet OUTGOING FTP. You would tell  BBSnet  to
put the FTPed files into a dynamic directory and the  callers
could download the files from there.

The  files are, of course, not deleted after  downloading  so
you can browse and if you find useful files move them to your
normal file areas.

(H129)
This lets you move files from one area to another while ON-LINE.

The following restrictions were placed on moving a file.

1. You cannot move a file FROM a CD ROM.
2. You cannot move a file TO a CD ROM.
3. You cannot move a file to an area that has NEW uploads that
   have not been FREED for downloading.
4. You can ONLY move a file if: You were the one that uploaded
   it, you are the sysop, or your access level is greater than
   or equal to the GLOBAL MOVE ACCESS level defined in NODExx.BBS.

With these restrictions, it is pretty safe to give callers access
to the move command.

There aren't a bunch of system messages associated with this
command, in fact there are only two. You can get a message telling
you that you can't move the file because you were not the one that
uploaded it or you'll get a message telling you the file was
successfully moved.

You don't actually HAVE to plug this command into a slot to access
it.

The FILE LIST, NEW UPLOAD, BOOLEAN SEARCH, and the SYSOP NEW
UPLOAD listboxes have a hidden MOVE command.

This HIDDEN MOVE command works ALMOST like the plug in move does
accept only the SYSOP and those with GLOBAL MOVE access can use
it.

In RIP mode, the UPPER LEFTHAND CORNER box, the one with the - in
it, is a hidden button. Click on it and you can move the file that
is highlighed by the selector bar.

In ANSI mode, the HOTKEY is M

If a "NORMAL" caller should happen to click on the hidden button
or press M in ANSI mode, nothing will happen.

(H130)
A CUSTOM upload command lets you redirect files that are about to
be uploaded to a specific file area.

One use that comes to mind; one of your users may have a
commerical application that he or she needs help with. You, being
an honest person, would help them then delete the program. But you
don't want to take a change on those files getting mixed up with
other files and accidently being FREED for downloading.

To setup a custom upload, pick out or define a new file area
,primary file system. I would suggest that you set the access
level to this file area so you are the only one that has access to
it.

Next, load SM and plug the CUSTOM UPLOAD command into a slot and
define the file area the files are to go into. You'll find the
CUSTOM UPLOAD command located under the "FILE AREA COMMANDS".

(H131)
To set-up a CUSTOM download, select the CUSTOM download option,
located in the OSIRIS.BBS section of SM. The command is listed
under the FILE AREA COMMANDS.

When you select this command, you'll be asked to provide the name
of the control file, you make this so it can be anything you want.
The control file should go in the MENU directory defined for the
command record you are going to use.

The contents of the control file is pretty straight forward. You
list the name of a file, one per line, unlimited lines.

The name of the file can be JUST the file name, in which case the
file MUST be in one of your file areas, or the name can contain
the full DRIVE, PATH, and file name.

If you use the full DRIVE, PATH, and FILE NAME the file does not
have to be listed in one of your file areas. In fact, Osiris will
assume that it isn't.

The ONLY restriction, you cannot use WILD CARD characters, * or ?,
in the file name.

The download will only send the files you have listed in this
control file. If the user has tagged other files for downloading,
they will be SAVED and RESTORED after the download.

A sample control file (one we use):

XLT303_A.UC2
XLT303_B.UC2
XLT303_C.UC2
XLT303_D.UC2
XLT303_E.UC2

We'll use (CDL) to identify a CUSTOM download control file when
viewing a command record.

(H132)
The functions listed on this menu deal in some way, sharp, or form
with conference message areas.
(H133)
Allows you to switch conference areas. Only the areas you have
selected will be displayed.

Please keep in mind that Osiris is CONFERENCE based. That means
simply ADDING new conference message areas will NOT affect your
area display and only areas SELECTED will be displayed. I suggest
you use a system bulletin to notify your callers about new areas.

(H134)
Allows you to enter a message. If you defined the area as a LOCAL
message board, then you can ONLY enter a message to someone on the
system or address the message to ALL. If you defined the area as
ECHO, you may address the message to anyone.

(H135)
This takes you to the conference area selection system where
you can add, remove, or view the areas you want to read.

You can select up to 8000 message areas to read.

(H136)
You can select one of two formats, QWK or BLUEWAVE.

The BLUEWAVE and QWK packer REQUIRES Pkzip for both messages
being downloaded and REPLIES being uploaded.

                   EXTENDED QWK Specifications

Because the QWK TO and SUBJ fields are way to short for Internet
E-mail, Private e-mail, or Internet newsgroups, we've added a
couple of extensions to the QWK specifications.

When you read a message you may notice one or more of the
following lines in the BODY of the message.

#TO  : support@hq.itc.com
#SUBJ: this is a test message
#REF : <952398483@itc.com>

The "#TO  :" line reflects WHO the message is going TO should you
REPLY to that message.

If you reply to the message, you must QUOTE the message and leave
those lines in the message. You must also remove any QUOTE symbols
your editor places in FRONT of those lines so the '#' character is
the FIRST thing on the line.

Example:

> #TO  : support@hq.itc.com
> #SUBJ: this is a test message
> #REF : <952398483@itc.com>

Remove the "> " part so that it reads:

#TO  : support@hq.itc.com
#SUBJ: this is a test message
#REF : <952398483@itc.com>

When POSTING a NEW message, you may enter the

#TO  : <Who it is to>
#SUBJ: <The original subject>

If you are sending e-mail, I.E. using the "e-mail" area, this is
NOT an option. You *MUST* enter these two fields.

                   Two OPTIONAL Control Fields

You may, if you wish, include #news: <Groups> or #fupt: <Groups>
posting to a newsgroup area.

#news: <Groups> gives you direct control over which USENET
newsgroups your message will be posted in.

When <Groups> contains multiple newsgroup names, each name is
separated by a comma and there are NO blank spaces.

Example:

#news: alt.bbs,alt.bbs.allsysop,comp.bbs.misc

This would force Osiris to ignore the area you are posting the
message to on the BBS and it would post to three different
newsgroups you defined here.

Btw, the name of the area on the BBS is *NOT* going to be the same
as the name of the newsgroup. The area name on the BBS might be
"BBS SYSOPS" but the newsgroup name might be
"alt.bbs.misc.western.missouri.poplar.sysops". If you want to
know, ask the sysop. You might also ask that he post a list of all
the USENET newsgroups so that you will have a list available to
you.

The BBS you are calling does *NOT* have to carry the newsgroups
you are posting to but if it doesn't, you need to include #fupt:
or ask that replies be sent to your e-mail address if no other
area on the BBS is appropriate for the type of message you are
posting.

Lets say the BBS you are calling only carries comp.bbs.misc and
you added the line "#news: alt.bbs,alt.bbs.allsysop,comp.bbs.misc"
to your message.

Adding "#fupt: comp.bbs.misc" to the message would cause any
replies to your post to be routed to "comp.bbs.misc" so that you
can read them.

Btw, fupt stands for FOLLOW UP TO.

As with the other special control sequences, #news: and #fupt:
must be the first and only thing on the line.

Example:

#news: alt.bbs,alt.bbs.allsysop,comp.bbs.misc
#fupt: comp.bbs.misc

                            LONG lines

Lets say you want to use the #news: line but the groups you want
to send it to will not fit on a single line. If that is the case,
you can use the APPEND control character, ~

Example:

#news: alt.bbs,alt.bbs.allsysop,~
alt.bbs.osiris

Notice ~ is the last thing on the first line. Osiris would append
the two lines together and the end results would be:

#news: alt.bbs,alt.bbs.allsysop,comp.bbs.misc

Anytime you want to append two lines together, just end the first
line with ~ and a carriage return, you get a carriage return when
you press the ENTER or RETURN key.

We've included a file called toreader.ext that contains pretty
much what you have just read. Move that file to your OSIRIS=
directory. When someone PACKS mail using QWK, this file will be
included in their bundle.

When they OPEN the QWK bundle, their reader will see a file called
NEWS.BBS which most will automatically display.

Not all readers will automatically display this file so we suggest
that you copy it to a file area and require a caller to download
and read it before you give them access to the QWK/BLUEWAVE
command.

(H137)
This command allows your callers to read NEW message using the
built-in threaded reader.

IMPORTANT NOTE: Always run ULINK.EXE after importing Newsgroups
or Fidonet Echomail.

A thread is a GROUP of one or more messages about a particular
subject.

When this command is selected, Osiris will start with the FIRST
area the caller has selected to read and scan for NEW messages.
The message area the caller WAS in before selecting this command is
preserved and restored when he or she exits the threaded reader.

If the area contains NEW messages, the caller will get a PICKLIST
display containing a LIST of all the DIFFERENT topics in the area.

Keep in mind that if there are 100 messages in the area but all
about the same thing, only ONE topic shows up in the list and that
is the FIRST unread message in the thread.

The PICKLIST display shows 10 threads at once and the caller can
pick which topic/thread they want to read.

The PICKLIST display offers the caller FIVE commands:

                               Mark
                        Post (New Message)
                            Next Area
                               Read
                               Exit

In ANSI mode, the caller can use their PgDn, PgUp, Up Arrow, Dn
Arrow, Home, and END keys to move the SELECTOR bar. Of course,
they must have their NUM LOCK turned on and they are told to make
sure it is.

In RIP mode, the caller can just CLICK on the TOPIC/THREAD to move
the SELECTOR bar. There are also 4 buttons located on the right
side of the screen graphically labeled with a SINGLE UP ARROW,
SINGLE DN ARROW, DOUBLE UP ARROWS, and DOUBLE DOWN ARROWS. These
buttons emulate PgUp, PgDn, Home, and End.

RIP mode also has a SCROLL BAR located on the right side of the
screen indicating the callers position relative to the FIRST and
LAST pages.

                         The READ Command

When reading a thread, each message is display and after the
message is displayed, the caller has the following commands:

                      Next Message In Thread
                    Previous Message In Thread
                              Reply
                     Download Current Message
                     Stop/Return To PICKLIST

                       The NEXT AREA Command

This will move the caller to the NEXT area they have selected that
contains NEW or unread messages. Areas that have NO new or unread
messages are skipped.

                         The MARK Command

This works almost like the "NEXT AREA" command except, and this is
a BIG except, it flags ALL the messages in the current area as
"READ" before moving to the NEXT area.

This is useful if the caller has been absent for a while and there
are simply TOO many message to even BEGIN to read.

It is also useful when you have finished with all the
topics/threads you find interesting and simply don't want the
remaining threads to show up the next time you use the reader.

The remaining two commands, EXIT and POST, are fairly straight
forward.

(H138)
This command allows your callers to list and read all the
messages, even those they have ALREADY read,  in the CURRENT area,
starting with the first available message.

Messages are listed by SUBJECT using the same basic PICKLIST
display the Threaded Reader uses. The PICKLIST display shows 10
messages at once and the caller can pick which message they want
to read.

The PICKLIST display offers the caller FIVE commands:

                              Delete
                        Post (New Message)
                               Read
                             Download
                               Exit

In ANSI mode, the caller can use their PgDn, PgUp, Up Arrow, Dn
Arrow, Home, and END keys to move the SELECTOR bar. Of course,
they must have their NUM LOCK turned on and they are told to make
sure it is.

In RIP mode, the caller can just CLICK on the TOPIC/THREAD to move
the SELECTOR bar. There are also 4 buttons located on the right
side of the screen graphically labeled with a SINGLE UP ARROW,
SINGLE DN ARROW, DOUBLE UP ARROWS, and DOUBLE DOWN ARROWS. These
buttons emulate PgUp, PgDn, Home, and End.

RIP mode also has a SCROLL BAR located on the right side of the
screen indicating the callers position relative to the FIRST and
LAST pages.
                        The Delete Command

The caller is only allowed to DELETE/KILL the message PROVIDED the
message is one that HE or SHE posted.

If the area is a UUCP area and the message has been exported,
Osiris will automatically issue a CANCEL command  instructing ALL
Internet systems to delete their copy of the message.

The remaining commands are pretty much the same as those found in
the threaded reader except for the READ command.

Instead of reading an entire thread, you are only reading the
CURRENT message. The option of moving back and forth between
threads is not available.

(H139)
Search allows you to search and read messages using 1 of 4 search
options in ANSI mode or 1 of 7 options in RIP mode.

1. Unread Msgs TO you.
2. All Msgs To You.
3. Msgs you've posted.
4. Msgs with File Attaches.

--- Available in RIP only ---

5. Msgs From a Specific person.
6. Msgs To a Specific person.
7. Topics.

The search is conducted on ALL areas selected starting with the
first area. If option 1, 2, or 3, the search checks for both
PRIMARY and ALIAS names.

(H140)
Lets you reset your message read pointers for all areas
or a specific area.
(H141)
The functions listed on this menu deal in some way, sharp, or form
with statistical information. All the statistic systems have very
nice built-in RIP counter parts.

If you are in RIP mode, we use two different WORKING displays. One
is a FUEL gauge and the arrow swings from left to right. The other
is a sliding percentage completed bar.
(H142)
This will display a list containing the names of the people that
called your system TODAY. The list contains the name of the
caller, where he called from, when he logged on, when he logged
off, and the total time spent on-line.

Callers that have the privacy switch turned on, no user list
display, will not be shown but will still be counted.

At the end of the list: the total number of calls, total minutes
of in-use time, and the percentage of utilization, based on 1440
minutes.

(H143)
Functions the same as "Todays Callers," but shows yesterdays
callers.
(H144)
Caller history shows a screen listing all the callers to your
system for the last xx days, if available. I will use a date bar
to divides each group of entries.

At the end of the list; the total number of calls, the total
number of minutes used, and the AVERAGE utilization.

(H145)
Uses the history log for the current node to compute the
SIX less used HOURS and displays them in less to most order. It
also shows the average in-use time for that hour.

This gives you a way to pick the BEST times to call the
system.

There is a small quirk that you may notice. It is possible, highly
probably, that you will see BUSY HOURS with more then 60 minutes.
Since I round each call up to the next highest minute, you may get
more than 60 minutes in a busy hour.

(H146)
This shows the SIX busiest hours when you should NOT attempt to call.

There is a small quirk that you may notice. It is possible, highly
probably, that you will see BUSY HOURS with more then 60 minutes.
Since I round each call up to the next highest minute, you may get
more than 60 minutes in a busy hour.

(H147)
There are two different charts displayed under this option. The
first is top 10 UPLOADERS to your system, based on the NUMBER OF
FILES uploaded. The second is top 10 UPLOADERS to your system,
based on KILO-BYTES uploaded.

Callers with zero uploads will NOT be allowed in the chart.

(H148)
This option displays two different charts. The first chart is base
on the NUMBER OF FILES downloaded. If you do not have enough
dnloaders to fill the 10 slots, the remaining slots will be empty.

The second chart is based on the number of KILO-BYTES down loaded.

(H149)
Lists the names of your ten most frequent callers. I will not
place anyone that has the privacy switch toggled ON in this chart.

(H150)
Lists the top ten people based on the number of messages they have
posted. I will not place anyone with the privacy switch turned ON
in this chart.
(H151)
This TRACKS the SPEED of your callers. In RIP mode, we use a very
nice Exploding PIE chart.

(H152)
This graph shows which protocols are popular and which are not. If
your callers aren't using a particular protocol, you may want to
replace it with one they will use.

In RIP mode, we use a very nice SCATTER chart.
(H153)
This is almost like the TODAYS CALLER display except you can enter
the DATE you want to look at. The available dates will be
displayed before you're asked to enter which date you want to look
at.
(H154)
This option allows you to track the times a specific individual
called the system.

The display shows the name, log-in date, log-in time, and the time
spent on-line for that call.

If you want to track yourself, simply press return. If you want to
track someone else, backspace to remove your name and type in the
name of the person you want to track.

I'll only list a person with the privacy switch for the sysop OR
that person.

I'll displayed all the dates on-line, the total number of
connects, and the total time spent on-line.

(H155)
You'll get a display showing the TOTAL calls, TOTAL in-use time,
the percentage of utilization, average callers per day, average
in-use timer per day, and the average percentage of utilizations
per day.

This can be useful when it comes to deciding IF you need to ADD
another line or maybe REMOVE an existing line.

(H156)
Unlike other BBS programs, Osiris doesn't log downloads to the
BBS' log. Instead I track them in a database and you can pull up a
list of the files downloaded on a specific date showing who
downloaded the files and exactly WHAT time downloaded took place.

I'll track the last 10,000 files downloaded.

It is quite safe to give callers access to this function because
unless you are the sysop, only YOUR downloads will be listed.

When you select this option, a range of dates will be displayed.
You can select which date you want or your can enter 00/00/00 for
ALL dates.

(H157)
Unlike other BBS programs, Osiris doesn't log uploads to the BBS'
log. Instead I track them in a database and you can pull up a list
of the files uploaded on a specific date showing who uploaded the
files and exactly WHAT time uploaded took place.

It is quite safe to give callers access to this function because
unless you are the sysop, only YOUR uploads will be listed.

When you select this option, a range of dates will be displayed.
You can select which date you want or your can enter 00/00/00 for
ALL dates.

This may be a bit redundant because the file record for each file
contains the same information, minus the exact time. However, this
system does provide an easy method of correlating ALL uploads.

(H158)
General Commands are command that do not fall under any SPECIFIC
catagory, like file or messages.

(H159)
Displays the DATE and TIME at your location.
(H160)
Gives you a graceful way of logging off the system with an
OPTIONAL message to the sysop.

It is ok to DROP CARRIER, it will not harm the software.

(H161)
This is a lot like the LOG OFF function except carrier is dropped
ASAP. No optional message to the sysop, no ARE YOU SURE question,
no BYEBYE display files . . . just a FAST CLICK and you're gone.

(H162)
Takes you to the on-line store subsystem for a little SHOPPING.
See section labeled "Online Store" for information about
the installation and setup of the online store.

(H163)
Displays who is on-line on each node and what their status is.
Those with the PRIVACY switch turned on will NOT show up in this
display.
(H164)
This lets you log-on and change someone's access level.

The first question is, "Who Do You Want To Upgrade?"
, enter that persons name.

If that person does NOT have a user record you'll get, "SKIPPING!
No such person on this system."

If that person does exist but is in-line, you'll get:

"Cannot Upgrade somebody that is CURRENTLY On-line!"

Otherwise you'll be asked, "To What Access Level ? xx", xx will be
the CURRENT access level. Backspace to delete that access level
and enter a NEW access level.

If you just wanted to CHECK a person's access level, press return
without changing it. I will make no attempts to update the record
unless you change the access level.

You should be VERY careful with this option. If someone else has
access to it, they can change YOUR access level.

(H165)
To delete a user remotely, use the CHANGE ACCESS command and set
the callers access level to 0. That person cannot get back on-line
and CAT will remove the record during normal maintenance.

(H166)
Allows you to browse through old system bulletins and read any of
them you may have forgotten about.

(H167)
Displays a LIST of the system users and where they are calling
from.

Those that have the PRIVACY switch turned on will be displayed as
PRIVATE and UNKNOWN for the city.

This display will NEVER be blank.

(H168)
The built-in multiline Chat system rivals most commerical stand
alone Chat systems. In fact, there is only one that I know of that
has more power and that is a commerical system called Zchat.

The built-in system features:

  Multiple Rooms  : You can define up to 32,732 different
                    ROOMS, each with a specific topic. ROOM
                    #1 is GENERAL CHAT and that is handled
                    automatically by Osiris.

                    When you issue a CHANGE command, we'll
                    list the number of occupants in each room
                    along with the name of the room. Listing
                    the number of occupants will save you from
                    logging into a ROOM that's empty.

  Lockout Feature : Lets you lockout people that bug you.

  Private Chat    : Lets you enter private chat with another
                    channel. You only see the messages from
                    that channel and your messages only goes
                    to that channel.

  Whisper         : Lets you say something privately to
                    someone without going into Private Chat.

  Who             : Displays who is in the room and what
                    channel they are on.

  Review          : Lets you browse the last 100 - 200 messages
                    you've received. This is ROOMED based and
                    is reset when you change rooms.

  Page            : Lets you page someone to CHAT.

Private and Whisper work in any ROOM. In other words, you don't
have to go to a special ROOM to hold a private conversation. You
can have 128 private conversations going on in the same room.

In ANSI mode, a short single line menu appears when you press a
key that doesn't activate a command. In RIP mode, the commands are
on buttons.

In ANSI mode, there is a CHAT help file, CHAT.HLP, and that file
should go in the OSIRIS directory.

You can say up to 20 lines at once and the full screen editor is
used to get your comments.

                   Setting Up Additional ROOMS

The CHAT system uses a subdirectory called CHAT.BBS located in
your OSIRIS directory. You don't have to create this directory,
Osiris will do it for you.

To add additional ROOMS, change into the CHAT.BBS directory and
create a new subdirectory.

Lets assume you are going to add a ROOM for WIN95.

We'll also assuming that you have Osiris installed in C:\XLT so
change into the C:\XLT\CHAT.BBS directory using the DOS command
"CD \XLT\CHAT.BBS".

Now create a subdirectory called WIN95 using the DOS command
"MKDIR WIN95".

Now change back to the OSIRIS directory and create a text file
called ROOMS.BBS.

Each line in ROOMS.BBS contains TWO fields separated by a SINGLE
blank space. This is very important, you must use ONE and ONLY ONE
blank space.

The first field is the name of the CHAT directory. Do *NOT* put
the FULL path, only the name of the directory. Osiris will build a
path to that directory.

In our example, that would be WIN95.

The second field would be the ROOM name, up to 40 characters. Lets
use the name "Discussion about WIN95"

The line in ROOMS.BBS would read:

WIN95 Discussion about WIN95

To add additional rooms, repeat the process.

Here is a sample ROOMS.BBS that has additional ROOMS defined:

WIN95 Discussion about WIN95
OS2 OS/2 WARP!
UNIX Unix for Tech Heads

This sample ROOMS.BBS expects to find 3 additional subdirectories
in the CHAT.BBS directory; WIN95, OS2, and UNIX.

If you have Osiris installed in C:\XLT then you'd need the
following 3 directories:

C:\XLT\CHAT.BBS\WIN95
C:\XLT\CHAT.BBS\OS2
C:\XLT\CHAT.BBS\UNIX


(H169)
Lets you EDIT or just view your user records settings.
(H170)
This command is for posting SMART(tm) system bulletins remotely.

I'll treat the bulletin as a msg, up till the time it is saved,
and use the Osiris message system to obtain the text. That means
you can use the line editor, full screen editor, or upload the
text.

The first question is "what is the subject of your msg". I'll
restrict the subject to 35 characters, 5 less than the subject of
a REAL message.

After you enter the subject, I'll ask for the access level and
access compare method.

(H171)
Just what the name implies. You can, provided the hours are OK,
page the sysop for a chat.

Osiris will play 10 short musical tunes to CALL you to the
computer. If you want to CHAT with the individual, press C.

Osiris has TWO built-in chat systems, ASCII and Split
screen ANSI.

(H172)
Displays the CURRENT version of Osiris and who it is registered to.

(H173)
All private messages on the system, as well as any incoming and
outgoing Internet e-mail goes in the message center or sometimes
called a callers MAILBOX. The message center also allows for
carbon copies, return recites, and file attaches.

If the message has a file attach, that file must be in the
attach.bbs subdirectory. Once the file has been downloaded, it
will be removed from the system.

I want to stress the word "Private". This is the ONLY place on the
system a caller can enter a "Private" message. In fact, the
message center does not allow for PUBLIC messages.

You do *NOT* have to setup and define a special message area for
the Message Center or Mailboxes. Osiris takes care of that.

(H174)
You do have the option of having CARBONS sent to any number of
individuals. If this attribute is selected, Osiris will ask you
for the names of the individuals you want to receive carbons.

(H175)
You can attach a file to a private message. If you are calling in,
you'll have to UPLOAD the file (Osiris will tell you when to do
that).

Attached files are placed in a SPECIAL subdirectory called
ATTACHx.BBS with X being replaced with the node number. Osiris
takes care of creating this directory.

If you want to ATTACH a file using Sphinx, the sysop editor,
you'll have to COPY the file to this directory BEFORE you compose
the message.

After the file has been downloaded, Osiris will DELETE the file
from the system.

(H176)
You have the OPTION of having Osiris notify you when the message
has been received.

(H177)
This is the on-line banking system. You can deposit time or
kilobytes you don't want or need to use in your accounts or
withdraw them as needed.

You can set the MAXIMUM amount of time or kilobytes that can be
deposited in the NODEx.BBS section.

You SHOULD use this feature because I deposit UPLOAD credits, if
any, to the BANK instead of given it DIRECTLY to you.

If you simply want to allow people to WITHDRAW what I deposit, set
the MAXIMUM amounts for the TIME and KILOBYTES to 0.

If you deposit time, I will deduct it from your DAILY or WEEKLY
amount and I'll adjust the TIME for the current call accordingly.
It is possible, highly likely, that a single deposit will have no
adverse effect on the time for the CURRENT call.

Example:

If you have 60 minutes PER call, 120 minutes PER day, and this is
the first call, you could deposit up to 60 minutes BEFORE the time
for the CURRENT call would be affected.

(H178)
Plugs in a sysop defined database system. See the section labeled
"Database Retrieval System" for instructions on how to setup
a database.
(H179)
Enter your mailers matrix area.

If you don't already know what MATRIX mail is, you should skip
this. You don't need additional software to run MATRIX
mail on your system other than a mailer.

Osiris supports your mailers matrix message area and gives your
callers the ability to send and receive matrix mail. The TYPE or
BRAND of mailer isn't important as long as it saves the matrix
messages in Fidonet .MSG format.  The .MSG format offers full
ZONE, NET, NODE, and POINT addressing. If your mailer does not
support the Fidonet ZONE field, it cannot be use. For instances,
Frontdoor 2.02 does not FULLY support the Fidonet .MSG format and
can only be used to SEND mail. It does not properly implement the
ZONE fields when RECEIVING mail.

Before you can install the matrix mail option, you need to have
InterBBS configured on your system. The Matrix mail module uses
the InterBBS configuration file to obtain the path to your mailers
matrix area and it also uses the MATRIX mail addresses you defined
in the InterBBS configuration file. This keeps the matrix mail
option fairly generic to the TYPE of mailer software you are
using.

If you have InterBBS install, select the NODE option  in SM and
fill out the  Matrix Cost, Crash Access, and POINT number fields.

You can also create a TEXT file called FREEBIE in your OSIRIS=
directory.

If the message is addressed to one of the systems listed in the
FREEBIE file, you will not be charged for sending the message.

The FREEBIE file contains one 4-D domain address per line in the
format of ZONE.NET.NODE.POINT

Pay special attention to the subdomain separator. Use a PERIOD to
separate the different subdomains and NOT : and  /

The final step is to pick-out a slot on one of your command
records and select the NETMAIL option. You will find the NETMAIL
option under GENERAL.

                             Nodelist

We decided against using any type of NODELIST because we'd have to
use one of our OWN due to the DIFFERENT formats in-use by mailers.
Nodelists already take up so much disk space, the thought of
burdening you with an another one was unthinkable. We'll let your
mailer handle orphaning any message that cannot or does not have a
valid address.

                          Access Levels

Unlike other MESSAGE type modules in Osiris, the READ/ENTER/REPLY,
etc. have no access levels. You cannot enter a message unless it
is a FREEBIE or you have enough matrix credit to send it. You can
only read and reply to messages addressed to you.

                          Multiple Nodes

Unlike other message systems found in Osiris XLT, the netmail
system is not MULTINODE because the Fidonet .MSG format itself is
not multinode.

That does NOT mean that you cannot use the Netmail option on a
multiline system, you can. However, Osiris will only give ONE node
at a time access to your mailers matrix area. If someone on NODE 2
is entering or reading matrix mail and someone on NODE 1 tries to
access the matrix area they will get a message telling them that
someone else is using netmail and to try later.

(H180)
Access a Classified Ad system. See the section labeled
"Classified Ad System" for instructions on how to setup
an AD system.

(H181)
This is functionally identical to the STARTUP.BBS Force ICON Check
only the caller must select this option.

It will ONLY work for those that support RIP graphics.

(H182)
Anonymous FTP is a method of retrieving Files on the Internet. A
lot of people think you have to have a SLIP/PPP,  56K or T1
connection to do FTP but that is not correct.

All you need for Anonymous FTP is a simple UUCP connect into
Internet. In fact, the UUCP connect is twice as fast as a SLIP/PPP
connect when it comes to Anonymous FTP.

Before you can plug in this function, you must have Scorpion
installed. Scorpion is the Internet E-mail Import and Export
program.

(H183)
Anonymous DIR is a method of retrieving a File LIST from a site on
the Internet. A lot of people think you have to have a SLIP/PPP,
56K or T1 connection to do this but that is not correct.

All you need for Anonymous DIR is a simple UUCP connect into
Internet.

Before you can plug in this function, you must have Scorpion
installed. Scorpion is the Internet E-mail Import and Export
program.

(H184)
Archie is a service that will search FTP sites on the Internet
to find files that match a search pattern.

A lot of people think you have to have a SLIP/PPP,  56K or T1
connection to use Archie but that is not correct. All you need is
a simple UUCP connect into Internet.

Before you can plug in this function, you must have Scorpion
installed. Scorpion is the Internet E-mail Import and Export
program.

(H185)
The World-Wide-Web (sometimes called WWW or W3) is a collection of
documents strung together by "hypertext"  links. This means that
any word in a WWW document can act as a pointer to another
document containing related information.

This function will allow you to retrieve documents on the WWW.

A lot of people think you have to have a SLIP/PPP,  56K or T1
connection to use WWW but that is not correct. All you need is
a simple UUCP connect into Internet.

Before you can plug in this function, you must have Scorpion
installed. Scorpion is the Internet E-mail Import and Export
program.

(H186)
KIS is short for Knowbot Information Server and it takes a persons
name and attempts to track down their Internet address.

Before you can plug in this function, you must have Scorpion
installed. Scorpion is the Internet E-mail Import and Export
program.

(H187)
WAIS stands for Wide Area Information Service, and is a means of
searching a set of over 500 indexed databases. The range of topics
is too broad to mention, always changing, and besides, you'll soon
know how to get the topic list for yourself.

You can "Surf the Net" to WAIS by telnetting to quake.think.com
but I'd rather edit a binary file with EDLIN. Talk about a geeky
Unix-smelling user interface... There are something things you
just can't blame on a poor VT100 emulator, and this is one.

A lot of people think you have to have a SLIP/PPP,  56K or T1
connection to use WAIS but that is not correct. All you need is
a simple UUCP connect into Internet.

In fact, it is much easier if you DO use a UUCP connect, given the
WAIS interface.

Before you can plug in this function, you must have Scorpion
installed. Scorpion is the Internet E-mail Import and Export
program.

(H188)
"Finger" is a utility that returns information about another user.
Usually it's just boring stuff like last logon, etc., but sometimes
people put fun or useful information in their finger replies.

A lot of people think you have to have a SLIP/PPP,  56K or T1
connection to use FINGER but that is not correct. All you need is
a simple UUCP connect into Internet.

Before you can plug in this function, you must have Scorpion
installed. Scorpion is the Internet E-mail Import and Export
program.

(H189)
This feature available only under PrimeStar.

This uses the TEXT VIEWER to display the XLT log for the current
node. Everything is displayed so you may want to restrict access to
this function.

If you are the sysop, you'll be asked if you want the log RESET when
you exit the TEXT VIEWER.

(H190)
This  is  similar  to  the Compuserv "GO" command and the
Prodigy "JUMP" command.

Basically, it allows you JUMP to a specific subsystem (Osiris.bbs
command record) without having to thread your way through other
command records, a short cut CHAIN command.

Lets assume you have 5 subsystem laided out something like this:

                         Conference System
                               ^
                               |
           Call History <- Main Menu -> File System
                               |
                               v
                            Internet


You have chain commands from the main menu to each of the other
subsystems. You may even have a chain command to link the
conference and file systems.

If you are in the Conference system and decide you needed to go to
the Internet system, you'd have travel to the main menu and then
to the internet system.

With the JUMP command, you could go directly from the Conference
system to the Internet system even thou the two are not directly
linked with a Chain command.

Obviously with the example above you could simply interchain all
the systems together.

But if you have a fair size system with oh... 30 or 40 subsystems
,not uncommon on some of the larger Osiris BBSes, you wouldn't
have enough command slots to hold the chain commands much less any
slots left for other items. Besides, having 50/60 commands on a
single menu would leave your callers in a dazed state.

(H191)
On our BBS, we have a lot of a lot of people that only call a
couple of times. They either come in to download Osiris, download
Vfast, test vFast, or just to look around.

That means our USER base builds up at a pretty fast clip and we
end up having to do a purge on it every couple of months.

So, what we've done is added a GUEST log-on feature. The GUEST
log-on allows anyone to use a set user record, no password is
every asked for, that gives them quick, and limited, access to the
system.

A GUEST log-on does not allow them to access any part of the BBS
that would require a unique user name.

Items a GUEST log-on cannot access:

Private E-mail
Threaded Reader
Read By Subject
Fidonet E-mail
Any of the Internet functions
Doors
Join/Unjoin Conferences
Offline Reader
TeleConferencing
Classified Ads
Plug&Play Database
On-line Store
Edit User Settings (Changing protocols is allowed)

If they attempt to access any of the items I've listed above,
they'll get a screen tell'em that basically a GUEST log-on is used
by Multiple people and the item they have selected is not
available using a GUEST account.

To engage this feature, create a USER record with the name of
GUEST, ALIAS of GUEST, whatever CITY you want, and whatever PHONE
number you want.

The easiest way is simply to log on in LOCAL mode and let the BBS
setup the record. You'll have to do that from DOS and not from the
WAITING FOR CALL SCREEN. Using L from the WAITING FOR CALL SCREEN
will simply log you on as the sysop.

Finally, add /G or -G to the command line you use with Osiris.

If you require TWO primary names, don't worry about it. Osiris
will not enforce that if someone attempts to use the GUEST log-on.

(H192)
A special post  lets you specify WHO the message is going to and
the caller  cannot change WHO it is addressed to.  The message is
posted to the message center (e-mail) and can be to an individual
on the BBS or it can be an Internet address.

To set-up a special post, select the SPECIAL POST option, located
in the OSIRIS.BBS section of SM. The command is listed under
GENERAL COMMANDS.

When you select this command, you'll be asked to provide the name
of the control file, you make this so it can be anything you want.
The control file should go in the MENU directory defined for the
command record you are going to use.

The contents of the control file containing the name of the person
the message is addressed "TO".

The line MUST be the first line in the control file and the name
must be 75 characters or less.

We'll use (SEP) to identify a SPECIAL POST control file when
viewing a command record.

(H193)
SUBMENU is a very powerful command that lets you create pull
down SUB MENUS for those using RIP GRAPHICS.

The idea is two fold. First, you can use submenu's to reduce the
number of commands you have to list on a single screen. Second,
you may want to use a graphic image (ICON or JPEG) on the screen
and you may not want to HIDE any part of it.

Create a SUBMENU using the following guidelines:

1. Start each SUBMENU with the QUERY text variable $SMF$
2. CLIP the area of the screen the SUBMENU is going to overlay
   to the CLIPBOARD. This must  be done prior to drawing
   ANYTHING. Write down the X0 and Y0 locations, you'll need it
   later to restore the screen.
3. Do *NOT* use a TEXT Window.
4. Buttons should *NOT* clear the screen.

When you create a submenu, you also have to create another
corresponding RESTORE rip screen with the same BASE name but with
the extension of .XIP.

Create the RESTORE rip screen with the following guidelines:

1. Start each SUBMENU with the QUERY text variable $MKILL$
2. Follow this with the QUERY text variable $RMF$
3. Paste the contents of the CLIPBOARD to the screen using
   the X0 and Y0 locations you wrote down.

Remember, X0 and Y0 *HAVE* to be in Meganum (base 32) format.

Steps 1 and 2 may look weird, but they are in the correct order.

SUBMENU and RESTORE files must have the same name with one
exception, the extension.

When you define a submenu, you enter ONLY the base name, no
extension. Osiris will add the extension of .RIP.

The name of the RESTORE file would be the same base name but with
the extension of .XIP. You don't have to define the RESTORE file
name anywhere. Osiris creates it from the BASE name of the
SUBMENU.

Assuming you define a submenu named SUB1. You would create the
SUBMENU file SUB1.RIP and the RESTORE screen file name would be
SUB1.XIP and BOTH files would go into the MENU directory for the
Osiris.bbs command record you are going to plug the submenu into.

When you PLUG the SUBMENU command into a slot, SM will ask you for
the name of the file. This is the BASE name and NO extension
should/can be used.

Taking our SUB1.RIP example, type in the name SUB1

You don't have to CLOSE the submenu to select something on the
PRIMARY menu but  it is a good idea to always put a CLOSE MENU
option on your submenu setup to send ^M to the HOST when clicked.

When a SUBMENU is open and the CLIENT sends a ^M, Osiris closes
the submenu using the RESTORE file and waits for more input.

That's really all there is to it. Just remember, a submenu is
nothing more than an extension of your primary RIP display menu.

If you want an example to look at, download the SUBMENU.UC2 file
from our BBS.

(H194)
You can setup ALT1.BAT - ALT10.BAT and call the batch files
from the Osiris WAITING for call screen by pressing ALT F1 - ALT F10.

The ALT1.BAT - ALT10.BAT file must be in a PATH directory or the OSIRIS
directory.
(H195)
Osiris uses its own built in high speed ANSI emulator that writes
directly to the Video port. This accounts for a VAST increase in
speed over the traditional ANSI.SYS drivers.

If you have no other applications that need ANSI.SYS, you can
remove it from your config.sys and save a little memory.

(H196)
If you try to log-on but you've used up your time for the day, or
week, I'll check your bank account. If you have a LEAST 10 minutes
of banked time, I'll automatically withdraw 10 minutes so you can
at least get ON-LINE and make it to the bank.

When you attempt a download and you don't have enough time I'll
check your bank account and if you have enough banked time to make
up the difference WITHOUT overrunning any pending event, I'll
withdraw the time for you.

If you select to download TOO many files and you don't have enough
KILOBYTES left for the day, or week, I'll check your bank account
and if you have enough banked kilobytes to make up the difference,
I'll withdraw enough to allow the download.

(H197)
One little used but never the less very important feature to
command records is the AUTOxx.PRG and AUTOLxx. PRG file, xx
is replaced by the number of the command record.

In SM, you deal primaryly with the NAMES of the command records
but SM does show you the COMMAND RECORD NUMBER in the upper right
hand corner of the screen. You can see it, but obviously you cannot
edit/change the number.

When Osiris loads a command record, it checks the menu directory
for that command record to see if AUTOxx.PRG exists and if it
does, it is executed ASAP.

Lets assume you've just loaded command record #2. Osiris would
look for AUTO2.PRG.

We use it on Genesis to warn 2400 baud callers that happen to
wonder into the RIP demo section. Some of the demos are quite
large and could take upwards of 5 minutes to display at 2400 baud.

So we've got an AUTO8.PRG file setup that does something like:

IF(_BAUD < 9600)
{
cls();
printf("Warning, some of these Demo's can take 5\n");
printf("minutes or longer to display at 2400 baud.\n");
printf("I would advice that you exit this section ASAP.\n");
force_pause();
}

AUTOLxx.PRG functions the same as the AUTOxx.PRG except it is
automatically executed when you LEAVE (That's what the L stands
for) a command record.

BEFORE Osiris loads a NEW command record, it checks the menu directory
for the CURRENT command record to see if AUTOLxx.PRG exists and if it
does, it is executed BEFORE the new command record is loaded.

Lets assume command record 2 is CURRENTLY loaded and Osiris is about
to LOAD command record 0. Osiris would look for AUTOL2.PRG and execute
it BEFORE it loads command record 0.



(H198)
Unlike other BBS application, Osiris has no FIXED command
structure. Instead, Osiris uses COMMAND records, each with 26
slots that hold commands such as show user list, read messages,
download a file, play a game, show this text file, use this
database, etc.

If it helps to understand exactly what a command record is, think
of each command record as a traditional BBS subsystem like your
Main Menu or your message system.

The installation program installed THREE command records and they
give you a BASIC BBS with commands that are found on most BBS
system. You can have up to 32736 command records each with 26
commands. You can nest command records as deep as you want but I
would suggest that you not go more than three levels deep.

When you select the SM/Command/Osiris.Bbs option you'll get a screen
that looks something like this:

╔════════════════════════════════ osiris.bbs ═════════════════════════════╗
║                                                                         ║
║                                                                        ║
║  Record Name                           Record Number  0               ▓ ║
║                                                                       ░ ║
║  Menu Path                                                            ░ ║
║                                                                       ░ ║
║  Menu Name                  Require Rip  No                           ░ ║
║                                                                       ░ ║
║                                                                       ░ ║
║  Display File Area Info  No        Display Msg Area Info  No          ░ ║
║                                                                       ░ ║
║  Menu Sound File                                                      ░ ║
║                                                                       ░ ║
║                                                                       ░ ║
║  Command                             Hotkey        Access ▄           ░ ║
║                                                    ▀▀▀▀▀▀▀▀           ░ ║
║                                                                       ░ ║
║  Command                             Hotkey        Access ▄            ║
║                                                                         ║
║             First▄ Last▄ Add▄ Del▄ Next▄ Prior▄ Exit▄ Update▄           ║
║              ▀▀▀▀▀  ▀▀▀▀  ▀▀▀  ▀▀▀  ▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀▀▀▀           ║
║                   Click on BLUE field to edit or define.                ║
║                                                                         ║
╚═════════════════════════════════════════════════════════════════════════╝

Data entry field editing and movement commands for this section
are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, UP/DN arrow keys, the SCROLL bar at the BOTTOM of
the screen, PGDN and PGUP.

Each command record has a field labeled "Record Name".

This should CLEARLY explain what the command record is for. When
the callers help level set to SHORT or NO menus, the record name
is displayed to give the caller some idea as to WHERE he or she is
located.

Typical records names might be "Main Menu", "File Area", "Message
Area", "Statistics", or "Games".

The next field on a command record is labeled "Menu Path".  This
is the path to a subdirectory that holds ALL the display files,
menus, SPL/I, and special control files. Special control files
such as those needed by the database retrievel system, the
document retrieval system, and the classified ad system (to name a
few).

Quite often sysops FORGET this and they will not move a new menu
or display file to the proper directory and they can't figure out
WHY it isn't displayed.

The next field on a command record is labeled "Menu Name". This
field should contain the name of the MENU file, minus file
extension, and it will be displayed to the caller when their help
level is set to FULL.

Again, the name should NOT contain any type of file extension.
Osiris will ADD the file extension based on the CALLERS graphic
settings. See the section labeled "Creating Menus" to learn more
about making and NAMING menu files.

The next field is labeled "Require Rip". If this field is set to
"YES", Osiris will NOT allow the caller to select this command
record UNLESS, he or she is using RIP graphics.

The fields "Display File Area Info" and "Display Msg Area Info"
tell Osiris WHEN/IF information such as area name, area number,
file subsystem name, should be displayed. You can toggle one or
the other to YES but never toggle BOTH of them to yes.

The next field is labeled "Menu Sound File". Three guesses what
this field does :) Just enter the name of the sound file you want
played when this command is selected. Place all .WAV sound files
in your ICONS directory.

                         Adding a Command

This is where you PLUG-IN the commands, define the hotkeys for
those commands, and setup access information.

To define a command, click on the BLUE field following the text
"Command".

A small menu will open listing several command cateogires such as;
File Area Commands, Msg Area Commands, General Commands, SPL/I
Command File, Display File,  External Program, Statistics, Chain
Command, and Rip Display File.

The menu will look something like this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌──────────── Select Category ────────────┐ ║
║ │File Area Commands                        ║
║ │Msg Area Commands                        ▓ ║
║ │General Commands                         ░ ║
║ │SPL/I Command File                       ░ ║
║ │Display File                             ░ ║
║ │External Program                         ░ ║
║ │Chain Command                            ░ ║
║ │Statistics                                ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║       Ok ▄      Cancel ▄     Delete ▄       ║
║       ▀▀▀▀      ▀▀▀▀▀▀▀▀     ▀▀▀▀▀▀▀▀       ║
╚═════════════════════════════════════════════╝

To select a category, click on the one you want. It will
be HIGHLIGHTED then click on OK. Click on CANCEL to exit
without selecting anything. Clicking on DELETE will CLEAR
the current definition.

If you select File Area Commands, Msg Area Commands, General
Commands, or Statistics another menu will open listing the
commands available under that category.

The screen display looks and functions the same as the one listed
above.

SPL/I, an Osiris programming language command file, has to be in
the directory defined in the "Menu Path" field.

Display File is an ASCII based text file. If the caller is in RIP
mode, Osiris will use the full screen text VIEWER (has scroll
bars and ICONS) to display the file. The Display file must be in
the directory defined in the "Menu Path" field.

Rip Display File is like the "Display File" but this one is
specifically for RIP screens ONLY. If the caller does NOT support
RIP graphics, they cannot select this slot.

Chain Command, this is how the caller moves from Command record to
Command Record. When you select this command, a menu will open
listing all the command records, select the one you want to CHAIN
to. This is a VERY powerful command and there is a HELP section
devoted exclusively to Chaining. This section is listed as
"Building Roads Between Command Records"

External Program . . .. The program can be a batch, com, or
exe file and can be located anywhere. Well, DOS has to be able to
find it so it will either have to be in the OSIRIS directory or in
a PATH directory.

I will write DOOR.SYS, DORINFOx.DEF, USERx.QBS, and OUTx.QBS in
the OSIRIS directory, in case your external application needs one
of them.

If the application does, then you'll want to execute a BATCH file
that copies the file to the correct directory and THEN calls the
application instead of trying to call the application directly.

I will also passes several command line switches. Whether or not
you use them is up to you and the program you're calling.

The switches are; Connect Rate, Serial Port, Node Number, UART
Rate, Time Left In Minutes, and finally a 0 or 1 with 1 meaning
LOCAL mode. If you were to process this information with DOS batch
variables, it would be:

%1 = Connect Rate, %2 = Serial Port, %3 = Node Number, %4 = Uart
Rate, %5 = Time left in minutes, and %6 contains 0 or 1.

Keep this in mind if you are a programmer. USERx.QBS is your BBS
user record. ANY and ALL modifications to this file will be
RETAINED.

After you select the command, SM will ask you to PRESS the HOTKEY
you want to activate this command. SM will NOT allow you to have
DUPLICATE hotkeys and if you select one already IN-USE, SM will
BEEP at you and make you do it again.

After selecting the HOTKEY, the ACCESS screen will open and this
screen looks something like this:

╔═══════════════════════════════════════════════════════════════════════════╗
║                            () Greater Than or Equal To                   ║
║                            ( ) Less Than or Equal To                      ║
║ Access Level  0            ( ) Equal To                                   ║
║                            ( ) Less Than                                  ║
║                            ( ) Greater Than                               ║
║                                                                           ║
║ Active On       Node 0     Starting Time  00:00    Ending Time 00:00      ║
║                                                                           ║
║ Mon [X]         Sound File                       Cost 0                   ║
║ Tue [X]                                                                   ║
║ Wed [X]                            SPL/I Flags                            ║
║ Thu [X]                                                                   ║
║ Fri [X]     1   2   3   4   5   6   7   8   9  10  11  12  13  14  15  16 ║
║ Sat [X]    [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]║
║ Sun [X]                                                                   ║
║                                                                           ║
║              Ok ▄                                  Cancel ▄               ║
║              ▀▀▀▀                                  ▀▀▀▀▀▀▀▀               ║
║                                                                           ║
╚═══════════════════════════════════════════════════════════════════════════╝

From here you set the access level, compare method, time of day, days
of the week, command key flags (if any), which node you have to
be on to use the command (0 = ANY NODE), cost (if any) that Osiris
will subtract from your matrix credit, etc.

Any time you want to CHANGE any of the ACCESS information, click
on the ACCESS button.

To Delete or Remove any command, click on the BLUE field following
the label "Command" and when the CATEGORY menu opens, click on the
DELETE button.

When you are VIEWING a command record, you may notice that some
of the COMMAND boxes have text that includes items enclosed in
brackets, ( ).

             (DBS) : Stands For Database System
             (RIP) : Stands For Rip Display File
             (SPL) : Stands For SPL Command File
             (EXT) : Stands For EXTERNAL Program
             (DRS) : Stands For Document Retrieval System
             (CAS) : Stands For Classified Ad System
             (C)   : Stands For CHAIN Command

Reason: Sometimes a NAME like BOX.CTL doesn't tell you WHAT it
goes to. But, BOX.CTL (DRS) tells you that this is a CONTROL
file for a Document Retrieval System.

(H199)
While you CAN delete a command record, we strongly advise that
you do NOT use this option. You can create all kinds of WORK for
yourself if you do.

Chain uses a command records PHYSICAL record number to identify
WHICH record you want to jump to. If you DELETE a record, every
record number from that record to the END of the file will change
and you'll end up with chain commands linked to the WRONG record.

If you use AUTOxx.PRG and/or AUTOLxx.PRG files, those will be
thrown off.

It is much better to simply UNLINK (remove all CHAIN's to that
record) if you no longer need it. You can REUSE the record later
if you need to expand your system.

(H200)
If you find and report a bug in OSIRIS.EXE and we can duplicate
and verify the bug, we'll fix the problem with 72 hours providing
it is something within our control and make that fix available at
no charge.

You *HAVE* to report the bug before we can fix it. If you don't
report it, don't expect to see it corrected.

Please notice that we are talking about the MAIN BBS program.
Secondary programs, while important, are not critical to the
operation of your system. Those bugs will be fixed and made
available during our normal maintenance releases.

Items not under our control would be something like a bug in a
compiler or commerial library. In this case, we'll try to find a
work around and report the bug to the people that CAN fix the
problem.

There are, of course, exceptions to these rules.

If the problem demands a massive change in the code to correct,
we may require a testing period before it is made available.
Swapping one bug for another is simply not acceptable to us.
(H201)
International TeleCommunications general makes Beta software
available to any REGISTERED Osiris sysop that wants to download
it.

Beta software often has bugs so use it at your own risk.

Do NOT ask any of our Technical support staff questions about beta
software, they will not be able to answer. For obvious reasons,
technical support personal are not permitted to use beta
applications.

Beta applications are generally, but not always, released on
Fridays.

(H202)
Now you're thinking that this is kind of nice. You can create an
unlimited number of command records (subsystems) but how do you
get the callers from one command record to another ???? . . . use
the CHAIN option.

Think of the chain command as a ONE WAY ROAD that provides the
caller a way to travel from one command record to another.

Let's assume that you have defined THREE command records; one for
your main menu, one for the conference message areas, and one for
the file areas (you COULD have used just one command record but it
would be a tad crowed).

Let's further assume that you used the names "main menu",
"Conference Area", and "File area" when you created the command
records.

To build a road between the "Main Menu" and the "Conference Area",
load SM and go to the COMMAND/Osiris.Bbs section.

Move to the command record labeled "Main Menu". Pickout an empty
slot and click on it. When the Category menu opens, select the
CHAIN option.

A menu will open listing the names of the command records you have
defined. You want to build a road to the "Conference Area" command
record so click on the option with that label and then click on
OK.

You've now built a road the caller can travel to get from the
"Main Menu" command record to the "Conference Area" command
record.

Hold on, you aren't finished yet. Remember, all ROADS are ONE WAY.
You've provided a road from the "Main Menu" TO the "Conference
Area" but, that is a ONE WAY road so you'll have to build another
road to get the caller BACK to the "Main Menu".

Move to the command record labeled "Conference Area" and repeat
the process only this time, select the "Main Menu".

Having said that, I want to point out that you don't HAVE to do
that. You COULD build a road from the "Conference Area" to another
command record and then build a road from THAT command record BACK
to the "Main Menu" command record. That's a round about way, but
under some conditions, you might want to do that.

A single command record can have MANY roads branching out in ANY
number of different directions.

A command record can also only have ONE road and that road takes
you BACK to the PREVIOUS command record. That option is labeled
BACK UP.

On our BBS, Genesis, we use 6 command records laid out something
like this:

                           --------------
                          |  Main Menu   |
                           --------------
                         /       |        \
                  ----------   -----------  \  ------------
                 |Call Stats| | File Areas|---| Conf Areas |
                  ----------   -----------     ____________
                              /         \
                            /             \
                    -----------         ----------
                   |File Maint.|       |File Stats |
                    -----------         -----------

The Call Stats, File Maint., and File Stats command records use
the BACK UP CHAIN command to return to the command record they
were called from.

I've interconnected the main menu, file areas, and Conf areas with
CHAIN options so you can move back and forth between the command
records.

You'll notice there is a road between the file area and conf area
records and roads connecting both to the main menu.

You could further sub-divide the system by including a third
command record chained to from the File Area's record for ARCHIVE
maintenance, extracting and viewing, to even further simplify the
file area menu.

We don't have 'ON-Line' games but if we did, I might create two or
three other command records interlinked together and to the main
menu.

The expansion possibilities are unlimited and because they are
unlimited, you can get yourself into trouble by creating a system
so complex that people will not like to call.

Try to keep it simple. By that I mean don't go TOO many levels
DEEP. To get to something, you should not have to go through 3 or
4 levels of nested command records.

The maximum I would recommend is nesting no more than 2 levels
deep.

In the example of our system, the file maint. command record is on
the 2nd level, nested under the file area command record. Going
deeper would create a rather complex system for callers.

That isn't to say that you can't, I don't care HOW deep you nest
command records, you can go 2000 levels deep if you want.

There is also a SHORT cut method of getting from one command record
to another. Read the section on "LONG JUMP" for an explaination.
(H203)
Every time someone logs on to your BBS, Osiris always says they
are connected at 19200, 38400, 57600, or 115200 even if they are
calling with a 2400 baud modem.

You are running a FIXED DTE rate of 19200, 38400, 57600, or 115200
and your modem is reporting the DTE rate instead of the CONNECT
rate.

This is fine for TERMINAL programs but not for a BBS. The BBS
needs to know the EXACT CONNECT rate to enforce time limit when it
comes to downloading.

You need to dig out the modem manaul and find out which command
you need to include in the -W string that will TELL your modem NOT
to report the DTE rate.

(H204)
Every time someone logs on to your BBS, Osiris always says they
are connected at 300 baud.

                   Running a FIXED DTE Rate

If you are running a FIXED DTE rate of 38400, 57600, or 115200 and
your modem is reporting the DTE rate instead of the CONNECT rate.

Say your modem reported CONNECT 38400. When Osiris scanned the
mdmstr1.bbs looking for something that matched this, the only thing
it could find was "CONNECT". "CONNECT" matches the first part of
"CONNECT 38400". 300 baud is defined as the baud rate to use
for "CONNECT".

CONNECT 38400 might be CONNECT 57600 or CONNECT 115200, depending
on what FIXED DTE rate you use.

You have two options:

1. (Recommended)

Dig out the modem manaul and find out which command you need to
include in the -W string that will TELL your modem NOT to report
the DTE rate.

2. (Not Recommended)

Add "CONNECT 38400", or whatever, to the top of your mdmstr1.bbs
file. This should only be used as a STOP GAP until you can
implement option 1.

                       Not using a FIXED DTE Rate

If you are NOT running a FIXED DTE rate, then your modem is reporting
a rate that is *NOT* defined in MDMSTRx.BBS. Since most connect messages
begin with the word CONNECT, the only thing that matches is the 300 baud
definition CONNECT.

The answer, find out what your modem is reporting and add that to
MDMSTRx.BBS

(H205)
This is caused when Osiris uses one serial RATE and your modem is
using another.

Generally this happens when you have a LOCKED serial rate and you
forgot to TELL Osiris about the LOCK rate or, you told Osiris but
didn't tell your MODEM.

Modem's have to be TOLD via AT commands to FIX the serial rate.

Assuming you failed to tell Osiris and your fixed serial rate is
38,400 and your using COM PORT 2.

Add the following to your autoexec.bat file and REBOOT your
computer.

SET COM2=38400

If you DID tell Osiris  but you forgot to setup your modem to use
a fixed serial rate, sometimes called a fix dte rate, you'll have
to consult your modem manual and find out which commands you need
to use.
(H206)
Osiris XLT contains an internal CALL BACK VERIFICATION system, CBV
is the short name. CBV will call the person currently on-line so
that you will know the name and phone number he or she left is
valid.

You can access CBV from TWO locations, NEWUSER and STARTUP. You'd
primarily want to use CBV in the NEWUSER sections but you MAY want
to include it in the STARTUP as a backup just in case something
happened that prevented verifications when that person originally
logged on.

To use CBV, you need to create three files, two text and one
binary configuration file. All three files should be in the OSIRIS
directory.

You will need to create, in the Osiris directory, a MDMSTRx.BBS
and x should be replaced by the NODE number of the node that is
going to use this control file, file listing your modems response
strings along with the connect rates to associate with each
string.

Example of MDMSTR1.BBS (control file for node 1):

CONNECT_19200 19200
CONNECT_16800 16800
CONNECT_14400 14400
CONNECT_12000 12000
CONNECT_9600 9600
CONNECT_7200 7200
CONNECT_4800 4800
CONNECT_2400 2400
CONNECT_1200 1200
CONNECT 300

You will notice the connect message cannot contain spaces. If the
message NEEDS a space, most all do, use the underscore character.
I will replace it with a space when I read the file.

The faster connect messages MUST be listed first. A sample
MDMSTR1.BBS file is included in the XLT archives. 99.99 percent of
you can use this file as is.

Next, Setup a CBV.CTL file. CBV.CTL serves TWO purposes, first it
is a PHONE NUMBER translation control file consisting of THREE
fields per line.

<LOOK FOR THIS> <EXCHANGE IT WITH THIS> <LENGTH OF #>

<LOOK FOR THIS> is part or all of a phone number to look for when
examining the callers PHONE number.

This is used to trap area codes, LD numbers, etc. and change them
into a format that can be dialed from your location.

Assume that your area code is 314 and several local exchanges your
area are 686 and 785. The callers phone number is 3146860120. You
can't DIAL that number from your location because it is local.
You'd first need to translate that to just 6860120.

The first TWO lines in your cbv.ctl would look like this:

314686 686 10
314785 785 10

I would take the callers phone number and check to see if it
started with 314686 or 314785. If so, the six digits would be
replaced with either 686 or 785, depending on WHICH line matched.

The 10 is a SAFETY fallback system. It simply means the callers
phone number MUST ORIGINALLY contain 10 digits.

Keep in mind the callers phone number will VARY depending on the
type of PICTURE mask you use.

Lets assume that you want to go ahead and verify ANYONE in the
United States, including LOCAL numbers. You'd HAVE to make sure
that your Phone number PICTURE mask also required the caller to
enter COUNTRY code (1 for the United States).

The mask might look something like this:

9 (999) 999-9999

Add up the 9's and you'll find that each caller would have a 11
digit phone number.

If you have forgotten, you defined the picture mask in NODEx.BBS,
phone number field.

1314686 686 11
1314785 785 11
1314 1 11

The FIRST two lines translates LOCAL numbers. The THIRD line
translates IN-STATE toll calls by stripping out the area code.

The SECOND purpose is to give OSIRIS the OK to dial that system.
In order for call back verification to proceed, Osiris must make
SOME type of match with the callers phone number and a <LOOK FOR
THIS> field.

E.g. If the callers phone number is 3186869913 and the cbv.ctl
contained:

314686 686 10
314785 785 10

there would be NO match and I would NOT make an attempt to verify
the caller.

Finally, select the SM/MISC/CBV and configure your CBVxx.CFG.
See help section labeled /SM/MISC/CBV for details.

I've also provided for a optional fourth text file called
phone.bad. This file can contain phone numbers that you do NOT
want called. The police are not very understanding about having
modems dial the local police station at 2 AM.

This is the actual DIAL out number so assuming 13146860120
translated to 6860120 and you did NOT want that number called, you
would place 6860120 in this file.

You can have a maximum of 21 numbers listed.

In order for CBV to work, the caller MUST have the access level
equal to that of a NEW caller. I'll ignore this function request
if the callers access level is NOT equal to the NEW callers access
level.

There is NO display or messages to the caller if the callers
access level is not equal to the NEW caller access level, the
phone number is not listed as OK to dial, or the phone number
is in the phone.bad file. As far as the caller is concerned,
nothing happened.

(H207)
In anticipation of the EXON bill, we've added a censorship system.

Censor.bbs goes in your OSIRIS directory and contains a list of
words, one word or phrase per line, that you or the government
consider as offensive and can't be used by callers in message.

When someone uses the line editor or full screen editor selects to
save the message, Osiris will scan their message and if any word
listed in censor.bbs is used, they'll get a screen telling them
they have used an offensive word, what that word is, and to edit
their message and remove the word.

The censor.bbs file also applies to UPLOADING a message as well as
QWK and Bluewave. Because QWK/BLUEWAVE offline readers do not give
you the option of editing a message once it has been placed in a
REPLY archive, the message is simply not imported if it fails the
CENSORSHIP test.

(H208)
Each classified ad system requires a CONTROL file telling it the
full drive, path, and name of a file that it is suppose to use to
STORE the AD's, the ACCESS level required to POST an AD, and finally
the MAXIMUM number of days an AD can run.

A control file might look something like this:

C:\OSIRIS\AD\CAR.DAT 5 30

Use the file C:\OSIRIS\AD\CAR.DAT to store all the ads, the maximum
number of days an AD can run is 30, and access level 5 or higher
is required to post an AD.

You can use ANY name you want for the CONTROL file, as long as it
is unique.

Decide which COMMAND record you are going to use and copy the
control file to the directory you defined for that command record.

Load SM and go to the COMMMAND/OSIRIS.BBS section and move to the
that command record, click on a blank slot, select GENERAL
commands, click on the Classified Ad, enter the name of the
CONTROL file, set the the HOTKEY, and the access information.

Now load your CAT.CFG file and add:

CLASSIFIED <DRIVE/PATH/DATAFILE NAME>

In the control file example listed above I used
"C:\OSIRIS\AD\CAR.DAT 5 30", the corresponding cat.cfg entry would
look like this: CLASSIFIED C:\OSIRIS\AD\CAR.DAT

This tells CAT to scan this file and remove any EXPIRED ad's.

I would recommend that you setup a WHOLE subsystem devoted to
classified ad's and setup a different Classified ad system for
individual items like Cars, Houses, Computer Equipment, etc. Just
like you newspaper breaks down Classified ads by category.

The CLASSIFIED AD system also supports GRAPHIC (RIP BASED) posts.
The RIP based posts can contain ICONS, JPEG, and WAV sound files.

In your classified control file, the maximum days a post can
accepts 0 (ZERO). If you set it to ZERO, the AD/POST is not
automatically deleted and stays until the person that posted it
kills the POST/AD.

Example: C:\OSIRIS\CLASS\PRODUCT.CTL 1 0

If you want to change the text on the top status bar for different
Classifed commands, you can extract the 210.XLT file and use it to
create another display file.

Basically, I'd just copy it to a different file name and edit the
file with any text editor. Of course, you should be careful and
only change the text:

Osiris XLT (c) International TeleCommunications

For this example, lets rename it to POWER.RIP.

In the classified control file, add a fourth field, the name of
the new rip screen.

Example:

C:\OSIRIS\CLASS\PRODUCT.CTL 1 0 C:\OSIRIS\POWER.RIP

Notice I included the drive and path.

If you edit the 210.XLT file with RIPAINT, save it using only the
KILL FIELD option and don't optimize it.

And remember .... you can only SAFELY chance the text on the top
bar, the blue bottom backdrop, and the shadow.

Everything else must stay the same.

(H209)
The best, but certainly not the only, method of handling CD-ROM
areas, give each CD-ROM it's own personal File System.

If you want to replace an OLD CD with a NEW one, you just click
one time and 1/100th of a second later all evidence of the OLD
CD's gone and it doesn't effect ANY of the other file areas or
file systems.

If you only have ONE CD-ROM drive but 20 CD's, you can define 20
file systems and only the File System corresponding to the disk
currently in the drive will be seen or available.

See the section labeled "Defining Multiple File Systems". That
section will show you how to setup a new file system.

The files on a CD-ROM are grouped into several, generally 50 or
more, subdirectories off the ROOT directory. Each one of those
subdirectories will be a file area.

If you are not going to use a different file system, skip the next
paragraph.

We'll assume you decided to give the CD it's own personal file
system and you have already setup that file system. If so, Load SM
and go to the MISC/Select File Group option and change into the
file system you setup for this CD.

Go to the Boards/Filboard.Bbs section and select the AUTO ADD
option. SM will ask you for a drive/path to the subdirectories on
the CD.

If the CD is drive F then you would enter F:\

SM will create file areas for each one of the subdirectories. SM
will use the AREA name  NEW : <SUBDIRECTORY NAME>

You can edit the area names at any time.

Exit back to the primary SM menu and  go to the Files/File Area
Manager Section and switch into one of the new file areas.

Each CD subdirectory has a text file (or should) and this text
file contains the names and descriptions of all the files in that
subdirectory. Generally, but not always, they use the file name
"Files.bbs".

Open the OPERATION menu and move to the very last option, the one
labeled "Adopt From Control". When you select this option, SM will
ask you for the NAME of the text control file. This is the file we
talked about in the last paragraph.

If you are not SURE what the name is, shell to DOS (ALT-D) and
look.

Now, SM will do a bit of processing and then a window will open at
the top of the screen and a single line of text will appear. This
is a SAMPLE of one of the lines in the control file and SM will
ask you, "How many spaces to start of description?"

Example:

BELL.ZIP 83838 10/10/94 This is a test file.
        ^     ^        ^
        1     2        3

You would enter 3.

or

BELL.ZIP [0] This is a test.
        ^   ^
        1   2

You would enter 2.

As soon as you provide this information, SM will start the
ADOPTION process.

If the description contains multiple lines, the first line is used
for the SHORT description. The ENTIRE description is also added as
an EXTENDED description.

When SM has finished, move to anther file area and repeat this
process until you have adopted all the files.

If the CD does NOT have a text file, you'll have to use the normal
ADOPT option and descriptions will have to be entered by hand.

The final step needs only be done once, the first time you add
second file system. To allow callers access to a second, third,
fourth, fifth, etc. file system, you need to plug in a command to
change file systems.

Go to the command record, generally the one you use for all the
file area type commands, find an empty slot, and plug in the command
'CHANGE FILE SYSTEMS'.

You'll find this command listed under the FILE AREA COMMAND submenu.

(H210)
Cat's the Osiris Robot maintenance system. It handles all the
GRUNT work of cleaning, converting archive formats, etc.

If you run a MAILER Front-end, you should setup a MAILER event
that will run CAT one a day to keep your system in TOP condition.

If you run Osiris WITHOUT a mailer front-end, i.e. Osiris answers
the phone, you do *NOT* have to worry about running CAT.

See the section on MIDNIGHT MAINTENANCE for further details.
(H211)
Cat requires a control file to tell it WHAT to do. The name of the
control file is CAT.CFG, I've included a sample CAT.CFG, and must
be in the OSIRIS= directory.

CAT.CFG can contain any or all of the following in any order:

Call History <NODE> <DAYS TO KEEP>
Delete Not Called <Day Of Month> <Days Not Called>
Make Filelist <CtrlFname> <HeaderFile> <ArchiveCommand>
NEW Filelist <DAYS> <CtrlFname> <HeaderFile> <ArchiveCommand>
Post Bulletin <Day Of Month> <ACCESS> <COMP> <Filename> <Subj>
Post Conference <Day Of Month> <Area> <Filename> <Subject>
Check Message Areas <Day Of Week>
Remove Old Bulletins <Days Old>
Message Center Maintance <Day Of Week>
Archive Type 1 <DAY OF WEEK>
; Archive Type's are as Follows . . . .
;
; 0 No Conversion.
; 1 Uc2 [Uses Uc.exe]
; 2 Arj [Uses ARJ.EXE]
; 3 Zip [Uses Pkzip/Pkunzip.exe]
; 4 RAR [Uses RAR.EXE]
; Archives MUST be in one of the directories defined in
; your PATH= statement.
Run Program <FILENAME> <DAY OF WEEK>
VIRUS CHECK SCAN C: D: E: /NOPAUSE /M
VIRUS CHECK TBSCAN C: D: E: -allmem -log -batch
TEST E:OVL01819.EXE 13457893123
Delete Received <No Days>
Archive Comment
Strip Files <INSERT FILENAME>

                          <DAY OF WEEK>

Several of the CAT.CFG commands were followed by <DAY OF WEEK>.
This is the day or days you want CAT to execute this particular
command.

Valid day of week designators are:

MON
TUE
WED
THU
FRI
SAT
SUN

You may stack multiple days on the same line.

Example:

Check Message Areas MON WED FRI

                          <DAY OF MONTH>

Several options require a DAY of the MONTH to run.

                         Archive Comment

Tells CAT to add an ARCHIVE comment to any NEWLY uploaded ZIP or
ARJ file.

Cat obtains the archive comment from COMMENT.FAM. See the section
on SM/COMMENT.FAM for an explanation of COMMENT.FAM

                           Strip Files
                        <INSERT FILENAME>

Tells CAT to scan NEW uploads and check the archive for the files
listed in STRIP.CFG. If it finds one, remove it from the archive.

STRIP.CFG is a simple text file located in the OSIRIS= directory
and it contains one file name per line, unlimited number of lines.
The file name CAN contain DOS wildcard characters.

This is generally used to STRIP out BBS ADS from new uploads.

<INSERT FILENAME> is the name of a text file you want INSERTED
into NEW uploads. This is generally your OWN BBS AD. We use it to
insert a file that tells the person downloading it that it HAS
been VIRUS check by this system and found to contain NO known
viruses.

                        Delete Not Called
                      <DAY OF MONTH> <Days>

E.g., Delete Not Called 1 185

Cat will delete users on the 1st day of the month that have NOT
called the system in 185 days, about six months.

Although you may NOT stack day of the month designators, you may
use multiple lines if you want to run it more than once a month.

Delete Not Called 1 185
Delete Not Called 15 185

Cat will delete users on the 1st or the 15th.

NOTE: Cat will also remove any user records with access level
zero, 0.

                           New Filelist
                            <DAYS OLD>
                         <CTRL FILENAME>
                          <HEADER FILE>
                        <ARCHIVE COMMAND>

This is generally used as a NEW File's Request list or to offer
callers a text listing they can down load and read off line.

<DAYS OLD> is the number of days, 1 to 99. Any file uploaded
within <DAYS OLD> is included. Otherwise, it is EXCLUDED from the
list.

'NEW Filelist' requires a control file, you can pick the name and
it is the FIRST argument following the KEY Phrase "Make FileList".
The control file contains two lines. The first line is the full
drive, path, and file name that is to be used for the TEXT
listings.

E.g. c:\osiris\files\filelist.txt

The second line contains a list of the Osiris File areas to add to
the TEXT listing. The list consists of the numeric area number, up
to 500, separated by a blank space. All areas MUST fit on ONE
line.

e.g. 1 2 3 4 8 11 23

Example of a control file

c:\osiris\files\general\filelist.txt
1 2 3 4 5 6 8 9 10 11 12 13
<EOF>

The second argument is the name of a text HEADER file to insert at
the TOP of the list. This file may contain almost anything but is
generally used to display the name of your BBS.

The third and final argument is the complete archiving
instructions.

E.g. arj m -e -jm d:\general\filelist filelist.txt

Example of a complete Make FIlelist statement

NEW Filelist 14 Flist.ctl fist.hdr arj m -e -jm d:\flist filelist.txt

You can add multiple "NEW FILELIST" commands to the cat.cfg file
if you want to create MULTIPLE lists.

                          Make Filelist
                         <CTRL FILENAME>
                          <HEADER FILE>
                        <ARCHIVE COMMAND>

This is generally used as a File Request list or to offer callers
a text listing they can down load and read off line.

'Make Filelist' requires a control file, you can pick the name and
it is the FIRST argument following the KEY Phrase "Make FileList".

The control file contains two lines. The first line is the full
drive, path, and file name that is to be used for the TEXT
listings.

E.g. c:\osiris\files\filelist.txt

The second line contains a list of the Osiris File areas to add to
the TEXT listing. The list consists of the numeric area number, up
to 500, separated by a blank space. All areas MUST fit on ONE
line.

e.g. 1 2 3 4 8 11 23

Example of a control file

c:\osiris\files\general\filelist.txt
1 2 3 4 5 6 8 9 10 11 12 13
<EOF>

The second argument is the name of a text HEADER file to insert at
the TOP of the list. This file may contain almost anything but is
generally used to display the name of your BBS.

The third and final argument is the complete archiving
instructions.

E.g. arj m -e -jm d:\general\filelist filelist.txt

Example of a complete Make FIlelist statement

Make Filelist Flist.ctl fist.hdr arj m -e  -jm d:\flist filelist.txt

You can add multiple "MAKE FILELIST" commands to the cat.cfg file
if you want to create MULTIPLE listings.

                         Post Conference
                          <Day of Month>
                              <Area>
                              <File>
                            <Subject>

This lets you automate the posting of a specific message, like
echo area rules, on a particular day of the month.

<Day of Month> is the day, integer from 1 to 31, of the month to
post the message.

<Area> is the Conference message area, 1 to the highest area you
have defined, the message goes into.

<File> is the name of a text file, one created with MKPOST.EXE,
that contains the body of the message.

<SUBJECT> is the text you want used as the SUBJECT of the message.
Do NOT exceed 38 characters. I do not check this and if you exceed
38 characters you will corrupt the message area.

Example:

Post Conference 1 10 c:\osi\rules.txt Echo Area Rules

On the 1st of the month post a message in area 10. Use the text
file c:\osi\rules.txt for the message body and use "Echo Area
Rules" as the subject of the message. There is no limit to the
number of "post conference" commands you can have in your cat.cfg
file.

                          Post Bulletin
                          <Day of Month>
                          <Access Level>
                         <Compare Method>
                              <File>
                            <Subject>


This lets you automate the posting of a specific system bulletin,
like system rules, on a particular day of the month.

<Day of Month> is the day, integer from 1 to 31, of the month to
post the bulletin.

<Access Level> is the access level required for this bulletin.

<Compare Method> is HOW Osiris is to compare the bulletins access
level to the callers access.

Compare method is an integer between and including 1 and 5.

1 = Greater Than Or Equal To.
2 = Less Than Or Equal To.
3 = Equal To.
4 = Less Than.
5 = Greater Than.

<File> is the name of a text file, one created with MKPOST.EXE,
contains the body of the system bulletin.

<SUBJECT> is the text you want used as the SUBJECT. Do NOT exceed
38 characters. I do not check this and if you exceed 38 characters
you will corrupt the message area.

Post Bulletin 15 11 4 c:\rules.txt System Rules

On the 15th of the month post a bulletin. Use the text file
c:\rules.txt for the bulletins body and use "System Rules" as the
subject.

The Bulletin's access level is 11, compare method is Less Than.
Meaning, only those with access levels less than 11 will see this
bulletin.

There is no limit to the number of "post bulletin" commands you
can have in your cat.cfg file.

                       Check Message Areas
                          <DAY OF WEEK>

When I see an area that exceeds the pack trigger level, I'll trim
the area back to the pack level. This keeps the individual message
bases down to size. When an area has deleted messages, I'll also
PACK the area to get rid of the messages. You may NOT need the
pack trigger level or the deleted messages checked every day.
Especially if you have enough hard drive space to allow them to go
OVER the trigger level.

The reason you may want to relax this part of the check is disk
fragmentation. Packing a message area does generate some
fragmentation and can take a lot of time, specially if you keep a
lot of messages on-line.

Check Message Areas <DAYS TO RUN> is used to govern this part of
the message area maintenance section in Cat. I will only TEST the
Trigger levels and watch for deleted messages on the day or days
you specify.

Of course, if you handle a LOT of echomail or you have a marginal
amount of free disk space, you may need to do it every day.

E.g.

Check Message Areas Mon Wed Fri

                             WARNING

Cat does NOT know or care if you have messages that have NOT been
exported. If you've told Cat to trim an area back, it will do so
regardless of the message's echo status.

Therefore, make SURE you export prior to running CAT.

                         Delete Received
                              <DAYS>

Cat defaults to removing PRIVATE messages that have been received
after 4 days. If you want them kept longer, you can reset this
using the "Delete Received" command.

DELETE RECEIVED 14
DELETE RECEIVED 2

                           Archive Type
                          0, 1, 2, 3, or 4
                          <DAYS TO RUN>

Here you define the default archive type, if any, and the day or
days of the week you want this to run. This is the archive format
you want all files to be placed in.

Cat will scan your files.bbs and convert any file, not located on
a CD-ROM drive, not in the proper format.

Example:

Archive Type 1 MON WED FRI
Archive Type 1 FRI

                           Run Program
                            <Filename>
                          <Days to Run>

You may have applications or maintenance programs that are not
directly related Osiris that you'd like to run on a scheduled
bases.

"Run Program" allows you to define programs, generally batch
files, along with the day or days of the week you want them to
run.

There is no limit to the number of programs you can define and
they will have at least 512K of free memory to run, providing you
had 512K free BEFORE you ran cat.

E.g. Run Program HDMAINT.BAT MON WED SAT

<Filename> cannot contain spaces so you cannot pass command line
parameters. If the program requires command line parameters, call
a batch file and have the batch file call the program.

                           Virus Check
                          <Command line>

If you want a SYSTEM wide virus scan run during your maintenance
event, use this verb.

Place the name of the virus checking program and any command line
settings following the key words VIRUS CHECK.

I've defined TWO for you, one for Mcafee's SCAN.EXE and one for
TBSCAN.COM.

Uncomment the one you want to use and edit to suit your system.

You'll need to change the " C: D: E:" to go along with YOUR
drives. You may also need to change the "C:\OSIRIS\VIRUS.MSG".
This is the file SCAN.EXE uses to LOG any files that may contain a
virus. TBSCAN.COM will use "TBSCAN.LOG" and you'll find it in your
OSIRIS= directory.

You may define a TOTALLY new program to replace either of these.
Just include the name of the program along with any command line
switches.

There are two restrictions. If the program does not find a virus,
it must return error level 0. If it does find a virus, it must
return 1 or higher.

The command line, including the name of the program, can't exceed
128 characters.

(H212)
                    Cat File Integrity System

This engages the CAT FILE INTEGRITY system. Cat will computer an
Integrity checksum for the file you've defined and if it doesn't
match the integrity checksum you've listed, it will be flagged as
infected with an Unknown virus. One the virus checker didn't know
about.

You define a file by using the key work TEST. Following TEST
include the FULL drive, path, and the name of the file to check
and the Integrity Checksum for that file.

e.g. TEST C:\OSIRIS\OSM.EXE 3459123475

There is no limit on the number of files you can define for
testing. There are several advantages to using this system over
the normal virus check, TBSCAN.EXE. It can detect changes in a
file and it doesn't have to know anything about the virus that did
it. New virus comes along, doesn't matter. It'll be detected if it
does anything to the files you've defined.

The 2nd big advantage is speed. This system is 10 to 20 times
faster than using TBSCAN.EXE to do a system wide virus scan.

Chksum.exe can be used to generate the file's original integrity
checksum. Chksum requires one of three possible command line
switches.

/Ffilename : Computer a file integrity
             checksum on "filename."

eg. /FC:\OSIRIS\CAT.EXE

If this switch is used, the file integrity checksum will be
displayed on the screen. Write it down and manually edit the cat
control file and add the file name and the integrity checksum.

/Cfilename : Use the CONTROL file "filename"
             to obtain the names of the
             files.

The control file is a text based file with a complete drive, path,
and filename. One per line.

Instead of printing the checksum on the screen, I'll place them in
a text file called CHKSUM.DAT. If chksum.dat already exists, I'll
append to it.

The entries in Chksum.dat will be PRE-FORMATTED so you can simply
IMPORT chksum.dat into the cat control file.



eg. Chksum /Cfile.ctl

/SDRIVE : Analyze the drive and build a chksum.dat file
          containing the full drive, path, filename, and the
          integrity checksum for all COM, EXE, OVL, and OVR files
          on the system. If chksum.dat already exists, I'll append
          to it.

This is the QUICKEST method of getting all the executable files
and overlays, ovl and ovr, added to the cat control file.


You will also need to MANUALLY, using /F, generate integrity
checksum for EVERY file listed in your CONFIG.SYS.

The entries in Chksum.dat will be PREFORMATTED so you can simply
IMPORT chksum.dat into the cat control file.

You now have one more defense against NEW viruses.

                    Call History <NODE> <KEEP>
                       1 - 255 and 1 - 365

This is how I find out WHICH HISTxx.BBS file to keep trimmed back
to <KEEP> days.

You supply the NODE number following the key words CALL HISTORY
and following the Node number, the number of days you want to keep
on file. I recommend a minimum of 30 days.

Examples:

CALL HISTORY 1 30
CALL HISTORY 2 30
CALL HISTORY 3 45

You can have up to 255 CALL HISTORY commands listed in CAT.CFG

                     Message Center Maintance
                          <DAY OF WEEK>

This is similar to Check Message Areas in respects to removing
deleted messages and renumbering.

The message center has no pack trigger level, however, CAT does
delete RECEIVED messages that are over 4 days old. It will also
delete messages that have NOT been received if they are over 90
days old.

You may adjust the delete received and the delete NOT received
days with OTHER CAT.CFG commands.

                    Download/Upload Databases

Cat automatically checks the upload and download databases and
keeps them to 10,000 entries, each.

                       Remove Old Bulletins
                            <DAYS OLD>

Tells CAT how long <DAYS OLD> to KEEP a system bulletin.

E.G.

Remove Old Bulletins 30

Remove any bulletin that is OVER 30 days old.

                      Command Line Operation

You can run CAT from the COMMAND LINE and only those functions you
list on the command line will be executed.

Optional Command line switches are: -Ax, -V, -I, -E, -C, -M, -H,
-F, -Z, -?, and -Nxxxx

The forward slash, /, may be used in place of the dash, -.

-C Triggers Check Conference Areas.
-M Triggers Message Center Maintance.
-F Triggers Build File Request List.
-Zxx Remove User Records with ACCESS LEVEL xx.
-Nxx Remove Users Who Haven't Called in xxx Days.
-Ax Archive conversion using type X [1, 2, or 3].
-V Virus scan.
-I Cat File Integrity check.
-E Run External Programs.
-G Triggers Build New File Request List.

If you are running on the "TIGHT" side in respects to disk space,
you might want to include "CAT -C" after you import and export
echomail. Be SURE you do it AFTER exporting.

(H213)
Osiris has a color optimizer built into the MMU color display
system that can reduce the number of characters to the screen and
com port by 38 to 40 percent, depending on colors used.

COMPILED MMU files will be optimized, RAW ANSI will be displayed
AS IS without being optimized or altered in any way.

Most, if not ALL, the internal colors within Osiris will go thou
the color optimizer. Callers should see the "Jerky" movement (at
12/2400 baud) associated with color changes all but disappear.

(H214)
Below is a COMPLETE list of command line arguments that you COULD
use with Osiris. Many of these switches are listed in other places
but we wanted to come up with a COMPLETE list that you could
reference at a single glance.

You can use a dash, - , in place of the forward slash, /

                                /E

Total Disable RIP graphics for EVERYONE.

                                /I

This forces the display of RIP log-on Help reminder screen to
everyone and not just to those with a new user access level.

                                /C

/C cancels the "LEAVE MESSAGE TO SYSOP" log-off prompt.

                                /A

/A  cancels the ARE YOU SURE prompt during log-off.

                                /G

Activate the GUEST log-on.

                                /D

Default the local display in SNOOP mode for ANSI callers.

                                /R

Require as least TWO words for the primary user name. This does
not effect ALIAS names.

                                /H

Leave the modem HOT, don't drop carrier, when logging off.

                                /W

Running in STAND-ALONE, no front-end mailer, mode.

                       /N<Numeric Argument>

Run using this node number, <Numeric Argument>. Node number must
be a numeric value between 1 and 255.

                       /B<Numeric Argument>

Use this baud rate, <Numeric Argument>, for the current caller.

                       /T<Numeric Argument>

This is the number of minutes, <Numeric Argument>, to the NEXT
"Mailer" event. If this switch is not used, Osiris assumes
MIDNIGHT to be the next "Mailer" event.

"Mailer" is assumed to be an EXTERNAL FRONT-END mailer and *NOT*
the built-in mailer.

                                /L

Logging on in LOCAL mode, do not use SERIAL DRIVER.

                       /P<Numeric Argument>

Use serial port <Numeric Argument>.

                       /S<Numeric Argument>

Set internal screen blanker to <Numeric Argument>. <Numeric
Argument> is the number of minutes to wait before blanking the
screen.


(H215)
The first thing you need to know is WHERE to put menus. To figure
that out, go to the Osiris.bbs command record you plan on doing a
menu for and look for the field labeled "Menu Path". Any menu you
create goes in the directory defined in this field.

If you are creating a menu for a NEW command record and that field
is blank, you'll have to fill it in. You can use an existing
subdirectory or you can make a new one.

Once you know WHERE it goes, you have to know what file name to
use.

A DOS file name contains TWO parts, the primary consisting of the
first 1-8 characters up to the PERIOD and the extension
consisting of 1 - 3 characters FOLLOWING the PERIOD.

Example 1: JBMENU.EXE
           ^^^^^^

Example 2: JBMENU.EXE
                  ^^^

Example 1 shows you the PRIMARY name, Example 2 shows you the
extension.

Now that you know the parts of a file name, Load SM and go to the
OSIRIS.BBS command record you are creating a menu for and look for
a field labeled "MENU NAME". This field contains the PRIMARY name
of the menu. If the field is BLANK, i.e. this is a NEW command
record, you'll have to fill the PRIMARY name and it must be unique
and cannot already exist in the MENU PATH diretory.

Again, this field should only contain the PRIMARY part of the menu
name and should never contain the EXTENSION.

The EXTENSION is automatically added by the BBS depending on the
callers graphic settings and would be either: RIP, MMU, or ANS

RIP = RIP menu
ANS = ANSI menu
MMU = Compiled ANSI menu

Assuming you defined a menu called "MAIN"

If the caller is in ANSI mode, Osiris would look for MAIN.MMU. If
that doesn't exits, Osiris would look for MAIN.ANS. If that
doesn't exit, the caller doesn't get a menu.

If the caller is in RIP mode, Osiris would look for MAIN.RIP

                       Creating ANSI Menus

NOTE: Replace <FILENAME> with the PRIMARY file name you're using
for the menu.

The first step to creating a menu is to load SM and go to the
Command/Osiris.Bbs system and move to the Command Record you are
creating the menu for. Jot down which command keys you used for
each function. The entire process should take no longer than a
couple of minutes.

Load an ansi draw program, THEDRAW is highly recommend, and draw
the menu the way you want it to look. You can use any colors you
want, but I do advice that you avoid using background colors other
than BLACK. You should clearly outline the KEY required to
activate each function.

One word of warning, do not go pass column seventy eight on the
screen. You'll want to avoid the DOS automatic screen wrap and you
do that by keeping the width to seventy eight or less.

Once you've got the menu LOOKING the way you want, save it using
the PRIMARY file name plus the extension of .ANS.

If you are using THEDRAW, use CLEAR SCREEN, ANSI , and DISPLAY
SPEED 0.

You'll need to edit the ANSI file with your text editor and remove
the extra blank lines at the end of the file, to keep the menu
from scrolling off the screen.

The ANSI program MAY use the ANSI VERTICAL tab sequence instead of
blank lines. Check the file and if you see something like "<-[20H,
<-[21H, or <-[24H at the end, remove them. The <- is an arrow but
this word processor doesn't allow that character.

The finished product with be <FILENAME>.ANS

Now, you have TWO options at this point; You can COPY
<FILENAME>.ANS to the menu directory as is or you can go one step
farther and optimize it for SIZE and SPEED.

OPTMIZING is optional but it does speed up the display. COMPILE
<FILENAME>.ANS with the MMU compiler use the following command
line:

MMU <FILENAME>.ANS /A /F

The MMU compiler will create a file called <FILENAME>.MMU and this
is a highly compressed display file. You would copy <FILENAME>.MMU
to the menu directory.

Again, if you compile with the MMU compiler, copy the
<FILENAME>.MMU to the menu directory and *NOT* <FILENAME>.ANS

All the default ANSI menus that come with Osiris are compiled with
the MMU compiler. We don't distribute the ANSI files we used but
that isn't a problem.

If you WANT to use the default menus as a TEMPLATE for creating
your own, you can REVERSE compile the <FILENAME>.MMU into an ANSI
file by using the command line:

MMU <FILENAME>.MMU /R

See the section on MMU for a detailed explanation of MMU and
optional command line switches.

                             WARNING!

Do not attempt to edit a MMU file. If you want to make changes,
use the ORIGINAL ANSI file. Make your changes then compile the new
ANSI file.

                        Creating RIP Menus

Creating RIP menus is pretty much the same as creating ANSI menus
except you use a RIP draw program instead of an ANSI draw program.
There are quite a few out there but we recommend two of them:
JDRAW and RIPaint.

RIPaint, the best, goes for about $140-$200 depending on who you
buy it from.

JDRAW goes for $20 dollars and is adequate for menus.

You can make your menus look any way you want but there are a
couple of things  you have to do.

1. When making buttons, NEVER set a button to reset the screen.

2. We'll use RIPaint as an example and you can translate this to
match whatever RIP draw program you are using.

When saving a screen, use the following settings:

File Width : 2000            Leading C/R   :
Max Size   : 0               Kill Fields   : X
WordWrap   : X               Reset Windows :
1 Cmd/Line :                 Auto-Optimize : X
No Text Win: X               Add CLS       :

3. Run the FIXRIP.EXE program with the name of your menu file.

   Example: FIXRIP MAIN.RIP

This program fixes it so that your screens will display correctly
no matter what column you happen to be in.

4. Use the same BASE name you used for your ANSI menu. If your
ANSI menu was MAIN.ANS or MAIN.MMU, your RIP menu would be
MAIN.RIP.

If you are making a menu for a file system or conference system,
you must also add a button that displays the current ACTIVE
message or current ACTIVE file system.

The button should send a ^A (Control A).

(H216)
Under GENERAL you'll find a very powerful command called SUBMENU.
SUBMENU lets you create pull down SUB MENUS for those using RIP
GRAPHICS.

The idea is two fold. First, you can use submenu's to reduce the
number of commands you have to list on a single screen. Second,
you may want to use a graphic image (ICON or JPEG) on the screen
and you may not want to HIDE any part of it.

Create a SUBMENU using the following guidelines:

1. Start each SUBMENU with the QUERY text variable $SMF$
2. CLIP the area of the screen the SUBMENU is going to overlay
   to the CLIPBOARD. This must  be done prior to drawing
   ANYTHING. Write down the X0 and Y0 locations, you'll need it
   later to restore the screen.
3. Do *NOT* use a TEXT Window.
4. Buttons should *NOT* clear the screen.

When you create a submenu, you also have to create another
corresponding RESTORE rip screen with the same BASE name but with
the extension of .XIP.

Create the RESTORE rip screen with the following guidelines:

1. Start each SUBMENU with the QUERY text variable $MKILL$
2. Follow this with the QUERY text variable $RMF$
3. Paste the contents of the CLIPBOARD to the screen using
   the X0 and Y0 locations you wrote down.

Remember, X0 and Y0 *HAVE* to be in Meganum (base 32) format.

Steps 1 and 2 may look weird, but they are in the correct order.

SUBMENU and RESTORE files must have the same name with one
exception, the extension.

When you define a submenu, you enter ONLY the base name, no
extension. Osiris will add the extension of .RIP.

The name of the RESTORE file would be the same base name but with
the extension of .XIP. You don't have to define the RESTORE file
name anywhere. Osiris creates it from the BASE name of the
SUBMENU.

Assuming you define a submenu named SUB1. You would create the
SUBMENU file SUB1.RIP and the RESTORE screen file name would be
SUB1.XIP and BOTH files would go into the MENU directory for the
Osiris.bbs command record you are going to plug the submenu into.

When you PLUG the SUBMENU command into a slot, SM will ask you for
the name of the file. This is the BASE name and NO extension
should/can be used.

Taking our SUB1.RIP example, type in the name SUB1

You don't have to CLOSE the submenu to select something on the
PRIMARY menu but  it is a good idea to always put a CLOSE MENU
option on your submenu setup to send ^M to the HOST when clicked.

When a SUBMENU is open and the CLIENT sends a ^M, Osiris closes
the submenu using the RESTORE file and waits for more input.

That's really all there is to it. Just remember, a submenu is
nothing more than an extension of your primary RIP display menu.

If you want an example to look at, download the SUBMENU.UC2 file
from our BBS.

(H217)
Osiris has a unique file recovery system that functions almost
like Zmodem crash recovery.

If you have file selected for downloading or you are in the middle
of a download and lose carrier, Osiris will remember WHICH files
you were downloading or had selected. When you call back, Osiris
will give you the option of having those files placed BACK in the
download queue so you can continue.

If you have files selected for downloading and you elect to log-
off before downloading them, Osiris will give you the option of
SAVING those files for you next call.

This CAN save you and your callers a considerable amount of time
if you have a very large system. Large in respects to the number
of files and file areas you have.

(H218)
                           Restrictions

1. A record can contain up to 17 line and a maximum of 50 fields.
2. The maximum field size is 80 characters.
3. A field MUST fit on a single line.
4. A Database can contain a maximum of 32736 records. If you need
   more than 32736 records, you need to use multiple databases
   that are MORE specific. Callers are not going to want waste
   time wading through thousands of records to find the EXACT one
   they want.



                    Creating a Database System

To build a database system, you must create a CONTROL file that
contains the BASE name of the data files, the name of the PRIMARY
menu file, the HOTKEYS for the menu, a SEARCH menu, a HELP display
screen( optional) , and the SCREEN and DATABASE layout.

The first line of the control file contains the BASE name of the
DATA files. You do NOT use a file extension, Osiris will add
those. You CAN, if you want, include a DRIVE and PATH with the
BASE name, "c:\osiris\bbs".

Lets assume you are going to create a BBS database. The logical
BASE name would be "bbs" and that is what you would put on the
FIRST line.

Osiris will create the files; BBS.DAT, BBS.IDX, and BBS.HDR.

BBS.DAT contains the actual records, BBS.IDX is the indices, and
BBS.HDR contains specific information about each record, like who
entered the record.

That's really all you need to know about the BASE name and the
data files.

The second line contains the name of the PRIMARY menu, minus the
file extension. Osiris will ADD the file extension based on the
callers GRAPHIC settings. You can, if you want, include a drive
and path.

You'll need to create the menu's, two of them. One ANSI menu with
the file extension of .ANS, .MMU if you compile it with MMU, and
a RIP menu with the file extension of .RIP

Each menu should show the following commands:

A)dd Record
S)earch
V)iew By Record Number
H)elp (Optional)
E)xit.
ENTER = View ALL starting with FIRST record.

The HELP file is option and if you create it, use the BASE name
plus a .HLP extension. Using our example, the help file for the
BBS database would be BBS.HLP.

The third line of the control file contain the HOTKEYS for the
menus. This line must contain "ASVEH", minus quotation marks and
in that specific order. A is for Add, S is for Search, V is for
View, E is for exit, and H is for Help. You cannot leave out ANY
of them.

If you are not using the English language, substitute the
corresponding characters for the language you are using.

The fourth line contains the BASE name of the SEARCH display file.
This is displayed to the caller when the SEARCH option is selected
and should contain instructions on HOW the search feature works
and what fields are indexed.

In RIP mode, you MUST supply a TEXT windows 79 characters long.

I strongly suggest that you use the search.ans file that we've
included in the Osiris archives to derive your own search file.

At this point, your control file would look something like:

bbs
menu
ASVEH
search

         Defining The Screen Display And Database Record

Lines 5 - 21 contain the screen layout and database record
field definitions. Anything pass line 5 is optional but you MUST
have at least one line with at least one field.

We're going to use 5 lines, lines 5 - 9, to show you how to setup
a record.

First Define the field names, screen locations, field width and
type of input for each field.

The field width's and the type of input that is allowed must be
defined using PICTURE symbols: X, A, or 9, anything else is just
displayed. Please make note that X and A are UPPER CASE. Lower
case will NOT work.

X - Any Alphanumeric Character
A - Alpha Character
9 - Numeric Character

Example:

BBS Name  XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

City      XXXXXXXXXXXXXXXXXXXXXXXXXX    State XX

BBS Phone (999) 999-9999

When the record is displayed, for viewing or to add/edit a record,
the screen will be laid out just like you defined it.

Now that you have laid out the display record and fields, you must
actually DEFINE the fields.

To define a field, enclose it in curly brackets, { }.

Example:

BBS Name  {XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX}

City      {XXXXXXXXXXXXXXXXXXXXXXXXXX}    State {XX}

BBS Phone {(999) 999-9999}

Now you must define the FIELD ATTRIBUTES.

Each field has THREE attribute settings separated by a COMMA:
Required, Index, and FULL. You must define the attributes in the
exact same order as I've listed them and each attribute setting
has either a Y indicating Yes or N indicating No.

Required means the caller MUST put something in this field. Index
tells Osiris to use the field as an Index field and you can index
one or all of the fields, and FULL means the caller MUST fill out
the ENTIRE field before leaving it.

Example:

BBS Name  {Y,Y,N,XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX}

City      {Y,Y,N,XXXXXXXXXXXXXXXXXXXXXXXXXX}    State {Y,Y,Y,XX}

BBS Phone {Y,N,Y,(999) 999-9999}

The BBS name field is set to REQUIRED, INDEX, FULL NOT REQUIRED.
The City field is set to REQUIRED, INDEX, FULL NOT REQUIRED.
State field is set to REQUIRED, INDEX, FULL REQUIRED.
BBS Phone Field is set to REQUIRED, NOT INDEX, FULL REQUIRED.

Notice how each attribute setting and the FIELD picture mask is
separated by a comma.

By the way, I indexed the BBS name field to give the person that
ENTERED the record an easy way of FINDING it when he or she needs
to change it.

That's all there is to setting up a database and now all you have
to do is copy the control file to the directory you defined for
the COMMAND record you are going to plug it into.

Go into SM, subsystem OSIRIS.BBS, click on an EMPTY slot, select
GENERAL commands, click on Database Retrieval, and enter the name
of the control file.

If you are still confused, study the sample BBS database we've
included.

                     Removing Deleted Records

You will periodically need to PHYSICALLY remove deleted records
and rebalance the btree. Go to the SM/DBASE subsystem and select
the PACK DRS option and enter the name of the CONTROL file.

                              Searching

The caller can enter up to 8 items or 80 characters, whichever
comes first, separated by !, |, or &.

! = NOT
| = OR
& = AND

Example:

USA&MO!DEXTER

Assuming the database is indexed on COUNTRY, CITY, and STATE this
means find all records in the USA, State of MO, excluding the CITY
DEXTER.

The search will terminate when it makes a maximum of 2000 matches.
A caller will more than likely give up long before he or she looks
at even half that many records. If the search terminates because
it has found TOO many matching records, you need to consider
breaking your database into multiple databases.

Osiris will start display the record or records after it has found
all matching records.

                         Viewing A Record

When you are viewing a record, you have the option of Moving to
the NEXT record, PREVIOUS record, DELETING the record, going to the
LAST record, going to the FIRST record, or EDITING the record.

You may only DELETE or EDIT a record if you where the one that
ADDED it or you are the sysop.

(H219)
This subsystem allows your callers to search, read, and download
text based documents. The documents themselves can be just about
anything from software/hardware technical documents, help files,
newsletters, product update notices, or anything else you can
think of.

All you have to do create a simple little control file and plug
the command into a OSIRIS.BBS slot. You don't even have to MOVE
the documents to any SPECIFIC directory.

The first line of the control file is the NAME of the database.
This is not displayed to the caller but used internally by Osiris.

The remaining line(s) contain the full drive:\path\filename of
each text file along with a brief, no more than 40 character,
description.

Example:

Harddrives
C:\DOCS\SEAGATE.DOC Seagate Drive Spec's
C:\DOCS\ADAP.DOC Adaptec Drive Spec's
C:\DOCS\CDROM.DOC Varies CD-ROM Spec's

You must place this control file in the OSIRIS= directory.

Since all the text files, documents, MUST have a DRIVE and PATH,
you can split the documents across multiple drives and
directories. They can even be listed in your FILES.BBS if you
want.

This is VERY important, you MUST include the drive and path and
NOT just the filename.

If you do something like:

SEAGATE.DOC Seagate Drive Spec's

Your system will crash.

Another important warning. Osiris does NOT validate the documents.
If you list it in the control file, it MUST be correct and it MUST
exist. It is TOO time consuming to validate, especially during
searches, each file.

To plug this in to a command record, go to the Command/Osiris.BBS
section and when it asks you to select the category, select the
"File Area Commands" and look for the option "Document Retrieval".

When you select "Document Retrieval", SM will ask you for the name
of the external program. This is the name of the CONTROL file.

That's really all there is to creating and using this feature.

From the callers point of view, it is very easy to use. The only
restriction, they MUST support ANSI.

The main menu has several selections; Search, Download, View, List
Documents, and EXIT. The names are a little different that what I
used here.

The menu(s), all 3-D, uses a SCROLL BAR to highlight the current
option. To move the SCROLL BAR, the caller uses the UP/DN arrow
key (NUM LOCK MUST BE ON, but they are told to turn it on).

To select, press ENTER.

Your first reaction might be... this is going to be slow for 2400
bps callers, but it isn't. It uses highly optimized ANSI sequences
and is very fast.

The SEARCH lets you enter from 1 to 8 KEY words. If you enter more
than one word, you are asked to specify the TYPE of search,
AND/OR/NOT to use with each word. The characters &, |, and ! are
used to designate AND, OR, or NOT.

Example: DRIVE&CONNER|SEAGATE!WESTERN

Meaning, find anything that has the text DRIVE and CONNER or
SEGATE but NOT WESTERN.

When a match is made, the document is displayed and at the end of
the display, you have the option of downloading the document.

The LIST option shows up to 10 document names and descriptions per
page, a display box is used. The contents of the display box will
scroll, as you change pages, but the box itself is displayed only
once (unless you view or download).

Again, a SCROLL BAR is used and you can use UP, DN, PGUP, PGDN to
move, ENTER to VIEW, D to DOWNLOAD, or Q to quit. If you DN arrow
and you are on the last item, it will automatically PAGE DN. If
you UP arrow and you are on the FIRST item, it will automatically
PAGE UP. Of course, Paging is contingent on there BEING another
page. In RIP mode, just click on the item to move the SCROLL BAR
or click on the PGUP or PGDN ICON to switch pages.

The VIEW and DOWNLOAD options on the MAIN screen will ask for a
FILE NAME. You would find this with the LIST option. Of course,
all screens have ample instructions displayed so the caller will
know what and how to use the system.

(H220)
This should NOT be confused with defining FILE AREAS. File Systems
CONTAIN file areas. Defining MULTIPLE file systems is OPTIONAL and
the PRIMARY use is to make handling CD-ROM areas EASIER.

Again, since this cannot be stressed too many times, a FILE SYSTEM
is N O T the same as a FILE AREA. FILE SYSTEMS ** CONTAIN ** file
area(s).

Example:

Primary File System
     File Area "Word Processors"
     File Area "Term Programs"
     File Area "Apple Programs"
     etc.
Secondard File System
     File Area "GIF"
     File Area "OS/2 Programs"
     File Area "Unix Programs"
     etc.

Osiris allows you to create multiple file systems. A file system
consists of a several database's used to define file areas and
store information about files that are AVAILABLE for downloading.

You can define a different FILE SYSTEM for each CD-ROM and put the
file areas for that CD in it's OWN  personal FILE SYSTEM. This
makes MAINTENANCE much easier when you swap out an OLD disk with a
NEW one or you have more disks than CD-ROM drives.

Osiris has a DEFAULT file system, the one you are in when you
first log-on. This is labeled "Primary File System" and it is
generally used for file areas on your READ/WRITE drives.

Each file system definition record has 8 fields you HAVE to fill
out and one OPTIONAL field.

Field       What it is
Label
----------------------------------------------------------------
Base Name : This is the NAME of the file system, the one shown to
            the caller.
Files.Bbs : The name of the file used to store information about
            the files available for download and it must be
            UNIQUE.
Files.Idx : The name of the file used to store INDEX information
            about the files and it must be UNIQUE.
Areas.Idx : The name of the file used to store INDEX information
            about the file AREAS and it must be UNIQUE.
Fileboard.Bbs: The name of the file used to store information
               about the FILE BOARDS and it must be UNIQUE.
FileCat.Bbs : The name of the file used to store the names of the
              different categories and it must be UNIQUE. Even if
              you don't plan on using categories, you still have
              to define this file.
Filesbbs.Loc: The name of a special LOCK file used to guard against
              SHARE not working right and it must be UNIQUE.
Desc.Bbs: Name of the file used to hold the EXTENDED descriptions
          and it must be UNIQUE.

You really don't need to know what each file is used for but I've
provided the information "Just in case".

Each file system also has an access level and a compare method
along with access flags and they function the same as the area
access levels and flags.

If the caller doesn't have access to a file system, it simply does
not show up.

Each file system has a field labeled "Validate Using".

This field should contain the FULL drive, path, and filename of a
file that is UNIQUE to the CD. Osiris will use this to verify the
CORRECT CD is in.

If the verification fails, the area will simply not show up.

                      Defining a File System

Step 1> Load SM go to BOARDS/FILEDEF.BBS

Step 2> Add a New Record.

Step 3> Move to the NEW record and change the file names so they
        are TOTALLY unique. You MUST change every single filename.
        The names are LABELED with their BASE or original names.

Step 4> Enter the drive, path, and file name that is FOUND on CD
        in the Validate Using Field. Osiris will use this to verify
        the CORRECT CD is in the drive for this file system.

        If you leave this field empty, Osiris will skip the
        verification process.

Step 5> Select the MISC/Select File Group option and switch to the
        NEW file group. This tells SM which file system it is working
        with when you select any option that deals with the file area.

*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*
   Skip Steps 6 and 7 if you are going to use the AUTO ADD option.
   See section "CD-ROM, Step By Step Guide".
*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*

Step 6> Go To the BOARDS/Filboard.Bbs option and define your first
        file area.

Step 7> Go to the Files/File Area Manager Section to build the correct
        Files.bbs replacements.

Step 8> Go to COMMAND/Osiris.Bbs section and plug in the Change File
        Systems command. You'll find the command listed under the
        File Area Commands.

One final note, the first RECORD is fixed except for the NAME
field. You can change the name field, if you use a language other
than english or you simply don't like the default name. But,
cannot changes to ANY other field on the first record.

That's pretty much all there is to it. Now, any time you want to
work on this particular file system, just repeat step 5.

                    How This effects Osiris.

If you do a new upload search in a file system other than the
primary system, the search date is based on the LAST time you
called. Since the idea behind this system was to make handling CD-
ROM drives easier, New uploads aren't likely but the command
needed to be available.

If you had files tagged for downloading, Osiris will start you in
the file system THOSE files were in the next time you log-on.
Providing you want to continue with the download, otherwise it'll
start you in the primary file system.

If you DO select to add those files to the download queue and they
were NOT in the PRIMARY file system the new upload search
, providing you had it plugged into a startup.bbs slot, will be
skipped.

Downloads, you cannot have files tagged for downloading in
multiple file systems. All the files you are going to download
must be in the current file system, in fact Osiris will make sure
of that.

*IF* you have files tagged and select to switch file systems,
you'll get a warning message and the option of aborting the
switch.

The primary reason; greatly reduces disk thrashing on carousal
drives.

                         Recommendations

If it were me, I'd set-up my system:

Primary File System : Contains Files on my READ/WRITE drives.

Sub File Systems: 1 For EACH CD-ROM disk. Most CD's have about 50
directories so that would be 50 or so file areas per subsystem.

(H221)
Normally, I will drop carrier and ask the modem to go OFF hook
when you log off using the GOODBYE option. If, for some reason,
you want carrier and the modem left as is, add -H to your command
line.

E.g. Osiris -P2 -B9600 -N1 -H

This MIGHT be useful for multiple BBSes. In other words, running
more than ONE BBS with the same PHONE/MODEM. You could shell,
using SPL/I, to other copies of Osiris and exit those copies back
to the original.

(H222)
At the top of the screen you'll find two fields, User List Display
and Phone Number Required.

                        User List Display

You have three ways of handling the display of a user's name when
or if you use the User List Display option in a command record.

If this is set to YES, ALL names will be shown. If set to YES, you
should set the USER LIST DISPLAY access level and access flags so
no one has access to it.

If this is set to NO, NOBODY will show up. If you set this to NO,
you should set the USER LIST DISPLAY access level and access flags
so no one has access to this change command.

If set to OPT, this gives EACH caller the option of having their
name withheld from the user list display.

Names withheld will be replaced with PRIVATE so the user list will
not be BLANK.

                      Phone Number Required

You can REQUIRE a phone number by setting this field to YES. If
you don't care if a user leaves their phone number, set this
option to NO.

(H223)
At the top of the screen you'll find two fields, User List Display
and Phone Number Required.

                        User List Display

You have three ways of handling the display of a user's name when
or if you use the User List Display option in a command record.

If this is set to YES, ALL names will be shown. If set to YES, you
should set the USER LIST DISPLAY access level and access flags so
no one has access to it.

If this is set to NO, NOBODY will show up. If you set this to NO,
you should set the USER LIST DISPLAY access level and access flags
so no one has access to this change command.

If set to OPT, this gives EACH caller the option of having their
name withheld from the user list display.

Names withheld will be replaced with PRIVATE so the user list will
not be BLANK.

                      Phone Number Required

You can REQUIRE a phone number by setting this field to YES. If
you don't care if a user leaves their phone number, set this
option to NO.

(H224)
Osiris supports 4 door drop files; USERx.QBS, OUTx.QBS, DOOR.SYS,
and DORINFOx.DEF (x  in OUTx.QBS, USERx.QBS, and DORINFOx.DEF is
replaced with the NODE number.

Osiris places all four files in the OSIRIS directory when you call
an external application and then REMOVES those drop files when you
exit from the external application. That means they will only be
there WHEN they are actually needed.

USERxxx.QBS is a copy of the callers USER RECORD. Any
modifications to this file will be retained.

OUTxxx.QBS is a drop file used by QKDOOR and DOORMASTER to create
other DROP files.

DOOR.SYS and DORINFOx.DEF are fairly popular DROP formats and
should be all you need for most external applications.

DOOR.SYS has a one major draw back, it uses a STATIC file name and
a DOOR.SYS for someone on node 1 would overwrite the DOOR.SYS for
someone on node 2 should they both select external programs.

To over come this, we've modified the name of DOOR.SYS to fit a
multiline environment. For node 1 the name remains the same, i.e.
DOOR.SYS. For nodes 2 - 255, the name of the drop file will change
to DOORxxx.SYS with xxx being the node number.

DORINFOx.DEF while multinode, is limited to nodes 1 - 9. To
overcome this, we've changed the name of the drop file on nodes 10
- 255 to DORxxx.DEF with xxx being the node number.

We've included a little program, channel.exe, that you can use in
your DOOR batch files to determine  WHAT node is calling the batch
file hench, what name to use for the DROP file.

Example of HOW to use CHANNEL.EXE

         CHANNEL %3
         if errorlevel 4 goto NODE4
         if errorlevel 3 goto NODE3
         if errorlevel 2 goto NODE2
         if errorlevel 1 goto NODE1
         exit
         :NODE4
         Copy door4.sys c:\game4\door.sys
         cd \game4
         SOMEGAME.EXE
         EXIT
         :NODE3
         Copy door3.sys c:\game3\door.sys
         cd \game3
         SOMEGAME.EXE
         EXIT
         :NODE2
         Copy door2.sys c:\game2\door.sys
         cd \game2
         SOMEGAME.EXE
         EXIT
         :NODE1
         Copy door.sys c:\game\door.sys
         cd \game
         SOMEGAME.EXE
         EXIT


(H225)
Each time a caller selects a door or external program, Osiris will
track the callers total time in the door and write it to a file
called DOOR.BBS.

The primary purpose is to allow you to BILL the callers based on
TIME when they use BBSnet or some other application to access
Internet. You can also use it to figure out which DOOR games are
popular and which aren't.

Each record in DOOR.BBS contains the users name, the name of the
door program, the date, and the total number of seconds spent in
the door.

If you need or want to write a program to read DOOR.BBS, the file
structure for each record in DOOR.BBS is;

struct _door_bbs
{
  char name[36]; /* Callers name */
  char program[13]; /* Program they called */
  long seconds; /* number of seconds in program */
  int  year,     /* Date executed and year is 2 digits. */
       month,
       day;
};


We've included a small program, DOORSTAT.EXE, that you can use to
generate several different types of reports.

This isn't a FANCY program and if you are going to use DOOR.BBS as
a method of billing, we suggest that you either WRITE something or
have someone write something for you that can take this
information and put it into some type of accounting system,
billing system, or spreadsheet.

                           DOORSTAT.EXE

Doorstat needs several command line parameters to function, what
and how many depends on the type of report.

The first command line parameter is the TYPE of report you want
and that will be 1, 2, 3, 4, or 5.

NOTE: Don't enter ANYTHING on the command line if you want a
      HELP screen.

DOORSTAT 1 "CALLERS NAME"  will generate a report telling you what
doors a specific caller has selected. The CALLERS NAME should be
enclosed in DOUBLE quotes.

Example:  DOORSTAT 1 "John Doe"

DOORSTAT 2 "CALLERS NAME"  PROGRAM NAME will generate a report
telling you when and how many times a specific person accessed a
certain door. Again, the callers name must be enclosed in DOUBLE
quotes. You don't have to enclose the name of the program in
DOUBLE quote's.

Example: DOORSTAT 2 "John Doe" LORD.BAT

DOORSTAT 3 PROGRAM NAME will generate a report listing all the
people that use that door and how much time each person spent in
the door.

Example: DOORSTAT 3 LORD.BAT

DOORSTAT 4 will generate a report on ALL doors, the number of
times each door was accessed, and the total time spent in that
door. This does *NOT* include the NAMES  of the people that access
each door.

The doors are sorted based on NUMBER of times accessed with the
ones being accessed the most at the top of the list.

Example: DOORSTAT 4

Look closely at the example, there is NO parameters after the
report type.

DOORSTAT 5 is the same as a TYPE 4 report accept the doors are
sorted on TIME.

Example: DOORSTAT 5

All the reports that DOORSTAT.EXE generate contain some type of
TOTAL time using the format HH:MM:SS

Example:  Total Time Spend In Door         :  01:23:02

In this example, the time is 1 hour, 23 minutes, and 2 seconds.

Depending on the report type, HH may be HHH or HHHH (3 or 4
digits) while MM and SS will always remain 2 digits.

DOORSTAT was not built into SM because report TYPES 3, 4, and 5
can use a lot of memory. While DOORSTAT.EXE is only a 11K program,
it COULD use as much as 400K and some of you do not have that much
memory *left* when you run SM.

To RESET the door statistics, delete DOOR.BBS. Osiris will create
a new one.


(H226)
You can define up to 20 external events to be executed at a preset
time on selected days.

Each event has time to execute, errorlevel to exit with, and the
DAYS of the week the event is active.

Time to execute is in 24 hour format, HH:MM. Just CLICK on the
field and enter the time.

Errorlevel, the errorlevel you want me to exit with when the event
is executed. Errorlevels should ALWAYS be higher than 50. We'd
like to reserve 50 and below for internal use.

DAYS of the week are the days the event is active. Click on the
box(s) that bare the label for the day or days you want. You can
select one day, any combination, or all seven.

To DISABLE an event, don't set any days.

To CLEAR an event, set the ERRORLEVEL to 0. 0 will cause the other
fields associated with the event to CLEAR.

It *IS* possible to set the errorlevel to 0 however, I will NOT
execute any event that has an errorlevel of 0.

I will ONLY execute the event ONE time per day and FIVE minutes
prior to the event, I will bring the modem OFF-HOOK.

One question that has been asked numerous times, HOW do you tell
Osiris WHAT to do during an event? The answer is, you don't.
Osiris does NOT care WHAT you do during your event. It simply
exits with the errorlevel, you trap for the errorlevel in your
batch file and do whatever.

Below is a SAMPLE runbbs.bat file that illustrates this.
Errorlevels 51, 52, 53, and 54 were defined as EVENT errorlevels.

By the way, this is a FULL functional Internet HUB batch file that
calls up twice a day to pickup and drop of Internet e-mail and
news. It also handles INCOMING UUCP sessions.

:TOP
C:
CD\OSIRIS
osiris -n1 -w
IF ERRORLEVEL 254 GOTO UUCP
IF ERRORLEVEL 54 GOTO PICKUP2
IF ERRORLEVEL 53 GOTO PICKUP2
IF ERRORLEVEL 52 GOTO MIDNIGHT
IF ERRORLEVEL 51 GOTO PICKUP
IF ERRORLEVEL 50 GOTO END
GOTO TOP
:PICKUP
ghost
scorpion
UUCICO  -V -k4096 -x0 -t60 -r3 -ga -s netcomsv
modem /P4 /B57600 /SATH1M0S0=0
scorpion
ghost
GOTO TOP
:MIDNIGHT
del import.log
cd\osiris
EXPORT /O /A1.296.5.0
viper /E
cat
ulink
ftpmail
list
mail_s
snews
news_s
scorpion
boot
:UUCP
ghost
scorpion
mail_s
list
ftpmail
scorpion
goto TOP
:PICKUP2
ghost
mail_s
ftpmail
scorpion
snews
UUCICO  -V -k4096 -x0 -t60 -r1 -s netcomsv
modem /P4 /B57600 /SATH1M0S0=0
viper
scorpion
ghost
list
snews
scorpion
GOTO TOP
:END

(H227)
Osiris requires ONE environment variable, OSIRIS=DRIVE:\PATH
DRIVE: is the DRIVE letter and \PATH is the FULL path to the
directory.

OSIRIS= should point to the directory that contains the Osiris
system files (user records, message board definitions, file area
definitions, etc.).

There is a SECOND environment variable that is also required
PROVIDING you have your serial port locked, E.G.COMx=LOCKRATE

x is replace with the serial port number and LOCKRATE is replaced
with the serial lock rate.

COM1=19200
COM1=38400
COM2=57600

(H228)
It is possible that you MAY have the OSIRIS= set in your
environment but Osiris cannot find it. This is generally caused by
an OVERLOADED PATH= statement. DOS acts VERY strange when you
overload the PATH.

I'm not sure, at least I can't find any technical specifications
on it, just how long your PATH= line can be but if you experience
this problem, start removing DIRECTORIES from the PATH= line.

(H229)
It is possible that you MAY have the OSIRIS= set in your
environment but Osiris cannot find it. This is generally caused by
an OVERLOADED PATH= statement. DOS acts VERY strange when you
overload the PATH.

I'm not sure, at least I can't find any technical specifications
on it, just how long your PATH= line can be but if you experience
this problem, start removing DIRECTORIES from the PATH= line.

(H230)
If the key word FAX appears in any connect message, Osiris calls
up FAX<node>.BAT to handle the incoming fax call.

Assuming an incoming FAX is received on NODE 1, Osiris would call
up FAX1.BAT. If the FAX is on NODE 4, Osiris would call up
FAX4.BAT.

The contents of FAX<node>.BAT, entirely up to you.

(H231)
Any fossil driver will work. See documentation that comes with the
fossil driver for details.

Add

COMDRV=FOSSIL

to your AUTOEXEC.BAT and reboot the computer. You must use UPPER
case, no spaces, and you must reboot the computer before this
takes effect.
(H232)
If you don't already know what MATRIX mail is, you should skip
this section. You don't need additional software to run MATRIX
mail on your system other than a mailer.

Osiris supports your mailers matrix message area and gives your
callers the ability to send and receive matrix mail. The TYPE or
BRAND of mailer isn't important as long as it saves the matrix
messages in Fidonet .MSG format.  The .MSG format offers full
ZONE, NET, NODE, and POINT addressing. If your mailer does not
support the Fidonet ZONE field, it cannot be use. For instances,
Frontdoor 2.02 does not FULLY support the Fidonet .MSG format and
can only be used to SEND mail. It does not properly implement the
ZONE fields when RECEIVING mail.

Before you can install the matrix mail option, you need to have
InterBBS configured on your system. The Matrix mail module uses
the InterBBS configuration file to obtain the path to your mailers
matrix area and it also uses the MATRIX mail addresses you defined
in the InterBBS configuration file. This keeps the matrix mail
option fairly generic to the TYPE of mailer software you are
using.

If you have InterBBS install, select the NODE option  in SM and
fill out the  Matrix Cost, Crash Access, and POINT number fields.

You can also create a TEXT file called FREEBIE in your OSIRIS=
directory.

If the message is addressed to one of the systems listed in the
FREEBIE file, you will not be charged for sending the message.

The FREEBIE file contains one 4-D domain address per line in the
format of ZONE.NET.NODE.POINT

Pay special attention to the subdomain separator. Use a PERIOD to
separate the different subdomains and NOT : and  /

The final step is to pick-out a slot on one of your command
records and select the NETMAIL option. You will find the NETMAIL
option under GENERAL.

                             Nodelist

We decided against using any type of NODELIST because we'd have to
use one of our OWN due to the DIFFERENT formats in-use by mailers.
Nodelists already take up so much disk space, the thought of
burdening you with an another one was unthinkable. We'll let your
mailer handle orphaning any message that cannot or does not have a
valid address.

                          Access Levels

Unlike other MESSAGE type modules in Osiris, the READ/ENTER/REPLY,
etc. have no access levels. You cannot enter a message unless it
is a FREEBIE or you have enough matrix credit to send it. You can
only read and reply to messages addressed to you.

                          Multiple Nodes

Unlike other message systems found in Osiris XLT, the netmail
system is not MULTINODE because the Fidonet .MSG format itself is
not multinode.

That does NOT mean that you cannot use the Netmail option on a
multiline system, you can. However, Osiris will only give ONE node
at a time access to your mailers matrix area. If someone on NODE 2
is entering or reading matrix mail and someone on NODE 1 tries to
access the matrix area they will get a message telling them that
someone else is using netmail and to try later.

(H233)
International TeleCommunications has been producing Fidonet
echomail programs since Echomail was first developed.

Due to our years of experience with Fidonet, InterBBS is the
fastest, most reliable, and most bug free set of echomail programs
you're likely to find.

InterBBS is a TWO phase Conference mail processor. It  imports and
dup checks on one pass and then exports on the 2nd  pass. InterBBS
uses two programs to do this, Import and Export.

By  using a TWO phase processor we take advantage of  loading
data   into  memory only twice. We avoid the  pit  falls   of
SINGLE phase  processors, Qmail and QuickBBS, by avoiding the
creation    of   FRAGMENTED  outbound   bundles.   Fragmented
bundles increase  import  time  for those receiving  echomail
from you.

InterBBS is about as bullet proof to errors as we could possible
make it.  It was setup or designed to prevents such things as
defining multiple COMPRESSION formats for the same system, using
an ECHO TAG name more than once, defining the same AREA more than
once, sending the same area out within the SAME zone using more
than one address, failing to STRIP seen by and path lines when you
scan an area to multiple zones and failing to Strip SEEN BY and
PATH lines when dealing with POINTS.

InterBBS takes the GUESS work out of doing ECHOMAIL correctly.

The InterBBS programs can be found in the archive INTERBBS.ZIP.

Move Export.exe, Import.exe, and ICS.EXE to your Osiris= Directory
and run the program ICS.EXE.
(H234)
Any Fidonet Echomail area you define must be within the
FIRST 1000 message areas. You cannot define and use
message area 1020, 3000, 4041, etc. as Fidonet Echomail
areas.

(H235)
ICS.EXE is the InterBBS Control System and you use it to setup and
maintain your echomail control files.

The FIRST time you run ICS, select the 3rd option on the screen,
the one labeled "Import & Export Configuration".

           Import & Export Configuration

This is where you define your subdirectories, echomail addresses,
and other items.

The configuration sections consists of two screens and you must
fill out almost all of the fields.

               Matrix Addresses

You have 10 boxes at the top of the first screen. These boxes hold
your ECHOMAIL matrix addresses and Import uses those addresses to
determine if an echomail bundle belongs to you.

You MUST define at least one matrix address, the remaining nine
are optional.

                 Archive Dir.

I'll store  all outbound ARCHIVED bundles in   this   directory.
Useful if you are low on disk space  and  wish to split  things
between two drives.

                Mailer Msg Dir

I'll place  the  MSG file attach   messages   in    this
directory.

               Pkt Temp Storage

I'll  place  the  unarchived  PKT  files  in   this   directory
until it is time to move them  into  the  archive.

Useful  if your disk space is a little on  the  low  side. You
might want to store  the PKT files on one  drive  but  when it
comes time to   archive   them,  archived to a different drive.

             Mailer Inbound Dir.

Points IMPORT to your INBOUND file area. Import will LOOK in this
directory for any incoming ECHOMAIL.

               Dup.dat Storage

Tells  me  which directory  the   DUPxx.DAT   files   will   be
stored.  Useful if you  need  to   spread  things across two or
three drives. e.g.   DUP.DAT STORAGE c:\dups Export    takes
messages  out  of  your    conference   message area  and moves
them into archive bundles  ready  to be  mailed out to other
systems.

                 Use EMS Cache

Import has its own internal EMS/LIM 4.00 cache that  is  hundreds
of  times more  effective  than  your  traditional disk cache.

I  have  the advantage of knowing in  advance  what  data  is
likely to be needed again and  I'll  only  cache that data. I'll
ignore data that isn't  going  to  be needed again. This accounts
for  its  higher  than normal hit ratio, generally around 90
percent. Since I know what should or should not be cached, I  can
bypass the system read/write requests  and  go  directly to the
cache. This allows your normal disk  cache,  if  you  are running
one,  to  retain  data  longer than it normally would.

The import EM cache is an expandable cache.  Unlike  traditional
caches,  I'll expand the size  of  the  cache  when  I need more
space. I'll start  with  0  bytes  and expand the cache up to 4
million  bytes.  If  no space is available, I'll use a  "LESS
USED"  algorithm to determine which block to replace  with  the
new data.

                Cache Statistics

At the end of an import run, I'll display  the  EM  cache
statistics; Memory used  for  cache,  number  of  read  requests,
number  of  write  requests,  number  of  reads  actually   done,
number of writes actually done, read hit rate,  and write hit
rate.

The  number of read and write requests do  not  reflect  ALL
read/write requests.  They  only  reflect  read/write requests for
data I  would  normally cache. I ignored read/write  requests  for
data I would not normally cache.

If you want IMPORT to use the EMS cache, set this field to YES.
BUT, before you do, set the MAXIMUM CACHE Size.

                Maximum Cache Size

You need to tell Import HOW many blocks of memory you have
available for the CACHE. Just CLICK on this field and ICS will
calculate the maximum cache size for you.

The larger the cache, the faster the system will run. The Optimal
size is 200, 3.3 Meg.

If you come up with a MINUS cache size, e.g. -1, -2, etc. then you
cannot engage the EMS caching system.

              Ems Handles, Very Important

In  order for import to use an EXPANDABLE,  on  demand  cache,
each block uses 1  EMM  Handle.

Almost all memory  managers  have  a  default of  32  or  64  EMM
handles,  but  do allow you  to  increase  the  number  of  EMM
Handles with  a  command  line  switch. QEMM uses HANDLES=, AST
uses PID=  and  CONTEXT=. Check the manual that came with your
memory   manager   for  the   correct   switch  settings.

                     Maximum Systems

This tells EXPORT how many individual  systems  your config.sys is
setup to support  during a single export  run.  See section on
EXPORT.EXE for further details.

To set this field, click on it and ICS will calculate the maximum
number of systems.

                   Use Send Direct Flag

This tells Export that you're using Phoenix and you want the file
attached Echomail bundles flagged as DIRECT.

           Use Phoenix Echomail ID Flag

This tells export that you're using Phoenix and you want the
Echomail ID Flag used. This flag tells Phoenix the attach is
echomail. This isn't required, but it does speed up processing a
little bit.

                       Point Net

Define  a POINT net address. When exporting, I'll  take  this
address  and strip it from the  CURRENT  seen  by lines. See the
section on POINT NETS for further details.

After you complete the Import & Export Configuration section,
you'll want to define your areas and the systems that you will be
getting or sending those areas from or to.

Select the first option, System and Area Control Files.

             System And Area Control Files

The main screen in this sections is made up of 3 columns. Each
column has room for 21 systems for a total of 63 systems. That is
the maximum number of systems that you can send an area TO.

The systems that get the current area will show in in these
columns. The address will be displayed as ZONE:net/node.

At the TOP of the screen, two fields. One is the Area No and the
other is Area Name. This is the OSIRIS XLT area No and the OSIRIS
XLT area name.

The FIRST time you select this section, the top two fields will be
BLANK. Add your first area and THEN change into that area. This is
VERY important and you MUST not skip it.

Along the RIGHT side of the screen are two different groups of
controls, System Controls and Area Controls.

                  System Controls

These deal with the systems getting the area.

                        Add

Lets you add a system to the area. This option will not let you
add someone who more than once.

When you select this option, ICS will ask for the zone, net, and
node number.

If the system does NOT have a record, you'll be asked to supply
the archive type, file attach message attribute, Areafix password,
Packet Password and the system's access level (used by the Areafix
section of ICS).

If you do not know what Areafix password that system wants to use,
just press ENTER. This will allow the system to access areafix
without a password. Areafix passwords can be a maximum of 8
characters long and CASE is not important.

If you do not know what PACKET password that system wants to use,
just press ENTER.  A PACKET password can be a maximum of 7
characters long and CASE is not important.

The systems access level governs WHICH areas he has access to. His
SYSTEM access level must be equal to or greater than the AREA'S
access level.
                         Del

Deletes the TAGGED systems from this area. It does NOT remove a
systems record.
                         Edit

Edit the TAGGED systems system record (Archive Type, Message
Attribute, Password, and Access Level).


                         View

View a Tagged systems Archive Type, Message Attribute, Password,
and access level.

                         Pack

Remove system records that do NOT get ANY echo areas from you.
Maybe they were only getting one and you removed them from that
area.

                      Area Controls

These controls deal with defining and maintaining Echo Area
definition records.

                          Add

Lets you ADD a new Area. A scroll menu will open listing your
Osiris message areas. Move to the one you want to add and click on
it. Full error trapping to prevent it from being defined more than
once (cross linking can happen if you do).

You'll also be asked to supply the ECHO TAG name (the one that
echomail uses to ID the area). Again, full error trapping is
engaged to keep you from defining the same ECHO TAG more than
once.

You will then be asked to supply the access level required to get
this area. If a  system does not have a SYSTEM access level
greater than or equal to this access level, they will not see nor
can they ADD the area. This field is used by the Areafix section
of ICS.

The last thing you'll be asked to enter is an AREAFIX Area
Description. When someone does an Areafix %LIST request for all
available areas, ICS will list the ECHO TAG name followed by this
field. It should briefly outline what TOPICS the area covers.

                         DEL

 Delete an area. System records are automatically updated.

                         Chng

Change to a different Message Area.

                         Edit

Edit the current message area definition. You can change the Echo
Tag or the area's access level.

                         View

View the current areas ECHO TAG name and Access Level.

                         EXIT

Exit back to the MAIN menu.

Several functions work on TAGGED system addresses. To tag a
system, move to it and click the left mouse button. To Untag,
repeat.

                Echo Notification System

This notifies the sysops the areas they are feeding or picking up
from your system.

                 Incoming Traffic Report

Generates a report, TRAFFIC.DAT, telling you who is sending what
to what areas and how much.

The report is broken down by individual SYSTEMS with a summary
listing the traffic for all systems.

(H236)
Export    takes    messages  out  of  your    conference   message
area  and moves them into archive bundles  ready  to be  mailed
out to other systems. .lm20

Export {/BZONE.NET.NODE.POINT *L *U /O} {/F /M /P /R} /AZONE.NET.NODE.POINT

Items inside the curly brackets are optional, /A is required.

To reduce code overhead, we use a period to separate
zone,net,node, and point.

/R  . . . REMOVE all Un-moved echo flags.

/F  . . . Don't reset  high-water  markers   nor   mark  messages
as scanned out.

/M  . . . Maximum  number of messages to  export  during   the
run.  Default  is  32700 but can  be  changed  with   this
switch.

/A  . . . You address in 4-D format. Each Subdomain should be
separated by a PERIOD

/O  . . . Use  old  style conference  mail  naming.  Some    Older
echo processors use a restricted echomail  naming  system.

If  you're  sending  echomail to one of  these  systems,   not
likely, then you may need to use this.

/P  . . . During a normal export, export.exe will not export to
any system that has a net address equal to your POINT net address.
To EXPORT to your point net, include /P on the export command
line. Export.exe with then export only to those systems in your
POINT net. Also requires the use of /B. See section dealing with
POINTS for details.

/? . . . Help

                     Config.sys

Export  is VERY fast, compared to  other  echo  processors.    To
obtain some  of this  speed,  I had to design special file
routines.

Because  of the  way they work,  once I use  a  file  handle,  it
cannot be freed back  to the  POOL  for   reuse  until  the
program   ends.    This  means   you    have  maximum  number  of
DIFFERENT  Nodes you can  send  to  during   a  single  run.

This   can   be  varied  by   a   setting   in  InterBBS.ctl,
MAXIMUM SYSTEMS.

To increase   the  maximum  number  of   systems,   you   must
increase  your  files=#  For  20  systems,  your  FILES=  should
be  set  to FILES=34. This   may  vary depending  on  your
hardware  setup.  After you change config.sys, reboot the computer
and use ICS to boost the maximum system settings.

                     Import.log

Export  will use, if it is available,  a  file  called
"IMPORT.LOG", created by import.exe, to  control which areas it
exports from.

This can get you into trouble if you happen to  use the /F and /R
switches.

Since /R sets ALL "I NEED EXPORTING FLAGS"  to  OFF,  if you had
messages in areas not  listed  in  the import.log file, those
messages  will  not be exported.

If you are using the /R and /F switches, place  "DEL IMPORT.LOG"
in the batch file BEFORE  you  run export. This  can  increase
your  export  time,   but  guarantees   that   ALL  messages
will   get  exported. Again, If you use  /R or /F, delete the
import  log file before exporting.

(H237)
Although export does support file locking, there are other
concerns when exporting WHILE callers are on-line.

When you export using multiple address, you run the risk of having
someone POST a message AFTER the first pass, but before the second
pass. Their message will go out in the files created during the
second pass, but not the  first.

The solution to this type of problem is to divert any conference
messages that may be posted while you are exporting to the REV
holding area, even if you have NOT defined the area as REV.

If you are going to export WHILE callers are on-line AND you are
using more than one address, you'll need to call export with the
command line switch *L BEFORE you begin the export process.

E.g., EXPORT *L
      EXPORT ....Your FIRST run.

This engages a conference system DIVERSION LOCK and causes all
newly posted conference messages to be diverted to the REV holding
area.

There WILL be a 5 second pause before export EXITS when you use
the *L switch, to give all lines time to respond to the LOCK.

After you have finished exporting, you call export with the
command line *U.

E.g., EXPORT *L
      EXPORT ....Your FIRST run.
      EXPORT ....Your SECOND run.
      EXPORT *U

*U will DISENGAGE the conference system DIVERSION LOCK and newly
posted messages will be posted according to the area type.

You should periodically check and move any messages that are
diverted to the REV hold area.

(H238)
Import   takes    messages   out  of  archive    bundles
and  tosses  them  into  the   various  echomail  areas. Import
does NOT require any command line switches.   It   gets all  its
information from InterBBS.cfg.

Import  supports   EIGHT archiving  formats: UC2, SQZ,   normal
ARC,  PKARC, PKZIP format, LHARC, ARJ, and finally, ZOO. Nothing
needs to be done on your part except to have the following
programs in your OSIRIS= directory or in a PATH directory:

           PKXARC.EXE (renamed from PKUNPAK)
                      PKUNZIP.EXE
                        ZOO.EXE
                       LHARC.EXE
                        ARJ.EXE
                        SQZ.EXE
                         UC.EXE
                          ARCA

If   all  attempts to  unbundle the  archive  fail,    I  will
assume the bundle is bad. If that happens, I  will  rename the
bundle to HHMMSSXX.BAD and leave it for  your  personal attention.

Import supports one OPTIONAL command line switch, /N. This disable
the SECURE ECHOMAIL option in IMPORT. You might have to do this if
the person you are doing ECHOMAIL with does not support ZONE
addressing in ECHOMAIL packets. .lm20

                       Dups

Import   checks the newly arrived  messages to  see   if
you've already  seen them. It does  this BEFORE  you  import the
message which should save a  little  disk fragmentation. Import
uses  an EID duplicate   checking   system.  It's    the   most
reliable method to   date   for   controlling duplicates.

Import   will track the last 2000 messages in  each  area   with a
fixed dupXX.dat file size. The  file  will  never grow  nor shrink
so the file will  stay   contingent on your hard drive.

                      Backup System

Import has TWO backup systems in case an EID is not in the
message. If an EID wasn't found, Import will look for a MSGID.
While the MSGID isn't nearly as effective as the EID, it is better
than the third method, CRC. If Import couldn't find an EID or a
MSGID, Import will fall all the way back to the old fashion CRC
system for messages.

I'm not going to waste time monitor disk space and I'm  going  to
just assumes  you've  got enough  to get  the  job  done.  If  you
run out, InterBBS  is   as  good   a   place as any to Stop. If
you're out, nothing  else   on  your system is going to run. I
will not even be able to  write an error log so . . .

                   Seen By Lines

InterBBS supports FULL seen by lines in or out as well as
sub-sets.  I'll not tamper with existing seen  by  lines
except    to  remove  any  point  net  listings   you've
defined.  I'll automatically remove any NET ZERO ie. 0/9   or
0/0 entries as non-valid. Quad Already Seen System I   use a
QUAD Already Seen it system  instead  of   the  traditional
single phase seen by line  approach.  Which  means  import is 4
times more  accurate  when it  comes   to   stopping  duplicate traffic
than  Confmail  4.0  or  Qmail.

This  makes InterBBS, combined with the  FILTER  options,  the
blazing  speed, and the EID dup checking  the  best  Echomail
processor you could possible run.

(H239)
You'll  find, in each message area, a  place  to define   an
ORIGIN  line for the area.

You  use  an  ORIGIN  line to  show  WHERE  the  message
originated. You should place the NAME of your BBS,  City  and
State,   and the PHONE number, providing  there  is  room, in the
origin line.

e.g.

VetLink #3, Cape Girardeau, Mo. (314 334-6359)

(H240)
Areafix  allows remote systems to add, remove, list all areas and
list areas they have selected to receive echomail from.

To activate Areafix, use -A when calling ICS.

E.g. ICS -A

                 Areafix Commands

                    %LIST

List Areas You have Selected And Areas You have Access To.

                 +<AreaName>

Add <AreaName> To Your List

                  -<AreaName>

Remove <AreaName> From Your List

              %COMPRESSION <Type>

Change The Archive Used To Compress Your Echomail To <Type>. Valid
<TYPES> Are ZIP, LZH, ARJ, SQZ, ARC, and UC2.

                    %RESCAN

Rescan Areas you have selected. Osiris Msg Areas MAY contain as
many as 32,766 msgs PER area. This can result in LARGE Echomail
bundles. To conserve disk space, the MAXIMUM packet size will
automatically default to 500 messages. When this limit has been
reached, the packet will be compressed and export continue. This
process is repeated until all messages have be scanned out.

You can disable RESCAN by including /NR on the command line. It
MUST come before the -A switch.

E.g. ICS /NR /A

               %Password <Password>

Change your Areafix password to <Password>. <Password> must be 8
characters or less.

                    %PKTPWD

Change your PACKET LEVEL password to <Password>. <Password> must
be 7 characters or less.

                     %HELP

Get a list of all the commands ICS/AREAFIX supports.

Example of an Areafix message.

FROM: John Doe, 1:296/5.0
TO  : Areafix, 1:296/6.0
SUBJ: <PASSWORD>
-----------------------------
+SYSOP
-GENERAL
%LIST
%COMPRESSION ZIP
%PASSWORD ROLODEX
%RESCAN

              Issuing an Areafix Request

The System operator   enters  a  message  and  addresses  it  to
"Areafix" and his PASSWORD on the Subject line.

The System operator enters his requests one per line,  case not
important, in the BODY of the message.

                  Preventing REMOVE

You can disable the REMOVE option by including /N.

E.g. ICS /N /A

It MUST come before /A.

You might want to disable the REMOVE option to prevent systems
from calling in towards the end  of the month and removing
themselves from echo areas.

They might do this to get around any type of SHARED billing
system.

(H241)
To avoid problems and there are plenty of folks out there that
will do their level best to cause you plenty of them, follow these
basic rules concerning ECHOMAIL.

1.  ALWAYS use SESSION level passwords with ANY system you do
Echomail with.

2. ALWAYS use a mailer that has SECURE ECHOMAIL, like Phoenix.

3. ALWAYS use PACKET level passwords. A system's PACKET level
password, SESSION level password and AREAFIX password should be
different. Do not use the same password for multiple fields. If a
system cannot do PACKET level passwords, do NOT do echomail with
him.

You might ask why is this so important and the answer is ECHOMAIL
HACKERS.

It use to be that one needed to be a REAL Hacker to cause problems
but not any more. People are now actually releasing programs that
allow ANYONE to hack into an echomail system that isn't protected.

Below is the documentation from one of those programs.

(NOTE: We at ITC use the TERM SECURE ECHOMAIL in our PHOENIX
mailer. It is the same thing as SECURE INBOUND.)

   ======= BOGUS PACKET EDITOR DOCUMENTATION =======

                PURPOSE OF THIS PROGRAM:

Bogus packet editor is a mail processing utility designed for your
cross linking pleasure. It will take any mail packet (that meets
fidonet standards) and change: 1) The tear line, 2) The seen-bys,
3) The origin lines, 4) The path statement, 5) The originating and
des-tination node, 6) The "To:" field, 7) The "From" Field, to
anything you desire. In addition it will change around the flags
and packet packer code, all within Fidonet guidelines.

                     HOW IT WORKS:

First off a bit about how mail processors work. When a mail packet
comes into a BBS inbound directory the mail processor unpacks it
and tosses it in the proper area and sends it to any downlinks
, other BBSes, in its Area.bbs. The mail processor really does not
care who it gets it's mail from rather it looks at the Onode
, originating node, in the packet header (or if the processor is
running in the unsecure mode it does not care who it gets it's
mail from). The implications of this are very interesting. It
means it is very easy to get around basic fidonet security to send
anything you want in to any echo you want.  Example: I know that
1:13:13 gets its mail from 1:106/116. I also know that 1:13/13 and
1:106/116 are session level pass-worded.

Therefore I use Bogus Packet Editor to make the Onode 1:106/116
and the Dnode 1:13/13, I pick a echo that I know they exchange to
hack into. I then configure my mailer for a third system say
1:315/1 (a system I think that they would have no reason to be
passworded with) and send the mail to 1:13/13 as this node.
1:13/13 gets the packet in it's inbound directory and it's mail
processor "looks: at the Onode of 1:106/116 and goes ahead and
tosses it (unless the system has packet level passwords or secure
inbound, more on that latter). You bundle of bogus mail gets
tossed into the echo(s) in question.

When Bogus Packet Editor is used this way, session level passwords
do not even slow it down. However protected inbounds and packet
level pass-words are a problem. However, Front Door does not have
protected inbounds and many mailers do not have the ablity to do
packet level passwords (most noteably I-Mail). So find a system
that runs both Max, Wildcat, Quick or SuperBBS and runs FD or DB
and you know this person can not stop you.

In any case very few people use packet level passwords, they
mistakeingly believe that a system is protected using session
level password protection. This belief will change. Always
remember that a net is only as secure as it's weakest link. In
other words, used properly this program can not be stopped. Myself
and my beta testors have proved that time and time again.

To operate make your changes to BBP.CFG as fits the situation and
type BPP BPP.CFG, that is all there is to it.

                          End.

========================================================

A combination of InterBBS and Phoenix will stop bogus and other
applications like Bogus dead in its tracks.

(H242)
I'm not going to explain WHAT points are because that is not
within the scope of this document. If you don't know what they
are, then skip this section.

There are a number of ways one can deal with POINTS and echomail
but there is only one method that will work with any echomail
processor.

That method also happens to be the one Fidonet recommends. We will
further assume that your MAILER supports 4-D addressing.

Again I want to point out that there are a number of DIFFERENT
methods you COULD use to handle this but they are PROGRAM
specific. They would work with SOME echomail processors, but not
with others. This method works with EVERYTHING. So if the
APPLICATION you WERE using, prior to installing Osiris XLT,
handled things different that doesn't mean BRAND-X was doing it
WRONG, only different.

First you have to setup a "FAKE NET" or "POINT NET". The NET
number is up to you but be sure you pick one that isn't used by
FIDONET, ITCnet, WORLDNET, or whatever network you belong to.

You will be the EC of the POINT net and your NODE number will be
0.

Lets assume your Fidonet address is 1:296/5.0 and you pick the
POINT NET number of 5000. You're POINT NET address would be
1:5000/0.0.

You would start assigning POINT addresses to your point systems
beginning with 1.

E.g. 5000/1, 5000/2, 5000/4, etc.

Your POINT net systems would ONLY use that address for ECHOMAIL
purposes. Their MATRIX MAIL addresses would be 1:296/5.1,
1:296/5.2, 1:296/5.3, etc.

RUN ICS and select the SYSTEM AND AREA CONTROL FILES option then
add the POINT net addresses to to the AREAS you are going to
export to them. Again, use the POINT NET ADDRESS and not the
MATRIX addresses.

Next select the IMPORT & EXPORT configuration option, ICS. Go to
the second page and enter the POINT "NET"  address in the slot
labeled POINT NET. If your POINT net is 5000, then you would enter
5000.

When exporting ECHOMAIL, you will need to run EXPORT three times,
first for the REGULAR systems and then for the POINTs. The final
run is a CLEAN UP run and you don't actually EXPORT anything, you
just CLEAN up areas that you had listed for the REGULAR systems
but do not SEND to the POINT systems.

During the first pass, Export will not export to any system that
has a NET address equal to the POINT NET address you defined with
ICS.

E.g.

Export /O /A1.296.5.0 /F

Notice the /F, this must be included.

During the second pass you would change the /A address to your
POINT NET address and include /P and /B on the Export command
line. /P tells export to export only to your POINT net. /B gives
your regular FIDONET address.

Assuming POINT NET 5000

Export /O /P /A1.5000.0.0 /B1.296.5.0

The third and finally run consists of a single command line
switch, /R

E.g. EXPORT /R

We want to make sure we CLEAN up any LOOSE echo flags in areas.
This is a SAFETY run to prevent the possibility of DUPLICATES and
should never be skipped.

Example of a complete RUN.

Export /O /A1.296.5.0 /F
Export /O /P /A1.5000.0.0 /B1.296.5.0
Export /R

The ECHOMAIL FILE ATTACH messages to your POINTS would be
addressed as coming FROM 1.296.5.0 and going to the 4-D matrix
address. E.g. 1.296.5.1, 1.296.5.2, etc.

(H243)
Interzone echomail references sending the same area to multiple
zones.

You have to make multiple passes with Export to send to different
zones. You /A address would be the one you use for that zone.

Example:

Export /A1.296.5.0 /F
Export /A62.500.0.0
Export /R

Export will automatically take care of stripping SEEN BY and PATH
lines in messages going to multiple ZONES.

(H244)
OSIRIS is actually easy to set up in terms of echomail processing
for FIDO type systems. The first step is to sit down and write
out all the ECHO areas you want to use. Using a piece of paper,
write down the EXACT AREA TAG as listed in the FIDO.NA or other
network list of ECHOS. This is important in making sure the Zones
will work out for you.

Once you have an idea of the echo areas, you must set then up in
SM. Next, on this paper, make a second column of the name you
will use on the BBS to name the ECHO area in the first column. In
SM can match the AREA TAG if you like. Using SM, define all
the ECHO areas you wish to carry. In SM MSGBOARD.BBS area,
make sure to list them as ECHO/REV. This will save many headaches
later in flames from other Sysops.

For example: You wish to carry ECHOS DBRIDGE, FRODO, PHOENIX. You
can use more descriptive names in SM for the BBS, such as
D'Bridge mailer ECHO, etc. Next column you need to label your
Uplink, who you get the mail from, and who you send your replies
to.

DBRIDGE         D'Bridge mailer ECHO    1.289.13.0
FRODO           Front Door mailer ECHO  1.289.13.0
PHOENIX         Phoenix mailer ECHO     1.296.5.0

Once you have these listed out, and in place in SM, you are ready
for the next step.

With ICS, Import and Export in your OSIRIS= subdirectory, run ICS.

Under configuration, you need to fill in the blanks for incoming
ECHO bundles to make sure they are handled properly. Fill in your
Matrix addresses that you will use for ECHO bundle importing. You
don't have to put in administrative numbers that will not import
mail.

For example, in ADANET I have 94.109.0.0, 94.109.1.0, 94.109.2.0
as valid addresses! Only Node 1 imports and exports ECHOS, so
ONLY place that address in ICS: 94:109/1.

Fill in other Zone addresses you might have, then fill in the
other slots. The inbound directory for files must match your
Phoenix inbound directory. You will also make the matrix
directory the same as you have in Phoenix. The Archive directory
can be anywhere you like, and the same for PKT storage temp
directory. On Page 2 of configuration, set up a dupe storage
subdirectory, and then click on EMS cache until it says YES, and
then click on the size, and it will detrmine the appropriate size.
Click on Max systems, DIRECT FLAG to YES, Phoenix ID to YES, and
put in a FAKE point net only if you will run POINT systems off
your system.

Next, with your List of ECHOS in hand, go to the System and Area
Control Files. This gets to the meat of setting up the ECHOS for
mail flow. For each ECHO on your list, you will need to ADD an
area from the bottom panel of buttons. When you add an area, you
can pick it from the pop up list ICS gives you of your SM areas,
then you will need to fill in the AREA TAG exactly as listed in
column 1 of your list. Next are items like area security levels,
and a more detailed description for AREAFIX users.

Add all your ECHO areas this way. When this is complete, next go
to the first area you have defined by using CHANGE. Next you add
systems to the ECHO areas you have defined. You will need to use
the TOP panel of buttons to add your Uplinks and Downlinks to the
areas. This is cumbersome if you have a LOT of ECHO areas, but
once set up it is easy to change. For the first entry, add your
Uplink, that is who you pick the ECHO up from, and who you return
replies to.

Once you add the number of the system, you will need to define
the type of priority, Hold, Normal or Crash, and the Archive type,
and two types of security. First, the AREAFIX password, then the
Security Level of this system, and then a packet level password.
If you are new to ECHOS, leave the PACKET LEVEL PASSWORD BLANK.

Go through each ECHO area this system will be added to by using
the CHANGE button, and fill in all the areas this system will get.
The next time you add this system, you will not have to fill in
the AREAFIX passwords, etc.

After this system is added, add each other system you will FEED
for mail.

When this is all done, an excellent way to check the function of
your setup is to run ECHO Notifier from ICS. Enter your Zone
address and you will generate an e-mail message for each system
listed in ICS and it will include each ECHO that system is linked
to. You can read these e-mail messages from PED in Phoenix.

This is the bulk of setting up the system. Next, you will need to
make the actual importing and exporting happen. This will send
you back to PHOENIX. You will need a file called ECHOMAIL.BAT to
import your ECHO bundles.

Since I run PHOENIX and XLT in different subdirectories, I need
to change to the XLT sub.

CD\XLT
IMPORT
IF ERRORLEVEL 1 GOTO END
IF NOT EXIST F:\XLT\IMPORT.LOG GOTO END
ULINK
DEL F:\XLT\IMPORT.LOG
CD\PHOENIX
:END
EXIT

This is what I use to Import. I export only in the midnight
Event, since this takes a lot of time. In my Phoenix.Bat file, I
run a section of the midnight event for exporting. Exporting can
be a bit trickier than importing!

:TOP
PHOENIX
IF ERRORLEVEL 50 GOTO MIDNIGHT
.....


:MIDNIGHT
CD\XLT
AMA /L /R <frees my messages for regular users, like myself>
DEL IMPORT.LOG <just to be sure>
EXPORT /A1.289.8.0
GOTO TOP

This is the most basic. You have 1 Zone for mail, and that's it.
Well, the world is more complicated for some of us. There may be
multi-lines, and there may be many Zones.

MIDNIGHT:
CD\XLT
AMA /L /R
DEL IMPORT.LOG
EXPORT *L <diversion lock for multiple nodes>
EXPORT /F /A1.289.8.0
EXPORT /F /A94.109.1.0
EXPORT /F /A369.1000.0.0
EXPORT /R
EXPORT *U <turns diversion lock off>
GOTO TOP

Note this: You MUST run Export for EACH ZONE you export. Under /A
you use YOUR matrix address (same as in ICS and Phoenix).

Note the /F above. This is CRITICAL!!!! When you run Export once,
it turns OFF all the ECHO flags. If you leave off the /F, the
second and third pass through no more ECHOS will be exported.
NONE of Zone 94 or 369 would go out, period! /F tells Export NOT
to mess with the ECHO flags, and then /R at the last line turns
them all off. If you don't use /R, you will export the SAME
ECHOS on your next run through export.

This is also why I choose to run Export as a midnight event. I
have SEVEN zones, so I have to run Export EIGHT times (once with
/R, right). If you have a lot of ECHOS, this may take awhile.
Also, with only one run, your Export bundles will be larger, less
fragmented, and easier for your downlinks to unpack.

Other pointers: in Phoenix, make sure you have added all your
Matrix addresses. Three fit in Config, and the rest can be added
to a text file called PHOENIX.AKA in your Phoenix subdirectory.

Make sure you have ECHO processing ON in Phoenix, so ECHOmail.Bat
will run when mail is received.

For starters, in Phoenix turn OFF the Secure Address and ECHO
features. You can add them later, but you will probably lose mail
at one time. It goes into a black hole, and is gone for good.

If you have any questions past this, make sure you Netmail me
your questions, and I will try to answer them. Use the XLT.DOC
and PHOENIX.DOC files for reference in setting up the ECHOS.

If you need a test ECHO system, we can arrange that here, too.
I'm sure other sites will be happy to help with OSIRIS XLT and
Phoenix, and as they make themselves known, I will add them to
this text file.

Thanks!


(H245)
If you want to set up a PRIVATE BBS, then set the default new user
access level to zero. If the default new user access level is
zero, no new callers will be allowed to log-in. A text file
called  "PRIVATE.MMU," if it exists, will  be  displayed.

PRIVATE.MMU must be located in the OSIRIS directory.

(H246)
Ultralink is an OSIRIS XLT conversion linker that links messages
that did not originate on your system.

The MAXIMUM number of message I can link in any given area is
5000.

Ultralink looks small and doesn't require much memory when it
first starts, 80K, but it can quickly consume a large chunk of
memory. It can require as much as 512K on areas that push it close
to the 5000 message limit.

You should run Ultralink directly AFTER import.exe and but BEFORE
export.

(H247)
   Key Combination   Desired Effect     Key Combination   Desired Effect

   ^E or Up Arrow  = Cursor up          ^W, ^QS or Home = Goto begin of line
   ^X or Dn Arrow  = Cursor down        ^P, ^QD or End  = Goto end of line
   ^S or L-Arrow   = Cursor left        ^A  or ^L-Arrow = Cursor word left
   ^D or R-Arrow   = Cursor right       ^F  or ^R-Arrow = Cursor word right
   ^C or PgDn      = Page down          ^R  or PgUp     = Page up
   ^H or Backspace = Backspace          ^U, or ^KD      = Exit/Done
   ^I or TAB       = 10 spaces          ^B              = Reformat paragraph
   ^L or ^KR       = Re-draw screen     ^Y  or ^KY      = Delete the line
   ^G  or Del      = Delete character   ^M  or Enter    = New line
   ^KX or ^QY      = Del to end of line ^N              = Split line
   ^V  or Ins      = Toggle Insert Mode ^Z              = Help
   ^Qc or ^End     = Goto Bottom        ^Qr or ^Home    = Goto Top
   ^Ki             = Insert Line

EXAMPLE: ^N  = Hold down CTRL & press N
         ^QY = Hold down CTRL & press Q. Release CTRL & Q then press Y

Insert Mode is OFF by default. When you toggle it ON, you'll hear a short
BEEP. When you toggle it OFF, you'll hear TWO short BEEPS. You'll also have
a VISUAL aid that indicates the status of Insert.

In RIP mode, the button label will change to "Insert ON" or "Insert Off".
In ANSI mode, the status bar at the bottom of the screen will always show
the current status of Insert.

The full screen editor supports the fundamental WordStar type commands,
Wildcat compatible commands, VT100, VT102, and DOORWAY Extended commands.

WordStar and Wildcat commands typically involve holding down the control
key and then pressing the corresponding letter for the desired effect.  For
example, to reformat the message, holding down the [CONTROL] key while
pressing the letter B.

When editing, usually there is a alternate keystroke(s) that can cause the
same function.  In the previously listed table of commands, the other
possible combinations are displayed to the right of its control key
counterpart.

ANSI color, animation, RIP, and music are not allowed in the message base.
This is due in part to the full screen editor using ANSI and RIP control
sequences for maintaining the cursor and character positioning during
advanced functions of message editing.  If they were allowed, unpredictable
results could occur due to misinterpretation of the message control codes
and the editors control code usage.

The full screen editor supports several cursor movement commands generated
by different communication programs.  Cursor positioning using ANSI
terminal emulation as well as standard Escape commands are interpreted
properly.  If you find that your communication program is not operating
properly when in the full screen editor, you may need to activate ANSI
terminal emulation mode.

Some programs support both ANSI and Escape codes and do not require ANSI to
be activated.  If you still have problems with cursor positioning, make use
of the Ctrl keys to move the cursor.

Some commands such as Del, Ins, PgDn, PgUp, ^L-Arrow, ^R-Arrow, ^End, and
^Home are EXTENDED SCAN codes and your communication program has to support
DOORWAY extended scan codes. If you are using RIPscript, Doorway extended
scan codes are automatically toggled ON and OFF for you.

In RIPscript mode, you can also select commands from two PULL down menus or
from the menu BAR at the top of the screen. You can also PGUP and PGDN
using the scroll bar buttons on the RIGHT-HAND side of the screen.

                                JOIN LINES

                                 Method #1

You can JOIN the current line with the line ABOVE it by moving to the FIRST
character on the CURRENT line and pressing the BACKSPACE key.

                                 Method #2

You can also JOIN the line BELOW your current position with the line you
are CURRENTLY on by moving to the END of the line and pressing ^G or DEL.


                              INSERTING LINES

The CTRL key for inserting a blank line is ^Ki but there is an alternate
method of inserting.

Move to the FIRST character on the line BELOW the insertion point and press
ENTER. The editor will move the CURRENT line DOWN and insert a BLANK line
in it's place.
                                SPLIT LINE

The CTRL key for SPLITTING a line is ^N however, you can use the ENTER key
to do the same thing.

                                Editor HELP

There is a HELP file called EDITOR.HLP that explains pretty much everything
listed above. This file is displayed when a caller requests HELP from within
the full screen editor. You can customize this file to suit your own personal
tastes.
(H248)
For those in RIP mode, we have a VERY advanced full screen editor
that utilizes ICONS, BUTTONS, SCROLL BARS, and other advanced
features.

This editor is SO easy to use, we don't have to explain anything
about it.

(H249)
You create a file area using SM/Boards/Filboard.Bbs option.
When you select this option, you'll get a screen that looks
something like this:

╔══════════════════════════════ Filboard.Bbs ══════════════════════════════╗
║                                                                          ║
║ Area Name                                                               ║
║                                                                        ▓ ║
║ File Path                                                              ░ ║
║                                                                        ░ ║
║                              () Greater Than Or Equal To              ░ ║
║                              ( ) Less Than Or Equal To                 ░ ║
║ Area Access Level 0          ( ) Equal To                              ░ ║
║                              ( ) Less Than                             ░ ║
║                              ( ) Greater Than                          ░ ║
║                                                                        ░ ║
║                                                                        ░ ║
║ Category                                                               ░ ║
║                                                                        ░ ║
║                     1   2   3   4   5   6   7   8   9  10  11  12  13 4░ ║
║ Area Access Flags  [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] ░ ║
║                                                                        ░ ║
║                     1   2   3   4   5   6   7   8   9  10  11  12  13 4 ║
║▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░  ║
║Auto Add▄ Jump▄  First▄  Last▄  Add▄  Del▄  Next▄  Prior▄  Exit▄  Update▄ ║
║ ▀▀▀▀▀▀▀▀  ▀▀▀▀   ▀▀▀▀▀   ▀▀▀▀   ▀▀▀   ▀▀▀   ▀▀▀▀   ▀▀▀▀▀   ▀▀▀▀   ▀▀▀▀▀▀ ║
║                            Record 1 of 1                                 ║
║                                                                          ║
╚══════════════════════════════════════════════════════════════════════════╝

To edit a field, click on the field using the LEFT mouse button.
Data entry field editing commands for this section are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, PGDN, PGUP, UP ARROW or DOWN ARROW.

The following settings are available.

                            Area Name

This is the NAME of the file area and should be unique.

This name will be displayed when you change area, do a new upload
search, text find, and when you specify that area information
should be displayed when a specific command record is used.

                            [ ] CD-ROM

Toggle this to YES, [X], if this file area is a CD-ROM. This is
VERY important and you MUST do it.

                            File Path

This is the full drive and path to the physical files associated
with this file area.

                        Area Access Level

This is the access level you MUST have to gain access to this
area.

The FIRST file area you define MUST be accessible to ALL callers.
I MUST KNOW that I can switch you to file area one in case of
trouble.

                      Access Compare Method

This mean HOW do you want me to compare the callers access level
with the access level required to enter the area.

You  have FIVE options:

                     ( ) Greater Than Or Equal To
                     ( ) Less Than Or Equal To
                     ( ) Equal To
                     ( ) Less Than
                     ( ) Greater Than.

Your TYPICAL BBS or CBIS program uses Greater Than or Equal To.

                      [ ] Auto Free Uploads

By default, all NEW uploads are held and you can neither see nor
download them until you (or your co-sysop) FREES them. However,
you may want files uploaded in a specific area to be made
available for downloading ASAP. If you do, toggle this to YES.

                        Area Access Flags

You MUST have the SAME EXACT AREA ACCESS FLAGS turned on to gain
access to this area.

This is used to SUB-DIVIDE access levels so two people with the
same access level may or may not have access to the same area,
even if the area access level is the same.

Using this can produce a rather complex system to manage if you
aren't VERY careful. I recommend that you use area access flags
sparingly.

Example:

Assume area 2 has access flags 1, 3, and 15 turned on. For you to
get INTO that area, you must ALSO have area access flags 1, 3, and
15 turned on. It doesn't matter if your access level IS the same
as the area access level, your FLAGS have to match the ones for
the area.

Only the flags need to enter the area are check. That means that
if you also have area flags 5 and 16 on, it isn't going to matter.
They are ignored because only 1, 3, and 15 are needed.

There are 16 flags and that gives you over 32000 different
combination to work with.

Again, using area flags can complicate your system and I recommend
that you don't use them right away and if you DO decide you need
them, use them sparingly.

                        General App. Flags

These are provided for EXTERNAL applications that deal with file
areas. Each application that requires the use of one or more of
these flags will explain what, why, and how.

(H250)

If you need help with Osiris . . .

1. Send e-mail to support@hq.itc.com
2. Call our BBS at (314) 686-0120 and leave e-mail to the sysop.
3. If you live within the United States, Fax your question(s) to
   (314) 686-0154. You must provide a 24 hour RETURN FAX number if
   you want a reply.
4. Send Fidonet E-mail to 1:296/5.0 , wait a day or so then POLL for
   a reply.
5. Call Technical Support voice at (314) 686-0154 between 11 AM
   and 5 PM.
6. Contact a member of TEAM OSIRIS.

Method #1 is the recommended method for getting help and all Internet
e-mail messages will be answered within 24 hours, excluding weekends.

                            Team Osiris

Those that belong to Team Osiris are highly skilled Osiris sysops
that have offered to help other sysops with their problems.

Members of Team Osiris are not employees nor do they speak for
International TeleCommunications.


NAME     : Mark D. Winton
BBS Phone: (314) 893-6099   (United States)
Fidonet  : 1:289/8.0
Internet : mwinton@med.itc.com


NAME     : Rob Roy
BBS Phone: (905) 312-0311   (Canada)
Fidonet  : 1:244/407.0


Name     : Mark Janelle
BBS Phone: (207) 967-0618   (United States)
Internet : mj@frntline.com


Name     : Raimond Groegel
BBS Phone: 49-911-748169   (Germany)
Internet : na248@fim.uni-erlangen.de
Fidonet  : 2:2490/2055

(H251)
You have the ability to automatically give new callers certain
CONFERENCE areas. Create a text file in the Osiris directory
called  MSGAREA.BBS.

This is a simply text file listing the area NUMBERS you want to
give NEW callers. Area #1 is automatically given so don't put it
in the control file. If you do, Osiris will ignore it.

You can format MSGAREA.BBS just about any way you want as long a
you put a space between each area number. You can put one number
per line or 50 numbers per line.

Sample contents of a MSGAREA.BBS control file;

2
3
4
5
6

or

2 3 4 5 6

or

2 3
4
5 6

Be careful about loading callers down with areas. Give them only a
FEW areas, maybe 4 or 5 of the most popular conferences on your
system. Otherwise, they'll have to go in and toggle a bunch of
areas ON and OFF to get what they REALLY want.

(H252)
Osiris provides you with a method of subdividing or GROUPING like
conference areas under a "CATEGORY". You might do this if you have
a LOT of message areas.

You can define up to 21 different CATEGORIES. Keep in mind that
this was designed to be a BROAD BASED group so pick the categories
carefully so the maximum number of message areas can fit under a
single category. Maximum, but not TOO many.

To define categories, go to the Boards/Message Categories
subsytem.

When you select Message Categories, you'll get a screen that looks
a bit like this:

╔═════════════════════════════════════════════╗
║                                             ║
║ ┌────────── Message Categories ───────────┐ ║
║ │All Areas                                 ║
║ │--- Open Slot ---                        ▓ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                        ░ ║
║ │--- Open Slot ---                         ║
║ └─────────────────────────────────────────┘ ║
║                                             ║
║          Add ▄  Del ▄  Edit ▄  Exit ▄       ║
║          ▀▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀▀▀  ▀▀▀▀▀▀       ║
╚═════════════════════════════════════════════╝

To EXIT this section, press EXIT mouse button. To Add a
category, click on a slot labeled "--- Open Slot ---"
and then Click on ADD.

To PLACE a message area into one of the categories, go to the
Boards/Msgboard.Bbs subsystem. You'll see a field labeled
"Message Category". Just CLICK on the field and SM will present
you with a list of all the categories you have defined.

Osiris only uses the CATEGORY field when the caller goes to ADD or
REMOVE conference areas. He or she is asked to select a CATEGORY
and only those areas falling into that category will be displayed.

The caller can mix and match areas from different categories. That
is to say, you can have five areas selected from category number
1, 3 from category number 2, 9 from category 7, etc.

(H253)
Well, that is really something only you can answer. However, we
can give you some help.

More than once, we've heard sysops say they want to carry all the
internet Newsgroups or they want to carry 3000 newsgroup.

While this is a worth while goal, it is one that most sysops will
never be able to achieve.

The AVERAGE newsgroup message is roughly 2500 bytes. Some will be
smaller and some will be MUCH bigger.

You need to keep each newsgroup message on-line long enough to let
your callers read them and long enough so they can reference
THREADS, something they need to do.

That means you will likely end up with about 2000 messages PER
area, more if it is a HIGH volume newsgroup. That all boils down
to needing about 5 GIG per 1000 newsgroup areas.

If you carry all the newsgroups, roughly 7000 of them, you are
going to need at LEAST 35 GIG of hard drive space and that does
NOT include the space required for processing.

Very few sysops have enough space to handle 1000 newsgroups and
even fewer have a spare 35 Gig or so laying around.

Osiris will, providing you have the disk space, let you define
up to 8000 message areas.

Even if you DO have the diskspace, I'd really think twice before
putting 8000 message areas on-line.

A) It is going to require a lot of time to perform maintenance on
that many message areas.

B) It is going to require a lot of time to IMPORT that many
newsgroup messages.

C) Your callers are going to have FITS dealing with that many
message areas. Even if you use categories, it is still going to
cause a lot of them to throw their hands up in frustration.

Solution: If you want to carry ALL the usenet newsgroups, by all
means do it. But, just don't IMPORT them into Osiris. Only import
the areas you callers have REQUESTED.

After all, what is the point of wasting all that time and disk
space importing messages into areas nobody is reading?

(H254)
The maximum number of messages any single area can have is 32732.

Your callers will have access to the FIRST 2000 message in each
area. Nothing BAD will happen if you have more than 2000 messages,
those message will be available as soon as they float within
range.

You might be wondering why 2000 . . .

Osiris has to keep track of each message the caller has or has not
read in any given area. Even with our advanced tracking system,
this does require memory and disk space. We felt that all of you
would have the memory and disk space required to track 2000
messages per area.

(H255)
You can have up to 1500 file areas PER file system and up
to 32,000 file systems.

We recommend that you try and keep the number of file area's
per file system to less than 100.

This makes the system much less confusing to your callers.

(H256)
The interrupt manager automatically assigns priority to each of
the system's interrupts. The timer counter, keyboard, and cascaded
interrupt all have higher priority than the UART.

To gain the MAXIMUM throughput (especially when multi-tasking), I
suggest that you allow Osiris to alter the IRQ manager so the UART
has the highest priority.

You can do this using the environment variable 8259=IRQ{1-7}

Examples:

8259=IRQ4
8259=IRQ3

Keep in mind that only ONE of the uarts (in a multiuart
environment) can be switched to the HIGHEST priority, select the
one that contains the fastest modem.

Intelligent Multiport cards use a single shared IRQ. This is the
one you want to give the highest priority.

Keep in mind that you must use UPPER CASE and reboot your
computer before Osiris can access the environment variable.

(H257)
Osiris can, running in stand alone mode, detect and accept an
incoming UUCP mail session.

First, create a file in your OSIRIS= directory called "SYSTEMS".

Each line in this file contains two words, a UUCP name and a UUCP
password.

Example:

BUZZ J6781
CAMELOT HKH29

Incoming UUCICO programs should look for/send the following:

LOOK FOR                 SEND
------------------------------------------
SERVICE:                 UUCP
LOGIN:                   <THEIR UUCPNAME>
PASSWORD:                <THEIR UUCP PASSWORD>

This script format is common with UNIX, SUN, and WAFFLE systems so
most UUCICO script files will work with Osiris without having to
be modified.

Osiris will scan the SYSTEMS file looking for their UUCPNAME and
if found, compare the PASSWORD with their UUCP PASSWORD.

If they match, Osiris will call up UUCICO to send/receive the
mail.

After the session, Osiris will exit with the errorlevel of 254.
Trap this and run your INTERNET programs; Scorpion, Viper, Ghost,
SNEWS, Etc.

Of course, Osiris will update all supplement files such as the
UUCP.DAT (billing system), HISTORY LOG, etc.

UUCICO will already be configured if you have installed Scorpion
and Ghost. If you haven't, you need to install those packages
first.

(H258)
Osiris has built-in support features for internet E-mail,
newsgroups, list servers, etc. Most of this is invisible to you
and you don't need to do anything special to the BBS.

Scorpion   : Internet E-mail daemon.
Viper      : Internet Newsgroup Import/Export package.
FTPmail    : Ftpmail daemon.
Mail-Server: General purpose mail daemon.
List       : List Server.
Ghost      : Intelligent HOST software including a very advanced
             news feed system complete with accounting software
             and areafix. This is not distributed with the basic
             package and not included in the purchase price. You
             only need this package if you plan on acting as an
             Internet HOST to other systems.


(H259)
Osiris, like other BBS applications, has formatted fixed maximum
field lengths.

This posses problems when you have TO and FROM fields that have no
specific length. Internet has no maximum field lengths so we have
to do a bit of fancy foot work to get things to work.

When Scorpion imports an e-mail message, it creates an AIR field
with the original untouched FROM field. Then the message is
converted to fit into a MESSAGE CENTER message.

When you REPLY to an Internet e-mail message, Osiris will ask if
you want to use automatic reply addressing, AIR. Nine times out of
ten, you'll answer yes.

(H260)
When you reply to a NEWSGROUP message, I will ask you if you want
the reply to go EMAIL or if the reply should be posted in the
current newsgroup area.
(H261)
Viper automatically encodes

In <MESSAGE ID>
<John Does> Writes:

with <MESSAGE ID> being replaced by the Internet MESSAGE ID: field
and <John Does> being replaced by the persons who actually posted
the message into each message it imports.

When you reply to one of these messages, Osiris decodes and
includes this in the reply.

(H262)
Yes, you can attach files to Internet e-mail messages.

Just enter the message and when Osiris asks if you would like to
attach a file answer YES and upload the file.

When Scorpion spools the message for Internet delivery it will
automatically uuencode the file.
(H263)
Yes, you can hook Osiris directly to Internet via a SLIP/PPP, 56K,
or T1 connection. This gives you real time Incoming FTP, Out Going
FTP, Archie, Telnet In, Telnet Out, and Gopher.

Netware 386 will be sufficient, depending on the number of nodes
you use. This will run you about $400 to $500 mail order.

Contact Technical Support at (314) 686-0154 for further details.


(H264)
Osiris supports follow-up and References fields in
NEWSGROUP areas.

The callers, for obvious reasons, are not allowed to set
newsgroup or followup fields.

(H265)
While a SHORTER version of the subject line is used for display
purposes, Osiris DOES retains the ORIGINAL Subject, up to
1000 characters. If it is MORE than 1000 characters, the subject
is truncated at the 1000th character.

When replying to a newsgroup message, the ORIGINAL subject is
used when it is exported back into Internet. If "RE:" is not in
the original subject, Osiris will add it.

(H266)
The original NEWSGROUPS control line is retained and when you
reply to a newsgroup message, your reply is sent back using
the ORIGINAL newsgroups control line.

The ONLY exception: If the message had a FOLLOWUP-TO control line,
your reply is sent BACK to the newsgroups listed in this line and
the orignal FOLLOWUP-TO control line is added to your reply to keep
things flowing in the right direction.

(H267)
You can define an AUTO signature file that will be appended to all
newsgroup messages posted on your system.

The signature file can contain a standard disclaimer something
like this:

=============================================================
The views and opinions expressed in this message are those of
the person that posted the message and in no way reflect the views
and opinions of <YOUR NAME or COMPANY NAME>
=============================================================

In SM/BOARDS/MSGBOARD.BBS, you'll notice a slot labeled "SIG",
providing the area is defined as UUCP or UUCP/REV.

Create your signature file with any text editor and then type in
the name of the signature file in this field. I would suggest that
you include a full path and file name if you are running on a
network.

You can create a different signature file for each area or you can
create one and have SM apply the change (when you type in the
signature name for the first time) to all LIKE message area.

By LIKE message areas, I mean that if the area is defined as UUCP,
the change would be apply to all other UUCP area.

NOTE: UUCP/REV and UUCP are NOT like areas.


(H268)
When you view/read a newsgroup message, you'll see the SENDERS
real name, not his internet address, when possible. The ORIGINAL
from field is preserved and used if you want to reply via e-mail.

You'll also notice that all newsgroup messages have a TO field of
ALL. That's because newsgroup messages have NO to field but,
Osiris has to have one so we place ALL in the field.

(H269)
Each time a person logs onto the system, Osiris will notify the
other nodes with a message that looks something like, "John Doe
from New York, NY has just logged on to Node 10".

When this person logs OFF the system, Osiris will notify the other
nodes witha message that looks something like, "John Does just
logged off Node 10".

This is contingent on two things. First, you have to be running
multiple lines. Second, the person logging on has to allow his or
her name to show-up in the user list.

                  Disabling This Feature

If you do not want Osiris to do this, create a file called
NO_TELL.BBS" in the OSIRIS= directory. First line should read,
DISABLE LOGON/LOGOFF NOTICE.

We don't feel that enough of you will toggle this OFF to warrant
the memory required to store an ON/OFF switch.

(H270)
Before you log on in LOCAL mode, you must make sure your SCROLL
LOCK key is engaged.

To prevent STATIC discharge from triggering false keyboard input,
Osiris XLT will IGNORE ALL keyboard input unless SCROLL LOCK is
engaged. You're advised NOT to keep SCROLL lock ON unless you are
actually going to interact with Osiris in some way, shape, or
form.

Osiris requires TWO command line switches for LOCAL log-on; -L and
-Nx

-L means LOCAL mode, don't need SERIAL drivers.
-Nx means use this node number, x is the node number.

Example: OSIRIS -L -N1

(H271)
For those that don't want to use Full Screen ANSI Editor you have
the LINE editor.

It allows you to edit existing lines, insert lines, delete lines,
continue to add to message, list the message, abort the message,
and even do QUOTED replies.

A QUOTED reply is where you REPLY to a message and IMPORT sections
of original message so the other person will KNOW what you're
referring to.

The LINE editor will allow up to 150 Lines of text, roughly 12K.

(H272)
Osiris supports 3 different log levels: 0, 1, and 2.

The default log level is 0 and supplies more information than
most sysops need.

To switch to a level 1 log, add the following to your AUTOEXEC.BAT
and reboot your computer.

SET LOGLEVEL=1

The level 2 log provides a TON of information and will consume a
LOT of disk space in a hurry.

To switch to level 2 logging, add the following to your
autoexec.bat file and reboot your computer.

SET LOGLEVEL=2

Log levels  1 and 2 are NOT recommended for systems running under
OS/2, Windows, or on a network. They can really slow your system
down.

(H273)
Osiris will take care of THREADING messages that your
callers enter but you need to run the program "ULINK.EXE"
to thread the messages you import from Fidonet or Internet.

(H274)
Osiris supports Intelligent multiport serial cards, intelligent
multiport serial cards, fossils, and has an internal serial
driver (fastest method of dealing with the serial port).

I STRONGLY urge you to consider using one of the intelligent
multiport serial cards if you plan on running more than 4 nodes on
a single computer. Or if you plan on running under Windows or OS-
2.

The intelligent multiport cards have onboard processors and memory
that takes care of the serial I/O and this reduces the strain on
the computers CPU. Not only does it free a lot of CPU time, but
you aren't likely to lose data when you switch tasks.

Running 8, 16, or even 32 lines under Desqview is possible ( 486
CPU required for more than 8 lines).

While some manufactures will tell you THEIR software can handle 64
lines, or more, on a single computer, I will not.

While it is possible to run 64 Osiris nodes on a single computer,
the system is likely to come to a stand still during such things
as online games and file transfers. The drain on the CPU is just
too intense under those conditions.

For MAXIMUM performance, I don't recommend more than 16 lines,
even with an intelligent serial card, on a single computer.

(H275)
Load the Star Gate device driver, ACL.SYS, in your config.sys.
When your system boots, run ACLDL to download your code. Assuming
a memory address of D000 and Latch I/O address of 200: ACLDL D000
200 ACL

You'll need to create a SERIAL.CFG control file in your Osiris=
directory.

The first line of this file should contain 5 settings separated by
a single space.

BOARD BOARD_SEGMENT PORT FIRST_PORT_NUMBER NUMBER_OF_PORTS

Board: Stargate board to use (0 - 3).  Osiris can handle up to
four stargate boards ( 64 ports) at once. This tells me which
board you want to use.

Board_segment: Segment, in HEX, of the Star Gate board's memory
window.

Port: The Address, in HEX, of the board's I/O latch.

First_port_number: Name given to the first port on the board
(1,2,3,etc). The designation of the port number for the first port
on the board is arbitrary.

Number_of_ports: Number of ports on the board.

Example:

{SERIAL.CFG}

0 d000 200 5 8

meaning Board 0, Memory Segment D000, I/O Latch address 200,
Starting com port 5, total ports 8.

Add

COMDRV=STARGATE

to your AUTOEXEC.BAT and reboot the computer. You must use UPPER
case, no spaces, and you must reboot the computer before this
takes effect.
(H276)
When you load  the Arnet device driver, port number assignments
will be displayed on the screen. These are the number you'd use in
the Osiris with the /P switch.

Use the /N5 switch on ASP.SYS. If you do not use this switch,
attempts to set handshaking will result in an error.

ASP.SYS, supplied with Arnet boards, uses the files, box.bin and
fastbios.bin at boot time and must be in your root directory to
work properly.

Add

COMDRV=ARNET

to your AUTOEXEC.BAT and reboot the computer. You must use UPPER
case, no spaces, and you must reboot the computer before this
takes effect.

(H277)
Run the Digiboard config. program (XIDOSCFG.EXE) which asks you
for the desired port numbers. Also, install the device driver
supplied with the board. You must also complete the following
steps:

1. Set up the board NOT to use interrupts.

2. Setup to support INT 0x14 for most drivers and EBIOS for the
XIDOS5 driver.

3. Change the configuration to enable ports, if your driver
requires it. Make sure "NONE" is the selected handshaking for
ports.

4. Reboot your system. During the boot, the driver should respond
with the message "successfully initialized board".

Add

COMDRV=DIGI

to your AUTOEXEC.BAT and reboot the computer. You must use UPPER
case, no spaces, and you must reboot the computer before this
takes effect.
(H278)
Osiris uses a language database to store the text, colors, and
certain RESPONSE characters (Y/N type, MORE etc.) used within
the main Osiris.exe program. This means you can alter any text
display, change it to a different language, and the colors
Osiris uses.

The default language database is called "LANG.DAT"  and  the
uncompiled TEXT version is in a file called "LANG.TXT".

Each  line of text in LANG.TXT is a SINGLE  database  record.
Osiris does, in a few places, combine multiple database  records.

The  text's POSITION in the LANG.TXT file is  very  important  and
if you modify the text, or colors, you must  NOT  modify  the
texts position in this file. If you do, you'll throw  the  entire
display system off.

Each record, or line, has a maximum length of 254 characters,
including color, formatting characters, etc.

There is no EASY method of identifying exactly where each  record
is used. Actually there is, but it requires the Osiris  source
code but you don't have that and we're not going to  give it to
you.

The best way to tell is just to look, while in local mode, at the
text being displayed and try to match it with text in the control
file.

In a lot of cases, it will be fairly obvious where the  text  is
displayed and what it is used for. In other cases, you may  have
to use the old trial and error method. I am assuming that you
aren't going to be tampering with this file until you are fairly
familiar with the Software.

In some cases, we'll TRY to comment the line if it isn't very
obvious where it goes.

If all else fails, you can always ask us.

LANG.TXT  not  only  contains the text and  colors,  it  also
contains a LOT of the formatting commands. Either in the  form  of
\r, \n, _, |, or spaces.

\r generates a carriage return. This does NOT generate a  NEW
line,  it simply puts you on COLUMN 0, same line.

\n generates a NEW LINE, i.e., it moves you down a line.

_ is a BLANK SPACE indicator, most text editors do not  allow  you
to end a line with a space, and they shouldn't. When  you  are
required to RESERVE a blank and the blank is at the  end  of a
line, use the underscore character.

| is used to tell Osiris WHERE to insert information, such as time
left for call, time on-line, etc.

If you want to translate the text to another language, first do   
a DIRECT, if possible, translation line for line without regards  
to the combined use of multiple records.

Do this a section at a time. By section, I mean a SET number of   
lines . . . 20 is a good number. Log-on locally and try out the  
areas that use the text. You may need to adjust the text   
alignment if the language conversion makes the text longer or  
shorter.

Osiris can't make direct use of LANG.TXT, it must be compiled  
using SM. The compiled database that Osiris uses is LANG.DAT.


(H279)
There's not much in the way of CONCRETE solutions for modem
problems because there are too many UNKNOWN variables involved.

We can give you some HINTS on WHERE to look if you have problems.

The most COMMON problem, running Osiris without providing the
modem information. In other words, running osiris with NO command
line switches or running Osiris with the WRONG or incomplete
command line, generally no -W switch.

There is a section in this help system labeled "Running Osiris".
You should read that if this is your problem.

The second most common problem, using a FIXED DTE rate but
forgetting to TELL Osiris.

You need to have an environment variable defined for each COM PORT
if the modem on the COM PORT has a fixed DTE rate.

Assuming COM 1 has a modem on it with a fixed DTE rate of 38400,
you need the environment variable COM1=38400.

You define this using the SET command in your AUTOEXEC.BAT file
and you MUST reboot the computer before OSIRIS can see it.

The SET command would look something like:

SET COM1=38400

Notice that it is in UPPER CASE and the ONLY space is between SET
and COM1.

The third most common problem, telling Osiris to use a FIXED DTE
rate with the COMx=DTE RATE but not setting up the MODEM to use
it.

Osiris can NOT tell your modem to use a FIXED DTE rate, only YOU
can do that. You'll have to consult your modem manual to see HOW
to do that.

The fourth most common problem is the MODEM string itself.

We get several "Its the same string I use with other BBS programs
but Osiris will not work right with my Modem"  comments a year.

The only thing I can say... That's pretty hard for us to believe.
I'm not saying it isn't POSSIBLE, but in every case we've seen,
there was an TYPING ERROR of some type in the modem string.

Some BBS applications MAY micro-manage your modem. In other words,
they may send commands to configure it without your knowledge or
consent.

Osiris will NOT and does not attempt to do ANYTHING to behind your
back. Osiris simply passes the -W  modem string to the modem AS IS
and then sits back and waits for a CONNECT message.

It doesn't even require the modem to return OK.

Osiris DOES require the modem to:

1) Return CONNECT messages you've defined in the MDMSTRxx.BBS
   file.
2) Report DTR LOW when there is no carrier, report DTR HIGH
   when there is carrier, and DROP carrier when DTR is forced low.
3) Your -W string should HANGUP the modem.

Item 1, add V1 and then consult your modem manual on what VERBOSE
connect messages it returns.

Item 2, Generally a FACTORY default. If not you'll have to consult
your modem manual.

Item 3, Generally adding H0 takes care of that.

Another settings you might want to include:

E0, disable echo. This is not required but it will speed things up
because Osiris WILL examine the echo to see if it contains a
CONNECT message.

If you cannot figure out your problem, call out technical support
voice line. We'll do our best to help you but we cannot make any
promises in the area of solving modem problems.

(H280)
You see RING appear on the screen but the modem doesn't answer?

There are two ways your modem can answer and you can use one or
the other but not both at the same time.

1. Set your modem to AUTO ANSWER.
2. Set your modem to answer when it received a specific string
   (generally, but not always, ATA<CR>).

If you select method 1, then you should NEVER place ANYTHING in
the MODEM ANSWER STRING field (SM/NODE). Most, in fact all that
I've seen, will ABORT the answer if they receive anything from DTE
, your computer, when set to AUTO-ANSWER.

Method 2 REQUIRES that you modem send the word "RING" to the DTE
and the modem should NOT attempt to answer UNTIL it receives the
command string from the DTE. Again, if your modem trys to answer
on its own and it receives a command string from the DTE, it will
abort the ANSWER and the command string is ignored.

When the modem doesn't answer, the most COMMON reason is that you
have intermixed the two methods.

Osiris itself actually has little to do with answering the phone.
If you use the MODEM ANSWER STRING, all Osiris can do is send the
contents of the field to the modem when your modem reports RING
and then wait for some type of CONNECT message from your modem
that matches something in the mdmstrX.bbs file.

(H281)
Osiris has an internal Virtual Memory Manager, referenced simply
as VMS, that assures the maximum amount of free memory is
available for all external applications such as protocol drivers,
SPL/I _EXECUTE calls, archive calls, etc.

VMS will use either your DISK, XMS, or EMS memory to store mapped
Memory Segments before making these calls. VMS will make memory
available, except for 2.6K

(H282)
MMU will take an ANSI file and convert it to MMU format using
compressed color commands and then compress the file to speed up
display. If the caller doesn't support ANSI, Osiris will simply
skip over the color commands.

MMU is fairly simply to use, just enter the name of the file to
convert. If the file is in ANSI format, add /A.

Suppose you want to convert your main menu file, main.ans to MMU
format. MAIN.ANS is in ansi format so . . .

MMU MAIN.ANS /A

creates the file "MAIN.MMU".

Suppose you have a display file, it does NOT contain ANSI
characters, but you want to convert it to MMU format to save disk
space and to speed up the display. Lets call the file
"HELPFILE.ASC".

MMU HELPFILE.ASC

Since there are no ANSI commands, we don't use the /A switch and
the output file will be HELPFILE.ASC.

There is an optional switch, /F, that you MAY want to use. /F
controls data compression. Normally, data compression is turned
OFF. But, if the file contains NO BACKGROUND COLOR CHANGES, you
would get a faster displaying file if you use /F.

Example: MMU MAIN.ANS /A /F

Produces a smaller MAIN.MMU and it is even faster than the first
main.mmu we created.

                      Command Line Switches

For more advanced users, there are several optional switches.

/A Do conversion on <Infile>, when <Infile> is in ANSI format

/B Place [breakoff] at top of file. Only if '/A' is specified

/C Place [Cls] at top of file. Only if '/A' is specified

/M Place [Moreoff] at top of file. Only if '/A' is specified

/F Data Optimizing ON (default is OFF) /25 Allow FULL 25
 Line(s) (/A Only)

/O Do conversions from ANSI to MMU pre-compiler format ONLY.
   Only if '/A' is specified

/B Place breakoff at the top of the file. Turning break
   off means the caller cannot break out of the file. He has to
   wait until the entire file has been displayed.

/C Place clear screen at the top of the file.

/N Do color implants. I've never ran across an ANSI file
   that required this, but if you compile an ANSI file and you
   flat can't get the colors to come out right, add this  switch.

/R Reverse Compiler. Turn an MMU file back into an ANSI file.

(H283)
A conference area is a PUBLIC message area. Messages POSTED in this
area can be read and replied to anyone that has access. Use the
SM/Boards/Msgboard.Bbs option to create each message areas.

Again, I wish to stress the word "PUBLIC". Conference areas cannot
by their very nature contain private messages. In fact, Fidonet Echomail
and USENET newsgroups do not allow nor do they make provisions for
PRIVATE posts.

When you select SM/Boards/Msgboard.Bbs you'll get a screen
that looks something like this:

╔═════════════════════════════ Msgboard.Bbs ════════════════════════════════╗
║                                                                           ║
║Area Name                                                                 ║
║                                                                         ▓ ║
║Message Path                                                             ░ ║
║                                                                         ░ ║
║Pack Trigger 0       Pack Level 0                                        ░ ║
║                                                                         ░ ║
║                    () Greater Than Or Equal To                         ░ ║
║                    ( ) Less Than Or Equal To                            ░ ║
║Access Level 0      ( ) Equal To                                         ░ ║
║                    ( ) Less Than                                        ░ ║
║                    ( ) Greater Than                                     ░ ║
║                                                                         ░ ║
║                   1   2   3   4   5   6   7   8   9  10  11  12  13  14 ░ ║
║Area Access Flags [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ] [ ]░ ║
║                                                                         ░ ║
║Origin                                                                   ░ ║
║                                                                          ║
║▓░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░  ║
║      Jump▄  First▄  Last▄  Add▄  Del▄  Next▄  Prior▄  Exit▄  Update▄      ║
║       ▀▀▀▀   ▀▀▀▀▀   ▀▀▀▀   ▀▀▀   ▀▀▀   ▀▀▀▀   ▀▀▀▀▀   ▀▀▀▀   ▀▀▀▀▀▀      ║
║                           Record 1 of 1                                   ║
║                                                                           ║
╚═══════════════════════════════════════════════════════════════════════════╝

To edit a field, click on the field using the LEFT mouse button.
Data entry field editing commands for this section are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, PGDN, PGUP, UP ARROW or DOWN ARROW.

The FIRST area you define MUST be accessible to ALL callers. I
must KNOW that I can place you in area ONE if something happens. I
suggest the first area be a GENERAL conversation area.

                            Area Name

This is the name of the area and is displayed when you do an area
change, join a conference, and when you request the display of
message area information from within a command record.

                            Board Type

This determines the TYPE of message area and you must select one
of the following:

[ ] LOCAL, means the messages NEVER leave your system and new
messages are instantly available for reading.

[ ] LOCAL/REV, means the messages NEVER leave your system but they
should NOT be available for reading until you OK them.

[ ] ECHO, means the messages WILL be leaving your system (how
doesn't matter) and the messages should be made available for
exporting OFF the system and reading as soon as they are entered
, NOT RECOMMENDED!.

[ ] ECHO/REV, means the messages WILL be leaving your system (how
doesn't matter) BUT . . . not before you OK them. Recommended for
Fidonet Echomail or RCRElay Echomail areas, can save you a LOT of
headaches.

[ ] Pass Through, means this area's messages will be deleted ASAP
as soon as they leave. You should NOT give ANY caller access to an
area defined as Pass Through.

This type of area is strictly for Echomail (fidonet) processors to
work with and NOT for humans.

[ ] UUCP means the messages are coming from and going to Internet
newsgroup areas and messages are posted as soon as possible.

[ ] UUCP/REV, means the messages are coming from and going to
Internet newsgroup areas and messages posted should be held until
you can review them.

                           Message Path

This is the full drive and path pointing to the directory
containing the messages for THIS area.

Messages are stored in two files, HDRx.BBS and TXTx.BBS with x
being the internal area number. Area numbers start with 1.

The format of stored messages is very efficient and We've been
using it for about 5 YEARS. In fact, several Public Domain BBS'
have made attempts at duplicating my storage format. They are
close, but not as efficient or as reliable.

                           Access Level

This is the access level you have to have before you can get into
this area.

                      Access Compare Method

This mean HOW do you want me to compare the callers access level
with the access level required to enter the area.

You have FIVE options:

                   ( ) Greater Than Or Equal To
                   ( ) Less Than Or Equal To
                   ( ) Equal To
                   ( ) Less Than
                   ( ) Greater Than.

Your TYPICAL BBS or CBIS program uses Greater Than or Equal To.

                        Area Access Flags

You MUST have the SAME EXACT AREA ACCESS FLAGS turned on to gain
access to this area.

This is used to SUB-DIVIDE access levels so two people with the
same access level may or may not have access to the same area,
even if the area access level is the same.

Using this can produce a rather complex system to manage if you
aren't VERY careful. I recommend that you use area access flags
sparingly.

Example:

Assume area 2 has access flags 1, 3, and 15 turned on. For you to
get INTO that area, you must ALSO have area access flags 1, 3, and
15 turned on. It doesn't matter if your access level IS the same
as the area access level, your FLAGS have to match the ones for
the area.

Only the flags need to enter the area are check. That means that
if you also have area flags 5 and 16 on, it isn't going to matter.
They are ignored because only 1, 3, and 15 are needed.

There are 16 flags and that gives you over 32000 different
combination to work with.

Again, using area flags can complicate your system and I recommend
that you don't use them right away and if you DO decide you need
them, use them sparingly.

                           Pack Trigger

This is the MAXIMUM number of messages you want to in THIS area.
This is used by CAT (auto maintenance system).

                            Pack Level

If I have to REMOVE messages because the total number of messages
in the area exceeds the Pack Trigger Level, this is the number of
messages to LEAVE after packing the area. I recommend, to reduce
drive fragmentation, this number should be 1/3 the pack trigger
level.

In other words, if the pack trigger level is 300, the pack level
should be no more than 100.

Never set the PACK level to ZERO. This can cause unpredictable
results.

                              Origin

This field is provided for external applications. If an
application requires the use of this field, it will explain why,
what, and how.

                          [ ] Word Wrap

This tells me that I should END each line of a message, that you
type in, with a HARD carriage return or allows the line to WRAP.

This should ALWAYS be set to YES for message area unless the area
deals with PcRelay.

                        [ ] Alias Allowed

If set to YES, you can (providing you have defined one) use your
alias instead of your REAL name. Most Fidonet echomail areas do
NOT allow an Alias so check before allowing this.

                      [ ] Area Is Invisible

If you want to HIDE an area making it impossible to JOIN using the
normal JOIN command, toggle this flag to YES.

If this flag is set to YES, Osiris will not allow the caller to
JOIN/UNJOIN this area. In fact, the area will never show up.

Osiris will also NOT auto-assign the area to a NEW caller.

The ONLY way the caller can ADD/REMOVE this area is if you add or
remove the area via the SPL/I command "join_area()".

This gives you a great deal of control over WHO gets into which
area based on just about any thing you can think of.

This also lets you create your OWN join/unjoin subsystem and also
lets you personally handle giving new callers message areas.

           Actually Creating The Message Database Files

This is VERY important, Osiris MUST be used (In LOCAL MODE) to
create the actual message database files for CONFERENCE areas.

When you log-on locally, I will validate the message databases and
creates any that are missing.

I will only do it in LOCAL mode because of the amount of time, 15
to 20 seconds, it takes to validate several hundred messages
areas.
                            Templates

The best way to create several like message areas at once is to
create the first area, define all the attributes (fields) and then
use that area as a template when creating others.

Using an existing area as a template means you only need to change
one field, the area name.

To use an existing area as a template, simply JUMP to that record
and hit the ADD button.
(H284)
If you want to create a CUSTOM access check for  a specific
file area, you can!

Toggle GENERAL APP FLAGS (SM/Boards/Filboard.Bbs subsystem) number
3 on for that area. This prevents any individual from CHANGING
into (with area command) or selecting any file from that area
unless s/he's in the area.

The only way to can get into the area is with the SPL/I
set_file_area() command.

You can set a specific command on your menu to access the area and
that command would be an SPL/I command file.

If you want to totally HIDE the area from view, set GENERAL APP
FLAGS number 4 ON.

If GENERAL APP FLAGS 3 is ON but GENERAL APP FLAGS 4 is OFF, the
area will show up in the area change list but the caller will NOT
be able to select it.

Instead, Osiris will attempt to run the SPL/I command file
CAFxxxxx.PRG (should be in the MENU directory defined for the
current command record) with xxxx being the file area NUMBER.

You can do some type of ACCESS checking (name, age, password, etc)
and if they PASS the access check, use the set_file_area command
to finish the change.

Lets assume you want to setup a file area, 10, that requires a
password to get into and that password is speedstar. Further more,
you want the area to show up when an area  change is requested.

Set GENERAL APP FLAGS 3 ON, GENERAL APP FLAGS 4 OFF, and create a
command file, CAF10.SCR, containing:

 main()
 {
 char s[80];
 cls();
 printf("Enter Area Password ? ");
 gets(s,70);
 if(s = "speedstar")
 {
 set_file_area(10);
 }
 else
 {
 cls();
 printf("Password failure, access to area denied\n");
 printf("Press any key to continue");
 force_pause();
 }
 }

Lets say you want to setup a file area so that you and your co-
sysops can exchange files but you don't want the area to show up
if someone does a file area change.

Keep in mind that using an ACCESS LEVEL would, in this case, be
easier but for the sake of an example....

Set GENERAL APP FLAGS 3 and 4 ON. This HIDES the area from an area
change command and requires the use of an SPL/I file to get into
the area.

Create a SPL/I file called GIMME.SCR containing:

 main()
 {
 if(_name = "Sam Spad" || _name = "John Doe" || _name = "Billy Bob")
 {
 set_file_area(10);
 }
 }

Compile Gimme.scr and copy GIMME.PRG to the SLASH.BBS directory.

From the file subsystem, typing /GIMME from the file menu will put
you in file area 10 providing your name is Sam Spad, John Doe, or
Billy Bob.

CAFxxxxx.PRG does NOT have to do a file area change. You could use
it to create a totally CUSTOM file area with say, oh.... a fake
file list with a short menu for downloading.

Lets say you selected the area and right away get something like
this without having to do anything else.

Billing.zip 12128 Custom billing system.
Pkzip.exe 89349 Pkzip.

(D)ownload (C)ontinue ?

What you end up doing with this is entirely up to you.

(H285)
If you want to HIDE an area making it impossible to JOIN
using the normal JOIN command, toggle this flag to YES.

If this flag is set to YES, Osiris will not allow the caller
to JOIN/UNJOIN this area. In fact, the area will never show
up.

Osiris will also NOT auto-assign the area to a NEW caller.

The ONLY way the caller can ADD/REMOVE this area is if you
add or remove the area via the SPL/I command "join_area()".

This gives you a great deal of control over WHO gets into
which area based on just about any thing you can think of.

This also lets you create your OWN join/unjoin subsystem and
also lets you personally handle giving new callers message
areas.

(H286)
As indicated in the Software License Agreement, any multi- line
version of Osiris must be used "on multiple computers connected by
direct cable to the same network server." It is not licensed for
use at multiple locations. Any questions regarding your rights
under the Software License Agreement should be directed to ITC for
clarification.

Those installing the multiline version for the first time, as well
as those upgrading from a single-line version, should first set up
a single line system. Don't attempt to setup multiple lines right
off the bat.

                       How It Works

When writing a multiline BBS system there are two ways of talking
to more than one communication port at the same time. The first
makes use of "internal program multitasking."

A single PC/AT handles the port addressing for all lines and
internally directs the program responses to the ports. This type
of setup needing only the one computer, but you can't perform
activities outside the program or DOS shell support.

It is not possible to run doors, external protocols, or any other
program as a sub-process.

The second method loads a separate copy of the BBS program into
memory for each line or node. This setup allows an individual node
to perform whatever activity or BBS maintenance event it desires,
while allowing the remaining lines to perform independent
activity.

The disadvantage is the extra memory required for multi- tasking
software or additional hardware for network operation.

We use the second method because it is REQUIRED for doors and
external file transfer protocols. This, by no stretch of the
imagination means Osiris, or any program, can just leave
everything up to the multitasker or network software. That simply
would not work and your hard drive would end up a mass of mangled
files.

I'll not get into what Osiris does, most of it is pretty
technical, just don't attempt to run multiple copies of any
program that updates files unless that program SPECIFICALLY says
it can handle it.

(H287)
I've included support for file and record locking under Novell, 3-
COM, Banyan Vines, PC-MOS 386, Network OS, LANtastic, and any
networks that truly support DOS 3.x SHARE. Keep in mind that
several peer-to-peer networks claim SHARE support, but do not
actually have it!

In a LAN environment, each Osiris line operates on a separate
computer connected to the other PCs or ATs via network cable. Each
line loads and runs its own copy of Osiris from the server's hard
disk. In this context, a "server" is any computer in a LAN setting
that allows sharing any of its peripherals such as hard disks,
printers or other devices.

Some network configurations only allow sharing programs located on
a "dedicated server," one that only performs LAN management
functions. Others enable sharing of disk devices located in other
workstations and are normally referred to as peer- to-peer
networks. In a network which allows multiple "servers," the server
computers can also be used as a workstation for an Osiris node.
Each workstation running Osiris is assigned a separate and unique
Node ID Number. Regardless of the network used, only one copy of
Osiris needs to be kept on the disk. This copy is available to
each workstation running an Osiris node. All workstation nodes may
update and access a common message, file, and user databases.

(H288)
Novell offers several versions of NetWare including the entry
level system ELS Level I, ELS Level II, and Advanced NetWare. ELS
I is limited to 4 workstation connections, including a non-
dedicated server that can operate as a workstation. ELS II is
limited to 8 workstation connections and also uses a non-dedicated
server that doubles as a workstation. ESL, Level I and Level II,
are priced significantly lower than Advanced NetWare which will
allow up to 250 Osiris nodes.

It's been reported that Advanced NetWare ver. 2.15 is capable of
operating two nodes on a single workstation using DESQview. This
type of configuration allows you to operate six nodes using 3 AT's
connected as Novell workstations, with each AT running 2 BBS
lines.

(H289)
This network operates Osiris well when configured properly. The
following network parameters have been found to increase
reliability and improve operation: DOS ver. 3.1, 3.3, 5.0, or 6.0
is recommended, version 3.2 is not fully compatible with the
network communication interfaces and 4.x is just buggy. The SHARE
command is not necessary since LANtastic emulates SHARE in the
LANBIOS.

For maximum performance, I recommend using a small disk cache
system with LANtastic.

(H290)
For those interested in running only 2-3 or possibly 4 nodes, it
can done on a single 80286/80386 system under DESQview, a
multitasking operating environment available from Quarterdeck
Office Systems, 150 Pico Blvd., Santa Monica, CA 90405, (213) 392-
9701. Although very fast 386 combinations may be able to run 4 or
5 nodes, I've found that performance may suffer significantly on
slower systems when more than 2 serial port applications.

The number of nodes actually possible under DESQview will depend
on several variables, including the speed of the microprocessor &
clock, the baud rates of the connections, and the speed of the
hard disk.

Although my recommendation is for no more than 2 nodes under
DESQview, there are some situations which may allow additional
nodes to be added. If a fast 486 or P5 (Intel's newest CPU) CPU is
used, you may find that an additional node or two can be added
with little or no impact on performance.

DESQview should be set up with two windows and follow the same
procedures as a network. The only real difference here is that
SHARE must be loaded before starting the DESQview program with DV
or XDV. There is no need to load SHARE in each DV window. Osiris
is DESQview "aware" and will recognize when it is operating in a
DV environment. When the TX buffer can no longer take data, I'll
slice time to the other partitions. The same holds true when
Osiris is waiting for input. If no input is available, I'll slice
time to the other partitions.

(H291)
Desqview can, at times, come up with an exception 13 error. No one
really KNOWS what this error message means. If they do, they don't
want to share that information with anyone.

It also only shows up on SOME systems while others NEVER see it.
Which indicates that it has something to do with the way your
system is configured.

Someone DID figure out that changing two parameters within
Desqview "SEEMS" to make the error message go away.

Try changing the COMMON MEMORY from 17K to 20K and change the DOS
BUFFERS FOR EMS to 5. You may need to go higher on one or both of
these settings but try the 20K and 5 first.

Some else suggested adding STACKS 18,256 to your CONFIG.SYS.

(H292)
This follows the same Osiris software setup procedures as a
network. The only real difference here is that SHARE must be
loaded in EACH SLAVE ENVIRONMENT. Alloys' PC Slave system is
established to act much like a network with no cables connecting
the individual workstations. Instead, each workstation is actually
a card installed into the bus on the "server." Alloys' own network
software is NTNX. Setup the hardware and software according to the
instructions from Alloy. If the slave cards are populated with 1
megabyte of memory, I recommend allocating 512K for the slave
partition and the remaining 512K as a system disk cache within
NTNX. The Osiris configurations on the slave cards are established
on the server hard disk exactly like any other network setup.

The individual slave cards may be accessed by connecting directly
to the cards via terminals (monitor & keyboard). Alloy cards also
operate with the utility program NXSCAN to control slave cards
from the server in real time without using additional terminals.

The NTNX software includes a utility to monitor each slave from
the server, although interaction is not possible. When operating a
slave system, all Osiris sessions MUST answer the phone by Auto-
Answer. Alloy uses the ring detect line, pin 22, to reboot the
individual slaves from the server.

(H293)
Osiris performs exceptional well under Windows 3.1. In fact, you
may find that on a 466/33 you can run as many as EIGHT nodes
, multiport intelligent serial card required.

Osiris has built in AUTO-DETECT time slicing functions for Windows
3.1. However, in order for the time slicing to function properly,
you'll need to use a memory manager that supports DPMI. The
"LATEST" version of QEMM and 386MAX 6.0+ both support DPMI

Osiris is a DOS application so set your PIF to reflect that and
allow Osiris as much XMS and EMS as it wants.

(H294)
Osiris performs exceptional well under OS/2 Warp. Actually,
Osiris runs faster under OS/2 Warp than it does under DOS.

OS/2 Warp does have one QUIRK that you have to work around,
loading DOS high.

If you load DOS high under OS/2 Warp, you will not be able
to run secondary command shells. Osiris lets command.com handle
running external applications via command shells but OS/2 Warp
will not allow command.com to do this if you load it high.

To overcome this nasty little quirk, don't load DOS high under OS/2
Warp.

Make sure you have direct access to timing ports turned OFF if
running multiple nodes.

Some DOS settings. You may or may not be able to use all of the AS IS.
This is from a P90 system with 32 Meg of RAM.

AUDIO_ADAPTER_SHARING=None
DOS_AUTOEXECv=C:\bbsEXEC.BAT
DOS_BACKGROUND_EXECUTION  On
DOS_BREAK Off
DOS_DEVICE=c:\os2\mdos\ansi.sys
DOS_FILES=20
DOS_HIGH  Off
DOS_RMSIZE=640
DOS_SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS
DOS_UMB Off
DPMI_DOS_API=ENABLED
DPMI_MEMORY_LIMIT= 4
DPMI_NETWORK_BUFF_SIZE=8
EMS_FRAME_LOCATION=AUTO
EMS_HIGH_OS_MAP_REGION=0
EMS_LOW_OS_MAP_REGION=384
EMS_MEMORY_LIMIT=2048
HW_NOSOUND  Off
HW_ROM_TO_RAM Off
HW_TIMER Off
IDLE_SECONDS=50
IDLE_SENSITIVITY=50
INT_DURING_IO  Off
KBD_ALTHOME_BYPASS Off
KBD_BUFFER_EXTEND Off
KBD_CTRL_BYPASS=NONE
KBD_RATE_LOCK  On
MEM_EXCLUDE_REGIONS=c000-c7ff
MEM_INCLUDE_REGIONS=
MOUSE_EXCLUSIVE_ACCESS
PRINT_SEPARATE_OUTPUT On
PRINT_TIMEOUT=15
SESSION_PRIORITY=1
SIO_Allow_Access_COM1  On
SIO_Allow_Access_COM2 Off
SIO_Allow_Access_COM3 Off
SIO_Allow_Access_COM4 Off
SIO_Idle_Sensitivity=50
SIO_Mode_DTR=No Change at OPEN or CLOSE
SIO_Mode_FIFO_Load_Count=16
SIO_Mode_IDSR=Ignore DSR During Receive
SIO_Mode_OCTS=HandShake Signal, as in RTS/CTS
SIO_Mode_ODSR=Ignore DSR During Transmit
SIO_Mode_RTS=HandShake Signal, as in RTS/CTS
SIO_Mode_XON/XOFF=No XON/XOFF flow control by SIO
SIO_Screen_Sync_Kludge Off
SIO_Share_Access_With_OS/2 Off
SIO_Virtualize_16550A  On
SIO_Virtualize_COM_Ports On
VIDEO_8514A_XGA_IOTRAP  On
VIDEO_FASTPASTE  Off
VIDEO_MODE_RESTRICTION=NONE
VIDEO_ONDEMAND_MEMORY On
VIDEO_RETRACE_EMULATION Off
VIDEO_ROM_EMULATION On
VIDEO_SWITCH_NOTIFICATION Off
VIDEO_WINDOW_REFRESH=1
XMS_HANDLES On
XMS_MEMORY_LIMIT=2048
XMS_MINIMUM_HMA=0

Below a functional config.sys that has been provided by
bfoot@bfoot.itc.com. A couple of the lines were rather long so
we wrapped them. You should have no trouble telling which ones.

IFS=C:\OS2\HPFS.IFS /CACHE:64 /CRECL:4
PROTSHELL=C:\OS2\PMSHELL.EXE
SET USER_INI=C:\OS2\OS2.INI
SET SYSTEM_INI=C:\OS2\OS2SYS.INI
SET OS2_SHELL=C:\OS2\CMD.EXE
SET AUTOSTART=PROGRAMS,TASKLIST,FOLDERS,CONNECTIONS,LAUNCHPAD
SET RUNWORKPLACE=C:\OS2\PMSHELL.EXE
SET COMSPEC=C:\OS2\CMD.EXE
LIBPATH=.;C:\OS2\DLL;C:\OS2\MDOS;C:\;C:\OS2\APPS\DLL;C:\MMOS2\DLL;
SET PATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\MDOS;
     C:\OS2\APPS;C:\MMOS2;C:\WINDOWS
SET DPATH=C:\OS2;C:\OS2\SYSTEM;C:\OS2\INSTALL;C:\;C:\OS2\BITMAP;
     C:\OS2\MDOS;C:\OS2\APPS;C:\MMOS2;C:\MMOS2\INSTALL;C:\WINDOWS
SET PROMPT=$i[$p]
SET HELP=C:\OS2\HELP;C:\OS2\HELP\TUTORIAL;C:\MMOS2\HELP;
SET GLOSSARY=C:\OS2\HELP\GLOSS;
SET IPF_KEYS=SBCS
PRIORITY_DISK_IO=NO
FILES=20
BASEDEV=IBMKBD.SYS
DEVICE=C:\OS2\INSTALL\IBMCSFLK.SYS C:\OS2\INSTALL\IBMCSFLK.LST
DEVICE=C:\OS2\BOOT\TESTCFG.SYS
DEVICE=C:\OS2\BOOT\DOS.SYS
DEVICE=C:\OS2\BOOT\PMDD.SYS
BUFFERS=90
IOPL=YES
DISKCACHE=d,LW
MAXWAIT=3
MEMMAN=SWAP,PROTECT
SWAPPATH=C:\OS2\SYSTEM 2048 100000
BREAK=OFF
THREADS=256
PRINTMONBUFSIZE=134,134,134
COUNTRY=001,C:\OS2\SYSTEM\COUNTRY.SYS
SET KEYS=ON
SET BOOKSHELF=C:\OS2\BOOK;C:\MMOS2;
SET SOMIR=C:\OS2\ETC\SOM.IR;C:\OS2\ETC\WPSH.IR;C:\OS2\ETC\WPDSERV.IR
SET SOMDDIR=C:\OS2\ETC\DSOM
REM SET DELDIR=C:\DELETE,512;D:\DELETE,512;E:\DELETE,512;F:\DELETE,512;
    G:\DELETE,512;H:\DELETE,512;I:\DELETE,512;J:\DELETE,512;
BASEDEV=PRINT01.SYS
BASEDEV=IBM1FLPY.ADD
BASEDEV=IBM2FLPY.ADD
BASEDEV=IBM1S506.ADD
BASEDEV=XDFLOPPY.FLT
BASEDEV=OS2DASD.DMD
SET EPMPATH=C:\OS2\APPS;
PROTECTONLY=NO
SHELL=C:\OS2\MDOS\COMMAND.COM C:\OS2\MDOS
FCBS=16,8
RMSIZE=640
DEVICE=C:\OS2\MDOS\VEMM.SYS
DOS=LOW,NOUMB
DEVICE=C:\OS2\MDOS\VXMS.SYS /UMB
DEVICE=C:\OS2\MDOS\VDPMI.SYS
DEVICE=C:\OS2\MDOS\VDPX.SYS
DEVICE=C:\OS2\MDOS\VWIN.SYS
DEVICE=C:\OS2\MDOS\VW32S.SYS
DEVICE=C:\OS2\MDOS\VCDROM.SYS
REM DEVICE=C:\OS2\BOOT\COM.SYS
REM DEVICE=C:\OS2\MDOS\VCOM.SYS
DEVICE=C:\OS2\OS2CDROM.DMD /Q
IFS=C:\OS2\CDFS.IFS /Q
BASEDEV=OS2SCSI.DMD
DEVICE=C:\OS2\MDOS\VCDROM.SYS
BASEDEV=SBCD2.ADD /P:220
BASEDEV=MITFX001.ADD /P:350
CODEPAGE=437,850
DEVINFO=KBD,US,C:\OS2\KEYBOARD.DCP
DEVINFO=SCR,VGA,C:\OS2\BOOT\VIOTBL.DCP
DEVICE=C:\MMOS2\SBAWED2.SYS 1 1 5 10 220 4 330 /N:SBAUD1$ /Q
DEVICE=C:\MMOS2\AUDIOVDD.SYS SBAUD1$
SET MMBASE=C:\MMOS2;
SET DSPPATH=C:\MMOS2\DSP;
SET NCDEBUG=4000
DEVICE=C:\MMOS2\SSMDD.SYS
DEVICE=C:\MMOS2\R0STUB.SYS
DEVINFO=SCR,BGA,C:\OS2\BOOT\VIOTBL.DCP
SET VIDEO_DEVICES=VIO_SVGA
SET VIO_SVGA=DEVICE(BVHVGA,BVHSVGA)
DEVICE=C:\OS2\ATI0.SYS
DEVICE=C:\OS2\ATIM64.SYS
DEVICE=C:\OS2\MDOS\VSVGA.SYS
DEVICE=C:\OS2\MDOS\VAD64.SYS
DEVICE=C:\OS2\MDOS\VMOUSE.SYS
DEVICE=C:\OS2\BOOT\POINTDD.SYS
DEVICE=C:\OS2\BOOT\MOUSE.SYS
DEVICE=C:\SIO\SIO.SYS (COM1:38400) (COM2:38400) (COM3:38400,3E8,9)
DEVICE=C:\SIO\VSIO.SYS
RUN=C:\OS2\INSTALL\IBMCSFLK.EXE C:\OS2\INSTALL\IBMCSFLK.LST
REM FaxFaxFaxFaxFax -- Please do not modify this group of lines
IOPL=FxPrint
DEVICE=C:\FaxWorks\Fmd.sys
REM FaxFaxFaxFaxFax -- FaxWorks for OS/2
DEVICE=C:\OS2\APPS\SYSIOS2.SYS

(H295)
The VAST number of methods that CAN be used and the differences
that can exist between individual set ups forces us to limit
Technical support to only the OSIRIS interface.

I cannot offer setup, installation, operational help, or
maintenance support for other produces such as Desqview, Novell,
Lantastic, etc.

(H296)
Despite the method of multitasking, you will NEED to set your EXE,
COM, OVL (overlay), and OVR files to READ ONLY to prevent DOS
SHARE violations. When DOS loads an EXE or COM, it opens it in
READ/WRITE mode. If two or more nodes attempt to LOAD the same
program, a protocol driver or archiver, you can get a share
violation. Since this is external to Osiris, I cannot trap it.

I have included a program in the package, setlock.exe, that allows
you to MASS set, in the current directory, EXE, COM, OVL, and OVR
files to READ ONLY.

The program is easy to use. Log into the directory and type
SETLOCK /L <ENTER>. This sets all the COM, EXE, OVL, and OVR files
in the current directory to READ ONLY.

If you need to set them back to READ/WRITE, to delete or replace
one of the programs, log into the directory and type SETLOCK /U
<ENTER>. This will set all the COM, EXE, OVL, and OVR files in the
current directory to READ/WRITE mode and you can make the required
changes. But, don't forget to change them back to READ ONLY.

(H297)
First, I'm assuming you've already read the sections in this help
file labled;

Multiple Nodes
    Local Area Networks
    Novell
    Lantastic
    Desqview
    Slave Cards
    Windows
    OS/2 WARP!
    Help
    Despite The Method, Read This.

If not, read those sections first and then come back to this one.

Setting up a second, or 3rd, node is just as easy as setting up
the first one.

Load SM and go to the NODE section. When asked which node, enter
2.

SM will tell you that node doesn't exist and ask that if you want
to create one, answer Yes and fill out all the fields.

Copy your ACCESS1.BBS file to ACCESS2.BBS.

Copy your MDMSTR1.BBS file to MDMSTR2.BBS.

Copy your RUNBBS.BAT file to RUNBBS2.BAT.

Edit RUNBBS2.BAT and on the line that runs Osiris, change -N1 to
-N2

If you are using DV, Windows, or OS/2, open a new window and log
into the OSIRIS directory and run the RUNBBS2.BAT

If you are using a network, log onto the the OSIRIS directory from
the workstation and run RUNBBS2.BAT.

(H298)
                 Store restrictions

A) A maximum of 300 departments (depending on the AMOUNT of FREE
memory you have available, you may get more).

B) A maximum of no more than 9,999 products PER department.

C) A maximum of 13, 70 character lines for the product's
description.

First, create a sub-directory called online. Create  this
directory in your OSIRIS= Directory.

NOTE: Please  use ALL the names I use. It'll help a lot when or
if  you need help.

You'll  put  the information files about the  on-line  store,
databases, in this directory.

You'll  place all of them there except for 'STORE.DEF'.  This  is
the  file  you create that tells ME  where  to  find  the  product
databases for a certain store. The Store.def MUST  be  placed in
the Osiris directory.

The  Store.def  file contains one line per store.  This  line
consists of THREE parts.

Part  one  is the name (first and last) of the person responsible
for answering QUESTIONS  about the store and ends with a comma.
That person MUST have a user record.

Part two is the NAME of the store, e.g. Walmart,  and  ENDS  with
a comma.

Part three is the full drive and path to the directory, the one
you just created.

Sample: Sam Walton,Walmart,C:\Osiris\online

Did you notice the commas?

This  is  used to divide the different fields. There should be NO
spaces following the comma  and the  start  of the next field.

If  you're going to have more than one store, add a line  for
each store you add.

Make  SURE  you  use  a  different  sub-directory  for   EACH
INDIVIDUAL store.

e.g.
Sam Walton,Walmart,C:\osiris\online
John Brown,The Business Store,C:\Osiris\online2

Next create, in your OSIRIS= directory, a sub-directory called
STORE.

The order forms, help menus, etc. for the store system must be
placed in this directory.

Now, unarchive the file called STORE.ZIP. This archive contains
the help file, HELP.MMU, a sample SPL/I order form, ORDER.SCR, and
DBEDIT.

Move HELP.MMU and ORDER.SCR to the sub-directory STORE, located in
the OSIRIS= directory.

DBEDIT is used to create and manage the product databases for the
stores.

Next, create a file called STORE.TXT. STORE.TXT should contain a
menu listing the store number(s) and the name of each store you
have on your system, even if you only have ONE store.

The stores are numbered starting with 1 in the same order they are
listed in STORE.DEF.

Assume store.def contained:

Sam Walton,Walmart,C:\osiris\online
John Brown,The Business Store,C:\Osiris\online2

Store.txt might look something like this:

1. Walmart Super Store      2. The Business Store

Now, compile store.txt with MMU.EXE and move STORE.MMU to the sub-
directory STORE, located in your OSIRIS= directory. This is
displayed when the caller selects to change stores.

The PRIMARY menu for the on-line store is held in the BLKTXT
language file so you don't have to do anything with that.

Now you are ready to create the actual product databases using
DBEDIT.

(H299)
Change into the directory that contains or WILL contain the store
data files, the ONLINE directory, THIS IS IMPORTANT!

DBedit does NOT read the store.def and will NOT go TO the
database.

Now, simply type DBEDIT from the DOS prompt.

When DBEDIT comes on-line, it checks for PROBOARD.QBS.
PROBOARD.QBS is a DATABASE containing the names of the
departments, vendor, and access level for each department.

If Proboard.qbs does NOT exist, DBEDIT will create it and add a
DEFAULT department to get you going. You can, and likely will,
edit that department to suite your own set-up.

After the check for Proboard.qbs, DBEDIT will validate the PRODUCT
databases for EACH department. If one is missing, it will create a
new one. That means, and this is important; IF for any reason you
find a product database is BAD or CORRUPT (maybe a cross linked
cluster) you can DELETE the database and DBEDIT will RECREATE it
for you.

DBedit is MODELED after OSM  and that means it is MENU and
MOUSE driven. That also means to SELECT a menu option, move your
MOUSE curser to that OPTION and CLICK the LEFT mouse button. To
EXIT DBedit, click the RIGHT mouse button.

The TOP menu bar has TWO primary options: DEPARTMENTS and
PRODUCTS. The RIGHT half of the menu bar lists the NAME of the
CURRENT department. DBedit will automatically select the FIRST
department listed in PROBOARD.QBS when it starts.

When you move the MOUSE cursor to the DEPARTMENTS option, a
SUBMENU will automatically drop down.

The SUBmenu contains: Set Department and EDIT, Add, View
Departments. EDIT, ADD, VIEW Departments is a single option.

(H300)
Set Department lets you SET the department you'll be working WITH
when you EDIT, ADD, DELETE, or VIEW products.

To select this option, move the cursor so that it is HIGHLIGHTED
and click the left mouse button. DBedit will OPEN a window listing
the NAMES of the departments. Move to the department you want and
click the LEFT mouse button.

You can also move with the UP/DN arrow keys, Pgup, PgDn, HOME, and
END keys.

To SCROLL the menu with the mouse, move to the FIRST or LAST
department name and hold DOWN the RIGHT mouse button.


(H301)
From here you can ADD, DELETE, EDIT, and VIEW department
definition records.

Each record contains the NAME of the department, the VENDOR or
VENDER depending on WHICH part of the country you live in as both
spellings are considered to be correct, and finally the ACCESS
level for that department.

The menu options are: ADD, DELETE, ->, <-, GOTO, and EXIT.

Move the mouse cursor to the options BOX and CLICK the left
button.

To EDIT a field in an EXISTING record, move to that field and
CLICK the left mouse button.

(H302)
From here you can view, edit, add, or delete PRODUCT database
records for the CURRENT department.

Your MENU options are: EXIT, DELETE, ADD, ->, <-, and FIND.

To select a menu option, move to the options BOX and click the
LEFT mouse button.

To EDIT any field, move to that field and click the left mouse
button. The ONLY exception to this is the DESCRIPTION. To EDIT the
description, move to ANY description line and CLICK the left mouse
button. This will drop you into the EDIT description subsystem.

(H303)
The only field in this record that isn't fairly plain is ORDER
FORM.

This is the name of an SPL/I command file that YOU create that
takes the order for THIS product.

Do NOT enter a file extension. Enter only the FIRST EIGHT
characters (maximum). I will add the extension of .PRG.

This file MUST be placed in the STORE sub-directory, located in
the OSIRIS= directory.

We've included a sample order  form, ORDER.SCR.

(H304)
Once you have ENTERED this subsystem, simply MOVE the mouse cursor
to any line and CLICK the left mouse button to EDIT that line.
When you are DONE, move to the BOX labeled DONE and CLICK the LEFT
mouse button.

You will THEN be asked for to CONFIRM that you want the PHYSICAL
record updated.

(H305)
When you click on ADD, the CURRENT product record will be COPIED
to a NEW record, except for the description. This lets you USE
exist FIELD from the CURRENT record, such as ORDER FORM, CAT. NO,
and TERMS with  minimum effort. You may CLEAR the field, pressing
ESC or clicking MIDDLE mouse button and type in TOTALLY new
information or you can just EDIT the field.

When you reach the DESCRIPTION part of the record, you will be
placed on the FIRST line of the description. Type in the
description, you'll will AUTOMATICALLY wrap to the next line when
you reach the end of the current line.

Enter a BLANK line when you are DONE with the description.

When you have finished with the description, you'll be placed in
EDIT DESCRIPTION mode. If you made any TYPING errors, you can
correct them from here.  Just click on the LINE you want to edit
and when you are DONE editing, click on DONE.

(H306)
When you select this option, DBEDIT places HEX 0x01 (a smiling
face character) as the FIRST character of the product NAME. This
indicates the record is MARKED for removal. If you wish to
UNDELETE a record, edit this field and replace the first character
of the name, HEX 0x01, with the ORIGINAL first character.

You MUST do the UNDELETE PRIOR to EXITING the PRODUCT subsystem.
Once you EXIT, it is TOO late to undelete.

If you DO delete a record or records, DBEDIT will PHYSICALLY
remove the records when you select the EXIT option.

(H307)
Find gives you a way of locating a particular product record
without having to move from record to record with the ARROW boxes.

Find gives you three options: Search on Name, Search on CAT. No.,
and search on ORDER FORM.

A lot of times, you'll use the same ORDER FORM for a specific
group of products and you may need to HUNT down those records from
time to time.

The SEARCH always starts on the NEXT available record. If you are
on the FIRST record, the search will start with the SECOND record.
If you are on record no. 100, the search will start on record #
101. I think you can see the advantages of this without having it
explained to you.

(H308)
Just pick a slot on one of the command records and define it as an
external program then enter the name of the batch file that runs
the game. Select the key to active that slot and add something to
your menu telling folks what it is.

Create a batch file that can:

a) Copy DorinfoX.def or Door.Sys (they are in the OSIRIS=
directory) to the GAME directory. If the game uses something other
than one of these, use Door Master or Qkdoor to generate the
appropriate control file and copy that into the game directory.

b) Change into the game directory and run the game.

c) That's it, there is nothing else to do.


You can do this to ANY command record but you MIGHT want to just
create a whole new subsystem for games, nice and easy isn't it?

(H309)
If you have a busy system, you can stop the same caller from
logging back-on until someone else has had a chance to log-on.

To engage this option, create a file in your osiris directory
called "laston."

The file "laston" contains two fields, elapse time and access
level.

e.g.

Copy Con Laston<CR>
10 20^Z

Field one, elapse time, is the maximum amount of time the system
stands idle. If no one calls within the time frame specified, the
caller may log back on.

Field two is the access level needed to bypass the laston feature.
Used to allow co-sysops, area moderators, paying customers, etc.
to log-on back-to-back.

If this option is active and the same caller attempts to log back
on I'll show, if it exists, the text file called "last_on.mmu."
You can briefly explain that you don't allow back-to-back log-on
and ask the caller to wait till someone else has had a chance to
call or until the in-activity time, field one, has elapsed.

Last_on.mmu MUST be in the OSIRIS directory.

(H310)
You're given the option of having your name withheld from the user
list display. This goes along with the ALIAS names to offer some
degree of privacy.

When you request a user list display and I come across any caller
not wishing to have his or her name display, I'll use "Private
Listing" in place of the name and "XXXXXXXXXXXXXXX" in place of
the city. Your caller list will NOT be blank under any conditions.

Those having the privacy switch turned on will not be listed as
last caller to the system and will not be able to receive CB
internode Email.


(H311)
When you select SM/MISC/PROTOCOLS, you'll get a screen that looks
something like this:

╔═══════════════════════════════ Protocol.Bbs ══════════════════════════════╗
║                                                                           ║
║ Display Name                           Access Level 0                     ║
║                                                                           ║
║ Protocol                                                                  ║
║                                                                           ║
║ Slow Speed Percentage 0       High Speed Percentage  0                    ║
║                                                                           ║
║ Times Used  0                 [ ] Batch Protocol                          ║
║                                                                           ║
║ Send Cmd                                                                  ║
║                                                                           ║
║ Recv Cmd                                                                  ║
║                                                                           ║
║                  Send/Recv CMD Special Character Sequences                ║
║                                                                           ║
║          *B Place Connect Rate Here     *P Place Port Number Here.        ║
║          *L Place Uart Rate Here        *F Place File Name Here.          ║
║          *U Place Sendx.Ctl Name Here   *N Place Node Number Here.        ║
║          *T Place Path To Bidirectional UPload Directory Here.            ║
║                                                                           ║
║         Jump▄ First▄ Last▄ Add▄ Del▄ Next▄ Prior▄ Exit▄ Update▄           ║
║          ▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀  ▀▀▀  ▀▀▀▀  ▀▀▀▀▀  ▀▀▀▀  ▀▀▀▀▀▀           ║
║                                Record 1 of 1                              ║
╚═══════════════════════════════════════════════════════════════════════════╝

To edit a field, click on the field using the LEFT mouse button.
Data entry field editing commands for this section are listed below.

Key                Command/Action

Backspace          Rubout last character
Left Arrow         Character Left
Right Arrow        Character Right
Delete Key         Delete CURRENT Character
Home Key           First Character Of Field
END Key            Last Character Of Field
Insert Key         Toggle Insert Mode
Ctrl Left Arrow    Previous Word
Ctrl Right Arrow   Next Word
Ctrl HOME          Clear Field
Ctrl END           Clear From Current Position To END Of Field

Screen may be scrolled using the SCROLL bar on the RIGHT side of
the screen, PGDN, PGUP, UP ARROW or DOWN ARROW.

Osiris is setup to use a control file called "protocol.bbs" to
define the protocol names, programs to use, and the
command line to send and receive files. I have included a
Protocol.bbs mapped to use my protocol drivers.

This allows, providing you have a suitable protocol driver,
up to 32722 protocols.
                         How It All Works

Osiris uses the protocol.bbs file by assigning a number to each
protocol. The position in the file is the protocols number.
For instances, if the first protocol defined is Zmodem and it
is in the default protocol.bbs file, then Zmodem would be
referenced as protocol number one (1).

I'll take care of formatting a display screen listing your
available protocols.

                           Display Name

The name of the protocol, the one shown to callers. Generally this
is not important to Osiris EXCEPT for you zmodem driver. The
Zmodem driver MUST have the display name: Zmodem

                             Protocol

This field contains the name of the actual protocol driver, e.g.
ZMODEM.EXE.

A file extension, .EXE or .COM, is optional. But, if the protocol
driver is NOT in a PATH directory you MUST include the full drive
and path as well as the name.


NOTE: If you are running MULTIPLE lines under OS/2, make sure you
set all the protocol drivers to READ ONLY.

E.g. C:\OSIRIS\AUXPRGS\ZMODEM.EXE

Had C:\OSIRIS\AUXPRGS been in the DOS Path, then I could have
simply used 'ZMODEM'.

                             Send Cmd

This field should contain the entire command line need to
send a file or group of files and you would use the special
embedded protocol characters, defined later on, to tell me
what to put where.

                             Recv Cmd

This field should contain the entire command line need to
receive a file or group of files and you would use the special
embedded protocol characters, defined later on, to tell me
what to put where.

         Slow Speed Percentage And High Speed Percentage

I'll use these fields for figuring transfer times and they should
contain the AVERAGE percentage, based on 100 percent, of
efficiency. Efficiency is how well the protocol performs at any
given baud rate with 100 percent being perfect.

No protocol drive can give you 100 percent performance but vFAST
is about as close as you can get. vFAST is so close that we figure
it at 100 percent but it is really something like 99.8.

The protocol.bbs file, included in the Osiris package, has already
been set-up with percentage rates. You can use those as a guide
when adding NEW protocols.

                            Times Used

Shows the number of times this protocol has been used for a file
transfer.

                        [ ] Batch Protocol

This field, set to Yes or No, tells me whether or not the
protocol can handle BATCH downloads.

                           Access Level

This is the access level you have to have to USE this protocol.
This is to accent the ANTI-PMS system. If you don't have access to
a specific protocol, I'm not going to bother to HIDE it.

                   Embedded Protocol Characters

You will need a method of passing the com port, baud rate, and the
name(s) of the file(s) to be sent or received. Therefore, 7
special two character sequences have been reserved.

*L : Locked Serial Rate
*P : Com Port
*U : Use File SEND control file (MUST BE LAST ITEM LISTED)
*P : Replaced with the SERIAL port number.
*T : Place full drive and path to the temporary upload directory
     for this node.
*B : I'll place the CONNECT speed here.
*F : means place the file name to SEND or RECEIVE here.
*D : Means place the name of the LOG file here.

If the protocol uses *F, it is assumed to be a NON-BATCH protocol.
All protocol drivers we've tested, to date, support a SEND control
file.

*U means place the names, including drive/path, of the files to
send in a control file and pass the name of the control file to
the protocol driver. I'll generate the name of the control file
and it'll be called SENDxx.CTL with xx being the NODE number the
caller is on.

The control file will be placed in the Osiris system directory and
the full drive, path, and name WILL be passed to the driver.

e.g. Assuming you are using my drivers then

-@*U

would translate to -@C:\OSIRIS\SEND1.CTL

Providing C:\OSIRIS was the Osiris system directory and the caller
was on NODE 1.

You MUST use the *U approach if you're going to allow your callers
to take full advantage of the file queue system. Otherwise they'll
be restricted to downloading only 1 file at a time. *L - SERIAL
LOCK RATE and is primarily for protocol drivers I didn't write but
need to have the serial lock rate passed to them.

                            Logging

Osiris requires all protocols, ours or third party, to report
files sent using the DSZ.LOG format.

Osiris uses this log when it SENDS files to determine which files
were and were not sent. Files that are UPLOADED are handled
differently and a LOG is not needed.

The name of the log file can be supply two ways, with an
environment variable or with a command line switch.

To support the command line approach, there is a variable
available in the protocol.bbs record, *D. *D means replace these
two characters with the name of the log file.

If you were on node 1 and the OSIRIS= directory is C:\XLT, *D
would be replaced with C:\XLT\DSZ1.LOG

If you were on node 2, C:\XLT\DSZ2.LOG

The name of the log file is also supplied by the environment
variable DSZLOG=

You do *NOT*  define this environment variable!

Osiris will define it for you prior to a file transfer and then
remove it AFTER the transfer has been completed.

After a download, the lines in the DSZx.LOG that reference  files
that was actually sent, are appended to the XLTx.LOG and the
DSZx.LOG is deleted.

Any line in the DSZx.LOG that begins with E, S, or L is skipped.

E=Error. Some type of error occured and the file was not sent.

S=Skipped. Simply means the file was SKIPPED. Generally, the
receiver already had it and the caller just forgot.

L=Lost Carrier. Carrier was lost before this file was sent.

This should give  you considerable flexiblity when it comes to
selecting protocol drivers. If you don't like our Zmodem and want
to switch to DSZ, the only thing you'll lose is the name of the
person doing the downloading.

To avoid confusion, I should point out that you do NOT have to do
anything when using *OUR* protocol drivers. They are geared to
work with Osiris and the DSZx.LOG automatically.

                     Bi-directional Protocols

Osiris does have internal support for bi-directional or full
duplex protocols such as Bimodem and HS/Link.

To set-up a protocol as bi-directional, simply include the *T
switch with the appropriate protocol command line argument that
indicates where the upload directory is located.

E.g., HS/Link would use -U*T

If node 1, I would replace that with

-UC:\OSIRIS\UPL1.TMP

When the caller selects the files he wants to download, he may
have HS/Link or Bimodem send the files he wants to upload.

Bi-directional transfers CAN be an asset if you have callers
willing to upload files and they are using 2400 baud modems.

                           Restrictions

Be forewarned, bi-directional transfers are VERY CPU intensive.
Your computer may be able to handle bi-directional transfers at
2400 baud but it may not be able to handle them under v32, v32bis,
or vfast connects.

Bi-directional transfers at speeds higher than 2400 baud RARELY
work under Windows, Desqview, or when Network software is in
memory unless you have an intelligent serial card.

Bi-directional transfers at speeds higher than 2400 baud generally
requires a 16550 highspeed uart.

Bi-directional transfers will not work with USRobotics 14.4, Hayes
9600v series, TeleBit PEP, CompuCom CSP, and several other
highspeed modems.

You will get credit for uploading files, but ONLY the Kilobyte
credit. Since I cannot determine the exact amount of time that was
spent uploading, you will not get TIME BACK credit.

(H312)
Who wouldn't want these 10 essentials the competion considers as 
options you must buy.

 1. Internet Gateway.
 2. 3 built-in Accounting systems.
 3. Built-in programming language.
 4. Built-in QWK.
 5. Built-in Bluewave.
 6. Built-in Database Retrieval System.
 7. Built-in Classified Ad System.
 8. Built-in Document Retrieval System.
 9. Support For Multiport Intelligent Serial Cards.
10. Built-in Fidonet Mailer.

The Fidonet Mailer and the Interent Gateway would cost you over 
$200 dollars in most other BBS packages, if they are even 
available!

Call Mustang Software, MediaHouse, TBBS, Exalibur, Galacticomm, or 
a dozen other BBS developers and ask them if a built-in Fidonet 
mailer and Internet Gateway are part of their BASE package or do 
you have to pay extra.

Even with ALL these features, the price for a 2 line Osiris system 
is only $150.00!

We'll also give you FREE upgrades for a full year, FREE lifetime 
voice support, and FREE life time BBS support.
(H313)
Once your free years worth of upgrades has expired, upgrading to
the next version costs $50.00 for the two node version.

For more than 2 nodes, add an additional $5.00 per node.

Examples of upgrade costs:

2 Node  :  $50.00
3 Node  :  $55.00
4 Node  :  $60.00
5 Node  :  $65.00
6 Node  :  $70.00
7 Node  :  $75.00
8 Node  :  $80.00

When you upgrade and receive your new Osiris.dll, you'll also
receive another year's worth of free upgrades.

(H314)
You can add additional nodes 1 node at a time or in any
combination at ANY TIME.

Adding an additional node costs $45.00 per NODE. If you add
10 or more nodes, the cost is $30.00 per NODE.

Adding additional nodes also EXTENDS your 1 year free upgrades.
If you purchase a 2 Line Osiris system in Oct. 1994 and add 2
more lines in March 1995, your year's worth of FREE upgrades
will be extended to March 1996.

(H315)
A few networks use the QWK message format to exchange conference
mail between different BBSes.  This should not be confused with
PcRelay. PcRelay is a proprietary format and you have to purchase
PcRelay software from the PcRelay folks.

QWK echomail is broken into TWO parts, HUB and NODE. HUB's feed
nodes, nodes get conferences FROM the HUB and send mail back to
the HUB. Nodes do not feed other Nodes.

QIN and QOUT is NODE software. You can send mail BACK to the HUB,
but you cannot send mail to other NODES.

How you GET Qecho bundles from your HUB and how you SEND replies
or messages that originated on your system back is entirely up to
you.

Networks that USE this format do NOT use mailers. You have to log
onto the HUBS BBS and DOWNLOAD mail and UPLOAD the replies or
original messages back to the HUB. You can either do this manually
or use something like TELIX Scripts to handle it automatically.

Yes, it is a bit archaic, time consuming, and in some cases very
expensive compared to Fido Style echomail.

The Qecho utilities can be found in the archive QECHO.UC2 on our
BBS.
(H316)
The QEcho programs require two control files, the first is a
static, the name cannot be changed, control file called QWK.CTL

QWK.CTL contains the path to the DIRECTORY where the you will be
placing the QECHO archives you receive from your HUB,  the HUB ID,
Phoenix Domain Address, and the archive format (for EXPORTING).

HUB ID is the primary part of the FILE name (NOT including file
extension and period) used for the QWK bundles.

The Archive format is a number defining the TYPE of archiver to
use when EXPORTING.

1 = Pkzip
2 = Arj
3 = Lzh
4 = Pkware Arc

Eg.

PATH TO INBOUND STORAGE AREA
HUB_ID ARCHIVE_TYPE

Sample:

C:\HUB
GENESES 2
BLUEQ 1

You can have up to 30 "SYSTEM_ID DOMAIN_ADDRESS ARCHIVE_TYPE"
lines, one after the other. This allows you to pull QECHO from up
to 30 different HUBS.

The SECOND control file is an AREA control file and the NAME will
vary depending on the HUB ID.

Take the following QWK.CTL file:

C:\HUB
GENESES 2
BLUEQ 1

You would create TWO area control files. One named GENESES.CTL and
one named BLUEQ.CTL.

The area control file lists the NETWORK conference numbers and the
corresponding OSIRIS area number, one set per line, up to 5000
lines.

10 2
33 9
22 10

10 is THEIR conference number (this is generally FIXED/PREDEFINED
for the entire network) and 2 is the OSIRIS message area FOR that
conference.

33 is THEIR conference number, 9 is the OSIRIS message area.
22 is THEIR conference number, 10 is the OSIRIS message area.

(H317)
To SET-UP an Osiris message area for Qecho, you should define the
board TYPE as ECHO and the message type as ASP or REVIEW. Most
Qecho conferences do not allow an alias. You should ALSO turn WORD
WRAP OFF.

Remember, TURN WORD WRAP OFF for that message area. If you don't,
you're replies will cause the Pcboard and Wildcat BBS programs to
CRASH (poor programming).

(H318)
QIN.EXE imports Qecho into the Osiris message base. Once you have
retrieved a QWK mail bundle from you HUB, place that bundle in the
directory defined in QWK.CTL and run QIN.EXE to check for incoming
Qecho.

Qecho will look for either HUB_ID.QWK or HUB_ID.REP (HUB_ID is the
HUB_ID defined in QWK.CTL).

QIN will exit with ERRORLEVEL 1 if it imports mail and ERRORLEVEL
0 if it does not.

(H319)
QOUT Exports messages posted on YOUR system back to the HUB using
the QWK REP format. QOUT will only export messages that ORIGINATED
on your system. Messages imported by QIN are ignored. QOUT places
the message bundle in a sub directory in your OSIRIS directory
called QECHO.

If you Osiris directory is C:\OSIRIS, QOUT would place the reply
bundle in C:\OSIRIS\QECHO

Because QWK uses a single STATIC reply file that cannot be added
to, QOUT will skip the EXPORT if the *.REP file already exists.

After you upload the REP back to the HOST, make SURE you delete
it.

(H320)
PrimeStar brings the Windows GUI Interface to ALL your callers 
without requiring Win 3.1, WFW, or WIN NT.

PrimeStar uses advanced RIP graphics to bring the Windows GUI to 
DOS, Windows, OS/2, Unix, Mac, and Amiga users without requiring 
yet another custom terminal program.

Forcing your callers to use a specific terminal program, owning a 
specific brand of computer, and using a specific operating system 
is not going to win you a lot of friends or make your customer 
very happy.

RIP, Remote Imaging Protocol, is used to transmit graphic images
via a communications link. RIP instructs the remote terminal to
interact with Osiris in a graphical, mouse-driven environment.

You can also use RIP to add graphics, charts, images and diagrams
to electronic mail, forum messages, and file descriptions to
provide a clearer understanding of their information and ideas.
The on-line community now has the means to communicate with
sophistication and ease. Users that found on-line systems to be
confusing and difficult may now easily navigate Osiris by clicking
their mouse on graphical images, like Prodigy(TM) and America
Online(TM).

Future plans for RIP include 24-bit color, transmittable bitmaps,
sound support, a resolution independent coordinate system, and
full motion video - complete multimedia capabilities.

RIP graphics may be viewed using a number of terminal program. 
There are to many to list here so we've only listed the most 
popular. Some are shareware, some freeware, and some commercial.

Ripterm
Telix For Windows
Qmodem Pro For Windows
Qmodem Pro For DOS
Argus (Windows, DOS, and MAC versions available)

We have RIPterm and Argus available on our BBS.

To create RIP menus and display screens, you'll need a draw 
program that supports RIP.

Some of the Draw programs:

Deadpaint
Flatline
RIPaint
Jdraw

RIPaint is the best, but it is also the most expensive. Jdraw is 
the next best and a SHAREWARE version is available on our BBS.

(H321)
The mistake most sysops make when setting up their first graphic
based BBS is going overboard.

When you create menus or other graphic files, be care when it
comes to using ICONS, JPEG, and WAV sound files.

While they are nice to look at, they don't actually make the
system easier to use and once you have seen them a couple of times
they become OLD HAT.

Keep in mind that most of your callers will *NOT* have 486 DX
100's or P-90's with graphic accelerator cards and displaying
jpeg files can be quite time consuming. So, try to avoid creating
a menu out of a JPEG or use several JPEG on a menu.

Of course, this is entirely up to you but we suggest the
following: If you want to get really fancy with the graphics,
don't do it on your PRIMARY menus. Primary being defined as menus
your callers are going to see a lot.

Another thing you'll want to keep in mind is the overall number
and size of ICONS, JPEG, and WAV files.

Your callers have to download these files (only one time)  and if
you have a couple of hundred files totally a meg of so, that is
going to turn a lot of people off. Try to keep the COMBINED size
"all ICONS, JPEG, and WAV" to less than 400K.

(H322)
All the internal PrimeStar RIP screens, about 350, are held in the
following files:

RIP.BBS
RIP.IDX
BUTTONS.BBS

(H323)
Osiris has an internal Graphics and Sound manager, simply called
GUS. GUS will check the callers hard drive to make sure he or she
has ALL the ICONS, ICONS Masks, HOT ICONS, SOUND FILES (including
Sound Blaster and MIDI WAV files), and local PLAYBACK rip scenes
used on your system.

To engage this feature, create a subdirectory in your OSIRIS=
directory called ICONS. Copy all the ICONS, Sound files, local
playback, etc. you use to this directory.

Plug in either FORCE ICON or ASK ICON in a STARTUP.BBS slot.

         ICON checking on a PER command record bases

You can define special ICON checking when entering a specific
command record by defining a special sub-directory called ICON.BBS
in the MENU directory for that command record.

Assuming you have a command record setup for ON-LINE games and the
MENU directory is C:\OSIRIS\GAMES

You would create the directory C:\OSIRIS\GAMES\ICON.BBS and place
all the game ICON/WAV/JPEG files in that directory.

When someone changes to the GAME command record, chain command or
jump, Osiris will check to see if they have the ICON/WAV/JPEG files.

I'd only use something like this for a game section because not
everyone plays games.

(H324)
Most of the internal PrimeStar RIP screens can be modified.

First, create a work directory some place and decompress the
archive BLDRIP.UC2 into that directory.

You'll find about 240-250 individual files with the .XLT extension
along with a program called BLDRIP.EXE.

The individual .XLT files are the ones you want to modify.

The first thing you have to decide, before you do anything with
the screen, is: Is it a WINDOWED screen or a NON-WINDOWED screen.

Load that file in RIPaint and use the LIST command.

If you see $STW$, $SMF$, $MKILL$, and Img->Clip then you know the
screen uses a WINDOW and you have to be very careful about editing
it.

First thing is the Img->Clip. That means the entire screen must
fit within the CLIP region.

You can EXPAND the CLIP region but you can only expand along the
X1 axis or the Y1 axis.

The X0 axis and Y0 axis MUST remain the same.

Basically, that means you can expand the CLIP region to the RIGHT
and DOWN but you cannot expand the CLIP region to the LEFT or UP.

Save the screen with the following settings:

File Width : 2000            Leading C/R   :
Max Size   : 0               Kill Fields   :
WordWrap   : X               Reset Windows :
1 Cmd/Line :                 Auto-Optimize :
No Text Win: X               Add CLS       :

If the screen does not have  $STW$, $SMF$, $MKILL$, and
Img->Clip then it is not a WINDOWED screen and you save the screen
using:

File Width : 2000            Leading C/R   :
Max Size   : 0               Kill Fields   : X
WordWrap   : X               Reset Windows :
1 Cmd/Line :                 Auto-Optimize :
No Text Win: X               Add CLS       :

Never Optimize a screen.

After saving a screen, run FIXRIP.EXE on the screen.

Recompile the RIP.BBS file using the BLDRIP.EXE program, copy the
new RIP.BBS and RIP.IDX over to the proper directory (the one
defined in SM/NODE), call in remote and check out your changes.

(H325)
The RIP Ad System or RAS is a PRODIGY (tm) style graphic ad system
and it displays rotating graphic ad's on the callers screen.

RAS uses a graphic window, the window is saved and restored, to
display the AD. The LOCATION and SIZE of the window is defined in
LANG.DAT (lang.txt) on line 407. The location is in base 36 format
and consists of the upper and lower X/Y corners of the window. Any
ad you create must fit within those borders.

"WHEN" an Ad is display is defined on line 406, Lang.dat/lang.txt.
The time frame is in 1/100th second increments. For instances, 700
would be 7 seconds and that also happens to be the default. If you
used 700, an ad would be displayed when the caller sits at one of
the MAIN command record prompts longer than 7 seconds.

How "LONG" an Ad remains on the screen is defined on line 405 and
this line is also in 1/100th second increments.

"HOW OFTEN" an AD is displayed is defined on line 408. A 0 (ZERO)
means only ONE AD is displayed PER MENU. In other words, if you
were to sit at the MAIN MENU for 7 seconds, Osiris would only
display ONE AD. For another AD to be displayed, you'd have to
select some type of operation or hit RETURN.

A 1 (ONE) means show multiple AD's per MENU. After each AD has
been displayed, Osiris resets the "WHEN" timer and when that timer
expires, another AD is shown.

Osiris automatically rotates the AD's and when the last AD has
been displayed, we start over again.

The menu's commands are NOT locked out while an AD is on the
screen. In other words, the caller can select an operation without
having to wait for the Ad to disappear.

To create RIP ads, use RIPaint or a LIKE product and simply
generate RIP display files. Move ALL those RIP files to their OWN
directory. Where that directory is located isn't important.
Anyway, after you have all the RIP ad RIP files in their own
directory, log into that directory and run the program MKAD.EXE.

MKAD collects ALL the *.RIP files in the CURRENT directory and
builds a file called RIP_AD.BBS. RIP_AD.BBS is your Osiris RAS
database.

After you have created RIP_AD.BBS, simply copy it to your OSIRIS=
directory. Osiris will AUTO-DETECT RAS and automatically turn it
on.

Now, there are a couple of restrictions with respects to your RIP
RAS files. No individual RIP AD file can exceed 1024 bytes and you
MUST save the RIP files with the following scene output options:

Leading C/R        NO
Kill Fields        NO
Reset WIndows      NO
Add CLS            NO
1 CMD/LINE         NO
Word Wrap          YES
No Text Window     YES
Auto-Optimize      YES
File Width         1024
Max Size           1024

You may NOT use the CLIPBOARD. This is VERY important, your RIP AD
files cannot make use of the CLIPBOARD due to RIPscript v1.xx
limitations.

To make creating Ad's a bit easier, we've included a little AD
creation program, PAD.EXE. PAD was designed to work with the
default AD windows and generates rather nice looking, although
they are not "FANCY" two line AD's.

All you have to do is RUN PAD and type in the TEXT you want
displayed. We are only allowing TWO 75 character lines per AD. You
want it short enough to read in a brief time frame and two 75
character lines seems to be just about right.

PAD saves the RAS Rip file using the static file name "NEW.RIP".
Rename it to something different before you make the NEXT AD.

While you can makes AD's simple but nice looking (PAD), you can
get very fancy with ICONS, JPED, and digial sound.

While the RAS was designed with the AD concept in mind, you aren't
restricted to using it for ADs. Uses your imagination and come up
with unique uses for RAS.

(H326)
If you want to disable RIP graphics on your system, add
the command line switch /E to your runbbs.bat file.

(H327)
Osiris has a built-in RIP help screen that will be
displayed to anyone that has an access level equal
to the new user access level.

The display is shown during the log-on process and
basically reminds people about the question mark in
the upper right corner of SOME of the built-in RIP
screens.

If you want EVERYONE to see this screen, add /I to
the Osiris command line.
(H328)
Osiris supports EMBEDDED RIP screens in conference or forum
messages. If a message has an embedded rip screen, you'll see a
button labeled RIP FILE in the upper right hand corner of the
screen.

You must read the ENTIRE message before this "RIP FILE" will
appear, it's the only way we can make sure the entire rip screen
has been captured.

For a line of text to be PART of a RIP file, it must begin with
the RIP characters !| and ! must be in the first column just like
it does in a normal RIP screen.

A RIP sequence can also begin with ^A which allows it to begin in
a column other than 1 but since ^A is also used as a "HIDE THIS
LINE" command by Fidonet and other applications, we can't allow
that type of RIP sequence. Since none of the RIP draw programs
save with the ^A sequence identifier, that shouldn't present a
problem.

The messages can be part text like you'd put in a normal message
and part RIP screen. You can have the RIP screen as the first or
last part of the message or you can put a line of normal text
between each line of the RIP screen.

To get a RIP screen *IN* a message, you have to UPLOAD the
message. For what should be obvious reasons ,the full screen and
the line editor will not allow you to type in RIP seqences.

(H329)
You can define special ICON checking when entering a specific
command record by defining a sub-directory called ICON.BBS in the
MENU directory for that command record.

Assuming you have a command record setup for ON-LINE games and the
MENU directory was defined as C:\OSIRIS\GAMES

You would create the directory C:\OSIRIS\GAMES\ICON.BBS and place
all the game's ICON/WAV/JPEG/Local Playback files in that
directory.

When someone changes to the GAME command record, chain command or
jump, Osiris will check to see if they have all the required
ICON/WAV/JPEG/Local Playback files.

Personally, I'd only use something like this for something like a
game subsystem and then only if I had a FEW games that used
ICON/WAV/JPEG/Local Playback files.

If you have a lot of games, you may want to do something like this
on a PER GAME bases using SPL/I++, not everyone will play every
game. Here is a sample for LORD:

// SPL/I++ that calls up Lord and
// does ICON checking PRIOR to calling LORD.BAT for
// those using RIP.

// This requires Osiris XLT v3.05 or later and the SPL/I++
// compiler v3.0 or later.

main()
{

int rtcode;
if(_RIP)
{

// assumes C:\OSIRIS\LICON directory contains the ICONS for LORD
// If you use a different directory, change the next line to
// point to the proper directory.

    check_icons("C:\OSIRIS\LICON");

// I do a RIP reset prior to calling LORD and when returning.
// LORD sometime doesn't detect RIP if you don't do that.

// Btw, LORD.BAT copies the DOOR drop file to the LORD directory,
// changes into that directory, and calls up the LORD program.

    printf("\n!|*|#|#|#\n");
    execute(0,"lord.bat",rtcode);
    printf("\n!|*|#|#|#\n");
}
else
{
    execute(0,"lord.bat",rtcode);
}


}

(H330)
Under PrimeStar, when you plug in a DISPLAY FILE function into an
Osiris command record, Osiris uses an internal TEXT VIEWER to
display the file. Some INTERNAL functions will use the TEXT VIEWER
to display information.

The TEXT view can handle text files up to FIVE MILLION bytes in
less than 10K of memory.

You can page UP and DOWN using the scroll bar at the side of the
screen, jump to the TOP or BOTTOM using the buttons on the MENU
bar, or DOWNLOAD the contents of the viewer.

For security reasons, the TEXT VIEWER will neutralize any ANSI or
RIPscript sequence.

(H331)
When you click on VIEW and the file is an ARCHIVE, PrimeStar
brings up the ARCHIVE Manger.

The Archive manager will READ the archive and present you will a
LISTBOX showing the contents of the archive.

You can page up and down using the scroll bar on the right side of
the screen.

There is a SELECTOR bar that you move, click on the file, to
highlight a file.

Along the TOP of the display is a MENU bar with VIEW, EXTRACT,
FINISHED, and TAG ENTIRE Archive.

To VIEW a file inside the archive, highlight the file (click on
it) and then click on VIEW.

To Extract a file, highlight the file (click on it) and then
click on EXTRACT.

To Tag the ENTIRE archive for downloading, click on the TAG
button.

There is a SHORT cut to VIEWING a text file. If the file does not
have an EXE or COM file extension and is not an archive, double
click on the file and Osiris will assume you want to view it.

There is a SHORT cut to EXTRACTING a file. If the file has an EXE
or COM file extension or the file is an archive, double click on
the file and Osiris will assume you wnat to extract it.

There is a question mark in the upper righthand corner of
the screen. Clicking on this will bring up a help screen.

(H332)
ROLODEX (PrimeStar Only) allows each caller can keep up to twenty
80 character names and/or Internet addresses stored in their
private Rolodex.

When entering a message, you can have the TO field filled in from
your ROLODEX. Which can be VERY helpful when dealing with Internet
addresses.

From the Private E-mail area, one of the option is labeled
ROLODEX. Clicking on this button will let you EDIT, VIEW, ADD, or
IMPORT names into your ROLODEX.

To IMPORT a name, or internet address, first HIGHLIGHT the message
with the selector bar and then click on the ROLODEX button then
click on IMPORT.

The individual ROLODEX files are stored in the ROLODEX.BBS
directory, Osiris will take care of creating this directory.

A persons private ROLODEX is stored using that persons INTERNET
mailbox name. If they change their Internet name, their ROLODEX
file is automatically renamed.

(H333)
You can add, PrimeStar RIP menus, your OWN pop-up help screens.

Obvously, you can do this with anything using a DISPLAY FILE
function but this method will save you from having to use a
command slot.

Create a button and label it with a question mark. The
internal HELP screens use this and you need to use the same
symbol (keeps things the same and causes less confusion).

The button should send a ^B (Control B).

Create your RIP help screen and use the file name HLPxxx.RIP with
xxx being replaced by the Osiris.bbs record number. The record
number is displayed when you are viewing the Osiris.bbs records
with SM.

Copy HLPxxx.RIP to the MENU directory defined for that Osiris.bbs
command record.

(H334)
If you want to FORCE everyone to use PrimeStar (RIP), create a
file in your OSIRIS directory and use the file name "ONLYRIP".

The first line of this file should contain the name of the MAC
RIPterm program, the SECOND line should contain the name of the
DOS Ripterm program.

This allows you to CHANGE the name to reflect changes in VERSIONS.

This is how our ONLYRIP is constructed.

argusdmo.157
ripterm.zip

Both files MUST be in one of the file areas.

When someone logs on and they aren't using RIP, an internal screen
is displayed explaining that you have decided that you want
everyone to use RIP graphics and if you don't have a terminal
program that supports RIP, you can download one from this menu.

The caller can select one of the terminal programs to download or
elect to hang-up.

(H335)
There is a SHORT CUT method of moving a selector bar and selecting
something, just DOUBLE CLICK on it.

This short cut method is available in the following places.

File List
Archive Manager
New Upload Search
File Text Search
Message Center
Threaded Reader
Subject Reader
Fidonet E-mail Reader
Join/Unjoin Conference Area

(H336)
If you want OSIRIS to answer the phone, you'll need to create a
batch file to run Osiris and a modem response file. Simply typing
OSIRIS from the command line will not work.

First Create a BATCH file that looks somthing like this:

:TOP
OSIRIS -N1 -W
IF ERRORLEVEL 50 GOTO END
GOTO TOP
:END

I will exit with errorlevel 50 when you request a SHUTDOWN from
the keyboard. Otherwise I will exit with errorlevel 0 after each
call to CLEAR memory. That is why we always cycle back to the TOP,
unless errorlevel 50 is used.

You tell me you want to Go ONLINE and WAIT for a call with the -W
switch.

You must also fill out the NODEx.CFG fields: Modem Setup String,
Serial Port, and Baud Rate. The Modem Answer String field is option
and only used if the modem DOES NOT automatically answer the phone.

The modem string should: Set Echo OFF, Set VERBOSE result codes
ON, and Set AUTO-ANSWER on. You can also include any optional
commands your modem may require.

Example of a generic modem string: -WATH0E0V1S0=1S7=30

Next you will also need to create, in the Osiris directory, a
MDMSTRx.BBS and x should be replaced by the NODE number of the
node that is going to use this control file, text file listing
your modems response strings along with the connect rates to
associate with each string.

Example of MDMSTR1.BBS (control file for node 1):

CONNECT_28800 28000
CONNECT_26400 28000
CONNECT 24800 28000
CONNECT_21400 28800
CONNECT_19200 19200
CONNECT_16800 16800
CONNECT_14400 14400
CONNECT_12000 12000
CONNECT_9600 9600
CONNECT_7200 7200
CONNECT_4800 4800
CONNECT_2400 2400
CONNECT_1200 1200
CONNECT 300

You will notice the connect message cannot contain spaces. If the
message NEEDS a space, most all do, use the underscore character.
I will replace it with a space when I read the file.

You should also place the LARGER CONNECT Speeds at the TOP. A
sample MDMSTR1.BBS has been included in the XLT archives, 99.99
percent of you can use it as is.


(H337)
You can create a text file called NONAME.BBS in the OSIRIS
directory, containing a list of names you don't want callers to
use for PRIMARY NAME, ALIAS, and INTERNET MAILBOXES.

This isn't for filtering out names like SHITHEAD or ASSHOLE but
you're welcome to use it for that. This is for preventing people
from using names that you have for FTPmail, LISTSERVERS, and
other items.


(H338)
If you do have to change your password periodically, you can have
Osiris track the time for you.

When you have called 10 times, I'll automatically prompt for a new
password. This is assuming the caller has it turned ON.
(H339)

Stand Along mode has a built-in Screen Blanker. The screen blanker
will kick in after 3 minutes. Tap ESC to reactivate the screen.

The screen will flicker once or twice a minute to make certain
WATCHDOG boards happy. Those boards reboot the computer after xx
minutes of no screen or keyboard activity.

You can alter the BLANK delay using the command line switch /S<Minutes>

Examples:

/S10   Means Blank after 10 minutes.
/S5    Means Blank after 5 minutes.
/S1    Means Blank after 1 minute.
/S0    Means Blank ASAP.

<Minutes> must be less than the Outbound Call Delay Field (Node
Configureation). If it is MORE, it is effectively disabled and no
blanking will occur.

(H340)
From the primary Waiting For Call Screen

The field labled "Msgs" on the primary display screen has 3
possible values: Yes, No, and Email.

YES   = Message Center mail to the sysop.
EMAIL = Fidonet E-mail to the sysop.
No    = No messages addressed to the sysop.

YES has priority over EMAIL.

This is only available if you run Osiris in STAND ALONE mode.
(H341)
One of the problems I run into with Osiris SE was wanting to add
more custom commands on my system than available slots. Osiris SE
was also a FIXED record system, by that I mean you had 3
subsystems (Main, Message, File) with a fixed number of slots.

To ADD more commands would mean redoing the file structures and
that would mean the aux. programs would have to be redone. So I
came up with the concept of a slash command.

You execute a Slash command when you pressing the forward slash
key, /. The command following the / is not really a command, it is
the NAME of a SPL/I command file (minus the .PRG file extension).
IF that file exists, it will be executed.

That gave me a CLEAN way to add an unlimited number of new
commands or subsystems without having to modify the file
structures.

But Osiris XLT does NOT have a fixed number of records so I don't
really need the SLASH commands anymore. I just add another COMMAND
record and I got a whole bunch of new slots to play with.

But if I do away with the SLASH concept, I'll find that I need
something like that so I'm going to KEEP the Slash commands with a
few minor adjustments:

The slash command must be in the SLASH.BBS subdirectory, this is
in the OSIRIS= directory. Osiris will take care of creating that
directory.

                          Illegal Names

I'll not allow you to use any SLASH command that starts with the
following.

COM CON PRN AUX LPT

This prevents you from entering COM1 or AUX which would LOCK up
the system.

ALL SPL/I slash command files HAVE to have the file extension of
PRG.
(H342)
This allows you to create DISPLAY/PRG files that will be shown to
the caller when you press one of the SHIFT F keys.

They will only be shown this file, or the SPL program, when it is
safe, i.e. they are at a primary menu.

If they are not at a primary menu when you press one of these
keys, the display will happen as soon as they return to a menu.

To use this function to display screens, you have to create a
couple of display files, a SFxx.MMU and a SFxx.RIP with xx being
replace with the F-key number.

For Shift F1, you would create SF1.MMU and SF1.RIP. For Shift F10,
you would create SF10.MMU and SF10.RIP.

These files go in your OSIRIS= directory.

If you want to use an SPL/I program, do the same thing only use
SF1.PRG or SF10.PRG.

(H343)
I will scan a file, if it exists, called bulletin.hdr. This
contains information headers about bulletins created using
the SM/MISC/POST BULLETIN option.

I'll compare the date and time you created the bulletin with the
date and time you were last on-line and if the bulletin was added
SINCE then AND you have access to view the bulletin, I'll show it
to you.

The dates are compared according to JULIAN dates so on Dec 31st,
you'll need to delete your old bulletins and start fresh ones.


(H344)
If you include the command line switch /D, Osiris will automatically
engage SNOOPmode for ANSI/ASCII callers. This is not recommended if
you are running multiple lines because writing to the screen is the
second slowest thing you can do with DISK READ/WRITE being the first.

(H345)
                            SM/E-MAIL

You have FOUR options available to you: Mailbox, Threaded Reader,
Read Specific, and Moderator.

                             Mailbox

This lists all your private mail.

There will be a short delay when you first enter the Mailbox. SM
is scanning and building the display tables.

All the buttons on this page are pretty plain except for TOGGLE.
This toggles the display between your PERSONAL e-mail and
EVERYBODIES e-mail.

You'll not be able to SEE any replies or new message you may post
while in the Mailbox until you exit and re-enter. They are there
and available to the person or persons they are addressed "TO:"
but they're just not in the display tables SM built when you
entered the Mailbox.

                        Reading a Message

To read a message, click on it. When reading a message, you have
the following HOTKEY options:

[R]eply
[K]ill
Up Arrow
Dn Arrow
PgUp
PgDn
Home
End

You'll also notice an upside down triangle in the upper right
hand corner of the screen. If you CLICK on the triangle, a menu
will drop down listing several options: Print, Save, Forward,
Edit, and Mark Read. Most of these are pretty straight forward.

Print sends the current message to your printer.

Save writes the current message to a text file. You specify the
name of the text file.

Mark Read flags the current message as RECEIVED. No personal
message to YOU will be marked RECEIVED until you use this option.

                         Threaded Reader

SM will take the first conference area you have selected and scan
for new/unread messages and present them to you in THREADED
format. Threaded format means that only one subject is listed per
thread.

You MUST use the BBS to to select and deselect message areas. SM
and Osiris use the same files and tracking method. Meaning Osiris
knows which messages you've read while in SM and SM knows which
messages you read while using Osiris.

The NEXT button will take you to the NEXT area you have selected
to read that has NEW messages. Areas that have NO new messages
will be skipped.

The MARK button works pretty much the same as the NEXT button only
SM marks ALL the messages in the current area as "READ" before it
moves the the next area.

Pickout the thread/topic you want to read and click on it.

While reading the following options are available:

[R]eply
[K]ill
Up Arrow
Dn Arrow
PgUp
PgDn
Home
End
Right Arrow (Next message in thread)
Left Arrow (Previous message in thread)

You'll also notice an upside down triangle in the upper right
hand corner of the screen. If you CLICK on the triangle, a menu
will drop down listing several options: Print, Save, Forward,
Edit, and Mark Read. Most of these are pretty straight forward.

Only PRINT, SAVE, and EDIT will work when you are in the threaded
reader.

Because of all the enbedded control lines in a message that make
it very area specific, forward is not allowed. If you have a
message you want someone else to see, SAVE it to a text file (this
strips all control lines) and then QUOTE that text file in a
message.
                          Read Specific

When you select this option, SM will ask you for a STARTING area
number. Once you have entered that, SM will display the next 100,
including the starting area, message areas. Select which one you
want to read.

Unlink the threaded reader, read specific shows you EVERY SINGLE
message in the area, even if it you have or have not read it.

                  Posting/Replying To A Message

When you post or reply to a message, you'll notice a button
labeled "Address.bok".

Address.bok is a text file listing, one per line, the name of
someone you talk to on a regular bases. The name can be the name
of someone on your BBS or it can be an internet name.

If you click on the Address.bok button, SM will list the contents
of Address.bok and you can select the TO: field from here.


When you post or reply to a message in the Mailbox, Threaded
Reader, or Read Specific you'll get something that looks like
this:

[ ] Add Tagline          OK Button
[ ] Add Signature
[ ] File Attach          Cancel Button

If you click on the CANCEL button, your message is NOT saved.

                             Tag Line

A TAGLINE is a single line witticism that you can have appended to
the end of each message.

To create taglines, make a file in your OSIRIS= directory called
Tagline.ctl. This file can contain an unlimited number of lines
but, each line cannot be any longer than 78 characters.

If you select the tagline option, SM will pull a tagline from this
file and insert it at the end of your message.

SM will CYCLE the taglines starting with the first one and when it
reaches the end of the file, it'll start over at the TOP.

                         Signature Files

A signature file is a simple text file that contains your
signature, the way you want to sign the message.

This generally contains your real name, phone number, fidonet
address, internet address, fax number, etc.

When you enter a message and click on the Signature option, SM
will scan the OSIRIS= directory looking for any file with a .SIG
extension and present you with a file list. Just select the one
you want to use and SM will append it to the end of the message.

You may, if you like, use BOTH taglines and signature files in a
single message.

                           Attach File

The attach file option works differently depending on where you
are at.


If this option is selected and you are in the MAILBOX, SM will
give you a list of all the files in the ATTACH.BBS subdirectory.
Pick the file you want to attach to the message.

Once the message has been received and the file has been
downloaded, Osiris will delete the file.

If this option is selected and you are in the THREADED reader or
READ SPECIFIC, SM will give you a list of all the files in the
GLOBAL.BBS subdirectory. Pick the file you want attached to the
message.

The file attach in this area will *NOT* be deleted after a
download and ANYBODY that has access to the message area has
access to the file attach.

File attaches in echomail or newsgroup areas are pointless. File
attaches are NOT sent out when you export messages.

                       Moderator

This function shows you the messages on HOLD and asks you to approve
or reject each message.

If you reject a message, it is sent back to the person that posted
the message and you are asked to select a reason the message was
rejected.
(H346)
To offset the COST of maintaining the BBS, you may want to CHARGE
callers a small fee to ACCESS your system.

Keep in mind that when you do this, you must switch your phone
from residential to a business line. If you don't and the phone
company finds out about it, they CAN make you pay the difference
between the two and make it retroactive. It doesn't cost that much
more for a business line so save yourself some headaches and do it
right the first time around.

I've given you THREE different methods of handling this, a DATE
system, a CONNECT TIME system, and a CHARGE per Kilobyte
downloaded.
(H347)
The DATE system is the most popular, I guess because most BBS
programs need external programs to do that and it is easier than
the time system.

The date system works by entering a caller EXPIRATION date in his
or her user record. When that date rolls around, Osiris
automatically resets that persons access level.

To implement the DATE system, enter the access level you Osiris to
give anyone who's subscription expires. You set this access level
in the NODE subsystem, field name:

Access Level When Subscription Expires

You'll also want to PLUG in the TIME LEFT function in one of your
STARTUP command slots so your callers when know when their
subscription expires and so that *I* can lower their access level
when it does.

If you want to EXCLUDE a specific access level, enter that access
level in the field labeled "Exclude From Subscription System".
You'll find the field in the NODE subsystem.

(H348)
This system is, I believe, a better way of doing it. A person
is charge so much per minute for each minute he or she spends on-
line. And unlike the DATE system, they are not paying for time
they do not use.

To implement the TIME system, define the access level you want
Osiris to give a person when their MATRIX CREDIT hits ZERO. The
field is labeled "Access Level When Subscription Expires " and
found in the NODE subsystem.

Now define the COST, in pennies, per MINUTE, 1 to 9. The field is
labeled "Connect Time Cost Per Minute" and you'll find it in the
NODE subystem.

You'll also want to PLUG in the TIME LEFT function in one of your
STARTUP command slots so your callers when know when their
subscription expires and so that *I* can lower their access level
when it does.

When someone subscribes to the system, take the amount of money
they sent you and break it into pennies. For instances, 5 dollars
would be 500 pennies. Now enter that amount in the caller's matrix
credit field. The caller's matrix credit field can be found under
the USER subsystem.

If you want to EXCLUDE a specific access level, enter that access
level in the field labeled "Exclude From Subscription System".
You'll find the field in the NODE subsystem.

(H349)
Another Bill method is charging the caller so much for every
kilobyte downloaded.

To setup the DOWNLOAD billing system, fill out the fields in the
NODE subsystem labeled:

Charge X Cents Per YY Kilobytes Download, Exclude Access level ZZ"

Field X is in PENNIES and YY is KILOBYTES (1024 bytes).

Reverse Billing is done when the caller UPLOADS a file. It works
the same as the billing for DOWNLOADING a file accept the amount
is ADDED instead of subtracted. You can disable this by setting
your GIVE BACK RATIO to 0.

                        Free Files

If you use the Download billing system, the FREE FILE field is
used differently.

The FREE file field found in EACH file area record normally mean
don't count this file towards the callers daily or weekly download
limits. If the download billing system is used, it means don't
CHARGE for downloading this file. The file is still counts towards
the callers daily or weekly download limit.

                Auto Free (don't bill) Files

If you want OSIRIS to automatically flag a newly uploaded file as
FREE, don't bill the caller (kilobytes or matrix credit), set
"General App Flags" 1 to the ON position.

You'll find the "General App Flags" are found in the
Boards/Filboard.Bbs subsystem and you have to do this on an area
by area bases.

When the caller has completed a download the caller's NEW credit
balance is shown right after the "XXXXXXXXX Sent OK" message.

E.g.

PHV300.ZIP, Sent Ok!
New Credit Balance, 345

345 is the amount he or she NOW has in the matrix credit field.

You can go to the Transfer Stats display and get the AMOUNT of
Kilobytes you have left at any time.

The file queue also shows up a little different if the download
billing system is used. When a person LISTS the files he or she
has tagged for downloading, a $ will appear in front of the
filename *IF* they are going to be charged for that file.

(H350)
You may, if you decide to get out of the BBS business or simply
want to switch BBS programs, sell your registered copy of Osiris
to someone else.

However, you must notify International TeleCommunications in
writing prior to the sale and pay a TRANSFER fee of 25 dollars.

The TRANSFER fee covers the cost of changing OUR records to
reflect that you have transferred ownership.

Failure to comply means the NEW owner will not be eligible for
upgrades.

(H351)
The Universal Text Interface (UTI) is a set of programs which
allow mail software to be compatible with virtually any BBS
software.  It consists of a set of six programs which generate
specifically formatted text files which are read by any mail
software that uses UTI specifications.

Applications such as RIME or PCRelay Echomail programs as well as
several OFFLINE readers use UTI drivers to work with virtually any
BBS program.

Simply move the programs found in the ARCHIVE UTI.ZIP to a PATH
directory. That is basically all WE have to do with it. The
application that uses the UTI drivers will give you further
instructions.

(H352)
There is no RESTRICTIONS placed on the user name or alias. You can
basically use anything you want.

                             Examples

                               John
                          John Q. Public
                           John Public
                            Bill Jones
                       William (Bill) Jones

As long as at least one word is there, you can use anything that
will FIT into the space allocated for name and alias.

If you want to FORCE at LEAST a two word USER name, has no effect
on ALIAS, add /R to your Osiris command line.


(H353)
An ALIAS is a secondary name you might want to use, in messages,
in place of your real name.

There are several reasons to use an Alias, professional people may
not wish to be bothered with giving out free advice.

When you fill out your user record, there is a field provided so
you can enter an ALIAS name. All Alias names MUST be unique.

You do, of course, have control over whether or not an ALIAS may
be used in ANY conference area.

(H354)
If you plan on running some type of MAILER as a FRONT-END to
Osiris, the mailer must pass several command line arguments. The
mailer must pass the CONNECT baud rate and the serial port number,
if you are running multiple lines.

The command line switches used for those two items are: -B and -P:
-B2400 -P1 or -B9600 -P5

You must ALSO supply a node number using the -N switch: -N1 or -N2

You can, if your mailer supports it, pass the time till the next
MAILER event using the -T command line switch.

Example -T345

(H355)
If you want to setup Osiris on a NETWORK and allow company
employees to log-on from the network, you can.

All you do is call up Osiris is LOCAL mode and let them  LOG-ON.
Osiris handles everything else.

Osiris will let them DOWNLOAD their messages to their local
directory as well as UPLOAD messages and FILEs into the FILE Area
from their own directory.

Since they already HAVE access to the FILES via the network,
downloading files from the file area isn't needed nor supported.

We have several utilities on our BBS to augment this feature. One
will scan and exit with the errorlevel equal to a FREE node and
the other allows YOU to monitor who is on what node from your own
workstation.

Both utilities are provided at NO charge and you can find them in
file area 1. Names, due to version changes, may change but the
descriptions will clearly point to the correct programs.

(H356)
I will allow you to UPLOAD the message using your DEFAULT protocol
but I WILL limit the size of the message to 10K.

What if someone uploads an ARCHIVE or BINARY (EXE/COM) file? Will
that hurt anything? No, I will skip any NON-PRINTABLE characters.
The message will not make any sense, but it will not lock anything
up on YOUR system or anyone else's (if you echo the message to
other systems).

(H357)
If you find the protocol driver doesn't come up and the UPLOAD
always fails... Osiris changes into a TEMP upload directory
before it starts the UPLOAD and DOS cannot find the protocol
driver.

There are TWO solutions. The first, and best, is to move the
protocol drivers to a DIRECTORY listed in your PATH= statement.

The second solution, load SM and go to MISC/PROTOCOL and add the
drive and path to the program you defined for this protocol.

There is another possiblity if you are running OS/2 Warp. OS/2
warp REQUIRES that ALL EXE, COM, OVL, and BAT files be READ ONLY
if they are to be used by more than one window.

Try setting them to READ ONLY.

(H358)
Quite often this is caused by a LOCKED or FIXED DTE rate higher
than 9600 and a standard 16450 or 8250 uart.

For speeds greater than 9600 bps, you MUST have a 16550 Uart.

If you are running multiple lines under Windows, Desqview, or
OS/2 then you simply must use an intelligent serial card if you
plan on running faster than 9600 bps.
(H359)
You *MUST* have Osiris set-up and running in stand-alone mode and
you MUST have a Fidonet or Fidonet style address before you can
install the mailer module.

Assuming you do, log into the OSIRIS= directory and run the
program FINSTALL with the command line of 1.

Example:  FINSTALL 1

This means install mailer functions for NODE 1.

You will need to make sure the following programs are in the
OSIRIS= directory *OR* in a PATHED directory.

FINSTALL.EXE
FMAIL.EXE
FM.EXE

FINSTALL will ask you a series of questions and then install the
mailer functions.

One of the first things you'll want to do, read all the HELP sections
relating to the mailer functions.

The second thing you'll want to do, create at least one event to
call your HOST to pickup mail. This will require creating a route
control file so re-read the section about "Explicity Routing Commands"
and "Examples and Common Mistakes".
(H360)
This shows you the last 100 mail calls to your system, most recent
displayed first.

Osiris keeps this log trimed so you don't have to do anything.

(H361)
Osiris keeps statistics on such items as incoming calls,
outgoing calls, incoming file requests, outgoing file requests,
incoming file attaches, outgoing file attaches, etc.

You can view those statistics using this option. You would also
use this option to CLEAR/RESET those statistics.

(H362)
At times, you may want to check your outbound mail to see if your
ROUTE control file is working the way you wanted it to work.

This option shows a table of outbound messages, who they are
addressed to and who they are ROUTED to along with the TYPE of
message (File Request, Echomail, E-mail, etc.) and the SEND status
(HOLD, CRASH, SEND, etc).

What you see here is EXACTLY how Osiris sees the messages.

(H363)
If Osiris has STOPPED trying to send a message because
that system has exceeded the number of BUSY signals, you
can RESET the busy signal counter to ZERO using this option.

(H364)
If Osiris does not send a message because that message
is addressed to a system that has exceeded the number
of connects allow per system during the event, you can
reset the TIMES CALLED counter to ZERO using this option.

(H365)
This function gives you the NAME of the current MAIL
event along with the time the event ends.

(H366)
This is the option you use to READ/REPLY/POST Fidonet E-mail.
There is one restriction, you may only access this section from
NODE 1.

With a couple of exceptions, using the matrix editor is pretty
straight forward and it uses the same text editor you defined for
SM.

When you enter a message, you are asked to provide certain pieces
of information such as SUBJECT, TO, FROM, etc.

One of the BUTTONS on this screen is labeled SEARCH. If you click
on this option, FM will take the CURRENT contents of the TO field
and scan the nodelist in SLIDE fashion and present you with any
matching records and ask you if this is the correct one.

If you entered BILL and clicked on SEARCH, you would see each
record in the nodelist where the sysops name beginning with BILL.
If you answer YES to one of the records, FM will use the sysops
name and the system address in the TO field and TO address fields.

The other item that needs some explaining is File Requests.

You'll get a screen with two fields and two buttons.

The two fields are labeled FILE and PASSWORD. You must fill in at
least the FILE field. The PASSWORD field is optional.

The two buttons are labeled OK and FINISHED. Once you've filled in
the FILE (and optional Password field) you click on OK.

Clicking on OK tells FM that you want the FILE field and the
PASSWORD field processed. It does *NOT* mean that you are done.

When you click on OK, FM will process the contents of the fields
and then clear them.

You can repeat this process and request as many files as you want
with a single message.

Once you have requested ALL the files and the FILE field is empty,
click on FINISHED.

With respects to running MULTIPLE mailer lines, be VERY careful
not to use the FM matrix editor or any other matrix editor  while
a mail session is in progress. This includes sessions that MAY
start while you are in the editor.

(H367)
The  nodelist editor lets you  View, Search, Edit, and ADD
nodelist records.

To EDIT a field, move mouse cursor to the field and click LEFT
mouse button.

The field Session Type is a CYCLE field. In other words, it CYCLE
to the NEXT selection when you click on the field. Continue to
CLICK until the field contains the data you want.

All HASH INDICES are automatically updated if you change an INDEX
field.

The PREDIAL.DAT file is automatically updated when you add, edit,
or CLEAR a system's PREDIAL string.

You'll notice there is no DELETE option. Since the HASH indices
are all based on the NODELIST.DAT record POSITION for each entry,
deleting a record from NODELIST.DAT would throw all the HASH
indices off and they would have to be rebuild from scratch. It
would be very time consuming to PACK a 3.5 Meg Nodelist and then
rebuild all 4 HASH indices. It would also create a lot of disk
fragmentation.

                              Search

You can quickly locate an individual record with the Search
option.

When you select SEARCH, you'll get another menu that looks
something like this:

      ╔═══ Select Search Criteria ═══╗
      ║                              ║
      ║           Address          ▄ ║
      ║  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ║
      ║   Exact Match, Sysop Name  ▄ ║
      ║  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ║
      ║    Exact Match, BBS Name   ▄ ║
      ║  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ║
      ║   Slide Match, Sysop Name  ▄ ║
      ╣  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ╠
      ║    Slide Match, BBS Name   ▄ ║
      ║  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ║
      ║           Cancel           ▄ ║
      ║  ▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀ ║
      ╚══════════════════════════════╝

Address and the EXACT MATCH options use the HASH tables to find
what you are looking for and what you type in must match EXACTLY.

The SLIDE match options take the text you type in and search the
appropriate field in SLIDE fashion. Obviously, this is going to be
somewhat slower.

For instances, if you select Slide Match, Sysop Name and type in
BILL, you'll see all the records where the sysops name starts with
"BILL".

(H368)
This section deals with the primary Fidonet Mailer configuration.
Below is a brief explaination of each field.

                            Your Name

This is YOUR name, generally first and last.

                             BBS Name

This is the NAME you have selected for your mail site.

                         Primary Address

This is your PRIMARY 4-D Fidonet address.

                       Secondary Addresses

You can define up to 53 alternate addresses. Three here and 50
using Phoenix.aka.

                          Nodelist Path

This is the PATH to your nodelist and it is ONLY used by Osiris.

                    Path To Inbound Directory

This tells Osiris WHERE to place incoming FILES, ECHOMAIL, PKT's
, and other items during a mail session.

                     Path To E-mail Directory

This should point to the directory that contains your matrix
messages and you SHOULD end the path with a backslash.

                      Name of Request FILES

This is the name of the file to send when someone file requests
FILES.

Osiris will replace FILES with the name of the file you define in
this field and then Osiris will search the directories listed in
REQUEST.CTL in an attempt to find it.

                        Carrier Out Delay

This determines the NUMBER of SECONDS Osiris will wait for an
OUTBOUND connect once the DIALING process has been completed.
SECONDS should be ONE second longer than your modems S7 register.

You should set this, and the S7 register, to at least 45 if you
have a v32,v32bis,HST, PEP, or any other high-speed modem.

If you are placing overseas calls, you should set this and the S7
register to at least 60. 75 if used with a high-speed modem.

                       Maximum Busy Signals

This determines the MAXIMUM number (between 1 and 255) of busy
signals you can get when calling an individual system during a
specific event. Once you reach the maximum number, Osiris will
stop calling. This is reset when you change events.

                     Maximum Calls Per System

This determines the MAXIMUM number (between 1 and 255) of calls to
an individual system during a specific event. Once you reach the
maximum number, Osiris will stop calling. This is reset when you
change events.

A CALL is registered when you get a physical CONNECT to the
system, mail does NOT have to be transferred. If the system is
having problems, software or hardware, this will prevent you from
running up a large phone bill. I would suggest that you keep this
low, no more than 10.

                           Serial Port

Tells Osiris which serial port to use. Valid ports range from 1 -
33.

                            Lock Rate

This tells Osiris to FIX the serial port at this baud rate. When
you connect with another mailer or a HUMAN calling for the BBS,
Osiris will NOT change the serial baud rate. It will simply allow
the MODEM to handle adjusting the SEND/RECEIVE speeds.

Osiris will NOT pass this rate as the CONNECT baud rate. It will
pass the rate the modem returns in the CONNECT message.

If you LOCK the serial rate higher than 9600 baud you MUST have a
16550 Uart. Attempting to run with a LOCKED serial rate higher
than 9600 will almost always generate errors when you attempt to
RECEIVE very large files, generally over 50K in size).

                            Fifo Size

Osiris will automatically detect and use a 16550 Uart. This tells
Osiris how many bytes to send per TX interrupt. You can use any
number between and including 1-16.

           Starting Baud Rate For Outound Dial Attempts

This is primaryly for those that do not run FIXED DTE rates.
If you do not run a FIXED DTE rate, use the highest baud rate your
modem supports.

Valid baud rates are in POWERS of 2.

Example: 1200, 2400, 4800, 9600, 19200, 38400, 57600, 115200.

Notice that 14,400 is not valid. 14,400 is a MODEM rate, not a
serial rate.

                        Modem Dial String

This is the command string you want Osiris to send to your modem
to get it to DIAL the phone number. Generally this is ATDT or
ATDP.

                        Modem Setup String

This is the command string that prepares the modem for an outbound
call. It is sent PRIOR to the NODELIST PERDIAL STRING and the
Modem Dial String.

If your modem requires a carriage return, most do but a few do
not, end the string with the vertical bar, |

              Modem CONNECT Messages and Baud Rates

Osiris lets you define up to 30 CONNECT messages along with the
serial rate to associate with the message.

The BAUD rate can be any legal serial rate you want Osiris to use
for that connect message.

                         Magic File Names

Osiris lets you define up to 10 MAGIC file names. A MAGIC file
name is a STATIC name someone can use when they do a file request
and always be assured of getting the current file.

For instances, the name of the current Fidonet nodelist changes
each week. If you want to set it up so that all a person has to do
is file request NODELIST and get the current nodelist then you
would set up a MAGIC name:

NODELIST NODELIST.A57

NODELIST.A57 would be THIS weeks nodelist, next week you'd have to
do something like

NODELIST NODELIST.A64

Osiris will search the directories listed in REQUEST.CTL for the
NEW file name.

Examples:

NODELIST NODELIST.A57
OSIRIS SE401?.ARJ
ISIS I6*.ARJ

                         CheckBox Fields

The remaing fields in the mailer configuration section are CHECK
BOX fields. If the little box, [ ], has an X in it, the option is
turned ON.

                    [ ] Desqview Time Slicing

While Desqview can be detected by searching memory for a specific
signature, several NETWORK programs use the same signature. To
avoid confusion, we ask that you TELL us if you have or do not
have Desqview installed.

                       [ ] Process Echomail

If Echomail is received, execute ECHOMAIL.BAT. This is restricted
to NODE 1. Nodes 2, 3, 4, etc. will not run ECHOMAIL.BAT even if
this is toggled on. See section on how to run MULTIPLE mailers.

                         [ ] Process Tic

If a TIC file is received, execute TIC.BAT. This is restricted to
NODE 1. Nodes 2, 3, 4, tec. will not run TIC.BAT even if this is
toggled on. See section on how to run MULTIPLE mailers.

                       [ ] Process Areafix

If an AREAFIX request is received, execute AFIX.BAT. This is
restricted to NODE 1. Nodes 2, 3, 4, etc. will not run AFIX.BAT
even if this is toggled on. See section on how to run MULTIPLE
mailers.

                        [ ] Unbundle Email

If you receive e-mail, Osiris will unbundle it if this is turned
on. This is restricted to NODE 1. Nodes 2, 3, 4, etc. will not
unbundle mail even if this is toggled on. See section on how to
run MULTIPLE mailers.

                         [ ] Process Raid

If you receive a RAID request, Osiris will execute RAID.BAT. This
is restricted to NODE 1. Nodes 2, 3, 4, etc. will not run
RAID.BAT even if this is toggled on. See section on how to run
MULTIPLE mailers.

          [ ] Accept File Requests From Unknown Systems

Only accept file requests if the system is listed in your
nodelist.

        [ ] Require Some Type of Password For Mail Pickup

Basically means that SOME TYPE of session level password MUST be
present before Osiris will hand off mail. See section on security
for a more in-depth explaination.

           [ ] Use DPMI Time SLicing (OS/2 or Windows)

This determines *IF* Windows or OS-2 DPMI time slicing will be
used.

                  [ ] Assume Crash Means Direct

Crash means go out ASAP while DIRECT means DO NOT ROUTE.

Normally, Crash does NOT mean the message or what-have-you will go
direct and it MAY be routed.

If you want ALL crash to go DIRECT and you do NOT want it routed,
toggle this on.

                   [ ] Secure Echomail Engaged

This prevents anyone from dropping off echomail unless their
NODELIST.DAT "ECHOMAIL ALLOWED" flag is turned on.

This is the ONLY method of running 100 percent secure echomail.

Osiris handles this by ALLOWING them to do the physical file
transfer but as soon as the transfer has finished, it will
promptly delete the file if they do NOT have echomail
authorization.

It is recommended that you use SESSION level passwords with ANYONE
that has echomail authorization.

I think we should also warn you that Fidonet Technology does
provide ways of HACKING session level passwords. While it does
require a certain level of SKILL and persistence on the part of
the HACKER, you can do it.

If you notice a NUMBER of PWD failure messages for any specific
system, you should call the owner of that system VOICE and ask him
what is going on.

                  [ ] Secure Addressing Enabled

When you place an outbound call with SECURE ADDRESSING turned ON,
Osiris matches the remote systems address with the one that
triggered the call. If they do not match, Osiris hangs UP.

This prevents mail from being sent to the wrong location due to an
error in the network NODELIST.xxx or an error in your PHONE.CTL
file.

When you receive an inbound call and secure addressing is turned
on, Osiris will HANG-UP if the callers NOT in the nodelist.dat
file.

This prevents TERMINAL programs with WAZOO emulation systems from
bypassing BBS download restrictions via file requests. Something
that is starting to become a problem.

                   [ ] Engate RTS Flow Control

In most cases, the default CTS is  best. However, if you are
running Osiris on a Network or under Desqview, Windows, or OS/2
you may need to use RTS and CTS.

If RTS is used, Osiris will lower RTS when it opens, reads from,
writes to, moves the file pointer to a new position, and closes a
file. Lowering RTS lets the modem know the computer is NOT ready
to receive data. The modem will store the data internally until
RTS is high.

RTS does slow down transfers and you can STILL get errors if RTS
is held low for TOO long and the modem runs out of storage space.

(H369)
Osiris has TWO different EVENT managers. One that you access via
SM is for BBS or MAINTENANCE type events.

The one you access from FM, (F)ido Mail from within Osiris, are
events that govern HOW mail is handed during a specific time
frame.

This section deals with the events that govern how mail is
handled.

Events are OPTIONAL. If there is no ACTIVE event Osiris uses the
following DEFAULTS:

All mail, except CRASH, is placed on HOLD.

BUSY and CONNECT restrictions are disabled.

No restrictions on Number of files that can be requested during a
single session.

Time to Next Event is the starting time of the NEXT  event or
midnight if you have NO events defined.

To define an event, run FM or press (F) from the Osiris waiting
for call screen. Select Mailer Configuration and then select
EVENTS.

                           Event Name

This is not used by Osiris, it is display so  you'll know WHICH
event is running. Osiris has its own method of identifying events.

                          Starting Time

This tells Osiris what time of day this event is suppose to
START.

STARTING TIME is in HH:MM format, military time. Legal starting
times range from 00:00 to 23:59.

                           Ending Time

This tells Osiris WHEN the event is suppose to END.

ENDING TIME is in HH:MM format, military time. Legal ending times
range from 00:01 to 24:00.

NO event may span midnight.

                            Execure On

This tells Osiris which DAYS the event is suppose to be active.

To ACTIVATE the event for a particular day, move the mouse cursor
to the BOX under the DAY and click the LEFT mouse button.

If the event is ACTIVE on a particular day and you want to
DEACTIVATE the event for that day move the mouse cursor to the BOX
under the DAY and click the LEFT mouse button.

You can have the event active on ALL days, any combination of days
or NONE. NONE is considered as a PLACE holder.

                             Dynamic

This means the event is ONLY suppose to be active *IF* there is
outbound mail. If there is NO outbound mail, Osiris terminates the
event, even if it has not reached the ENDING TIME.

WARNING!!!!! Absolutely NEVER setup any type of event that sends
mail or polls other systems during a time frame that may overlap
any DYNAMIC event.

In other words, if you have a dynamic event that is set to run
between 00:01 and 01:00, you must never setup another event that
sends mail or polls until AFTER 01:00.

I'm not going to get into WHY, but if you do not heed our warning,
your pocket book can and will be effected.

                        Route Control File

This is the name of a text file used to hold EXPLICIT routing
instructions for this event, see section on ROUTING for
information on the contents of this file.

                            Do Pick-up

This determines whether or not Osiris will pick-up anything
during an outbound call. If PICK-UP is turned off, Osiris will
drop off what every it has and then hang-up.

                    Maximum Request Per Event

This sets the maximum number of files a remote mailer can file
request during this event. If you set this field to ZERO, you have
disabled file requests during this event.


(H370)
Before you can use the Fidonet Mailer part of Osiris, you have to
understand the ADDRESSING system Osiris uses.

A Fidonet address uses 4 different segments:

Zone, Net, Node, and Point.

This address is called a DOMAIN and each segment is called a
SUBDOMAIN.

If you have used Fidonet mailers in the pass, you have no doubt
seen references to DOMAIN as being the 5th PART of the Fidonet
address and this is not correct. The word DOMAIN means address.

Example of a Fidonet Domain:   1:296/5.0

The COLON, FORWARD SLASH, and PERIOD are "NOT" part of the domain.
They are simply used by the software to DIVIDE the subdomains.
Subdomain divisors are not transmitted from system to system and
are SOFTWARE dependent.

Many, but not all, Fidonet mailers uses the COLON, FORWARD SLASH,
and PERIOD.

For this point on, the word DOMAIN will reference a 4 part Fidonet
address. Each segment of that address, zone, net, node, and point,
will reference a subdomain.

When Osiris asks you for an address, you are expected to provide
all four subdomains.

When using FM, you may use any NON-DIGIT subdomain divisor that
suits you.

In other words . . . .

1.296.5.0
1:296/5.0
1@296@5@0
1!296!5!0
1a296b5c0

all mean the same thing.

As noted, the applies only to FM because speed is not an issue.
In other areas, such as a ROUTE CONTROL File, you MUST use a
PERIOD as a subdomain divisor.

In short . .  1.296.5.0 would be correct but, 1:296/5.0 is NOT
correct and will not work in a ROUTE control file.

As noted earlier, the DOMAIN contains 4 subdomains: ZONE, NET,
NODE, and POINT.

When Fidonet was originally started, a domain only consisted of
NET and NODE. The concept that it might OUTGROW the two subdomains
wasn't considered.

Because it wasn't considered, there were no provisions in the file
structures for those fields.

Because backwards compatibility is of paramount important, Fidonet
Technical standards still has not changed the file structures to
include fields for the ZONE and POINT fields.

The file structures, some of them, have been KLUDGED to handle
these fields but no mailer can REQUIRE them.

While many mailers do support the ZONE field kludges, to some
degree, many do not support the POINT field kludge. Which is
understandable considering that a POINT is only referenced ONE
time in the Fidonet technical  specifications and then with only
two short lines of text.

We're providing this information to illustrate a point, no pun
intended.

There are some programs out there that simply cannot handle a NON-
ZERO point address. Indeed, there are even some that cannot handle
a ZONE address.

There is NOTHING wrong with those programs. Fidonet simply does
NOT require nor has it provided official guidelines for ZONE or
POINT handling.

(H371)
Creating Nodelist.dat and Domain.idx with FM is easy and painless,
but it isn't a viable method if you belong to a large network like
Fidonet and want to keep a recond on every single system.

Despite the fact that we've told you a number of times that
keeping a record on every single system is not desireable or
required, some of you will do so anyway.

Fidonet has a new nodelist that comes out weekly and contains more
than 32,000 systems. Adding those by hand, well by the time you
got them added you'd have to start over again with the new
nodelist.

MAKENL takes the raw nodelist.xxx file and compiles it into a
Osiris nodelist complete with HASH tables for Sysops name, BBS
name, and finally DOMAIN address.

                         Network Nodelist

To compile a NETWORK nodelist you call MAKENL with the command
line /N<NAME OF NODELIST>

E.g. MAKENL /NNODELIST.157

This, in the case of Fidonet, CAN generate a rather large
NODELIST.DAT file. The size of the COMPILED nodelist Fidonet is
about 4.5 Meg, including indices.

But, you do have options that can reduce the size without having
any impact on your ability to do mail.

Since Osiris is based on Fidonet routing and has an exceptionally
intelligent router, you do NOT have to have a nodelist record for
every system.

The section on ROUTING goes into details on how this works, but
for now just assume that what I'm telling you is factual.

You can reduce the size of the nodelist.dat file by reducing its
depth.

Lets assume your zone is 1. If you rarely do mail with anyone
outside your ZONE, then you can let the ZONE GATE handle routing
any messages you may send. If you do mail with only a couple of
systems outside your ZONE,  you can include a PERSONAL nodelist
with for those systems.

If you want to do that, you can reduce the nodelist.dat file by
over 1 Meg by including the command line switch /Z1

This means, only keep systems in ZONE 1. Ignore the rest.

This will have no impact on your ability to send mail except you
will HAVE to route mail to those outside your ZONE  to the
ZONEGATE.

You can further reduce the size, of your nodelist by including /R
on the command line.

/R means generate a routing nodelist.

It is kind of hard to explain what this means, but here goes.

Only specific systems are retained, those need for routing
purposes.

For instances, 1.247.0.0 would be retained while 1.247.456.0 would
be ignored. Ignored because you could route 1.247.456.0's messages
to 1.247.0.0 and he could route it to 1.247.456.0 for you.

This isn't something you have to do manually, Osiris knows how to
do it and can do it automatically without your help.

If you were to compile the latest Fidonet nodelist (32000+ systems
were listed) using the command line:

MAKENL /NNODELIST.xxx /R /Z1

You would produce a NODELIST.DAT file only 90K in size and, this
is important, you could STILL do mail with every system listed in
the nodelist.

If you use /R and you have to route mail to those under you, you
will need to make a PRIVATE nodelist listing the individual NODES
and merge it with the exiting NODELIST.DAT file.

                    Merging Multiple Nodelists

Merging multiple nodelists, from different networks, is very easy.

Simply use the DOS COPY command to merge the nodelists into a
single file.

Example:  copy nodelist1+nodelist2+nodelist3  nodelist.doc

and compile nodelist.doc with makenl.

                   Personal or Private Nodelist

You may want to include system records in your NODELIST for those
systems not listed in your NETWORK nodelist. You might do this for
points, NODE under you if you are a NET host and you use the /R
command, or for a few select systems in other ZONES when you use
the /Zxx switch.

To create and maintain a personal nodelist, use the program
PRIVATE.EXE.

Private is pretty simple to use and it isn't very fancy. You may
use it once in a blue moon so we didn't go overboard trying to
impress you with our programming skills.

You run the program with one of four command line switches; /A,
/L, /Exx, and /Dxx.

/A - Add a NEW record.
/L - Generate PRIVATE.TXT. This is a text list of the private
     records.

/Dxx - Delete Record xx. xx would be the RECORD number listed in
       PRIVATE.TXT.

/Exx - Edit Record xx. xx would be the RECORD number listed in
       PRIVATE.TXT.

Private.exe keeps the personal nodelist records in a file called
PRIVATE.DAT.

When you run MAKENL with /N to  generates a nodelist from a
NETWORK list, the records from PRIVATE.DAT will automatically be
included.
                      Including Static Data

When you have Systems with static data: Session Level Passwords,
Session TYPE, OK to Drop off Echomail, or PREDIAL strings,
creating a NEW nodelist.dat file from a NETWORK list would
overwrite that information.

It would be a PAIN to have to edit, with the nodelist editor, the
information back in by hand.

You can have MAKENL update the NODELIST records to include the
STATIC data for you.

You first create a STATIC  database using the program STATIC.EXE.

It functions exactly like PRIVATE.EXE only with different database
fields. It has the exact same command line switches.

When you run MAKENL with the command line /N, MAKENL will
automatically update the nodelist records with the information
found in the STATIC DATABASE.

                           HASH TABLES

Osiris uses several compact and very fast HASH tables to find a
system's nodelist record. MAKENL will create 4 different HASH
Tables:

DOMAIN.IDX, contains the hash code for ZONE, NET, NODE, and POINT.

SYSNAME.IDX contains the hash code for the SYSOPS name.

BBSNAME.IDX contains the hash code for the Name of the Mailer/BBS.

PASSWORD.DAT contains the hash code for systems that have
password.

You do NOT have to keep ALL of the Hash Tables.

DOMAIN.IDX is the ONLY Hash Table you HAVE to keep. If you don't
you can't do mail with anyone.

Finally, using MAKENL with a FULL nodelist, 30,000+ systems is
not something you HAVE to do.

Many of you can simply use the nodelist editor and enter your
nodelist records by hand and not worry about having to compile
weekly network nodelists.

If you are NOT an NC, you really only *NEED* 2 records. A nodelist
record contains information about your NC and a record containing
information about your EC.

(H372)
Osiris has TWO different EVENT managers. One that you access via
SM is for BBS or MAINTENANCE type events.

The one you access from FM, (F)ido Mail from within Osiris, are
events that govern HOW mail is handed during a specific time
frame.

This section deals with the events that govern how mail is
handled.

Events are OPTIONAL. If there is no ACTIVE event Osiris uses the
following DEFAULTS:

All mail, except CRASH, is placed on HOLD.

BUSY and CONNECT restrictions are disabled.

No restrictions on Number of files that can be requested during a
single session.

Time to Next Event is the starting time of the NEXT  event or
midnight if you have NO events defined.

To define an event, run FM or press (F) from the Osiris waiting
for call screen. Select Mailer Configuration and then select
EVENTS.

                           Event Name

This is not used by Osiris, it is display so  you'll know WHICH
event is running. Osiris has its own method of identifying events.

                          Starting Time

This tells Osiris what time of day this event is suppose to
START.

STARTING TIME is in HH:MM format, military time. Legal starting
times range from 00:00 to 23:59.

                           Ending Time

This tells Osiris WHEN the event is suppose to END.

ENDING TIME is in HH:MM format, military time. Legal ending times
range from 00:01 to 24:00.

NO event may span midnight.

                            Execure On

This tells Osiris which DAYS the event is suppose to be active.

To ACTIVATE the event for a particular day, move the mouse cursor
to the BOX under the DAY and click the LEFT mouse button.

If the event is ACTIVE on a particular day and you want to
DEACTIVATE the event for that day move the mouse cursor to the BOX
under the DAY and click the LEFT mouse button.

You can have the event active on ALL days, any combination of days
or NONE. NONE is considered as a PLACE holder.

                             Dynamic

This means the event is ONLY suppose to be active *IF* there is
outbound mail. If there is NO outbound mail, Osiris terminates the
event, even if it has not reached the ENDING TIME.

WARNING!!!!! Absolutely NEVER setup any type of event that sends
mail or polls other systems during a time frame that may overlap
any DYNAMIC event.

In other words, if you have a dynamic event that is set to run
between 00:01 and 01:00, you must never setup another event that
sends mail or polls until AFTER 01:00.

I'm not going to get into WHY, but if you do not heed our warning,
your pocket book can and will be effected.

                        Route Control File

This is the name of a text file used to hold EXPLICIT routing
instructions for this event, see section on ROUTING for
information on the contents of this file.

                            Do Pick-up

This determines whether or not Osiris will pick-up anything
during an outbound call. If PICK-UP is turned off, Osiris will
drop off what every it has and then hang-up.

                    Maximum Request Per Event

This sets the maximum number of files a remote mailer can file
request during this event. If you set this field to ZERO, you have
disabled file requests during this event.


(H373)
First, you must have the mailer function installed for NODE 1.
Assuming you do, create a new subdirectory, where and what you
call it doesn't matter, for node 2.

Change into that directory and run FINSTALL 2

2 indicates that you are installing the mailer functions for NODE
2.

FINSTALL handles creating all the files needed to install the
mailer functions for each node.

So you'll have a better understanding of HOW all this works, we'll
explain what you would *HAVE* to do if there was *NO* finstall
program.

The primary mail system is on node 1 and that one is installed in
OSIRIS=

The configuration files for the secondary mail systems, nodes 2 -
255, would be installed in their own subdirectories.

All nodes would share the same common matrix area but each node
would have it's own inbound file area.

The inbound file area for node 1 is the master inbound area. The
inbound areas for nodes 2 - 255 are just temporary HOLDING areas.
As soon as a session is over, the contents of the temporary
inbound area is automatically transfer to the master inbound area.
Everything except items relating to an interrupted transfer.

Node 1 is the only node that will process inbound echomail, tic,
or unbundle e-mail. It does, of course, handle that task for
everything that comes in on ALL nodes.

If any node's doing a mail session, Node 1 will not process
inbound echomail or TIC files. It simply would not do to have
EXPORT try to update an echomail archive that is in the process of
being SENT. Node 1 will simply skip the process that time around
and do it later.

For nodes 2-255, you need to create batch files called FMAILxx.BAT
with xx being the node number.

This batch file should change into the proper subdirectory and
pass 4 parameters to FMAIL.EXE.

Assuming you had node2's mail configuration files in the directory
c:\fido2, fmail2.bat file would look something like this:

         @cd\fido2
         @Fmail %1 %2 %3 %4

Notice that each line in the batch file start's with an AT sign,
@. This tells DOS not to ECHO the line and this keeps the display
looking pretty.

I would suggest placing these batch files in a PATH directory
instead of the Osiris directory.

NOTE: When you create your RUNBBS.BAT, or whatever, to run Osiris,
make sure you place ECHO OFF at the TOP of the batch file and ECHO
ON at the bottom.

There are two guidelines you *MUST* follow:

1. NEVER process TIC files. You should set each node to NOT
process TIC. TIC should *ONLY* be processed during the midnight
maintenance event when all nodes are down. OTC is *NOT* network
aware and you can damage your files.bbs if you attempt to use it
while people are ON-LINE.

2. NEVER setup to export echomail in your ECHOMAIL.BAT. You can
IMPORT to your hearts content but you must never EXPORT echomail
while there is a possibility of a mail session occurring or that
one is in progress.

Echomail should only be exported during the midnight maintenance
event when all nodes are down and there is no possibility of a
mail session occurring until you have finished exporting.

It is OK to have your ECHOMAIL.BAT file IMPORT echomail.

Why??? It has nothing to do with IMPORT.EXE or EXPORT.EXE, both
are network aware and can be run WHILE callers are on-line.

The big problem is that you might attempt to UPDATE an echomail
bundle that is in the process of being sent which can and will
result in the receiver getting a damage archive.

You may accidentally update an echomail bundle that has JUST been
sent but not yet deleted. If that happens, someone you feed will
lose echomail.

You can EXPORT echomail in the midnight.bat file, see the section
on "midnight.bat".


(H374)
There  are  almost  as many  different  mailer  protocols  as
mailers. Almost but not quite, there are over 100 different brands
of mailers used in fidonet.

Osiris supports the following Mail Transfer Protocols:

                     Xmodem/Modem7

Fidonet FSC-0001 states that ALL mailers should support  a basic
Xmodem/Modem7 protocol. This protocol sends MATRIX messages first
using xmodem and any file attaches using modem7.

But  Fidonet has never enforced its own regulations  and you find
a  lot  of  mailers that do not do Xmodem/Modem7.

Osiris is fully FSC-0001 compliant.

A number of mailers that do not support Xmodem/Modem7 do support
several variations of the xmodem/modem7 protocol, Diet INFA and
SEAlink.

                            Diet Infa

Diet  INFA  is  a "LITTLE" faster  form  of  the  FSC001  protocol
that uses Telink in place of modem7. Osiris supports Diet INFA.

                             Sealink

SEAlink  is  a  method that's quite a  bit  faster  than  FSC001
and Diet INFA.

Osiris supports SEALink including extended   form  of  SEAlink
known as   SEAlink   with  OVERDRIVE.

Because there is a CLASH between Spoofing to Telink, known as DIET
INFA, and Spoofing to SEAlink (They use the EXACT same character
sequence to SPOOF), You MUST have the NODELIST SESSION type set to
SEALINK if you want SEAlink used on an outbound call.

If Osiris were to go directly to SEAlink when the SPOOF (Don't
know where that name came from) sequence was received and the
mailer on the other end actually wanted Telink, 8 out 10 times the
transfer will fail even though Osiris will drop back to Telink in
an attempt to recover.

If Osiris is the receiver, it doesn't matter WHAT the sender wants
to use. It can slide back and  forth between Xmodem, Modem7,
Telink, and Sealink without skipping a beat.

                              Wazoo

Wazoo,  created by Wynn Wagner III, is a popular  mailer  protocol
and  widely implemented. It  isn't  that  much  FASTER  than
SEAlink with Overdrive, but it  does  offer  several advantages
over SEAlink.

The  Wazoo/Zmodem protocol built into Osiris is solid  and  fast.
Although I must admit that it took several  years  of  almost
constant FINE tuning, in our other mailer, to get it to  talk
with  all of the varies Wazoo based mailers.

                      HighSpeed Mail Session

While WAZOO does offer a faster "HANDSHAKE" than FSC-0001 mail
sessions, it is still fairly slow and often fails if it runs into
line noise or delays induced by satellite links.

We have developed, and used for several years, our own proprietary
highspeed mail session, simply called HSP, that is about 30 times
faster when it comes to establishing a handshake between the two
mailers.

It is also considerably more reliable and handles noisy lines and
satellite links hundreds of times better than Wazoo.

HSP is about 5 percent faster than Zmodem at 2400 baud, 10/15
percent faster at 14.4, and nearly 20 percent faster when used
with v.FAST (proposed v.FAST standard. v.FAST hasn't been
finalized yet)

                               EMSI

EMSI is pretty much like your standard WAZOO only it  uses a
different method of passing the system information. After the
system info has passed, the file and message transfers generally
revert to Wazoo's ZEDZAP or Osiris's HSP protocol depending on
what the other system supports.

EMSI uses a single password to cover all the addresses passed in
the EMSI header. For total security, you would have to pull up the
nodelist record for each one of those addresses and compare the
passwords to make sure they ALL match. Several EMSI mailers do not
do this. They use the primary address and compare the password
with only that record.

Osiris doesn't do that. Osiris will check every single address to
make sure the passwords match. Under normal conditions, Osiris can
do this at an exceptional fast rate, about 1/10th of a second per
20 AKA's.

                              Zmodem

While ZEDZAP, Zmodem with Large Blocks, is the stardard protocol
for EMSI and Wazoo sessions, some mailers only support Zmodem.

Osiris supports normal Zmodem sessions under both Wazoo and/or
EMSI.

(H375)
It is common practice among Fidonet sysops to belong to multiple
networks or even have multiple addresses within the same network.

You can define up to 53 ALTERNATE DOMAIN ADDRESSES, 3 in the
Mailer configuation file and 50 in an external text file called
phoenix.aka.

Osiris NEEDS to know about the alternate addresses to prevent it
from PACKING mail to YOUR OWN ADDRESS. Although it would never be
sent, it takes up space in the packet table and it takes time to
load and attempt to ROUTE. The implied router needs to know ALL of
your address so it can properly route mail.

If a mailer calls and their ZONE is one of YOUR alternate Domain
ZONE's, Osiris will switch to the ALTERNATE address for
that ZONE and your HMS or WAZOO header will show the ALTERNATE
address instead of your default address.

If Osiris has to pack any messages for the calling system to
PICK-UP, the packet HEADER (not the messages themselves, they are
not touched) will show your HIGHEST ALTERNATE address
within that ZONE and NET or highest alternate address within that
ZONE as the PACKING system.

                           Phoenix.Aka

Phoenix.aka is an optional text file, located  in  the Osiris
directory.

Each line contains one address and you can list up  to 50
alternate  addresses, that should be enough  for  anyone.

Please note that in this case, you are required to use a PERIOD to
divide the subdomains.

An example of a Phoenix.aka file:

1.296.5.0
500.500.1.0
500.214.0.0

(H376)
During Field Tests, we found something we have never seen before.
While transferring a 360K file to a D'bridge system, the D'bridge
system allowed the entire file to be transferred and when End of
file was sent, the D'bridge system sent a ZRPOS 0, meaning error
resend from position 0. Position 0 is the BEGINNING of the file.

While this would be considered to be very strange, considering
that it takes about 4 minutes to send the file (v32bis),  we
didn't think a WHOLE lot about it until the same thing happened
when the end of file was again reached. Osiris resent the file for
the 3rd time and when end of file was again reached, for the 3rd
time, D'bridge did the same thing.

We don't know HOW long this would have continued (we manual killed
the transfer) but in THEORY, it could continue forever. Since 50
percent of the file was sent without an error, Osiris would reset
the error counter back to zero.

To prevent something like that from ever happening again, we
installed a MASTER transfer timer. When Osiris estimates the
transfer time for the file, a master timer is set to three times
the estimated transfer time.

In other words, if the estimated transfer time is 4 minutes and 20
seconds, the master timer would be set to  780 seconds ( 13
minutes). If the file hasn't been sent OR received BEFORE this
timer expires, carrier will be dropped.

The MINIMUM is 120 seconds, 2 minutes. If the master transfer time
comes up less than 120 seconds, it is set TO 120 seconds. This
should give PKT's, REQ's, and other small files plenty of time.

(H377)
We're use the following structure for .MSG as outlined in Fidonet
Technical Standards document FTS-0001.015, version 015.

NOTE: Stored format should NOT be confused with the format used
between mailers during a mail session, they ARE different.

         1.  Application  Layer  Data Definition :  Stored Message


       Offset
      dec hex
              .-----------------------------------------------.
        0   0 |                                               |
              ~                 fromUserName                  ~
              |                   36 bytes                    |
              +-----------------------+-----------------------+
       36  24 |                                               |
              ~                  toUserName                   ~
              |                   36 bytes                    |
              +-----------------------+-----------------------+
       72  48 |                                               |
              ~                    subject                    ~
              |                   72  bytes                   |
              +-----------------------+-----------------------+
      144  90 |                                               |
|             ~                    DateTime                   ~
              |                    20 bytes                   |
              +-----------------------+-----------------------+
      164  A4 | timesRead (low order) | timesRead (high order)|
              +-----------------------+-----------------------+
      166  A6 | destNode (low order)  | destNode (high order) |
              +-----------------------+-----------------------+
      168  A8 | origNode (low order)  | origNode (high order) |
              +-----------------------+-----------------------+
      170  AA |   cost (low order)    |   cost (high order)   |
              +-----------------------+-----------------------+
      172  AC | origNet (low order)   | origNet (high order)  |
              +-----------------------+-----------------------+
      174  AE | destNet (low order)   | destNet (high order)  |
              +-----------------------+-----------------------+
|     176  B0 | destZone              | destZone              |
|             +-----------------------+-----------------------+
|     178  B2 | origZone              | origZone              |
|             +-----------------------+-----------------------+
|     180  B4 | destPoint             | destPoint             |
|             +-----------------------+-----------------------+
|     182  B6 | origPoint             | origPoint             |
              +-----------------------+-----------------------+
      184  B8 | Attribute2(low order) | Attribute2 (highorder)|
              +-----------------------+-----------------------+
      186  BA | Attribute (low order) | Attribute (high order)|
              +-----------------------+-----------------------+
      188  BC | Msg Type  (low order) | Msg Type  (high order)|
              +-----------------------+-----------------------+
      190  BE |                      text                     |
              ~                    unbounded                  ~
              |                 null terminated               |
              `-----------------------------------------------'

*NUMBER* indicates this bit flag is used for something else other
than what it was orginally used for. None of the modifications to
the  bit flags will effect most 3rd party applications that
supports the Fidonet .MSG format.


      AttributeWord   bit       meaning
                      ---       --------------------
           *1*          0       Private
                        1       Crash
                        2       Recd
           *2*          3       Sent
                        4       FileAttached
                        5       Unused
                        6       Orphan
           *3*          7       Kill Sent,Only Use If A File Attach.
                        8       Local
                        9       HoldForPickup
           *4*         10       Reserved By Osiris
                       11       Unused
                       12       Unused
           *5*         13       No Send Msg Header
                       14       Unused
                       15       Unused


         *1*  : Not needed, Osiris considers ALL mail as Private  and
                automatically  sets  the PRIVATE flag  on  all  matrix
                messages sent FROM your system.
         *2*  :Not Used because Osiris automatically deletes the  MSG
               after is has been sent.
         *3* : Originally Kill message. However, Osiris automatically
               deletes  messages after they are sent. We use  this  to
               tell  Osiris to DELETE the file attach, after  it  has
               been sent.
         *4* : Originally defined as UNUSED so Osiris reserves it for
               internal use.
         *5*  : Original used to flag a message as a  RETURN  receipt
                reply. However, this is not needed by Osiris  because
                a return receipt reply is just a plan message. We  use
                it  to flag messages so that only the file  attach  is
                sent, the body and message header is not sent.

The nextReply and replyTo fields are reserved for the Message
Editor to use for reply linking. Since Osiris deletes messages
once they are sent, there would be nothing to LINK so we use the
two fields for something else.

Msg TYPE use to be the nextReply field in the message header. It
is now uses as a TYPE bit flag field to quickly ID the TYPE of
message.

The following attributes are used.

         Bit           Meaning
         ----------------------------------
         0             Unused
         1             Plain File Attach.
         2             File Request.
         3             Echomail Bundle
         4             Service Request
         5             Tic


Osiris can auto-detect the following TYPES if the ID bit flag is
not supported by the application that created the message.

Echomail Attaches.
TIC.
Service Requests.
File Requests.

It is considerably faster to use the ID bit flags.

The Attribute2 field use to be the ReplyTo field. It is used as a
secondary ATTRIBUTE bit flag field. Right now only 1 bit flag uses
this field, 0x0001. This indicates the message is to go DIRECT
passing any type of routing, Implied or Explicit.

None of the modifications to the .MSG structure will effect most
3rd party applications that supports the Fidonet .MSG format.

The zone and point fields, origin and destination, were originally
defined as OPTIONAL. They are not optional in Osiris because
Osiris uses all four subdomains.

If the application that created the message does not support
zones, it must zero those fields. Most programmers, good ones,
will automatically zero a file structure prior to using it so you
should never see wild zone numbers.

If Osiris finds any ZONE 0 fields, it will scan the body of the
message to see if there is an INTL line. If so, it will pull the
Zone addresses from the body of the message and REWRITE the
message header to include the proper zone addresses. If there is
NO INTL line and the zone is 0, Osiris will ASSUME the zone is
equal to your primary address.

While they are not need by Osiris, it also supports some of the
kludge line ^AFLAGS used by Frontdoor, D'bridge, and several other
mailers.

^AFLAGS supported are: IMM, KFA, and DIR

IMM will be remapped to the CRASH ATTRIBUTE.

KFA will be remapped to the KILL ATTRIBUTE.

DIR will be remapped to the DIRECT ATTRIBUTE.

Osiris only needs to do this once. If Osiris finds a ^AFLAGS in a
message, the message header attribute and type flag fields are
updated and the message header is written back to disk. This saves
a CONSIDERABLE amount of redundant processing and why we don't use
the ^AFLAGS approach in our applications.

(H378)
Phone.ctl is the phone number translation control file. This is
used to translate phone  numbers into a form that can be dialed
from your location.

All mailers require that you build something like this but they
generally do the conversions when you compile a fidonet nodelist.
Osiris doesn't because Osiris doesn't require that you compile a
Fidonet style nodelist.

Place Phone.ctl in the directory that contains the rest of the
mailer control files for the node you are configuring for.

Phone.ctl contains two fields per line, WHAT TO LOOK FOR and WHAT
TO REPLACE IT WITH.

E.g.

1314335 335
1314334 334

The  first  field contains the numbers to look for  and   if
they're found, replace those  numbers  with  the  contents of the
second field.

You should ALWAYS place smaller numbers at the bottom of  the
file.

1314335 335
1314334 334
1314 1
1814 1

Line 1 and 2 translates local phone numbers. Line 3 and 4
translates same-area-code to just a 1.

Let's assume  the original phone  number   was 13143346359.

Line 1 is ignored, 1314334 does not match 1314335.

It would be translated to 3346359 by line 2.

What if you want to simply remove numbers?

Lets take the 718 area code, it is someone unique. In the
718 area code, all dialing prefixes are local. By that I mean
you can call any number without prefixing it with a 1.

           Area Code
           |
        1 718 289 5612
               |
               Dialing Prefix


Instead of listing all the dialing prefixes you could use a semi-colon
in the second field.

1718 ;

If the number were 17182895612, Osiris would dial 2895612

Be careful with the semi-colon because most area codes aren't like this.
In the 314 area code, you would only have a few, generally less than 4,
dialing prefixes that do not require a 1.

For instances, if you live in Poplar Bluff and you wanted to call
13146860154 you would dial 6860154. If you wanted to call 13142430666 you
would dial 12430666.
(H379)
TIC is a method of automatically ECHOING files from system to
system the same way you would echo messages.

We produce a TIC compatible processor called OTC that works with
Osiris.

If Osiris detects a TIC control file, they have a file extension
of .TIC, it will execute a BATCH file called "TIC.BAT"

You can place any TIC processing instructions in this batch file.

(H380)
Raid is a TIC utility that allows remote systems to ADD, REMOVE,
or get a list of the TIC areas they have access to.

When Osiris scans the matrix area, building the matrix tables, and
it DETECTS a message addressed to RAID, it will call the batch
file "RAID.BAT".

You should place any PROCESSING instructions for YOUR raid program
in this file.

(H381)
Areafix is a program that allows systems picking up echomail from
you to automate the process of adding, removing, or getting lists
of their areas and available areas.

When Osiris scans the matrix area, building the matrix tables,
and it DETECTS a message addressed to AREAFIX, it will call the
batch file "AFIX.BAT".

You should place any PROCESSING instructions for YOUR areafix
program in this file.

(H382)

ROBOT.EXE is a small program that automates the sending of files
with the same name that change on a weekly or daily bases,
NODEDIFS, NEWSLETTERS, REPORTS, DATABASE FILES, SPREADSHEETS, etc.

ROBOT handles this by tracking the date and time stamps of each
file it sends in a small database (ROBOT.DAT).

Prior to SENDING the file, it checks the files date/time stamp
against the one in the data base and if it is different, the file
is sent.

ROBOT will flag the messages as NORMAL, DIRECT, FILE ATTACH. You
can, using an optional command line switch, have the file attaches
flagged as CRASH.

Robot needs to know WHO to send the file(s) to and you supply that
information in a control file, the name is up to you.

Each line in the control file contains a single DOMAIN address.

E.g.

1.200.10.0
1.300.10.0
1.400.33.2

To SEND a file, use the command line

ROBOT /S <File name> <Ctrl File Name>

<FILE NAME> is the name of the file to send. You can use a full
path, e.g. C:\OSIRIS\WORKSHEET.SPL

You can also include DOS wildcard characters, e.g.

C:\OSIRIS\WORKSHEET.*

ROBOT also supports three additional command line arguments, /I ,
/C, and /R <File Name>

/I Clears the DATE/TIME stamps for every file in the database.

/R <File Name> clears the DATE/TIME stamp for <File Name>. This
lets you resend the same file even if the date/time stamp on that
file has not changed.

/C Mark the message as CRASH.


(H383)
When Osiris receives an echomail bundle, during an inbound or
outbound mail session, it will attempt to run "ECHOMAIL.BAT" after
the connection has been terminated.

Osiris will shift to EMS or overlay itself to disk if EMS is not
available freeing all but 5K of memory prior to calling
"ECHOMAIL.BAT".

You would create echomail.bat and place any echomail processing
instructions in this batch file.

This simplifies processing for those that have trouble with batch
errorlevels.

(H384)
When you have a LARGE number of systems, it isn't practical to
keep a nodelist record of every system for several reasons.  You
don't do mail with every system in the network and it can take a
lot of disk space.

There are two methods we can use to get around the problem: Use an
addressing system that doesn't require a nodelist or develop an
IMPLIED routing system.

Routing: to direct, send, forward mail along a specific PATH to
its final destination.

Fidonet used the INTERNET to model its IMPLIED routing system.
Each Fidonet net has a HUB site. This HUB site is called the
NC (Net Coordinator) and the NC's address is ZONE:NET/0.0

Notice the node and point numbers are 0. All inbound and outbound
mail is "SUPPOSE" to be routed through the NC. The NC has other
duties but the primary one is routing mail for his, or her, net.

The concept of sending DIRECTLY to another system and in the
process, bypassing all routing simply did not exist until a
program called OPUS was released.

Back in those days, the Fidonet nodelist was relatively small and
keeping the entire nodelist ON-LINE wasn't much of a problem.

However, Fidonet is still based on the principle of routing and
direct mail is discouraged for many reasons.

The nodelist is now quite large, more than 34,000 systems. The
resulting compiled nodelist takes up a lot of diskspace. Since you
aren't going to be doing *DIRECT* mail with most of the systems,
note the *DIRECT*, this is a gross misuse of disk space.

While NC's do attempt to keep nodelists accurate, they must rely
on information from those in their net and  sometimes that
information is old and outdated. Phone numbers are wrong, mailers
are NOT always on-line when they are suppose to be, and finally
some systems may have dropped out of the network.

This we know from personal experence. Over the course of several
years, we've placed more than 10,000 outbound calls to other
systems to test our mailers compatiblity with other mailers under
all kinds of conditions.

Many mailers do not have A.I. routers so you may have used a
mailer in the pass that simply would not send a message if you did
not have a nodelist record for that system.

Osiris is MUST smarter than that and  you CAN do mail with ANYONE
in fidonet as long as you have ONE nodelist record, your NC's.

If you are an NC, all you need is the nodelist records for the
OTHER NC's in the network and nodelist records for those systems
in YOUR own net. You simply do not need nodelist records for
everybody in Fidonet.

                         Types of Routing

There are TWO types of routing, IMPLIED and EXPLICIT.

                         IMPLIED Routing

Implied routing is what Osiris does INTERNALLY and in absents of
any EXPLICIT routing instructions.

In other words, without giving precise and clear instructions on
HOW to send a message, you are implying that Osiris should use
network routing to get the message to its final destination.

                         EXPLICIT Routing

Explicit routing is just that. You are giving CLEAR and precise
instructions on how to send the message.

You might have used the DIRECT flag. The DIRECT flag is an
EXPLICIT routing instructions.

You might have used a special ROUTE control file during the event.
A ROUTE control file gives EXPLICIT routing instructions.

Throughout this document, when we say simply ROUTING, we are
referring to IMPLIED ROUTING.

                    How Implied Routing Works

Assuming that a Network has the ZONE of 1. It has 2 different
NETs, 1 and 2. Each NET has 2 NODES and each NODE has 2 POINTS.

1.0.0.0 <- Zone Level System.
1.1.0.0 <- NET 1
1.2.0.0 <- NET 2
1.1.1.0 <- NET 1, NODE 1.
1.1.2.0 <- NET 1, NODE 2.
1.2.1.0 <- NET 2, NODE 1.
1.2.2.0 <- NET 2, NODE 2.
1.1.1.1 <- NET 1, NODE 1, POINT 1.
1.1.2.2 <- NET 1, NODE 2, POINT 2.
1.2.1.1 <- NET 2, NODE 1, POINT 1.
1.2.2.2 <- NET 2, NODE 2, POINT 2.

This Network contains a total of 11 systems. However, the maximum
number of REQUIRED nodelist records for any system in the network
is 2 and in several cases 1. Yet, every system in the network can
communicate with every other system.

When 1.2.2.2 sends mail to 1.1.1.1, it is routed to 1.2.2.0. The
message will continue to traverse the network until it arrives at
its final destination.

1.2.2.2 -> 1.2.2.0 -> 1.2.0.0. -> 1.1.0.0 -> 1.1.1.0 -> 1.1.1.1

               Common Questions Concerning Routing

Q: I'm 1.235.400.0 and I'm suppose to route mail for those in my
net (235).

A:  No, you aren't and can't route mail for others in and OUT of
your NET.

At least you are not going to do that with IMPLIED routing.

Q: Why?

Because you're a NODE and a NODE can only route mail UP and DOWN.

In order to automatically route mail, you would also have to have
a NC address.

If you were 1.235.400.0 AND 1.235.0.0, Osiris could automatically
route the mail.

Q: Suppose someone sends a message to my system for 1.237.500.5
and I'm 1.235.400.0

A: Implied routing will route it to 1.237.0.0, he is the NC. It
will NOT route it to 1.237.500.0, that is the NCs job and
you are not an NC.

Q: It doesn't work that way in Fidonet!

A: Yes it does, however . . . most, not all, the mailers you find
have very limited routing capablities.

Q: Can I override Implied Routing?

A: Yes you can. You can use EXPLICIT routing instructions to force
mail to be routed in a specific manner.

Q: What if I belong to multiple networks?

A: Osiris can automatically route mail without instructions from
you, 99.9 percent of the time, even if you define 54 addresses in
54 different networks or 54 different addresses in the same
network.

Q: How is that Possible?

A: Osiris has an A.I. routing system.

                        What about CRASH?

CRASH means send ASAP but do it according to the DIRECT flag.

It is likely that you want your mail routed, you are at the POINT
level, but you want your mail to get to the NODE level ASAP. That
is where CRASH comes into play.

The Routing architecture I've outlined above is built-in and done
without any special instructions on your part. You don't have to
setup any type of route control files or even WORRY about how it
all works.

(H385)
There may be cases where you need EXPLICIT Routing instructions or
NO routing at all.

Osiris lets you define a special EXPLICIT route control file,
totally optional, for each event (events are also optional). You
define the route control file when you set up an event. See
section on events for details.

Each EXPLICIT route control file you create uses one EXPLICIT
routing command per line, unlimited number of lines.

Each command acts independently  of the last command, TOP DOWN
processing.

The following EXPLICIT ROUTE Nouns are available:

FORWARD FOR
NO ROUTE
SEND TO
ROUTE {} TO {}
HOLD
BUSY ATTEMPTS
FORWARD FILE
MAXIMUM CONNECTS
POLL
USE ADDRESS {} For {}
ECHO PROCESSING {ON/OFF}
GATE {} TO {}

Each Noun is followed by ONE of the following verbs:

Domain Address
Wild-Domain Address
FILES
TIC
CRASH
ECHOMAIL

A Domain address is a SPECIFIC 4 dimensional address.

E.g. 1.242.200.0

You MUST use a PERIOD to separate the individual subdomains.

A WILD-DOMAIN address is almost like the regular domain address
but, you can use the DOS wildcard character '*' in place of any or
all of the individual subdomains.

And like the DOS '*', '*' will match anything in that position.

E.g. 1.237.*.0

Would match 1.237.1.0, 1.237.2.0, 1.237.45.0, etc.

This is used to address systems by GROUPS rather than
individually.

Look closely at the TYPE of address the route noun uses. You can
use a straight domain address in place of a WILD-DOMAIN address
but you CANNOT use a WILD-DOMAIN address in place of a straight
domain address.

The WILD-DOMAIN address also supports the question mark.

You may use the question mark in place of any single digit within
the NODE or POINT fields.

E.g.  1.296.20?.0 or 1.296.?00.2?

The QUESTION mark will match any digit.

                FORWARD FOR {WILD-DOMAIN ADDRESS}

The default is forward for anyone, required on certain levels
within Fidonet and other public domain packet networks.

However, if you are on the POINT level you are not required to
forward for anyone. If you are on the NODE level and do not have
any POINT systems under you, you can disable forwarding without
violating network regulations.

Example:

FORWARD FOR 1.237.504.4
FORWARD FOR 1.*.*.*
FORWARD FOR 1.237.504.*
FORWARD FOR 1.237.*.*

To DISABLE FORWARDING, use your OWN address.

If you are 1.237.504.0, using the statement

FORWARD FOR 1.237.504.0

                         NO ROUTE {VERB}

You can override IMPLIED routing with the noun NO ROUTE followed
by a single verb. The verbs are:

{Wild-Domain Address}, FILES, CRASH, TIC, and ECHOMAIL.

Osiris DOES provide for routing file attaches. However not all
networks allow routing files and/or echomail and some mailers do
not support file routing.

                  SEND TO {WILD-DOMAIN Address}

Osiris defaults all messages, unless marked CRASH, to HOLD. In
other words, you have to tell it which systems it can call during
an event.

Messages marked CRASH are the only exceptions to this rule.

You tell Osiris to PLACE a call to a particular system or group
of system with noun SEND TO followed by  a Wild-Domain address.

SEND TO 1.*.*.*
SEND TO 1.237.*.0
SEND TO 1.237.*.*
SEND TO 1.*.0.0

         ROUTE {WILD-DOMAIN Address} TO {Domain Address}

This noun lets you route mail to a specific address other than the
one it would NORMALLY go to.

NOTE: DIRECT mail cannot be rerouted.

Examples

ROUTE 1.238.0.0 To 1.237.504.0
Route 1.*.*.5 To 1.100.10.10
Route *.*.*.* To 1.200.0.0

Take note of the second address, the one following the word 'TO'.
It is NOT a wild-domain address. This is a standard domain
address.

                           HOLD {VERB}

The noun HOLD is used in conjunction with  SEND TO. You can use
the following verbs with HOLD: {Wild-Domain address}, FILES, TIC,
and ECHOMAIL.

Example

HOLD 1.237.504.0
HOLD 1.234.100.*
HOLD *.*.*.*
HOLD FILES
HOLD TIC
HOLD ECHOMAIL

                FORWARD FILE {WILD-DOMAIN Address}

Forwarding files is optional but not all mailers support file
forwarding. Some NETWORKS do not support file forwarding.

Example.

FORWARD FILE 1.237.*.*
FORWARD FILE 1.235.505.*
FORWARD FILE 1.237.504.10

To DISABLE file forwarding, use your OWN address.

E.g. If you are 1.100.10.0 then

FORWARD FILE 1.100.10.0 will disable file forwarding.


                      BUSY ATTEMPTS {number}

While this is not a ROUTING noun, it does affect the delivery of
mail. If you are going to call a system during the event that is
KNOWN to be a very busy system, you may want to override the
number of busy signals a certain system is allowed to have.

                    Maximum Connects {number}

This determines the maximum number of CONNECTS to any single
system during this event. A mail transfer does NOT actual have to
take place. You ONLY have to establish the physical connection.

              {number} can be any number between 1 and 255.

                     Echo Processing {ON/OFF}

E.g.    Echo Processing Off
E.g.    Echo Processing ON

This overrides the Osiris configuration setting ECHOMAIL.BAT
YES/NO during the current event. The default setting will be
restored when the current event ends.

Q: What's it for ?

Assume you are an echomail hub and you send to 10 systems. During
an event, you send to system 2 but half way through the transfer,
carrier is lost.

You proceed to send to system 3 and after you send, system 3 has
echomail for you to pickup. You pick it up and import it (and
export any mail going back out).

After you send to 4,5,6,7,8,9, and 10, you cycle back to system 2
, the one you lost carrier with 1/2 through the transfer.

System 2 already has 1/2 of the file BUT . . . you have ADDED to
that file and the file's date stamp, time stamp, and file size has
changed. That makes it impossible for system 2 to resume the
transfer. He will either ask for a SKIP or start a NEW DUP file.
If he uses a DUP filename, his echo processor will not be able to
process the bundle and the OLD partial bundle will set there until
he manually deletes it.

By toggling ECHO PROCESSING OFF during a SEND event, you have done
way with this problem. Not to mention spending what might amount
to a LOT of time processing echomail when you really want to be
sending out what you already have.

"AND . . ."

Assume you are an echo hub for 20 systems. You have set-up a 3
hour event so those systems can POLL you for echomail. You  might
not WANT to process any echomail THEY drop off because it WILL
take away from the ON-LINE time others will have to PICK-UP.

Better to WAIT until AFTER the event when everyone has gotten
their mail before processing anything they dropped off.


Q: Why Echo Processing ON ?

You might want to set the default echomail.bat to NO and ONLY
process inbound echomail during one or two specific events.

Lets say you have a REAL busy BBS during the day/night. You might
want to delay processing inbound echomail until 3 or 4 o'clock in
the morning so your callers will have more TIME to get on-line.

        Use Address {Domain Address} For {Domain Address}

This lets you switch to a specific address when calling a specific
system  during THIS event.

E.g

Use Address 99.23.3.0 For 99.23.0.0

                      POLL {Domain Address}

This is the final NON-ROUTE noun. This guarantees that you will
have a message that will trigger a call to a specific system
during this event.

Domain Address is the FULL domain address for the system you want
to call. E.g., 1.235.504.9

Osiris handles the POLL command by looking to see if you have
CONNECTED to that system during this event. If you haven't, then
it will generate the POLL. If you have, POLL is ignored. Osiris
will flag incoming Mailer calls as an OUTBOUND call to that
system. The purpose is to prevent POLL requests. If that system
calls to pickup/drop off, you don't want/need to place the a call
TO him.

POLL doesn't create a PHYSICAL message. There is a flag in the
packet table, this holds information about your messages,
specifically for POLL.

A  NULL PACKET is ONLY used when Osiris builds the temporary
packet, prior to placing the call, and nothing was packed.

                 GATE {ZONE} To {Domain Address}

This a very SPECIAL noun and should only be used by a gateway
between two networks.

{ZONE} is the  of the "OTHER" network.

{Domain Address} is the full domain address of the system in the
"OTHER NETWORK".

Assuming your address is 99.0.0.0 which makes you the TOP most
system in TCP/PC network. Since you are the TOP system, you're
required to GATE matrix between your network and Fidonet (You may,
but it isn't required, also GATE files).

The Fidonet systems Domain Address is 1.1.99.0

The statement: GATE 1 To 1.1.99.0

Would ROUTE anything and EVERYTHING, including direct, that has
the ZONE of 1 to 1.1.99.0.

(H386)
                           Examples #1

Lets assume that you are a POINT with the domain of 1.237.504.2
and you do run a 24hr mailer. You want to call the NODE you are
under, 1.237.504.0, once a night to pickup echomail and any matrix
mail, or to drop off.

Other than that, your mailer is used to front for the BBS.

You'll need to set-up one special event to achieve this, see the
section on events for details on how to set-up the event.

Lets also assume that you defined the route control file for this
event as CALLHOST.CTL.

The first two lines, the ONLY two lines you need, in callhost.ctl:

POLL 1.237.504.0
SEND TO 1.237.504.0

The first line will make sure that there is SOMETHING to trigger a
call to 1.237.504.0. The second line tells Osiris to place a call
to 1.237.504.0, if mail exits for that system.

If you have an echomail bundle or outbound matrix mail going to
1.237.504.0, you HAVE to have the 2nd line or Osiris will not
make the call.

                           Example #2.

Lets assume that you are 1.237.0.0 and you are going to be routing
mail to and from 1.237.x.x, since you are the NC, this is a
requirement.

You'll want to do this late at night when the rates are low so
you'll need to set-up an event and a route control file for this
event. Lets assume the route control file is called SENDEM.CTL.

SEND TO 1.0.0.0
SEND TO 1.*.*.0
HOLD 1.237.*.*
POLL 1.0.0.0

                            Example #3

Lets assume you're address is 1.237.0.0 and you want to send out
all matrix mail to 1.237.x.x, EXCEPT for 1.237.500.0, and you do
NOT want to send Echomail or TIC files. Those you want held for
pickup.

SEND TO 1.237.*.*
HOLD 1.237.500.0
HOLD TIC
HOLD ECHOMAIL

Notice how the TOP DOWN command structure works?

Ok, but what if you want the TIC files for ONE specific system,
1.237.555.0, to GO.

SEND TO 1.237.*.*
HOLD 1.237.500.0
HOLD TIC
SEND TO 1.237.555.0
HOLD ECHOMAIL

You can make your customized routing files as simple as the first
example, or as complex (or worse . . .MUCH worse) as the last
example.

                        Common Mistake #1

ROUTE 1.237.504.0 To 1.100.10.5
HOLD 1.237.504.0

If your intention was to HOLD the mail for 1.237.504.0, it would
not work. The first line routed 1.237.504.0's mail to 1.100.10.5
and there would not BE any mail for 1.237.504.0

                        Common Mistake #2

HOLD 1.237.504.0
SEND TO 1.237.*.*

In this example, above, you are sending mail to everyone that has
the address of 1.237.x.x but 1.237.504.0 is down, hard drive blew
up, and his mail is suppose to be held.

The first line is executed and 1.237.504.0's mail was placed on
HOLD. However, you countermanded the HOLD command with the SEND TO
1.237.*.* command. Since SEND TO 1.237.*.* was the last command
executed, it is the one that is retained.

(H387)
                          TIPS On Speed

There are TWO things you can do that will greatly reduce
processing time.

While Osiris is exceptionally fast, the IMPLIED route manager
actual does an enormous amount of work when it scans the matrix
area.

Not only does it load the messages, but it calculates a number of
possible ROUTING paths to get the message to it's final
destination.

To do this, it must repeatedly access the nodelist to find out if
certain systems are or are not listed and this is the most time
consuming part.

To speed-up this process,  run a disk cache. If possible, use at
least a 128K cache.

With a 128K disk cache in place, Osiris can scan the nodelist at
the rate of 45,000 records per second (16 Mzh 386 with a 25 Mls
Hard drive. Faster computers and/or faster hard drives will
product better speeds.

Without a disk cache, same hardware, Osiris could only scan at
the rate of about 19,000 records per second.

The second thing you can do: DON'T KEEP THE ENTIRE NETWORK
NODELIST.

You simply do NOT need it. Even if you are a NC (Net Coordinator)
you only need the other NC's and the NODES in your net. Along with
maybe a few select systems you do mail with on a regular bases.

Compile the fidonet nodelist with the /R switch and use a personal
nodelist control file for the NODES under you and those you do
mail with regularly and let Osiris do its job. After all, isn't
that way you purchased a computer for in the first place?

Not only will this save you a great deal of disk space, but the
overhead processing time will be drastically reduced.

(H388)
Osiris has a MULTIPLE level security system for business that
need the ULTIMATE in data security.

Just how much security you want or need is up to you. Select the
ones you want to use and toggle the appropriate field in Mailer
Configuration.

                         Secure  Address

If any outbound call is placed and the answering system doesn't
pass the address Osiris used to PLACE the call, Osiris hangs up
figuring the phone company goofed or YOU goofed. If any system
CALLS IN, they MUST be listed in your nodelist or Osiris hangs
up.

                           Slick Willy

This security system is ALWAYS on and it prevents mail session
with ANYONE that passes your address. In short, if your address is
1.296.5.0 and I call you and pass 1.296.5.0 as MY address, Osiris
will hang up ASAP. If it is an EMSI session, Osiris checks ALL
the addresses the caller PASSES. If ANY ONE of them matches one of
YOUR addresses (primary or AKA) Osiris will HANG-UP.

                      Packet Level Security

This system is ALWAYS on. When Osiris UNBUNDLES an incoming
message it checks the FROM address against your primary and AKA
addresses and deletes ANY message that shows up as coming from one
of your addresses.

                     Session  Level  Password

If the CALLING system does NOT provide the correct SESSION
password, the one YOU defined in the nodelist record for THAT
system, Osiris hangs up.

                   Require Pwd For Mail Pickup

This augments the SESSION passwords by REQUIRING some type of
session level password in order for mail to be picked up. This
doesn't CHECK the password, it only requires that one be passed.

Case in point, you are a RC and you route all mail to the HOST/HUB
systems and they send it on to its final destination. Suppose you
have mail for 1.200.20.0 and it is routed to 1.200.0.0 (normally
would be) but 1.200.20.0 calls your system with a file request.

Under normal circumstances, Osiris would give him his mail. But,
someone could be FAKING 1.200.20.0's address in order to to
INTERCEPT his mail.

1.200.20.0 DOES use a session level password with his host,
1.200.0.0, and SO do you. BUT . . . you do NOT have a session
level password set-up for 1.200.20.0 because you don't do mail
directly with him.

If you decide to require ttoggle the require some type of passward
to yes, Osiris would NOT give him his mail because no passwords
were INVOLVED. His FILE REQUEST would be accepted and processed.

                  Secure Echomail/Secure Address

A little additional information about Secure Echomail. Some
systems, not many but a few, like to send MATRIX mail inside of an
ECHOMAIL archive. This simply will NOT work if you run Secure
Echomail.

That system has not been authorized to drop off echomail and
Osiris will delete the file. If you run secure echomail, and I
suggest that you do if you value your system, you might want to
notify those you do mail with on a regular bases NOT to attempt to
send you MATRIX mail inside an ECHOMAIL archive.

That is assuming you do not do echomail with them. If you do and
you HAVE authorized them to drop off echomail, they CAN place
matrix mail inside the echomail archive.

Now, secure addressing. Fidonet policy DOES state that you HAVE to
accept mail from anyone that calls during National Mail Hour.
However, many RC/NC will allow you to ignore this requirement.
Some will not so check with your RC or NC prior to engaging secure
addressing.

(H389)
File Request: A mailer calls your system and sends a  REQUEST file
containing the names of files he would like to have. If those
files are available, Osiris gives them to him.

You have to tell Osiris  what  directories you'll allow file
requesting out of by making a text file called Request.ctl and
placing it in the directory you have the mailer control files for
the node you are configuring.

Each line in Request.ctl contains a FULL DOS PATH ending with a
backslash.

Example:

C:\OSIRIS\FILES\GENERAL\
C:\OSIRIS\FILES\FRONT-END\
C:\OSIRIS\FILES\CATNIP\

                       Password Protection

To  password protect a directory, add a space  then  the password,
up to 80 characters.

E.g.

C:\OSIRIS\FILES\GENERAL\
C:\OSIRIS\FILES\FRONT-END\
C:\OSIRIS\FILES\CATNIP\
C:\OSIRIS\FILES\GAMMA\ ULTRA


The directory "C:\OSIRIS\FILES\GAMMA\" requires the  password
"ULTRA".

Osiris  supports the standard wazoo method  of  doing  password
requests, i.e., FILENAME !PASSWORD

Osiris also supports : FILENAME PASSWORD

                         Update Requests

Osiris supports standard wazoo UPDATE file requests. That is like
a normal file request except the sender and receiver compare the
date and time the file was created and the sender, Osiris in this
case, would only send the file if it is newer.

                      Minimum Request Speed

You can set a MINIMUM baud rate for File Requests via the FM
mailer configuration option.

                  Requests From UNKNOWN Systems

You can restrict file requests to ONLY those systems listed in
your nodelist via a switch setting in your Mailer Configuration.

(end)
