------------------------------------------ Complete run-thru Doc for AmiExpress v2.30 ------------------------------------------ This doc does a complete run thru of the bbs and how its routines work for the September 1992 release version of AmiExpress v2.30 .......................................................... .: C O N T E N T S O F T H E D O C U M E N T A T I O N :. :::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Chapters: ~~~~~~~~ (1)................................. Introduction (2)....................... Copyrights Information (3)................................. Requirements (4)................... Installation of AmiExpress (5)............ The Way to install the ConfigFile (6)........ How to install the Express in Startup (7)............ All commands for your ACP.STARTUP (8)..................... The normal Documentation (9).............. The programmlogic of AmiExpress (10)......... The MainMenu Commands of AmiExpress (11)..... How to use the extended config in AmiEX (12)............ How the BBSInfo Conference works (13)................ AREXX Interface Module (AIM) (14).......... Traditional Interface Module (TIM) (15)........... AmiExpress Interface Module (XIM) (16)................. Custom Commands File Format (17)............ The MCI imbedded ControlSequence (18)... Complete List of all ACP.STARTUP Commands (19)........................... Noteable Features (20)...................... Note worthy of Mention (21)............................ Trouble Shooting ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ============================= 1. Introduction =============================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Ami-Express is a host Bulletin Board software program, allowing the transfer of data, between host and remote terminals via a telephone link. ( Obvious to some!! ). This data can be files uploaded or downloaded from remote (user end) from the BBS databases. Most Bulletin boards also contain message bases where you can read and leave electronic mail to other users. It is possible via some BBS`s to play online games, although these are of a simple nature, they can still be quite entertaining. For those of you that have been a user, either host or remote, for some time, will have noticed the major changes that Ami-Express has undergone. With the future proposed implementations Ami-Express will soon become comparable to other Major BBS programs found on Amiga and PC computers. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ======================== 2. Copyrights Information ========================= ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: If you own a an Illegal (Cracked copy) and you use it, then consider buying the original. This will not only provide you with support etc, but will encourage the further development of Ami-Express. ------------------------------------ AmiExpress and its source code are copyright 1992 by Light Speed Technologies AmiExpress is a comercial product, NOT shareware If you used it, please buy it! ------------------------------------ ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ============================ 3. Requirements ================================ ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: To install AmiExpress V2.30 you must have the following things: Program Location Description --------- -------- ----------- Express BBS/Utils Bulletin Board System ACP.ctrl BBS/Utils Bulletin Board controller AE.Library LIBS/ AmiExpress Library ^^ has been removed from Express, but Doors should use the LIB ^^ optional: CONFIG BBS Configuration Program - a stack of at least 50000 bytes - a Amiga Model (500/600/1000/2000/2500/3000) - the installed Version of Kickstart V2.0 (Soft or Hardware Version) - at least 2 MB free Space to be able to get uploads It is recommend to install AmiExpress on a Harddrive to increase the Speed of AmiExpress and to have enough space for Uploading software on the BBS. If you only want to test the AmiExpress Version than you can install the BBS also on a Diskdrive. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ======================= 4. Installation of AmiExpress ====================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: To install AmiExpress V2.30 you must have at least all the Requirement which were mentioned below. Now lets going on with the normal installation of AmiExpress. Now take your registered LZH file which you downloaded from your favourite Distribution Board of AmiExpress and decrunched it please on a Disk or take your Disk on which AmiExpress is allready installed. Now you must know where you want to install AmiExpress on your hard- drive. To explain the installation of AmiExpress much better it is recommend that you install the whole AmiExpress into the BBS: Directory on your Harddrive. If this Directory doesn`t exists you have to make it on your Harddisk. Now take your AmiExpress disk and take a look an it and you will see the following things: ------------------------- S (dir) libs (dir) Trashcan (dir) BBS (dir) BBS.DOX REVISE.DAT Trashcan.info ------------------------- Now you must know how many Conferences do you want to install in your bbs and the way you want to install AmiExpress. You have two ways to install the Conferences in a Configfile. 1.The first way to install a Config is to use the little Config program which is included in the Directory "BBS" under the name "Config" at the disk were AmiExpress is located. With this programm you have all the ability to install your BBS correctly. You can use the Configfiles which are allready at the BBS called "Config1" & "Config2". Each number at the end of the Config(x) replaceses the Node on which this Config shoudl be used. So you can use a other Config for every Node you are using as a normal Modemnode or as your Localsysopnode. If you want to use a Node as a Localnode (that means that only Local Logins are allowed at this node), then you only have to replace the serial.device defination with a empty line at the config of the node which will be your local one. If you are ready with the entries in the Configprogramm you have a menu called "Generate Conferences". If you use this Menu the Configprgramm will automatically create the directories and Files which are needed that the conferences are working perfectly. All the other Informations about the configprogramm you can see later when the ACP.STARTUP will be described. 2.The second way to install a config you can use the internal ACP.STARTUP which is located in the S: directory. In this Config you can do the same as in the Configprogramm. But this way is much better because the ACP.STARTUP is much saver against Viruses which changes the entries in the Config(x) file. All the Infos about how to install the ACP.STARTUP will be described later when the ACP.CTRL will be described. Then you have to copy the AE.LIBRARY which is located in the LIBS dir at the disk to your normal LIBS: directory at the Harddisk. The rest of the Installation will be described later in the normal Documentation. Now here comes some Directories you can copy directly from the Disk to the BBS directory at your Harddisk that the BBS will run correctly. -------------------------- S (dir) << install the whole BBS/Node1 (dir) << Files in this BBS/Node0 (dir) << directories AMI_DRIVES User.Data User.Keys -------------------------- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: =============== 5. The Way to install the Configuration Files =============== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ACP.Startup is the controller for the entire BBS, it defines who is allowed to do what. The ACP.STARTUP needs to know the following information: 1> The number of nodes you wish to run. 2> The way you wish the nodes to be started. 3> An instruction to load pre-made configuration files. Here is an example of S:ACP.STARTUP: ------cut here--------------------------------------------------- NUMBER_OF_NODES 3 STARTNODE0: RUNBACK >NIL: -S50000 BBS:UTILS/EXPRESS 0 STARTNODE1: RUNBACK >NIL: -S50000 BBS:UTILS/EXPRESS 1 STARTNODE2: RUNBACK >NIL: -S50000 BBS:UTILS/EXPRESS 2 LOADCONFIG ------cut here--------------------------------------------------- NUMBER_OF_NODES x = This tells the ACP.CTRL program how many nodes you will be running, the maximum is 9 nodes. STARTNODEx: This tells the ACP.CTRL how to start a particular node.. Prior users of AmiExpress probably had several script files to start the different nodes, but now with the ACP.STARTUP you do not need them. LOADCONFIG: This tells the ACP.CTRL that it should load all configuration files associated with the BBS. The configuration files are created with a program called CONFIG. Which should be in the BBS directory of the archive. We highly suggest that you store AmiExpress and all associated programs in a volume called BBS: this simplifies finding any probs you may have. Installing AmiExpress is fairly complicated so please be patient, even those who have run earlier version of AmiExpress should notice a lot of setup changes, Therefore there will not be any quick setup instructions. CONFIG - Prior to running AmiExpress you should create a CONFIG file for each node you are going to run, Use the program config which is located in the BBS directory of the archive, you will also notice in this directory that there is 3 pre-configured CONFIG files: Config0, Config1 & Config2 we created these so you would have an example to go by. Here is a list of steps involved in creating a Config(x) file: 1> Copy the config program to BBS: 2> Type BBS:Config from a command line or shell. 3> Answer all of the questions to the best of your ability. we suggest reading the complete docs to AmiExpress prior to doing this. a> you will need to know which node you are configuring. 4> After you have filled everything out, choose the generate conferences option from the CONFIG menu. 5> Choose the Save File option of the CONFIG program and save the file as BBS:ConfigX, where X indicates the node number. Node numbers can range from 0 to 8. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ================ 6. How to install the Express in your Startup ============== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: In order to get AmiExpress work perfectly you have to add the following things at your User-StartUp or Startup-Sequence file in the S: directory: -----cut here----------------------------------------------------- ASSIGN BBS: SYS:BBS PATH BBS:UTILS ADD RUNBACK >NIL: BBS:UTILS/ACP.CTRL -----cut here----------------------------------------------------- The above mentioned ASSIGN statement indicates that you have your BBS installed in a directory called BBS on the system drive. Once all of this is complete you should be able to reset your system. NOTE: You should have a BBS:Utils directory. Use this directory to put all amiexpress required utils, actually the only one we have that is required in the BBS:Utils directory is the Master Control Panel by Bryce! We are waiting an update to MCP, the example archive shows how to set it up. Keep in mind that BBS:Utils/MCP.script needs a S protection bit. If it does not have one then type the following once the MCP.script is in your BBS:Utils directory: protect BBS:Utils/MCP.Script +s ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: =================== 7. All Commands for your ACP.STARTUP ==================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: The ACP.CTRL program is the central hub to all bbs activity. You may wish to customize the way it works. Here are a few additional commands that you may put in your S:ACP.STARTUP file: definition of NODE commands: NODE* LEFTEDGE 0 ^ ^ ^ ^ | | | ----- Specifies LEFTEDGE should = 0 | | -------------- Specifies that you wish to set the LEFTEDGE variable | ---------------- Specifies that this command should effect all nodes | 1> * = all nodes. | 2> 0 = node 0 only | 3> 1 = node 1 only etc. upto 9. | ------------------- This is ACP.CTRL that you are executing a NODE COMMAND. ADVANCED COMMANDS INCLUDE: (x) & (y) indicates a value you put in. NODE* LEFTEDGE x = This specifies the LEFTEDGE of the specified NODE screen. NODE* TOPEDGE x = This specifies the TOPEDGE of the specified NODE screen. NODE* WIDTH x = This specifies the WIDTH of the specified NODE screen. NODE* HEIGHT x = This specifies the HEIGHT of the specified NODE screen. NODE* BITPLANES x = This specifies the number of BITPLANES of the specified node. NODE* INTERLACE = This specifies that you wish the specified node screen to come up in INTERLACE mode A complete List of all ACP.STARTUP Commands can you see at the end of this Documentation of AmiExpress. The above commands are only the main Commands which are needed to start the Express. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ======================== 8. The normal Documentation ======================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: The following documentation is designed to let the System Operator know exactly what is taking place in each step of the BBS operations. Apart from being a descriptive account of how Ami-Express works, this documentation also tries to help sysop's optimise their systems for maximum efficiency. Well, the real update of the V2.30 DOCS have been needed for a long time... Well here they are. This time done by The Bird with the help from Andy of X-Trade. The AmiExpress Logo was done by ENFORCER. The most difficult process in any software commericial release is the developement of the Documentation. After my first release of a update from the normal Documentation to a big V2.30 Doc found a very big response on my bbs and so Bomber decided to let me write a real update of the AmiExpress Doc which wil be included in every future version of AmiExpress. Any if you like this Documentation or you have a problem with AmiExpress you can call my BBS and i will help you with AmiEx as much as i can. And if a newer Version of AMiEx will be developed i will be very happy to do another update of the Documentation for this great BBS System. It`s very hard to write docs and i hope you like this new styling of the AmiExpress Docs. Everyone wants you to understand how the program works. But now lets go on with the normal Documentation of AmiExpress. Now open a shell and type BBS:UTILS/ACP.CTRL, You should notice a ICONIFIED window appear on the WorkBench screen. if ACP.CTRL did not appear on the Workbench Screen, ACP.CTRL should have left you an error message. If the ACP.CTRL doesn`t return a Error Message contact your local AMiEX Developer or me (The Bird) for more help. If there appear a Errormessage, please correct the error that is displayed. Now you should click on the ZOOM gadget to the ACP.CTRL window, This will expand the ACP window to reflect a series of buttons. To the left of the window you should see a NODE (x) button for each NODE you want to run. You should also notice at the upper portion of the window, 3 catagories: 'User', 'Location', 'Action'. Under 'Action' you should see a message pertaining to each node saying 'Awaiting Connect'. If you do not see the 'Awaiting Connect' message please open a shell and type Express x (where x is the node number), this should display an error message, most common problems is that you did not setup the configuration file correctly, could mean that you mispelled the device driver for the serial port, or it could be that you are missing some files. Whatever it is, it should tell you.. Refer to later sections in this documentation for corrective actions. Below the node buttons you should see a series of 18 buttons. There is 15 buttons in 3 columns on the left bottom of the window., These buttons control AmiExpress, the way to implement one of these buttons is to click on 1 of the 15 and then select a NODE button for action. Now if all nodes are showing 'Awaiting Connect' do the following: 1> Press the Accounts button 2> Press the NODE 0 button This will take you into account editing, you should see the following: ------------------------------------- S>earch by name N>ew account editing I>nfo Edit which account? ------------------------------------- 1> Type 1 then press This will take you into account number one, which is yours. You should see the following information: -------------------------------------------------------------------------------- ACTIVE [1] BAUD: 14400 A> Name: User Name-------------------30 B> Location ......: Location C> Pass ..........: Pass---8 D> Phone Number ..: 800-555-1212 (123456789) E> Ratio .........: 0 F> Conf Access ...: X________ G> Ratio Type ....: 0 <-Byte) H> Sec_Level .....: 255 I> Uploads .......: 0 J> AutoReJoin ....: 1 K> Downloads .....: 0 L> Messages_Posted: 0 M> Bytes Uled ....: 1 N> New_User ......: No #Calls: 0 O> Bytes Dled ....: 0 Last Called ...: Tue May 26 22:00:17 1992 Q> Byte Limit ....: 0 Computer Type : Amiga 1000 Y> Cps Up: 0 Z> Cps DN: 0 R> Time_Limit: [9600 ] secs S> Time_Used: [0 ] secs T> UUCP: 0 X=EXIT-NOSAVE TAB=Cont ~=SAVE 1-6=Presets 9=RE-ACTIVATE DEL=DELETE -------------------------------------------------------------------------------- 2> Press the letter A, this will let you put your name on your account. 3> Press the letter B, this will let you setup a address, group name or whatever you like. 4> Press the letter C, this will let you assign yourself a password. 5> Press the letter D, this will let you out your phone number in. 6> Now you can press a number between 1 and 6 for account defaults. 7> Make sure that your Time_Limit is not 0. 8> Press the tilde '~' to save the account,. Here is a sample of a completed sysop account: -------------------------------------------------------------------------------- ACTIVE [1] BAUD: 14400 A> Name: ByteMaster B> Location ......: ByteMaster's BBS C> Pass ..........: London D> Phone Number ..: 318-793-4101 (123456789) E> Ratio .........: 0 F> Conf Access ...: XXXXXXXXX G> Ratio Type ....: 0 <-Byte) H> Sec_Level .....: 255 I> Uploads .......: 0 J> AutoReJoin ....: 1 K> Downloads .....: 0 L> Messages_Posted: 0 M> Bytes Uled ....: 1 N> New_User ......: No #Calls: 1 O> Bytes Dled ....: 0 Last Called ...: Tue May 26 22:00:17 1992 Q> Byte Limit ....: 0 Computer Type : Amiga 1000 Y> Cps Up: 0 Z> Cps DN: 0 R> Time_Limit: [9600 ] secs S> Time_Used: [0 ] secs T> UUCP: 0 X=EXIT-NOSAVE TAB=Cont ~=SAVE 1-6=Presets 9=RE-ACTIVATE DEL=DELETE Save -------------------------------------------------------------------------------- 9> Press the TAB key to complete the editing. Now you should see the following: ------------------------------------- S>earch by name N>ew account editing I>nfo Edit which account? ------------------------------------- 10> With "I" you can get into the BBSInfo Conference witch will be described later.. 11> Press return to exit account editing. 12> Select the close gadget to return to the WorkBench screen. This will also of course close the BBS Window. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ==================== 9. The programmlogic of AmiExpress ===================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: We will now describe the program logic of the Express so you can learn how to operate AmiExpress to it's maximum potential. The ACP window has 15 major buttons at the bottom of the window. Here is a list of there names and function: [ Sysop Login ].....Logs you into a node as the sysop [ Local Login ].....Enters the initial long on phase of the Node This will require you to specify your name and password. [ Instant Login ]...This will give a carrier detect command to the modem, this is good for re-establishing a connection to a user after talking to them voice on the same line. [ Reserve Node ]....This allows you to tell the Node to only let a certain user on the BBS. After the user has called the node will no longer be reserved. [ AEShell ].........This will open a shell on the Node screen. [ Accounts ]........This takes you into account editing on a node. [ Toggle Chat ].....This toggles the Node's chat request flag, if a Nodes Chat request flag is off, then only user of a high enough security level be able to request a chat. [ Init Modem ]......This re-initializes a modem of a particular node. [ Exit Node ]......This will shutdown the node in question. [ Node(offhook) ]...This will shutdown the node in question and also make the line busy. [ Node Config ].....This will bring up our config program for a particular node. [ Node Chat ].......This button will take you into chat mode with a particular node. [ Save Win ]........This button does not require a NODE(x) complement. This simply saves the window coordinates of ACP to a file called S:ACP.Config [ Reserved ]........This button is reserved for future use. NOTE: All of the above mentioned buttons unless said otherwise, require you to press the Appropriate node button for them to take effect. Once all of the NODES are started the following actions take place for each node: At this point the bbs will load up the computer types from a file called: BBS:NODE(x)/COMPUTERLIST (x) indicates 1 of 9 nodes EXAMPLE: -----------(cut here)------------ 5 <- This entry describes how many computer types follow Amiga 500 <- 1st entry Amiga 1000 <- 2nd entry Amiga 2000 <- 3rd entry Amiga 3000 <- 4th entry Other <- 5th entry -----------(cut here)------------ ^ |_ | NOTE: The bbs and ACP require this file to exist in order to operate Ami-Express then checks if the node is already running as another task, and if it is, then the program halts and exits with an error message. Next, Ami-Express will try to access the LIBS:REXXSYSLIB.LIBRARY for it's Arexx port routines, and if not found, will disable the Arexx port and inform the user that the Rexx port is disabled. Now the Node will check to see if you have any logon and logoff screens. There is an auto randomization routine for displaying screens. If you wish to take advantage of this then you need to decide if the logon & logoff screens are to be node specific or BBS specific, once you decide, you need to place all Node Specific logon & logoff texts in the: BBS:Node(x)/Screens directory. If you wish the screens to be the same for all nodes then you them in BBS:Screens. NOTE that if a logon screen appears in the BBS:Node(x)/Screens directory then the Node will use it and not bother to check if you have any in the BBS:Screens directory.. You can say this is kind of a priority system. If there is no logon screens in neither the BBS:Screens or BBS:Node(x)/Screens then Express will look in the BBS:Node(x) directory. If you plan on using the randomization screens then you will need to put them in either the BBS:Node(x)/Screens directory or in the BBS:Screens/ directory under the following filename syntax: LOGON1.TXT LOGON2.TXT LOGON3.TXT etc... LOGOFF1.TXT LOGOFF2.TXT LOGOFF3.TXT Ami-Express will run thru it's initialisation process where it will take the modem off-hook, and configure it for BBS operation. This is done so that an incoming call does not alter the configuration process. While someone is online you have the following function keys available to you: F1 - Chat in/out F2 - Increase Online time limit +10 mins F3 - Decrease Online time limit -10 mins F4 - Asks for a path/filename for a capture file (only on the sysops side) or if one is already open then it closes the capture and lets you know it did so. when you press F4 again the capture will be stopped. SHIFT+F4 - Asks for a path/filename to ASCII send a file (only on the sysops side) F5 - Local Shell F6 - Account Editing SHIFT+F6 - This will let you change the Account of a User only for that call he is online. When he locks off the BBS will reset his Account to the old one. Press Shift+F6 a second time and the changes will be reseted to the old ones. F7 - Chat Flag toggle (whether you are to be paged or not) F8 - Serial in on/off (User can`t write until you press F8 again) F9 - Serial out on/off (User can`t see what you are typing) F10 - Keyboard out on/off (Disconnect OnLine User *KICK*) Now follows the normal reactions of AmiExpress when something happens if the bbs is in the standby mode and the nodes are standing at "Awaiting Connect". (1). The bbs checks for F key input from the local keyboard. (2). Or data coming in the serial port. (3). Or data coming in the internal commnunication AmiExpress_Node(x) msgport for commands either suspend, resume, or shutdown. (4). Or data coming in from the AmiExpress window itself (Gadgets etc..) (5). Or data coming in from AmiExpress Control.(ACP) Once the modem picks up a RING DETECT, the bbs sends an Answer string specified in the config file to the modem, and waits for a response from the remote modem. If the resultant string is a valid connect string, the bbs continues with normal operations, if not, it resets the modem and the ACP screen will return to "Awaiting Connect" state. If the connect string was a valid one, AmiExpress firstly checks a couple of things before performing the login routine: (1). System checks for a file called: BBS:NODE{x}/NOCALLERSAT{BAUD} where x is node number and BAUD is the baud rate that is unaccepted. If this file exists, and the current baud rate matches the BAUD, then the BBS displays the file and disconnects. (2). Displays the connect string received from the modem. (3). Now, the BBS displays the standard welcome message, and starts to perform the actual login procedure. (4). Check to see if you have a door called FRONTEND , if so it executes it. see section regarding doors for more info. Explanation: To Install the frontend door you have to add the following Line to the 'BBS:COMMANDS/SYS.CMD' File: -------Cut here---------- FRONTEND XM005DOORS:FRONTEND/DOORBEFORELOGON <<< That`s the Door !! -------Cut here---------- Where DOORBEFORELOGON is the door that will be executed right after the welcome message. This is a very flexible option in that it can be used with a door that checks who is online on the other nodes and their activities, and dumps this to one of the first BUllBatch bulls files that are displayed upon login. This is just an example, but it`s there to be explored. For more information on doors, please refer to the docs on advanced Door-Protocols and Implementation. (5). BBS checks if there is a door called "ANSI" in the SYS.CMD, if so it will start the door you insert and will skip the selecting of ANSI or ASCII Colors. Look at Point (4) above for more infos about installing these doors. If the BBS can`t find such a door it will asks if the user wants ANSI graphics or not. If a 'Q' is specified at the end of the line like: "YES Q" or "Y Q" etc. Then the BBS checks if the Option SUPPRESS_QLOGON is on or not if the option is on the BBS will display the Logon.txt because you want to have the users seen it. If the Option is off and the user answers "Y Q" or "YES Q" the BBS will not display the logon or logoff screens. (6). Then if the sysop has specified a SYSTEM PASSWORD it displays a file called: BBS:NODEx/PRIVATE.txt(.gr) then asks for the SYSTEM PASSWORD. The system gives the user three tries and if by then he hasn't gotten it the bbs hangs up, and displays in the callerslog that someone attempted to get the SYSTEM PASSWORD. (7). The bbs displays the file: BBS:NODE{x}/BBSTITLE.txt(.gr) (8). It now asks for the user to enter his FULL NAME, again wildcards are usable and will expand and ask if correct. A user gets five tries at his user name, then the bbs hangs up. (9). Now the BBS checks for a File called BBS:NODE{x}/NOTTHISNODE.TXT and if the BBS finds such a file it will look in it and if there is the name of the User who is online, the BBS will display the Textfile BBS:NODE{x}/NOTTHISNODE.MSG and logs the user off... (10). If the bbs can't find the name supplied it will tell the user and ask him if he would like to 'C'ontinue to join or 'R'etry entering his name again. [C]ontinue as a New User Selected: ---------------------------------- (1). If the bbs has been reserved it will notify the user that the bbs has been reserved for a specific member and will then hangup. (2). If the bbs hasn't been reserved then the bbs checks to see if the user's baud rate is allowed during the time he has called. If so, then the bbs allows the user to continue, otherwise it displays the file: BBS:NODE{x}/NOTTIME{BAUD}.txt(.gr) {x} = Node number, {BAUD} = Current Baud rate. (3). If the sysop has specified a new user password in the config file then the bbs displays the file: BBS:NODE{x}/NEWUSERPW.txt(.gr) Then it asks for the new user password and if the user gets the password wrong it goes back and asks for his FULL NAME again, after 5 tries the bbs hangs up. (4). If the System-Operator wishes to have no more NEW users the bbs would look for the file BBS:NODE{x}/NONEWUSERS then displays it and disconnect the User. And if you wishes to have no more NEW users at a SPECIFIC BAUD RATES, the BBS would look for a file called BBS:NODE{x}/NONEWAT{BAUD}, displays it and then disconnecting the User. {x} = Node number, {BAUD} = Current Baud rate. (5). Now it enters the New Account routines. 1. Search displays BBS:NODE{x}/JOIN.txt(.gr) 2. Asks for full name. At this point wildcards are NOT ALLOWED. The user only has 5 chances to enter it then the bbs says "Too Many Errors, Goodbye!" 3. The bbs checks for use of a name that already exists. If the name already exists it asks again. 4. The bbs checks the name given to see if not in the list of names supplied in the file BBS:NODE{x}/NAMESNOTALLOWED This is a file that contains names that the sysop does not want to allow on the bbs. If the file does not exists the bbs will not allow any new users to log on util the file has been added. This is to prevent someone getting on as ALL or EALL etc. A notice will be placed at the end of the BBS:NODE{x}/CALLERSLOG file. WARNING: You should specify in that list SYSOP, ALL, and EALL 5. Next it asks for the City, State. 6. The it asks for Phone Number (xxx-xxx-xxxx) 7. Next, it asks for the Users personal Password 8. Number of lines on screen (1-255) 9. Clear Screen between Messages ? 10. Display back all info and asks if it is correct if the user needs to change something he just says no its not correct and the process starts again at 2.. 11. At this point the bbs checks to see if there is a script questionaire to ask the user to fill out, it checks for BBS:NODE{x}/SCRIPT{BAUD} {x} = Node number, {BAUD} = Current Baud rate. NOTE: The {BAUD} should be specified as 1200,2400,4800, 9600, 12000, 14400 and 16800 to allow for proper connect handling by USR HST modems. Now the user is asked to fill out the script if existent. A sample script may look like: -------------Cut Here-------------------- What is your Real Name: ~ What is your Real # : ~ What is your Sex,Age : ~ -------------Cut here-------------------- Here, the ~ character is used when a prompt for input by the user is expected. The answers are saved to BBS:NODE{x}/TEMPANS before being validated by the sysop. Once the Sysop validates the User, the answers are copied over to BBS:NODE{x}/Answers. 12. The bbs then displays the file BBS:NODE{x}/JOINED.txt(.gr) (10). Once the system has loaded the users account, it checks to see if the system has been reserved, if so and the user who just logged in is not the reserved user the bbs displays that the system has been reserved for that specific user, and then hangs up. (11). Then the BBS will display the BBS:NODE{x}/LOGON{y}.txt(.gr) texts where x stands for the Node and y for the number of the Logon texts. if there are random Logontexts installed in the BBS:SCREENS Directory this one will be displayed. (12). If the bbs hasn't been reserved then the bbs checks to see if the user's baud rate is allowed during the time he has called. If so, then the bbs allows the user to continue, otherwise it displays the file: BBS:NODE{x}/NOTTIME{BAUD}.txt(.gr) (13). If the users Security level is 0 then the bbs displays the file: BBS:NODE{x}/LOCKOUT-0.txt(.gr) and then hangs up. (14). If the users Security level is 1 then the bbs displays the file: BBS:NODE{x}/LOCKOUT-1.txt(.gr) and then hangs up. NOTE: These two files allow a sysop to be either polite about not allowing a user on the system, or if the user is an abuser, the sysop can have a full blown rude as hell Lockout text for those types of users. (15). At this point the system adds to the end of BBS:NODE{x}/CALLERSLOG that a user just logged in. (16). Now the bbs asks the user for his password, every time the user gets the password wrong the bbs adds what he tried to the end of BBS:NODE{x}/CALLERSLOG. After 3 tries the bbs hangs up and adds this to the Callerslog. (17). The bbs checks to see if the beginning of the username starts with "UUCP." if it does and the user has access to do UUCP, it drops to UUCICO on the serial port. For more information on how to implement UUCP for the Amiga, and with AmiExpress, refer to the section on NETMAIL with Express. (18). Then the standard logon sequence takes place and puts the user at the main command prompt LOGON SEQUENCE FOR A PREVIOUS USER: ----------------------------------- When a user with an existing account logs into the BBS, the login procedure is a lot more simplified. The standard login procedure is listed below: (1). The bbs checks to see if the user has any time for the day if not it displays BBS:NODE{x}/LOGON24HRS.txt(.gr) file to the user and hangs up. (2). If no BULLBATCH files are specified, the BBS looks dor any Bulletin files in BBS:NODE{x}/BULL{SEC}.txt(.gr) where {x} = NODE NUMBER and {SEC} = USERS CURRENT SECURITY LEVEL. If a file is found that matches the user`s security level, it is displayed. For example, a last callers bulletin for standard user security of 20 would be saved in the BBS:NODE{x} directory as follows: BBS:NODE{x}/BULL20.TXT and BBS:NODE{x}/BULL20.TXT.GR. This routine has also been simplified from the sysop's end so that the appropriate bulletins are searched for in a rounded off method. ie: If a user level with security level of 20 has logged in, and the bbs can NOT find an entry for BBS:NODE{x}/BULL20.TXT but finds a file called BBS:NODE{x}/BULL15.TXT, then this file will be displayed. If there is also a file called BBS:NODE{x}/BULL30.TXT, this file will be displayed to users with security level of at least 30 or more. Once the BBS finds the nearest file, it displays that file only. NOTE: Routines have been added to AmiExpress to make sysop setup a little easier and less annoying to the user. The bbs will scan for a peticular file in this method: Say a user with access level 30 just logged in, with ansi color, now the BBS will check first if there is a BULL30.txt and if not the bbs will go on with searching for bulls lower than 30. Look here: BBS:NODE{x}/BULL30.txt.gr BBS:NODE{x}/BULL30.txt BBS:NODE{x}/BULL25.txt.gr BBS:NODE{x}/BULL25.txt BBS:NODE{x}/BULL20.txt.gr BBS:NODE{x}/BULL20.txt BBS:NODE{x}/BULL15.txt.gr BBS:NODE{x}/BULL15.txt BBS:NODE{x}/BULL10.txt.gr BBS:NODE{x}/BULL10.txt BBS:NODE{x}/BULL5.txt.gr BBS:NODE{x}/BULL5.txt BBS:NODE{x}/BULL.txt.gr BBS:NODE{x}/BULL.txt NOTE: because of this method of searching, all files to be searched for must end in either 0 or 5 (as above), the user access level will be rounded down to the nearest multiple of 5 and the search will start there. Thats an example of a search for a file to be displayed, once a file is found that exists it displays ONLY that file. This method is used on the following: BBS:NODE{x}/BULL BBS:NODE{x}/JOINCONF BBS:CONF/MENU BBS:CONF/BULL In some cases it works a little different, in this case the user security is not used, like: BBS:CONF/Bulletins/BULLHELP.txt.gr BBS:CONF/Bulletins/BULLHELP.TXT Thats how that one works and the following are like that: BBS:NODE{x}/JOINED BBS:NODE{x}/LOGON24HRS BBS:NODE{x}/GUESTLOGON BBS:NODE{x}/LOGON BBS:NODE{x}/LOGOFF BBS:NODE{x}/JOIN BBS:NODE{x}/NOTTIMEbaud BBS:NODE{x}/PRIVATE BBS:CONF/FILEHELP NOTE: For multiple bulletins upon login, a BULLBATCH script is used to display the necessary bulletins in the correct order. For more information on this, please refer to the section under BULLBATCH implementation. (3). Initial User specific checks are made: a> The bbs now scans thru all the conferences that the user has access privilege to for any waiting mail. If mail is found, it informs the user about it and asks the user if they want to view it. b> The bbs checks to see if there are any unfinished uploads. If someone looses carrier uploading a file and calls back he will be allowed to resume his/her upload. (4). Then the bbs rejoins the conference the user was in the last time he called. (5). It then checks the file BBS:CONF/NDIRS to see how many, if any, directories of files that specific conference has. This file would look something like this: ---------------CUT HERE------------ 2 ---------------CUT HERE------------ This would specify that there are two file directories where files are kept. A carriage return is necessary after the number. If this file is unavailable, the conference will have NO files available in it, meaning no uploads or downloads will be possible from it. (6). If the number of directories is greater than zero, the bbs looks to see if a file exists called BBS:CONF/FREEDOWNLOADS, if so then all files in this peticular conference are free to download. (7). Now, the BBS scans for any BBS:CONF/BULL{SEC}.TXT(.GR) files in the same method as described earlier on. NOTE: This works exactly like the BBS:NODEx/BULL files. (8). After displaying the available bulletins, if the user is not in EXPERT mode, the bbs displays the available BBS:CONF/MENU{SEC}.TXT(.GR) and reaches the MAIN MENU PROMPT. a> Any command entered at the MAIN MENU PROMPT will be looked up in a BBS:Commands/BBS.CMD file. If the command is found as a module name in that list then the module will be executed. If the command cannot be found, then the command will be compared to BBS:Commands/CONF{x}.CMD and like wise be executed if found. otherwise the command will be considered an internal command and maybe any of the commands listed below. NOTE: Customcommands are totally optional, If you do not have them then don't worry. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ================== 10. The Main Menu Commands of AmiExpress ================= ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: This is a list of commands accessable from the main menu prompt: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ AmiExpress has many functions that are part of the program code that assist users in what they want out of the system. These commands are mostly single letter commands that the user types and hits return for the execution. AmiExpress does not work with a HOT-KEY type of user input. This means that the user will be saved from having to look at a screen load of data when they accidentally hit a wrong key. A carriage return always indicates an intended execution. This section is divided into two parts, The SYSOP ONLY COMMANDS, and The Standard User Commands. First we'll have a look at the Sysop commands. SYSOP ONLY COMMANDS: ~~~~~~~~~~~~~~~~~~~ These commands are the only commands that are called up by single digit number codes. They are available only to users with SYSOP SECURITY LEVELS as defined in the config file by AmiConfig under ACCOUNT EDITING. [ 1 ] - Account Editing: ~~~~~~~~~~~~~~~ This is used to either review existing accounts and modify them, or scan for any new user logins that wish to be validated. The account editing module is very easy to use in that it is basically menu driven. You can also get into the BBSInfo Conf. from here. The Accountediting will look like this: ----------------------------------------------------------------------------- ACTIVE [1] BAUD: 14400 A> Name: ByteMaster B> Location ......: ByteMaster's BBS C> Pass ..........: London D> Phone Number ..: 318-793-4101 (123456789) E> Ratio .........: 0 F> Conf Access ...: XXXXXXXXX G> Ratio Type ....: 0 <-Byte) H> Sec_Level .....: 255 I> Uploads .......: 0 J> AutoReJoin ....: 1 K> Downloads .....: 0 L> Messages_Posted: 0 M> Bytes Uled ....: 1 N> New_User ......: No #Calls: 1 O> Bytes Dled ....: 0 Last Called ...: Tue May 26 22:00:17 1992 Q> Byte Limit ....: 0 Computer Type : Amiga 1000 Y> Cps Up: 0 Z> Cps DN: 0 R> Time_Limit: [9600 ] secs S> Time_Used: [0 ] secs T> UUCP: 0 X=EXIT-NOSAVE TAB=Cont ~=SAVE 1-6=Presets 9=RE-ACTIVATE DEL=DELETE ------------------------------------------------------------------------------ Press the following keys to change the datas of the User: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A> Let you change the name of the User you are looking at B> Let you change the location where the user is living C> Let you change the password of the user you are looking at D> Let you change the phonenumber of the current user E> Let you change the Ratio of the user you are looking at F> Here you can change the Conf.Access of the User G> Let you change the Ratio Type of the User. From here you have 3 different Ratio Types: - Ratio Type 0 = Bytes only - Ratio Type 1 = Bytes & Files - Ratio Type 2 = Files only This ratio type are for choosing in which way the Ratio will be calculated. H> Let you change the Security Level of the user you are looking at I> Let you change the number of Upload the user has done. J> Let you change the Conference at which the User logged in the last time he called the system. K> Let you change the number of downloads the user has done. L> Let you change the number of Messages the user posted in the bbs. M> Let you change the number of Bytes the user uploaded. N> Let you change if the user is a NEW USER or not. this is a flag function. if it is in the "YES" modus the user will be found if ya search for new users. After you edit the Userdatas with a present the flag will be changed automatically to "NO". O> Let you change the number of Bytes the user downloaded. Q> Let you change the number Bytes which the can download at a day. R> Let you change the Time Limit for a day. S> Let you change the Time the user has allready used today. T> Let you change if the User is a User of UUCP or not. Y> Let you change the Top Upload CPS the User ever had. Z> Let you change the Top Download CPS the User ever had. Now followes the normal commands in the Account Editing: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ [ X ] - Exit the Account editing without saving the current changes [ TAB ] - Let you go to the next user who matches to the username you entered before. [ ~ ] - Will save the current changes of the Userdatas. [ 1-6 ] - Will set the Userdatas to a Present of ACP.STARTUP [ 9 ] - This command will re-activate a deleted user. [ DEL ] - This command will delete the user you are looking at. you can re-activate a user by typing "9" at the Accountediting [ + ] - Will go on the next user in the Userdatas. [ - ] - Will go on the previews user in the Userdatas. [ 2 ] - View CallersLog: ~~~~~~~~~~~~~~~ This lets the sysop view the BBS:NODE{x}/CALLERSLOG file backwards. The last line written to the callerslog will be displayed first and the first line of the callerslog will be displayed last. On system running more than one node, this command will ask which NODE's CALLERSLOG to view. [ 3 ] - Edit File Directories (EDITOR/EMACS): ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If you started this Command, the bbs will check if the one who started the command is a remote or a local one. If the one who started it is a local one it will search for a Door called "EDITOR" in the SYS.CMD and if it exists it will be executed and the normal starting of the EMACS will be skipped. If the one who started the command is in REMOTE_LOGON then the command will be executed as follows: This command uses the command line version of MicroEmacs for on-line directory editing. For more information on how to use Emacs, you should refer to the section on COMMON EMACS COMMANDS. This command asks the user which directory to edit before it opens up the appropriate AUX: or CNN: channel and executing EMACS. NOTE: AUX{x}: is used only on remote connections and if active a watchdog task that checks for carrier loss is also invoked. If carrier is lost while editing directories, the computer will be reset withing two seconds. A special note to MULTI NODE systems: The watchdog resets the computer if a carrier is lost regardless of what the other nodes are doing. If users are logged in on other nodes, they will be disconnected when the computer resets. A later version of AmiExpress will send a notification to the other nodes and a time-out requestor locally will inform the sysop and users that express wants to reset the computer and that everyone should finish up what they're doing. Exiting from EMACS with CTRL-X CTRL-C key combination will return the user to the MAIN MENU PROMPT. While a user is in EMACS, the BBS will notify the sysop by placing a line like: User in Emacs........ WARNING! for those of you using the A2232 multi serial card you may run into problems using the editor. We are currently working on a fullscreen editor to take it's place. [ 4 ] - Edit any Text File on System (EDITOR/EMACS): ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ This command is basically the same as the previous with the option to specify full path and file name to edit. This commands prompts the user for the necessary information. [ 5 ] - List System Directories: ~~~~~~~~~~~~~~~~~~~~~~~ This command works just like the AMIGADOS List command and displays the directory and sub-directories available for the specified path. The command can also display any comments (FILENOTES), attached to the files themselves. When selected, AmiExpress will ask for the full path name and whether to include comments or not. [ 0 ] - Remote Shell: ~~~~~~~~~~~~ This Command has been removed currently in this version of express. There are some great door with the same capabilities soon to replace this command. if you choose one of the great doors who are out. Personallity I recommend the version of MALTESE FALCON. then install it as a normal door in your "BBS.CMD" commands and choose the 0 button for that. This sums up the SYSOP ONLY FUNCTIONS of AmiExpress. The Next section deals with the standard commands available to all users. Of course, certain command options can be disabled for specific security levels from the AmiConfig for the config file. REGULAR USER COMMANDS: ~~~~~~~~~~~~~~~~~~~~~ The following are the regular user commands. These commands are explained in detail, and any neccesary pre-requisite for the particular command to work is also outlined. All the commands here can be choosen in the ACP.STARTUP or the normal Config{x}. [ A ] - Alter File Flags: ~~~~~~~~~~~~~~~~ This command allows the user to change the flagged file list without having to do a file listings and get a PAUSE...MORE prompt to change the flags. Chaining data is allowed, or the routine will prompt the user for the information. First it will show the current list of flags. No file flags Filename(s) to flag: (C)lear, (Enter)=none? At this prompt the user can: 1. Enter new files to add to the flag list 2. Enter 'C' to goto the clear flag prompt Filename(s) to Clear: (*)All, (Enter)=none? At this prompt the user can: 1. Enter filenames to remove from the flag list, wildcards are valid, however they will only remove the first entry. 2. Use '*' to remove all entries in the list. 3. Hit Return to exit. Once a user exits the Clear prompt, it will once again show the list of flagged files and drop back to the MAIN MENU PROMPT. [ B ] - Bulletins: ~~~~~~~~~ This command allows the user to view bulletins that the sysop has made available. - Firstly, the BBS checks to see if the file BBS:CONFNAME/BULLETINS/BULLHELP.TXT is available; if not, it tells the user that no bulletins are available in that conference. - If the BBS:CONFNAME/BULLETINS/BULLHELP.TXT is found, it is displayed and the user is prompted to enter the bulletin # to view or '?' to redisplay the BULLHELP.TXT which is the bulletins menu. - If a user selects a valid bulletin #, it is displayed and the bbs returns back to the bulletin prompt. - If a user selects an invalid bulletin #, the bbs informs the user that there is no bulletin #{x} where {x} = the specified bulletin. [ C ] - Comment to Sysop: ~~~~~~~~~~~~~~~~ This command is exactly the same as the regular ENTER MESSAGE command except that the message is addressed privately to the System-Operator. The TO: field is automatically filled with the User name on SLOT 1, which is the Sysop. If the BBS located a file called BBS:ForwardSysopMail then this file will be readed and the first line will be the name of the user the comment will be forwarded. for example: ----- cut here for BBS:ForwardSysopMail ----- CoSysOp --------------------------------------------- Now the bbs will forward the mail also to that user you typed in there. This is very usefull if you go to holiday and want your cosys to read the messages to yeah without typing "R" for read messages. [ D ] - Download File(s): ~~~~~~~~~~~~~~~~ This command accesses the file transfer procedure for sending files from the system to the remote user. The flow-chart for this command is quite complex and is outlined below: 1. If the BBS:CONFNAME/NDIRS is unavailable, or it contains zero, the bbs informs the user that there are no files to download from that conference. 2. The bbs displays the File BBS:CONF/DOWNLOADMSG.TXT 3. The bbs displays the users Download/Upload stats. 4. The bbs calculates the ratio limits the user has before uploading files to the system. 5. Next, it displays the transfer protocol to use. AmiZmodem is the only available transfer protocol at the moment. Cotile is working on implementing XPR transfer protocols so, a later revision will have full XPR support. 6. Now the bbs displays the TOP CPS Downloader in your System 7. If the user had specified 'DS' instead of just 'D' the download is considered a sysop download and if the user's security level is over 200, the download can be made from any valid AmigaDos path on the system. If this is the case, the BBS asks for the full path and filename. NO WILDCARDS ARE ALLOWED with a Sysop Download. 8. The BBS asks the user to enter the filename(s). 9. Checks for special characters in the filename like ":/" etc. If found, tells the users that special symbols may not be included when downloading. 10. Full Wildcards are allowed when doing a regular download, but just the * wildcard character alone is not allowed. 11. Now, the bbs scans the specified paths from BBS:CONFNAME/PATHS and when it finds the file that the user requested, it displays the file length in Kbytes, time required to download it at current baud rate, and checks if the user has enough credits to download the file. If so, AmiExpress checks the filename against what is in existing File Flag list and if it isn't already there, it adds it. So, if the download sequence is aborted for any reason, just hitting "D" again will download the flagged file. To remove from flaglist, the user would use the 'A' command. 12. Now the BBS checks if there is an Comment at the File like "RESTRICTED" or "FREE DOWNLOAD" ... if there is a Comment like this then the BBS will display some messages when the File has a comment like "RESTRICTED" it is not not allowed to download this file and the bbs will write a comment into the BBS:NODE{x}/CALLERSLOG that a user tried to download this File... and with this comment you can`t download this file with a level of 255 and sysop download too.. so the file is 100% save for downloading... if there is the comment "FREE DOWNLOAD" the bbs will make this file free download and it will costs no crediz to download it... 13. After hitting return alone on a filespec prompt, the bbs re-checks the totals to see if the batch is within the user's limits. 14. If so, AmiExpress asks either to start, abort, or automatically logoff at the end of the transfer. The 'G'oodbye after transfer gives the user 10 seconds to change his mind after the transfer before performing an automatic disconnect sequence. 15. At this point the download sequence is about to begin and so the necessary information is written to the BBS:NODE{x}/UDLOG. 16. At the end of the download, if the users' security level is below 255, then the user's number of downloads and number of bytes downloaded get updated with the new download stats. Look at the ACP.STARTUP Command "KEEP_UPLOAD_CREDIT" too. 17. Now the bbs checks if the DownloadCps was higher than the last record. if the CPS is higher than the record it will display a little text that the user is now the fastest Downloader. 18. At this point, the download sequence is completed, and the bbs tells the user his new stats before returning back to the MAIN MENU PROMPT. [ E ] - Enter a Message: ~~~~~~~~~~~~~~~ This command allows the user to leave private or public mail to other users on the system. There are several options with this command and they are outlined below. 1. Asks for who to send it to. If a wildcard is used the search will find the first user that fits the wildcard and will display it and then ask if its correct, if the user says no then it will search forward. If it doesn't find the user it will exit back to the mainmenu prompt. 2. If the user just hits return on the TO: prompt it will send the message to ALL. 3. A feature added in is to be able to leave a message to "EALL" this means to EMAIL ALL people, this is only usable by users with an access level that you specified in the ACP.STARTUP "EALL_LEVEL". What this does is to leave ONE message to ALL USERS , when a person calls the system it searchs for mail in that conference to that user it will say they have mail, from the user that left the "EALL" message. The TO: will show the user who is receiving the message with "(ALL)" after their name. The message can only be deleted by the sender or a user with SYSOP access 4. Another name that is valid in the TO: prompt is SYSOP, this will be replaced by the Name of the SYSOP, in user slot 1 5. Next prompt is the Subject of the message, if the user just hits return it will exit out of the enter message 6. The bbs will now ask if the message is to be readable only by the receiver of the message or it will be public. 7. Now the user has entered the message editor. 8. Tabs now work in the editor, they are indicated by a '|' in the header. 9. Ctrl-X in the message editor will delete the current line. 10. If you hit a return on a blank line you will exit the edit to the edit command prompt. 11. The options are: 1. A)bort - Abort entering the message 2. C)ont - Continue entering the message, this option will print the last line with text and put the cursor at the end of the line. 3. D)elete - Allows a user to delete a specific line. 4. E)dit - Allows the user to change text within a line. 5. F)ile - Allows a user with access 240+ to attach a file to download to the message. This option will ask for the filename to attach to the message and if you wanted the file deleted with the message as its deleted. 6. M)ci List - If you have a MCI Header in yar Message you are able to use this function. This function will display you the whole text with all MCI comment in it. 7. L)ist - List the message to the screen. 8. S)ave - Saves the message. [ F ] - File Listings: ~~~~~~~~~~~~~ This command allows the user get Full directory listings of the catalogs maintained by the BBS. As mentioned before, this is specified in the BBS:CONFNAME/NDIRS file. 1. If the number of directories in the conference is zero or NDIRS is unavailable, then the bbs will display "No files available in this conference." and drop the user back to the main prompt. 2. Displays the file BBS:CONF/FILEHELP.txt(.gr) only if all the options were not specified on the command line 3. It will then ask for the directory to list including the 'H'old directory. The hold directory can only be used by a user with access greater than 200. 4. The specified directory will be displayed and will pause if the NS hasn't already been specified, at the users lines per screen point. 5. On the pause prompt, you can select 'F' for flaging files [ G ] - Goodbye (LOGOFF): ~~~~~~~~~~~~~~~~ This option is used to end the current session with the host system by the remote user. When the user hits 'G', the bbs performs several clean-up functions. 1. First checks to see if there was a ZooMail that hasn't been downloaded, if there was it would ask if the user wanted to leave anyway. 2. The system then checks to see if there were any partial uploads that the user hasn't finished sending yet. If so then it would let the user know and ask if he wanted to leave anyway. If the user didn't want to leave, then the bbs would ask if the user wanted to view the files. If the user did want to view them, then the bbs would go into the resume routine showing the user the filename and filesize, then ask if he wanted to resume on that peticular file. If not then the bbs would ask if the user wanted to delete the file. If the user didn't want to delete the file then the bbs would go to the next file that was to be resumed. 3. If the user hadn't specified the 'Q' at the ANSI color prompt, or the SUPPRESS_QLOGON is given the bbs would display the file: BBS:NODE{x}/LOGOFF.txt(.gr) [ H ] - Help: ~~~~ This command displays the on-line help text file for the user to refer to. At this command, the bbs looks for and displays the file : BBS:BBSHELP.TXT(.GR) and if not found will say that No help is currently available. [ I ] - Information Conference: ~~~~~~~~~~~~~~~~~~~~~~ This Command lets you get into a BBSInfo Conference where the user can see some bulletins like Top Uploader/Downloader/Caller etc. To enable this function for a specificed Level for User you must change the Accessnumber in the DEF.BBS Extended Config for AmiExpress 1. First this Command the bbs displays the Top CPS Downloader and the Top CPS Uploader... 2. Then the bbs checks if the user who locked in has the same or higher Security Level as in the DEF.BBS Extended Config which will be decribed later on. [ J ] - Join Conference: ~~~~~~~~~~~~~~~ This command is used to switch from the current conference to another conference that the user has access privilege to. The BBS looks for the file BBS:NODE{x}/JOINCONF{SEC}.TXT(.GR) and tries to display it. If not found, it will print a message informing the user that the file is missing. Then, prompts the user to enter the number of the conference they wish to join. If the user does not have access to the requested conference, then the bbs will tell the user that they don't have access to that conference. If the user has access to the requested conference, AmiExpress switches to that conference and checks for mail for the user, and then display any appropriate bulletin files if they exist. If the Option "RELATIVE_CONFERENCES" is turned on in the ACP.STARTUP this will only display the Conferences on which the User have access to. [ M ] - Mode Select: ~~~~~~~~~~~ This command switches between ANSI color output or Plain Monochrome output on the users end. When ansi is on, the bbs tries to display files that have the (.GR) extension by default. The normal plain (.TXT) files are reverted to if (.GR) extensioned files are not found. [ MC] - Enter MCI Comment: ~~~~~~~~~~~~~~~~~ This command is the same as the normal "E"nter Message command in AMiEX. ThE only difference is that with that command you can enter the comment to the Sysop MCI commands like displying UserNames or some other datas over MCI. This command will implement the MCI header so you don`t have to insert the MCI header by hand. [ ME] - Enter MCI Message: ~~~~~~~~~~~~~~~~~ This command is the same as the normal "E"nter Message command in AmiEX. The only difference is that with that command you can enter messages with MCI commands like displaying UserNames or some other datas over MCI. This command will implement the MCI header so you don`t have to insert the MCI header by hand. [ N ] - New Files Since Date: ~~~~~~~~~~~~~~~~~~~~ This command allows the user to list files from specified date onwards or from the last time they called the system. In other words, with this command, users can see what the system has to offer in terms of files since their last call. 1. If the number of directories in the conference is zero then the bbs will display "No files available in this conference." and drop the user back to the main prompt. 2. It will then ask for the date they want to list from. The last date they were on will be the default, this is selected by just hitting return alone. Entering the date to list from must be done as MM-DD-YY. 3. Next the bbs asks for the directory to search thru. An 'A' can be used to list all directories, also 'U' can be specified for the upload directory. And H for the hold directory. The hold directory can only be used by a user with access greater than 200. 4. The Pause prompt works the same as described in the file listing section. [ O ] - Operator Page: ~~~~~~~~~~~~~ This command is used by the remote user to call the system operator for on-line chat. 1. if the User is calling up the system operator for the first time on the current session, the users name field be changed to a red color when 3 bitplanes are active, and will have star preceding his name if the bbs was booted in 1 bitplane. Also, if the iconfied window is active, the name filed there will also be highlighted a different color. In this way, a sysop can see if the user on-line has requested to chat. 2. If the F7 Chat toggle flag is not set to allow paging then the bbs says: "Sorry, The SYSOP, is not around right now You can use 'C' to leave a comment." 3. If the chat toggle flag is set to allow paging, then the bbs adds to BBS:NODE{x}/CALLERSLOG that the user paged Then displays "Paging SYSOP (CTRL-C to Abort). ." followed by bells and more dots. 4. If you, the SYSOP, wanted to chat with the user you would Hit F1 to enter chat, then AmiExpress looks for the file BBS:NODE{x}/STARTCHAT.TXT(.GR), and if found displays it to the user. This can be a simple greeting to the user. If this file is not found, then the standard sysop chat active message is sent to the screen. The same F1 will exit chat when you are finished and the bbs will display the File BBS:NODE{x}/ENDCHAT.TXT(.GR). During chat, if ANSI mode is selected, your text will be a different color than the user ones. [ R ] - Read Mail: ~~~~~~~~~ This command is used to access the on-line mailing system to read mail either to the user or for all users. It is also used when a certain message will be replied to. 1. First the bbs shows the read prompt A>gain D>elete F>ile R>eply S>earch Q>uit =Next ( a+b )? (1). A>gain, displays the message currently on again. (specified by the 'a' in the above line) (2). D>elete, allows the user to delete a message only if he left the message or the message is to him. Also a user with access of 210+ can delete any mail. (3). F>ile, will test if there is any Attached File to download. (4). R>eply, allowes the user to reply to the current message. The bbs will place the user on the SUBJECT: field with the previous subject and place the cursor on the end of the line. If the user wants to change the subject he can delete over the existing subject and enter a new one, or hitting return will keep the old subject. After this, the bbs will ask if the reply should be private, and by default this is set to No. Next, the bbs will ask whether to quote the current message in the reply, again the default is No. if the user selected Yes to quote the message, the entire message will be re-displayed and the bbs will prompt the user with the following: Enter Startline,Endline or (*=ALL, A=Abort): Where the user would have to type either a '*' to quote the whole message specify start and end lines seperated by a comma. Then the user would be put in the on-line message editor to enter his message. Commands for the editor work in much the same way as the Enter Message command. For more information, please re-read the ENTER MESSAGE Command. (5). , let you continue search for new messages (6). "EH" - This allows the sysop to edit a messages Header. You can change who the msg is to, from, the subject and whether it is to be a private message. [ S ] - Status of On-Line User: ~~~~~~~~~~~~~~~~~~~~~~ This command simply reports the users' current information pertaining to his account. This is in the form of: (123456789) Conf Access: XXXXXXXXX Caller Num.: 2049 Lst Date On: 05-14-91 Security Lv: 30 # Times On : 579 Ratio DL/UL: Disabled # Downloads: 0 # Uploads : 0 Bytes DL'd : 0 Bytes UL'd : 1 Online Baud: 16800 Rate CPS UP: 0 Rate CPS DN: 0 Screen Clr: NO Bytes Avail: 0 If the option "RELATIVE_CONFERENCE" is turned on in the ACP.STARTUP the Conference Access Information is turned off. [ T ] - Time, at the system site: ~~~~~~~~~~~~~~~~~~~~~~~~ This command reports back to the user what the internal battery backed up clock at the bbs site is set at. Local time/date stamp function. [ U ] - Upload File(s): ~~~~~~~~~~~~~~ This command puts the bbs in the file receive mode, where the remote user can send files to the system. 1. The bbs first checks to see if there are file directories to be uploaded to, by looking at BBS:CONF/NDIRS. If this file is unavailable or reports zero, the user is returned back to the MAIN MENU PROMPT after a message stating "No files available in this conference." 2. If a file called BBS:CONF/UPLOADMSG.txt(.gr) exists the bbs displays that to the user. 3. The bbs now displays the Top Upload Speeders of the System.... 4. The bbs now calculates free disk space, the first number displayed, is the amount of free space on all the drives listed in BBS:AMI_DRIVES DH0: DH1: DH2: DH4: <-- DH3: is not used for the bbs at all therefore it is not in the list. Only drives that contain download files for the bbs should be included, this way the user knows how much free space is left on the total system. The second number displayed is the amount of free space only in the BBS:CONF/UPLOAD directory. This is so the bbs and the user know exactly how much space is available to receive uploads until the sysop does some maintance. Currently the bbs is content to allow uploads until the free space in BBS:CONF/UPLOAD is less than 2000000 bytes 5. At this point the bbs calls the resume routine to check if there are any files to resume on, this works the same as explained under the 'G'oodbye command. 6. The bbs will then ask the user to enter the filenames of the files he will be uploading, or he can press return alone to have zmodem tell the bbs the names. Specifing an 'A' will abort out of upload altogether and drop the user back to the main prompt. 7. If the user enters the filenames, the bbs will check to make sure they don't already exist in the conference, if not the bbs will ask him to enter the description for each file. You can choose in your Extended Config how many lines the User can use for his discription. Entering a blank line to end the description. 8. Next the bbs will display: (Enter) to Start, (G)oodbye after transfer, (A)bort? this works the same as specified in the download routines. 9. At this point if the user has not been added to the end of BBS:NODE{x}/UDLOG he will be. 10. If the Upload will now be started the bbs will check in the file you specified for the NODE* FilesNotAllowed option in ACP if this file is not allowed to be uploaded and will skip the upload. 11. If the Upload finished correctly the bbs checks if the User uploadcps was higher than the last Top Speeder User... if it is higher the bbs will display a little text that the user is now the fastest UploadCps User and then write it down.. 12. The bbs displays the stats from the transfer for all the files. 13. The users time is credited for the uploads. 14. Next the bbs goes thru the files sent and checks to see if the name is longer than 12 characters, if so the bbs asks the user to rename the file. 15. The bbs then checks to see if the user has already given the descriptions for the file, if so it posts it accordingly. 16. If the user has not already given the description the bbs asks for the description for the file. Again giving 8 lines for the description. 17. If the user gets disconnected while entering the description the bbs will put "LOSS CARRIER" for the description. and place the file in the BBS:CONF/LCFILES directory along with a .lc file which will contain a list of all the files he will need to enter descriptions for when he calls back. The Re-Enter description process is done at log on with the PartUploads routine. 18. Once the description has been entered the bbs checks if there is a door called "FILECHECK" in the SYS.CMD customcommand file and if it exists it will be executed and the normal "FCHECK" will be skipped. Here you can use a internal door for checking your files. If the door doesn`t exists express will check if there is a file extension. (a file extension is usually on 3 characters preceeded by a '.'.) Express now compares the extension if any with files of the same extension name in the BBS:FCheck directory. Files in the Fcheck directory specify that you are using external file checkers. The format for each file is as follows ----cut here----