home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Phoenix CD 2.0
/
Phoenix_CD.cdr
/
02a
/
om42_1.zip
/
OMEGA42.DOC
< prev
next >
Wrap
Text File
|
1989-11-09
|
56KB
|
1,613 lines
OmegaComm VERSION 4.2 DELUXE
Kingdom Enterprises
c/o Larry D. Loiselle
Route 2, Box 75-G
Manor, TX 78653
November 9, 1989
OmegaComm VERSION 4.2 DELUXE
TABLE OF CONTENTS
Page
-------------------------------------------------------------
Introduction................................................1
OmegaComm Features..........................................2
Files Included With OmegaComm...............................4
File Structures.............................................5
Door Programs...............................................7
Using CONFIG.EXE............................................8
Configuration Worksheet....................................10
Final Setup Steps..........................................16
Main Sysop Work Area.......................................18
Sysop Files Work Area......................................19
Sysop Commands.............................................20
Handshaking Conventions....................................21
User names and Passwords...................................21
Time Limits and Downloading................................21
Message System Notes.......................................22
Private BBS and Remote Users...............................22
BBS-BATS.DOC, FILES.DOC, LBR.DOC, & PROTOCOL.DOC ..........22
............................................................
. .
. OmegaComm VERSION 4.2 DELUXE .
. Kingdom Enterprises .
. Copyright 1989 All Rights Reserved .
. .
............................................................
REQUESTS FOR INFORMATION
KINGDOM ENTERPRISES
C/O LARRY D. LOISELLE
RT. 2 BOX 75-G
MANOR, TEXAS 78653
THIS PROGRAM IS PROVIDED AS IS WITHOUT ANY WARRANTY, EXPRESSED OR
IMPLIED, INCLUDING BUT NOT LIMITED TO FITNESS FOR A PARTICULAR PURPOSE.
THE AUTHORS ACCEPT NO RESPONSIBILITY FOR ANY DAMAGE TO EQUIPMENT OR
OTHER SOFTWARE THAT OCCURS AS A RESULT OF USING THIS PROGRAM.
OmegaComm is NOT public domain software. This program was written for
and given to God. It is provided for use only by christian sysops of
christian BBS's. Its primary purpose is for the advancement of the
Kingdom of God and the dissemination of the information about His
glorious Son. Violations are between you and the Living God. If you
like the program and plan to use it, it is suggested that you add an
additional $40.00 to the offering you give to your local church.
We wanted a quick, efficient bbs program for the christian community.
We wanted it to be easy to implement, easy to maintain, easy to make it
what you want quickly, and most of all we wanted it to be bug free.
IF YOU ARE INTERESTED IN EVENTUALLY NET WORKING WITH OTHER OMEGACOMM
BBS's AND RECEIVE SOFTWARE REVISIONS, SEND ME THE FOLLOWING INFORMATION:
1. BBS Name
2. BBS phone number
3. Hours of operation
4. Acceptable baud rates
A special thanks to Jay Kole for this fantastic documentation and Walter
Scott for his patient debugging.
Page 1
OmegaComm VERSION 4.2 DELUXE
INTRODUCTION
We have accomplished all this and more. OmegaComm has grown to be a huge
program of thousands of lines, and continues to grow. Tightly written
routines are continually being modified to enhance the speed and
efficiency of the program. We sincerely I hope that you enjoy this
sophisticated communications program and find many ways to use this
versatile software. We also appreciate any suggestions or comments
regarding this program and ways to improve performance.
*** OmegaComm 4.2 FEATURES ***
- Supports drives A through F
- The user can select either ASCII, ANSI Color Graphics, or
ANSI Color Only menus
- The user can select expert mode and flash (quick entrance and
exit) mode
- The user can select whether or not to use HOTKEYS (instant
response)
- The SYSOP can elect to use ASCII(MONO) & ANSI(COLOR), or
ASCII only
- PC-DOS and MS-DOS compatible
- The MENU files in ASCII AND/OR ANSI format
- User profile (password, terminal parameters, personal info)
kept on file
- Private and public messages supported
- Sysop defined restricted message area(s)
- Can be configured as a private BBS
- Set up for NINE access levels (0-9)
- Different time limits for each access level (SYSOP CONTROLLED)
- Auto validation option
- Sysop sets minimum access level to be able to enter the
files area
- Sysop sets minimum access level to have access to all file
sections
- Sysop sets minimum access level to be able to read/enter
messages
- Sysop sets minimum access level to have access to
restricted message section(s)
- Sysop sets minimum access level to have access to Doors
- Sysop defines the names of up to 20 File Sections
- Sysop defines the names of up to 20 Message Sections
- Supports multiple subdirectories/drives for the files
- Enhanced message section with delete, undelete, move, and
packing
Page 2
OmegaComm VERSION 4.2 DELUXE
FEATURES (cont'd)
- Message section allows reply option to messages read
- Message section allows search by subject
- Message section allows following replies
(checking/threading replies)
- Upload a message using ASCII protocol
- Supports up to 255 bulletin files (99 bulletin menus)
- Will currently handle 1500 files
- Will currently handle 1500 active messages (#1 - #65535)
- Number of accesses of each file recorded
- XMODEM (CRC/checksum/1k) uploads/downloads
- Qmodem-G, Imodem, & WXmodem uploads and downloads
- Jmodem, Lynx, PcKermit, SEAlink, Ymodem, Ymodem-G & Zmodem
BATCH uploads and downloads
- Downloads controlled by available time and download factor
- Upload time restored to the user
- Search for a file by file name or keyword/string
- Review new files by last date on or by specified date
- View contents of archive files (OmegaComm has built in view
procedures - no limit to the number of different file
compression methods)
- View a text file within an archived file
- Extract a part of an archive file and download it
- Test the integrity of an archive file
- Type text file to the screen
- Calls logged with sign-on and sign-off times
- Autobaud - Auto-answer
- Support 300 - 1200 - 2400 - 9600 BAUD (NO PROMISES ON THE
9600 BAUD SINCE THE MANUFACTURERS DON'T HAVE UNIFORMITY!)
- 2048 byte input buffer and 2048 byte output buffer
- Sysop window at the bottom of the screen that tells you the
name, password, and access level, telephone number, baud
rate, and whether the chat mode is on/off. If a caller
tried to page you and no luck the window displays "PAGED"
- Two sysop work areas (may be entered without entering the BBS)
- User packing (delete) ... also deletes their messages
- The sysop can change user levels after reading the message
- The sysop can edit user data from the SYSOP1 work area
- The user can leave a comment if sysop not available for
Page and as they leave the board
- The sysop (level 9) can drop to dos in local or remote status
- Sysop can drop to dos while a caller is online
- Sysop can change caller stats while a caller is online
- Full board record that includes: user actions, user log, &
comments
- Comments are part of the message section (last message
section.) Only level 9 can read the comments
- Doors at the main menu and file menu
1. Door to external games and other programs at the main
menu supports 255 doors or 9435 (255 x 37) with Doorway.Exe
(99 doors menus)
2. News Door (News.Bat) using a program like Today.Exe
3. Door to drop to dos in both sysop work areas
4. Door for upload/download with DSZ.COM, JMODEM.COM, LYNX.EXE,
PCKERMIT.EXE, CLINK.EXE, & QMXFER.COM
(upload.bat & download.bat)
5. VIEW.BAT, LIST.BAT, EXTRACT.BAT and TEST.BAT for work with
the archive files.
*************************************************************
*************************************************************
Page 3
OmegaComm VERSION 4.2 DELUXE
INCLUDED FILES
The following files are included with OmegaComm:
1. OMEGA.EXE/OMEGA.OVR - main program
2. CONFIG.EXE - Creates OMEGA.CNF
3. MENUS:
BULLET(X) ANS/ASC
CHKMAIL ANS/ASC
CONTROL ANS/ASC
DOOR(X) ANS/ASC
FILEMENU ANS/ASC
FILEEXP ANS/ASC
FLASH ASC
GOODBYE ANS/ASC
HOWDY(X) ANS/ASC
INFO ANS/ASC
MAINMENU ANS/ASC
MAINEXP ANS/ASC
MESSEXP ANS/ASC
NOCHAT ANS/ASC
OPENERS ASC
QUIZ ANS/ASC
RULES ANS/ASC
SYSOP1 ANS/ASC
SYSOP2 ANS/ASC
WELCOME ANS/ASC
(X) = 1 TO 99
4. BULL1.TXT (for example only)
5. NEWS.BAT (FOR OPTIONAL NEWS DOOR)
6. RCTTY.BAT AND RCTTY.INF (for remote drop to dos)
7. DSZ.COM, LYNX.EXE, PCKERMIT.EXE, WXFER.COM, JMODEM.COM,
CLINK.EXE, & QMXFER.COM (use UPLOAD.BAT/DOWNLOAD.BAT)
8. DOOR(X).BAT + DOORWAY.ARC -- Operates the Doors.
9. View.Bat, List.Bat, Extract.Bat, and Test.Bat for work with
the archive files
* NOTICE: If the SYSOP makes the decision not to use ANSI on
their board the XXX.ANS files may be deleted. If
the SYSOP decides to offer both ASCII and ANSI
then all these files are needed. All the menu
files can be changed. You can use programs like
ANSIDRAW or THEDRAW to create both the ASCII and
ANSI menus. Also, if you wish to use bulletins set
up files and use the name of BULL(1-255).TXT
(limit= 255).
ALL BULLETINS GO ON THE BULLDRIVE. IF YOU WANT THEM TO BE AVAILABLE FOR
DOWNLOAD THEN MAKE SURE THIS IS THE SAME SUBDIRECTORY/DRIVE AS THE
LOCATION OF THE FILE SECTION SUBDIRECTORY/DRIVE.
Page 4
OmegaComm VERSION 4.2 DELUXE
FILE STRUCTURES
You will need to set up a number of directories to run OmegaComm. The
directory names shown in this documentation are for example only. You
may use them for your board if you wish, or you can rename them to
something that suits your tastes. I strongly suggest you plan the names
and record them before running the CONFIG program.
\BBS : Contains the following files:
OMEGA.EXE
OMEGA.CNF
OMEGA.OVR
EXTERNAL PROTOCOLS
DSZ.COM
LYNX.EXE
WXMODEM.*
JMODEM.*
CLINK.EXE *
PCKERMIT.EXE *
QMXFER.COM *
DOOR PROGRAMS
Any DOOR programs you wish to run, such as DoorWay,
Gateway, Watchdog, etc.
* DOORX.BAT
* RCTTY.BAT
* RCTTY.INF
OTHER FILES: OMEGA.CNF is written by CONFIG.EXE
FILES.BBS is written by OMEGA.EXE
\MENUS : This is optional - menus can go on the main drive
or in their own directory.
* BULLET(X) ANS/ASC
* CHKMAIL ANS/ASC
* CONTROL ANS/ASC
* DOOR(X) ANS/ASC * ALL OF THESE FILES CAN BE
* FILEMENU ANS/ASC CUSTOM TAILORED TO YOUR NEEDS
* FILEEXP ANS/ASC USING A PROGRAM LIKE ANSIDRAW
* FLASH ASC OR THEDRAW.
* GOODBYE ANS/ASC
* HOWDY(X) ANS/ASC
* INFO ANS/ASC
* MAINMENU ANS/ASC
* MAINEXP ANS/ASC
* MESSEXP ANS/ASC
* NOCHAT ANS/ASC
* OPENERS ASC
* QUIZ ANS/ASC
* RULES ANS/ASC
* SYSOP1 ANS/ASC
* SYSOP2 ANS/ASC
* WELCOME ANS/ASC
(X) = 1 TO 99
Page 5
OmegaComm VERSION 4.2 DELUXE
FILE STRUCTURES
The following directories should be set up:
\USERS : OMEGA.EXE writes the following files to this
directory:
USERIDS.BBS
BOARDREC.BBS
\MESSAGES : OMEGA.EXE writes the following files to this
directory:
MESSAGES.BBS
Ox.BBS (where x = the message number)
\UPLOAD : This is the directory that you need to copy
all your .ARC, .PAK or .ZIP files to before
posting them in the various file
directories. This is also the directory
that users uploads will go to before you
post them.
\PRIVATE : This is the directory in which you can keep
any private files -- available to users with
access levels of 8 or 9 only, or to the
Sysop.
\FILESx : Where x = 1 to 17. These are the various
file sections from which users can download.
It is a simple setup. If you wish, you can
change the names to correspond with the file
section names you plan to use.
\BULLS : This is where you place your bulletin files.
If you make the bulletins available for
downloading, then place them in one of your
\FILEx directories. Make sure you specify
this when running CONFIG.EXE.
Any of these directory names can be changed. It will make your life
easier if you decide on the directory names before you run the
CONFIG.EXE program.
If you plan to use GATEWAY as a door program, then you'll also need to
put GATEWAY2.SYS in the root directory, and include DEVICE=GATEWAY2.SYS
in your CONFIG.SYS file.
Page 6
OmegaComm VERSION 4.2 DELUXE
DOOR PROGRAMS
Doors are programs that run outside of OmegaComm. You can run any
program external to OmegaComm AS LONG AS THE EXTERNAL PROGRAM IS SET UP
TO WRITE TO THE COMM PORT AND NOT THE VIDEO MEMORY. The program that
access doors must be placed on the main drive (\BBS in this
documentation).
Door programs that work well with OmegaComm are:
DOORWAY : A program written by Marshall Dudley. It has a lot
of features, including being able to run as many
doors as your computer's memory will allow. DoorWay
also allows 37 programs per door, so you have the
possibility of running 9435 doors on OmegaComm! It
also serves very well as a remote drop to DOS. It is
available from DataWorld BBS - (615) 966-3574. Look
for the file called DRWY146.ZIP -- although the
numbers in the filename may change with newer
VERSIONs of DOORWAY.
GATEWAY : Included in the registered VERSION of OmegaComm. It
works well, and is simpler to set up than DoorWay,
but doesn't have all the features.
WATCHDOG: This is not really a door program, but one you might
want to include in your DOORx.BAT files. It monitors
the carrier while a caller is in a door (something
DOS can't do) and if the carrier is dropped, it will
reboot your system and start your BBS up again.
Great for unattended BBS operation. This is available
on my BBS -- (512) 272-5770. My BBS is only in
operation on Sundays from 8am to 2pm, and Wednesday
evenings from 7pm to 10pm.
DOORx.BAT: Where x = 1 to 99. These are the batch files that
will run the programs accessed through the doors.
Using WATCHDOG and GATEWAY, a batch file to run a BBS
listing program called TELEPROG would look like this:
DOOR1.BAT ECHO OFF
WATCHDG1 ON
CTTY GATE1
CLS
ECHO Now Loading Telprog......
TELEPROG ANSI
CTTY CON
WATCHDG1 OFF
Substitute your programs name and parameters for other DOORx.BAT's.
Page 7
OmegaComm VERSION 4.2 DELUXE
USING CONFIG.EXE
CONFIG.EXE writes the file OMEGA.CNF, which contains information about
your particular BBS setup. This includes telling OmegaComm where to
look for the Users files, Message files, and files available for
downloading. It also includes your modem's reset, initialization,
off-hook and answering commands, as well as the comm port you're using,
baud rates allowed, access levels for certain sections of the board,
and whether the board is private or open.
A few things you should know before running CONFIG:
- Drives A through F may be used. the program seems to work better
if the subdirectories are only one level down from the root
directory i.e., C:\BBS instead of C:\BBS\FILES. Also, with some
machines, drop to DOS will only work if the maindrive (the one
with OMEGA.EXE on it) is also the drive with the AUTOEXEC.BAT
file.
- The files shown earlier as being on the maindrive (in this
example, \BBS) MUST be on the maindrive. NO EXCEPTIONS. OmegaComm
will stop running and return you to a DOS prompt if it can't find
the files it needs on the maindrive.
- Files for downloading must FIRST be placed in the subdirectory
allocated for UPLOADS (next to the last file section). They then
must be installed, one by one, on the board in local mode before
they are available for downloading. The files you receive from
users end up here as well, and you will have to install them
before they are available to all users.
- If you set ANSISCR=FALSE in CONFIG, then your board will only use
ASCII menus. Setting ANSISCR=TRUE allows your board to use ANSI
screens as well, which include color, music, and animation if you
want. If your board runs on a monochrome system, you can still
provide your users with color menus by having DEVICE=ANSI.SYS in
your CONFIG.SYS file. Example:
FILES=20
BUFFERS=20
DEVICE=ANSI.SYS
Of course, you will have to have the ANSI.SYS driver that came on your
DOS diskette installed on the root directory.
- VIEWING COMPRESSED FILES: You may use from one to six different file
compression programs. OmegaComm uses data supplied in the VIEW.BAT,
TEST.BAT, EXTRACT.BAT, & LIST.BAT files and creates ARC.TMP which is
then displayed on the screen for the user. You can do these things:
a. View the contents of an archive file
b. View a text file within an archive file
c. Test the integrity of an archive file
d. Extract a part of an archive file and download it
e. Download the entire archive file
Page 8
OmegaComm VERSION 4.2 DELUXE
USING CONFIG.EXE (cont'd)
- IMPORTANT WARNING!!! MAKE SURE THAT YOUR SELECTED MAINDRIVE IS
LISTED IN THE PATH IN YOUR AUTOEXEC.BAT FILE. IF IT IS NOT, THEN
DROP TO DOS, DOORS AND WATCHDOG WILL NOT WORK! YOUR AUTOEXEC.BAT
FILE SHOULD CONTAIN A LINE SUCH AS:
PATH C:\;C:\DOS;C:\OmegaComm
- Any external protocols you are going to use MUST be on the main
drive. DSZ.COM from Omen Technologies is includes as a minimum,
since it gives you these protocols:
Qmodem-G
Xmodem Checksum, Xmodem CRC, and Xmodem 1K
Ymodem-G
Ymodem Batch
Zmodem Batch
If you have a problem with DSZ.COM it is probably because you have
some memory resident program (such as Sidekick) that conflicts with
DSZ.COM.
OmegaComm also supports the following protocols:
Imodem
Jmodem Batch
Lynx
SEAlink
Wxmodem
PcKermit Batch
NOTE: THE UPLOAD.BAT AND DOWNLOAD.BAT FILES CONTAIN THE COMMAND
PARAMETERS FOR THESE FILE TRANSFER PROTOCOLS. THESE TWO FILES GO ON
THE MAINDRIVE.
Page 9
OmegaComm VERSION 4.2 DELUXE
CONFIGURATION WORKSHEET
Before running CONFIG.EXE, you may want to go through the following
worksheet and make some decisions about how your board will be set
up. Keep in mind the following:
-- Paths you specify for the maindrive, users files, messages, etc.,
can be no longer than 35 characters.
-- On many machines the subdirectories work better if they are only
one level down from the root directory such as C:\OmegaComm
instead of C:\OmegaComm\FILES. One level down should never be a
problem, but more than one level down might be.
-- OmegaComm supports the creation of restricted message and files
areas. Access is restricted by a user's access level. You'll
need to decide how many file and message sections you wish to use
(up to 20 each), and which section marks the beginning of the
restricted sections. You do not have to use all 20 file or
message sections -- just press ENTER at the prompt when running
CONFIG.EXE.
1. Which serial port will you be using (1 or 2)?
__________________________
2. Will you be using ANSI screens? Write TRUE if you will be,
FALSE if you don't plan to.
__________________________
3. Will this be an open or private board? An open board allows
anyone to call in and be registered; a private board allows
only users signed in by the Sysop. If the board will be open,
write TRUE. If it's private, write FALSE.
__________________________
4. You can have an optional news door using NEWS.BAT and a program
like TODAY.BAT. Do you want to use this news door? Write TRUE
or FALSE.
---------------------------
5. Where is the main drive going to be? (eg. C:\OmegaComm)
__________________________
6. Where is the menu drive? This is where all your menus go.
They can be placed on the main drive, or can reside in a
separate directory (eg. C:\MENUS).
__________________________
Page 10
OmegaComm VERSION 4.2 DELUXE
CONFIG.EXE WORKSHEET
7. Where is the message drive? This is where OmegaComm stores
messages (eg. C:\MESSAGES).
__________________________
8. Where is the bulletin drive? If you plan to make the bulletins
available for downloading, you MUST make this directory one of
your file section directories. If not, you can place them in a
separate directory (eg. C:\BULL).
__________________________
9. Where is the user drive? This is where OmegaComm stores all
user information (eg. C:\USERS).
__________________________
10. What is the top baud rate supported by your modem? Examples:
300, 1200, 2400, 9600. Warning: There is no guarantee that
9600 baud will work, since there is no uniformity among 9600
baud modem manufacturers at this time.
__________________________
11. What is the minimum baud rate you want to support? Examples:
300, 1200, 2400.
__________________________
12. What time factor do you wish to use? The time factor is
multiplied by the user's access level to determine how much
time per day that user is allowed. For example, if you wanted
all normal users to have an access level of 4 and 60 minutes of
board time per day, you would set the time factor at 15 (4 x 15
= 60).
__________________________
13. What is the download factor? This determines how many files
users are allowed to download before having to upload some
files. For example, a download factor of 5 would allow new
users to download 5 files without uploading, and thereafter
they would have to upload one file for every five they take.
__________________________
14. What is the minimum access level required for users to have
access to the files section? Access levels are from 0 (locked
out) to 9 (reserved for the Sysop).
__________________________
Page 11
OmegaComm VERSION 4.2 DELUXE
CONFIG.EXE WORKSHEET
15. What is the minimum access level required for users to have
access to the message section?
__________________________
16. What is the minimum access level required for users to have
access to doors programs? (NOTE: If you don't plan on using
the DOORS feature, set this to level 9).
__________________________
17. What is the minimum access level required for users to NOT have
to see the rules (RULES.ANS/ASC).
__________________________
18. What is the minimum access level required for users to be able
to use the FLASH feature?
__________________________
19. How many message sections will you be using? (1 to 20)
__________________________
20. How many files sections will you be using? (1 to 20)
__________________________
21. What is the file section number where the uploads will go?
__________________________
22. What is the minimum access level required for users to have
access to restricted message areas? (0 to 9)
__________________________
23. Where do the restricted message area(s) begin? (1 to 20)
__________________________
24. You may select automatic validation, where the callers access
level will be raised automatically after he makes his first
call to your board. The number you specify here will be the
access level the user has after his first call - 1 to 7. If
you do not wish to use automatic validation, enter a 0.
__________________________
Page 12
OmegaComm VERSION 4.2 DELUXE
CONFIG.EXE WORKSHEET
25. You may use up to 99 bulletin, doors, and howdy menus. The
program will page through these menus.
Number of Bullet(X) menus _____________
Number of Door(X) menus _____________
Number of Howdy(X) menus _____________
26. What file compression methods will you be using? What are the
compressed file extension and the appropriate commands?
Example: .ARC and PKXARC -V or .LZH and LHARC V You can have
from 1 to 6 ..................................
Extension Compression Program Command
1. _________ __________________________
2. _________ __________________________
3. _________ __________________________
4. _________ __________________________
5. _________ __________________________
6. _________ __________________________
27. Now for the hard part. You will need to study the manuals that
came with your modem. You will need to figure out the right
strings and delays. This is the most difficult part of the
setup since various modems are so different. Hayes compatible
does not necessarily mean 100% Hayes compatible! OmegaComm
looks for numeric result codes. ASCII 49 (1) = 300 baud, 53
(5) = 1200 baud, and 49+48 (10) = 2400 baud. You will see
these on your screen when the caller rings into your board.
All modems are different, so if you are having a problem call
the modem's manufacturer.
WITH AUTO BAUD MAKE SURE THAT DATA TERMINAL READY IS OFF AND
CARRIER DETECT OVERRIDE IS OFF. The are switches on the US
Robotics modem. External modems sometimes need to be treated
differently than internal modems. If you have tried every
possible combination and it still won't auto answer, the
problem may be in your ROM BIOS. Some pc clones are more IBM
compatible than others.
You may use the tilde / ~ / within a modem string to indicate a
1/2 second delay. You may also use '{' or '^M' to indicate a
carriage return. OmegaComm automatically send a carriage
return at the end of a modem string so the extra one may not be
necessary. On most Hayes compatible modems the string ~~+++~~
will put the modem in command mode.
PLEASE NOTE: The modem strings shown as examples below have
been tested and are known to work on the following modems :
US Robotics 2400 Internal
Hayes 1200 and 2400B
Avatex 1200 External
Everex 1200 and 2400 Internal
28. What is your modem's initialization string? We recommend these
as a starting point:
MAKE SURE THAT IN YOUR MODEM SETTINGS (SWITCHES OR STRINGS)
THAT DATA TERMINAL READY IS OFF AND CARRIER DETECT OVERRIDE IS
OFF (these are switches on the US Robotics modem). On the
Hayes modem &D1 and &C2 handle DTR and CD.
~~+++~ATS0=1H0S7=255Q0V0E0M0X4~~{ (for autobaud)
~~+++~ATS0=0H0S7=255Q0V0E0M0X1 (usually requires ATA
forced answer cmd.)
initialization String? __________________________
Page 13
OmegaComm VERSION 4.2 DELUXE
CONFIG.EXE WORKSHEET
29. What is your modem's hang up string? Possible strings are:
~~+++~ATH0 or ~~+++~ATH
Hang Up String? __________________________
30. What is your modem's reset string: Possible strings are:
~~+++~ATZH0 or ~~+++~ATZH0S0=1{~~
___________________________ __________________________
31. What is your modem's off-hook string? We use ~~+++~ATH1
__________________________
32. What is your modem's answer string? This is usually used with
ATS0=0. You can leave this blank if you do not want to force
your modem to answer . We use ATA. If you use ATS0=1 it is
best left blank.
__________________________
33. What is your modem's delay between answering the phone and
setting the baud rate? We use 500 (1/2 second).
__________________________
34. Handshaking protocols: If you do not have switches then you
will have to control these by add the proper codes for you
modem in the modem initialization string!
XONXOFF : This controls the XONXOFF software handshaking
protocol.
Recommend (TRUE) _____________________
CTS/RTS : Hardware handshaking is used with high speed
modems and null modem cable links.
Recommend (TRUE) _____________________
DSR/DTR : Hardware handshaking is used with high speed
modems and null modem cable links. Sometimes
a null modem cable will allow one type of
handshaking and not another.
Recommend (TRUE) _______________________
Page 14
OmegaComm VERSION 4.2 DELUXE
CONFIG.EXE WORKSHEET
35. Now specify the descriptions of the message sections. You may
use up to 20 message areas. The description can be no longer
than 35 characters. Remember, the last message section is
reserved for comments.
1. _____________________________________________________
2. _____________________________________________________
3. _____________________________________________________
4. _____________________________________________________
5. _____________________________________________________
6. _____________________________________________________
7. _____________________________________________________
8. _____________________________________________________
9. _____________________________________________________
10. _____________________________________________________
.
.
.
20. _____________________________________________________
36. Now specify the file section descriptions, their locations, and
minimum access levels. For example, a description could be
"DOS Files", location C:\DOSFILES, and minimum access level
"5". You may use up to 20 file sections. Remember that the
descriptions and paths can be no more than 35 characters each,
and that it will work better if the directories are only one
level down from the root directory (C:\DOSFILES instead of
C:\OmegaComm\DOSFILES).
MINIMUM
DESCRIPTION LOCATION ACCESS
1. ___________________________ _____________________ _______
2. ___________________________ _____________________ _______
3. ___________________________ _____________________ _______
4. ___________________________ _____________________ _______
5. ___________________________ _____________________ _______
6. ___________________________ _____________________ _______
7. ___________________________ _____________________ _______
8. ___________________________ _____________________ _______
Page 15
OmegaComm VERSION 4.2 DELUXE
CONFIGURATION SETUPS
9. ___________________________ _____________________ _______
10. ___________________________ _____________________ _______
11. ___________________________ _____________________ _______
12. ___________________________ _____________________ _______
13. ___________________________ _____________________ _______
14. ___________________________ _____________________ _______
15. ___________________________ _____________________ _______
16. ___________________________ _____________________ _______
17. ___________________________ _____________________ _______
18. ___________________________ _____________________ _______
19. ___________________________ _____________________ _______
20. ___________________________ _____________________ _______
Now you're ready to run CONFIG.EXE. Simply answer the questions with
the answers you've supplied on this worksheet.
OmegaComm VERSION 4.2 DELUXE
FINAL SETUP STEPS
Now that you've run the CONFIG.EXE program, you're ready to get the rest
of the directories and the menus set up. Follow these steps:
1. Create all the directories you've specified in the CONFIG work
sheet and program. If you are not sure of how to create
directories, refer to your DOS manual. (I'd also suggest you
spend some time learning DOS's tree directory structure and the
commands that are used with it if you aren't sure of them.)
2. Move the files included in the OmegaComm package to the proper
directories. The location of the files is outlined in the
FILES STRUCTURE portion of this documentation. Again, use the
directories that you have created, not the sample ones in this
documentation (unless those are the ones you set up!)
3. You'll need to modify some of the menus and other ANSI or ASCII
screens. The following screens are generic, and will work very
well as is. If you do customize these screens, at the very
least include all the information contained in them on any new
screens you build:
Page 16
CHKMAIL ANS/ASC { Message system commands }
FILEMENU ANS/ASC { File system commands }
FILEEXP ANS/ASC { Expert file system commands }
FLASH ASC { Flash message after sign on }
MAINMENU ANS/ASC { Main board commands }
MAINEXP ANS/ASC { Expert main board commands }
MESSEXP ANS/ASC { Expert message system commands }
OPENERS ASC { Opening message before sign on }
QUIZ ANS/ASC { Menus for the 99 quiz programs }
SYSOP1 ANS/ASC { Sysop's main board menu }
SYSOP2 ANS/ASC { Sysop's file section menu }
PROTOCOL ANS/ASC { List of file transfer protocols }
The screens that can (and should) be modified to make
your board more personal are:
BULLET(X) ANS/ASC { Your bulletin menus }
DOORS(X) ANS/ASC { Your doors programs menus }
GOODBYE ANS/ASC { Your sign off screen }
HOWDY(X) ANS/ASC { The 2nd - ? screens seen after log in }
INFO ANS/ASC { Displayed with welcome screens }
NOCHAT ANS/ASC { Sorry, Sysop is unavailable.... }
RULES ANS/ASC { Displayed with welcome screens }
WELCOME ANS/ASC { First screen seen at log in }
The screens are easy to edit -- you can use almost any word processing
package to change the ASCII screens. ANSI screens can be created and/or
edited with packages such as THEDRAW, ANSIDRAW, or ANSIANIM.
THE NAMES OF THE SCREEN FILES MUST REMAIN THE SAME!!!! All screens go on
the main drive, or whatever menu drive you have specified.
OmegaComm VERSION 4.2 DELUXE
FINAL SETUP STEPS
4. Check all of your DOORx.BAT files to make sure that they are
set up correctly. Check the commands carefully if you are
using DoorWay. Make sure that the paths to the door programs
are correct.
5. Copy any door programs to the subdirectories referenced in your
DOORx.BAT files. If the door program requires a configuration
file or data file, be sure these are copied over as well.
6. Copy any files you are going to make available for downloading
into your UPLOADS directory. These files must be placed here
first in order to install them on the board. If you have a lot
of files, you might consider copying only one file section's
files at a time to keep things straight.
Page 17
7. If you've moved everything into the correct directories, in-
stalled your modem, have the modem strings correct, and have
run the CONFIG.EXE program, you are now ready to sign onto the
board for the first time. Go to the directory containing
OMEGA.EXE (the main drive) and type OMEGA and press RETURN.
The software will start up, send some commands to your modem,
and you will see a screen that tells you that OmegaComm is
"Awaiting a Caller".
8. At this screen, press F5, then RETURN to go into LOCAL mode.
You will be asked for your first and last name. Type SYSOP and
press return. You will then be prompted to answer questions as
a new user. One of the most important things is to put in a
secure password. The user with the name of SYSOP has access to
every part of the board, and has features available to him that
should not be available to the general users. Make sure your
password is unique.
9. If you've made it this far, it means that you have probably
done everything right and the board is operational. If you get
an error message along the way and get kicked back to DOS, the
chances are great that a menu file didn't get put in the right
subdirectory, or that your OMEGA.CNF file contains a directory
name that is different than the directory you set up.
10. You're now signed on as SYSOP for the first time. When you get
to the main menu, type F4. A window will pop up in the upper
left part of the screen and ask what level you want to set for
this user. Type 9, then RETURN. You are now on the board with
access level 9 -- full sysop privileges. In order to store
this information and your access level of 9, you must leave the
board using the "Sign Off" command at either the main menu or
the file menu. If the board seems to go berserk when you sign
off, don't worry. Just reboot and it will be ok.
OmegaComm VERSION 4.2 DELUXE
SYSOP WORK AREAS
There are two Sysop working areas. These can be accessed at the main
menu prompt (#), file menu prompt (#), or at Call Waiting screen (F6).
Only access level 9 can get to these work areas.
Page 18
THE MAIN SYSOP WORK AREA
Pressing F6 at the "AWAITING CALL" screen or "#" at the main menu will
bring you to the main sysop work area. You will be given the following
menu:
ZDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDD?
3 Enter B To Read The Board Record 3
3 Enter C To Change User Data 3
3 Enter D To Drop To Dos 3
3 Enter F To Do File Maintenance 3
3 Enter K To Pack User File 3
3 Enter L To Get The User Log 3
3 Enter M Message System 3
3 Enter P To Pack Message System 3
3 Enter R To Restore Inactive Users 3
3 Enter T To Toggle Printer On/Off 3
3 Enter U To Users List With Data 3
@DDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDDY
Your Choices:
'B': Review the board actions of the users
You will have the option to delete.
'C': Change 15 of the user's data elements
'D': Drop To Dos Shell
'F': Do files system maintenance
'K': Pack the user file by level or last date on
'L': Read the user log (who, time on, time off)
You will have the option to delete.
'M': Enter the messages to read/write/delete/undelete/move
messages
'P': Pack the message system (get rid of those marked delete).
The messages will be renumbered and the userids.bbs file
will be updated accordingly.
'R': Restore inactive users if not overwritten
'T': Toggle the printer on or off
'U': List if names and levels of users
IF YOU ARE HAVING TROUBLE WITH DROP TO DOS THEN MORE THAN LIKELY YOU
HAVE ANOTHER PROGRAM (PROBABLY MEMORY RESIDENT) THAT IS TRYING TO USE
THE SAME MEMORY AREA.
Page 19
OmegaComm VERSION 4.2 DELUXE
SYSOP WORK AREAS
THE SYSOP FILES WORK AREA
If you have uploaded files or you have put some files in the file system
for the callers, here is where you want to go. To install a file or edit
an installed file type 'F' and follow the prompts.
[D] Drop To Dos
[E] Edit a File
[I] Install a File
[L] File Listing
[N] New File Listing
[S] Search For a file
[V] View archive/text file
Your choices are:
'D': Drop to DOS shell
'E': Edit the data on an installed file
.Rename Files
.Change File Sections
.Change file descriptions
.Delete files
'I': Install new files (must be in upload file section)
'L': List the contents of a file section
'N': New file since last logged on or by specified date
'S': Search for a file by
.Keyword
.String
.Name
'V': You can view the contents of a compressed file
.View archive file
.View Text file
OmegaComm VERSION 4.2 DELUXE
Sysop Commands
F1: Turns CHAT mode on and off. If CHAT is off or the Sysop
doesn't answer, then the system displays a message to the
caller that the Sysop is unavailable and allows them to leave
a comment. DEFAULT = OFF
F2: Toggles the Sysop message on/off. DEFAULT = ON
F3: Toggles the Sysop window on/off. DEFAULT = ON
Page 20
F4: This brings up a window at the top of the screen which shows
the caller's current access level and allows you to change
their level while on line.
F5: While you are in the "Awaiting Call" mode, you can press this
key, then press ENTER and you will sign on locally.
F6: While you are in the "Awaiting Call" mode, you can press this
key, then press ENTER, and you will enter the Sysop work area.
F7: If you get a "CREEP" on the board, you can press this key.
They will get a message telling them their presence is not
desired, and will be cut off the system.
F8: Forces CHAT mode with the user. Press ^Q twice to end forced
chat mode.
F9: Sysop Help window.
F10: Use this key to quickly exit the system.
CTRL-A: Answers a users page (enter chat mode).
CTRL-Q: Exit normal chat mode. Press CTRL-Q and
RETURN to exit forced chat mode.
ALT-T : Add more time to the user - current session only.
PGUP : Change a caller's stats/setup while they are online
PGDN : Drop to dos while a caller is online
WITH F4 AND ALT-T YOU MUST PRESS ENTER TO RECYCLE THE SCREEN.
OmegaComm VERSION 4.2 DELUXE
VARIOUS NOTES
*************************************************************
IMPORTANT WARNING
*************************************************************
MAKE SURE THAT YOUR SELECTED MAIN DRIVE IS LISTED IN THE PATH
IN YOUR AUTOEXEC.BAT FILE i.e., PATH C:\;C:\DOS;C:\OmegaComm.
IF YOU DON'T THEN DROP TO DOS, AND DOORS WILL NOT WORK.
*************************************************************
*************************************************************
Page 21
USER NAMES & PASSWORDS
----------------------
User names and passwords are always mapped to capitals by the BBS to
avoid errors. SYSOP's access level is set to level 9 automatically on
first sign-on. The SYSOP must sign in with password and sign off with "
S " command the first time to activate the USERIDS.BBS & BOARDREC.BBS
files and be able to do work. This allows master control access to the
first person to use this name. BEWARE !
TIME LIMITS AND DOWNLOADING
---------------------------
If the time limit is up the user will be notified and disconnected at
the next prompt. The user also will not be able to download a file if
not enough time is left.
OmegaComm VERSION 4.2 DELUXE
VARIOUS NOTES
MESSAGES
--------
All messages are visible to the SYSOP. The user has the options of
entering, reading, scanning, deleting, moving, and replying to messages.
In addition to these the SYSOP can also undelete and change messages
from private to public. All messages that are called deleted stay
around but are marked until the SYSOP packs the message system. When
you mark a message that has replies for deletion you will have the
option of deleting the replies or just giving them a new name. When you
undelete a message you have the option of undeleting the replies to that
message also. When you pack the messages and renumber the ones left the
replies also will reflect the new number. Messages will be numbered
from #1 to #65535. When a message is displayed the following header
information is displayed: to, from, subject, date stamp, deleted,
private, public, received, and if reply follows. Only level nine can
view messages marked for deletion and undelete them.
PRIVATE BBS AND REMOTE USERS
----------------------------
If the program is made to act as a private BBS in the configuration will
have the end result of hanging up on any REMOTE user who attempts to
sign on without supplying a registered user name within three attempts
(the default is an OPEN BBS). New users must be signed on locally
first, before their names will be permitted for remote access.
QUIZZES AND WORD FOR THE DAY FUNCTIONS
--------------------------------------------
Read QUIZZWORD.DOC for directions on how to effectively use these
functions.
OMEGACOMM FILE STRUCTURES
-------------------------------------------
Read FILES.DOC for complete information on the OmegaComm 4.2 file
structures
VARIOUS BATCH FILES USED BY OMEGACOMM 4.2
--------------------------------------------
BBS-BATS.DOC gives you all the detail you will need to effectively
utilize these files
PROTOCOLS FOR OMEGACOMM 4.2
--------------------------------------------
Please reference PROTOCOL.DOC. You may designate part or all of the
available protocols in the OMEGA.CNF file. The UPLOAD.BAT &
DOWNLOAD.BAT files contain the command line parameters (go on the main
drive).
*************************************************************
* *
* If you have any problems call the BBS during the hours *
* listed above and I will try to help you. If you find a *
* bug, let me know. Also, I would ask that if you do not *
* like this software, please write a letter and tell me *
* what is wrong with it. I need your help and suggestions *
* to make it better. Thanks! *
* *
* Good Luck and let us here from you if you have questions.*
* *
* Larry D. Loiselle *
* *
*************************************************************
- end -