BBS Installation Instructions  

	           	V.1.0/OSK  (For RCIS V.2.1 - 2.3)

                     (c)1993 Steve Rottinger
                       All rights reserved
                      Last updated: 11/21/93


The following is a list of steps required to install the RCIS BBS
software in its minimal configuration.  Please see sysop.txt and
RCIS man pages for more detailed explanations of the the various
commands and features.


1)   Ensure that the nil device driver is in your boot file

2)   Replace your w8 window descriptor with log, which can be found
     in the BOOTMODS directory. 

3)   Make sure that you have a /dd (default drive) descriptor for
     your main hard drive. If you don't already have one, you will
     need to create one, or rename an existing hard drive descriptor
     to dd.

4)   Copy all of the files and directories from the BBS package
     to your main hard drive.  You can run rcp, or a similar utility 
	 on each floppy, to do this. If you received the BBS package
	 archived, you simply need to unarchive it in your main directory. 
          If you decide to use rcp, assuming that you want to
     copy all the files on /d0 to /dd, the command would be:

     rcp /d0 /dd

5)   Modify your startup file so that it does the following
     things:

     - Sets up and initalizes /log window

     - loads incoming, constat, conmod, read, filelist, msglist

	 - adds /dd/rciscmds to the PATH environment variable
     
     - for example, you might add the following lines:

     iniz /log ; display 1b 32 f 1b 33 0 1b 34 d c>/log 
     load constat incoming  conmod read filelist msglist

     a sample startup file has been included for you to examine.
     Its also a good idea to set the default settings on all of
     your windows to the way you want them.  This can be done
     with wmode. The chat program will open the next available
     window with its default settings, if a user pages you.

6)   Reboot your system so that the changes you made to the
     os9boot file take effect, the log window gets created, and
     the various modules get loaded.

7)   Modify /dd/sys/localinfo using EDIT or a similar text editor.
     A sample localinfo file has been provided to give you an idea 
	 of its format:

NODE_NAME PHONE# PASSWORD CITY/STATE SYSOP_NAME

Each of the fields are separated with a signal space, and none of
the fields should contain spaces. The description of each field
is as follows:

NODE_NAME : RCISNet site name. This field should be no more than
15 characters long, and should only contain uppercase characters
and underscores. If you don't have a registered RCISNet node
name. Chose any name that best reflects the name of your BBS, and
fits the described criteria.

PHONE# : Self-expanatory. Enter your country code (if out of US),
area code, prefix, suffix.

PASSWORD: Enter a password here 8 chars or less. This is used for
RCISNet transfers
          
CITY/ST: Enter your City and state changing spaces to underscores

SYSOP_NAME: Real name of SysOp, no spaces


8)   Create /dd/datafiles/lprefix. This file is used for
     auto-callback validation. The first line should your area
     code. The remaining lines contain the local prefixes for
     your area, one per line. A listing of local prefixes for
     can be found in the phone book.

     Note: If there is more than one area code in your local calling
     area, you can start the information for the new area code by
     placing "---" after the end of the information for the previous
     area code:


     AREA_CODE1
     prefix1
     prefix2
     ...
     prefix(n)
     ---
     AREA_CODE2
     prefix1
     prefix2
     ....
     prefix(n)


 9)  Adjust your modem for either dumb or smart mode.

     "dumb" requires the following modem settings:

     -Echo should be off
     -Result codes should be off
     -Carrier status must be normal
     -Modem should reset when DTR goes off
     -Auto-Answer must be on

     Your modem can be set up this way by sending it the
     following commands:

     ATQ1E0&C1&D3&W
     ATS0=1

     "smart" requires these settings:

     -Echo should be off
     -Numeric result codes must be sent
     -Carrier status must be normal
     -Modem should reset when DTR goes off
     -Auto-Answer must be on

     To set your modem this with, use the following commands:

     ATX1V0Q0E0&C1&D3&W
     ATS0=1


     14.4Kbps operation: 

         For use with a 14.4Kbps modem, you must use "smart" mode
     along with the following additional settings:

	 -Modem to Computer baud rate must remain constant.
     -Modem should send connection speed, as well as carrier speed
      after establishing a connection.

     use the following command:

     ATW1N1X4V0Q0E0&C1&D3&W


10)  Execute the shell script /dd/cocopal. Since RCIS was originally
     developed for the CoCo, colors used within the BBS, and within
     many BBS utilities use the default CoCo color set. Until some
     kind of facility can be written to easily switch between the
     two color sets, cocopal must be used to adjust the default
     colors of the MM/1 to those of the CoCo.

