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

Text File | 1990-11-10 | 9.6 KB | 247 lines

<defaults!>
C:\XBBS\MESS\
C:\XBBS\MESS\MSGAREAS.XBS
C:\XBBS\MESS\MSGAREAS.BAK
C:\XBBS\FLSEARCH.CTL
C:\XBBS\FLSEARCH.BAK
<startup   >
Pick one of these formats.  If you choose Protocol.CTL
or Peeker.CTL, you'll need to be in the directory where
the file resides.  For Message and File area files, you
can specify a path (since you can have more than one).
Note that when editting the .CTL files, you no longer
have to run XPROTO or XPEEK on a text file:  this works
on the compiled binary.  Much easier.

XEdit can make file area and message area menus up for
you, too.  Just edit the appropriate file ([M]sg or
[F]ile), select an area to edit, then press the key
indicated on the area-edit screen (F4 for files, F6
for msgs).  When asked for the security level for file
area access, enter a number from 0-9.  Then XEdit will
automagically build you a menu.

Hit ESCape if you want to quit.

If you're just running HeadEdit, the only thing you need
to be concerned with is the message area file.  Don't
worry about making any menus, either; they're only for
XBBS.
<msgarealis>
Place the reverse video bar on a message area and press
[Enter] to select that area for editting.  You can put
the bar on "   -=Jump direct to an area #" and press
[Enter] to input a number directly.  ESCape will get you
back out of here.
<fileareali>
Place the reverse video bar on a file area and press
[Enter] to select that area for editting. ESCape will
get you back out of here.
<protolist >
Place the reverse video bar on a protocol entry and press
[Enter] to select that area for editting. ESCape will get
you back out of here.
<arclist   >
Place the reverse video bar on an archiver entry and press
[Enter] to select that area for editting. ESCape will get
you back out of here.
<areas     >
Enter an area number at this prompt and you will be
taken directly to that area number for editting.
<msgname   >
This is the name you want to call this message area.
<msgforce  >
This is the name, if any, you want to have messages
"forced" to be entered to.
<msgmax    >
This is the maximum number of messages you want to
keep in this area.  This only has effect in non-Matrix
areas.
<msgnumber >
This is the area's number.
<msgsub1   >
In Bulls-mode, this is the number that the user's
security level #0 must be equal to or greater than
in order to gain access to this area.  It is used in
conjunction with the next field to determine subop
status.
<msgsub2   >
If the user's security level #1 is equal to or
greater than this, and the criteria for the preceding
field is also met, the user has subop status.
<msgattr   >
These are the msg area's attribute bits:
 NoOrigin (no origin or tear in echo area--use with care!)
 ANSI Graphics area
 Private msgs ok
 Public msgs ok
 Echo area
 Netmail area
 MCI commands active
    MCI is a way for users to enter some of the more harmless special
    print routines that you have available as SysOp in the text files.
 ReadOnly area--only subops may post
 Alternate netmail area
 Alternate echo area
 Anonymous msgs ok
 Real Names required
 Associated (with file area)
 External (Extra prompt appears)
 Force: causes message to be forced even in Bulls-mode.
 Compress (LZSS compress msg text)
