ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng)/ProfitPress-MegaCDROM2.B6I/BBS/MISC/XEXE_117.ZIP/XCONFIG.HLP

Text File | 1990-06-28 | 20.1 KB | 595 lines

<name      >
Enter the name of the user
(First and Last name!)
<handle    >
Enter the user's handle,
or his repeat his name.
<city      >
Enter the name of the city
in which the user resides.
<state     >
Enter the 2-letter abbreviation
for the user's home state.
<zip       >
Enter the 5-digit postal
zipcode for the user's address.
<phone1    >
Enter the user's verification
(home) phone number.
<phone2    >
Enter the user's secondary
telephone number.
<length    >
Enter the user's terminal length
(the number of lines vertically
 on his screen).
<width     >
Enter the user's terminal width
(the number of columns horizontally
 on his screen).
<credit    >
Enter the user's credit
in cents for netmail.
<stat0     >
Enter the user's security level #0
(prime security).  If this level is
set to 0, the user is Locked Out.
<stat1     >
Enter the user's security level #1.
Security levels #0 and #1 are used
to determine subop status in message
and file areas.
<stat      >
Enter the user's security level for
each security level you use.
<calls     >
Enter the number of calls the user
will be allowed to make per day.
<time      >
Enter the minutes a user can spend
on a single call.
<total     >
Enter the total time a user can
spend online per day.
<namep     >
This is the first prompt the user sees
after your logon message.  It should
ask for his Real Name.
<handlep   >
This prompt should ask the user if he
wants to use a Handle instead of his
Real Name.  If you don't want to allow
Handles, leave this blank.  Note the
question defaults to No Handle if it
is answered by the user with [Enter].
<phone1p   >
This prompt should ask for the user's
verification, or home phone number.
<phone2p   >
This prompt should ask for the user's
secondary phone number.  This could be
the user's business phone, or the
number he's calling from if you want to
check for a busy signal on another line
as "instant verification".
<zipp      >
This prompt should ask for the user's
five-digit postal zip code, though you
could use it for other purposes if you
have other purposes for a five-digit
number...
<lengthp   >
This prompt should ask the user the
number of vertical lines he has on his
screen.  The number must be between
10 and 66; you should mention this.
<widthp    >
This prompt should ask the user the
number of horizontal columns he has on
his screen.  The number must be
between 32 and 80, so let him know
here to avoid confusion.
<cityp     >
This prompt should ask the user to
input his city.
<statep    >
This prompt should ask the user to
input his two-digit state code.
<ansip     >
This prompt should ask if the user
wants ANSI color/graphics.  The
question defaults to No ANSI if the
user answers with [Enter].
<ansiedp   >
This prompt should ask if the user
wants the Full Screen ANSI editor to
be the default.  If you aren't using
a Full Screen Editor, leave this blank.
The question defaults to No FSE if the
user answers with [Enter].
<birthp    >
This prompt should ask the user what
his birth date is (in the format
MM/DD/YYYY).
<passp     >
This prompt should ask the user for
the password they would like to use on
your system.  Minimum three characters,
maximum of twelve, Case Sensitive.
<specp     >
This is the only flag that XBBS will
set for you at logon.  Its meaning is
up to you.  You could use it to flag
a certain computer type, SysOps of other
boards, or whatever you can imagine.
The flag will be set if the user answers
Yes to this prompt.
<scrnclrp  >
This prompt should ask the user if he
wants to suppress screen clearing codes.
If the user answers Yes, no screen clear
codes will be sent; otherwise, they are.
<pagep     >
This prompt should ask the user if he
wants to suppress page pausing.  A Yes
answer will stop the More? prompt from
appearing.
<toonamep  >
This message is displayed to users who
reenter their name more times than you
have allowed, before disconnecting.
<toopassp  >
This message is displayed to users who
botch their password more times than
you have allowed, before disconnecting.
<badp      >
This message is displayed to users when
their phone number is found in
PHONECAN.CTL, before disconnecting.
<lockp     >
This message is displayed to users if
they are locked out (security level #0
is 0), before disconnecting.
<local     >
Answer 'Y' or 'N' depending on whether you
want automatic logon when in local mode
using account #1 (SysOp)
This function is not currently supported.
<loglim    >
How many minutes do you want to allow for
login?  This should give new users enough
time to complete the application.  Generally,
seven minutes is plenty.
<namea     >
Determines the number of times someone can
enter their name when trying to log on.
After the set number of times, they get a
message and are disconnected (see Logon
Prompts).
<passa     >
Determines the number of times someone can
incorrectly enter their password when trying
to log on.  Can dissuade "hackers".
<minbaud   >
This will be the minimum baud rate you
permit on your system.  Anyone at a lower
baud rate will be read the TOOSLOW.XBS file
and disconnected.  Enter 300 if you want to
let everyone in regardless of modem speed.
<net       >
This space is for your Net or Matrix
addresses.  If you have not been assigned
an address by your Net Coordinator, set
all these to 0.  The documentation for your
Mailer should explain more about this, and
there are guides to getting started in the
Matrix available on most Matrix boards.
Find your local Net Coordinator/Host if you
want more information.
<netboard  >
This is the number of the board that will
have net mail "tossed" into it from inbound
packages addressed to your primary node
address.  Enter 0 if you aren't involved in
the matrix.
<altboard  >
This is the number of the board that will
receive net mail addressed to your alternate
node address.  Enter 0 if you aren't using
an alternate address.
<homepath  >
This is the path where your BBS files (like
these configuration files) are stored.  Be
sure to include fully qualified pathnames here.
Be sure all the directories you specify here
actually exist.  If you do not know how to
create a subdirectory, please throw XBBS away
and get something easier to use.
<mailpath  >
This is the path where your net mail files
are temporarily stored before being mashed
into the outbound directory as packets.
<filepath  >
This is the path to your incoming mail files.
<menupath  >
This is the path to your "menu" files (the
text files that end with ".XBS" or ".GBS").
You can store other text files here, too.
If you use the XMenu version of XBBS, you'll
need a subdirectory off of this one called
MNU (i.e. C:\XBBS\MENU\MNU if you assign
C:\XBBS\MENU for this option)
<messpath  >
This is the path to your message base files
(XDATA.### and XTEXT.### files).
<outpath   >
This is the path to your Outbound or Holding
directory, where oMMM or similar masher puts
your outgoing mail.
<sysop     >
This should be your name (or handle).
<system    >
This should be the name of your BBS.
<logfile   >
The fully qualified pathname to your
logfile (i.e. C:\XBBS\XBBS.LOG)
<edline    >
The string to Spawn to get your Line
Editor for the user.  Metastrings work.
<edansi    >
The string to Spawn to get your ANSI
Full Screen Editor for the user.
Metastrings work (see Help @ Shells)
<edlocal   >
The string to Spawn to get your Local
Editor for local users.  Metastrings
work, but you probably won't need them.
<lastcaller>
The name of the last caller on the
system.
<sysopin   >
Are you available for chat requests?
<ansiavail >
Are ANSI color/graphics sequences
available on your system to outside
callers?  Requires ANSI.SYS or an
equivalent device to be loaded as an
installable device driver on the user's
system.  ANSI.SYS or equivalent must
always be loaded on your system.
<idlesecond>
How many seconds can a user be idle
(not hit a key) before the system will
get tired of him and disconnect?
<pages     >
How many times can a user page you in a
call without you answering him?
<touchup   >
If you answer Yes to this, XBBS will "fix"
filedates from protocols like ZModem that
preserve the file date on a file so that
the file's date reflects the current date.
This is so new uploads are known to be new.
Generally this is a good thing to do as most
files are archives, and the original file
date of each file in the archive is still
preserved.
<startat   >
Determines how many files a user must
have downloaded before U/D Ratio
enforcement will take affect.  This
lets the user get a "head start" on
downloading, so he doesn't "start off
behind".
<debug     >
Answering Yes to this will enable
XBBS's limited debug mode, which will
leave you a few notes in the logfile
when external programs are called,
errors occur, etc.  Set this to Yes at
least until you're sure everything is
working right.
<uptime    >
If you answer Yes here, XBBS will stop
the clock while users are uploading.
<downtime  >
If you answer Yes here, XBBS will stop
the clock while users are downloading.
<callcount >
This is the number of calls that have
been made to your system.  If you're
switching software, you may want to set
this to the number of calls that had
already been received with your old
software.
<commport  >
This is the number of the commport that
your modem is hooked to.  Enter 0 if
your modem is on COM1, 1 if it's on
COM2, etc.
<fname     >
This is the name of your default file
area.  This field may not include commas.
<dpath     >
This is the fully qualified path to
files available for download from the
default file area.  If you don't understand
what a pathname is, please throw XBBS away
and get something simpler.
<upath     >
This is the fully qualified path where
files uploaded to the default area
will be stored.  It can be the same as
the download path.  All file areas may
share a common u/l path, or it can be a
different path for each file area.
<attributes>
These attributes are either on (X) or off
(-).  Please note that the names given for
these attributes are not necessarily set
in stone; XBBS will allow you to use them
for other purposes.
<max       >
The maximum number of messages you want to
keep in this area.  Old messages will be
automatically deleted to make room (does
not apply to Matrix areas).  Can be 1 to
65534.
<number    >
The number associated with this area (for
naming conventions with XDATA and XTEXT
files).  Can be 1 to 999.
<forceto   >
This field can be used to force a message
to a particular user (usually the SysOp).
<mname     >
The name of this message area.  Do not
include commas in this field.
<private   >
Answer Yes if you want to allow private
messages to be entered in this area.
<public    >
Answer Yes if you want to allow public
messages to be entered in this area.  Both
public and private can be allowed in the
same area.
<origin    >
The default origin line for Echo Mail.
Do not include your node number; it is
automatically added.  Do not include the
*Origin: prefix.
<real      >
If you want message headers to be "from"
Real Names only in this area, answer Yes
to this.  It isn't necessary if you aren't
allowing Handles anyway...
<substat1  >
A user must have at least this security level
for Security Level #0 to be considered a
subop in this area and be able to delete
messages not posted by or to him.  He must
also meet the minimum for Security Level #1
below.
<substat2  >
A user must have at least this security level
for Security Level #1 to be considered a
subop in this area and be able to delete
messages not posted by or to him.  He must
also meet the minimum for Security Level #0
above.
<nett      >
Answer Yes if this area is your Net Mail board.
<echo      >
Answer Yes if this area is an Echo conference.
<alternate >
Answer Yes if this area is your Alternate Net
Mail board.
<readonly  >
Answer Yes if only the SysOp and subops can post
in this area.
<fflags    >
Answer Yes if you want XBBS to use the file time
stamp to track the number of times the file has
been downloaded.
<numcomps  >
The number of computer types you are tracking,
0-255 (related file: COMTYPES.XBS)
<edgraph   >
This is the string to invoke your ANSI color/
graphics editor.  This is for entering messages
with ANSI graphics commands in the message proper:
Do not confuse this with the full screen editor!
Metastrings work.
<dvideo    >
Answer Yes if you want direct screen writing
(the fastest method) used for the status line
and when reading non-ANSI message text.  Answer
No if you want to use BIOS routines instead.
<comments  >
Determines the number of lines of comments a
user can input when a file is uploaded.  Must
be between 1-255.
<bioswrites>
If you have something like FANSI installed that
will interpret BIOS writes like ANSI interprets
DOS writes, answer Yes to this.
<purge     >
XBBS will purge the outbound FOSSIL buffer
after a line is sent if the connect is at this
speed or slower.
<genphone  >
XBBS normally forces phone numbers into U.S.A.
standard 10 digit (Area_Code)Prefix-Suffix format.
If you don't like that, or it isn't applicable to
the area where you live, set this to Yes.  XBBS
will then accept input of any length (up to 10
chars) in any alphanumeric format.
<freefiles >
Answer Yes if you want files in this area to be
"free" (i.e. the user's download counters will
not be incremented if a file is downloaded from
this area).
<nodelist  >
This is the path to your nodelist file(s).  XBBS
uses a QuickNodeList, same format as QuickBBS uses.
<swap      >
XBBS can swap itself out to disk or EMS during
Spawns.  If you use EMS or a RAMdrive, this can
be very fast and free memory for things like
multitasking.  Place a Y here if you'd like to
have XBBS swap itself.  (Swap courtesy of Turbopower)
<swapdrive >
This is the drive where you want XBBS to create
its temporary swap file.
<ems       >
If you have EMS installed and would like XBBS to
swap itself here instead of to disk, put a Y here.
<ansibaud  >
This will be the minimum baud rate required to
turn ANSI graphics on.
<promptsay >
Answering Y here will cause XBBS to print the number
of the XBBS.?XT prompt being currently used, for
debugging purposes. You'll normally want to leave
this off.
<genstatezi>
Answering Y here will cause XBBS to treat the state
and zip fields in the user's file as a generic eight
byte string.  This may be more useful for use in
countries outside the USA (see also Generic Phone).
<numcarbons>
Put a 0 here if you don't want to allow carbon copies.
Otherwise, put a number from 1 to 9 to determine the
maximum number of carbons copies that can be sent from
one original message.  Carbons create multiple copies
of the header (about 190 bytes); the msg text is stored
only once.
<share     >
Put a Y here if you're multitasking.  This will enable
XBBS' file locking of regions of the message bases
during writing.  Running with this on and without
SHARE.EXE or equivalent will cause errors.
<jumpfiles >
Goto files are .XBS files which will be started up as
a Startfile (all gosubs will be cleared out) when the
user presses the associated key at any point when XBBS
is checking for a keypress except when memory is
temporarily allocated (as when reading a message or in
Bulls-mode). You do not have to use Goto files.  If
you do, they can be temporarily disabled (see @$).
If you opt to use one or more Goto files, do _not_
leave gaps (i.e. use file #1 and file #3).  XBBS stops
checking when it gets to a blank file.
<jumpkeys  >
This is the key that will activate the associated Goto
file.  Control keys and ALT-keys can be used.  ALT-keys
return their second scan code value+128 (i.e. ALT-Y
would return 25+128 or 153).  Remember that a remote
terminal might have trouble sending ALT-keys (an ASCII
0 followed by the scan code in ASCII) if it's not
flexible enough.  Also, several ALT-key combinations
are reserved by XBBS and won't be useable for this
purpose locally (like ALT-J, ALT-Y, F1-F10, etc.)
You can enter control keys by holding down control and
pressing the corresponding key (steer clear of keys
like CTRL-G, CTRL-H, and XOn and XOff).  You can enter
ALT keys by depressing the ALT key and typing the
number of the converted keypress (scan code+128) on the
numeric keypad.
<subfiles  >
Gosub files are .XBS files which will be started up as
a subfile (i.e. an @q will return to where you were)
when the user presses the associated key at any point
when XBBS would be checking for a hot keypress during a
menu. It will not check at other times.  You do not
have to use Gosub files.  If you do, they can be
temporarily disabled (see @$).  If you opt to use one
or more Gosub files, do _not_ leave gaps (i.e. use file
#1 and file #3).  XBBS stops checking when it gets to a
blank file.
<subkeys   >
This is the key that will activate the associated Gosub
file.  Control keys and ALT-keys can be used.  ALT-keys
return their second scan code value+128 (i.e. ALT-Y
would return 25+128 or 153).  Remember that a remote
terminal might have trouble sending ALT-keys (an ASCII
0 followed by the scan code in ASCII) if it's not
flexible enough.  Also, several ALT-key combinations
are reserved by XBBS and won't be useable for this
purpose locally (like ALT-J, ALT-Y, F1-F10, etc.).
Don't use CTRL-T, which is XBBS' special help key.
<nolmrs    >
This determines how many Last Message Read pointers XBBS
will keep in the message path(s).  Each pointer requires
two bytes/user.  This number isn't easy to change, so the
best thing to do is set it to about 1-1/2 times what you
think you'll need to allow for some expansion.  Valid
entries are from 50-4095.
<coldinput >
Answering Yes here will make XBBS treat most input that
would normally be "hot" (no [Enter] key required) as
"cold" for the user (switchable default).  You can get
around it where you want to by passing 2 instead of 1 as
the hot parameter in a @<#>I input (see @0...@9 in XBBS
docs).
<logmenu   >
Answering Yes here will cause XBBS to make a note in the
logfile every time a menu file is started.  This can be
handy for debugging or seeing which areas of the BBS are
getting attention and which aren't.
<logfiles  >
A Yes here will cause XBBS to make a log entry every time
a FILES.BBS-type file is listed.
<logtext   >
Putting a Y here tells XBBS to make a note in the log every
time a user reads a file with the "paged-reader".
<logmsg    >
A Yes here will cause XBBS to make a note in the logfile
when files are read or extracted in/from an area.
<fastansi  >
A Yes here will cause XBBS to use INT 29h to print through
ANSI.  This can be a little faster on some systems, but is
incompatible with others, so try before you buy...
<menu      >
Welcome to XBBS.  Go through this
menu (use your cursor keys and the
[Enter] key) and fill out each window.
When you're finished, use "EXIT AND
SAVE" to create CONFIG.BBS in the
default directory.
<domain    >
This is the Domain your primary
address is in (usually FidoNet).
Domains are required, so if you
don't know it, find it out.
<altdomain >
This is the Domain your alternate
address is in.  Domains are required.
<filemsg   >
Answering Y to this will make XBBS force
the user to leave a descriptive message
about uploaded files if you have an
Associated msg area set up
(see docs).
<nextid    >
This is the next unique user
number that XBBS will assign.
<packsize  >
This is the minimum amount of text a msg
must contain before packing (compression
of msg text) will take place (and then only
if the msg area has the COMPRESS attribute).
Don't set it too low (recommend 2048 bytes).
<helpkey   >
This is the key XBBS will use for the automatic
help system.  When the user presses this key
and help is available, he'll get the opportunity
to view it.  This should *not* be a key that you
will use during normal input or for gosub/goto
files!  CTRL-T is the default.
<RBBSorQBBS>
Set this to Y if you want XBBS to create an
RBBS-style DORINFO?.DEF exit file.  Try both
to see the difference.
<end>