1055 lines
42 KiB
Plaintext
1055 lines
42 KiB
Plaintext
-------- Continued from previous message --------
|
|
PART 7
|
|
|
|
*********************************************************************
|
|
CHAPTER 5 - BBSing WITH AMIGA
|
|
**********************************************************************
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
AMIGA COMMERCIAL BBS SOFTWARE
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
5.01 - AmiExpress
|
|
5.02 - BBX
|
|
5.03 - CNet Amiga
|
|
|
|
============================================
|
|
5.04 - DLG Pro. v1.0 (Dialog Professional)
|
|
============================================
|
|
|
|
FEATURES
|
|
---------
|
|
* up to 65000 users
|
|
* 255 different user levels
|
|
* 9999 different message areas
|
|
* 9999 different file areas
|
|
* number of BBS lines is limited only by serial port availability
|
|
* all text strings and ANSI colors are completely definable by
|
|
the sysop
|
|
* string sets are available in several languages
|
|
* each user can choose what language he wants to use for his
|
|
session
|
|
* custom international character mapping is supported
|
|
* 7/8 bit character transparency is configurable
|
|
|
|
Not all of DLG is built big, though. DLG was also designed to work on
|
|
even modest Amiga setups. Here are the facts:
|
|
|
|
* DLG's modular, disk based operating system design allows for
|
|
low memory usage
|
|
* DLG uses from 40-150K per active BBS line depending on setup
|
|
and usage
|
|
* low CPU usage for excellent performance on multiple lines
|
|
* works with as little as 512K of system memory
|
|
* works on Amiga 500, 1000, 2000, 2500, and 3000 under AmigaDOS
|
|
1.3 & 2.0
|
|
* works with even modest Hard Drive setups.
|
|
|
|
USER PREFERENCES
|
|
-----------------
|
|
Each DLG user can set a number of preferences for his on-line
|
|
session:
|
|
|
|
* help level (novice / intermediate / expert)
|
|
* screen length and width settings to match his terminal software
|
|
* optional MORE prompt for paced system output
|
|
* ANSI colour, smart ANSI screen positioning, screen clears, and
|
|
partial screen scrolling are all definable independently
|
|
* optional hot keys for fast single letter command input
|
|
* preference settings for personal upload/download protocols
|
|
* choice of message editors
|
|
* automatic command sequence (command stack) to be executed at
|
|
login
|
|
* alias name (handle)
|
|
* create and edit personal signatures (4 types) to be
|
|
automatically appended to messages and file descriptions
|
|
* create lists of message and file areas to search
|
|
* custom menu sets with different BBS languages attached to them
|
|
* custom character maps
|
|
|
|
CONFERENCES
|
|
-------------
|
|
In addition, there are a number of DLG features that users find
|
|
helpful:
|
|
|
|
* online user manual and help text files for individual commands
|
|
* full user list and search capabilities
|
|
* list of important events since last call - list is kept for
|
|
each user while he is off-line
|
|
* list of waiting public mail is kept for the user and marked for
|
|
easy retrieval at login
|
|
* ability to see who is on other BBS lines and what they are
|
|
doing
|
|
* ability to send online messages to users on other lines
|
|
* smart menus that show only those commands the user can actually
|
|
use, moment to moment
|
|
* fully customizable smart menu displays that allow the SysOp to
|
|
be creative with his menus
|
|
* quote of the moment module
|
|
* today in history module
|
|
* quick and easy searching for new messages and files
|
|
|
|
MESSAGING
|
|
------------
|
|
Here are some features of DLG's full online public/private mail
|
|
system:
|
|
|
|
* powerful, full-screen free-form ANSI based message editor
|
|
* free-form paragraph oriented message editor with query search and
|
|
replace and the ability to back up over lines using a standard
|
|
terminal program
|
|
* use of an external Amiga message editor/word processor is allowed
|
|
from a local session
|
|
* support for third-party online editors
|
|
* up to 9999 separate message areas
|
|
* users can automatically scan the areas they choose for new messages
|
|
* messages can be packed up and archived in the background while the
|
|
user does other things online, or the user can start the mail
|
|
packing and pick it up on a future call to the system
|
|
* users can edit their own custom message and file signatures
|
|
* message header scan with message TTagging' is supported to quickly
|
|
scan for messages in large message areas
|
|
* a smart message thread reading mode can be enabled to automatically
|
|
follow conversations as you read
|
|
* continuous read mode with optional ANSI/more-prompt disable
|
|
* ability to continuous read all areas at once
|
|
* active readers of an area can be listed
|
|
* individual privileges can be assigned to each user in each area
|
|
separately, or automatically assigned based on user level
|
|
* users are informed of all types of mail received
|
|
* users can kill their own messages depending on access
|
|
* maximum number of messages allowed in each area can be set
|
|
* messages can be renumbered at any time
|
|
* message areas can be searched based on who the messages are from,
|
|
who they are addressed to, or on the subject line of the message
|
|
* messages can be forwarded and transferred from public, to private,
|
|
to UUCP, to Newsgroups, to NetMail, to EchoMail or any combination
|
|
of the above
|
|
* messages can be re-edited by their author or by users with SysOp
|
|
access in the message area
|
|
* messages can be Lex checked and analyzed for readability
|
|
* messages can be sent to online group mailing lists
|
|
* translated message areas can be created with the help of PD novelty
|
|
programs such as Jive, ValSpeak etc.
|
|
* message areas can be set to have inappropriate language
|
|
automatically filtered out of messages as they are saved
|
|
* each user has a private mail directory
|
|
* user can keep a carbon copy of private mail sent
|
|
* message reading in forward and reverse directions
|
|
* private mail traffic can be monitored by the sysop
|
|
* messages can be automatically sent by the system or from batch
|
|
files using the off-line message sending module
|
|
|
|
FILES
|
|
------
|
|
Features of DLG's online file system:
|
|
|
|
* up to 9999 file areas are supported
|
|
* validated uploads are supported so that files may be checked by the
|
|
SysOp before they are made available
|
|
* each user's access can be tailored individually for each file area
|
|
or defaults can be set for each area based on user level
|
|
* full file searching of all available areas with wild card support
|
|
files can be searched by name, date, range of dates, since last
|
|
call, since number of days, or by description
|
|
* files can be sorted by natural forward/reverse, or alphabetical
|
|
forward/reverse
|
|
* users can easily scan file areas they wish to monitor for new files
|
|
* each file can have up to a 32K description
|
|
* users can add comments to existing file descriptions to aid others
|
|
with their downloading decision
|
|
* choice of quick or verbose listing of all files in an area
|
|
* users can kill files that they upload if their access permits
|
|
* trash-can-like directory saves deleted files as a backup against
|
|
accidental or unwanted deletions
|
|
* uploader's custom file signature is applied to file descriptions
|
|
* archive content viewing supported for any archiver with that ability
|
|
* protocols are completely configurable to allow the use of external
|
|
file transfer protocols (XPR) and DLG-compatible protocols
|
|
* custom Xmodem (Checksum / CRC / 1K) and Zmodem protocols included
|
|
* super fast Zmodem transfers that auto adjust to the CPU and current
|
|
load conditions to give optimum performance without 'bogging' the
|
|
rest of the system down
|
|
* files can be uploaded to another user's private directory
|
|
* users can have size limits placed on their private directories
|
|
* batch uploads are supported for appropriate protocols
|
|
* partially uploaded or downloaded files can be resumed at a later
|
|
date
|
|
* files can be Ttagged' for batch download using appropriate protocols
|
|
* partial 'tagged list' and 'partial file' downloads are supported
|
|
* a tagged file list is retained from call to call and is not deleted
|
|
until the user does so, or downloads the files it contains
|
|
* user can list and edit his tagged file list
|
|
* DLG supports upload / download ratios
|
|
* individual files can be marked as FREE and will not count on ratios
|
|
* default protocol can be set, or can be selected at time of download
|
|
* optional auto-log-off after download (5 second bail out)
|
|
* files can be transferred from public to public, private to private,
|
|
private to public or public to private
|
|
* file descriptions indicate number of times downloaded
|
|
* files show approximate download time based on protocol efficiency
|
|
* protocols are definable and defaults are selectable by the user
|
|
* SysOp can upload and download from a local session
|
|
* sysop can have up to 127 global file paths where files from any
|
|
section can be stored
|
|
* CD Rom drives are fully supported with the use of alternate and
|
|
global paths
|
|
* ADS file areas are supported with the use of third party 'tick'
|
|
programs
|
|
|
|
FIDONET
|
|
---------
|
|
* Includes TTrapdoor' - the Amiga's premier network mailer
|
|
* high speed nodelist compiler
|
|
* cost and call accounting
|
|
* ZedZip, ZedZap, DirectZap, Dietlfna and FTS-1 protocols
|
|
* FTS-1, FTS-6 and EMSI handshaking
|
|
* four dimensional addressing
|
|
* supports AKA's
|
|
* FidoNet - Echomail and Netmail areas are fully integrated into the
|
|
message system
|
|
* separate origin lines can be defined for each Echomail area
|
|
* support for multiple domains, multiple networks, multiple zones
|
|
* can feed points
|
|
* automatic dupe elimination
|
|
* supports all known types of mail bundling
|
|
* extensive routing capabilities
|
|
* can be used for hubbing or in network coordinator positions
|
|
* echo area traffic reports
|
|
* incoming Netmail is sent to the users' private mail directory for
|
|
assured reception
|
|
* full cost implementation allows charging for Netmail via a user
|
|
account credit system
|
|
* users are informed of incoming Echo/Netmail in real time if they are
|
|
online, or via their event log if they are not
|
|
* support for outgoing file attaches and file requests
|
|
* can accept file requests from other systems
|
|
* a list of requestable 'magic file names' can be created with
|
|
optional password protection
|
|
* file areas can be designated as File Requestable
|
|
* crashmail is supported
|
|
* can zonegate FidoNet messages
|
|
* can receive and send/reply to point systems
|
|
* full nodelist support
|
|
* echomail is imported in the background while even users are reading
|
|
the areas receiving mail
|
|
* incoming Netmail mail can be addressed to online group mailing lists
|
|
* is capable of running as a point
|
|
|
|
DLG Professional includes everything you need to set up a FidoNet
|
|
system.
|
|
|
|
DLG & USENET
|
|
-------------
|
|
* Each user has their own personal UUCP account
|
|
* UUCP mail can be received in a user's private directory
|
|
* UUCP mail can be entered by any user with the proper access
|
|
* UUCP messages can be replied to with one easy key-stroke
|
|
* UUCP mail can be sent to online mailing lists
|
|
* UseNet newsgroups are treated as normal DLG message areas
|
|
* UUCICO accounts may be set up to allow the system to provide UUCP
|
|
feeds to other sites
|
|
|
|
PEOPLETALK
|
|
------------
|
|
Message and file area support is standard for most Bulletin Board
|
|
System software. DLG adds to that the excitement of PeopleTalk -
|
|
multi-user real time conferencing. Here are some features of
|
|
DLG's PeopleTalk system:
|
|
|
|
* users can create rooms at any time
|
|
* minimum baud rate and user level can be set for each room
|
|
* people can view users in a room
|
|
* users in conference can send private messages to others in the same
|
|
room
|
|
* system wide message broadcast upon room creation
|
|
|
|
CONTROLS
|
|
----------
|
|
DLG has powerful options for SysOp control of the entire system:
|
|
Here are some features:
|
|
|
|
* a full point and click install program will have you up and running
|
|
within minutes 47 different attributes of each user can be edited,
|
|
including:
|
|
* user level which determines access to auto-access message and file
|
|
areas, and to menu command selections
|
|
* daily and session time limits
|
|
* time used today
|
|
* 'K' uploaded / downloaded
|
|
* upload / download ratio
|
|
* netmail credit
|
|
* bulletin write access
|
|
* UUCP write and client privileges
|
|
* definable archivers that users can select for mail packing and the
|
|
system can use for viewing archives
|
|
* multiple user validation templates make validating new users fast
|
|
and easy
|
|
* batch user editing capabilities
|
|
* users can be purged based on number of days since last call and can
|
|
be excluded from this based on user level
|
|
* message and file areas can be easily created/edited/deleted
|
|
* groups of users can be created for batch private mailing
|
|
|
|
OTHER FUNCTIONS INCLUDE:
|
|
------------------------
|
|
* the language / format of the new user application form is
|
|
configurable
|
|
* SysOp can break into chat with a user at any time
|
|
* user can page the SysOp for chat
|
|
* a requester is popped on the workbench screen that indicates who is
|
|
paging and the SysOp can answer or ignore the chat request
|
|
* two colour chat display with full word wrap
|
|
* chat keeps a full log file of all text entered in chat mode
|
|
* single or double linefeeds can be selected for chat
|
|
* configurable log entries
|
|
* internal log entries can be assigned the user level required to view
|
|
them
|
|
* additional custom log entries can be defined
|
|
* a logging utility is provided so that external tasks such as online
|
|
games and network mail events can be monitored
|
|
* File maintenance section
|
|
* All files from a particular directory can be uploaded at once. The
|
|
SysOp can individually enter file descriptions, specify a single
|
|
file description for all files, or take descriptions from filenotes
|
|
* All attributes of a file can be edited
|
|
* message and file areas can be easily renumbered
|
|
|
|
Each BBS line can be configured separately. IE:
|
|
-------------------------------------------------
|
|
* modem configuration
|
|
* BBS Name
|
|
* public vs private (only users in a certain group have access)
|
|
* idle timeout delay
|
|
* minimum baud rate
|
|
* initial menu to be used
|
|
* default login command stack
|
|
* screen colors
|
|
* forced login command stack (applied before a user's personal login
|
|
command stack)
|
|
* language
|
|
* character mapping
|
|
* SysOp can easily monitor users who are online
|
|
* custom and workbench screens are supported
|
|
* screens for current online users can be open and closed from
|
|
AmigaDos
|
|
* any screen resolution / depth can be used
|
|
* any non-proportional font can be used
|
|
* can have a screen open automatically as each user logs in or have
|
|
them remain closed for more memory / CPU efficiency
|
|
* can configure screens to open only for designated users
|
|
|
|
MANAGEMENT
|
|
------------
|
|
* access to serial ports is managed so that term programs and network
|
|
mail software will not interfere with the BBS
|
|
* automated tasks that use the serial port are executed one at a time
|
|
as the serial port becomes available
|
|
* access to message and file areas is managed so that conflicts do not
|
|
arise between users and network mail software
|
|
* a powerful event scheduler is provided necessary for a 24hr
|
|
automated system especially if networked mail is being used
|
|
* events can be scheduled to occur on any combination of minute, hour,
|
|
day of week, day of month, month of year
|
|
* typical uses include scheduling of mail events, renumbering of
|
|
message areas, dynamically regulating access to phone lines DROP TO
|
|
DOS
|
|
* SysOp has full access to DOS from remote
|
|
* limited access to DOS can be given to users
|
|
* access to DOS commands is configured based on user level
|
|
* number of arguments allowed for each DOS command can be set
|
|
|
|
MENUS & DOORS
|
|
---------------
|
|
* powerful menu configuration
|
|
* any number of menus can be configured
|
|
* menu items can launch batch files, executables, other menus,
|
|
command stacks, or special DLG batch files
|
|
* any program that runs with standard input / output from a CLI can be
|
|
run from a menu
|
|
* menu items are accessible by user level
|
|
* user's only see the menu items they can access
|
|
* SysOp-editable help files can be attached to any menu item
|
|
* up to 128 custom menu TSETS' can be added to the system to allow
|
|
thousands of custom displays to be defined
|
|
* custom menu displays have no limits - they are totally free-form can
|
|
still maintain the Tsmart menu' philosophy where the user only sees
|
|
the commands that are available at the time
|
|
|
|
|
|
OBTAINING A DEMO OF DLG
|
|
------------------------
|
|
For a live demo of DLG Professional BB/OS, call the DLG development
|
|
BBS at:
|
|
|
|
BBS: (306) 249-2352
|
|
(306) 652-2084
|
|
Voice: (306) 665-3811
|
|
Fax: (306) 665-3811
|
|
|
|
FidoNet address: 1:140/90
|
|
|
|
Mailing address: #20 - 1524 Rayner Avenue,
|
|
Saskatoon, Saskatchewan, Canada
|
|
S7N 1Y1
|
|
|
|
=======================
|
|
5.05 - Excelsior! BBS
|
|
=======================
|
|
- Info for Excelsior! BBS will be available in future versions
|
|
of the BBS FAQ.
|
|
|
|
|
|
================
|
|
5.06 - MEBBS
|
|
================
|
|
|
|
MEBBSNet v1.0 highlights
|
|
-------------------------------
|
|
Fixes, and changes you can expect to see in MEBBSNet v1.0 are:
|
|
|
|
o DRASTIC reduction in executable size. The MEBBSNet executable is
|
|
now under 270k vs. 380k+ for StarNet. (Possibilities are good it
|
|
will shrink even further before release as fine tuning continues).
|
|
|
|
o DRASTIC reduction in the amount of system STACK usage. MEBBSNet
|
|
only requires a 20k stack for operation (Down from 60k in StarNet).
|
|
|
|
o DRASTIC increase in execution speed. Sophisticated programming
|
|
techniques and removal of 'busy loops' have resulted in incredible
|
|
speed increases in system operation.
|
|
|
|
o Removal of all Enforcer and MungWall problems. The software has
|
|
been converted to TRUE 32bit base-relative addressing, and uses a
|
|
'vanilla' compile (no switches needed at compile time).
|
|
|
|
o All Date handling code rewritten from the ground up for proper
|
|
operation.
|
|
|
|
o WorkBench v1.3 Compatable.
|
|
|
|
o Complete new file transfer protocol operation. Existing file
|
|
transfer protocols have been completely removed (and subjected to a
|
|
horrible, fiery death). XPR protocols are now used for file
|
|
transfers, and are Sysop configurable via an included GUI utility.
|
|
There is no hardcoded limit to the number of XPR's you may use.
|
|
(Hooks are in place to allow XPR protocols to be configurable by
|
|
accesslevel in v2.0)
|
|
|
|
o Libraritized Task Management system keeps memory usage to a minimum
|
|
while maintaining a secure and stable environment.
|
|
|
|
o 3rd Party Developers Library and programming support
|
|
(MEBBSutility.library). Developers are furnished full library
|
|
information, example code, and complete documentation in 'autodoc'
|
|
format.
|
|
|
|
o 3rd Party Developers are assured upwards compatability with new
|
|
releases of the MEBBSutility.library. No more recompiling when a new
|
|
version is released. If it works under MEBBSNet v1.0, it will work
|
|
under future releases.
|
|
|
|
o Graphic User Interface (GUI) utilities for Editing system
|
|
configuration, Users, and Files (MEBBScfg, MEBBSue, MEBBSfl).
|
|
|
|
|
|
MEBBSue (User Editor) feature highlights:
|
|
------------------------------------------
|
|
Hotkey launch from BBS screen.
|
|
Find New users
|
|
Add new users
|
|
FAST searching. Point/click search ability on upto 2 fields at once.
|
|
Ability to delete user(s) waiting mail file.
|
|
Full report generating capabilities w/definable path:filename.
|
|
|
|
|
|
MEBBScfg (System configuration) feature highlights:
|
|
----------------------------------------------------
|
|
Hotkey launch from BBS screen.
|
|
Full report generating capabilities w/definable path:filename.
|
|
Changes made are updated immediately, not just upon exit.
|
|
Full point-n-click operation for adding file/message areas,
|
|
access levels, and all system paths.
|
|
|
|
MEBBSfl (File Area Maintenance) feature highlights:
|
|
----------------------------------------------------
|
|
Hotkey launch from BBS screen.
|
|
Built-in Help. Ability to 'localize' language used for Help functions.
|
|
ARexx port.
|
|
Adopt/OnDisk functions for adding/removing files.
|
|
Check/Change file extensions (great when using re-archivers)
|
|
Filenote files with short descriptions.
|
|
Kill/Move/Rename/Edit file functions.
|
|
Update file information (size, etc.)
|
|
Sort existing files in file catalog.
|
|
Fully configuable filelist generation via Point-n-click or Arexx.
|
|
Includes all aspects of file catalog entries such as uploader,default
|
|
description, <Free Download>
|
|
All features are configurable to operate on either individual file
|
|
areas or on a global basis.
|
|
Full report generating capabilities w/definable path:filename.
|
|
|
|
o Support for alternate character sets.
|
|
o Full Internal ASCII string configurability. This includes not only
|
|
the text itself, but also the Menu Command letters.
|
|
o Sysop-definable font for bbs screen(s).
|
|
o Serial I/O has been rewritten from the ground up with an eye on
|
|
stability and speed.
|
|
o Support for 16,800, 19,200, 21,600 bps modems and ISDN lines.
|
|
o NEW Modem Compiler.
|
|
o NEW Menu Compiler.
|
|
o NEW ARexx port (with MORE features).
|
|
o NEW Nodelist Compiler (MEBBSnlp) is full-featured and FAST.
|
|
o CLI Door support.
|
|
o Emulator for running existing StarNet doors (games).
|
|
o NEW Line-oriented Message Editor
|
|
o Line Editor has the ability to upload a message from disk and dump
|
|
a message to disk (or printer).
|
|
o All file I/O code rewritten. (No more 'lost' files.)
|
|
o Internal File Indexing routines rewritten using linked-lists.
|
|
ReIndexing now is fast (system dependant) as well as easy on the
|
|
CPU.
|
|
o Support for alternate 'FrontEnds' rewritten for proper operation.
|
|
o Internal FrontEnd now supports EMSI. EMSI is sysop configurable
|
|
(On/Off) and will properly fall-back to YooHoo (then lotek) if it
|
|
fails to get an EMSI connect. Support for 9 (nine) network addresses.
|
|
Addresses now use a common inbound/outbound area. No more multiple
|
|
inbound/outbound directories!
|
|
o NEW Tosser/Packer (MEBBStoss), is 5x faster than the previous
|
|
Tosser/Packer. MEBBStoss supports 4-D Addressing, FidoNet 2.2 packet
|
|
headers, and Packet-level passwording. Exports conform to Fidonet
|
|
2.0 message standards.
|
|
o MEBBStoss has the ability to generate a report on your mail areas
|
|
for debugging purposes when setting up FidoNet.
|
|
o Packet-level passwords are Sysop configuable for inbound mail,
|
|
outbound mail, or both.
|
|
o Mail packets are processed in chronological order. No more reading
|
|
replies before the original.
|
|
o Poll packet generation can be done on a z:n/n.p basis, or use the
|
|
Call_<line>.ctl file to generate multiple poll packets at once.
|
|
o Tosser/Packer has the (Sysop definable) ability to auto-create new
|
|
echomail areas as they are received. MEBBStoss generates E-Mail to
|
|
Sysop with full stats on the area(s) created. MEBBStoss auto-updates
|
|
the Areas.cfg file with the new tagname(s) for reduced Sysop
|
|
maintenance requirements. Path to new message areas is configuable.
|
|
o EchoMail security features abound (even with nodes you already
|
|
connect to). Network connections and mail processing now have
|
|
security features which are several orders of magnitude above that
|
|
which existed previously.
|
|
o Netmail routing as Originator or Passthru.
|
|
o Point.CTL file removed. All point information is contained in
|
|
Areas.CFG and is listed in 4D format.
|
|
o PassThru.ctl removed. All Passthru information is contained in
|
|
Areas.CFG. PassThru areas do not need a message base
|
|
(or any other directory space) on your system other than the space
|
|
the outbound (passthru) mail packet(s) will occupy.
|
|
o Tagnames are no longer tied to a particular messagebase #. If you
|
|
move a messagebase from one area to another, Areas.CFG no longer
|
|
needs to be modified.
|
|
o MEBBStoss has a RESET commandline switch to auto-update all high
|
|
message counters automatically.
|
|
o .TIC files are deleted upon sucessful transmission. Reduced
|
|
maintenance for those who Hub in file networks is a result.
|
|
o Netmail/Fido File attaches now can use complete Path:To/Filename in
|
|
.FLO files for both convienience and space savings.
|
|
o Event handling completely rewritten. The old problem of a user
|
|
getting shorted daily time because an upcoming event was near is no
|
|
longer a factor if the next event also allows callers (MEBBSNet
|
|
will execute the script(s) in the background). 64,000 (sixtyfour
|
|
thousand) scripts supported for your convienience. Flags for start
|
|
of event script, fidoin, fidoout, and user logoff. Also configurable
|
|
are file requests, crashmail, mailonly, and nonetwork. If NoNetwork
|
|
is selected, the bbs will not display the 'Press Escape' prompt, and
|
|
go directly to the Welcome screen. This has been added for those
|
|
systems who do not belong to any network(s).
|
|
o NewUser Login has been rewritten for more logical operation. The old
|
|
problem of a newuser entering an existing handle no longer dumps
|
|
them back to the beginning.
|
|
o NodeList search function rewritten for proper operation. Display has
|
|
been reorganized to show Net address, system name, and phone number.
|
|
o MEBBSbase now removes 'holes' (deleted file #'s) from the filebases
|
|
upon initialization (aka 'NOGAPS'). A CLI/Shell utility is supplied
|
|
(CleanCatalog) to automatically remove duplicate filenames from your
|
|
file areas. CleanCatalog generates a batch file which (if executed)
|
|
will also delete the files themselves.
|
|
|
|
o General reorganization of the system for more logical operation. For
|
|
FidoNet(c) systems, Areas.cfg now handles 4-D Addressing, Passthrus,
|
|
and tagnames.
|
|
o All user-configurable text files (.ctl) now reside in the
|
|
MEBBSnet:Configfiles directory. A Sysop now need only look there to
|
|
find configurable textfiles. 3rd party developers are encouraged to
|
|
use this reorganizational change for their utilities also. Binary
|
|
configuration files are located in MEBBSNet:S
|
|
o Log files now are more descriptive and consistant. This will allow
|
|
for 3rd party utilities for billing, and other things that rely
|
|
upon system logs for operation to operate easier and with greater
|
|
efficiency.
|
|
o Modem Dial-out functions have been completely rewritten.
|
|
o New miscellaneous CLI/Shell utilities include:
|
|
|
|
BBSStringParse Compile ASCII strings within the executable into binary.
|
|
BBSStringDump Take bbs stings (binary) file and dump to ASCII
|
|
CheckEvent Returns information about current running event.
|
|
CleanCatalogs Remove duplicate filenames from file catalogs.
|
|
Generates script file that can be edited and executed
|
|
to remove duplicate filenames themselves.
|
|
DinkyRobo WB2.0 GUI message posting utility.
|
|
FrekIt Generates list of file-requestable files. Supports
|
|
'magicnames' include file, ability to remove file
|
|
extensions from requestable names, attach passwords.
|
|
KillEmpty Kill any file listed by AmigaDOS as <Empty>
|
|
ProtocolConfig WB2.0 XPR protocol configuration.
|
|
NLSearch Find a node in the nodelist.
|
|
ReScanStrings Edit BBS ASCII strings, recompile, then use this
|
|
utility to make MEBBSNet aware of the new changes.
|
|
TestMessage View message headers.
|
|
TestPacket View Fido packet headers.
|
|
TestRoute View Fido routed netmail.
|
|
ShowModemDat View compiled Modem_<line>.Dat file as MEBBSNet sees it.
|
|
|
|
o This is not to mention the dozens of little changes and refinements
|
|
to remove backwards logic in things that worked before.
|
|
o Eight Support Site systems available 24 hours a day to registered
|
|
users. Four are located in the United States, 1 each in Australia,
|
|
Denmark, Sweden, and the United Kingdom. All are available via
|
|
FidoNet(c) and some are available via alternate networks.
|
|
|
|
|
|
o Software Upgrade Fees, MEBBSNet v1.0:
|
|
|
|
Registered StarNet licensees: NO CHARGE
|
|
|
|
o Documentation Upgrade Fees, MEBBSNet v1.0: (Not set at this time)
|
|
|
|
A completely new manual will be made available upon release. Due to
|
|
printing costs, it will be made available at our cost (We are NOT in
|
|
the manual selling business!). Cost has not been determined at this
|
|
time, and will be set after quotes have been received from printers.
|
|
|
|
Roger Walker
|
|
Director, MEBBSNet BBS Product Development
|
|
MEBBS Engineering and Software
|
|
|
|
|
|
================================
|
|
5.07 - X E N O L I N K v1.90
|
|
================================
|
|
|
|
BRIEF DESCRIPTION OF THE PRODUCT: XENOLINK 1.90
|
|
------------------------------------------------
|
|
Next Generation Professional Bulletin Board Software
|
|
Copyright (C) 1990-1994 Xenomiga Technology
|
|
Available: March, 1994
|
|
|
|
|
|
The principle upon which Xenolink has been designed:
|
|
|
|
"If a QuickSort in C is faster than a Bubble Sort in Assembly Language,
|
|
then let Xenolink be the QuickSort in Assembly Language."
|
|
|
|
Xenolink's efficient new architecture is now faster and more compact
|
|
than ever.
|
|
|
|
The changes are obviously far too numerous to list, but a brief
|
|
synopsis of the areas affected is listed below:
|
|
|
|
- Attractive AmigaDOS Release 2 interface
|
|
- Vastly enhanced security features
|
|
- Improved door support
|
|
- Completely redesigned FidoNet support
|
|
- Decrease in the already low usage of memory and disk space
|
|
- Even faster operation than before
|
|
|
|
Xenolink 1.90 has been tested as never before, by countless beta
|
|
testers with setups ranging from Amiga 500's to 4000's, 68000's to
|
|
68040's, CD-ROMs, FAX-Modems, HST 16.8k modems, Point hosts, Network
|
|
hubs, multi-line systems - the list goes on.
|
|
|
|
|
|
Overview
|
|
---------
|
|
- Designed and written for AmigaDOS Release 2 and above.
|
|
- Superlative reliability
|
|
- Very easy to use
|
|
- Attractive interface
|
|
- State of the art software design and system architecture
|
|
- Full multi-line capability
|
|
- Configurability to an almost sinful degree
|
|
- Foreign language support
|
|
- Highly efficient use of memory and disk space
|
|
- Optimised high speed performance
|
|
- Object Oriented library and door interface
|
|
- Full XPR (External Protocol) support
|
|
- Low CPU usage
|
|
- Supports all serial cards and all baud rates
|
|
- Uses Commodore's (GUI) Installer program for easy installation
|
|
- Mature software; large amount of third party Xenolink software
|
|
available.
|
|
- Large private support network linking together hundreds of Xenolink
|
|
owners with Xenomiga Technology.
|
|
|
|
|
|
Base Software Architecture
|
|
----------------------------
|
|
- Xenolink Resource Handler controls access to all Xenolink resources.
|
|
- Avoids unnecessary disk activity if a resource (such as a message.
|
|
base or file area) is in use by more than one process.
|
|
- Crash protection; if a door crashes or hangs a Xenolink node, system
|
|
data files and log files are preserved, even on the node that
|
|
crashed.
|
|
- Automatic resource preloading enables Xenolink to asynchronously
|
|
open files before they are required, thus reducing the bottleneck
|
|
caused by disk activity.
|
|
|
|
|
|
MEMORY USAGE
|
|
--------------
|
|
- Dynamic memory and resource allocation
|
|
- Xenolink and its accompanying utilities are residentable
|
|
(extremely low memory usage for multiple nodes)
|
|
- Extensive use of xenolink.library shared library routines
|
|
- All executables are very compact (needless compiler overhead
|
|
eliminated)
|
|
|
|
|
|
DISK SPACE USAGE
|
|
------------------
|
|
- Two files per message area, for unequalled speed and compactness
|
|
- Three files per file area
|
|
- Compact user data files
|
|
- Real-time data compression used on compiled nodelist
|
|
- Xenolink's compact data files have numerous advantages:
|
|
o Very high speed operation due to the small number of files used
|
|
o Minimises disk fragmentation
|
|
o Data files are easily archived
|
|
o Makes backing up very easy (very few files to back up)
|
|
|
|
SPEED
|
|
-------
|
|
- Very fast implementation of fast algorithms (both are important!)
|
|
- Enhanced Global Quick Indexing (EQDX) algorithms enable virtually
|
|
instantaneous location of any file catalogue entry or user.
|
|
- Written in C and assembly language, using SAS/C Version 6
|
|
- Any area requiring speed has been written directly in assembly
|
|
language; this includes:
|
|
o Screen/modem i/o
|
|
o Mail processing parsing and i/o
|
|
o Searching
|
|
o Sorting
|
|
o Hashing
|
|
o Semaphoring
|
|
o CRC checking
|
|
|
|
- Only a few assign statements required.
|
|
o Xenolink does not require you to add countless assign statements
|
|
to your startup-sequence
|
|
o Location of all directories specified in "dir.config" file
|
|
|
|
- Separate configuration files, stored in a single directory:
|
|
o General/global configuration options
|
|
o Node configuration
|
|
o Message bases
|
|
o File areas
|
|
o User access templates
|
|
o Bulletins
|
|
o Archivers
|
|
o External protocols
|
|
o BBS text
|
|
o BBS entry points
|
|
o Access restrictions
|
|
|
|
- FidoNet configuration files stored in a separate directory:
|
|
o Node security (password, default protocol, archive type,
|
|
send type)
|
|
o Nodelist configuration
|
|
o NetMail routing and forwarding
|
|
o EchoMail area configuration (origin lines, feeds, passthrough
|
|
are as)
|
|
|
|
|
|
DOOR SOFTWARE SUPPORTED:
|
|
-------------------------
|
|
- Full CLI door support
|
|
o Any program that runs in your CLI (shell) can be run as a door
|
|
o Does NOT require the use of fifo.library or custom handler files
|
|
|
|
- DOS Shell feature allows the CLI shell to be run within Xenolink
|
|
|
|
- AREXX interface
|
|
o Complies with the ABBEREXX door standard
|
|
o Supports many commands used by other BBS programs
|
|
o Many Xenolink specific commands
|
|
|
|
- Can run many Paragon/Star-Net doors
|
|
|
|
- Xenolink doors run in the same task context as Xenolink itself:
|
|
o Eliminates task context switching
|
|
o Door interface provides direct hooks into Xenolink functions
|
|
|
|
- Xenolink's shared library (xenolink.library) provides an easy to use
|
|
Object Oriented Interface for door programmers:
|
|
|
|
o Complete access to users, messages, the file catalogue, system
|
|
configuration, linked lists, node operations & tilde codes.
|
|
o Doors may initiate file transfers, send messages to other nodes.
|
|
o Doors which use the Xenolink library routines extensively are
|
|
often as fast as Xenolink.
|
|
|
|
- Internal BBS commands can be replaced by external modules.
|
|
|
|
|
|
Where can I purchase Xenolink 1.90 & how much does it cost?
|
|
------------------------------------------------------------
|
|
|
|
Tech Support/Sales:
|
|
--------------------
|
|
- None provided at the time of this release.
|
|
|
|
Xenolink can be ordered from the author:
|
|
----------------------------------------
|
|
Jonathan Forbes
|
|
1132 Bay Street
|
|
Suite 1101
|
|
Toronto, Ontario
|
|
M5S 2Z4 Canada
|
|
|
|
COST:
|
|
------
|
|
US$ 150 + $15 P&P if ordered directly from the author, contact your
|
|
local support board for the price in your currency.
|
|
|
|
Contact your local support board for the latest information file and
|
|
demoversion of Xenolink.
|
|
|
|
Local support sites:
|
|
----------------------
|
|
BBS Name: The Castle Arrgh!
|
|
Location: Vancouver, British Columbia, Canada
|
|
Fido #: 1:153/727.0
|
|
Phone #: 604-327-9494
|
|
SysOp: Jeno Horvath
|
|
Baud/Modem: 1200/14.4k - SupraFAX
|
|
|
|
BBS Name: Electronic Image
|
|
Location: Montreal, Quebec, Canada
|
|
Fido #: 1:167/165.0
|
|
Phone #: 514-937-9984
|
|
SysOp: Sean Mollitt
|
|
Baud/Modem: 1200/14.4k - Dual Standard
|
|
|
|
BBS Name: The Amiga Alliance
|
|
Location: Sedalia, MO USA
|
|
Fido #: 1:280/81.0
|
|
Phone #: 816-827-1688
|
|
SysOp: Ron Teague
|
|
Baud/Modem: 2400/14.4k - Dual Standard
|
|
|
|
BBS Name: The Attic
|
|
Location: Methuen, MA, USA
|
|
Fido #: 1:324/125.0
|
|
Phone #: 508-975-2340
|
|
SysOp: Mike Soucy
|
|
Baud/Modem: 1200/14.4k - v32bis Sportster
|
|
|
|
BBS Name: Destroyers Den
|
|
Location: Napa, CA, USA
|
|
Fido #: 1:161/903.0
|
|
Phone #: 707-255-0784
|
|
SysOp: Robert Thaller
|
|
Baud/Modem: 2400/21.6 - Dual Standard
|
|
|
|
BBS Name: The Mouse Trap
|
|
Location: San Diego, CA, USA
|
|
Fido #: 1:202/121.0 1:202/122.0
|
|
Phone #: 619-464-2134
|
|
SysOp: Bruce Lawson
|
|
Baud/Modem: 1200/21.6 - Dual Standard (v32/HST)
|
|
|
|
BBS Name: Arkham Asylum
|
|
Location: Stockholm, Sweden
|
|
Fido #: 2:201/244.0
|
|
UseNet Add: Daniel_Frost@bad.se
|
|
Phone #: +46-8-626-9355
|
|
SysOp: Daniel Frost
|
|
Baud/Modem: 1200/28.8k - V32bis/V.FC
|
|
|
|
BBS Name: Disaster Teams BBS
|
|
Location: Landskrona, Sweden
|
|
Fido #: 2:200/219.0
|
|
Phone #: +46-418-36999
|
|
SysOp: Micke Persson
|
|
Baud/Modem: 2400/14,4k - Dual Standard
|
|
|
|
BBS Name: Fish Disc Office Switzerland
|
|
Location: Buttwil, Switzerland
|
|
Fido # : 2:301/562.0
|
|
Phone #: +41-57-443222
|
|
SysOp: Adrian Glutz
|
|
Baud/Modem: 1200/14,4k - HST
|
|
|
|
BBS Name: Echo BBS Dordrecht
|
|
Location: Dordrecht, Holland
|
|
Fido #: 2:285/312.0
|
|
Phone #: +31-78-180305
|
|
Usenet: bart@xecho.wlink.nl
|
|
Sysop: Bart Schraa
|
|
Baud/Modem: 1200/14.4k - ZYX/V32bis
|
|
|
|
BBS Name: BAT
|
|
Location: Lisboa, Portugal
|
|
Fido #: 2:362/4.0
|
|
Phone #: +351-1-705070
|
|
SysOp: Paulo Laureano
|
|
Baud/Modem: 1200/14.4k - V32bis
|
|
|
|
BBS Name: Pertos Asshole
|
|
Location: Aarhus, Denmark
|
|
Fido #: 2:230/815
|
|
Phone #: +45-867-20273
|
|
SysOp: Kenneth Perto
|
|
Baud/Modem: 1200/16.8k - Dual Standard
|
|
|
|
BBS Name: Amiga Central
|
|
Location: Redditch, United Kingdom
|
|
Fido #: 2:253/167
|
|
Phone #: +44-527-69701
|
|
Usenet: marjon@martinac.demon.co.uk
|
|
SysOp: Martin Wasley
|
|
Baud/Modem: 300/21.6k - Dual Standard Terbo
|
|
|
|
BBS Name: Sidecar Express BBS
|
|
Location: Logan Village, Queensland, Australia
|
|
Fido #: 3:640/463.0
|
|
Phone #: +61-75-463-252 - MultiLine
|
|
Usenet: bpratt@splat.paxnet.com.au
|
|
SysOp: Brendan Pratt
|
|
Baud/Modem: 300 - 14400 v32bis + ZyXEL 19200
|
|
|
|
BBS Name: Pipeline BBS
|
|
Location: Auckland, New Zealand
|
|
Fido #: 3:772/250.0
|
|
AmigaNet #: 41:649/250.0
|
|
Phone #: +64-9-262-3563 - MultiLine
|
|
SysOp: Dan Croft
|
|
Baud/Modem: 1200 - 14400 v32bis
|
|
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
AMIGA SHAREWARE/FREEWARE BBS SOFTWARE
|
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
- 4D-BBS
|
|
- ABBS Software
|
|
- AXsh
|
|
|
|
==================================
|
|
- A M I G A C I T A D E L
|
|
==================================
|
|
|
|
What is the address for Citadel BBS & how much does it cost?
|
|
--------------------------------------------------------------
|
|
NAME OF THE PRODUCT: Amiga Citadel BBS(also know as Citadel 68K)
|
|
|
|
ADDRESS:
|
|
SNAIL MAIL:
|
|
Custom Services
|
|
P. O. Box 254
|
|
Moorestown, NJ 08057
|
|
|
|
BBS: The Amiga Zone (609) 953-8159
|
|
Internet: apreston@isd.csc.com, or tony-preston@portal.com
|
|
|
|
COST: FREEWARE, but donations accepted.
|
|
|
|
|
|
Brief Description Of Amiga Citadel BBS(also know as Citadel 68K)
|
|
------------------------------------------------------------------
|
|
|
|
Minimum System
|
|
----------------
|
|
Can be run on an A500 with 1.3 ROM and 512K with 2 floppies, but is
|
|
very limited.
|
|
|
|
Recommended System
|
|
--------------------
|
|
Any Amiga with 2.04 ROM or better, 20 MB HD space, and 2 MBs or more
|
|
of memory.
|
|
|
|
Citadel is a FREEWARE BBS project that is supported on the Amiga, IBM,
|
|
MAC(although the MAC is inactive now), and Atari.
|
|
|
|
Citadel is a room-based system. It is excellent for messaging. The
|
|
basic organization is in floors and rooms. While other BBS programs
|
|
have a message base as a secondary item attacked to the BBS,
|
|
in Citadel it is the BBS. Floors are a group of rooms. Floors
|
|
are a partitioning of the rooms into groups so that sysops and
|
|
users can manipulate their view of the system(you can for example
|
|
forget a whole floor). Think of floors as similar to conferences.
|
|
The basic unit is a room. A room is a location of a conversation.
|
|
Messages are that conversation. Most rooms will have a topic
|
|
(Like Amiga, MS-DOS, ect), some rooms can be shared with other
|
|
systems(networked). Room-based systems like Citadle have an
|
|
extremely streamlined set of commands for fast access to the messages.
|
|
|
|
|
|
History Of Amiga Citadel
|
|
-------------------------
|
|
Citadel was created in Nov. 1981 from something called DandD.pas,
|
|
a Dungeons and Dragons an adventure game editor/driver It then was
|
|
substantially revised and made to run on a CP/M based system.
|
|
Somewhere around April to June 1985 is became Citadel-86 with
|
|
automatic networking.
|
|
|
|
Later, versions for the Amiga, Atari, and MAC were created by various
|
|
people along with other variants for the IBM. The source was public
|
|
domain and spreading like wildfile! I have maintained the Amiga
|
|
Citadel since Jan 92 after complaining of bugs and was told by the
|
|
current maintainer to put up or shut up... I inherited the source
|
|
and have since done additional ports from the IBM source. Citadel is
|
|
not perfect or bug free, but all the major features work and it is
|
|
Enforcer hit free!
|
|
|
|
|
|
Basic functionality of Amiga Citadel
|
|
--------------------------------------
|
|
A Room is the basic unit. it may be:
|
|
- Shared, networked with other systems on the C86Net, or even other
|
|
networks(like FIDOnet, USENET) via external programs.
|
|
- Private, Public, Hidden, or Invitational. Rooms default to public,
|
|
with all users invited. Hidden rooms are available to users if they
|
|
know the name(a user tells the bbs to goto the room) after which it
|
|
is public to them. The Invitational rooms are private and the room
|
|
moderator must invite them to the room.
|
|
- Anonymous, where there is no user identification as to who posted the
|
|
messages. This is great for door games where users can create their
|
|
own identification using their door names.
|
|
- Directory, where a sysop or aide can attach a directory for uploading
|
|
and downloading of files. Files have a short and long display format.
|
|
Users can not only up and download files, they can examine the contents
|
|
of archives, extract and download just one file! Citadel has a powerful
|
|
command set.
|
|
- Doors may be attached to a room or globally accessable. Citadel uses
|
|
a stdio door interface and can run many popular door. The interface is
|
|
flexible enough that you can run any program that runs from a cli shell
|
|
window. Citadel comes with a full set of documentations, help files for
|
|
the user, and both a 68000 version and a 68030/20 version. Included in
|
|
the documentation is a list of about 100 systems in Canada and the USA
|
|
that are on the C86Net so you can call and ask questions. All required
|
|
files can be found on the Amiga Zone BBS (609) 953-8159 along with door,
|
|
external protocol and archives information.
|
|
|
|
|
|
CLOSING
|
|
---------
|
|
Citadel comes with several large documentation files that detail all the
|
|
inner workings of the configuration file and the BBS setup. Much of
|
|
this is the IBM documentation, but there are Amiga specific files.
|
|
|
|
Citadel is FREEWARE and may not be sold. It may be distributed with any
|
|
hardware or software collection so long as no charge is made for it.
|
|
|
|
Commercial use of Citadel may only be made to the extent that a BBS is
|
|
being run. Pay BBSes must get prior approval from the authors or
|
|
current maintianers before charging users for access.
|
|
---------- continued in next message ----------
|
|
|
|
|