11)  Execute SysOp from an 80 column window. Enter the requested
     information for the status file. Don't worry if you don't set
     up everything correctly the first time around; you can go back
     and fix the settings later.

12)  Exit the SysOp utility by selecting option 6.

13)  Execute the BBS by typing: rcis [enter]

14)  Sign yourself on as a new user. Avoid using "sysop" as a
     handle, since it will confuse things if you decide to
     join a network in the future. 
     You should use the name you entered in the status file, for
     the SysOp's name, as your handle. Ignore any errors that
     might occur, and answer no to Auto-call back verification.

15)  Logoff the BBS with "G".

16)  run sysop, and use option 1 to change your access level to
     250, and upgrade your time limit.

17)  Use option 5 to set your first voting topic.

18)  Use option 4 to make all of your SIGs.
     Most of the menus are self-explanitory. Ignore SIG type,
     Usenet MSG#, first message, and last message. Those fields
     are either used by the system or for netmail.
     
     The SIG name must be a valid OS-9 file name (no spaces, or
     special chars except for _ and .)     

     The message limit is used to adjust the amount of messages
     you wish to allow the SIG to grow to. Once that limit has
     been reached, each time a new message is posted, the oldest
     one will be deleted.

     The Access requirement allows you to require a certain
     security level for a user to access that SIG. If the user's
     access level matches or is greater than the access
     requirement, the user will be permitted entry to that SIG.

19)  Use option 2 to add all of the file sections. You can add
     file sections to any of the SIGs that you just created.
     Again, the menus are mostly self-explanitory. The size limit
     refers to the size, in bytes that file section is permitted to
     grow to. Total size, is the current size of the file section.
     The directory name must be a valid OS-9 filename.

20)  Add tsmon to your startup file. Tsmon is a program that
     operates in the background, and is used to connect the BBS
     with your modems.  It waits for an incomming call, detects
     the baud rate; then runs "rcis".

     Tsmon has a couple of switches that need some mentioning:

     -f  Fast mode. In this mode, TSMon will not adjust the CPU
         to computer baud rate.  The baud rate the port is currently
         set for will be used.

     -p  Pulse mode.  Use this switch, if the modem is on a Pulse
         dialing only line.

     add the following line to your startup, substituting port for
     the name of your modem port, and {opts} for the options, as
     described above:

     tsmon /port {opts}&

     For each modem you have, you will need to run a tsmon on the
     corresponding port. So far, a maximum of two modems per
     computer has been tried. While the BBS software will handle
     up to 32 users; the total amount of users you will be able
     to handle depends entirely on your hardware.

21)  Create /dd/sys/crontab. Crontab contains a list of scheduled
     events, and at what time they occur. This file is read by
     rcron. The format of this file is as follows:
     
B MN HH DY MH DW command

B - Just place this before each line. This is here for further
    expansion of rcron.

MN - Minute

HH - Hour (24 hour format)

DY - Day

MH - Month (1-12)

DW - Day of week (0-6) 0=Sunday

Any of the time fields can contain an "*" this acts as a
don't-care.

The line:
B 03 00 01 * * arcup

tells rcron to execute arcup in the background at 12:30, on the
first day of each month.
Be sure to examine the sample crontab that was included.

The following maintenance utilities should be included in your
crontab:

arclog - run once a day. Archives the callerlog for the day
arcup  - run once a month. Archives the upload list for the month
crunchmb - run once a day. Necessary maintenance for message bases
optmsg /dd/mail - run once a week. Cleans mail section

22)  Place the line: rcron& in your startup file

23)  Make sure your clock is set correctly at all times. The BBS
     is very dependant upon the system time. It uses the system
     time for determining when to start different events, and
     what messages are new. Especially if your system is part of
     a network, if the time isn't correct, duplicate messages
     could be sent.  A hardware clock is strongly recommended. If
     you need to execute a command to update the software clock
     from the hardware clock every once in a while, you can place
     that command in /dd/sys/clockup.

24)  Create /dd/datafiles/loginprogs. Loginprogs is a one line
     file that gets sent to a shell every time a user logs
     on. Its useful for displaying the users online,
     bulletins,etc. A sample loginprogs has been included.


This completes the installation process. Be sure to read sysop.txt,
and the RCIS MAN pages for more details on BBS operation.