home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Software of the Month Club 1995 December
/
SOFM_Dec1995.bin
/
pc
/
os2
/
adeptbbs
/
adpxbbs.doc
< prev
next >
Wrap
Text File
|
1995-10-31
|
254KB
|
4,970 lines
----------------------------------------------------------------------
AdeptXBBS
Bulletin Board for IBM 32-bit OS/2
Version v1.0x
Copyright (c) 1993 - 1995 by AdeptSoft
portions Copyright (c) 1991-1994 M. Kimes
All Rights Reserved
AdeptSoft, AdeptXBBS, GateKeeper,
are trademarks of AdeptSoft.
----------------------------------------------------------------------
For tech support, registration and the latest versions:
Support BBS: (407) 477-6310 (v.Everything)
: telnet://adeptsoft.com
FTP Site : ftp://adeptsoft.com
E-Mail : support@Adeptsoft.com
If you would like to develop software that supports AdeptXBBS
or develop OS/2 Doors log into the support BBS or E-Mail
Tower@AdeptSoft.Com
NOTEWORTHY INFO:
Wide Beta version 0.90 was released Jan. 17, 1995.
Version 0.94 on March 15, 1995.
Version 0.96 on May 7, 1995.
Version 0.97 on May 29, 1995.
Version 0.98 on August 5th, 1995.
Version 1.00 on August 7th, 1995.
Version 1.01 on August 8th, 1995.
Version 1.04 on September, 2nd, 1995.
Version 1.05 on October, 7th, 1995.
TABLE OF CONTENTS:
INTRODUCTION ........................................................5
What Is AdeptXBBS? .................................................5
Features: ..........................................................5
Limitations: .......................................................7
System Requirements: ...............................................7
Copyright Information: .............................................7
Disclaimer: ........................................................8
3rd Party Developers: ..............................................8
Acknowledgments: ...................................................8
CONTACTING AdeptSoft ...............................................10
REGISTERING ADEPTXBBS ..............................................12
Registration Form: ................................................13
INSTALLING ADEPTXBBS ...............................................14
First Time Install: ...............................................14
Upgrading From Previous Versions: .................................14
Command Line Options: .............................................15
CONVERTING From Other BBS Programs: ...............................15
BBS CONFIGURATION ..................................................16
Configuring ADEPT Via Pulldown Menus: .............................16
Directories Used By Adept: ........................................21
Text Files Used By Adept: .........................................23
The TRASHCAN File ...............................................26
The Phone Can File ..............................................27
The Quotes File .................................................27
Setting Up News Files ...........................................27
RIP Graphics: .....................................................28
AdeptXBBS MENU INTERFACE ...........................................29
Menu Types: .......................................................33
ADEPT MULTI-LANGUAGE SUPPORT .......................................62
Language.Text Configuration: ......................................63
ADEPT USER HELP TOPICS .............................................66
ADEPT META VARIABLES ...............................................69
EVENT FILE CONFIGURATION ...........................................75
uNuke - ADEPTXBBS USER BASE UTILITY ................................78
How to install uNuke: .............................................78
Command Line Parameters: ..........................................78
Environment Variables: ............................................79
Frequently Asked Questions Concerning uNuke: ......................79
INTERNET CAPABILITIES ..............................................81
NNTP Support ......................................................82
FILE AREA CONFIGURATION ............................................84
File Area Editor: .................................................84
File Transfer Protocol Editor: ....................................88
File Area Control File Configuration: .............................88
An Example File_Areas File: .......................................89
Adding Files To Your New Adept BBS: ...............................91
Converting a Files.BBS to the Adept Filebase Format: ..............92
Using CD-ROMS Including Multi-Changer CD-ROMS With Adept: .........95
FileEdit: .........................................................95
fList - An "all-files" List Creator For Adept: ....................95
ReIndexFile - Adept File System Reindexing Program: ...............96
ReadArc.Cmd - Archive Command Processor: ..........................97
MESSAGE AREA CONFIGURATION .........................................98
Message Area Editor: ..............................................98
Message Area Control File Configuration: .........................101
An Example Message_Areas File: ...................................102
Xmsg - AdeptXBBS Message Base Utility/Packer: ....................104
MAILER CONFIGURATION ..............................................105
Line Specific Mailer Settings: ...................................105
Address Settings: ................................................107
Nodelist Information: ............................................107
Gate Keeper Control Documentation (GateKpr.Ctl): .................108
Sample GateKpr.Ctl File ........................................113
Sample Area.Control File .......................................116
.TIC File Echo Configuration For GateKeeper ....................120
Format of File.Control: ........................................121
Outbound Mail Naming Conventions: ................................124
AreaFix Type Commands: ...........................................125
Mailer 'OK' File - File Request Format (FREQ): ...................126
Other Text Files Used With The Mailer: ...........................126
Configurable Mail Directories: ...................................127
Bad Mail Packets: ................................................128
XSENDPM - FIDO File Sending Utility: .............................128
FAX Connects: ....................................................129
SETTING UP DOORS UNDER Adept .....................................131
Sample Batch Files: ..............................................132
APPENDIX ..........................................................134
Example .MENU Files: .............................................134
AdeptXBBS USER Base Structure: ...................................136
AdeptXBBS Message Base Structures: ...............................140
Bitmaps For The fflags: ..........................................141
Bitmaps For The xflags: ..........................................141
Structure For The AdeptXBBS Message Base .Index File: ............142
Structure For The AdeptXBBS File System - File.Data File: ........142
INTRODUCTION
AdeptXBBS is an OS/2 bulletin board program written in 'C' and
compiled with the WATCOM C32 Optimizing Compiler Version 10.0.
AdeptXBBS fully exploits all the features that make OS/2 the operating
system of the future and today. AdeptXBBS is extremely well threaded
in order to give you that 'instant' response you expect from OS/2.
What Is AdeptXBBS?
AdeptXBBS is a 32-bit, Multi-thread, Multi-user, PM BBS for 32-bit
OS/2.
AdeptXBBS incorporates the best that is OS/2! AdeptXBBS is designed
to give you speed, reliability, power and flexibility in one
package. Almost everything about AdeptXBBS can be customized.
All the text displayed in the PM system, to every prompt and menu.
AdeptXBBS gives you robust support for DOS and OS/2 doors using the
DOOR.SYS and Session Info (ask us about Session Info) drop file.
Features:
The AdeptXBBS file system has support:
o Multi-CD rom changers
o FILE_ID.DIZ
o File Tagging
o Virus Checking
o Archive Conversion
o Archive Viewing/Extraction
o Files.BBS importing
o Password protected files and file areas
o Age limited files, and file areas
o Extensive file security and area security
o Xmodem, Ymodem, Ymodem-G, Sealink, Zmodem and ZedZap
protocols
o User configurable file lists
o Mark files as offline (single CD-ROM, multiple CD-ROM support
o Mark files as hidden by downloadable
The AdeptXBBS message base system has support for:
o Password Protection
o Extensive security features
o Context sensitive searches
o Message tagging
o .QWK, Bluewave, Fidonet Point and Text exporting
o Last Read Pointer Manipulation
o Unlimited Message Areas, Message Per Area and Message Size.
(The current file system (FAT, and HPFS) will break before the
BBS does)
o Full Screen and Text Message Editors
o Full Reply Linking/Threading
o On the fly compression of messages.
o Message encryption
The AdeptXBBS mailer has support for:
o 100% Fidonet compatible
o FTS-001 through FTS-009 Fidonet standards
o Around 20 additional FSC proposals
o File Attaches, File Requests
o WAZOO, EMSI and DietIFNA mail sessions
o Complete events handling, with external program support
o Fidonet v7 Nodelist support
o Auto Execution of a fax program for FAX connects
o AREAFIX with auto add and auto forward capabilities
o TIC processing with forwarding
o Completely and seamlessly integrated into the BBS software
The AdeptXBBS BBS has support for:
o DOS and OS/2 Doors, using the DOOR.SYS and Session Info drop files
o The ability to run redirected OS/2 programs
o Completely custom menu system
o Completely custom prompts system
o Multi-Lingual support
o TTY, ANSI, AVATAR, ANSI-TE2 graphics, auto ANSI and ANSI-TE2
detection
o Multi-node, multi-user chat
o Internet Telnet Support
o Named Pipe Support
o Internal REXX program processing and execution
Limitations:
DOS doors/games do not work over the Internet, most OS/2 doors/games
should work over Telnet. (The DOS limitation does not exist if you
are using SIO's VMODEM).
System Requirements:
AdeptXBBS requires OS/2 v2.0, v2.1, v2.11, v2.99 or OS/2 v3 in order
to run. OS/2 v3 or IBM TCP/IP required for Internet capabilities.
AdeptXBBS requires 2 Megabytes of FREE ram and at least 5 megs of
free disk space. A MODEM is optional.
IMPORTANT-- AdeptXBBS requires a HPFS partition!
Copyright Information:
AdeptXBBS and it's support programs are not to be modified or
distributed in modified form without the express written permission
of AdeptSoft.
AdeptSoft, AdeptXBBS, GateKeeper and are trademarks of
AdeptSoft.
"XBBS" Copyright (c) 1988 - 1994 by M. Kimes. The "XBBS" name is a
Trademark of M. Kimes
AdeptSoft holds an exclusive license to develop and distribute
shareware and commercial versions of the XBBS-OS/2 BBS program by M.
Kimes.
All support programs Copyright 1993-95 AdeptSoft, except where
otherwise noted.
All other trademarks and copyrights belong to their respective owners.
Disclaimer:
There is no warranty, period. Even if there was we are NOT
responsible for its actions. If the mailer dials Iraq and sits
on the line for 12 hours AT&T will be very happy with you. If
the BBS hiccups and all in a sudden you have 3 gigs of free disk
space when you originally had 5 megs free, consider yourself lucky
for having a large hard drive. i.e. We cannot take responsibility
for what this program does. We have tried in well over a year of
beta testing to remove as many of the bugs as possible and it has
not to our knowledge done either of the above things, but who knows.
3rd Party Developers:
AdeptXBBS offers a complete set of programming API's for 3rd party
developers. If you are looking to develop a door game for OS/2 BBS's
please contact us. Of if you are looking at writing a AdeptXBBS
specific module. We currently have complete API's for the UserBase,
FileBase, Chat Server, Video Functions, COM and I/O routines and
Memory Servers. If you are writing a door our Chat Server is freely
available for door authors to use with any system.
We include in this archive v0.95 of our File System .DLL's with
basic documentation, including examples of how to make use of
the AdeptXBBS File System. ALL the functions in the fSys DLL's
are also duplicated in the latest revision of the REXX engine.
You can contact us about doing 3rd party development for AdeptXBBS
by logging into our support BBS (407) 477-6310, telnet://adeptsoft.com
or by E-Mailing Tower@Adeptsoft.com
Acknowledgments:
All the people acknowledge below in some way or another contributed
to this program. I tried to remember everyone I could and I am sure
I missed a few. Of you feel your name should be here please contact
us and we will add it. Thanks to everyone who have helped me out over
the last year a half, helped beta test this program and contributed
ideas and suggestions. And thanks to those who remained the programs
biggest critics, yet at the same time it's greatest supporters.
Special thanks to Mark Kimes.
Stefan Andersson Scott Baldwin Kimberly Bobrow Vince Coen
Vicci Conway Mario Dulisse Brady Flowers Chris Griffin
Mike Hammers Rich Hawley Jason Klank Koen Koster
Joe Lemere Scott Livingston Paul Lockley Andrew Lozier
Pam Lunsford Eddy Matthews Barry Mcmenomy Julie Niesen
Eric Miller Fred Miller Steve Mohacey David Moskowitz
Pete Norloff Jim Mullins Jason Perlow Dan Polivy
David Prentice Ronen Raz Graham Reid Kevin Royalty
Bill Schaeffer Jason Schuster Horace Skinner Joey Snell
Brian Snyder Brent Pranger Mark Wheeler Scott Wilkos 10
CONTACTING AdeptSoft
AdeptSoft is located in Boca Raton, Florida. Our current mailing
address is:
AdeptSoft
8903 Glades Road - Suite L9-199
Boca Raton, FL 33496
AdeptSoft can be reached via the following methods:
E-Mail: AdeptSoft@adeptsoft.com
Fidonet: 1:18/210.0@Fidonet
AdeptSoft@adeptsoft.com
You may also contact us at our support BBS at the number:
(407) 477-6310, 28.8k or you may Telnet to AdeptSoft.Com
You may also be placed on the AdeptSoft mailing list by sending mail
to info@adeptsoft.com with the statement 'Add Me' as the subject and
you will be added to our auto mailing list. To be removed from the
mailing list send a message to info@adeptsoft.com with the subject
'Remove Me'. Both adding and removing will generate a auto response
acknowledging that you have been added or removed.
AdeptSoft has a public Fidonet Echo called 'ADEPTSOFT'. For a list of
sites carrying this echo send e-mail to ECHO@adeptsoft.com and you
will receive a list of sites carrying the echo. You may also send
e-mail to ECHO or FREQ the FileName ECHO from 1:18/210.0@Fidonet for
a list of sites carrying the echo area.
You can also FTP to AdeptSoft.Com to get specific files and
information.
If you have a account on our BBS please use your account name when
logging into the FTP server, if you do not have an account on our BBS
log in with the name anonymous.
Bugs, Comments, Suggestions and Ideas can be e-mailed to the
following e-mail addressed at AdeptSoft:
Support@AdeptSoft.Com
If you are reporting a bug, please, try to be as specific as possible.
I.E. - "The mailer is broken" doesn't give us any idea as to what is
broken in the mailer. Also please to not get discouraged if
you are having problems. Many times it's something simple
that can be fixed with a quick phone call. So please leave
a phone number you may be reached at.
Feature requests:
At the moment we have locked down the current feature set. If a
suggestion comes along that we feel really should be in v1.0 we
will do our best to add it. If the feature you want is not in
v1.0 please don't think we have forgotten about you.
Your feature requests will be added.
REGISTERING ADEPTXBBS
2 Node AdeptXBBS with REXX ($99)
2 Node AdeptXBBS with REXX and Internet ($159)
4 Node AdeptXBBS with REXX ($219)
4 Node AdeptXBBS with REXX and Internet ($279)
8 Node AdeptXBBS with REXX and Internet ($449)
16 Node AdeptXBBS with REXX and Internet ($699)
32 Node AdeptXBBS with REXX and Internet ($1199)
Please call if you wish to discuss orders larger then 32
nodes.
__________________________________________________________
___HOW TO REGISTER___
1) Send a check made payable ADEPTSOFT to :
AdeptSoft
8903 Glades Road - Suite L9-199
Boca Raton, FL 33496
2) ...You may also send FAX in your credit card registration to:
(407) 483-2480.
3) Use on Online Credit Card Registration through our support
BBS via the Internet (telnet) at Adeptsoft.com
or via land line at (407) 477-6310 USR v.Everything 28.8k.
Registration Form:
--------8<-------CUT HERE--------8<--------
registrant's name:
address:
city/state/zip
voice phone:
fax phone:
Internet e-mail address:
Fidonet address:
card holder's name:
Card type: MasterCard, Visa, Discover
(we do NOT accept AMEX or Sears at this time)
Card Number (xxxx-xxxx-xxxx-xxxx):
Expiration date:
What are you ordering:
How much does it cost:
If Bonus included in price, do you want: Internet or REXX?
You can receive your key by logging on to our support
BBS or via E-Mail to RegKeys@AdeptSoft.Com
any comments you would like to make:
--------8<-------CUT HERE--------8<--------
INSTALLING ADEPTXBBS
First Time Install:
Create a directory called ADEPT at the root of your hard drive.
Remember that this HAS to be an HPFS formatted drive.
Copy the Adept .ZIP file into a TEMP directory that you
created. Unzip this file with PkUnzip or OS/2's INFO-ZIP.
If you don't have INFO-ZIP, it can be downloaded or FTP'd
from many locations including the support FTP site at adeptsoft.com.
Run the install Program, Install.cmd from your root \TEMP sub-
directory. Chose the INSTALL FULL A COPY OF ADEPTXBBS from the menu.
After the install program runs you can click on the AdeptXBBS icon in
the new AdeptSoft folder that has been created on your desktop. All
setup options will be available from the Config and Edit Pull Down
menus.
Upgrading From Previous Versions:
It is always best to backup your existing BBS software BEFORE you
install a new version.
To upgrade to a new version of Adept, copy the archive file to a temp
directory and unzip it. Run the INSTALL.CMD file and chose the
Upgrade a Previous Version of AdeptXBBS. Be sure to pay particular
attention when the program asks you if you want to install the default
menus. If you answer YES, it will overwrite any customizing that you
may have done to files in the \Adept\Text and \Adept\Menus
directories. You will also want to back up your language.text file if
you have done any modifications of it.
Command Line Options:
All command line options should be proceeded by a '/' or '-', you can
mix and match the two.
/NODES ### - This specifies the number of nodes to bring on-line.
/NOINIT ## - This specifies a node number not to initialize on
startup. This can be repeated as many times as you
want in the command line. This option is great for if
you want to bring all the nodes on-line, but are using
one of the com ports, so you can specifically tell the
BBS/Mailer NOT to try to access that port until you
want it to.
/VERSION - Will display the current version information.
/HELP or /? - Will display a help dialog with commands and our
contact information.
/SETUP - Will bring the software up in Setup mode. It will
not try to access any comm ports.
CONVERTING From Other BBS Programs:
There are conversion programs included with this BBS software.
\Adept\Convert\Mxtoadp.zip - Maximus User Conversion Utility
\Adept\Convert\Ratoadp.zip - Remote Access User Conversion Utility
BBS CONFIGURATION
Configuring ADEPT Via Pulldown Menus:
Accessed from Config->Active Line->General Settings...
+--------------------------------------------------------------------+
: Line # General Settings :
+--------------------------------------------------------------------+
: :
: +-- Basic Modem Strings ------------------+ +------------------+ :
: : : : Logon Security : :
: : Answer : ATA| : +------------------+ :
: : Init : v~^ATM0| : :
: : Dial Pref : v~^ATDT : x Use Telnet Timers :
: : Dial Suf. : | : x No Carrier Detection:
: : : x Use Socket Port :
: +-----------------------------------------+ x Use Telnet Port :
: x ATO on DATA :
: +-----------------------------------------+ :
: : Port Name : COM1 Ring Response : RING : :
: : Answer on Ring : 1 : :
: +-----------------------------------------+ :
: :
: +-- BPS Rates ------------------------------+ :
: : : :
: : Initial BPS : 19200 Mn. BPS : 1200 : :
: : Mn. Mail BPS : 1200 Mn. Call BPS : 2400 : :
: : : :
: : x Locked : :
: +-------------------------------------------+ :
: :
: +----+ +------+ +----+ :
: : OK : :Cancel: :Help: :
: +----+ +------+ +----+ :
+--------------------------------------------------------------------+
'v' - Drops DTR '^' - Raises DTR
'~' - 1 Second Delay '`' - 1/10th of a Second
'|' - Carriage Return '\\' - Escape Character
Com Port:
This can be a Com port or a named pipe. AdeptXBBS will work
with any valid communications serial port and or named
pipe.
Answer on Ring:
This is the number of rings to answer the modem on.
You can choose any number. If there is a 10-15 second
delay between rings AdeptXBBS will reset the counter.
Ring Response:
This is the 'RING' statement to look for from the modem.
For example if you have distinctive ring you can have the
BBS look for 'RING1' instead of 'RING'
Use Telnet Timers:
This option tells the Mailer/BBS to use a completely
different set of timing sequences for Telnet and
VMODEM sessions.
No Carrier Detection:
This option is used if you are configuring this node to be
an internet node for your BBS. If people will be telneting
into it instead of dialing into it, use this option.
Use Socket Port:
This option should be used if you are using this node as an
internet node for people to telnet into.
Use Telnet Port:
This option should be used if you are using this node as an
internet node for people to telnet into.
ATO on Data:
This option is recommended if you are using AdeptXBBS to
send/receive faxes with a modem other than a CLASS 2 fax
modem.
Logon Security:
This will bring up a dialog of security settings a user must
meet in order to be allowed on this node.
Answer:
This is the string to send to the modem to make it answer
the phone when a call comes in.
Init:
This is the string transmitted to the modem to initialize
it. AdeptXBBS will not work properly if the modem is set to
Auto Answer.
Dial Pref:
Dialing prefix, this is the string to send to the modem to
dial a number.
Dial Suf:
Dialing suffix, this is the string to send to the modem to
finish a dialing sequence.
Initial BPS:
This is the initial baud rate to initialize the modem at.
Locked: Check this box to lock the port at the initial BPS.
Mn BPS: Minimum BPS to allow users to connect at.
Mn Mail BPS: Minimum BPS to allow mail sessions.
Mn Call BPS: Minimum BPS to initiate a mail session.
Mx Call BPS: Maximum BPS to initiate a mail session.
Accessed from Config->Active Line->Dial Strings...
+--------------------------------------------------------------------+
: Line # Dial Strings :
+--------------------------------------------------------------------+
: Dial Pre1: Dial Pre5: :
: Dial Suf1: Dial Suf5: :
: :
: Dial Pre2: Dial Pre6: :
: Dial Suf2: Dial Suf6: :
: :
: Dial Pre3: Dial Pre7: :
: Dial Suf3: Dial Suf7: :
: :
: Dial Pre4: Dial Pre8: :
: Dial Suf4: Dial Suf8: :
: :
: +------+ +--------+ +------+ :
: : OK : : Cancel : : Help : :
: +------+ +--------+ +------+ :
+--------------------------------------------------------------------+
Accessed from Config->Active Line->CPU Priorities...
+--------------------------------------------------------------------+
: CPU Priorities :
+--------------------------------------------------------------------+
: +-- BBS Priorities ----------------------------------------------+ :
: : : :
: : Main: <----X-----------> 2 Local: <----X-----------> 2: :
: : <X---------------> 1 <X---------------> 1: :
: : : :
: +----------------------------------------------------------------+ :
: : +-- Line # CPU Priorities -------------------------------------+ :
: : : :
: : Mailer: <----X-----------> 2 Send: <------------X---> 3: :
: : <X---------------> 0 <X---------------> 0: :
: : : :
: : BBS: <----X-----------> 2 Export: <----X-----------> 2: :
: : <X---------------> 0 <X---------------> 0: :
: : : :
: : Outside: <----X-----------> 2 Recv: <------------X---> 3: :
: : <X---------------> 0 <X---------------> 0: :
: : : :
: +----------------------------------------------------------------+ :
: :
: +------+ +--------+ +------+ :
: : OK : : Cancel : : Help : :
: +------+ +--------+ +------+ :
+--------------------------------------------------------------------+
Accessed from pressing right mouse button on user window.
+--+-----------------------------------------------------------------+
: : BBS: Local :
+--+-----------------------------------------------------------------+
: User Name User Town Time Remaining Loc :
: :
: :
: :
: +--------------------------+ :
: : Edit User : :
: : Chat : :
: : ---------------------- : :
: : Time -> : :
: : ---------------------- : :
: : Hang Up : :
: : Lockout : :
: : Moron : :
: : ---------------------- : :
: : Change Font : :
: : ---------------------- : :
: : Paste to KB Buffer : :
: : Paste to Output : :
: : ---------------------- : :
: : Redraw Screen : :
: Mouse Pointer -> x+--------------------------+ :
: :
: Click with right mouse button on local screen. :
: :
: :
: :
+--------------------------------------------------------------------+
Directories Used By Adept:
The following directory entries are defaults and some can be changed:
---------------------------------------------------------------------
.\ (default) -- Where configuration files are kept.
.\Logfiles -- Where logfiles are kept.
.\Events -- Where Adept keeps its event files.
.\Files -- Where Adept keeps its B-Tree style file
system.
.\Help -- Where Adept keeps its help files.
.\Convert -- Where Other BBS -to- Adept converters are
kept.
.\Samples -- Sample menus and rexx files.
.\Mailer -- Where Adept keeps all its mailer related
files.
.\Mailer\Aborted_Files -- Where aborted mail files are kept.
.\Mailer\NodeList -- Where the node list is kept.
.\Mailer\Outbound_Mail -- Where outbound mail is kept.
.\Mailer\Packets -- Where packets are kept (unused at this
point).
.\Mailer\Password_Inbound_Mail (see Mailer section).
.\Mailer\Public_Inbound_Mail (see Mailer section).
.\Mailer\Unlisted_Inbound_Mail (see Mailer section).
.\Mailer\Scripts -- Not Yet Used -
.\Menus -- Where menus and REXX scripts are kept.
(Main.Menu, Main?.Menu menus, Main.Cmd
Main?.Cmd, AtEnd.Cmd, AtEnd?.Cmd REXX
scripts).
.\Message_Bases -- Where all message bases are kept.
.\Personal_Mail -- This is where AdeptXBBS stores it's PMI
message Indexes.
.\System -- Where system related files are kept.
(Message_Areas, File_Areas, Library_Areas,
Addresses, Archivers, Computers,
Language.Text, Groups).
.\System\Line? -- Where data files are kept for each node
(? equals the node number in decimal).
.\System\MiscNews -- Where miscellaneous news is kept.
.\System\SysNews -- Where system news is kept.
.\Temp_Directories -- Where temporary files are kept (for
example, when viewing archive files)
.\Text -- Where text files are kept
(*.ASC, *.ANS, *.RIP, *.AVT).
Text Files Used By Adept:
AdeptXBBS text files. Filenames and where they are shown.
----------------------------------------------------------------------
Text files have a name and extension. The regular filename extension
is .ASC which means this is a regular ASCII text file. If the user
has ANSI color turned on, Adept will look for a file with the same
name, but with the extension .ANS. If the user has Avatar support
turned on, a text file with the extension .AVT is search for. If the
user has RIP graphics support enabled, a text file with the extension
.RIP is searched for.
If the files with the alternate extensions (.ANS .AVT .RIP) are not
found, then the default .ASC file is used.
If any of these files are not found, the file is not shown and the
error is ignored. You as the Sysop must create these text files if you
wish them to be displayed. These files may use meta variables.
File Names:
DupePhone.ASC -- Shown when the phone number entered is
found to be a duplicate of another users
phone number.
Upload.ASC -- Shown before a user starts an upload.
Download.ASC -- Shown before a user starts a download.
LockedOut.ASC -- Shown when a user is locked out of the
system.
Login.ASC -- Shown when the user first logs on, before they
enter their name.
Preregister.ASC -- Shown to a new user when the system only
accepts pre-registered users.
NoRoom.ASC -- Shown to a new user when there is no room
for new users.
CantFind.ASC -- Shown when the users name is not found.
GetPassword.ASC -- Shown before the user types in their
password.
BadPassword.ASC -- Shown every time after a user types in the
wrong password.
BadPass.Asc -- Shown before the user is logged out after
they have failed to enter the proper
password after 'Max Attempts' attempts.
Shown before 'BadPass.Menu' menu is
auto-executed.
HappyBirthday.ASC -- Shown when it is the users birthday.
Welcome.ASC -- Shown after the user has entered their
password and before the news files are
shown.
News.ASC -- Shown after Welcome.ASC
Bullet.ASC -- Shown after News.ASC
MsgAreas.ASC -- If this file exists, then it is shown in
place of the default message area listing.
MsgAreas###.ASC -- If this file exists, it will be shown before
the MsgAreas.ASC would have been shown. ###
is the security level to show to.
FileAreas.ASC -- If this file exists, then it is shown in
place of the default file area listing.
FileAreas###.ASC -- If this file exists, it will be shown
before the FileAreas.ASC would have been
shown. ### is the security level to show
to.
NewUser.ASC -- Shown to new users before they enter their
user info. (text line #194 is shown
immediately after this file)
ReAsk.ASC -- Shown before ReAsk.Menu is executed. The
ReAsk text file and menu are executed if
the user exists and the users 'ReAsk' flag is
false. The 'ReAsk' system is used to fill in
missing fields in the user record.
BeforeNew.ASC -- Shown after 'NewUser.ASC' (and text line
#194) (text line #21 is shown immediately
after this file)
NewBirthday.ASC -- Shown before the user enters their birth
date.
BadAge.ASC -- Shown when the users age is too young or too
old.
FixUser.ASC -- Shown before the edit new user menu
(EditYou.MNU) is executed.
LogonMsg.ASC -- Shown before the user enters their first
logon message (only if the 'first logon
message' bit is set)
xxx.Rules -- Shown before reading messages in a certain
message area. Typically used to post echo
mail area rules. Where 'xxx' is the message
area name.
xxx.Desc -- Shown before reading messages in a certain
message area. Typically used to describe the
contents of the message area. Where 'xxx'
is the message area name.
Trashcan.ASC -- Shown when the users name has been found in
the 'Trash can' file. See below for format.
PhoneCan.ASC -- Shown when the users phone number has been
found in the phone 'trash can' file. See
below for format.
PageSysop.ASC -- Shown just before the Sysop is paged for a
chat request.
TooManyPages.ASC -- Shown when a user has paged the Sysop too
many times. This checks the Max Page Attempts
field found in the config pulldown menus.
NoMoreTime.ASC -- Displayed before carrier is dropped on a
user that has run out of time.
Quotes -- Shown upon login, logoff or before a new
menu is displayed. See below for format.
GoodBye.Asc -- Shown when using a menu item 1000 style
logoff.
DumbUser.Asc -- Shown when user can't figure out how to
type their name correctly after 'Max
Attempts' attempts.
Shown before 'DumbUser.Menu' menu is
auto-executed if it exists.
NoNewUsers.Asc -- Shown when the new users security level is
below that necessary to log into a node
(login security)
NoAccess.Asc -- Shown when a regular users security level is
below that necessary to log into a node
(login security)
Levelxx.Asc -- Where 'xx' is the users security level
#1 Shown after correct password has been
type in.
xxxx.Asc -- Where 'xxxx' is the name of the user group
the user belongs to. Shown after Levelxx.Asc
(if it exists) ie. After successful password
input.
YouMoron.Asc -- Shown when SysOp logs user out with the
moron menu item. This could be used in
several ways, for instance, the SysOp could
put a message in 'YouMoron.Asc' that says
'SysOp needs system now. Loggin you off'
FunctionKeyxx.Asc -- Where 'xx' is a function key number
corresponding to the press of a function key
by the SysOp. This is not tested and may not
be working, but the code is in there.
The TRASHCAN File
"\Adept\System\Trashcan" uses the following format:
; - Comment
: - Compares Last Name
! - Look in name
- Exact Compare
!Look_anywhere_in_name
:Compare_with_last_name
;Comment
This is a exact compare
example:
;This is the Trashcan File
:Butthead
!Hacker
John Doe
In the example above, the first line is a comment, the 2nd line
tells AdeptXBBS to compare the user's last name to 'Butthead', if
it matches, this user won't be allowed to login. The 3rd line tells
AdeptXBBS to look anywhere in the name for a match of 'Hacker'. So,
if the user logged with the name Joe Hacker, Hacker Bob, or
Joe Hackerson, he wouldn't be granted access. The last line will
look for an exact match. So, if the person logs in with the name
John Doe, they won't be granted access. If they log in with the
name Johnny Doe, they will get access.
The Phone Can File
"\Adept\System\Phonecan" uses the following format:
!look_in_number
Exact Compare
;Comment
example:
;This is the Phonecan File
!911
!1-800
!1-900
555-1212
1-800-111-2222
In the example above, the first line is a comment, the 2nd line
tells AdeptXBBS to look in the number for a match of '911', any
phone number that has this pattern in it will match. So, if the
user inputs 342-9110, it will match. The 3rd line will look for
a match of '1-800' anywhere in the number that the user has typed
in. Same for the 4th line. The 5th and 6th lines will look for an
exact match of those numbers.
The Quotes File
"\Adept\System\Quotes" uses the following format:
%%
Quote of the day - We have nothing to fear but fear itself...
%%
Quote of the day - A penny saved is a penny earned...
%%
Quote of the day - Make new friends but keep the old.
Some are silver and the others are gold
%%
Setting Up News Files
Naming convention is: anynameyouwant.news.ans (.asc,.rip,.avt)
The files are then placed in the \Adept\System\Sysnews or the
\Adept\System\MiscNews directory. These files that you create
will only be shown once to the user. Editing of the files will
cause them to be shown again. AdeptXBBS will check the dates
on these files to see if they have been updated since the last
time that they were displayed to the user. If they were updated,
they will be shown again.
From the pulldown CONFIG->BBS->BBS Action Flags menu, add the
USE ANSI NEWS option.
From the pulldown CONFIG->BBS->New User Defaults menu, add the
SEE SYSTEM RELATED NEWS option.
If you have a news file that you want shown to the user every
time they login, make a NEWS.ANS (or .ASC) file and place it
in the \Adept\Text directory.
RIP Graphics:
We have been told that .RIP graphics does work in adept and has been
tested. In v0.94.10 I added a new multi-threaded display that
will display the rip screen remotely while displaying the ANSI version
of the screen locally. This should be a nice change from seeing all
those wonderful .RIP codes fly across your local screen. If a .RIP
screen does not exsist, the .ANS or .ASC equivilant of that file will
be shown instead. For a user to see the .RIP screens, the Sysop must
toggle the RIP option in the user's record. This is found in the USER
EDITOR for each user.
AdeptXBBS MENU INTERFACE
Menu files are plain ASCII files which describe the functions
available at the current menu.
Menu files are named 'xxxx.Menu' (where 'xxxx' is the menu name)
Fields on each line are separated by commas, so commas are not allowed
in the text.
Menu files are stored in the \Adept\Menus directory. The following are
descriptions of default menus:
Main.Menu or Main?.Menu -- This is executed after the user has logged
in successfully. Main?.Menu is tried
before Main.Menu So a SysOp could set up
a main menu based on a node number basis.
If Main?.Menu doesn't exist, Main.Menu is
executed. The '?' should be substituted
with the node number.
DumbUser.Menu -- This is executed when a user forgets their
name. And answers N 'Max Attempts' times.
(SysOp configurable).
BadPass.Menu -- This is executed when a user forgets their
password and gets it wrong more then the
specified number of maximum tries.
AtLogin.Menu -- This is executed every time a user logs on
just before the new message, new files
options are executed if they are turned
on.
EditYou.Menu -- This one is kinda scary. Runs after the
new user routine. It must be exited
with a menu item 1001 otherwise strange
things _will_ happen.
ReAsk.Menu -- This menu is an auto-execute menu which
is executed if the 'ReAsk' bit in the
users record is not set. It is executed
after the entering of the password.
This menu would be used to fill in, say,
blank fields in the users record.
NewUser.Menu -- Executed when a new user logs in.
The first line of the menu file describes the prompt, the file to be
displayed, color and flags of the menu. The format of the first line
is:
<Prompt text>,<Color>,<Menu filename>,<Flags>
If you don't want a color or text menu displayed, then leave the
field blank. For example:
Main Prompt: ,,,
This leaves all fields blank except the prompt text.
All lines that follow are used to describe menu options available
at the current menu. The lines have the following format:
<Key>,<Command#>,<Output String>,<Data String>,<Color>,
<MinAge>,<MaxAge>,<Sec1>,<Sec2>,<Flags1>,<Flags2>,<StartTime>,
<EndTime>,<Gender>,<MinCredit>,<MaxCredit>,<MinTime>,<MaxTime>,
<MinCall>,<MaxCall>,<MinPosts>,<MaxPosts>,<MinUpl>,<MaxUpl>,
<MinDl>,<MaxDl>,<Group>,<PortFlags>
Everything after DataString is optional
Time format is 'HR:MN', 13:30 - 1:30pm
PortFlags - Add the numbers together to come up with the accessible
port types.
1 - Accessible by Comm Ports (Modem, TA's, any Serial Devices)
2 - Accessible by Named Pipes
4 - Accessible by Telnet Ports
This field is optional, if this is not set, the BBS software
assumes there is no limitation as to what type of port can
use a specific command.
<Key> is what the user should type to invoke this command.
<Command#> is the menu command number to execute (those numbers
will be described below).
<Output String> is the text that is shown to the user for this
command if the <Menu filename> field of the first line is blank.
<Data String> is data used by certain command functions. It can be
used to change the behavior of some commands. See the command
function list to see which commands use the data string field.
<Color> what color to display the 'output string' in.
The fields
<MinAge>,<MaxAge>,<Sec1>,<Sec2>,<Flags1>,<Flags2>,<StartTime>,
<EndTime>,<Gender>,<MinCredit>,<MaxCredit>,<MinTime>,<MaxTime>,
<MinCall>,<MaxCall>,<MinPosts>,<MaxPosts>,<MinUpl>,<MaxUpl>,<MinDl>,
<MaxDl>,<Group>,<PortFlags> are optional.
They are compared against the same fields in the user record, if the
user doesn't have the access then that command is disabled.
o A menu file may have comments in it if the first character on
the line is a semi-colon ';'.
o Maximum commands in a single menu is 80. A menu that big
would probably be pretty user unfriendly anyway!
o If there is not a menu file in the first line of the menu
description, then the 'output strings' of every command are
displayed in the order that they appear.
o There are three menu flags: (use the number or combination of
numbers) Quote every time or 1
This means that an attempt to display a quote will happen every
time the menu is displayed depending on the 'quote odds' in the
BBS settings.
The quote odds are based on a 100 percent scale. 50 would mean
you would get a quote only half the time.
Quote once only or 2
This means that an attempt to display a quote will happen the
first time the menu is displayed depending on the 'quote odds' in
the BBS settings. But after a quote is shown once, there will not
be another quote for that menu.
First on [ENTER] or 4
This means that if the user hits enter, the first menu item is
the default choice.
Both menu and Menu file or 8
This means that if you have a menu display file, both it and the
menu 'output strings' will be replaced. The display file will be
shown before the 'output strings'
o Meta variables can be place in the data field for each menu item.
This allows for great flexibility in creating menu commands.
o Menus are stored in the .\Menus directory.
o Menus should have a file extension of '.Menu'. If the user has
the RIP graphics flag set, Adept will look for '.Renu' if the
user has ANSI color turned on, Adept will look for '.Cenu' and if
the user has ANSI cursor movement turned on (not color) then Adept
will look for '.Genu' Those files are looked for in that order.
If none of the other optional files are found, '.Menu' will be
used by default.
o There should be (in almost every case) a Main.Menu (or Main?.Menu
for a particular node number.) This is the menu which is started
after the user logs into the system. Adept will look for a
Main?.Menu first and if one is not found for that line, then
Main.Menu is used.
If you have a Main?.Cmd or Main.Cmd REXX script in the .\Menus
directory it will be used instead of Main.Menu See AdptREXX.Doc
for more info.
o Adept uses a 'New User' menu called, appropriately enough,
NewUser.Menu This is an auto-execute menu that is called right
after the NewUser.ASC and BeforeNew.ASC files are shown to the
user. All the commands in this menu will be executed in the order
that they are found. If you don't want a question to be asked,
feel free to delete that line. Be creative! If you have an
'EditYou.Menu' file it will be executed after NewUser.Menu
o 'EditYou.Menu' can be created if you want to give the new user a
chance to edit their info before it is saved.
o Adept supports a special menu which helps a SysOp get complete
information from a user after they have converted to Adept from
another BBS. ReAsk.Menu is an auto-execute menu which is run if
ReAsk.Menu exists and the 'ReAsked' flag in the user record is
set to false.
Each command in this menu is executed one after another. When the
menu is complete the 'ReAsked' flag is set to true. Also, the
file 'ReAsk.ASC' is shown before the menu is executed.
Menu Types:
----------------------------------------------------------------------
Menu Type: 0
----------------------------------------------------------------------
Option Data: Menu Name
Description:
Go to another menu. Name of menu is in the data field.
----------------------------------------------------------------------
Menu Type: 1
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Gosub to another menu. Name of menu is in the data field.
you can only go 9 gosubs deep. If you wish to have more nested
menus (more than 9) then use the (0) goto menu command.
----------------------------------------------------------------------
Menu Type: 2
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Return from a gosub'ed menu. Returns to the previous menu.
----------------------------------------------------------------------
Menu Type: 3
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Clear all gosub'ed menus.
----------------------------------------------------------------------
Menu Type: 4
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Go to another menu and ask for a password. The data field should
read MenuName;Password
----------------------------------------------------------------------
Menu Type: 5
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Gosub to another menu and ask for a password. The data field
should read MenuName;Password
---------------------------------------------------------------------
Menu Type: 6
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Gosub a forced-return menu (This type of menu returns after any
command is selected)
----------------------------------------------------------------------
Menu Type: 7
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Gosub an auto-execute menu (This type of menu executes all the
commands in the menu file, then returns)
----------------------------------------------------------------------
Menu Type: 10
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Execute a REXX script file in cached mode. Name of file is in the
data field. The current line number is passed as the first
argument to the REXX script.
The line number must be the first argument pass back to any Adept
REXX functions.
----------------------------------------------------------------------
Menu Type: 11
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Execute a REXX script file in NON cached mode. Name of file is in
the data field. The current line number is passed as the first
argument to the REXX script.
The line number must be the first argument pass back to any Adept
REXX functions.
----------------------------------------------------------------------
Menu Type: 15
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Read messages forward with no prompting for message number.
----------------------------------------------------------------------
Menu Type: 16
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
QuickScan message (to, from, subject)
----------------------------------------------------------------------
Menu Type: 17
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Scan message headers
----------------------------------------------------------------------
Menu Type: 20
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Read messages forward, with prompting
----------------------------------------------------------------------
Menu Type: 25
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Globally read msgs from current newest message
----------------------------------------------------------------------
Menu Type: 26
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Globally read messages, stop at each area
----------------------------------------------------------------------
Menu Type: 28
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Searches current message area for keywords in the
to, from, subject and message body
----------------------------------------------------------------------
Menu Type: 31
----------------------------------------------------------------------
Optional Data:
Description:
Export mail - Text format
----------------------------------------------------------------------
Menu Type: 32
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Export mail - Fido packet format
----------------------------------------------------------------------
Menu Type: 33
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Export mail - QWK format
----------------------------------------------------------------------
Menu Type: 34
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Export mail - Bluewave format
----------------------------------------------------------------------
Menu Type: 35
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Export mail - format based on user preference
----------------------------------------------------------------------
Menu Type: 36
----------------------------------------------------------------------
Optional Data:
Description:
Import mail - allows user to upload a mail packet
----------------------------------------------------------------------
Menu Type: 41
----------------------------------------------------------------------
Optional Data:
Description:
Display user status
----------------------------------------------------------------------
Menu Type: 42
----------------------------------------------------------------------
Optional Data:
Description:
Who is on-line
----------------------------------------------------------------------
Menu Type: 43
----------------------------------------------------------------------
Optional Data:
Description:
List users
----------------------------------------------------------------------
Menu Type: 45
----------------------------------------------------------------------
Optional Data:
Description:
Edit your user record
----------------------------------------------------------------------
Menu Type: 46
----------------------------------------------------------------------
Optional Data:
Description:
Adjust accessible file areas
----------------------------------------------------------------------
Menu Type: 47
----------------------------------------------------------------------
Optional Data:
Description:
Adjust accessible message areas
----------------------------------------------------------------------
Menu Type: 48
----------------------------------------------------------------------
Optional Data:
Description:
Page SysOp
----------------------------------------------------------------------
Menu Type: 49
----------------------------------------------------------------------
Optional Data:
Description:
Display help (If 'text' in data field, help on 'text' will be
shown)
----------------------------------------------------------------------
Menu Type: 50
----------------------------------------------------------------------
Optional Data:
Description:
Adjust tags on off-line mail export
----------------------------------------------------------------------
Menu Type: 51
----------------------------------------------------------------------
Optional Data: FileName.### (Asc will then have it display the default
for the user)
Description:
Display a text file
----------------------------------------------------------------------
Menu Type: 60
----------------------------------------------------------------------
Optional Data:
Description:
Select message area
----------------------------------------------------------------------
Menu Type: 61
----------------------------------------------------------------------
Optional Data:
Description:
Select file area
----------------------------------------------------------------------
Menu Type: 62
----------------------------------------------------------------------
Optional Data: Name of Message Area
Description:
Find message area (name of area in data field)
----------------------------------------------------------------------
Menu Type: 63
----------------------------------------------------------------------
Optional Data: Name of File Area
Description:
Find file area (name of area in data field)
----------------------------------------------------------------------
Menu Type: 64
----------------------------------------------------------------------
Optional Data: 1/-1
Description:
Next/Previous message area (1 in data field means next area, -1 in
data field means previous area)
----------------------------------------------------------------------
Menu Type: 65
----------------------------------------------------------------------
Optional Data: 1/-1
Description:
Next/Previous file area (1 in data field means next area, -1 in
data field means previous area)
----------------------------------------------------------------------
Menu Type: 70
----------------------------------------------------------------------
Optional Data:
Description:
List files in current area
----------------------------------------------------------------------
Menu Type: 71
----------------------------------------------------------------------
Optional Data:
Description:
Search files in current area. Asks for search string
----------------------------------------------------------------------
Menu Type: 72
----------------------------------------------------------------------
Optional Data:
Description:
Search files in current area newer than specified date. Asks for
search string and date.
----------------------------------------------------------------------
Menu Type: 73
----------------------------------------------------------------------
Optional Data:
Description:
New files in current area. asks for date.
----------------------------------------------------------------------
Menu Type: 74
----------------------------------------------------------------------
Optional Data:
Description:
New files in all areas, searched sequentially.
----------------------------------------------------------------------
Menu Type: 75
----------------------------------------------------------------------
Optional Data:
Description:
List ALL files in alphabetical order.
----------------------------------------------------------------------
Menu Type: 76
----------------------------------------------------------------------
Optional Data: Search String
Description:
Search files in all areas. Asks for search string.
----------------------------------------------------------------------
Menu Type: 77
----------------------------------------------------------------------
Optional Data:
Description:
List files in current area, in dated order newest to oldest.
----------------------------------------------------------------------
Menu Type: 78
----------------------------------------------------------------------
Optional Data:
Description:
List files in current area, in alphabetical order. A->Z
----------------------------------------------------------------------
Menu Type: 84
----------------------------------------------------------------------
Optional Data:
Description:
View archive
----------------------------------------------------------------------
Menu Type: 85
----------------------------------------------------------------------
Optional Data:
Description:
Download file(s) - asks for file name(s)
----------------------------------------------------------------------
Menu Type: 86
----------------------------------------------------------------------
Optional Data:
Description:
Download file contained in data field
----------------------------------------------------------------------
Menu Type: 90
----------------------------------------------------------------------
Optional Data:
Description:
Upload file(s) - Asks for file names, unless the 'upload blind'
bit is turned on for the file area and blind uploading is possible
with the users current protocol. (blind uploading means the
transfer comes first, with the file names and descriptions
determined after-wards)
----------------------------------------------------------------------
Menu Type: 91
----------------------------------------------------------------------
Optional Data:
Description:
Upload specific file. (file in data field)
----------------------------------------------------------------------
Menu Type: 100
----------------------------------------------------------------------
Optional Data:
Description:
OR user attributes 1 with number in data field
----------------------------------------------------------------------
Menu Type: 101
----------------------------------------------------------------------
Optional Data:
Description:
AND user attributes 1 with number in data field
----------------------------------------------------------------------
Menu Type: 102
----------------------------------------------------------------------
Optional Data:
Description:
OR user attributes 2 with number in data field
----------------------------------------------------------------------
Menu Type: 103
----------------------------------------------------------------------
Optional Data:
Description:
AND user attributes 2 with number in data field
----------------------------------------------------------------------
Menu Type: 104
----------------------------------------------------------------------
Optional Data:
Description:
OR user flags 1 with number in data field
----------------------------------------------------------------------
Menu Type: 105
----------------------------------------------------------------------
Optional Data:
Description:
AND user flags 1 with number in data field
----------------------------------------------------------------------
Menu Type: 106
----------------------------------------------------------------------
Optional Data:
Description:
OR user flags 2 with number in data field
----------------------------------------------------------------------
Menu Type: 107
----------------------------------------------------------------------
Optional Data:
Description:
AND user flags 2 with number in data field
----------------------------------------------------------------------
Menu Type: 110
----------------------------------------------------------------------
Optional Data: Character of Protocol
Description:
Set user file transfer protocol to letter contained in data
field
----------------------------------------------------------------------
Menu Type: 111
----------------------------------------------------------------------
Optional Data: Number/Letter of Computer Type
Description:
Set user computer type to number in data field (number is
index into 'Computers' file)
----------------------------------------------------------------------
Menu Type: 130
----------------------------------------------------------------------
Optional Data:
Description:
Change address (address line 1, lines 2 and 3 if those bits
are set in BBS flags.
----------------------------------------------------------------------
Menu Type: 131
----------------------------------------------------------------------
Optional Data:
Description:
Change ANSI color flag
----------------------------------------------------------------------
Menu Type: 132
----------------------------------------------------------------------
Optional Data:
Description:
Change high ASCII (chars 128-255) flag
----------------------------------------------------------------------
Menu Type: 133
----------------------------------------------------------------------
Optional Data:
Description:
Change cold input flag (not hot key)
----------------------------------------------------------------------
Menu Type: 134
----------------------------------------------------------------------
Optional Data:
Description:
Change screen length
----------------------------------------------------------------------
Menu Type: 135
----------------------------------------------------------------------
Optional Data:
Description:
Change pause flag
----------------------------------------------------------------------
Menu Type: 136
----------------------------------------------------------------------
Optional Data: NONE
Description:
Change handle
----------------------------------------------------------------------
Menu Type: 137
----------------------------------------------------------------------
Optional Data:
Description:
Change password
----------------------------------------------------------------------
Menu Type: 138
----------------------------------------------------------------------
Optional Data:
Description:
Change screen width
----------------------------------------------------------------------
Menu Type: 139
----------------------------------------------------------------------
Optional Data:
Description:
Change phone number(s) (home phone. data, business and fax
phones if these bits are set in the BBS flags)
----------------------------------------------------------------------
Menu Type: 140
----------------------------------------------------------------------
Optional Data:
Description:
Change interests
----------------------------------------------------------------------
Menu Type: 141
----------------------------------------------------------------------
Optional Data:
Description:
Change information to be shown to other users
----------------------------------------------------------------------
Menu Type: 142
----------------------------------------------------------------------
Optional Data:
Description:
Change expert mode
----------------------------------------------------------------------
Menu Type: 144
----------------------------------------------------------------------
Optional Data:
Description:
Change ANSI cursor movement flag
----------------------------------------------------------------------
Menu Type: 145
----------------------------------------------------------------------
Optional Data:
Description:
Changes protocol, new msgs flag, new files flag, limit file
list flag, see news flag, ask download flag, user available
flag and last but certainly not least EBCDIC conversion
flag.
----------------------------------------------------------------------
Menu Type: 146
----------------------------------------------------------------------
Optional Data:
Description:
Change file transfer protocol
----------------------------------------------------------------------
Menu Type: 147
----------------------------------------------------------------------
Optional Data:
Description:
Change new message at logon flag
----------------------------------------------------------------------
Menu Type: 148
----------------------------------------------------------------------
Optional Data:
Description:
Change new files search at logon
----------------------------------------------------------------------
Menu Type: 149
----------------------------------------------------------------------
Optional Data:
Description:
Change limit file list flag
----------------------------------------------------------------------
Menu Type: 150
----------------------------------------------------------------------
Optional Data:
Description:
Change see misc. news
----------------------------------------------------------------------
Menu Type: 151
----------------------------------------------------------------------
Optional Data:
Description:
Change ask download
----------------------------------------------------------------------
Menu Type: 152
----------------------------------------------------------------------
Optional Data:
Description:
Change user available for chat flag
----------------------------------------------------------------------
Menu Type: 154
----------------------------------------------------------------------
Optional Data:
Description:
Change full screen editor flag
----------------------------------------------------------------------
Menu Type: 155
----------------------------------------------------------------------
Optional Data:
Description:
Change mail export type
----------------------------------------------------------------------
Menu Type: 156
----------------------------------------------------------------------
Optional Data:
Description:
Set birthday (should be used from NewUser.Menu ONLY)
If the user is too young or too old , this will _end_ the
current BBS session!!
----------------------------------------------------------------------
Menu Type: 157
----------------------------------------------------------------------
Optional Data:
Description:
Change clear screen
----------------------------------------------------------------------
Menu Type: 158
----------------------------------------------------------------------
Optional Data:
Description:
Change computer type
----------------------------------------------------------------------
Menu Type: 159
----------------------------------------------------------------------
Optional Data:
Description:
Change gender (should be used from NewUser.Menu ONLY)
Use sparingly.
----------------------------------------------------------------------
Menu Type: 161
----------------------------------------------------------------------
Optional Data:
Description:
Change to Avatar
----------------------------------------------------------------------
Menu Type: 162
----------------------------------------------------------------------
Optional Data:
Description:
Change ANSI-TE2
----------------------------------------------------------------------
Menu Type: 163
----------------------------------------------------------------------
Optional Data:
Description:
Change 8 dot 3 names (will convert long names down to 8.3)
----------------------------------------------------------------------
Menu Type: 164
----------------------------------------------------------------------
Optional Data:
Description:
Change Avatar/Ansi Flags
----------------------------------------------------------------------
Menu Type: 165
----------------------------------------------------------------------
Optional Data:
Description:
Change View off-line mail status
----------------------------------------------------------------------
Menu Type: 166
----------------------------------------------------------------------
Optional Data:
Description:
Change default archiver
----------------------------------------------------------------------
Menu Type: 167
----------------------------------------------------------------------
Optional Data:
Description:
Deposit Bank Time
----------------------------------------------------------------------
Menu Type: 168
----------------------------------------------------------------------
Optional Data:
Description:
Withdraw Bank Time
----------------------------------------------------------------------
Menu Type: 190
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Toggle a bit in user attributes 1 (bit can be 1 thru 32)
bit number is in data field
----------------------------------------------------------------------
Menu Type: 191
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Toggle a bit in user attributes 2 (bit can be 1 thru 32)
bit number is in data field
----------------------------------------------------------------------
Menu Type: 192
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Toggle a bit in user flags 1 (bit can be 1 thru 32)
bit number is in data field
----------------------------------------------------------------------
Menu Type: 193
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
Toggle a bit in user flags 2 (bit can be 1 thru 32)
bit number is in data field
----------------------------------------------------------------------
Menu Type: 200
----------------------------------------------------------------------
Optional Data: 'To Name';'Subject';'AreaNum';'1' or '0';Node Number
Description:
Write message, no optional data needed. If no optional data is used
the message is treated as a normal message entry option. Public or
Private messages may be posted via this method, uses the options
set for the area you are posting in.
The force to data requires a name and will take a optional subject
if a ; is placed between the name and subject.
To Name : Name of person to force message to
Subject : Subject to force message to be pasted as
AreaNum : Message area number to post message in
1 or 0 : Return to message area user was in when they posted the
message or stay in the new messages area. 1 - Return 0
- Stay
Node Number: Node number to force message to if it is NetMail, this
must be a full 5-D Address. i.e. 1:18/210.0@Fidonet
Example: F,200,This is a Command,Sysop;Comment from {U0;2;1,0
Example: E,200,This is a Command,;;2;1;1:368/210.0@Fidonet,0
In this example it would go to Area 2, Post a Message to Sysop, with
the Subject of 'Comment from 'User Real Name' and after the message
was saved or aborted it would return to the message area the user
was in when this command was executed.
All data on this command is optional. If you do not specify a name
to force the message to it will then try the name in the force to
field in the message configuration, if that doesn't exist it will
default to Sysop.
----------------------------------------------------------------------
Menu Type: 201
----------------------------------------------------------------------
Optional Data: 'Force To Name';'Subject';'AreaNum';'1' or '0';Node
Number
Description:
Write message to user name specified in area 'forced to' data and
marks the message as private.
The force to data requires a name and will take a optional subject
if a ; is placed between the name and subject.
To Name : Name of person to force message to
Subject : Subject to force message to be pasted as
AreaNum : Message area number to post message in
1 or 0 : Return to message area user was in when they posted the
message or stay in the new messages area. 1 - Return 0
- Stay
Node Number: Node number to force message to if it is NetMail, this
must be a full 5-D Address. i.e. 1:18/210.0@Fidonet
Example: F,201,This is a Command,Sysop;Comment from {U0;2;1,0
Example: E,201,This is a Command,;;2;1;1:368/210.0@Fidonet,0
In this example it would go to Area 2, Post a Message to Sysop, with
the Subject of 'Comment from 'User Real Name' and after the message
was saved or aborted it would return to the message area the user
was in when this command was executed.
All data on this command is optional. If you do not specify a name
to force the message to it will then try the name in the force to
field in the message configuration, if that doesn't exist it will
default to Sysop.
----------------------------------------------------------------------
Menu Type: 300
----------------------------------------------------------------------
Optional Data: 'Prompt/Question'
Description:
Get string input from user and temporarily store it. Prompt is in
data field.
----------------------------------------------------------------------
Menu Type: 303
----------------------------------------------------------------------
Optional Data: Menu Name
Description:
temporarily stores text in data field as last user input.
----------------------------------------------------------------------
Menu Type: 400
----------------------------------------------------------------------
Optional Data: 'Chat Area'
Description:
Internode chat, with Area defined in data field
----------------------------------------------------------------------
Menu Type: 601
----------------------------------------------------------------------
Optional Data:
Description:
Toggles ANSI color flag
----------------------------------------------------------------------
Menu Type: 602
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles high ASCII flag
----------------------------------------------------------------------
Menu Type: 603
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles MORE prompt flag
----------------------------------------------------------------------
Menu Type: 604
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles clear screen flag
----------------------------------------------------------------------
Menu Type: 605
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles cold input flag
----------------------------------------------------------------------
Menu Type: 606
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles show address flag
----------------------------------------------------------------------
Menu Type: 607
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles show phone flag
----------------------------------------------------------------------
Menu Type: 608
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles show real name flag
----------------------------------------------------------------------
Menu Type: 609
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles no kill flag
----------------------------------------------------------------------
Menu Type: 610
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle deleted flag
----------------------------------------------------------------------
Menu Type: 611
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle expert flag
----------------------------------------------------------------------
Menu Type: 612
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle twit flag
----------------------------------------------------------------------
Menu Type: 613
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle new files flag
----------------------------------------------------------------------
Menu Type: 614
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle new messages flag
----------------------------------------------------------------------
Menu Type: 615
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle download new messages flag
----------------------------------------------------------------------
Menu Type: 616
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle download new file list flag
----------------------------------------------------------------------
Menu Type: 617
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle see misc. news flag
----------------------------------------------------------------------
Menu Type: 618
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles ask download flag
----------------------------------------------------------------------
Menu Type: 619
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles novice flag
----------------------------------------------------------------------
Menu Type: 620
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles point mail only flag
----------------------------------------------------------------------
Menu Type: 622
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggleslocked out flag
----------------------------------------------------------------------
Menu Type: 623
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles chat availability
----------------------------------------------------------------------
Menu Type: 624
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles protected from user list display
----------------------------------------------------------------------
Menu Type: 625
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles misc. news display
----------------------------------------------------------------------
Menu Type: 626
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles limit file list to current area
----------------------------------------------------------------------
Menu Type: 628
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles verified flag
----------------------------------------------------------------------
Menu Type: 629
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggles ANSI TE2 graphics
----------------------------------------------------------------------
Menu Type: 631
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle AVATAR graphics
----------------------------------------------------------------------
Menu Type: 632
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle off-line mail monitoring
----------------------------------------------------------------------
Menu Type: 640
----------------------------------------------------------------------
Optional Data: NONE
Description:
Pack up and download off-line mail
----------------------------------------------------------------------
Menu Type: 655
----------------------------------------------------------------------
Optional Data: NONE
Description:
Change archiver
----------------------------------------------------------------------
Menu Type: 656
----------------------------------------------------------------------
Optional Data: NONE
Description:
Edit file transfer list (tagged files)
----------------------------------------------------------------------
Menu Type: 700
----------------------------------------------------------------------
Optional Data: NONE
Description:
Tag all areas for off-line mail
----------------------------------------------------------------------
Menu Type: 701
----------------------------------------------------------------------
Optional Data: NONE
Description:
Untag all areas for off-line mail
----------------------------------------------------------------------
Menu Type: 702
----------------------------------------------------------------------
Optional Data: NONE
Description:
Toggle a specific area for off-line mail
----------------------------------------------------------------------
Menu Type: 703
----------------------------------------------------------------------
Optional Data: NONE
Description:
Change type of mail export (Text, QWK, Fido, etc)
----------------------------------------------------------------------
Menu Type: 704
----------------------------------------------------------------------
Optional Data: NONE
Description:
Message area Last message Read Editing
----------------------------------------------------------------------
Menu Type: 800
----------------------------------------------------------------------
Optional Data: Program Name (CMD.EXE)
Description:
Run OS/2 type door. Pgm must use stdin/stdout for
I/O.. and allow itself to be killed. Data field
contains door to run.
----------------------------------------------------------------------
Menu Type: 801
----------------------------------------------------------------------
Optional Data: Program Name/Batch File (CMD.EXE /c Batch.Cmd)
Description:
Spawn a separate session. data field contains door to run.
Can be used for any door program that accesses the com port
in a more traditional (and complicated) fashion. (includes
DOS doors)
This is the one to use for 99% of all DOORS!
----------------------------------------------------------------------
Menu Type: 802
----------------------------------------------------------------------
Optional Data: Program Name/Batch File (CMD.EXE /c Batch.Cmd)
Description:
Run OS/2 type door. (same as 800 but assumes a program which
is more friendly to having its I/O redirected thru pipes
to the com port.)
----------------------------------------------------------------------
Menu Type: 803
----------------------------------------------------------------------
Optional Data: Program Name/Batch File (CMD.EXE /c Batch.Cmd)
Description:
The type 803 door works exactly like a type 802 except that it
sets and allows your to set several 32-bit semephores giving
you and the BBS more interaction.
They are as follows.
\SEM32\ChildDone\Line#
\SEM32\Carrier\Line#
\SEM32\TimeTick\Line#
We will activate the \SEM32\Carrier\Line# when a user drops
carrier. This then gives you 10 minutes to complete your
task and return to the BBS software. If you issue
a \SEM32\ChildDone\Line# and exit we will handle everything
normally.
Next the TimeTick warns you of when the user has 3, 2 and 1
minute remaining. We will issue it three times.
These should help make your programs more aware of Adept and
Adept more aware of them.
----------------------------------------------------------------------
Menu Type: 810
----------------------------------------------------------------------
Optional Data: Program Name/Batch File (CMD.EXE /c Batch.Cmd)
Description:
Spawn a separate session. Inherits Adepts environment.
(same as 801.. ahem..)
----------------------------------------------------------------------
Menu Type: 811
----------------------------------------------------------------------
Optional Data: Program Name/Batch File (CMD.EXE /c Batch.Cmd)
Description:
Spawn a separate session. Inherits OS/2's default environment.
----------------------------------------------------------------------
Menu Type: 815
----------------------------------------------------------------------
Optional Data: Program Name/Batch File (CMD.EXE /c Batch.Cmd)
Description:
See 801 and 810. Session is in foreground (default is
background)
----------------------------------------------------------------------
Menu Type: 900
----------------------------------------------------------------------
Optional Data:
Description:
Personal Mail Check
----------------------------------------------------------------------
Menu Type: 950
----------------------------------------------------------------------
Optional Data:
Description:
Shuts down the BBS! This is EXTREMELY powerful! It will cause
the BBS to shut itself down after the last user logs off.
----------------------------------------------------------------------
Menu Type: 999
----------------------------------------------------------------------
Optional Data: 'Area Number'
Description:
Logoff with option to leave a message to the sysop. The area
number that you want the message to be placed in should be entered
in the data field.
After the user has entered the message, it will display
'Goodbye.Asc' and then prompt #202.
----------------------------------------------------------------------
Menu Type: 1000
----------------------------------------------------------------------
Optional Data: NONE
Description:
Log use off, displays Goodbye.Asc and Prompt #202 (language.text)
before hanging up.
----------------------------------------------------------------------
Menu Type: 1001
----------------------------------------------------------------------
Optional Data: NONE
Description:
Instant log off.
ADEPT MULTI-LANGUAGE SUPPORT
The AdeptXBBS software includes Multi-Lingual support. The following is
a example 'Languages' file. The Language file is the configuration
file for the multi-lingual support. The languages file has three
fields delimited by a comma. The first parameter is the name of the
language, the second is the Identifier for the language and the third
is the root dir in which that language resides.
You can have up to 36 languages. If the need arises we can expand
this number, but in order to assure that the mailer is still
operational on all levels we decided to limit it to the keys 1-0 and
A - Z.
-- BEGIN: 'Languages' file ---
English ,ENG,D:\Adept\
French ,FRN,D:\Adept\French\
Spanish ,SPN,D:\Adept\Spanish\
Finish ,FIN,D:\Adept\Finish\
-- END: 'Languages' file ---
If the user chooses French the BBS will look in the following
directories for the language support files.
\Adept\French\System
\Adept\French\Menus
\Adept\French\Text
You should place all the files that you would normally put in the
\Adept\System, \Adept\Menus and \Adept\Text sub-dir in the language
directories corresponding to the language they refer to.
If a user chooses a language and the BBS cannot find the Language.text
file in the \Adept\Languagename\System sub-dir it will default to the
language.text in the \Adept\System dir.
Language.text - Contains some clues on how to edit the Language.Text
file.
Language.Text Configuration:
Language.Text is the prompts file, but with the low ASCII chars
eliminated as control chars. (the need to edit them is eliminated) In
place of the single ASCII chars are 5 character strings which take
their place.
The strings are in the format: [xxx] the 'xxx's denote a type of
command for that line of text. There are currently 23 possible
command types:
[Str] - Means to return the string to the calling subroutine.
(normally string is sent to user)
When a line has [Str] in it, DO NOT remove it. If the line
does not have [Str] in it, DO NOT add it.
[Log] - Means log this line to the log screen.
[Loc] - Means show this line locally only.
[Ans] - Means show this line to users with ANSI cursor movement on.
[Asc] - Means this line is for ASCII users only. (ANSI is not on)
[Run] - Means try to execute the rexx program specified on this
line.
[Fil] - Means show this file.
NOT IMPLEMENTED
[Cmd] - Means send this line to CMD.EXE.
NOT IMPLEMENTED
[Clr] - Means show this line to users that have color on.
[Pse] - Means pause at this line.
[8bt] - Means this line contains high ASCII characters.
[Cls] - Means clear the screen.
[Exp] - Means show this line to experts only.
[Twt] - Means show this line to Twits only.
[Nov] - Means show this line to novice users only.
[Hlp] - Means show help file.
NOT IMPLEMENTED
[Mnu] - Means execute this menu.
NOT IMPLEMENTED
[Mta] - Means that META commands should be converted
(i.e. {M1, {UG, {W1, etc.)
[Cvt] - Means that literals should be converted
(i.e. \x1B, \r, \n, etc.)
[Rem] - Means send this line to the remote end only.
[Slg] - Write to screen log. (this may be backwards with [Log])
[Sts] - Means write this to Adept screen in status window.
[Wav] - Means play a .WAV sound file. The filename follows the [Wav]
command. Wildcards OK. MMPM/2 should be installed.
------------------
Execution Commands
------------------
[Str], [Log], [Loc], [Run], [Fil], [Cmd], [Hlp], [Mnu], [Rem], [Slg],
[Sts],[Wav]
Should be the last command before the text on the line, because they
cause that command to be executed immediately.
----------------
Special Commands
----------------
[Pse], [Cls]
Any text following these commands is ignored.
----------------
Convert Commands
----------------
[Mta], [Cvt]
Will change the text on the line.
[Mta] will cause all 'smart text' commands such as {M0, {U3, {L1 to
be converted to the proper text. (see the Meta Variables section)
[Cvt] will cause string 'literals' to be converted. A string literal
is the same as a 'C' string literal such as \x1B (ESCape), \r
(return), \n (new line) If a line doesn't have 'smart text' or string
'literals' then you don't need to use these commands, because they can
slow the display of the text down.
-------------
Flag Commands
-------------
[Ans], [Asc], [Clr], [8bt], [Exp], [Twt], [Nov]
determine who should see the line. ANSI is considered different than
ANSI color because some terminals support ANSI cursor movement, but
not color.
If you have an ANSI line it would probably be okay to turn on
highlighting "[1m" because highlighting is usually supported even on
dumb terminals.
You can put the flag commands in front of the Execution, Special or
Convert commands.
You can use a combination of these flags to determine which lines are
sent to the user. Any order is okay and a user has to match all
flags on a line to be shown that line. If the line were:
[Ans][Clr][8bt]Hello there!
Then the user would have to have ANSI, Color and high ASCII chars
turned on to see that line!
---------------------
In 'Language.Text' you use the format: #xx to start a line of text.
Language.Text is the file you edit. When Adept runs and sees a new
Language.Text file, it will compile Language.Text into the file
Language.Text.Compiled then Adept will create an index file called
Language.Text.Index
ADEPT USER HELP TOPICS
Adept User Help Topics: (and when they are used)
(not all topics are currently found in Adept.Help)
Setup File -- Setting access to files areas.
List FileAreas -- List command when setting up file area
access.
All FileAreas -- All areas command when setting up file
areas.
FileSetup Prompted -- when asking for access to each file area
one at a time.
FileSetup Lorange -- When setting Low file area of a range.
FileSetup Hirange -- When setting High file area of a range.
FileSetup RangePick -- When setting range.
FileArea Inquire -- When inquiring which areas.
Setup Msg -- When setting access to message areas.
List MsgAreas -- List command when setting up message
areas.
All MsgAreas -- All areas command when setting up message
areas.
MsgSetup Prompted -- When asking for access to each message
area one at a time.
MsgSetup Lorange -- When setting Low message area of a range.
MsgSetup Hirange -- When setting High message area of a
range.
MsgSetup RangePick -- When setting range.
MsgArea Inquire -- When inquiring which areas.
Calendar -- When asking for which calendar to
display.
ChatHelp -- When in Internode chat
Chat Reason -- When requesting a SysOp chat
Edit You -- When selecting options in 'EditYou'
function.
User Interests -- When getting one line of user interests.
User Address -- When setting one of three user address
strings.
User city -- When setting city
User state -- When setting state/province.
User Zipcode -- When setting ZIP/postal code.
User Phone -- When setting one of four phone numbers.
User Password -- When setting password.
User Handle -- When setting handle.
User Showaddress -- When setting show address flag.
User Showphone -- When setting show phone # flag.
User Showreal -- When setting show real name flag.
User ANSI -- When setting ANSI (movement) flag.
User Color -- When setting ANSI color flag.
User HighASCII -- When setting High ASCII flag.
User Gender -- When setting gender.
User Novice -- When setting novice flag.
User Expert -- When setting expert flag.
User FSE -- When setting full screen editor flag.
Download Mail -- When asking whether a user wants to
download mail packet.
User Rolling -- When setting rolling prompts flag.
User Mailtype -- When setting mail packet type.
User Pause -- When setting more prompt flag.
User Hot -- When setting hot keys flag.
User Clear -- When setting clear screen flag.
User Width -- When setting screen width.
User Length -- When setting screen length.
User Computer -- When setting computer type.
User Protocol -- When setting file transfer protocol.
User Archiver -- When setting default archiver.
User Newmsgs -- When setting read new msgs flag.
User Newfiles -- When setting view new files flag.
User TypeFList -- When setting type of file list.
User Shownews -- When setting show news flag.
User AsktoDL -- When setting ask download flag.
User Available -- When setting Internode chat flag.
User EBCDIC -- When setting EBCDIC conversion flag.
Download1 -- When asking for files to download.
Upload1 -- When asking for which file to be
uploaded.
Tag1 -- When asking for files to be tagged.
I1_Msgnum -- When asking which message number to read.
Lib Mask -- When asking for a library area file mask.
Lib Read -- When reading library file.
Lib Search -- When searching for library file.
Text delete -- When deleting lines in text editor.
Are You Sure -- When at a 'are you sure' prompt.
Text edit -- When editing a line in the text editor.
Text insert -- When inserting a line in the text editor.
Msg To -- When setting who message is to.
Msg From -- When changing message from.
Msg Subj -- When changing message subject.
Autodownload --
NewFileDate -- When asking for a new files date.
User Search -- When searching user list.
User Name -- When user enters name at login.
Are You You? -- When name not in user records.
Password -- When asking for password at login.
Scan All Mail? -- When asking if we should scan all mail.
MsgArea Selection -- When changing message areas.
FileArea Selection -- When changing file areas.
LibArea Selection -- When changing library areas.
Area Password -- When asking for an area password.
Text Title -- When getting name when creating a text
file.
Abort Text -- When aborting creation of text file.
Menu Password -- When asking for menu password.
File Matchstring -- When asking for a file search string.
I1_Logoff Msg -- When asking for logoff comment.
User Birthmonth -- When asking for user birthday month.
User Birthday -- When asking for user birthday day.
User Birthyear -- When asking for birthday year.
Quote Reply -- When asking if we are quoting in reply.
Msg Locate--from -- When locating message with from field.
Msg Locate--to -- When locating message with to field.
Msg Locate--subj -- When locating message by subject.
Msg Locate--body -- When locating message by contents.
Msg Locate--all -- When locating message by all of the
above.
Scan Page -- Scan messages more prompt.
Search String -- When getting a search string (for showing
text files)
File Read -- When show any text files in a directory.
View Arc -- When viewing archive
View Arc Member -- When viewing archive member.
Msg Destaddr -- When asking for address to send message
to (NetMail)
Addr Correct -- Is address correct?
Msg Private -- Is message private?
Msg Anonymous -- Is message anonymous?
ADEPT META VARIABLES
Adept supports the use of META variables in all text files. Meta
variables are used to display a value, known by the system, to the
user.
Meta variables are in the format {xx where 'xx' is the META
variable. (at a future date, the '{' (brace) may be a configurable
value)
(at a future date all kludges & crap will be nuked)
Current supported META variables:
System
S0 -- Number of calls to the BBS
S1 -- Minimum age of user allowed on BBS
S2 -- Maximum age of user allowed on BBS
S3 -- Maximum users on BBS
S4 -- Maximum mail connection attempts
S5 -- Maximum times a user can page the SysOp
S6 -- Name of BBS
S7 -- SysOp name
S8 -- Current BPS rate
User
U0 -- Name
U1 -- Handle
U2 -- Address
U3 -- Home phone
U4 -- Interests (one line of text)
U5 -- Computer type # (line # of computer in 'Computers'
file)
U6 -- Computer type string
U7 -- ID number
U8 -- Point ID number
U9 -- Birthdate yy/mm/dd
UA -- Credit
UB -- Minute limit
UC -- Time used so far today (on previous calls)
UD -- Time allowed per day
UE -- Number of times called
UF -- Uploaded # of files
UG -- Downloaded # of files
UH -- Uploaded # KBytes
UI -- Downloaded # KBytes
UJ -- Uploaded # KBytes today
UK -- Downloaded # KBytes today
UL -- Max upload KBytes per day
UM -- Max download KBytes per day
UN -- Security Level 1
UO -- Security Level 2
UP -- Flags 1 (bit flags as integer)
UQ -- Flags 2 (bit flags as integer)
UR -- Attributes 1 (bit flags as integer)
US -- Attributes 2 (bit flags as integer)
UT -- Screen length
UU -- Screen width
UV -- Last msg area #
UW -- Last file area #
UX -- Protocol (letter)
UY -- Archiver (letter)
UZ -- Time per call (outdated??)
V3 -- Age
V4 -- Graphics (1=on 0=off)
V5 -- Group in
V6 -- Number of messages posted
V7 -- Uploaded # of files (9 chars long) (all right
justified)
V8 -- Downloaded # of files (9 chars long)
V9 -- Uploaded # KBytes (9 chars long)
VA -- Downloaded # KBytes (9 chars long)
VB -- Uploaded # KBytes today (9 chars long)
VC -- Downloaded # KBytes today (9 chars long)
VD -- Max upload KBytes per day (9 chars long)
VE -- Max download KBytes per day (9 chars long)
VF -- Name (36 chars, left justified)
VG -- Handle (36 chars, left justified)
VH -- MaxBankTime
VI -- Time in Bank
VJ -- Calls Today
VK -- Total Minutes used since first call
O7 -- Banked time (in minutes)
O9 -- City
P1 -- Address (2 of 3)
P2 -- State
P3 -- Zip/Postal code
P4 -- Data phone
P5 -- Fax phone
PF -- Offline mail packing method (QWK, Fido, Bluewave etc.)
PI -- Scan for new mail at logon (ON/OFF)
PJ -- Scan for New Files at logon (ON/OFF)
Q9 -- File transfer protocol name or 'None'
QA -- Archiver name or 'none'
QB -- Max mail packet size in bytes
(the below display the text ON or OFF according to the flag in
the user record)
O1 -- ANSI
O2 -- Color
O3 -- High ASCII
O4 -- No More prompts
O5 -- No Clear screens
O6 -- Cold input (i.e. not hot keys)
P6 -- Avatar
P7 -- ANSI/TE2
PM -- Displays a YES/NO/MORE prompt
PN -- Turns off non-stop display
PO -- Turns on non-stop display
P9 -- Available for Internode chat
PE -- Monitoring Mail (ON/OFF)
Message Area (some variables are based on text found in
Language.Text)
M0 -- Name of area
M1 -- # msgs in current area
M2 -- Last msg read in current area
M3 -- # of msg area
M4 -- Last msg read + 1
M5 -- Description
M6 -- Name of area (12 characters long, left justified)
M7 -- # msgs in area (5 chars long, right justified)
M8 -- last msg read (5 chars long, right justified)
M9 -- # of msg area (5 chars long, left justified)
MA -- Last msg read + 1 (5 chars long, left justified)
MB -- Description (48 chars long, left justified)
MC -- Current msg number
MD -- Msg from (based on text #361)
ME -- Msg date
MF -- Msg to (based on text #363)
MG -- Msg private flag (based on text #352)
MH -- Msg read flag (text #353 if read, #354 if not read)
MI -- Msg deleted flag (text #355)
MJ -- Msg NetMail (text #356)
MK -- Msg EchoMail (text #357) 72
ML -- Msg keep (text #358)
MM -- Msg w/ file (text #370)
MN -- Msg request flag (text #371)
MO -- Msg update request flag (text #372)
MP -- Msg Kill/sent flag (text #373)
MQ -- Msg crashmail flag (text #374)
MR -- Msg sent flag (text #375)
MS -- Msg host flag (text #376)
MT -- Msg hold flag (text #377)
MU -- Msg anonymous (text #378)
MV -- Msg originating zone (text #379)
MW -- Msg originating net (text #380)
MX -- Msg originating node (text #381)
MY -- Msg originating point (text #382)
A2 -- Msg destination zone (text #383)
A3 -- Msg destination net (text #384)
A4 -- Msg destination node (text #385)
A5 -- Msg destination point (text #386)
A6 -- Msg subject header (text #387 if request, text #388 or
#389 if not)
A7 -- Msg subject (text #390)
A8 -- Msg subject (20 characters long, left justified)
A9 -- Msg from (20 characters long, left justified)
AA -- Msg to (20 characters long, left justified)
AB -- Msg # (5 characters long, left justified)
Q1 -- Msg area name (M0???)
Q2 -- Msg area number (M3??)
Q3 -- Msg area description (M5??)
Q4 -- # msgs in area (M1??)
Q7 -- Prints '*' if last read is less than current # of msgs.
' ' if not
Q8 -- Prints '+' if current area is tagged for offline mail.
' ' if not
QC -- Time/date msg was received (24 characters)
QD -- # times msg read (5 characters, right justified)
File area
A0 -- Area name
A1 -- Area number
Library area
L0 -- Area name
L1 -- Area number
Time (user time)
T0 -- Minutes left in session
T1 -- ????
T2 -- Seconds left in session
Date (current date/time)
D0 -- Month abbreviated (Jan, Feb, etc)
D1 -- Day abbreviated (Mon, Tue, etc)
D2 -- Year
D3 -- Month number
D4 -- Day number
D5 -- Month name (complete name)
D6 -- Day name (complete name)
D7 -- Time (HH:MM:SS)
D8 -- Date/Time (Dayofweek Month Dayofmonth HH:MM:SS Year)
_or_ (Mon Jan 1 00:00:01 1996)
Input
I0 -- Copies in last user input
Download / Upload stats
K0 -- Uploaded bytes (total)
K1 -- Downloaded bytes (total)
K2 -- Uploaded bytes (today)
K3 -- Downloaded bytes (today)
K4 -- Max upload bytes per day
K5 -- Max download bytes per day
K6 -- Download bytes left today
K7 -- Download KBytes left today
K9 -- Upload bytes left today
KA -- Upload KBytes left today
Misc
H0 -- Com port handle
LN -- Line number (1, 2, 3, etc)
PA -- cycle thru color scheme and return next ANSI color in
cycle
PB -- Press any key to continue prompt
PC -- Press [ENTER] prompt
PD -- Pause for 1/2 second
PG -- Pause for 1/30 second
PH -- Spinning cursor (return next cycle.. use with PA)
Q5 -- Add 1 to number of lines printed
Q6 -- Add 1 to number of lines printed
QF -- User storage??
QG -- Turns on U2_MONITOR_MAIL?
(All ANSI commands will be set to blank if user doesn't have
color turned on)
Foreground ANSI Color
F1 -- Black
F2 -- Dark blue
F3 -- Dark green
F4 -- Dark cyan
F5 -- Dark red
F6 -- Dark magenta
F7 -- Brown
F8 -- Light gray
F9 -- Dark gray
FA -- Blue
FB -- Green
FC -- Cyan
FD -- Red
FE -- Magenta
FF -- Yellow
FG -- White
Background ANSI color
B1 -- Black
B2 -- Dark blue
B3 -- Dark green
B4 -- Dark cyan
B5 -- Dark red
B6 -- Dark magenta
B7 -- Brown
B8 -- Light gray
Other ANSI
CL -- Clear to end of line
CS -- Clear screen
QE -- Last ANSI color
EVENT FILE CONFIGURATION
Events are interruptions during the normal BBS day. Such interruptions
might include polling for mail or door maintenance. The events.text.x
(x being the node number) file is located in the \Adept\Events
directory. Below is the format of that file:
Comments begin with semi-colons and can be on any line.
Any text after a semi-colon is ignored.
Keywords:
EVENTBEGIN -- Begins description of an event.
EVENTEND -- Ends description of an event.
NAME -- Name of the event
START -- Starting time of event in HH:MM format.
END -- (temporary) Ending time in HH:MM format.
LENGTH -- Length of event in minutes
COMMAND -- Command to spawn at beginning of event. If this is
a .CMD file, that file should be located in the
\Adept directory.
FLAGS -- Flags to control event
1 = Forced (event must run)
2 = Recv Mail only (doesn't call out)
4 = Send mail only (doesn't answer ring)
8 = No File REQuests
16 = BBS calls allowed
32 = Send Crash Mail
64 = Send Crash Mail no matter what the cost is
128 = Cost must be less than MAXCOST
256 = Cost must be more than MINCOST
512 = Cost must equal MAXCOST
1024 = Wait for COMMAND to finish before continuing
*** Add numbers together to combine flags.
ex: 24 = 8 (no FREQs) and 16 (BBS calls OK)
MINCOST -- Minimum cost (see flags)
MAXCOST -- Maximum cost
DAYOFWK -- Day of week to execute
1 = Sunday
2 = Monday
4 = Tuesday
8 = Wednesday
16 = Thursday
32 = Friday
64 = Saturday
256 = Weekdays (Mon. thru Fri.)
512 = Weekends (Sat. -n- Sun.)
1024 = All Days
Add numbers to combine days
DAYOFMONTH -- Day of month to execute. Use w/ MONTH
MONTH -- Month to execute. Use w/ DAYOFMONTH
Using the above combo can cause execution to happen
on a certain day of a certain month. If day of month
is set and month is not set (0) then it event will
occur on that day every month.
CALLTIME -- Time (in seconds) between calls
MAXBAD -- Max bad calls
MAXTRIES -- Maximum connects allowed
An Example Events.text.1 file:
EVENTBEGIN
START 00:00
END 00:05
DAYOFWK 1024
FLAGS 2049
COMMAND Cmd.Exe /c Bbsmaint.Cmd
NAME Daily Midnight Maintenance
MINCOST 0
MAXCOST 10000
MAXBAD 10
MAXTRIES 200
EVENTEND
EVENTBEGIN
START 00:06
END 04:59
DAYOFWK 1024
FLAGS 80
COMMAND Cmd.Exe /c Mail.Cmd
NAME My regular BBS mail event
MINCOST 0
MAXCOST 10000
MAXBAD 10
MAXTRIES 200
EVENTEND
EVENTBEGIN
START 05:00
END 06:00
DAYOFWK 1024
FLAGS 10
COMMAND Cmd.Exe /c Poll.cmd
NAME Poll for mail
MINCOST 0
MAXCOST 10000
MAXBAD 10
MAXTRIES 200
EVENTEND
EVENTBEGIN
START 06:01
END 23:59
DAYOFWK 1024
FLAGS 80
COMMAND Cmd.Exe /c Mail.Cmd
MINCOST 0
MAXCOST 10000
MAXBAD 10
MAXTRIES 200
EVENTEND
uNuke - ADEPTXBBS USER BASE UTILITY
uNuke is a user data base packing program for AdeptXBBS. This also
means that it will adjust last read pointers for all message areas
based on the newly packed user file. In other words, if a user record
is purged, then their last read pointers for each area must also be
purged.
How to install uNuke:
Copy uNuke.Exe to the AdeptXBBS directory. uNuke expects to operated
from that directory.
Command Line Parameters:
Parameters in brackets [] are optional.
uNuke [/Exx] [/Dxx or /Mxx] [/Q] [/K]
/Exx Set the 'Exempt' security level. Where 'xx' is the
security level. Any user with a security level greater
than or equal to this number will not be purged from the
user data base. They are considered 'Exempt' from purging.
/Dxx Set the maximum number of inactive DAYS.
/Mxx Set the maximum number of inactive MONTHS.
Where 'xx' is the number of inactive days or months.
You should use either days or months, but not both. If you
try to use both, the months figure will be ignored.
/K uNuke will kill back-ups of the user data base when it has
completed the packing process.
/Q Quiet Mode. The speed of uNuke will be approx. 500%
faster! Though your mileage may vary. In normal mode, the
user names are shown on the screen with a message showing
whether or not they have been purged.
/? Gives a quick list of parameters.
---------
Examples:
---------
uNuke /Q /D60 /E6
uNuke will operate in quiet mode, will purge users not on in over 60
days and users level 6 and above will not be purged.
uNuke /M6
uNuke will purge users not on in 6 months.
NOTE: All command line parameters are optional.
Environment Variables:
uNuke will look for the existence of two environment variables to aid
in its adjustment of the last read pointers. By default, uNuke will
look in the \Adept\Message_Bases directory for all *.LMR files. You
can change the default behavior with the following environment
variables:
XMSG -- Changes the default message base location from
\Adept\Message_Bases to whatever you specify.
Example: SET XMSG=H:\Adept\MsgBases
XXMSG -- Tells uNuke to also search these directories (yes, plural is
okay) for more *.LMR files. Separate multiple directories
with semi-colons.
Example: SET XXMSG=H:\Adept\Messages;M:\Message_Bases;
Frequently Asked Questions Concerning uNuke:
What would cause uNuke to purge a user record?
----------------------------------------------
uNuke will purge a user record if any of the following conditions are
met:
1. Blank 'Name' field. If there is no name, then uNuke will purge the
record. Being that uNuke is a 'C' program, a NULL as the first
character of the 'Name' field would be considered a blank name.
2. 'U_DELETED' bit is set in the user record 'Attribs' field.
If this flag is set, then the user record is purged. The only time
this will NOT work, is if the U_NOKILL bit flag is also set.
'U_NOKILL' means that this user record should never be purged.
3. If 'Maximum Inactive Days' is set and they have not been on in
that time. They will NOT be purged if they are exempt or the
U_NOKILL flag is set.
4. If 'Maximum Inactive Months' is set and they have not been on in
that time. They will NOT be purged if they are exempt or the
U_NOKILL flag is set.
What will keep uNuke from purging a user record?
------------------------------------------------
1. If the 'U_NOKILL' bit is set in the 'Attribs' field. This will
prevent uNuke from purging the record in nearly all cases. The
_only_ exception is if the user 'Name' field is blank.
2. Their security level meets or beats the 'Exempt' security
parameter. If the user 'Security1' field is greater than or equal
to the 'Exempt' parameter, then they will not be purged, unless the
'U_DELETED' bit is set in the 'Attribs' field.
3. The user will not be purged if they have been on more recently than
the inactivity parameter.
When should I run uNuke?
------------------------
uNuke tends to rearrange user records at will, therefore, AdeptXBBS
should be taken off-line when you decide to pack a user data base.
AdeptXBBS expects to place a user record back where it found it. If
you tried purging while AdeptXBBS is on-line, you risk corruption of
the user data base.
INTERNET CAPABILITIES
AdeptXBBS offers seamless integration into the Internet for E-MAIL,
TELNET, FTP, FINGER, NEWSGROUPS, IRC, mailing list services and
others as they come along. At the current moment the Internet
package for AdeptXBBS includes:
Those of who purchase the Internet capabilities will have access to
the beta versions of all of our internet modules. Once v1.0
is finished you will receive the finished i-net package including
E-MAIL, TELNET, FTP, FINGER, NEWSGROUPS, IRCII and the mailing list
capabilities.
AdeptXBBS's Internet modules requires a TCP/IP stack in order to
function properly. The AdeptXBBS host BBS 1:18/210.0@Fidonet will
provide seamless Fidonet/Internet gating for registered AdeptXBBS
Sysops.
If you have purchased the Internet Module:
To enable the Internet features, go to the Config->BBS->Internet
Options menus. Telnet Server and Socket Server support is supported
in this version. Set the ports you want the servers to sit on. For
Telnet the default in port 23, for Sockets we default to 6530.
After setting up the Telnet and Socket options you can then pick one
of the nodes to be the recipient of the Telnet and Socket connects.
To do this, go to the Config->Active Node->General Settings and check
the Telnet and the Socket options, also check the Use Telnet Timers
box. Any node can support BOTH a Telnet and a Socket connect!
If you ONLY want to allow telnet or sockets on that node check the one
you wish to allow. But it is recommended that you allow both. It is
also recommended that you keep the sockets on port 6530 so that anyone
using a terminal that supports sockets can 'call' your BBS. Sockets
are faster and cleaner then Telnet. They are also binary by nature
and will allow clean file transfers, something not always possible
over telnet.
NNTP Support
This is the first version of the BBS software with native Internet
Newsgroup Support via NNTP!
To setup NNTP go to the Config->BBS->Internet Options and fill in
the name of your NNTP News Server. This name will be specified
by your Internet provider. Next click on The NNTP Client option
checkbox. (It is best that you already have your SLIP, PPP
or TCP/IP network running with the news server available). The
BBS should be able to handle it if you are not connected to the
to the NET.
*** If you do not have a dedicated SLIP or PPP line, you can still
receive newsgroups. First, shut down Adept. Then connect to your SLIP
or PPP account. After you are connected, start up Adept with the
/NOINIT 1 option. Then go into the CONFIG->BBS->Internet Options
and click on the NNTP active button.
When the software first connects to the server it will
pull down the available newsgroup list. This could take 5-10
minutes.
After you have the list it is recommended that you then decide what
newsgroups you would like to get. There will be a file in the
\Adept\Usenet dir called Available.List that will also contain
a list of available newsgroups. You can pick the newsgroups to
turn on and off from the Config->BBS->Internet Options Menu.
FILE AREA CONFIGURATION
File Area Editor:
Accessed from Edit->File Areas...
+--+-----------------------------------------------------------+--+--+
: : File Area Editor : : :
+--+-----------------------------------------------------------+--+--+
: Name: Number: + Flags ----------------+ :
: : : :
: Desc: : x Free Downloads : :
: : x No Uploads : :
: Addr: : x No Downloads : :
: : x Leeching : :
: DL Path: : x Down Back? : :
: : x Up Back? : :
: UL Path: : x Charge for Files : :
: : x ULs Not Listable : :
: UL Time Back: : x ULs Not Downloadable: :
: : x No File List : :
: +----------------------+ : x Common File List : :
: : File Area Security : : x Upload Blindly : :
: +----------------------+ : x Copy From Drive : :
: +-----------+ +-----------+ +------------+ : :
: : Prev Area : : Next Area : : List Areas : : :
: +-----------+ +-----------+ +------------+------------------------ :
: +---------+ +---------+ +---------+ :
: : Add : : Insert : : Delete : +------------------+ :
: +---------+ +---------+ +---------+ : SAVE CHANGES : :
: +------+ +------+ +------------------+ :
: : Ok : : Help : :
: +------+ +------+ :
: Changes are *NOT* saved until you click on :
: <Save Changes> :
+--------------------------------------------------------------------+
Name : Place the name of the file area in this field.
Number: Place the # for this file area in this field.
Desc: This is where you can place the description of the file area.
Addr: This field is not yet currently used, but will be used for
internal TIC processing at some point.
DL Path: This is the default path for files in the current area.
UL Path: This is the default path for uploads to the current area.
Free Downloads : Check this box to make all downloads free in this
area.
No Uploads : Check this box to turn upload off for this area.
No Downloads : Turn off downloads for this area.
Leeching : Turn on leech checking for this area.
Down Back : Give back the users download time.
Up Back : Give back the users upload time.
Charge for Files : This is not fully implemented but you will be able
to assign a cost on a per file basis to be taken
from the users credit.
ULs Not Listable : Uploads will not show up in file listing.
ULs Not Downloadable : Enabling this will make new uploads non-
downloadable.
No File List : N/A
Common File List : Default
Upload Blindly : If the user has Zmodem, Ymodem or Sealink chosen it
will let them upload the files before asking them
for a description.
Copy From Drive : Copy files from download path.
+--+-----------------------------------------------------------------+
: : Area Security - (Area Name) :
+--+-----------------------------------------------------------------+
: +---------+ +---------+ +---------+ :
: Password: Age: : OK : : Cancel : : Help : :
: +---------+ +---------+ +---------+ :
:+- Download Security ----------------------------------------------+:
:: Sec Level 1: Sec Level 2: ::
:: Flags 1 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: Flags 2 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: ::
:+------------------------------------------------------------------+:
:+- Upload Security ------------------------------------------------+:
:: Sec Level 1: Sec Level 2: ::
:: Flags 1 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: Flags 2 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: ::
:+------------------------------------------------------------------+:
:+- SysOp Security -------------------------------------------------+:
:: Sec Level 1: Sec Level 2: ::
:: Flags 1 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: Flags 2 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: ::
:+------------------------------------------------------------------+:
+--------------------------------------------------------------------+
Password : Password required to upload a file into this area.
Age: Minimum age required to upload or download in area.
Download Security:
Sec Level 1: Sec Level 2:
Set security level #1 & #2 to the minimum security level required to
Download from the current area.
Mark the flags you will require the user to have in order to
download files in this area. Both the flags and the security levels
must pass in order to download files.
Upload Security:
Sec Level 1: Sec Level 2:
Set security level #1 & #2 to the minimum security level required to
upload from the current area.
Mark the flags you will require the user to have in order to upload
files in this area. Both the flags and the security levels must
pass in order to upload files.
SysOp Security:
Sec Level 1: Sec Level 2:
Set security level #1 & #2 to the minimum security level required to
gain access to the sysop functions in the current area.
Mark the flags you will require the user to have in order to gain
access to the sysop functions in this area. Both the flags and the
security levels must pass in order to use the sysop functions.
SysOp functions in the file area are not completely finished. But
will include such options as setting costs for files. Set Download
paths. Set file passwords. Set individual file security levels and
flags.
File Transfer Protocol Editor:
Accessed from Edit->File Protocols...
+--------------------------------------------------------------------+
: : File Transfer Protocols :
+--+-----------------------------------------------------------------+
: Name: Name Word # Sel. Char: :
: Log File Desc. Word #: :
: :
: +- Download ------------------------+ +- Flags -------------+ :
: : : : : :
: : Cmd; : : x Internal : :
: : Keyword: : : x External : :
: : String: : : x Batch : :
: : : : x Bi-Directional : :
: +-----------------------------------+ : x Full Screen : :
: +- Upload --------------------------+ : x Windowed : :
: : : : x UL Blind Ok : :
: : Cmd: : : x Rq. EC Connect : :
: : Keyword: : : : :
: : String: : +---------------------+ :
: : : :
: +-----------------------------------+ :
: +----+ +----+ +---+ +------+ +------+ +----+ +--+ +------+ +----+ :
: :Prev: :Next: :Add: :Insert: :Delete: :Save: :OK: :Cancel: :Help: :
: +----+ +----+ +---+ +------+ +------+ +----+ +--+ +------+ +----+ :
+--------------------------------------------------------------------+
File Area Control File Configuration:
Path and name of control file : \Adept\System\File_Areas
This is the file that Adept creates when you edit the file areas using
the pulldown menus. You can edit this file with a standard text
editor.
AREABEGIN - This directive marks the beginning of a area definition
NAME - This defines the message areas name
NUMBER - This defines the message area number
AGE - This defines the minimum age required to access the area
DESC - This is the description of this area
SEC1 - This is the minimum sec required to access this area
when compared with the users security level #1
SEC2 - This is the minimum sec required to access this area
when compared with the users security level #2
FLAGS1
FLAGS2
WSEC1 - This is the minimum sec required to write a messages in
this area, this is compared with user sec level #1
WSEC2 - This is the minimum sec required to write a messages in
this area, this is compared with user sec level #2
WFLAGS1
WFLAGS2
SSEC1 - This is the minimum sec required to access sysop
functions for this message area. I.e. Delete mail, read
private mail.
Compared with security level #1
SSEC2 - This is the minimum sec required to access sysop
functions for this message area. I.e. Delete mail, read
private mail.
Compared with security level #2
SFLAGS1
SFLAGS2
FLAGS
PASSWORD - Password required to access this message area.
MAXAGE - Maximum age of user to be able to access area
DLPATH - Download Path
ULPATH - Upload Path
COSTPERK - Cost Per K
AREAEND - This directive marks the end of a area definition
An Example File_Areas File:
AREABEGIN
NAME New Files
NUMBER 1
DESC ** UPLOAD New Files Here **
DLPATH D:\UPLOADS
ULPATH D:\UPLOADS
SSEC1 100
SSEC2 100
FLAGS 3105
AREAEND
AREABEGIN
NAME MIDI Files
NUMBER 2
DESC .MID Files
DLPATH D:\MIDI
ULPATH D:\UPLOADS
SSEC1 100
SSEC2 100
FLAGS 3105
AREAEND
AREABEGIN
NAME MOD Files
NUMBER 3
DESC .MOD and .S3M Files
DLPATH D:\MODS
ULPATH D:\UPLOADS
SSEC1 100
SSEC2 100
FLAGS 3105
AREAEND
AREABEGIN
NAME WAV Files
NUMBER 4
DESC .WAVs and .VOC Files
DLPATH D:\WAVS
ULPATH D:\UPLOADS
SSEC1 100
SSEC2 100
FLAGS 3105
AREAEND
AREABEGIN
NAME Adept
NUMBER 5
DESC Software / Info for use with Adept
DLPATH C:\ADEPTFIL
ULPATH D:\UPLOADS
SSEC1 100
SSEC2 100
FLAGS 3105
AREAEND
Adding Files To Your New Adept BBS:
When a user uploads a file the following things occur in the following
order.
1. When the transfer completes the BBS software determines if the file
or files uploaded are known archives based on the information in the
Archivers file. If the file is an archive the following is done to
that file:
The BBS software searches your path for a file called TestUpload.Cmd.
If this file is found it executes the file with the following command
line parameters:
CMD.EXE /c TestUpload.Cmd <fullfilename> <line#> <handle> <filename>
<extension>
<fullfilename> - Complete path/filename
<line#> - Line number
<handle> - handle to open com port
<filename> - Plain file name, no path, no extension
<extension> - Just extension.. no '.'
This CMD file may test the upload in whatever manner it sees fit. For
example: unzip -t, virus scan.. both.. neither.. whatever.. It could
also move the file for safe keeping.. etc.
If file does NOT pass the test, there should be a file in the Adept
directory called <filename>.Error This tells Adept the file did not
pass the test.
2. If the file passes that test, then the DIZ extraction is attempted.
The command line is identical to the previous one.
CMD.EXE /c ExtractDIZ.Cmd <fullfilename> <line#> <handle> <filename>
<extension>
This CMD file just looks for a description of some kind. Could be a
FILE_ID.DIZ, .DOZ... DESC.SDI whatever the format.. If it finds a
description it should create a text file with the description in it
The filename is:
\Adept\System\Line#\<filename>.Description
If the software doesn't find this file, it will ask for a description.
3. There is also a conversion command file called Convertxxx.CMD Same
commandline where 'xxx' is the extension of the upload itself. If a
.ZIP file is uploaded, the software looks for ConvertZIP.Cmd
CMD.EXE /c ConvertZIP.Cmd <fullfilename> <line#> <handle> <filename>
<extension>
If the conversion takes place, a file should be created in the Adept
directory called <filename>.NewName It should contain just the
filename of the file. For instance, if a file went from FROOD.ARC to
FROOD.ZIP Then 'Frood.NewName' would be created and it would have a
single line:
FROOD.ZIP
The file should be in the same path as the original.
If ALL fails and the file is marked as BAD, the BBS will execute the
file BadUpload.CMD with the following command line parameters.
Ex: "BadUpload.CMD Node FileName_With_Path FileName File_Extention"
The BadUpload.CMD file can be used to 'move' bad uploads into a
storage area for the sysop to check at a later date.
Converting a Files.BBS to the Adept Filebase Format:
BFSMake: (This refers to BFSMake1.exe)
BFSMake is designed to convert your current files.bbs's to the
AdeptXBBS FileBase.
There are several problems with the Files.BBS format that make even
converting them difficult. There are several different 'standard
formats' for the Files.BBS. And there is absolutely nothing you can
do to distinguish these formats from each other.
BFSMake supports Files.BBS Format #1 and Format #2.
Format #1:
-- Begin Sample Files.BBS Format #1 --
FILENAME.EXT ######## ##-##-## First line of description to 80 chars
| second line begins after the pipe.
| This is the format used by Hobbes
| CD-ROMS and it is the same format as
| the PCBoard DIR## lists.
NEXTFILE.EXT ######## ##-##-## Once again description begins here
| and continues here.
-- End Sample Files.BBS Format #1 --
Format #2:
-- Begin Sample Files.BBS Format #2 --
FIRSTFIL.EXT ######## ##-##-## The whole description on ONE line and
.. can go on for 255 characters.
BFSMake will support one line
descriptions up to 1024 characters.
-- End Sample Files.BBS Format #2 --
When BFSMake is run from the \Adept sub-directory. It will read your
File_Areas file. It will then proceed on a two pass system. On the
first pass it will scan EVERY directory in the File_Areas list and
import all the files in every directory into a index. Next on the
second pass it will start with the first directory and look for the
file 00_INDEX.TXT, it will scan the 00_INDEX.TXT from top to bottom
for the file names and match them to the index. If the 00_INDEX.TXT
is not found, FILES.BBS and then 00INDEX.TXT is looked for and
searched.
You can also specify a MASTER file list that meets the above formats
for BFSMake to search along with the 00_INDEX.TXT, FILES.BBS or
00INDEX.TXT. for file descriptions.
All your file areas need to be configured in the File_Areas file in
order for BFSMake to be able to find them and import the file lists.
BFSMake: (This refers to BFSMake2.exe)
BFSMake is designed to convert your current files.bbs's to the
AdeptXBBS FileBase.
There are several problems with the Files.BBS format that make even
converting them difficult. There are several different 'standard
formats' for the Files.BBS. And there is absolutely nothing you can
do to distinguish these formats from each other.
BFSMake supports Files.BBS Format #1 and Format #2.
Format #1:
-- Begin Sample Files.BBS Format #3 --
FILENAME.EXT First line of description to 1024 chars.
FILE1.EXT First line of description to 1024 chars.
-- Begin Sample Files.BBS Format #4 --
FILENAME.EXT First line of description to 1024 chars.
Second line of description to 1024 chars.
Third line of description to 1024 chars.
FILE1.EXT First line of description to 1024 chars.
Second line of description to 1024 chars.
Third line of description to 1024 chars.
When BFSMake is run from the \Adept sub-directory. It will read your
File_Areas file. It will then proceed on a two pass system. On the
first pass it will scan EVERY directory in the File_Areas list and
import all the files in every directory into a index. Next on the
second pass it will start with the first directory and look for the
file 00_INDEX.TXT, it will scan the 00_INDEX.TXT from top to bottom
for the file names and match them to the index. If the 00_INDEX.TXT
is not found FILES.BBS and then 00INDEX.TXT is looked for and
searched.
You can also specify a MASTER file list that meets the above formats
for BFSMake to search along with the 00_INDEX.TXT, FILES.BBS or
00INDEX.TXT. for file descriptions.
All your file areas need to be configured in the File_Areas file in
order for BFSMake to be able to find them and import the file lists.
Using CD-ROMS Including Multi-Changer CD-ROMS With Adept:
AdeptXBBS has built in support for CD-ROM drives. As users select
files they wish to download, a special file queue automatically takes
the needed files from the CD-ROMS, places them in a temp directory,
for you to download. This is all done in the background and will
prevent the constant disk swapping that sometimes occurs on multi-cd
rom changers especially when 2-5 users all want different files from
different drives. The area or file should be marked for 'Copy from
Drive' in order to activate this feature.
-- Listing Files From Inside Adept -----------------------------------
On a large system when a user does a [S]earch or [W]ide
area search or more commonly when the caller accidentally chooses
Continuous display, they can abort the scan by pressing CTRL-K or
CTRL-S
fList - An "all-files" List Creator For Adept:
Command line parameters:
------------------------
/Ccfgfilename - Change the default configuration file name from
fList.Cfg
Example: /Cmybbs.cfg
/? - Short help screen.
Configuration file key words:
-----------------------------
BBSNAME xxx - Where 'xxx' is your BBS name. 60 chars max.
INCLUDEAREAS xxx - Where 'xxx' are Area numbers to include in this
list.
A sequence of areas may be specified using the following format:
xxx-xxx
For instance, if you wanted areas 1 thru 10 in the list, you would
say:
INCLUDEAREAS 1-10
Multiple sequences may be separated by commas:
INCLUDEAREAS 1-10,31-45,99
You can have up to 10240 included areas.
PREPENDFILE xxx - Where 'xxx' is the name of a text file which
should be at the top of the file list.
APPENDFILE xxx - Where 'xxx' is the name of a text file which
should be added to the bottom of the file list.
OUTFILE xxx - Where 'xxx' is the name of the file list. Default
is 'Files/AllFiles.List'
DATESORT - Flag to tell the program to sort by date. Default
is by filename.
REVERSESORT - Flag to tell the program to sort in reverse order.
May be combined with DATESORT to start your list
with the most current files.
Example configuration file:
----[cut here]----
BBSNAME The Abandoned Land
INCLUDEAREAS 1-40,60-70,99
DATESORT
REVERSESORT
----[cut here]----
This example file includes file areas 1 thru 40, 60 thru 70 and 99,
and is sorted in dated order with newest files first.
ReIndexFile - Adept File System Reindexing Program:
Run this program from your \Adept directory. It will delete your
current file system indexes and build them from scratch using the
data in \Adept\Files\Files.Data
It will not reindex descriptions at this time, as Adept has a built in
function to do that.
NOTE: This program will use all the CPU you can give it.. it is a CPU
hog and proud of itself for it. So, run this program when you don't
mind if a few other processes get slowed down a wee bit.
Program requires a /NUKE command line parameter to run. This makes
sure the sysop wants to run this program which destroys the current
file system indexes and rebuilds them from scratch. No /NUKE? no
deleting of indexes.
Program updated to use fSys.Dll for it's interaction with the file
system.
Due to these changes, the program is smaller! but it may also be a
touch slower. This is because it operates on one file at a time,
rather than a block of 100 files at a time. Reindexing happens on
about 100 files per second on my system. Your mileage will vary.
ReadArc.Cmd - Archive Command Processor:
Don't delete or touch this, it knows what to do all by itself. :-)
The format of the ReadArc.Cmd file is:
%1 %2 %3 %4 %5 %6 %7 %8 %9
MESSAGE AREA CONFIGURATION
Message Area Editor:
Accessed from Edit->Message Areas...
+--+-----------------------------------------------------------+--+--+
: : Message Area Editor : : :
+--+-----------------------------------------------------------+--+--+
: Name: Number: + Flags ----------------+ :
: : : :
: Desc: : x EchoMail : :
: : x NetMail : :
: Addr: : x UseNet : :
: : x GroupMail : :
: Force To: : x Force Public : :
: : x Force Private : :
: Path: : x Anonymous Messages : :
: : x No Origin Line : :
: Msg Time Back: : x Compression : :
: : x ANSI Color Required : :
: +-------------------+ : x Macros in Text : :
: : Msg Area Security : : x Require Real Name : :
: +-------------------+ : x Assoc w/ File Area : :
: +-----------+ +-----------+ +----------+ : x Force to Same Name : :
: : Prev Area : : Next Area : :List Areas: : : :
: +-----------+ +-----------+ +----------+ : : :
: +--------+ +--------+ +--------+ +-----------------------+ :
: : Add : : Insert : : Delete : +-----------------------+ :
: +--------+ +--------+ +--------+ : SAVE CHANGES : :
: +------+ +------+ +-----------------------+ :
: : Ok : : Help : :
: +------+ +------+ :
: Changes are *NOT* saved until you click on :
: <Save Changes> :
+--------------------------------------------------------------------+
Name : Place the name of the message area in this field.
Number: Place the # for this message area in this field.
Desc: This is where you can place the description of the message
area.
Addr: Origin Address to use for this message area
Force To: Name to force all messages in this area to.
Path: Path to message files if not using the default.
Msg Time Back: Give the user the time back that it took to
write the message.
x EchoMail - Check this if this is a Fidonet EchoMail Area
x NetMail - Check this if this is a Fidonet NetMail Area
x UseNet - Check this if this is a UseNet Newsgroup (Not Implemented)
x GroupMail - Check this is this is a Fidonet GroupMail Area
x Force Public - Force All Messages Public
x Force Private - Force All Messages Private
** NOTE Check Force Public and Force Private to give the user a
choice.
x Anonymous Messages - Allow anonymous messages
x No Origin Line - Don't add a Origin and tear line to messages
x Compression - Turn on the fly compression on.
x ANSI Color Required - User requires ANSI color to read this area.
x Macros in Text - Allow Adept META Commands in the text.
x Require Real Name - Require the users real name, else uses their
handle.
x Assoc. w/ File Area - Associated with a file area.
x Force to Same Name - For to force to name.
Message Area Security:
+--+-----------------------------------------------------------------+
: : Area Security - (Area Name) :
+--+-----------------------------------------------------------------+
: +---------+ +---------+ +---------+ :
: Password: Age: : OK : : Cancel : : Help : :
: +---------+ +---------+ +---------+ :
:+- Read Security --------------------------------------------------+:
:: Sec Level 1: Sec Level 2: ::
:: Flags 1 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: Flags 2 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: ::
:+------------------------------------------------------------------+:
:+- Write Security -------------------------------------------------+:
:: Sec Level 1: Sec Level 2: ::
:: Flags 1 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: Flags 2 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: ::
:+------------------------------------------------------------------+:
:+- SysOp Security -------------------------------------------------+:
:: Sec Level 1: Sec Level 2: ::
:: Flags 1 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: Flags 2 ::
:: x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x x ::
:: ::
:+------------------------------------------------------------------+:
+--------------------------------------------------------------------+
Password - Password required to enter a message into this area.
Age: Minimum age required to post or read messages in area.
Read Security:
Sec Level 1: Sec Level 2:
Set security level #1 & #2 to the minimum security level required to
read messages in the current area.
Mark the flags you will require the user to have in order to read
messages in this area. Both the flags and the security levels must
pass in order to read messages.
Write Security:
Sec Level 1: Sec Level 2:
Set security level #1 & #2 to the minimum security level required to
write messages in the current area.
Mark the flags you will require the user to have in order to write
messages in this area. Both the flags and the security levels must
pass in order to write messages.
SysOp Security:
Sec Level 1: Sec Level 2:
Set security level #1 & #2 to the minimum security level required to
gain access to the sysop functions in the current area.
Mark the flags you will require the user to have in order to gain
access to the sysop functions in this area. Both the flags and the
security levels must pass in order to use the sysop functions.
Message Area Control File Configuration:
Path and name of control file : \Adept\System\Message_Areas
This is the file that Adept creates when you edit the message areas
using the pulldown menus. You can edit this file with a standard text
editor.
AREABEGIN - This directive marks the beginning of a area definition
NAME - This defines the message areas name
NUMBER - This defines the message area number
AGE - This defines the minimum age required to access the area
DESC - This is the description of this area
SEC1 - This is the minimum sec required to access this area
when compared with the users security level #1
SEC2 - This is the minimum sec required to access this area
when compared with the users security level #2
FLAGS1
FLAGS2
WSEC1 - This is the minimum sec required to write a messages in
this area, this is compared with user sec level #1
WSEC2 - This is the minimum sec required to write a messages in
this area, this is compared with user sec level #2
WFLAGS1
WFLAGS2
SSEC1 - This is the minimum sec required to access sysop
functions for this message area. i.e. delete mail, read
private mail.
Compared with security level #1
SSEC2 - This is the minimum sec required to access sysop
functions for this message area. I.e. Delete mail, read
private mail.
Compared with security level #2
SFLAGS1
SFLAGS2
FLAGS
ADDRESS - Fidonet Address to use for posted Net/EchoMail
messages.
PASSWORD - Password required to access this message area.
FORCETO - Name to force, force to messages to
ECHO - Nodes to Forward/Receive mail from
ORIGIN - Origin to use for this message area
PATH - Drive/Path to place message area files for this area
MAXAGE - Maximum age of user to be able to access area
AREAEND - This directive marks the end of a area definition
For more information on FidoNet and setting up echomail, see the
MAILER section of this documentation.
An Example Message_Areas File:
AREABEGIN
NAME General
NUMBER 1
DESC Local Messages
WSEC1 5
WSEC2 5
SSEC1 100
SSEC2 100
FLAGS 2376
AREAEND
AREABEGIN
NAME Private Mail
NUMBER 2
DESC E-Mail
SSEC1 100
SSEC2 100
FLAGS 2308
AREAEND
AREABEGIN
NAME Fos2bbs
NUMBER 3
DESC [FidoNet] OS/2 BBS Discussions
WSEC1 5
WSEC2 5
SSEC1 100
SSEC2 100
FLAGS 2328
ADDRESS 1:231/1320.0@Fidonet
AREAEND
AREABEGIN
NAME Fadeptsoft
NUMBER 4
DESC [FidoNet] Adept Software
WSEC1 5
WSEC2 5
SSEC1 100
SSEC2 100
FLAGS 2328
ADDRESS 1:231/1320.0@Fidonet
AREAEND
AREABEGIN
NAME Netmail
NUMBER 99
DESC Netmail
RSEC1 100
RSEC2 100
WSEC1 100
WSEC2 100
SSEC1 100
SSEC2 100
FLAGS 32
ADDRESS 1:231/1320.0@Fidonet
AREAEND
Xmsg - AdeptXBBS Message Base Utility/Packer:
XMSG:
Run XMSG without any parameters for more info.
Here are a few tips and tricks when it comes to XMSG and maintaining
the New Message Index's.
Several people have complained that users have gone and read mail and
days later the BBS still tells them that they have new messages
waiting and it's letters the user has already read. This is why we
invented the XMSG -I parameter.
XMSG -I reindexes and rebuild the personal message indexes for the BBS
and will NOT rebuild them for messages already read via other means.
It is recommended that you run XMSG -I ONCE a day in a nightly event
usually it's best to run it after your biggest nightly mail session
if you know when it is.
Also it is IMPERATIVE that you run XMSG -I after your have run XMSG
with ANY other parameter!
So if you have a nightly event that runs XMSG several times to
complete all your packing passes on the message base the LAST XMSG
should be a XMSG -I or your pointers will be all wrong and could cause
some problems with personal mail.
MAILER CONFIGURATION
Line Specific Mailer Settings:
Accessed from Config->Active Line->Mailer Settings...
+--+-----------------------------------------------------------------+
: : Line # Mailer Settings :
+--+-----------------------------------------------------------------+
: :
: +-- EMSI Strings ----------------+ +-- Flags -----------------+ :
: : : : : :
: : Phone # : (###) ### - #### : : x No Mailer : :
: : BPS Rate : 14400 : : x Versions 7 Nodelist : :
: : Flags : CM,XA,OS2,V32b,V42b : : x Call collision detect : :
: : : : : :
: +--------------------------------+ +--------------------------+ :
: :
: Mail Proc. Cmd : cmd.exe /c mail.cmd %s :
: :
: +-- Costs ---------------+ +-- Errors --------------+ :
: : : : : :
: : Mx. Mail K : 1024 : : Mx. Resyncs : 200 : :
: : : : : :
: : Mx. Mail Secs : 3600 : : Mx. Xfer Errs : 0 : :
: : : : : :
: : : : x Recv. From unknown : :
: : : : x Send to Unknown : :
: +------------------------+ +------------------------+ :
: +------+ +--------+ +------+ :
: : OK : : Cancel : : Help : :
: +------+ +--------+ +------+ :
+--------------------------------------------------------------------+
--- EMSI Strings -------------------------------
Phone #: This is the phone number displayed during a EMSI session.
BPS Rate: This is the Maximum BPS rate, it is displayed during a EMSI
session.
Flags: These are the flags for your system passed during a EMSI
session.
--- Flags --------------------------------------
No Mailer: Turns the Mailer On/Off (Check it for OFF)
Version 7 Nodelist: Tells XBBS to use a version 7 Nodelist, XBBS also
supports a version 6 Nodelist.
Call collision detection:
----------------------------------------------------------------------
Mail Proc. Cmd : This is the filename to run for mail processing.
----------------------------------------------------------------------
--- Costs --------------------------------------
Mx. Mail K : Maximum size of mail in K to send from this node. This
is also used to set the maximum K that someone can
FREQ from this node.
Mx. Mail Secs : Time limit is seconds to disconnect a stalled
transfer.
--- Errors -------------------------------------
Mx. Resyncs: Maximum number of transfer resyncs before aborting a
transfer
Mx. Xfer Errs: Maximum number of transfer errors before the mailer
aborts the session
Recv. From unknown: Tells XBBS it's Ok to receive mail from unlisted
nodes.
Send to unknown: Tells XBBS it's Ok to send mail to unlisted nodes.
Address Settings:
Accessed from Config->Active Line->Mailer Addresses...
+--+---------------------------------------+
: : Addresses :
+--+---------------------------------------+
: +-----------------------+-+ +---------+ :
: : ##:###/###.#@******** :^: : OK : :
: : ##:###/###.#@******** : : +---------+ :
: : : : +---------+ :
: : : : : Change : :
: : : : +---------+ :
: : : : +---------+ :
: : :v: : Help : :
: +------------------------+-+ +---------+ :
+------------------------------------------+
: +-------------------------------------+ :
: : : :
: +-------------------------------------+ :
: +---------+ +----------+ :
: : ADD : : Delete : :
: +---------+ +----------+ :
: :
+------------------------------------------+
Nodelist Information:
AdeptXBBS uses and supports the Fidonet Version 7 nodelist. AdeptXBBS
does not come with it's own internal nodelist compiler.
There are several nodelist compilers that can produce a Version 7
nodelist, these can be obtained from our support BBS or FTP sites.
QNODE and FASTLST are two such compilers.
Gate Keeper Control Documentation (GateKpr.Ctl):
The following is a list of commands that can be in your GateKpr.Ctl
file.
AREAFILE - This tells GateKeeper the name of your Area Control file.
Ex. - AREAFILE Area.Control
MAXDUPES #### - Dupe detection. Adept uses two methods of dupe
detection, both are extremely reliable and effective.
In order to turn dupe detection on you MUST specify
BOTH the Maximum number of dupes checking records to
keep (MAXDUPES).
The MAXDUPES keyword allows you to specify the maximum
number of dupe records to keep. Each dupe record is 8
bytes in size. If you want to keep dupe records for
the last 1000 messages it will be a 8k file.
The size of the dupe file for 8192 messages will be
64k
Ex. - MAXDUPES 1024
TOUGHDUPE - The TOUGHDUPE keyword turns on extremely stringent dupe
checking. It is possible, that this will catch a non-
duplicate message, however unlikely.
Ex. - TOUGHDUPE
KEEPDUPES - The KEEPDUPES keyword tells the BBS software to toss dupe
messages to the file AREDUPES.$$$ if you rename this file
to AREDUPES.PKT the BBS software will toss the file,
ignoring the duplicate messages.
Ex. - KEEPDUPES
NODUPES - The NODUPES keyword turns off dupe checking entirely, no
matter what other options are set.
Ex. - NODUPES
INBOUND - You can have as many inbound areas you want with Gate
Keeper. The inbound area is where Gate Keeper will look for
incoming .PKT's or Archived mail packets.
Ex. - INBOUND C:\ADEPT\MAILER\PUBLIC_INBOUND
INBOUND C:\ADEPT\MAILER\PRIVATE_INBOUND
OUTBOUND - You can only have one outbound directory with Gate Keeper.
The outbound directory is where Gate Keeper will place
outgoing mail packets both archived or otherwise.
Ex. - OUTBOUND C:\ADEPT\OUTBOUND_MAIL
MSGDIR - The MSGDIR is where adept will default to placing incoming
messages for your Adept Message base. Please realize Gate
Keeper also reads the Adept Message_Areas control file so
that it can check and see if you chose another directory to
place the messages in.
Ex. - MSGDIR C:\ADEPT\MESSAGE_BASES
ADDRESS - Gate Keeper requires a 5-D Fidonet style mail address. You
can have as many addresses as you want. The below example
shows 3 addresses on a address line. Please remember to use
a 5-D mail address.
Ex. - ADDRESS 1:18/210.0@Fidonet 55:50/0.0@AdeptNet ##:##/##.##@OtherNet
NETAREA - The NetArea tag sets the default area that Gate Keeper will
scan for Net Mail. Gate Keeper will place incoming NetMail
into this area also.
Ex. - NETAREA 99
LOGFILE - The logfile tag sets the name of the Gate Keeper Log File.
Ex. - LOGFILE C:\Adept\GateKeeper.Log
PACKSIZE - The PackSize tag sets the minimum size of the message to
run it through the Lzss compression
Ex. - PACKSIZE 8192
NOTINY - The NOTINY flag tells GateKeeper not to use TINY SEENBY's in
mail processing. Regular SEENBY's are pretty much useless
and just plain extra baggage. You only want to turn this on
if you are SURE this is what you want.
Ex. - NOTINY
NOFORWARD - Tells GateKeeper NOT to forward 'foreign'
mail.
Ex. - NOFORWARD
NOLOCALFORWARD - Tells GateKeeper not to forward local mail within
your net.
Ex. - NOLOCALFORWARD
KEEPPATH - Tells GateKeeper to KEEP EchoMail PATH lines when
importing them into the message base.
Ex. - KEEPPATH
KEEPSEENBYS - Tells GateKeeper to KEEP EchoMail SEENBY lines when
importing them into the message base.
Ex. - KEEPSEENBYS
TONAME "NAME" <OPTION>
MSG - Toss this message to a .MSG Fidonet style message
AREACNTL - This message is a Areafix Control Message.
ROUTE - 5-D Address
PROG - Program to run
The TONAME tag is a very special tag. This tag allows you to turn
on special functions like Areafix.
Ex. - TONAME "Any Name" MSG
TONAME "Areafix" AREACNTL
TONAME "Someone Name" ROUTE 1:18/210.0@Fidonet
TONAME "A Name:" PROG Program.exe
KILLBADDATES - The KILLBADDATES flag tells GateKeeper to trash all
messages with a bad dates field.
Ex. - KILLBADDATES
ALLOWBADAREAS - The ALLOWBADAREAS tells GateKeeper to NOT delete
messages with a BAD AREA: tag.
Ex. - ALLOWBADAREAS
DELETEINSECURE - variable tells GateKeeper to send all INSECURE
messages to the digital trash can in the sky.
NOUNKNOWN - Tells GateKeeper *NOT* to make UNKNOWN.PKT packets. This
option is useful if you are tossing things like planet
connect and have hundreds of Echos you DON'T want sitting
on your drive because they are 'UNKNOWN'
Ex. - NOUNKNOWN
NOSECURE - The NOSECURE variable tells GateKeeper to ignore message
security. If a message is received for a known area but
the node number is not in your downlink list instead of
marking the message as insecure it will toss it as if the
message was in the list of nodes allowed to send/receive
messages.
Ex. - NOSECURE
NOINSECURE - Tells GateKeeper *NOT* to make INSECURE.$$$ packets. If
a message is 'Insecure' it will be sent to the digital
trashcan in the sky.
Ex. - NOINSECURE
ACKNOWLEDGEERRQ - The ACKNOWLEDGEERRQ tells GateKeeper to acknowledge
reply requests.
Ex. - ACKNOWLEDGEERRQ
MAXTOHIBIT ## - The MAXTOHIBIT flag defines the maximum number of high
bit characters to allow in the To: field of a message
before it's considered a trashed message.
Ex. - MAXTOHIBIT 5
MAXFROMHIBIT - The MAXFROMHIBIT flag defines the maximum number of
high bit characters to allow in the To: field of a
message before it's considered a trashed message.
Ex. - MAXFROMHIBIT 5
MAXSUBJHIBIT - The MAXSUBJHIBIT flag defines the maximum number of
high bit characters to allow in the To: field of a
message before it's considered a trashed message.
Ex. - MAXSUBJHIBIT 5
NOROUTENET - Tells GateKeeper not to allow routed NetMail through this
system.
Ex. NOROUTENET
CHECKSEENBYS - Turns on SEEN BY checking. <barf>
Ex. - CHECKSEENBYS
PVTECHOASNET - Tells GateKeeper to send private EchoMail as NetMail.
Ex. - PVTECHOASNET
GROUNGEATTEMPS - Tells GateKeeper how many times to
parse a packet before it is considered a grunged
packet.
Ex. - GROUNGEATTEMPS 10
NOINDEXES - The NOINDEXES flag tells GateKeeper not to make AdeptXBBS
style message INDEXES. This is NOT safe to use if you run
AdeptXBBS
Ex. - NOINDEXES
MESSAGES <path> - The above tag tells GateKeeper where to place .MSG
messages
Ex. - NETPATH C:\Adept\MsgFiles
HOLD <path> - The HOLD tag tells GateKeeper where to hold .TIC files.
Ex. - HOLD C:\ADEPT\MAILER\TICS
FLAGSPATH - The flagspath tells GateKeeper where AdeptXBBS is keeping
it's flags for outgoing/incoming mail
Ex. - FLAGSPATH C:\ADEPT\MAILER\FLAGS
PKTSORTER - The PKTSORTER option tells GateKeeper the name and
location of a packet sort program to run before the
processing of a mail packet
Ex. - PKTSORTER C:\UTILS\PKTSORT.EXE
PASSWORD - The above tag lets you set a .PKT password.
Ex. PASSWORD #:###/###.##@Fidonet MYPASS
IMPORTALLNETMAIL - This keyword causes any NetMail going thru a
system to be imported into the NetMail area. If
this keyword is not present, the current default
behavior occurs.
Sample GateKpr.Ctl File
BEGIN Sample 'GateKpr.Ctl' file for GateKeeper
INBOUND C:\ADEPT\MAILER\PASSWORD_INBOUND_MAIL
INBOUND C:\ADEPT\MAILER\PUBLIC_INBOUND_MAIL
INBOUND C:\ADEPT\MAILER\UNLISTED_INBOUND_MAIL
;
OUTBOUND C:\ADEPT\MAILER\OUTBOUND_MAIL
;
MSGDIR C:\ADEPT\MESSAGE_BASES
;
ADDRESS 1:18/210.0@Fidonet
;
;
NETAREA 99
;
LOGFILE GateKpr.Log
;
PACKSIZE 65535
;
UNARCHIVE ARC.EXE ewn
ARCHIVE ARC.EXE mwn
;
AREAFILE Area.Control
;
TONAME "AreaFix" AREACNTL
TONAME "Area Control" AREACNTL
;
ROUTE 1.142.*.*.* Crash Same ZIP.EXE -m -j
ROUTE 1.320.*.*.* Crash Same ZIP.EXE -m -j
ROUTE 3.800.887.0.* Hold Same ZIP.EXE -m -j
ROUTE 1.*.*.*.* Crash Same ZIP.EXE -m -j
ROUTE 2.*.*.*.* Crash Same ZIP.EXE -m -j
ROUTE 3.*.*.*.* Crash Same ZIP.EXE -m -j
ROUTE 4.*.*.*.* Crash Same ZIP.EXE -m -j
ROUTE 5.*.*.*.* Crash Same ZIP.EXE -m -j
ROUTE 6.*.*.*.* Crash Same ZIP.EXE -m -j
;
To setup a pass through area using GateKeeper set the area to 0.
Sample Area.Control File
; -- BEGIN Sample 'Area.Control' file for GateKeeper -----------------
;
; GateKpr EchoMail control file
;
;
; DEFLOCK and DEFKEY should come before any addresses in this file, if
; you wish to use them.
;
;
;=====================================================================
;DEFLOCK <default lock>
;
; ** Assign default lock to all areas not included in the PROTECT
; lines. Any locks present on PROTECT lines will take precedence.
;
; NOTE: See PROTECT lines for more info on locks.
;
DEFLOCK Ab1
;
;=====================================================================
;DEFKEY <default key>
;
; ** Assign default key to all addresses not included in the
; ADDRCONTROL lines.
; Any keys present on ADDRCONTROL lines will take precedence.
;
; NOTE: See ADDRCONTROL lines for more info on keys.
;
DEFKEY Ab1
;
; Remember those 5D addresses!
;
;=====================================================================
;ECHO <ECHOID> <msg area #> <5D FTN address> [<5D FTN address>]
[<5D FTN address>]
;
ECHO ADEPT_BETA 1 1:213/760.0@fidonet
ECHO ADEPTSOFT 2 1:213/760.0@fidonet
ECHO OS2 3 1:213/760.0@fidonet
ECHO C_ECHO 4 1:213/760.0@fidonet
ECHO OS2BBS 5 1:213/760.0@fidonet
ECHO OS2PROG 6 1:213/760.0@fidonet
ECHO OS2HW 7 1:213/760.0@fidonet
ECHO OS2LAN 8 1:213/760.0@fidonet
ECHO OTHERNETS 9 1:213/760.0@fidonet
ECHO PASCAL 10 1:213/760.0@fidonet
ECHO NET_DEV 11 1:142/906.0@Fidonet
ECHO BBS_STANDARDS 12 1:142/906.0@Fidonet
ECHO DOORWARE 13 1:142/906.0@Fidonet
ECHO OPENDOORS 14 1:142/906.0@Fidonet
ECHO TREK_VOYAGER 15 1:142/906.0@Fidonet
ECHO SYSOP142 16 1:142/906.0@Fidonet
ECHO POWERPC 17 1:142/906.0@Fidonet
ECHO MENSA 18 1:142/906.0@Fidonet
ECHO OS2COMM 19 1:142/906.0@Fidonet
ECHO OS2 20 1:142/906.0@Fidonet
ECHO OS2BBS 21 1:142/906.0@Fidonet
ECHO ADHD 22 1:142/906.0@Fidonet
;
;
;
;=====================================================================
;GROUP <groupid> <msg area #> <numdays> <5D FTN address | !topstar
;option>
;
; The above is the control statement outline for GROUP Mail.
;
;
;=====================================================================
;PROTECT <echo|group id> <seclevel[,lock]>
;
; ** Assign security level to an area for area control messages
;
; <echo|group id> Name of echo or group area to assign protection.
;
; <seclevel[,lock]> Security level assigned to this node address.
; may also contain a 'lock' similar to used with Areafix.
; To secure the area with a lock, separate it with a comma
; from the security level.
; for example: 5,FgH
;
; NOTE: You must include a security level before the comma,
; even if it is zero.
;
;Locking Mechanism: To put it simply, the nodes 'key' must contain all
; the characters contained in an areas 'lock'.
; No Lock?? Then, no key is necessary.
;
; Valid characters in a lock will be: A-Z, a-z, 0-9
;
; Locks can be up to 15 characters in length
;
;=====================================================================
;PROTECT <echo|group id> <seclevel[,lock]>
;
PROTECT ADEPTBETA 6,GJk
PROTECT OS2 5
;
;=====================================================================
;ADDRCONTROL <5D FTN Address> <password> <seclevel[,key]>
;<flags>
;
; ** Address control
;
; <password> which allows access to area control functions
;
; <seclevel[,key]> Security level assigned to this node address.
; This may also contain a 'key' similar to used with
; Areafix. To add a key, separate it with a comma from the
; security level.
; for example: 5,DEFGH
;
; NOTE: To add a key, you must include a security level
; before the comma, even if it is zero.
;
; Locking Mechanism: To put it simply, the nodes 'key' must contain
; all the characters contained in an areas 'lock'.
;
; Valid characters in a key will be: A-Z, a-z, 0-9
;
; Keys Can be up to 19 characters in length
;
; <flags> Flags to set for this node address. Current valid flags are:
; TYPE2 -- Build a type 2 packet for this node
; TYPE2+ -- Build a type 2+ packet for this node
; TYPE3 -- Build a type 3 packet for this node (not
; implemented)
; TYPE2QM -- Build a type 2 packet w/QMail revisions for
; this node
; TYPE2+QM -- Build a type 2+ packet w/QMail revisions for
; this node
; TYPE2DOT2 -- Built a type 2.2 packet for this node
;
; NOTE: A security level must be on the line to set the flags
;
;=====================================================================
;ADDRCONTROL <5D FTN Address> <password> <seclevel[,key]>
;<flags>
;
ADDRCONTROL 1:213/760.0@fidonet BUZZER
ADDRCONTROL 1:18/210.0@fidonet REALM 6,GAHJk TYPE2+
.TIC File Echo Configuration For GateKeeper
TIC-Style file areas are supported by GateKeeper. We call it "File
Control".
The TZ environment variable should be set the same as if you were
using TICK.. i.e.: SET TZ=PST8PDT
All file control information is normally stored in a file called
"File.Control" But you can specify any name you wish. To specify a
name, use the FILEAREA keyword in GateKpr.Ctl:
FILEAREA filename
example:
FILEAREA File.Control
NOTE: the FILEAREA keyword in GateKpr.Ctl is different than the
FILEAREA keyword when read from the File.Control file.
Other file control keywords are (found in GateKpr.Ctl):
NOTICCRC - Don't check or generate CRC-32's for the files in this
area. This will only happen if the TIC file received also
had no CRC-32 in it. If the TIC had a CRC-32 in it, it is
passed on to the down-stream nodes. This keyword is a
global keyword. It causes ALL file control areas to
bypass generating and checking TIC CRC-32's.
DELETEFILEDUPES - If you have TIC CRC-32 checking enabled and a file
has the same name, area and CRC as a previous file,
it will be deleted. If this option is off, then the
TIC file is renamed and the duplicate is logged.
You can then decide what needs to be done with the
file. By default deleting is off.
FILECOLLISION [action] - A file collision happens when you try to add
a file to an AdeptXBBS file area which has
the same filename as a file already in that
area. The FILECOLLISION keyword helps you
tell GateKpr what to do in that event. The
following are the current available actions:
OVERWRITE - This deletes the entry for the old file and puts the
new file in its place. Only the entry in the file
system is deleted. The actual file may not be deleted
or overwritten if it is not in one of the directories
specified for that file area.
OVERWRITE is the default.
RENAMEOLD - This renames the older file to a unique name and
adds the new file to the file area.
RENAMENEW - This renames the new file to a unique name and adds
it to the file area.
So a valid line would be: FILECOLLISION RENAMEOLD
HOLD [path] - This is the file control hold path. Files and TICs are
placed there while they are waiting to be sent. Dupe
files are also stored here.
Example:
HOLD C:\ADEPT\MAILER\HOLD
Format of File.Control:
FILEAREA AreaNum AreaName
Address Password Flags
;
; this is a remark
;
FILEAREA AreaNum AreaName
FLAGS DLDIR
Address Password Flags
Address Password Flags
;
FILEAREA AreaNum AreaName
Address Password Flags
Address Password Flags
;
;
; etc.
The FILEAREA keyword creates a file area which may correspond to an
AdeptXBBS file area and/or a TIC style file area.
FILEAREA AreaNum AreaName
AreaNum = Adept File Area Number
0 = no corresponding AdeptXBBS file area, in other words a
passthru file area.
When a corresponding AdeptXBBS file area is found, the file
is moved into the upload directory for that file area and
the file and its description are added to the file system
in that area.
AreaName = TIC file area name
Corresponds to the file area found in the .TIC file.
FLAGS flag1 [flag2] [flag3]
Flags control how this area is acted upon. Flags do not need to be
included for each area. If you have a flags line, it should follow the
FILEAREA line.
Valid flags are:
DLDIR - Instead of moving the file to that areas upload path,
move it to that areas download path.
NOTICCRC - Don't check or generate CRC-32's for the files in this
area. This will only happen if the TIC file received also
had no CRC-32 in it. If the TIC had a CRC-32 in it, it is
passed on to the down-stream nodes.
CHECKDUPES - Checks for TIC duplicates. This involves saving the file
name, the area it is associated with and the CRC-32 of
the file.
You should use this flag in each area where you wish to
have checking for TIC duplicates.
GateKpr also employs checking for AdeptXBBS style
duplicates.
These duplicates occur when a file goes into an AdeptXBBS
file area which already has a file of the same name. See
the FILECOLLISION keyword above to specify the action
GateKpr should take on AdeptXBBS duplicates.
NOTE: AdeptXBBS duplicate checking is employed at all
times!
AdeptXBBS allows for duplicate filenames in the
file system, but they cannot be in the same file
area.
More flags will be supported in the future, along with more keywords
for each file area.
Following the FILEAREA and FLAGS keywords must be one or more nodes
which may deal with this area. The first may be the node from which
you received the file, the following nodes would be the nodes you are
sending the file to. But, the order is not important.
An address entry looks like so:
Address Password Flags
Address = Valid address, can be 3D, 4D or 5D address. TIC appears to
work with 3D addresses. Gate Keeper will do 5D.
Password = Password used when dealing with this node.
When receiving a file, this password must match the
password in the .TIC file or the .TIC file is considered
invalid. When sending to a node, password is put into the
.TIC file. A password is required at this time.
Flags = Contains one or more flags. Valid flags are:
S - Secure password mode. The password is sent in a
numerical form, not as the password itself. Any nodes
using the secure password option should have the S flag
set for each node it is swapping secure passwords with.
This will only work with systems running GateKeeper!
R - Node is Read-Only. In other words, we should only
receive files from this node. We will not send any
files to this node.
W - Node is Write-Only. We should only send files to this
node, we will not receive any files from this node.
If we do receive a file or files, we will ignore it.
H - Hold Flag.
C - Crash Flag.
D - Direct Flag.
N - Normal Flag.
5 - 5D address flag. Puts 5D addresses into .TIC file. Not
recommended unless you are sending to a system which
won't puke when it finds a 5D address in a .TIC file.
(i.e. Another AdeptXBBS system)
- NOT YET IMPLEMENTED -
Flags can be combined:
WH = Write only, put files on hold.
WC5 = Write only, crash files to node, put 5D addresses in
.TIC file.
Outbound Mail Naming Conventions:
AdeptXBBS uses long file names for it's mail packets. The following
is the basic outline for all Adept Mail Packets.
TYPE.ZONE.NET.NODE.POINT.NETWORK
TYPE Can be any of the following.
A = Archived Mail Packet
R = File Request
H = Hold Mail
C = Crash Mail
D = Direct Mail
N = Normal Mail
P = Unarchived Packet
C, N, D, H are modifiers. And can also contain the name of a file to
be sent using that particular flavor.
For example you can have a archived mail packet for me.
1:142/210.0@Fidonet.
A.1.142.210.0.Fidonet
Now say you want to send it crash mail, you can then create a 0 byte
file as 'C.1.142.210.0.Fidonet'.
To send a file attach to me at 1:142/210.0@Fidonet
You would create a file called 'C.1.142.210.0.Fidonet' And on the
first line of the file place the name of the file to crash mail to me.
C:\ADEPT\MYFILE.TXT
If you append a ' before the name it will delete the file after it had
been sent.
AreaFix Type Commands:
GateKpr accepts lines in an Areafix style message that begin with '+'
GateKpr accepts lines in an AreaFix style message that begin with '%'
the two key words recognized are 'query' and 'list' all other words
are ignored at this time.
In the \Adept\gatekpr.ctl add the following line:
TONAME "AreaFix" AREACNTL
"Areafix" can be anything, but Areacontrol is usually called AreaFix
or AreaMgr.
Also define your downlink's Areafix password's in the Area.Control
file. That is outlined in more detail in the section on AREA.CONTROL.
Here is an example of a message that your downlink might write to
'AreaFix' to tell AreaFix what it has to do for him/her.
Example:
Msg : 13 of 23 Uns Pvt Loc K/s
From : Joe Smoe 1:282/9999 Wed 31 Dec 93 23:59
To : AreaFix 1:282/3029 <--Address of your BBS
Subj : PASSWORD <- Your AreaFix password
---------------------------------------------------------------------
+RA_UTIL <- Add (link) area
-SYSOPS.024 <- Remove (unlink) area
%QUERY <- Ask for your active areas
%LIST <- List available areas
Mailer 'OK' File - File Request Format (FREQ):
An `OK' file is a file that tells your mailer which files are
available for people to FREQ (File Request) from you. Create a
PUBLIC.OK file and place it in your \Adept\Mailer directory.
OK files follow the 'Binkley' style OK file format
where MAGIC names have a `@' in front of them. Other
wise, the file path is listed so that any file in that
path can be FREQed. In the example below, a person can
FREQ SIO142.ZIP by using the magic name SIO
@ADEPTXBBS C:\Files\Adept\Adept_90.Zip
@SIO C:\Files\Comm\Sio142.Zip
@NODELIST D:\fido\fidofile\Nodelist.A??
@NODEDIFF D:\fido\fidofile\nodediff.A??
D:\Files\netupld\*.*
D:\Files\upload\*.*
D:\Files\fidofile\*.*
D:\Files\games\*.*
D:\Files\utilities\*.*
Other Text Files Used With The Mailer:
These are looked for when your system gets a bad file request (FREQ).
Create these files and place them in your \Adept directory.
SYSTREQ.TXT - System error (as in BBS program)
Could have been, say, unable to allocate memory.
etc.
SYSPREQ.TXT - OK File list not found. Sysop hasn't created them
or maybe in the wrong dir.
BADPREQ.TXT - Passwords don't match.
Password on file request didn't match.
BADFREQ.TXT - File request not found on system. Pretty self
explanatory :)
Configurable Mail Directories:
There are three distinct inbound directories that can be used.
They should, ideally, all be on the same drive (the default)
The directories are for, in order:
.\Mailer\Password_Inbound_Mail -- Passworded connections
.\Mailer\Public_Inbound_Mail -- Unpassworded but listed
connections
.\Mailer\Unlisted_Inbound_Mail -- Unlisted connections
There are corresponding OkFile listings as well.
.\Mailer\Password_File_List
.\Mailer\Public_File_List
.\Mailer\Unlisted_File_List
The directory to be used is decided after the YooHoo packet is
exchanged or after the introductory packet is received in an FTS-0001
session.
When Adept starts a session with the ext(ernal)mail processor because
mail was received, it passes the inbound directory currently in use
(which is usually where the mail will be :-). If you press M for Mail
Processing at the "waiting" screen, the first outbound area will
always be passed.
You can change these directories from Adepts setup dialog boxes.
Bad Mail Packets:
Insecure.$$$ - ONLY created when you receive messages in a known
message area from a node that is not defined in the
Area.Control file.
Unknown.$$$ - Created if the area does not exist.
-- Mail.Cmd - Sample mail processing command file --------------------
The Mail.Cmd file is a sample batch file for handling incoming mail
processing.
XSENDPM - FIDO File Sending Utility:
XSENDPM.EXE copyright (c) 1993-95 by M. Kimes all rights reserved
Overview:
========
XSENDPM is a simple PM program that allows you to send files via
XBBS-OS/2 or AdeptXBBS.
XSENDPM supports drag-and-drop to its WPS object and also
provides an "open dialog"-style interface to allow the user to
select files to send. Files to send may be typed into an entry
field or selected from listboxes. Version 7 nodelists are
supported for lookup of sysop names and information about nodes.
See GS.EXE for a command line alternative.
Installation:
============
Edit the file XSEND.CMD that comes with AdeptXBBS to contain the
proper drive letters and paths for your AdeptXBBS Outbound and
nodelist directory.
Usage:
=====
Drag a file onto XSENDPM's WPS object or double-click the object to
start XSENDPM. You'll get a dialog that allows you to specify to
whom you want the file sent and some other options. Brief help is
available from within the program.
Warranty:
========
There is no warranty expressed or implied. You're on your own,
goodnight.
FAX Connects:
AdeptXBBS's Mailer has the ability to run a fax command file for fax
connects allowing you to run BGfax or another program to receive fax's
with AdeptXBBS.
First you need to have the following 3rd party programs:
BGFAX (BGFAX147.ARJ)
Ray Gwinn's SIO Drivers (SIO153.ZIP)
Both of these programs can be found from the same places
you download or FTP other OS/2 shareware.
Modify your config.sys:
SET BGFAX=C:\BBSFAX
SET FAX=DEBUG
* modify C:\BBSFAX to your directory where BGFAX is installed.
* SET FAX=DEBUG if you wish to log extra info about what BGFAX does!
DEVICE=C:\sio\SIO.SYS (COM2:57600,02F8,3,-) (COM3:57600,03E8,5,-)
DEVICE=C:\sio\VSIO.SYS
* Adjust your ports / IRQ's accordingly.
Modify AdeptXBBS modem Init's:
Here are 2 examples using two modems under Adept: COM2:Hayes Optima 288 V34
and COM4:USR V.Everything
A) Hayes:
Answer: AT+FAE=1;A|
* this is adaptive answering for class 1 modems
INIT: ATH0|~AT+FCLASS=1|~AT&C1&D2S95=43|
DIAL: AT+FCLASS=0DT
B) USRobotics Courier V.Everything
Answer: AT+FAA=1+FNR=1,1,1;A|
Init: ATH0|~AT&F1&K3X4|~AT+FCLASS=2.0|
Dial: AT+FCLASS=0DT
Modify or create the following .CMD files:
\Adept\fax1.cmd has the following: (FAX1.CMD)
rem *** fax.cmd for my node 1 - Hayes Optima V34 - Locked 57600!
SU LOCK 0
c:\bbsfax\BGFAX2.EXE /FHAY:965_252-1974 C:\FAXWORKS h%1 q
SU LOCK 57600
\Adept\fax2.cmd has the following: (FAX2.CMD)
rem *** fax.cmd for my node 2 - USR Courier V.Everything - Locked 57600!
SU LOCK 0
c:\bbsfax\BGFAX2.EXE /FCO C:\FAXWORKS h%1 q
SU LOCK 57600
SETTING UP DOORS UNDER AdeptXBBS
DOS and OS/2 Doors can be run successfully under Adept.
Doors are online games that your users can play against
other users or computer players. These instructions assume
that you have at least a limited knowledge of how to
set up doors.
First you need Ray Gwinn's SIO comm drivers for OS/2.
These can be downloaded or ftp'ed from various sources
or you will be able to find them on the Adept Support BBS.
After you install them, you need to make sure that the
undocumented '-' feature is used. Here's what the appropriate
lines in your config.sys should look like:
REM DEVICE=C:\OS2\BOOT\COM.SYS
REM DEVICE=C:\OS2\MDOS\VCOM.SYS
REM ......... Ray Gwinn's SIO Com drivers ........
DEVICE=C:\SIO\SIO.SYS (1, 3F8, 4,-)
DEVICE=C:\SIO\VSIO.SYS
DEVICE=C:\SIO\VX00.SYS
Here, OS/2's original com drivers have been commented out and
the SIO drivers are used with the '-' switch. In this example,
only COM1 is setup. Consult the SIO documentation for more
information on setting up these drivers for your system.
The following are the steps that would be used to set up the
popular game Trade Wars 2002 for DOS.
1. Unzip the game into its own directory and install it
according to the directions.
2. Add the following entry to your door.menu file:
1 ,801,,cmd.exe /c twar.bat {LN {H0,0
Pressing 1 will now start the door, passing it the line
number and the user's handle.
3. Create a file called twar.bat in your \Adept directory.
Below is a sample of what your twar.bat should look like.
Edit it to use your drive and path information.
Notice that DOOR.SYS is copied from the \Adept\System\Line%1
The DOOR.SYS file is created by Adept and placed in the Line%1
directory. The %1 is the current node. So, if someone started
the door on node 2, a '2' would be substituted for the '%1'
character.
If your door game does not support the DOOR.SYS drop file, then
you must obtain a drop file converter. These can be downloaded
or FTP'd from other BBSes.
Sample Batch Files:
----twar.bat------
D:
CD \doors\tw
del door.sys
copy c:\adept\system\line%1\door.sys
tw2002 NOEMS
del door.sys
c:
cd\adept
-----------------
Here are some other examples of batch files that run door games:
----Barren Realms Elite batch file------
D:
CD \DOORS\BRE
del door.sys
copy c:\adept\system\line%1\door.sys
SRDOOR
BRE
del door.sys
c:
CD \adept
----------------
----Mines of Gorr batch file------
D:
CD \doors\mog
del door.sys
copy c:\adept\system\line%1\door.sys
gorr door.sys
del door.sys
c:
cd \adept
----------------
----Iron Ox (OS/2 Version) cmd file-------
D:
CD \doors\ox
copy c:\adept\system\line%1\door.sys
/ironox /PORT
del door.sys
c:
cd\adept
----------------
APPENDIX
Example .MENU Files:
The following is an example of a MAIN.MENU file:
\r,0,MainMenu.ASC,Main Menu ,4
? ,51 ,,Commands.Asc ,0
- ,2 ,,,0
~ ,1000,Goodbye/Logoff ,,0
G ,1 ,Good-bye,LogOff.Menu ,0
;
; Other Menus
;
M ,1 ,Message Menu,Messages.Menu ,0
F ,1 ,File Menu,Files.Menu ,0
B ,1 ,Bullet Menu,Bullet.Menu ,0
O ,1 ,Doors Menu,Door.Menu ,0
* ,1 ,Sysop Menu,Sysop.Menu ,,,,100,100
;
; Commands
;
A ,10 ,,Callers.cmd ,0
S ,51 ,,Info.asc ,0
L ,43 ,User [L]ist ,,00
T ,1 ,Time Bank,TimeBank.Menu ,,,,5,5
C ,201 ,Comment to the Sysop ,Sysop;Comment from {U0;2;1,0
P ,10 ,,UserInfo.cmd,0
U ,1 ,User Setup,EditUser.Menu ,0
E ,10 ,,Sendemail.cmd,0
Y ,48 ,Yell for Sysop ,,0
Example DOOR.MENU:
\r,0,door.asc,Online Games,4
? ,51 ,,Commands.Asc,0
T ,1 ,Gosub main menu,Main.Menu
* ,1 ,Gosub main menu,Main.Menu
M ,1 ,Gosub main menu,Messages.Menu
F ,1 ,Gosub main menu,Files.Menu
U ,1 ,Gosub main menu,EditUser.Menu
- ,2 ,Return to previous menu,,0
G ,1 ,Goodbye/Logoff,LogOff.Menu,0
~ ,1000,Goodbye/Logoff,LogOff.Menu,0
1 ,801,,cmd.exe /c twar.bat {LN {H0,0
2 ,801,,cmd.exe /c bre.bat {LN {H0,0
3 ,801,,cmd.exe /c mog.bat {LN {H0,0
4 ,801,,cmd.exe /c ox.cmd {LN {H0,0
5 ,801,,cmd.exe /c hang.bat {LN {H0,0
6 ,801,,cmd.exe /c tarot.bat {LN {H0,0
7 ,801,,cmd.exe /c songs.bat {LN {H0,0
8 ,801,,cmd.exe /c tune.bat {LN {H0,0
9 ,801,,cmd.exe /c cards.bat {LN {H0,0
0 ,801,,cmd.exe /c warlrd.bat {LN {H0,0
A ,801,,cmd.exe /c freevote.bat {LN {H0,0
B ,801,,cmd.exe /c war.bat {LN {H0,0
C ,801,,cmd.exe /c fictfact.cmd {LN {H0,0
Example FILES.MENU:
\r,12,FileMenu.ASC,File Menu,4
?,51 ,,Commands.Asc,0
M,1 ,,Messages.Menu,0
!,1 ,,Door.Menu,0
*,3 ,,Main.Menu,0
-,2 ,,,0
~,1000,,,0
L,78 ,[L]ist File In This Area ,,15
N,74 ,[N]ew files ,,15
T,10 ,,tabnav.cmd ,0
S,1 ,,Search.Menu,0
A,61 ,[A]rea Selection ,,15
D,85 ,[D]ownload file(s) ,,15
P,146 ,[P]rotocol Selection ,,15
U,90 ,[U]pload file(s) ,,15
>,65 ,[>] Next file area ,1,15
<,65 ,[<] Previous file area ,-1,15
V,84 ,[V]iew Archive contents ,,15
R ,801,,cmd.exe /c rom.bat {LN {H0,0
G,1 ,[G]oodbye ,LogOff.Menu,15
E,670 ,[E]dit Files List ,,0
C,201 ,Comment to the Sysop ,Sysop;Comment from {U0;2;1,0
AdeptXBBS USER Base Structure:
The following is the structure for the AdeptXBBS user file.
The following flags are used for the 'user.attribs' bits.
#define U_ANSI 0x00000001 - Ansi Movement
#define U_COLOR 0x00000002 - Ansi Color
#define U_HIGHASCII 0x00000004 - High Ascii
#define U_NOMORE 0x00000008 - No? More? Prompts
#define U_NOCLEAR 0x00000010 - Don't Clear Screens
#define U_COLD 0x00000020 - No Hot Keys
#define U_NOSHOWADDRESS 0x00000040 - Don't show address in user
list
#define U_NOSHOWPHONE 0x00000080 - Don't show phone numbers
in user list
#define U_NOSHOWREAL 0x00000100 - Don't show real names in
user list
#define U_NOKILL 0x00000200 - User cannot be
killed/deleted
#define U_DELETED 0x00000400 - User marked as deleted
#define U_EXPERT 0x00000800 - User set for expert mode
#define U_TWIT 0x00001000 - User is a twit!
#define U_NEWFILES 0x00002000 - New files search at logon
#define U_NEWMSGS 0x00004000 - New message search at
logon
#define U_DLNEWMSGS 0x00008000 - Auto download mail packets
at logon
#define U_DLNEWFILELIST 0x00010000 - Auto download new file
list at logon
#define U_SEENEWS 0x00020000 - Sees new news
#define U_ASKDL 0x00040000 - Ask logoff before download
#define U_NOVICE 0x00080000 - User set to novice
#define U_NOROLL 0x00100000 - no rolling prompts
(obsolete)
#define U_POINTONLY 0x00200000 - Fidonet point mail only
#define U_LOCKEDOUT 0x00400000 - User locked out
#define U_AVAILABLE 0x00800000 - Available for multi-node
chat
#define U_LISTPROTECTED 0x01000000 - Not shown in user list
#define U_MISCNEWSOK 0x02000000 - Sees misc. news
#define U_LIMITFLIST 0x04000000 - Limit file list to current
area
#define U_EBCDIC 0x08000000 - EBCDIC <-> ASCII
Conversion
#define U_VERIFIED 0x10000000 // user call back
verified, turn this off,
they get // verified
again.. (if BBS verifies)
#define U_ANSITE2 0x20000000 - User supports Ansi-TE2
Special Chars
#define U_RIPSCRIPT 0x40000000 - User has RIP Support
#define U_AVATAR 0x80000000 - User has Avatar Support
The following flags are used for 'user.attribs2' bits.
#define U2_FSE 0x00000001 - User Full Screen Message
Editor
#define U2_OFF_AFTER_MAIL 0x00000002 - Log off after mail
download
#define U2_MONITOR_MAIL 0x00000004 - Monitor mail
export/packing
#define U2_INT_NEW_FILES 0x00000008 - include new files in mail
packet
#define U2_INC_BULLETS 0x00000010 - include bulletins in mail
packet
#define U2_INC_WELCOME 0x00000020 - include welcome screen in
mail packet
#define U2_DEFAULT_QWK 0x00000040 - Default use to QWK mail
#define U2_DEFAULT_FIDO 0x00000080 - Default use to Fidonet
Point Mail
#define U2_DEFAULT_TEXT 0x00000100 - Default to text export
#define U2_DEFAULT_BLUE 0x00000200 - Default to Bluewave Mail
#define U2_AVTANS 0x00000400 - Can handle both ANSI and
Avatar
#define U2_8DOT3 0x00000800 - Convert long names to 8.3
names
typdef struct _AdeptXBBS_User_Info
{
CHAR name[36]; // Users Name
CHAR handle[36]; // Users Handle
CHAR address[60]; // Address line 1
CHAR address1[60]; // Address line 2
CHAR address2[60]; // Address line 3
CHAR city[20]; // Users City/County
CHAR state[5]; // Users State
CHAR zipcode[10]; // Users ZipCode
CHAR home_phone[21]; // Users home phone number
CHAR data_phone[21]; // Users data phone number
CHAR fax_phone[21]; // Users fax phone number
CHAR bus_phone[21]; // Users business/office number
CHAR interests[78]; // Interest Line
CHAR SysOpComment[78]; // Room for Sysops comment
USHORT banktime; // Time in the bank
USHORT computer_type; // Computer type
LONG userid; // User ID
SHORT pointid; // Point Mail ID
time_t initial_logon; // Time/Date of initial logon
time_t expires; // Time/Date user expires
time_t last_logon; // Time/Date of last logon
time_t logon_today; // Last time the user logged on
today
SHORT birthyear; // Birth Year
CHAR birthmonth; // Birth Month
CHAR birthday; // Birth day
CHAR gender; // Gender
LONG credit; // User credit
LONG minlimit; // Minimum limit
LONG group; // Group number the user
belongs to
LONG currlastread; // Last read pointer for
current area
LONG time_today; // Number of minutes user used
today
LONG time_per_day; // Time limit per day
LONG time_per_call; // Time limit per call
LONG numcalls; // Number of total calls user
made to BBS
LONG ulnum; // Total number of uploads
LONG dlnum; // Total number of downloads
LONG ulk; // Total uploads in K-bytes
LONG dlk; // Total downloads in K-bytes
LONG uktoday; // Uploads in K-bytes made
today
LONG dktoday; // Download in k-bytes made
today
LONG ukperday; // Max k-bytes user can upload
a day
LONG dkperday; // Max k-byes a user can
download a day
LONG numposts; // Number of messages ever
written
LONG security1; // Security level #1
LONG security2; // Security level #2
LONG flags1; // Sysop definable 32 flags
LONG flags2; // Sysop definable 32 flags
LONG attribs; // User attributes
LONG attribs2; // User attributes
SHORT length; // Screen length
SHORT width; // Screen width
SHORT lastmsgarea; // Last message area user was
in
SHORT lastfilearea; // Last file area user was in
CHAR lastprotocol; // Last protocol user chose
CHAR lastarchiver; // Last archiver user chose
LONG forsysop; // unused
CHAR interface; // obsolete
CHAR exp; // unused
SHORT leech_percent; // File leech ratio
SHORT maxbanktime; // Maximum time user can have
in bank
SHORT timecredit; // Current time user has credit
for
SHORT callstoday; // Number of calls user made to
BBS today
LONG totalminsever; // Total minutes users has used
ever
LONG netmaildebits; // Total spent on NetMail
time_t lastpwchange; // Time/Date of last password
change
time_t lastlistednewfile // Time/Date user last listed
new files
ULONG filekcredit; // Amount of file k-byte credit
user has CHAR unixid[8];
// Users Unix Specific ID
UCHAR _unused[94]; // reserved for future use
UCHAR mailtags[128]; // Message areas tagged for
off-line mail
UCHAR usermsg[128]; // Message areas user can
access
UCHAR userfile[128]; // File areas user can access
ULONG passwordcrc; // User password CRC
ULONG passwordcrc2; // User password CRC2
USHORT max_mail_pkt; // Max msgs to pack for off-
line mail
CHAR reasked; // Has user answered the ReAsk
questionairre
CHAR reserved[75]; // reserved for future user
} ADEPTUSER, *PADEPTUSER;
AdeptXBBS Message Base Structures:
*.Data - Structs
typedef struct _AdeptXBBS_Message_Header
{
CHAR MajorVersion; // Minor revision number of this
message style
CHAR MinorVersion; // Minor revision number of this
message style
USHORT StructLen; // The length of this data structure
CHAR from[60]; // Who the message is from
CHAR to[60]; // Who the message is to
CHAR subj[70]; // The subject of the message
CHAR date[35]; // Date the message was written
CHAR indate[4]; // Import date
ULONG msgnum; // Current message number
ULONG timesread; // Number of times the message has been
read
time_t timerecv; // Time user received this message
ULONG length; // Length of message stored in .Text
Data file
LONG start; // Pointer to starting byte in .Text
Data file
ULONG Extra1; // Extra space // Was going to be for
reply
ULONG Extra2; // Extra space // linking instead came
up with
ULONG Extra3; // Extra space // a better method
USHORT o_zone; // Messages origin zone
USHORT o_net; // Messages origin net
USHORT o_node; // Messages origin node
USHORT o_point; // Messages origin point
USHORT d_zone; // Messages destination zone
USHORT d_net; // Messages destination net
USHORT d_node; // Messages destination node
USHORT d_point; // Messages destination point
USHORT cost; // Cost to send this message
USHORT fflags; // Fidonet related flags
USHORT xflags; // XBBS related flags
ULONG iflags; // Internet related flags
ULONG oflags; // Other network related flags
} XMSG, *PXMSG;
Bitmaps For The fflags:
#define MSGPRIVATE 0x0001 /* private message, */
#define MSGCRASH 0x0002 /* accept for forwarding */
#define MSGREAD 0x0004 /* read by addressee */
#define MSGSENT 0x0008 /* sent OK (remote) */
#define MSGFILE 0x0010 /* file attached to msg */
#define MSGFWD 0x0020 /* being forwarded */
#define MSGORPHAN 0x0040 /* unknown dest node */
#define MSGKILL 0x0080 /* kill after mailing */
#define MSGLOCAL 0x0100 /* FidoNet vs. local */
#define MSGXX1 0x0200 /* */
#define MSGXX2 0x0400 /* STRIPPED by FidoNet<tm> */
#define MSGFRQ 0x0800 /* file request */
#define MSGRRQ 0x1000 /* receipt requested */
#define MSGCPT 0x2000 /* is a return receipt */
#define MSGARQ 0x4000 /* audit trail requested */
#define MSGURQ 0x8000 /* update request */
/*----------------------------------------------------*/
Bitmaps For The xflags:
/*------------------------------------------------------*/
/* */
#define MSGDELETED 0x0001 /* deleted message, */
#define MSGANON 0x0002 /* anonymous message */
#define MSGECHO 0x0004 /* unmoved echo message */
#define MSGNET 0x0008 /* unmoved net message */
#define MSGHOLD 0x0010 /* file attached to msg */
#define MSGHOST 0x0020 /* being forwarded */
#define MSGSCANNED 0x0040 /* Fidonet scanned */
#define MSGKEEP 0x0080 /* don't delete */
#define MSGTREATED 0x0100 /* soft cr's & lf's removed */
#define MSGPACKED 0x0200 /* message LZSS compressed */
#define MSGGSCAN 0x0400 /* GroupMail scanned */
#define MSGRSCAN 0x0800 /* rfc0822 scanned */
#define MSGARCHIVED 0x4000 /* Message stored */
#define MSGTAGGED 0x8000 /* used by offline readers */
/* */
/*------------------------------------------------------*/
Structure For The AdeptXBBS Message Base .Index File:
*.Index - Structs
typedef struct _AdeptXBBS_Index_Structor
{
SHORT to; // Checksum of the to field
SHORT from; // Checksum of the from field
SHORT subj; // Checksum of the subject field
LONG // 32-bit CRC of the MSGID
LONG msgidserialno; // MSGID Serial Number
LONG replycrc; // REPLYID 32-bit CRC
LONG replyserialno; // REPLYID Serial Numver
} ADEPTINDEXES, *PADEPTINDEXES;
Structure For The AdeptXBBS File System - File.Data File:
typedef struct _File_Data_Struct
{
UCHAR Name[31]; // File Name
ULONG Size; // File Size
UCHAR User[20]; // Uploader Name (Truncated at 20
chars)
UCHAR Password[13]; // Password required to download file
ULONG Path; // Pointer to path in File.Paths file
ULONG SecLevel; // Min Security level required to
download
UINT Area; // Area this file belongs to
ULONG Flags; // For internal use
ULONG Desc; // Pointer to description in
File.Descriptions
LONG TimesDL; // Times the file has been downloaded
SHORT Group; // Group this file belongs to
SHORT Age; // Min Age Required to download the
file
SHORT Cost; // Cost of the file
FDATE Date; // File Date
} ADPFILESYS, *PADPFILESYS;
----------------------------------------------------------------------
The FileBase uses a commercial, copywritten index that we cannot
distribute the actual code to without charging a fee. Therefore we
have wrapped all the index and FileBase code into a .DLL that allows
complete control over the file system. This .DLL is not complete
finished yet, in fact the BBS doesn't use it yet, only FILEDIT does.
From these structures you could at least get needed info from the
FileBase system.