<msgfile   >
This is the filename of the file that you want to edit.
<msgpath   >
This is the fully qualified path to where your message
base files are kept.
<msgbackup >
This is the backup file (if any) you want to make/keep.
<filefile  >
This is the filename of the file that you want to edit.
<filebackup>
This is the backup file (if any) you want to make/keep.
<filename  >
This is the name of this file area.
<security  >
This is the minimum security level for this area.
<download  >
This is the fully qualified path to this area's download section.
<upload    >
This is the fully qualified path to this area's upload section.
<fileattr  >
These are the file area's attribute bits:
 Track number of downloads by timestamp
 Free download file area (d/l's not counted against user)
 Associated (with message area)
 Free upload file area (no credit given)
<protoname >
This is the name the user will see for this protocol.
<protokey  >
This is the keypress that will select this protocol.
<protoadj  >
This is the "adjustment factor" for this protocol.  Generally, the lower
the number, the slower the protocol.  You might try ZModem at about 85
and XModem at about 65 to get started, then adjust based on observation.
<protodn   >
This is the string that XBBS spawns to perform a download with this
protocol.  *F is replaced with filenames where found.  The line below
this one is a continuation of this string.
<protoup   >
This is the string that XBBS spawns to perform an upload with this
protocol.  *F is replaced with filenames where found.  The line below
this one is a continuation of this string.
<protodn1  >
This is the string that XBBS spawns to perform a download with this
protocol.  *F is replaced with filenames where found.  This is a
continuation of the line above.
<protoup1  >
This is the string that XBBS spawns to perform an upload with this
protocol.  *F is replaced with filenames where found.  This is a
continuation of the line above.
<protoabort>
This is the string that completes "...or " <string> " to abort"
<protowild >
Put an X here if the protocol accepts wildcarded (?*) filenames.
<protomulti>
Place an X here if the protocol accepts multiple filenames
(separated by a space).
<protosimul>
This shouldn't be used.
<protolist >
Place an X here if the protocol supports @List files *and* you want
to use them.
<protoopus >
This shouldn't be used.
<protononam>
Put an X here if you don't want the user to have to enter filenames
before an upload.  Not really recommended.
<protodsz  >
Put an X here if the protocol maintains a DSZLOG-style log.  Note that
you must have the environment variable DSZLOG set to a string that
includes the string "DSZLOG" (i.e. SET DSZLOG=C:\XBBS\DSZLOG.LOG)
<protoreser>
Not currently used; shouldn't be set.
<arcaname  >
Name of the archiver program that creates this type of archive, complete
with extension (as it's listed in your directory).
<arcename  >
Name of the archiver program that extracts from this type of archive,
complete with extension (as it's listed in your directory).  Example:
ZOO.EXE
<arcext    >
File extension associated with this type of archive.  Note that you can
list a protocol more than once with different extensions (like both ARC
and PKA for PK(X)Arc).
<arclist   >
Command that lists the archive to the screen (stdout), like
ZOO.EXE v
Note that for all commands you should include the "nopause parameter"
(/WA with PAK, /m with LHARC, etc.) so that the archiver doesn't "hang"
waiting for local keyboard input on an error.
<arcmove   >
Command that Moves files into the archive (adds them to the archive and
then deletes them) like PAK.EXE M
<arcextract>
Command that extracts files from this archive, like PKXARC.EXE
<arcerror  >
String that is displayed when an attempt is made to list a file that
isn't an archive.
<arcid     >
This is the string displayed to the user when asking them to pick how to
repack extracted files (i.e. [A]rced).
<arcpick   >
This is the key that will select this archiver for repacking.
<arcskip   >
This is how many lines to skip when reading in the list file created by
redirection.  Usually you'll want to skip the first few "advertisement"
lines, though you don't have to do so.
<arcerrline>
This is the line that the errorstring usually appears on.  You can fudge
this number high if you want to.
<msgdescr  >
This is the description that XBBS will use when you list msg areas with
@&L...
<filedescr >
This is the description that XBBS will use when you list file areas.
<fileseclvl>
This is the XBBS security level # (0-9) that you want
me to use when making up one of the automagic menus.  The
msg menu needs to know this for looking up name-matching
file areas for Association.
<fileage   >
XEdit uses this only for making up the sample file area menu.
It is *not* saved with the file area file.  If you have a large
block of areas that are age-protected, you should probably have
two entry points.  If the age is positive, users under the given
age will not have access to the area.  If negative, users over
the given age will not have access.
<msgage    >
XEdit uses this only for making up the sample message area menu.
It is *not* saved with the message area file.  If you have a large
block of areas that are age-protected, you should probably have
two entry points.  If the age is positive, users under the given
age will not have access to the area.  If negative, users over
the given age will not have access.
<leech%    >
This field determines what u/d ratio (if any) XBBS will enforce
for this area.  Leave it blank if you don't want to enforce one,
or if you'd rather do it yourself with @LK/@L#.
<minwrite  >
This field determines what minimum access in security level
#0 is required before the user has write access.  Leave it 0
if you don't give a damn.
<fileflags >
This field is a bitmap corresponding to the user's attr2
(flags) field.  If a bit is set (X), the user must also have
that bit set to get access.
<msgflags  >
This field is a bitmap corresponding to the user's attr2
(flags) field.  If a bit is set (X), the user must also have
that bit set to get access.
<end>
Note that the defaults after <default!> at the top of this
file can be editted to your taste.  The first line is the msg
area path, the second is the msg area file, the third is the
msg area backup file, the fourth is the file area file, and the
fifth is the file area backup file.