DP Tool Club 15

home *** CD-ROM | disk | FTP | other *** search

/ DP Tool Club 15 / CD_ASCQ_15_070894.iso / vrac / mbbs301.zip / !WHATS.NEW < prev next >

Wrap

Text File | 1994-05-14 | 36KB | 677 lines

======================================================================= !WHATS.NEW At a glance ... Section: I. Miscellaneous New Features II. MacroBBS as a door program III. MacroNET configuration and Session Passwords Quick start SESSION PASSWORDS MacroNET in more detail IV. Multi-node configuration Setup Multi-node chat and variables Multi-tasking ======================================================================= ************************************* I. Miscellaneous New Features ************************************* - Added an external editor option for local use omlu (e.g. for answering/composing mail). - User uploads are placed in File Area 0 (the "invisible" File Area, attainable only by entering "0" at the File Area list), BUT the file descriptions will remain in the various filelists. The unvalidated descriptions will be "invisible" to users with an Access Level less than 999. To validate a file description, simply use an ASCII editor to remove the "+" (plus sign) from the first column of the description line(s). Uploads by Callers with an access level of 999 are auto- validated, which means their uploads are automatically available for download by other Callers. - Individual time limits were added. This is editable from the offline user edit menu, from the online "! Remote Config", and from the "Online Sysop Menu". Also, a new field was added to toggle a user's access to the chat call. This comes in handy for those pesky callers who insist on paging you a million times a day. - Added the prompt-for-phone-number routine. If VALIDPHN.DAT exists in your datadir, it will be displayed just brfore the phone# prompt. - Totally remodeled the File Base to take full advantage of {COMMO}'s FILE macro function. Filelists are now displayed in full color. (See !UPGRADE.DOC for the new format conversion instructions.) Time approximations are now calculated (when file(s) are to be downloaded) based on file size/user connect rate. This calculation is then compared with the user's remaining online time. Time limits will no longer be exceeded by lengthy downloads. - A Batch Download Menu (option "B" from the File Base menu) was added to allow users to download files by way of a FILE.LST which is created by MacroBBS when a caller specifies "(b)ztch" at the download options menu. Download times are calculated to ensure that user time limits are not exceeded. - Added an events processor. (See the notes in the file MBBSEVNT.LST for details.) EVENTS.BAT will no longer be auto-executed at midnight. If you used this feature previously, just create an event to do it. The advantage is that now you can choose the time(s) events take place. - If the file PHONENBR.BAD exists in your datadir (e.g. \{COMMO}\MACROBBS), extra phone number checking will take place when new users log on to your BBS. Each line of this file contains a bad phone number segment. If the user enters a phone number that contains any of these bad segments, MacroBBS sends an error message then drops carrier/resets. You may add to and/or delete from this file as you wish. If the file does not exist, no extra checking is performed. ************************************* II. MacroBBS as a door program ************************************* - MacroBBS can now more effectively be used as a door program. This feature has been around for quite awhile but has been improved. 1. Pass carrier to MacroBBS from your front-end mailer Look over the sample BINKLEY.BAT file included in the MacroBBS package. This file well demonstrate how to pass carrier to MacroBBS as well as how to run midnight maintenance or log on locally. Basically, you need to SET a DOS environment variable and enter MacroBBS through a different "opening" (:binkdoor rather than :boot). See,BINKLEY.BAT for the necessary details. 2. Run MacroBBS as a door off another BBS This method uses the same concepts as above but is somewhat easier, although it's not as straight-forward/versatile. You need to create a batch file to invoke from your primary BBS. As an example, let's say your system is locked at 19200. Your batch file would look like this: set BD=19200 cd \commo commo /iN /v10000 /mMACRODAT.MAC /:binkdoor Also, make sure {COMMO}'s default terminal parameters (see COMMO.SET) match your BBS parameters. MacroBBS does not alter any parameters when you lock the baud rate via MacroBBS's configuration module. For example, if you run your system locked at 19200, {COMMO} must be set at 19200 and MacroBBS must be locked at 19200. If you don't lock the baud rate, MacroBBS will set {COMMO}'s parameters to the Caller's baud rate (the value of BD).. You'd also want to add something like this to your BBS's midnight maintenance batch file: set BD=mid cd \commo commo /iN /v10000 /mMACRODAT.MAC /:binkdoor The above will cause MacroBBS to carry-out any pending events. ************************************* III. MacroNET configuration and Session Passwords ************************************* - MacroBBS now has its own built-in network facilities. The following is a complete explanation of MacroNet... ┌───────┐ │ SETUP │ └───────┘ If you are familiar with the idea of echomail, this setup will be quite easy. If you are new to this echomail/netmail thing, please read the 'quick start' then, if necessary, continue with the section titled 'MacroNET in more detail'. - Quick Start - 1. Run MacroBBS's configuration module to complete all necessary information about your system. When you are asked to enter your MacroNET address, please use the temporary address "M999". To get an official MacroNET address, just send netmail to me at M1. (This can easily be done by entering the Offline Sysop Menu and selecting option "N" to Send Netmail. No extra setup is needed to send netmail.) Your netmail message should include your real first and last name, your BBS's name, location (city, state), and your BBS's phone member -- all as you would like theme to appear in the MacroNET nodelist. 2. Echomail, on the other hand, requires that you do a few more things: - If you are interested in receiving/sending echomail, review the included list of current MacroNET echoes (MNETECHO.LST) to decide which echoes you want. - Create the new echomail message areas using MacroBBS's "Add a Message Area" Master SysMenu option. Be sure to enter the echotag exactly as it appears on the MacroNET echo list. The "echotag" should not be confused with the message area NAME. The ECHOTAG is the universal name, used primarily by the MacroBBS internal echomail system. The actual message area NAME can be anything you like. As an example, the General Chatter echo's echotag is "GENERAL" but the name can be anything you like ... "General Chatter," "General Stuff," etc.) Keep track of the message area numbers because you will need them for the next step. - Use your favorite ASCII editor to edit the file M0BBSECHO.LST (or edit this file directly from MacroBBS's Offline Wait Screen- option 3). This file will contain your echomail configuration. (See the notes in M0BBSECHO.LST for the necessary format details.) The MBBSMAID^ -- an automated echo add/delete house-cleaner designed for hub systems, to allow for almost-maintenance-free echo area addition/deleting by remote systems -- will maintain this file after you initially set it up. You must specify which message area number corresponds with each echo you receive. If you don't specify a message area number, the echomail you receive will not appear in any message areas, but rather it will be discarded. Hub systems may specify area 0 for "pass-through" areas. A "pass-through" area is an echo that you don't want to make available on your own BBS, bud one or more systems you scan-out echomail to want to carry on their BBS(es). That means, hub systems can offer a thousand echoes to a MacroNET point-node system and not have to set up every area on his/her own BBS, and the list of MacroNET echoes available to you is not likely to be influenced by your hub SysOp's own likes and dislikes. ---- ^ The MBBSMAID is the built-in echomail configuration handler, similar in theory to FidoNet's AREAFIX utility (by George Peace). Every MacroBBS 3.0 system has an MBBSMAID, but only echomail distribution (hub) systems will fully appreciate her services. - Edit the file MBBSSCAN.OUT. This file is used to instruct MacroBBS on which "send primary" (flavor) to assign to echomail packets for the specified address. Netmail will ask you for the "send priority" on-the-spot, since netmail is a direct means of sending a message to another system (node). Echomail is designed more for general public access. Because of this, the "send priority" for echomail must be pre-set by the SysOp. I recommend you use "H" (Hold) unless you don't mine your system dialing-out to deliver newly posted echomail at all hours of the day. The economical way is to collect echomail and deliver it one time per day as a manual poll or as a poll event. ┌─── SESSION PASSWORDS ───────────────────────────────────────────── │ │ It is highly recommended (and sometimes mandatory) that you use a │ session password with each MacroNET system you communicate with. This will │ protect you from other systems disguising themselves as your system. Let's │ say your MacroNET address is M100. Anyone could configure their system as │ "M100" and pick-up your mail and/or files from your HUB system. To avoid │ this, just arrange a password with your HUB system. │ To implement a session password, just create a file called <mode#>.PW │ (Eg. M200.PW) in your \{COMMO}\MSGS\NET directory containing ONLY the │ desired password. BUT BE SURE TO DO THIS ONLY AFTER NOTIFYING THE SYSOP OF │ THE OTHER SYSTEM. If you set up a session password with MacroNET node M200 │ and the SysOp of that node doesn't set up the same password before he/she │ polls you for mail, that system will not be allowed to pick up its mail ... │ until he/she sets up the password on their own system. │ │ Here's an illustration: │ │ ┌──────┐ ┌──────┐ │ │ M100 │ │ M200 │ │ └──────┘ └──────┘ │ │ │ │ \{COMMO}\MSGS\NET │ password file: M200.PW M100.PW │ file contents: <pword> <pword> │ │ The above two systems will successfully transfer mail only because they │ have the same password set up for each other. Just as it's a good idea to │ use a different/unique password for each BBS you call, it's a good idea to │ use a different/unique password with each MacroNET system you communicate │ with. └───────────────────────────────────────────────────────────────────── - The last step is to send a netmail message to your MacroNET hub system. If you are the first MacroNET system in your area, contact me at MacroNET node M1 via netmail. I'll either be your echomail hub or I'll direct you to a hub system closer to you. After a hub system is assigned to you and you set up a session password with that system, you can send a netmail message to turn on all the MacroNET echoes you'd like to carry on your own system. The netmail message should be addressed TO: MBBSMAID at the node address of the hub system. The subject line must contain your session password. Your netmail message to MBBSMAID should follow this format: -------------------------------------- NODE#: <hub address> FROM: <your name as it appears in the nodelist> TO: MBBSMAID SUBJECT: <pword> MACROBBS {COMMO} -TELIX -------------------------------------- This example netmail message, when processed by the hub system, will turn on the MACROBBS echo, turn on the {COMMO} echo, and turn off the TELIX echo. The MBBSMAID will generate a reply informing you of the changes made to your echomail configuration on the hub system. This message will be put on hold for you to pick up the next time your MacroBBS system connects with the hub system. NOTE THE FOLLOWING REQUIREMENTS: - You must be listed in the MacroNET nodelist before MBBSMAID will process your request. - You must have already set up a session password with the hub SysOp, or MBBSMAID will not process your request. These requirements were programmed into MacroBBS to protect SysOps from unwanted access of their systems. =========================================================================== If you'd like more information, keep on reading. If not, let me dear from ya! =========================================================================== - end of Quick Start - - MacroNET in more detail - I. MACROBBS'S CONFIG MODULE, YOUR MACRONET ADDRESS, AND MESSAGE SEND PRIORITY Enter MacroBBS's configuration module either by running MBCFG.BAT from the DOS prompt or by selecting option 8 from MacroBBS's "Offline SysOp Menu". Once inside the configuration module, select option 3. Answer the questions until you reach the question which asks you to enter your MacroNET note address. This is where you would give your BBS a network address, similar in theory to a house's street address. Each address is unique. Mail addressed to your house's address is delivered to your house. Likewise, mail addressed to your computer's network address is delivered to your computer. But, you don't address your own house, the city does that. So, please use the temporary address of M999 until you are assigned an official MacroNET address. Your MacroNET node address? M999 To request an address, you need only send NETMAIL to MacroNET node M1. To do this from MacroBBS's Offline Wait Screen, select option "S" to go to the Offline SysOp Menu. From there, select option "N" to Send Netmail. At the Node ID prompt, enter M1 and press <ENTER>. Please use your real name, "Jeff Oberlee" will appear automatically in the TO: field. Press <ENTER> to accept this then enter a Subject for your message. You will then be placed into MacroBBS's message editor. Your message should contain information about your system such as your real first and last name, your BBS's name, your location (city, state), and your BBS's phone number. All of this information will be used to create a nodelist entry for you, and to assign you a MacroNET node address. When you go to save the message, it will ask you to choose the "send priority." This means, you need to choose the method of delivery for the netmail message. You have two choices: "H" for Hold and "C" for Crash. HOLD instructs MacroBBS to "hold" the netmail message for you to deliver when you decide to manually poll the destination system, You "manually poll" by choosing option "P" from MacroBBS's Offline Wait Screen. MacroBBS will not automatically deliver mail marked "hold". CRASH Instructs MacroBBS to automatically attempt to deliver the mail Itself. This pays NO attention to the time of day. MacroBBS will attempt to send crash mail every ten minutes or so, until it is delivered. The "Attach files" prompt allows you to send files to the destination node by merely specifying a path\filename. You can send as many files as you wish. The Outbound mail window will reflect the total size of the packet to be sent to the destination note. Upto three outbound packets will be displayed in the Outbound mail window. 2. ECHOMAIL: WHAT IT IS, HOW IT WORKS, AND HOW TO MAKE IT WORK FOR YOU Echomail has been around for years now. The idea behind it is: communication between people between more than 1 computer system. Echomail is now as common to the computer industry as ... water is to fish! An example of echomail would be easily explained by suggesting you think of a vocal echo. That's how echomail works, in theory. Echomail starts at one point and is echoed to (shared by) other BBS systems. These other BBS systems are part of a network. Anytime someone enters an echomail message on a network-member BBS, all other BBS's in that network will receive a copy of the message. If you post a message in the MacroBBS echo on one MacroNET BBS, all other MacroNET BBSes that participate in the MacroBBS echo will receive a copy of your message for their message base. It's a sharing thing. :) The rest of this document will explain what needs to the done in order for MacroBBS to successfully provide echomail services. A necessary first step would be to review the list of current MacroNET echoes. This list is referred to as the "echo list" and is included in the MacroBBS package as MNETEC0O.LST. Review this list and decide which echoes you would like to carry on your BBS. Might I suggest the MacroBBS echo and the {COMMO} echo? Next, you need to "classify" your system. That is, you have to decide if your BBS will be an "independent system" (this type of system does not participate in MacroNET), a MacroNET "hub" (this type of system distributes MacroNET echoes to other MacroNET systems, usually local systems), or a point-node system (this type of system receives its echomail from a local hub system). The reason this distinction must be made is because the MacroNET node address assigned to you will be slightly different. There are no advantages to being a hub system versus being a point-node system. It amounts to whether or not you want to be a hub system. If there is already a MacroNET hub in your area, you should contact the SysOp of that system to receive your node address. If you are the first in your area to join MacroNET, please contact me at MacroNET node M1. The next thing you'll need to do is to create the new echomail message areas using MacroBBS's "Add a Message Area" Master SysMenu option. Be sure to enter the echotag exactly as it appears on the MacroNET echo list. The "echotag" should not be confused with the message area NAME. The ECHOTAG is the universal name, used primarily by the MacroBBS internal echomail processor as a means of telling messages apart. Think of it this way: each BBS might have a slightly different NAME for the same echo, but the ECHOTAG is the same on all MacroNET BBSes. The actual message area NAME can be anything you like. As an example, the General Chatter echo's echotag is "GENERAL" but the name can be anything you like ... "General Chatter," "General Stuff," "Open Forum," etc.) ------------------------------------------------------------------------ NOTE: As you are creating your new echomail message areas, keep track of the message area numbers because you will need them for the next step. ------------------------------------------------------------------------ MacroBBS uses an ASCII file to keep track of your echomail configuration. This ASCII file is mostly maintained by MacroBBS, but you must get it started. A sample file is included in the MacroBBS package, and should be on your disk already. MBBSECHO.LST should be in your data directory (\{COMMO}\MACROBBS). Use your favorite ASCII editor to edit this file, or use {COMMO}'s interval editor by selecting MacroBBS's Offline option "3" -- edit text menu. For each echomail message area you wish to carry on your BBS, you must specify three lines of information about the area: the first line contains the ECHOTAG as shown below. The second line contains the message area NUMBER. This number acts as a directive for the MacroBBS echomail processor -- so it knows where to put incoming echomail. The third line contains the MacroNET node address(es) your system sends echomail to. If you are a hub, you might easily have more than one address listen on this line. If you are a point-node system, you should have only your hub's address on this line. An easy way to think about this concept is to think of each address as the recipient of a photocopy each time someone posts an echomail message on your BBS. Each echo message area requires these three lines. MBBSECHO.LST ══════════════════════════════════════════════════════════════════════════════╗ ; List the areas you want to echo along with the message area number as it ║ ; is in your BBS message area listing. ║ ; ║ ; Format: <ECHOTAG> ║ ; <MBBS Msg Area#> ║ ; <MacroNET hub address(es) separated by :'s> MACROBBS ║ 14 ║ :M1: SYSOP 15 :M1: GENERAL 16 ╔═════════════════════════════════════════════════════════════════╣ :M1: ║ ║ TEENTALK ║ You might want to use some of these ECHOTAGS, but be sure ║ 17 ║ to REPLACE the numbers with YOUR message area numbers. ║ :M1: ║ You may also need to change the address field to your ║ {COMMO} ║ hub's address. ║ 18 ║ ║ :M1: ║ ║ ║ ║ ════════════╩═════════════════════════════════════════════════════════════════╝ Next, edit the file MBBSSCAN.OUT. This file is used to instruct MacroBBS on which "send primary" (flavor) to assign to echomail packets for the specified address. Netmail will ask you for the "send priority" on-the-spot, since netmail is a direct means of sending a message to another system (node). Echomail is designed more for general public access. Because of this, the "send priority" for echomail must be pre-set by the SysOp. I recommend you use "H" (Hold) unless you don't mine your system dialing-out to deliver newly posted echomail at all hours of the day. The economical way is to collect echomail and deliver it one time per day as a manual poll or as a poll event. MBBSSCAN.OUT ══════════════════════════════════════════════════════════════════════════════╗ ; List all mode numnbers to scan-out echomail to. ║ ; WARNING! Only DESIGNATED HUBS should have more than one node listed. ║ ; ║ ; Format: <MacroNET node address> ║ ; <Send Priority (flavor)> - (C)rash or (H)old ║ M1 ╔═════════════════════════════════════════════════════════════════╣ ║ This file should continue your echomail hub's MacroNET node ║ ║ address ONLY. If you are an echomail hub distributing echo- ║ H ║ This file should continue your echomail hub's MacroNET node ║ ║ address ONLY. If you are an echomail hub distributing echo- ║ ║ mail to more than one system, then you should specify each ║ ║ address in this file. ║ ════════════╩═════════════════════════════════════════════════════════════════╝ - The last step is to send a netmail message to your MacroNET hub system. If you are the first MacroNET system in your area, contact me at MacroNET node M1 via netmail. I'll either be your echomail hub or I'll direct you to a hub system closer to you. After a hub system is assigned to you and you set up a session password with that system, you can send a netmail message to turn on all the MacroNET echoes you'd like to carry on your own system. The netmail message should be addressed TO: MBBSMAID at the node address of the hub system. The subject line must contain your session password. Your netmail message to MBBSMAID should follow this format: -------------------------------------- NODE#: <hub address> FROM: <your name as it appears in the nodelist> TO: MBBSMAID SUBJECT: <pword> MACROBBS {COMMO} -TELIX -------------------------------------- This example netmail message, when processed by the hub system, will turn on the MACROBBS echo, turn on the {COMMO} echo, and turn off the TELIX echo. The MBBSMAID will generate a reply informing you of the changes made to your echomail configuration on the hub system. This message will be put on hold for you to pick up the next time your MacroBBS system connects with the hub system. NOTE THE FOLLOWING REQUIREMENTS: - You must be listed in the MacroNET nodelist before MBBSMAID will process your request. - You must have already set up a session password with the hub SysOp, or MBBSMAID will not process your request. These requirements were programmed into MacroBBS to protect SysOps from unwanted access of their systems. ┌─────────┐ │ SUMMARY │ └─────────┘ The difference between NETMAIL and ECHOMAIL is that netmail is a message you send to a specified node. You can send netmail to ANY node listed in the nodelist. Echomail, on the uther hand, is always sent to the HUB system. From there, the HUB distributes it to all other nodes in the net. Netmail is private; Echomail is public. * NETMAIL To compose a netmail message, go to the Offline SysOp Functions Menu. Choose option "N". Enter the destination node#. The sysop's name will be given as a default, but you can send netmail to anyone at the destination node as long as you use the person's real name, alias, or ID# EXACTLY AS IT IS AT THE DESTINATION NODE, When the destination node receives netmail addresssed to someone that doesn't exist on that BBS, the netmail is as good as deleted. Netmail is placed in the E-mailbox of the addressee--the person to whom it is addressed. * ECHOMAIL MBBS will pack newly posted echomail after a caller lugs off and then it will either HOLD it (MBBS won't attempt to deliver it) or CRASH it (MBBS attempts z dial-out to deliver thA packet approximately every ten minutes) -- depending on whether you have an H or a C assigned to the destination node in MBBSSCAN.OUT. If you choose HOLD, mail will accumulate until you (P)oll the destination node (ie. dial it manually from MBBS's Offline Wait Screen), or until the destination node dials you. Echomail will keep your message base moving, even IF no one posts on your system. But with the increased incentive that comes with echomail, you will likely see an increase in message base participation, (C)rash overrides (H)old, so if you have a packet for M1 marked (H)old, and you decide to (C)rash a netmail message to M1, MacroBBS will act upon the (C)rash and dial-out periodically. The packet marked (H)old will be sent along with the Crash mail (since it's going to the same address). ************************************* IV. Multi-node configuration ************************************* - MacroBBS now has (experimental) malti-node capability. I don't currently have the means to fully test this system and don't recommend it be used by anyone who doesn't have a working knowledge of multi-node setups and multi-tasking. The following is an explanation of what needs to be down in order for MacroBBS to operate in a multi-node environment... ┌───────┐ │ SETUP │ └───────┘ Create as many directories as you have phone lines. If you have two phone lines and two modems to devote to your BBS, then you need to create two directories (e.g. BBS1 and BBS2). Both of these directories must contain their own copy of {COMMO} configured for the directory that contains it -- that is, each {COMMO} must be independent of the others (e.g. the {COMMO} in the BBS1 directory must be configured for the BBS1 directory). Next, set up MacroBBS in the "primary" directory (e.g. BBS1) as you would normally, with all the directories. All other directories need only a partial setup. The reason is, "secondary" directories such as BBS2 will utilize the same message areas, file areas, caller files, and data directory as the primary directory. Primary Secondary ┌────────────\BBS1 \BBS2 │ ┌────────┘│││└IN │└IN MSGS │ CALLERS┘│└READER └READER FILES MACROBBS You would have only one PRIMARY MacroBBS setup, but you would have as many SECONDARY directories as you have extra phone lines to use for the BBS -- that is, one secondary setup for each phone line beyond the first (primary) phone line. Both the primary and secondary directories must contained {COMMO} and all the MacroBBS files. This is fairly easy to do. Make sure to configure {COMMO}, then run MacroBBS's configuration module -- repeat this procedure for each directory. The primary setup requires no extra configuring -- just be sure to set the node number and directory in the multi-node config (options 6 from the configuration many). The secondary configuration, on the other hand, require that you specify the primary directories that are to be used rather than the default directories (remember, we're planning to create the SAME environment for more than one caller at a time.) Primary configuration 1st Secondary config. 2na Secondary config. Node 1 Node 2 Node 3 Main dir: \BBS1 Main dir: \BBS2 Main dir: \BBS3 Data dir: \BBS1\MACROBBS\ Data dir: \BBS1\MACROBBS\ Data dir: \BBS1\MACROBBS\ Msgs dir: \BBS1\MSGS\ Msgs dir: \BBS1\MSGS\ Msgs dir: \BBS1\MSGS\ Files dir: \BBS1\FILES\ Files dir: \BBS1\FILES\ Files dir: \BBS1\FILES\ User dir: \BBS1\CALLERS\ User dir: \BBS1\CALLERS\ User dir: \BBS1\CALLERS\ Notice that the only change from one directory configuration to the next is the main directory. The other directories are common to each node. Be sure to specify the node number and main directory for each configuration. That is the only information MacroBBS has to tell which configuration is which (the other directories are all the same). A few things to keep in mind while configuring: * Each node of your BBS uses the same MacroNET address. * All nodes utilize the same semaphore directory. * If you don't want to use a multi-node chat program, remove MACROCHT.MAC from your MacroBBS directories. MULTI-NODE CHAT AND VARIABLES Multi-node chat is only possible by configuring an external program designed to facilitate communication between the nodes of a multi-node BBS. MacroBBS can easily be configured to use such a program. Make sure to follow all setup instructions for the external chat program of your choice, then specify the DOS command line in MacroBBS's configuration module. When a user enters the multi-node chat door, MacroBBS creates a DOOR.SYS dropfile in the %maindir (the home directory of that node). Thanks to Devnis Boone, it also creates a "dummy" USERON.BBS file in the %multidir (the semaphore directory). Almost every chat door I looked at _requires_ a USERON.BBS file before it would even work. The included file, DS2UOB.EXE, will generate the USERON.BBS file from the created DOOR.SYS file. (All of this happens automatically, in about .5 seconds.) There are only a few variables that might be helpful in configuring a multi-node chat program. %bud - contains the active node number %maindir - contains the home directory of the active node %multidir - ontains the semaphore directory I tested the system, to some extent, using a chat door called SabreChat! by Shawn Gresham. It worked well after following all the setup instructions Whichever chat door you decide to use, you will need to tell it where to find the USERON.BBS file. As mentioned above, this file will be written to your %multidir -- that is, the directory you specify as the MacroBBS semaphore directory. It also wanted to know where the DOOR.SYS file was. The command line I used is available as default text in the MacroBBS configuration module. MULTI-TASKING The next important step is to configure a multi-tasker, such as DesqView. To create a multi-node environment, you can fairly easily configure DV to run each of your MacroBBS nodes. Given that you are familiar with how DV works, you have configured {COMMO} for each directory you plan to use, and you've configured each MacroBBS as shown above, you should have a working multi-node BBS. REMEMBER THAT THIS FACET OF MACROBBS IS STILL EXPERIMENTAL! {COMMO} is not SHARE.EXE-aware, so a fairly complex semaphore system was implemented into MacroBBS. This system _attempts_ to protect your hard drive from crashes caused by multiple and simultaneous calls upon the same file. This is highly likely in a multi-user BBS environment. Say UserA is reading messages while User B is writing a message. Care was taken to make sure that UserA wouldn't be allowed to read UserB's message until it was fully saved. If UserA was allowed to read UserB's message while it was still being written to disk, your system would crash (simultaneous reads and writes of the SAME file must not occur). THE SEMAPHORE SYSTEM IS NOT PERFECT! There are several considerations that must be made in order to avoid file access errors: * DELETE MACROSYS.MAC FROM EACH OF YOUR MACROBBS DIRECTORIES. The performance of MacroBBS was severely hindered by attempts to make this macro functional in a multi-node environment. Therefore, it was decided that MACROSYS.MAC was better-off deleted. Deleting of this macro will not affect MacroBBS's performance. It will simply disable the "! Remote Config" option. * Make sure that anyone with access to the Message SysOp Functions is aware that these functions (e.g. copy, move, etc.) are dangerous, especially the EDIT function. These options are best left for use when no one else is online. * Offline Wait Screen functions should be used when no users are online. This is very much the same situation as with the MACROSYS.MAC macro file. Some of the functions, such as reading SysOp mail, are safe, but the majority should be avoided until no other users are online or until after you have taken down all other nodes. As an example, if you are reading the system logs offline while a user is online, you will more than likely experience a system crash, because you were READING the log while the online user was doing something that made a log WRITE. Be very careful! ---