Part 2 ----------------------------------------------------------------------------- DT_TIMEUSED Allows you to retrieve or change timeused today. msg->Command = 114 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be timeused. if msg->Data = 0, then timeused will be msg->String. NOTE: This is in seconds. (FUNCTION #: 114 ) ----------------------------------------------------------------------------- DT_TIMELIMIT Allows you to retrieve or change timeallowed for a user. msg->Command = 115 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be timelimit. if msg->Data = 0, then timelimit will be msg->String. NOTE: Time in seconds. (FUNCTION #: 115 ) ----------------------------------------------------------------------------- DT_TIMETOTAL Allows you to retrive or change total time remaining. for a user today. msg->Command = 116 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be time remaining. if msg->Data = 0, then time remaining will be msg->String. NOTE: Time in seconds. (FUNCTION #: 116 ) ----------------------------------------------------------------------------- DT_BYTESUPLOAD Allows you to retrieve or change bytes uploads per user. msg->Command = 117 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be bytesuploaded. if msg->Data = 0, then bytesuploaded will be msg->String. (FUNCTION #: 117 ) ----------------------------------------------------------------------------- DT_BYTEDOWNLOAD Allows you to retrieve or change bytes downloaded per user. msg->Command = 118 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be bytesdownloaded. if msg->Data = 0, then bytesdownloaded will be msg->String. (FUNCTION #: 118 ) ----------------------------------------------------------------------------- DT_DAILYBYTELIMIT Allows you to retrieve or change a users daily byte download limit. msg->Command = 119 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be bytelimit. if msg->Data = 0, then bytelimit will be msg->String. (FUNCTION #: 119 ) ----------------------------------------------------------------------------- DT_DAILYBYTEDLD Allows you to retrieve or change daily bytes downloaded. msg->Command = 120 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be dailybytes. if msg->Data = 0, then dailybytes will be msg->String. (FUNCTION #: 120 ) ----------------------------------------------------------------------------- DT_EXPERT Allows you to retrieve or change expert mode. msg->Command = 121 msg->Data = 1 or 0 (FUNCTION #: 121 ) ----------------------------------------------------------------------------- DT_LINELENGTH Allows you to retrieve or change user linelength specs. msg->Command = 122 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be linelength. if msg->Data = 0, then linelength will be msg->String. (FUNCTION #: 122 ) ----------------------------------------------------------------------------- ACTIVE_NODES Allows you to retrieve a string of active&inactive nodes. msg->Command = 123 msg->Data = N/A msg->String will be a string 10 bytes in length, with 'X's marking the active nodes. NOTE: This command will surely be changing, the current limit is 9 nodes. (FUNCTION #: 123 ) ----------------------------------------------------------------------------- DT_DUMP Allows you to dump the user's data structure to a specified file. msg->Command = 124 msg->String = FileName (FUNCTION #: 124 ) ----------------------------------------------------------------------------- DT_TIMEOUT Allows you to retrieve or change the door timeout limit. msg->Command = 125 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will equal timeout. if msg->Data = 0, then timeout will equal msg->String. NOTE: This time is in seconds. (FUNCTION #: 125 ) ----------------------------------------------------------------------------- BB_CONFNAME Allows you to retrieve or change the conference name. msg->Command = 126 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be name. if msg->Data = 0, then name will be msg->String. (FUNCTION #: 126 ) ----------------------------------------------------------------------------- BB_CONFLOCAL Allows you to retrieve or change the conference location. msg->Command = 127 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be location. if msg->Data = 0, then location will be msg->String. (FUNCTION #: 127 ) ----------------------------------------------------------------------------- BB_LOCAL Allows you to retrieve the current BBS location. msg->Command = 128 msg->Data = N/A (FUNCTION #: 128 ) ----------------------------------------------------------------------------- BB_STATUS Allows you to retrieve the current status of the node. msg->Command = 129 msg->Data = N/A msg->String will be 'OFFLINE' or 'ONLINE' depending on whether a user is logged onto the node. (FUNCTION #: 129 ) ----------------------------------------------------------------------------- BB_COMMAND Obsolete, DO NOT USE msg->Command = 130 (FUNCTION #: 130 ) ----------------------------------------------------------------------------- BB_MAINLINE Allows you to retrieve the menu prompt arguments prior to the door being entered. msg->Command = 131 msg->Data = N/A msg->String will be the menu prompt arguments. (FUNCTION #: 131 ) ----------------------------------------------------------------------------- NB_LOAD Obsolete, DO NOT USE msg->Command = 132 (FUNCTION #: 132 ) ----------------------------------------------------------------------------- DT_USERLOAD Obsolete, DO NOT USE msg->Command = 133 (FUNCTION #: 133 ) ----------------------------------------------------------------------------- BB_CONFIG Obsolete, DO NOT USE msg->Command = 134 (FUNCTION #: 134 ) ----------------------------------------------------------------------------- CHG_USER Obsolete, DO NOT USE msg->Command = 135 (FUNCTION #: 135 ) ----------------------------------------------------------------------------- RETURNCOMMAND Allows you to specify an internal command to be executed when the door is finished. msg->Command = 136 msg->Data = N/A command to be executed will be msg->String. (FUNCTION #: 136 ) ----------------------------------------------------------------------------- ZMODEMSEND Allows you to send files to the user via Zmodem protocol. msg->Command = 137 msg->String = filename (complete pathname) msg->Data = N/A result of transfer will be in msg->Data, where if msg->Data = 1 , then transfer successful. if msg->Data = -2, then user lost carrier. if msg->Data = 0 , then transfer unsuccessful. (FUNCTION #: 137 ) ----------------------------------------------------------------------------- ZMODEMRECEIVE Allows you to receive batch uploads via Zmodem protocol. msg->Command = 138 msg->String = receive directory path msg->Data = N/A result of transfer will be in msg->Data, where if msg->Data = 1 , then transfer successful. if msg->Data = -2, then user lost carrier. if msg->Data = 0, then transfer unsuccessful. (FUNCTION #: 138 ) ----------------------------------------------------------------------------- SCREEN_ADDRESS Allows you to retrieve the screen address. msg->Command = 139 msg->Data = N/A msg->String will be a string containing the hexadecimal address of the Node screen. (FUNCTION #: 139 ) ----------------------------------------------------------------------------- BB_TASKPRI Allows you to retrieve the priority the node is running at. msg->Command = 140 msg->Data = N/A msg->String will contain the priority of the node. (FUNCTION #: 140 ) ----------------------------------------------------------------------------- RAWSCREEN_ADDRESS Allows you to retrieve the screen address of the node. msg->Command = 141 msg->Data = N/A msg->String will be a string containing the decimal address of the express node. (FUNCTION #: 141 ) ----------------------------------------------------------------------------- BB_CHATFLAG Allows you to retrieve the current chat setting. msg->Command = 142 msg->Data = N/A msg->String will be "ON" or "OFF". (FUNCTION #: 142 ) ----------------------------------------------------------------------------- DT_STAMP_LASTON Allows you to retrieve a date string containing the date of when the user last logged on. msg->Command = 143 msg->Data = N/A msg->String will be the date string. (FUNCTION #: 143 ) ----------------------------------------------------------------------------- DT_STAMP_CTIME Allows you to retrieve a current time string. msg->Command = 144 msg->Data = N/A msg->String will be a current time string. (FUNCTION #: 144 ) ----------------------------------------------------------------------------- DT_CURR_TIME Allows you to retrieve the current time in seconds since January something. msg->Command = 145 msg->Data = N/A msg->String will be the current time. (FUNCTION #: 145 ) ----------------------------------------------------------------------------- DT_CONFACCESS Allows you to retrieve the users conference access. msg->Command = 146 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be access string. if msg->Data = 0, then access string will be msg->String. NOTE: string consists of upto 9 'X' or '_'. ie: 123456789 --------- X_XXXX_XX <-- 'X' = access, '_' = no access (FUNCTION #: 146 ) ----------------------------------------------------------------------------- BB_PCONFLOCAL Reserved, DO NOT USE msg->Command = 147 (FUNCTION #: 147 ) ----------------------------------------------------------------------------- BB_PCONFNAME Reserved, DO NOT USE msg->Command = 148 (FUNCTION #: 148 ) ----------------------------------------------------------------------------- BB_NODEID Allows you to retrieve the Node number for the current node msg->Command = 149 msg->Data = N/A msg->String will be the node number. (FUNCTION #: 149 ) ----------------------------------------------------------------------------- BB_CALLERSLOG Allows you to add a line of text to the callerslog. msg->Command = 150 msg->String = text msg->Data = N/A (FUNCTION #: 150 ) ----------------------------------------------------------------------------- BB_UDLOG Allows you to add a line of text to the udlog. msg->Command = 151 msg->String = text msg->Data = N/A (FUNCTION #: 151 ) ----------------------------------------------------------------------------- EXPRESS_VERSION Allows you to retrieve the current version string of express. msg->Command = 152 msg->Data = N/A (FUNCTION #: 152 ) ----------------------------------------------------------------------------- SV_UNICONIFY Reserved, DO NOT USE without first consulting the author msg->Command = 153 (FUNCTION #: 153 ) ----------------------------------------------------------------------------- BB_CHATSET Allows you to retrieve or change the chat status. msg->Command = 162 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be current status. if msg->Data = 0, then status will be msg->String. (FUNCTION #: 162 ) ----------------------------------------------------------------------------- ENVSTAT Allows you to retrieve or change the current environment stat variable code. msg->Command = 163 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be status. if msg->Data = 0, then status will be msg->String. (FUNCTION #: 163 ) ----------------------------------------------------------------------------- GETKEY Reserved, DO NOT USE. msg->Command = 500 (FUNCTION #: 500 ) ----------------------------------------------------------------------------- RAWARROW Reserved, DO NOT USE. msg->Command = 501 (FUNCTION #: 501 ) ----------------------------------------------------------------------------- CHAIN Reserved, DO NOT USE. msg->Command = 502 (FUNCTION #: 502 ) ----------------------------------------------------------------------------- NODE_DEVICE Allows you to retrieve the node device name. msg->Command = 503 msg->Data = N/A msg->String will be the device string. (FUNCTION #: 503 ) ----------------------------------------------------------------------------- NODE_UNIT Allows you to retrieve the node unit number. msg->Command = 504 msg->Data = N/A msg->String will be the current node number. (FUNCTION #: 504 ) ----------------------------------------------------------------------------- NODE_BAUD Allows you to retieve the initialized baud rate of the node. msg->Command = 505 msg->Data = N/A msg->String will be the init baud rate. (FUNCTION #: 505 ) ----------------------------------------------------------------------------- NODE_NUMBER Obsolete, DO NOT USE. msg->Command = 506 (FUNCTION #: 506 ) ----------------------------------------------------------------------------- JH_MCI Allows you to send mci text to express. msg->Command = 507 msg->String = text msg->Data = N/A (FUNCTION #: 507 ) ----------------------------------------------------------------------------- PRV_COMMAND Allows you to immediately execute an internal express menu command. msg->Command = 508 msg->String = commandstring msg->Data = N/A (FUNCTION #: 508 ) ----------------------------------------------------------------------------- PRV_GROUP Reserved, DO NOT USE. msg->Command = 509 (FUNCTION #: 509 ) ----------------------------------------------------------------------------- BB_CONFNUM Allows you to retrieve the current conference number. msg->Command = 510 msg->Data = N/A msg->String will be conference number ranging from 0 to 8. (FUNCTION #: 510 ) ----------------------------------------------------------------------------- BB_DROPDTR Allows you to drop carrier on a user. msg->Command = 511 msg->Data = N/A (FUNCTION #: 511 ) ----------------------------------------------------------------------------- BB_GETTASK Finds the current nodes task address. msg->Command = 512 msg->Data = N/A msg->task will be the express task address. (FUNCTION #: 512 ) ----------------------------------------------------------------------------- BB_REMOVEPORT Obsolete, DO NOT USE. msg->Command = 513 (FUNCTION #: 513 ) ----------------------------------------------------------------------------- BB_SOPT Obsolete, DO NOT USE. msg->Command = 514 (FUNCTION #: 514 ) ----------------------------------------------------------------------------- NODE_BAUDRATE Allows you to retrieve the current users connect rate msg->Command = 516 msg->Data = N/A msg->String will be the connect rate (FUNCTION #: 516 ) ----------------------------------------------------------------------------- BB_LOGONTYPE Allows you to retrieve the LOGONTYPE. msg->Command = 517 msg->Data = N/A msg->Data will be: 0 = AWAIT_LOGON 1 = SYSOP_LOGON 2 = LOCAL_LOGON 3 = REMOTE_LOGON (FUNCTION #: 517 ) ----------------------------------------------------------------------------- BB_SCRLEFT Allows you to retrieve the screen coordinates. msg->Command = 518 msg->Data = N/A msg->Data will be the Node's Initial leftedge coordinate. (FUNCTION #: 518 ) ----------------------------------------------------------------------------- BB_SCRTOP Allows you to retrieve the screen coordinates. msg->Command = 519 msg->Data = N/A msg->Data will be the Node's Initial topedge coordinate. (FUNCTION #: 519 ) ----------------------------------------------------------------------------- BB_SCRWIDTH Allows you to retrieve the screen coordinates. msg->Command = 520 msg->Data = N/A msg->Data will be the Node's Initial screen height. (FUNCTION #: 520 ) ----------------------------------------------------------------------------- BB_SCRHEIGHT Allows you to retrieve the screen coordinates. msg->Command = 521 msg->Data = N/A msg->Data will be the Node's Initial screen width. (FUNCTION #: 521 ) ----------------------------------------------------------------------------- BB_PURGELINE Allows you to abort serial input. msg->Command = 522 msg->Data = N/A aborts serial input and flushes the serial buffer and sends a request for more input. (FUNCTION #: 522 ) ----------------------------------------------------------------------------- BB_PURGELINESTART Allows you to CLEAR the serial buffer and request more serial input. msg->Command = 523 msg->Data = N/A (FUNCTION #: 523 ) ----------------------------------------------------------------------------- BB_PURGELINEEND Allows you to CLEAR the serial buffer. msg->Command = 524 msg->Data = N/A (FUNCTION #: 524 ) ----------------------------------------------------------------------------- BB_NONSTOPTEXT Allows you to change the NONSTOP text scrolling flag. msg->Command = 525 msg->Data = 1 or 0 if msg->Data = 1, then display text will not pause. if msg->Data = 0, then display text will pause. (FUNCTION #: 525 ) ----------------------------------------------------------------------------- BB_LINECOUNT Allows you to retrieve or change the user's current number of lines viewed. msg->Command = 526 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be current line. if msg->Data = 0, then current line will be msg->String. (FUNCTION #: 526 ) ----------------------------------------------------------------------------- DT_LANGUAGE Allows you to retrieve or change the current language specifications. msg->Command = 527 msg->Data = 1 or 0 if msg->Data = 1, then msg->String will be language. if msg->Data = 0, then language will be msg->String. NOTE: Languages need to be standardized, please what for guidlines. ie: Default language .txt , .txt.gr English .Eng , .Eng.gr German .Ger , .Ger.gr note that this only effects the menus, bulletins & other screen text files. (FUNCTION #: 527 ) ----------------------------------------------------------------------------- DT_QUICKFLAG Allows you to change the QUICKTEXT flag. msg->Command = 528 msg->Data = 1 or 0 if msg->Data = 1, then the QuickFlag will be set. if msg->Data = 0, then the QuickFlag will not be set. (FUNCTION #: 528 ) ----------------------------------------------------------------------------- DT_GOODFILE Allows you to set the results of a tested file after upload. msg->Command = 529 msg->Data = 1,0 or -1 if msg->Data is 1, then the file was not tested. if msg->Data is 0, then the file passed the filetest. if msg->Data is -1, then the file failed the filetest. NOTE: This command is only useful with the sys.cmd door called FILECHECK. (FUNCTION #: 529 ) ----------------------------------------------------------------------------- DT_ADDBIT Reserved, DO NOT USE. msg->Command = 1000 (FUNCTION #: 1000 ) ----------------------------------------------------------------------------- DT_REMBIT Reserved, DO NOT USE. msg->Command = 1001 (FUNCTION #: 1001 ) ----------------------------------------------------------------------------- DT_QUERYBIT Reserved, DO NOT USE. msg->Command = 1002 (FUNCTION #: 1002 ) ---------------------------------------------------------------------------- NOTE!!!!!,, VERY IMPORTANT!!! DO NOT USE ANY COMMANDS THAT ARE NOT DOCUMENTED, SERIOUS PROBLEMS COULD OCCUR. The commands that are Obsolete or Reserved do not use either. At the moment these are the only commands available for AmiExpress Door Interfaces. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ================== 14. TRADITIONAL INTERFACE MODULE (TIM) ================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: The Traditional interface provides the capability to run "DOORS" designed for other Bulletin Board Systems. This is not to say that it will interpret all "DOORS" but some may work. The traditional interface requires a file called PARADOOR, which is supplied with AmiExpress and must be located in a path that AmiExpress can find. If a CARRIER LOSS is detected or a keyboard timeout is detected, the BBS will notify the Module, but it is up to the Module to do an orderly halt. Most door programmers know how to close their doors properly. AmiExpress automatically launches the PARADOOR so please do not run it yourself. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ================= 15. AMIEXPRESS INTERFACE MODULE (XIM) ==================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: My interface is by far the best of all of these put together, it allows you to do a lot of stuff. The best part about this interface is you don't need a seperate program to access it. There will be a lot of Modules out for this in the near future, we have several being made right now. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ===================== 16. CUSTOM COMMANDS FILE FORMAT ====================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Custom Commands is the key to making the new Modules work on AmiExpress All you have to do is specify the Module name you would like users to use, in a file called BBS.CMD or CONF{x}.CMD, this file can go in the BBS:Commands directory. If the Door is listed in the CONF{x}.CMD or BBS.CMD file then the door will be executed. The format is as follows: ~~~~~~~~~~~~~~~~~~~~~~~~ __________ COMMAND TO ENTER MODULE | _______ MODULE TYPE ( SEE BELOW FOR EXPLAINATION OF TYPES ALLOWED) | | ________ MULTI or SINGLE NODE MODULE | || _________ SECURITY ACCESS LEVEL | ||| ________MODULE LOCATION AND FILENAME | ||| | | ||| | v vvv v BB XS020BBS:BulletinBoard Bulletins XM030BBS:BulletinBoard CoSysop XS040WORK:CoSysop/CoSysop Test RM050bbs:rexx/test.rexx spawn RS001pgdoors:hacker/misc/rxx.maint hacker RM100pgdoors:hacker/hacker.strip motel RS090pgdoors:motel/motel! NOTE: That this is a formatted file, The module type must be in position 11 and the path and filename of the module must be in position 16. OPTIONAL RETARD COMMANDS FORMAT ____________ TRUNCATE COMMAND COMPARISON. | __________ COMMAND TO ENTER MODULE | | _______ MODULE TYPE ( SEE BELOW FOR EXPLAINATION OF TYPES ALLOWED) | | | ________ MULTI or SINGLE NODE MODULE | | || _________ SECURITY ACCESS LEVEL | | ||| ________MODULE LOCATION AND FILENAME | | ||| | | | ||| | v v vvv v *BB XS020BBS:BulletinBoard *Test RM050bbs:rexx/test.rexx MODULE TYPE - Module type may be any of the following: X,R,P X = This means the module is an AmiExpress module. R = This means the module is an Arexx module. Which means RexxDoor will be called to execute it. P = This means the module is a Traditional module, so the BBS will launch ParaDoor to execute this module. NOTE: RETARD COMMANDS- Could not think of a better name for it but the '*' at the beginning of the module name indicates that if the first part of the command from the menu prompt matches the module name then it will assume you made a mistake when typing the command, Otherwise it would not find the module name and try to execute an internal command in the BBS. IE: Looking above at the 'Test' Module if we did not have the '*' then a user could accidently type 'Testit'. If this did occur then express would not be able to locate the module named TestIt and therefore execute the internal 'T' command which would result in the user getting the system time instead of the test. Using the RETARD command is a good why of overriding internal BBS commands with commands of your own. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: =================== 17. THE MCI IMBEDDED CONTROL SEQUENCE ================= ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Any text file may contain imbedded control sequences which will send out variable text or cause certain things to happen. MCI - Introducer: ~~~~~~~~~~~~~~~~ ~ This is the MCI introducer, this must be at the beginning of each text file by itself inorder for Express to switch to the MCI interpreter for displaying the text file. MCI - User Specification: ~~~~~~~~~~~~~~~~~~~~~~~~ ~N User Name ~UL User Location ~P User PasswordP ~# User Phone ~TC Total User Calls ~LC User Last Call to the system ~M User Message Posted ~A User Access Level ~S User Slot Number ~CA User Conf. Access **** NOTE CHANGED FROM X **** ~BR User BaudRate ~HW User Computer Equipment ~TL User Inital Time Limit at logon in Minutes ~TR User Number of Mins Remaning today ~UB User Bytes Uploaded ~DB User Bytes Downloaded ~FU User Files Uploaded ~FD User Files Downloaded ~BD User Byte Download Limit ~LG User Logged On-Node ~Dx Change the MCI command terminator. i.e: ~D.| will change the '|' to '.' ~cx Change foreground ansi color to anything from 0-f. ~bx Change background ansi color to anything from 0-f. ~h Back Space ~q Change to default ANSI mode. ~f Clear Screen. ~nx Newlines where x is the number of them you would like ~~ This indicates you wish the ~ symbol to apprear, you can have as many of them as you like after the first ~ to display them (NOTE: no ',' on this command) ~xn Goto X position on screen. ie: ~x10 ~yn Goto Y position on screen. ie: ~y10 NOTE: The above commands allow you to specify a width identifier before the action test.. ie: ~10N would only display the first 10 letters of the username. MCI - System Specification: ~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~SC System Total calls ~CT Show current Time ~DT Show current Date MCI - Extra Specification: ~~~~~~~~~~~~~~~~~~~~~~~~~ ~CR will wait for any key to be pressed. ~CR_Prompt will wait for and prompt the user to press any key. ie: ~CR_PressAnyKey ~SP will do a standard pause, this is useful to put in between each ~SS command. ~SS_Name Show file. This file may also be an MCI file. WARNING: This command could cause a serious loop problem if you tell it to show the same file you are viewing. WARNING: You may need to increase STACK if you nest to many of these files. NOTE: If this command is accessed via the message base or the View or ViewSysop commands, then the file you are going to view has to have a file comment of 'Allowed' or '{xxx}Allowed' {xxx} specifies security level or above ie: {050}Allowed, idicates that only those over or equal to access level of 50 are allowed to view the file. ~CC_Name Launch a door 'Name' is the door's name. ie: ~CC_WHO will look in SYS.CMD, BBS.CMD and CONF.CMD customcommands which must be located in the BBS:Commands directory. ~CL this command will display a list of conferences, commonly used in the JoinConf.txt file ******************************************************************* NOTE: ALL MCI COMMANDS MUST END WITH EITHER A SPACE OR A '|' SYMBOL ALL COMMANDS ARE CASE SENSITIVE!!!!!!!! ******************************************************************* Having a line in a text file that contains: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~N , I hope everything is going well in ~L . Might show: ~~~~~~~~~~ Joseph Hodge, I hope everything is going well in Virginia. ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: =============== 18. COMPLETE LIST OF ALL ACP.STARTUP COMMANDS ============== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: WELCOME TO THE BRAIN OF AMIEXPRESS NOTE: The following commands are for ACP.CTRL, these are not AmigaDos commands, so please do not try and execute it ;) NOTE: All commands must begin in the 1st column of each line. Any commands that you do not wish to implement should have a ';' in front of it, or deleted altogether The command NODE has the following syntax: NODE('*'|node) - where '*' indicates all nodes and 'node' refers to the specific node number. ie: NODE* LEFTEDGE 0 ^ ^ ^ ^ | | | ----- assign 0 to variable LEFTEDGE | | -------- variable | ----- All nodes ------ NODE command NOTE: ALL 'NODE' commands may be placed anywhere in the text file after the NUMBER_OF_NODES specification. They can be in any order you like as long as it is after that specification ------------------------------------------------------------------------------ ACP_PRIORITY x Will Set the Taskpriority of ACP.CTRL to 'x' ------------------------------------------------------------------------------ ITOP 23 Will Set the Window to the specified Coordinates. ILEFT 220 ------------------------------------------------------------------------------ ICONIFY If Set, the BBS will start all nodes Iconfied ------------------------------------------------------------------------------ NUMBER_OF_NODES 3 Will tell ACP.CTRL how many nodes you are running NOTE: 'NODE' commands must not be used before this specification. This is the only restriction in the order of commands in the script file. ------------------------------------------------------------------------------ PUBLICSCREEN AEBench Will let you specify a PublicScreen for ACP to run on If the screen cannot be found then it will be created. If this option is not specified then ACP will use the workbench screen. ------------------------------------------------------------------------------ NODE* LEFTEDGE 0 This speficies the left position of the Express window NODE* TOPEDGE 0 This specifies the top position of the Express window NODE* WIDTH 640 This specifies the width of the Express window NODE* HEIGHT 200 This specifies the length of the Express window NODE* BITPLANES 3 This specifies the number of bitplanes you wish to use This value can range from 0 to 4, this tells express how many colors is allowed for the specified node. BITPLANE 0 = Use WorkBench Screen and colors associated with it. 1 = 2 colors 2 = 4 colors 3 = 8 colors 4 = 16 colors ------------------------------------------------------------------------------ NODE* A2232_PATCH This command will tell express to run A2232 Patch routines, if you do not have a A2232 MultiSerial card, please do not choose this option. This option will allow express to accept ASCII sends. ------------------------------------------------------------------------------ NODE* BREAK_CHAT This Command will turn on/off the ability for yar users to break out of the chat by pressing CTRL-C or to stop the displaying fo files with CTRL-C in the chat. ------------------------------------------------------------------------------ NODE* LOGOFFBATCH This Command let you choose a LOGOFFBATCH which will be executed every time a user logs off the bbs. The should be replaced with a valid pathname ie: BBS:Logoff.bat The logoff batch file may need a script bit placed on it depending on the type of shell interface you are using. If your LOGOFFBATCH scripts do not seem to work then try doing the following: PROTECT +s ie: PROTECT BBS:logoff.bat +s ------------------------------------------------------------------------------ NODE* SHUTDOWN_BATCH This Command let you choose a SHUTDOWN BATCH which will be executed every the bbs will be shutdown. This command is very similiar to the LOGOFFBATCH. ------------------------------------------------------------------------------ NODE* STATBAR If this command is given the Statusbar will be turned on for the specified Node you give to the command. Note: Because of many request and bugs the public screen & right mousebuttonmenu are removed now and the statbar is back in business. Hope ya like it to have the statbar back. ------------------------------------------------------------------------------ NODE* PLAYPEN This Command let you specify where your playpens (where the files fo WHILE uploading and will be moved later to the upload directory) will be located, also will (or should) allow for conferences to be on different partitions if this options is used. NOTE: This command will cause express to creat this directory. There should be a different directory name for each node. NOTE: I do not advise using this in RAM: at the moment This will be implemented later on. ------------------------------------------------------------------------------ NODE* FilesNotAllowed BBS:FilesNotAllowed This command will prevent the uploading of files who are listed in the file BBS:FilesNotAllowed. In this file you can also use wildcards(Joker) for restricting uploading of file with these extensions. ----- cut here for BBS:FilesNotAllowed ----- *.c *.Doc *.WRP ----- cut here ----------------------------- Now the uploading of file with these extensions is not allowed. The BBS will skip the upload if it found a file like the above. ------------------------------------------------------------------------------ NODE* EALL_LEVEL 220 This command lets you choose the Level at which a User can send a message to EALL (ALL) users. If you wish all 100 ACCESS LEVEL users to have the ability then you would put the following in the startup file: NODE* EALL_LEVEL 100 ------------------------------------------------------------------------------ NODE* INTERLACE If this command is given, the specificed Node will be started in interlace mode. ------------------------------------------------------------------------------ NODE* RELATIVE_CONFERENCES If this command is given AmiExpress will handle the Conferences much differently. If you press "J" it will only allow a user to join conferences they have access. They will not know how many conferences are unavailable to them. This command works nice if using the MCI command ~CL in the JoinConf.txt file. The Conference access display at the "S" command will be disabled. ------------------------------------------------------------------------------ NODE* ACTIVATE_WINDOW If this command is given, the specified node will be started directly with a opened window. ------------------------------------------------------------------------------ NODE* EXTCONFIG With this command you choose the filename for the extended config. The extended config is totally optional and will be OBSOLETE in upcoming releases as we merge the extended config commands into the ACP standardized commands. ie: NODE* EXTCONFIG BBS:BBS.def ------------------------------------------------------------------------------ NODE* DUPE_FILECHECK If this command is given, the specified node will check the dir(x) files & dir(x).purged files after an upload, if the file exists in the dir(x) or dir(x).purged, the file will be placed in the sysop hold directory and flagged as a duplicate file. ------------------------------------------------------------------------------ NODE* SUPPRESS_QLOGON If this command is given the specified node will force a user to see your logon/logoff screens. ------------------------------------------------------------------------------ ============================================================================== Now follows all the ACCESS LEVEL things for AmiExpress, that means at which level a User can do something. The following commands are not really needed. You can use the normal Config(x) instead of the following commands. But remeber, never put a ZERO (0) at a ACCESS LEVEL or this function will be disabled for all levels. ============================================================================== NODE* ACCOUNT_EDITING 255 This Command specifies the Security Access at which a user can use the Account Editing It is recommend to put there the access level of 255 so that no other users can use this very important command. ------------------------------------------------------------------------------ NODE* BULLETINS 10 This Option lets you choose at which Level a User can view the Bulletins in your bbs. ------------------------------------------------------------------------------ NODE* COMMENT_TO_SYSOP 10 This Option lets you choose at which level a User can leave a private comment to the sysop. ------------------------------------------------------------------------------ NODE* DOWNLOAD 10 This Option lets you choose at which level a User is able to download any File. ------------------------------------------------------------------------------ NODE* UPLOAD 10 This Option lets you choose at which level a user is able to upload any File. ------------------------------------------------------------------------------ NODE* ENTER_MESSAGE 10 This Option lets you choose at which level a user is able to leave private & ALL messages. ------------------------------------------------------------------------------ NODE* FILE_LISTINGS 10 This Option lets you choose at which level a user is able to view the intern Filelistings ------------------------------------------------------------------------------ NODE* JOIN_CONFERENCE 10 This Option lets you choose at which level a user is able to join other conferences. ------------------------------------------------------------------------------ NODE* NEW_FILES_SINCE 10 This Option lets you choose at which level a user is able to few the Filelistings since his a specified date. ------------------------------------------------------------------------------ NODE* PAGE_SYSOP 10 This Option lets you choose at which level a user is able to page the sysop for a Chat. ------------------------------------------------------------------------------ NODE* READ_MSG 10 This Option lets you choose at which level a user is able to read private & ALL messages. ------------------------------------------------------------------------------ NODE* REMOTE_SHELL 255 This Option lets you choose at which level a user is able to get into the REMOTE SHELL of the system. This is another function which ^^ The Remoteshell has been ^^ should be only accessed by people with a level ^^ removed now so that ^^ of 255. ^ Command is removed ^ NOTE: This command is not required in the current release but in upcoming releasing it will serve a purpose. ------------------------------------------------------------------------------ NODE* DISPLAY_USER_STATS 10 This Option lets you choose at which level a user is able to view his own boardstatistics. ------------------------------------------------------------------------------ NODE* VIEW_A_FILE 10 This Option lets you choose at which level a user is able to view a Textfile in the system. ------------------------------------------------------------------------------ NODE* EDIT_USER_INFO 10 This Option lets you choose at which level a user can edit his own UserInformations like: Handle, Password etc. ------------------------------------------------------------------------------ NODE* EDIT_USER_NAME 10 This Option lets you choose at which level a user is able to change his own username. ------------------------------------------------------------------------------ NODE* EDIT_USER_LOCATION 10 This Option lets you choose at which level a user is able to change his own location where he/she is living ------------------------------------------------------------------------------ NODE* EDIT_PHONE_NUMBER 10 This Option lets you choose at which level a user is able to change his own phonenumber. ------------------------------------------------------------------------------ NODE* EDIT_PASSWORD 10 This Option lets you choose at which level a user can edit his own Password. ------------------------------------------------------------------------------ NODE* ZIPPY_TEXT_SEARCH 10 This Option lets you choose at which level a user can use the internal Zippy Search to search for strings in the FileDir. ------------------------------------------------------------------------------ NODE* OVERRIDE_CHAT 250 This Option lets you choose at which level a a user can also page the sysop if he is not available. ------------------------------------------------------------------------------ NODE* CHAT_COLOR_SYSOP 35 This Option let you choose the colors which NODE* CHAT_COLOR_USER 32 will be used in the SysopChat. ------------------------------------------------------------------------------ NODE* SYSOP_READ 255 This Option let you choose at which level a user can read all the messages in the Confs. The private ones too.. for saver messagebase turn the level to 255. ------------------------------------------------------------------------------ NODE* KEEP_UPLOAD_CREDIT This Option lets specify the way upload credits are stored and also how to keep track of additional time awarded for uploads. maybe any of the following 0 - Do not keep upload credits. 1 - Keep upload credits and award extra time for the current logon session. 2 - Keep upload credits and award extra time to account for duration of the current date. ------------------------------------------------------------------------------ NODE* OVERRIDE_TIMES 255 This Option lets you choose at which level a user can logon at a not allowed baud also without beeing kicked. ------------------------------------------------------------------------------ NODE* TASK_PRIORITY 10 This Oprion lets you choose the Taskpriority for each Node you are running. NOTE: be sure you chosse a lower taskpri then in the ACP_PRIORITY. ------------------------------------------------------------------------------ NODE* START_0300_TIME 0 This Options lets you choose at which time NODE* START_1200_TIME 0 the calling at the baudrates is allowed or NODE* START_2400_TIME 0 not. if you don`t use this options turn the NODE* START_9600_TIME 0 override_times to "0" and it will be disabled. NODE* START_19200_TIME 0 NODE* END_0300_TIME 0 NODE* END_1200_TIME 0 NODE* END_2400_TIME 2359 NODE* END_4800_TIME 2359 NODE* END_9600_TIME 2359 NODE* END_19200_TIME 2359 ------------------------------------------------------------------------------ NODE* PUBLICSCREEN ScreenName This command is similiar to PUBLICSCREEN mentioned above, only this command pertains ^^ REMOVED ^^ to each node vs ACP. If the specified Public Screen does not exist it will be created. Because of many requests and bugs this option is NOTE: If you wish express to open on the removed now. It could be Workbench screen then use this command: that it will be turned back in further AmiEX Versions. NODE* PUBLICSCREEN Workbench NOTE: If this command is omitted then a custom screen will be created. NOTE: The screen name is case sensitive. ------------------------------------------------------------------------------ NODE* STANDARD_COLOR This command tells express to swap the RED/WHITE colors, this option may produce strange visual results, but nothing harmful. Actually I prefer this option. ------------------------------------------------------------------------------- NODE* BBS_NAME BYTEMASTER'S BBS This Command will give AmiExpress your BBS name for the logon screen etc. you can also use ANSI codes in there. ------------------------------------------------------------------------------ NODE* BBS_LOCATION BBS: This tells amiexpress where all the important files are located for the operations ------------------------------------------------------------------------------ NODE* SYSOP_NAME BYTEMASTER This will tell AmiExpress the name of the SystemOperator where the bbs belongs to. ------------------------------------------------------------------------------ ============================================================================== The following commands are togglable, to turn off a feature, place a ';' in front of the NODE command. ============================================================================== ------------------------------------------------------------------------------ NODE* QUIETNODE This Option will turn on/off the ability for users to see you on another node if you are online. This is only interesting for Doors who know to determine the status. ------------------------------------------------------------------------------ NODE* SENTBY_FILES This Option will turn on/off the SentBy: Comments if a file will be upped. ------------------------------------------------------------------------------ NODE* CLEAR_SCREEN_MSG This Option will turn on/off the Clearscreens between each message is displayed. NOTE: This command may override the user screen clear options. ------------------------------------------------------------------------------ NODE* CAPITOLS_IN_FILE This Option will turn on/off UPPERCASE conversion of file names for uploads. ------------------------------------------------------------------------------ NODE* NO_TIMEOUT This option will disabled the nodes timeout routines. This may be useful for direct line communications. And very useful for local nodes. ------------------------------------------------------------------------------ NODE* ALLOW_FREE_RESUMING This Option will turn on/off the ability for users to resume their unfinished uploads ------------------------------------------------------------------------------ NODE* DO_CALLERSLOG This Option will turn on/off the output to the Callerslog of the specified node. ------------------------------------------------------------------------------ NODE* DO_U/D_LOG This Option will turn on/off the UDLOG actions of the specified node. ------------------------------------------------------------------------------ NODE* STARTLOG This Option will turn on/off the StartUpLog actions of the specified node. ------------------------------------------------------------------------------ NODE* DOORLOG This Option will turn on/off the DoorLog actions which will register all action of all doors. ------------------------------------------------------------------------------ NODE* SCREEN_TO_FRONT This Option will turn on/off the ScreenToFront command for a specified node. Then the Express screen will come to front if a user loggs on or a BEEP will be sended. ------------------------------------------------------------------------------ NODE* ONE_TIME_BULLETINS This Option will turn on/off the One Time Bulletins for the specified node. ------------------------------------------------------------------------------ NODE* ZOO These commands are used to turn on the internal NODE* LHARC checking system. Put a ";" before each command to NODE* PKAX turn it off. NODE* WARP NODE* ZIP ------------------------------------------------------------------------------ NODE* DEFAULT_CHAT_ON This Option will turn the ChatFlag automatically to ON for the specified node if the BBS will be started. ------------------------------------------------------------------------------ NODE* VARYING_LINK_RATE This Command is to turn on/off that if a User logged in with a specified baurate this baudrate will be setted to the serial.device too. ------------------------------------------------------------------------------ ============================================================================== - P R E S E T S - The following command are to allow 6 different presets which can be activated by pressing 1-6 at the account editing. So you can make a spec. Userdata to one key.. this is very usefull. This is available in the Config(x) too. ============================================================================== For example here follows how to set it: NODE* PRESET_ACCESS_LVL 01-10 ^ ^ ^ ^ |__ |__ The Command |_ |_____ the Variable | | | | The Node specification identifies the preset 1 ------------------------------------------------------------------------------ NODE* PRESET_ACCESS_LVL 01-10 <-- To set the Accesslevel NODE* PRESET_RATIO_TYPE 01-1 <-- Set the Ratio type for the preset NODE* PRESET_RATIO 01-3 <-- Set the Ratio for the preset NODE* PRESET_DAILY_BYTES 01-90000 <-- Set the Daily ByteLimit NODE* PRESET_CONF_ACCESS 01-X________ <-- Set the Conf. Access for preset NODE* PRESET_TIME_LIMIT 01-2800 <-- Set the TimeLimit for the preset NODE* PRESET_ACCESS_LVL 02-50 NODE* PRESET_RATIO_TYPE 02-1 NODE* PRESET_RATIO 02-3 NODE* PRESET_DAILY_BYTES 02-90000 NODE* PRESET_CONF_ACCESS 02-XX_______ NODE* PRESET_TIME_LIMIT 02-3600 NODE* PRESET_ACCESS_LVL 03-100 NODE* PRESET_RATIO_TYPE 03-1 NODE* PRESET_RATIO 03-3 NODE* PRESET_DAILY_BYTES 03-90000 NODE* PRESET_CONF_ACCESS 03-XX_______ NODE* PRESET_TIME_LIMIT 03-4800 NODE* PRESET_ACCESS_LVL 04-150 NODE* PRESET_RATIO_TYPE 04-1 NODE* PRESET_RATIO 04-3 NODE* PRESET_DAILY_BYTES 04-90000 NODE* PRESET_CONF_ACCESS 04-XX_______ NODE* PRESET_TIME_LIMIT 04-9600 NODE* PRESET_ACCESS_LVL 05-200 NODE* PRESET_RATIO_TYPE 05-1 NODE* PRESET_RATIO 05-3 NODE* PRESET_DAILY_BYTES 05-90000 NODE* PRESET_CONF_ACCESS 05-XXX______ NODE* PRESET_TIME_LIMIT 05-9600 NODE* PRESET_ACCESS_LVL 06-255 NODE* PRESET_RATIO_TYPE 06-1 NODE* PRESET_RATIO 06-0 NODE* PRESET_DAILY_BYTES 06-90000 NODE* PRESET_CONF_ACCESS 06-XXX______ NODE* PRESET_TIME_LIMIT 06-9600 ============================================================================== - M O D E M S T R I N G S - The following commands are only to set your modem to the correct settings to answer AmiExpress. The Settings are you seeing here are very good and can be used if you are using a HST Courier modem or a DUAL modem. For other types the settings can be diverent. ============================================================================== ------------------------------------------------------------------------------ ;NODE* MODEM_INIT ATE0X1S2=255S7=60S27=0S14=1 NODE* MODEM_INIT ATE0F1M0Q0V1X1S0=0S2=255S7=40S12=255 This command let you choose you modemsettings wenn AmiEx is intitalising itselfs you one of the above ones if you are using a HST modem. ------------------------------------------------------------------------------ NODE* MODEM_RESET ATM0H0 This command sets your Modem reset command if a user logged of and the modem begin to reset itself. ------------------------------------------------------------------------------ NODE* MODEM_RING RING This commands indicates the String who will be sended by the modem if someones call the bbs and the modem will indicate a RING on the line. ------------------------------------------------------------------------------ NODE* MODEM_ANSWER ATA This command indicates the Answer string who will be executed if the modem indicates a RING and so the modem will be answer automatically. ------------------------------------------------------------------------------ NODE* MODEM_OFFHOOK ATM0H1 This command allows you to specify which modem commands to send to make the modem go offhook. Default is ATM0H1 ------------------------------------------------------------------------------- NODE* MODEM_HARDFLUSH This command helps the ones of you who have problems with hanging up the modem correctly. This will cause to let express do drop DTR 2 times. ------------------------------------------------------------------------------- NODE* CONNECT_300 CONNECT NODE* CONNECT_1200 CONNECT 1200 NODE* CONNECT_2400 CONNECT 2400 NODE* CONNECT_4800 CONNECT 4800 NODE* CONNECT_9600 CONNECT 9600 NODE* CONNECT_19200 CONNECT 19200 During a modem connect, the connect rate string is sent to express, you must specify with the above above commands the connection rate desired with each connection ------------------------------------------------------------------------------ ;NODE* TRUE_RESET This Command will reset the Modem with a TRUE DTR hangup and later it will be intialized with the MODEM_INIT. This will costs some seconds. ------------------------------------------------------------------------------ ============================================================================== - C O N F E R E N C E S C O N F I G S - The following commands will set the conferences who are available in your bbs and at which directory it is located. ============================================================================== NODE* CONF_NAME 01-VALIDATION <- This will set the Name of the Conf.1 NODE* CONF_LOCAL 01-BBS:VALIDATE/ <- This will set the Directory of Conf.1 NODE* CONF_NAME 02-PUBLIC DOMAIN <- This will set the Name of the Conf.2 NODE* CONF_LOCAL 02-BBS:PD/ <- This will set the Directory of Conf.2 NODE* CONF_NAME 03-/X 2.0 SUPPORT NODE* CONF_LOCAL 03-BBS:AE20/ <- Notice the '/' after the conference location. NODE* CONF_NAME 04-/X 2.0 DEVELOPERS NODE* CONF_LOCAL 04-BBS:DEVELOPE/ NODE* CONF_NAME 05-/X 2.0 BETATESTERS NODE* CONF_LOCAL 05-BBS:BETA/ NODE* CONF_NAME 06-/X 2.0 DISTRIBUTORS NODE* CONF_LOCAL 06-BBS:DISTRIBUTE/ NODE* CONF_NAME 07-/X 2.0 ALPHA-BETA NODE* CONF_LOCAL 07-BBS:ALPHA/ NODE* CONF_NAME 08-/X 2.0 TOP-BRASS NODE* CONF_LOCAL 08-BBS:BRASS/ NODE* CONF_NAME 09-RESTRICTED NODE* CONF_LOCAL 09-BBS:RESTRICTED/ ------------------------------------------------------------------------------ NODE* TOTAL_CONFERENCES 9 This command will tell AmiExpress the total numbers of AmiExpress which you are using now. ------------------------------------------------------------------------------ NODE1 INIT_BAUD 38400 This command will tell AmiExpress at which node AmiExpress should lock at a specified baud. ------------------------------------------------------------------------------ NODE1 UNIT 0 This command will tell AmiExpress the Unit of the serial.device which you are using on a specifid node. ------------------------------------------------------------------------------ NODE1 DEVICE_DRIVER serial.device This command will tell AmiExpress the device name you are using actually for your bbs. ------------------------------------------------------------------------------ NODE* SYSTEM_PASSWORD SYSPASS This command let you choose a system password which will be asked every time a user logson. ------------------------------------------------------------------------------ NODE* NEW_USER_PASSWORD YES This command let you choose a new user password which will be asked every time a new user loggs on. ------------------------------------------------------------------------------ NODE* REMOTE_PASSWORD Shell This command let you choose a remoteshell password which will be asked every time ^^ No Effect at the moment ^^ a user wants to go into the shell. NOTE: This command currently does not effect the BBS, but Modules may use it in the future. ------------------------------------------------------------------------------ NODE* NO_MCI_MESSAGE This command will disable MCI capabilities in the BBS. ------------------------------------------------------------------------------ ============================================================================== - N E W P R O T E C T I O N C O M M A N D S - The BACKUP Option is very useful.. every time you start up your ACP.CTRL it will make a Copy of the File you see above... it will only add a {n} at the end of the file (where n is the number of the copy).. and if ACP.CTRL has done 5 backups it will start again with No.1 ============================================================================== ------------------------------------------------------------------------------ BACKUP BBS:User.Data This command will let you backup a specified file BACKUP BBS:User.Keys which will be backuped every time ACP.CTRL starts. BACKUP S:ACP.STARTUP This command also performs the RESTRICT option mentioned below. The Files you listed here will get backup 5 times then AMiX will start over to overwrite at the first backup. This will prevent you to have millions of backups. ------------------------------------------------------------------------------ RESTRICT BBS:COMMANDS/BBS.CMD With this option you can restrict several files. If someone tries to download one of the files it will be writen down to the callerslog an the download will be canceld. ------------------------------------------------------------------------------ NODE* USERDATA_LOCATION BBS:User.Data With this command you can choose where your User.Data should be located to save it for bad viruses and hackers. ------------------------------------------------------------------------------ NODE* USERKEY_LOCATION BBS:User.Keys With this command you can choose where your User.keys should be located to save it for bad viruses and hackers. ------------------------------------------------------------------------------ STARTNODE0: runback >nil: s:bbs.startup 0 STARTNODE1: runback >nil: s:bbs.startup 1 STARTNODE2: runback >nil: s:bbs.startup 2 With this command you specify how the express nodes should be started. NOTE: Please note that s:bbs.startup in this case is a file containing amigados commands. The main purpose of that is so you can specify a stack size of at least 50000 for each node. If you use this method for starting the nodes, then you must do the following to the file from AmigaDos Shell: PROTECT s:bbs.startup +s ------------------------------------------------------------------------------ IDLENODE0: runback >nil: s:bbs.startup 0 IDLENODE1: runback >nil: s:bbs.startup 1 IDLENODE2: runback >nil: s:bbs.startup 2 This new command is the same as the STARTNODEx: command with the execption that this command will wait for your action on pressing the Nodebutton to activate the specified node. This command is very usefull for your local node, because you don`t need your Local Node very often and so you can activate your local node at every time you want. ------------------------------------------------------------------------------ ;NODE1 TRAPDOOR This Command tells ACP that an external programm will take care of starting the node in question. If this option is used then the external program must start express node with the following command: Express Note: This Option is in the beta stage but if you would like to experiment with it and leave me some feedback it would be appreciated. ------------------------------------------------------------------------------ BUTTON01: AXVal |run >con:0/0/640/100//CLOSE axval <* BBS: 2 WAIT BUTTON02: SalvUser |run >con:0/0/640/100//CLOSE salvuser <* ACP BUTTON03: AERegCards |runback dh1:amigadex/amigadex s:AEREG.CARDS BUTTON04: LaDraw |runback dh1:ansi/ladraw.101 ___^ | column 24 must contain the '|' symbol With this commands you can specify the Buttons on your ACP.CTRL. Here you can install some little Utilities. ----------------------------------------------------------------------------- NUTTON01: Utility |runback dh1:ansi/ladraw.101 This command is the same as the above "BUTTONxx". There is only one difference. if you click on a NUTTON you have to click on the node the programm should be activated. The the bbs will ad the nodenumber to the execution ------------------------------------------------------------------------------ ;LOADCONFIG With this command you can turn on/off the external Config(x) files. if this command is given Acp.CTRL will try to open the Config(x) files for all inform- ations. If it isn`t given, ACP.CTRL will search in the ACP.STARTUP for all the Configs to work perfectly with the Accounts. ------------------------------------------------------------------------------ ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: =========================== 19. NOTEABLE FEATURES =========================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: 1. Command history has been added in to allow up to 20 history lines to be remembered. Once the limit of 20 has been released the history will cycle thru. CTRL-B will reset the history pointer to zero entries. 2. The HELP key performs a screen to background command 3. The bbs checks to make sure the AUXx: or CNN: device can be opened and tells the user if there is a problem. 4. Baud Calling times has been added in, kinda of a throw in and will be changed, but for now, specify the time period a baud rate CAN call, like to allow a baud to call all the time enter 0 for start and 2359 for end. Start time must be a lower number than end time. As I stated this is not perfect and will be removed from the config and a file will contain all the times a baud can't call. It will allow more flexiblity. 5. AREXX port 'AmiExpress_Node.x', supports the following features: suspend - causes the bbs to close the serial port and iconify and wait for a resume command. If someone is online the bbs will wait util they logoff to reply to the suspend message, and then the bbs will suspend. This allows you to create a batch file that will automatically suspend the bbs and load your terminal program and once your finished with the terminal program put the bbs back up. a example Arexx Programm should be like this that the bbs will suspend: ------------- cut here ------------------ /* The Suspend Command for AmiExpress V2.30 */ address 'AmiExpress_Node.1' 'suspend' ------------ cut here ------------------- resume - this command is only used while the bbs is suspended. shutdown - this command will cause the bbs to lower the users time online to 2 mins and tell the user that it has received an emergency shutdown notice. Once the user is off the bbs exits from memory. NOTE: None of these features work without arexx. There will be lots of AREXX commands in the future, including node to node chatting.. 6. Automatic zmodem upload, if a user starts a zmodem upload on the main prompt the bbs will detect this and enter the zmodem upload routines. 7. SYSOP now has the ablity to run a node in the background just for his local use. To do this just remove the device name from the config file and the bbs will not use the serial port. To properly remove the serial device, click in the gadget and hit RIGHT-AMIGA-X that will empty the gadget. 8. When the bbs asks for the number of line on the display it now displays numbers down the side of the screen and asks the user to enter the number he sees at the top of the screen. 9. The addition of customcommands and the Interface to program modules has greatly added to a very flexible BBS, you could just about run a BBS within a BBS with the power this offers the sysop. ----------------------------------------------------------------------------- ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ======================= 20. NOTE WORTHY OF MENTION ========================= ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: I would personally like to thank Mike Thomas, who originally wrote AmiExpress, I still do not know to this day why he choose me to carry on with AmiExpress but I sure am appreciative, It has been a wonderful learning experience in both the programming world and friendships. I would personally like to thank Phil Julias for his hard work on his original documentation for AmiExpress 1.(x) series, It has helped considerably in the developement of the current documentation. I would personally like to thank all of the wonderful people listed on the ACP credits menu. They are great people, and have a lot of patience and enthiusiasm in making express the best BBS program around. I would also like to thank all the users who have helped guide me in the developement of express. It is not to see the devotion that comes from the registered users, more devotion then I ever expected. Enjoy the BBS, once setup will assuredly become second nature to run. It is a fantastic program, and we all have Mike Thomas to thank for it's creation. Please report any errors in this file, or any other file in the official August 1992 AmiExpress Update to: ----------------------------------- AmiSupport (703) 639-6114 ----------------------------------- or if you find a bug in this documentation call: ---------------------------------- MeTAL DeCADE +49(0)711-777-5990 ---------------------------------- Or Mail to: Light Speed Technologies P.O. Box 3016 RadFord, Virginia 24143 ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: ============================ 21. Trouble Shooting =========================== ::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::::: Problem Solution -------------------------------- ----------------------------------- ACP will not start. 1. Make sure ACP.CTRL is being run from the startup-sequence or user-startup. 2. Goto an AmigaDos shell, goto the directory where the command is located and type ACP.CTRL, this should give you an error message indicating that perhaps a file is missing. Express will not start, but ACP will. 1. Make sure that if you are using a batch file to execute express that the batch file has a 's' bit assigned to it, ie: PROTECT S:BBS.Startup +s ^ | batch filename 2. Goto the directory in which express exists and type from a shell: Express 0 ^ |___ (node number) This should tell you why the program is not running. ACP and EXPRESS run but express 1. The stack size of express is not gurus everytime someone enters getting set. You must have a stack the msgbase scan. size of 50000 for this to work. 2. Make sure AE.Library is in the LIBS: directory. ACP comes up but there is no 1. Make sure the statement: NODE buttons. NUMBER_OF_NODES x exists, where x should be replaced with the number of nodes you are going to have. My modems will not initialize 1. Make sure the NODE* UNIT statements reflect the correct UNIT number. 2. Make sure the NODE* DEVICE_NAME is correct. 3. Make sure you have a NODE* MODEM_INIT string in the ACP.STARTUP file. ------------------------------------------------------------------------------ This Documentation was updated by The Bird of X-TRADE For further information call my BBS: ==========================[+49-711-777-5990]=============================== _|____ ______________._________/\ ___ EqUiPmEnT: | \/ |o _ | / \ | | EmPeRaToRs; ~~~~~~~~~~ |o || |_\___|o | // \ |: | ~~~~~~~~~~~ 21øMb OnBoard || \ / |: _|___|| |__// \|_ |._/\ ThE BiRD 384øø/Os2.0 |: |\/| |. |_/ || | /. /\ / || \ S/\/\S AmiX 2.3ø Reg |. | |___|___|_____|___|/ ___\ / |____/ AnDY!/MoTiON |___| | \ / \/|___| J.J.F.! _______ _________._________. \/\ ._______ _________. | \| _ |o _ | / \| \| _ | ============|o |\_ \_ |_\___|| | \___|// \o |\_ \_ |_\___|========= CaLL NoW! || | / / _|___|| | ___// \__| / / _|____ ------>> ============|: |/ /: |_/ |: |_/ /. /\ /|/ /: |_/ |========= |___/___/|. |_____|_______/ ___\ /_/___/|. |_____| | __| \ / \/ | __| [eNf] |/ \/ |/ ø-2 DayZ WaREZ ! | ...where the warez come from... | ø-2 Dayz WaREZ ! ==========================[+49-711-777-5990]=============================== I hope you like this little documenatation of the newest AmiExpress. I think i updated very much. but still some things are missing. so call my bbs and we can make a better update of this Docfile. The Bird. ------------------------------------------------------------------------------ ============================================================================== - C H A N G E S O F A M I E X P R E S S - ============================================================================== Because of some request i decided to release a little file where all changes of the newest AmiEx Version will be written down. This Idea is not new, but it have been lost since the V1.1x version and it is very hard to overwork the hole new doc to see the changes of the newest AmiEx Version. So i hope you will like this little improvement of the new docs. For more Information about AmiEx and it functions call Bytemaster BBS or my own bbs called METAL DECADE BBS the number is > +49-711-777-5990 <. Hope ya call soon. The Bird (AmiEx Devel.Team) ============================================================================== - CHANGES TO AMIEXPRESS V2.30 (?? ??? ???? ??:??:??) - ============================================================================== - Re-Compiled code prior to release of 2.20 due to the numerous probs users were having with 2.20. This removed the Puclicscreens and re-installed the statbar. - Now The Modem Reset has been changed. The Modem will be reseted only one times per logoff. Please report bugs of that if it works. - The NODE* STATBAR is now totally put back into ACP - The BBS Titlebar is changed so that you can view the last user who was online. - Now the Playpen checking correctly identify if a file already exits in another playpen. - There is a new Command installed in the ACP: NODE* PLAYPEN This Command let you specify where your playpens will be located, also will (or should) allow for conferences to be on different partitions if this option is used. NOTE: This command will cause express to create this directory. There should be a different directory name for each node. NOTE: I do not advise using this in RAM at the moment. - NODE* STANDARD_COLOR will be removed in upcoming releases. - The internal FileChecking is totally removed NOW !! It was outdated anyhow. - There is a new Command in the ACP: NODE* FilesNotAllowed BBS:FilesNotAllowed ----- cut here for BBS:FilesNotAllowed ----- *.c *.Doc *.WRP ----- cut here ----------------------------- This command will prevent the uploads of those files. Notice the "*" wildacrd (joker). - Added a new CustomCommand called "Sys.CMD". This is the same as customcommands except that the doors in it cannot be executed from the Menu Prompt or the msgbase. In order for the FRONTEND customcommand it must be moved to Sys.CMD to be executed. Reserved SySCommands for the CustomCommand for further releases: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ *ANSI - Optional Skipping of the ANSI Question *EDITOR - Custom Msg Editor UPDESC - Upload Descriptions MENU - Optional Menu routines *FRONTEND - Optional Front end to express after ANSI (y/n) SHOWFILE - Optional Show File routines SCANMAIL - Optional MsgBase Scanner *FILECHECK - Optional File Checker door MOVEFILE - Optional Upload Filemover *PWFAIL - Optional Excessive Password Failure * indicates that this option is already installed. - The Door Protocols have been modified to use the internal Editor vs the normal door file editor. - The Modem Reset routine at logoff has been modified due to problems with AMiX and the A2232 Multiserial Card. - The BBS Logoff reset for Sysop&Local logins on nodes have been speeded up without serial device. - CustomCommand changes: Now AMiX not longer search for a file called: BBS:Commands/CustomCommands. Now this big Customcommand is swapped between the number of your conferences and 2 extra files. Instead of CUSTOMCOMMANDS you must use the following file names to be run your door: bbs.cmd - use this if you want to have these door everywhere available in the bbs conf{x}.cmd - use this if you want these doors only run in the conference {x} sys.cmd - use this for door you don`t want to run from the menu prompt or message base. this is for doors like FRONTEND. watch out for more like this for example: bbs.cmd - the doors in there will executed everywhere conf1.cmd - the doors in there will executed only in Conf.1 conf2.cmd - the doors in there will executed only in Conf.2 - Fixed a bug with the chattoggle which getting not updated when the F7 key was used from the node, now Express nodes tell acp when to change the chat flag on the acp window. Note: Modifications to the modem init sequence may cause probs if you do not have an A2232, if this is the case let me know as soon as possible, the problem should be obvious if it exists,, I suspect that the modem will not answer calls if there is going to be a problem at all. - Found a new function in AmiExpress which were never been discripted: You can have a file called "BBS:ForwardSysopMail". if this file is available amiexpress will open it if you want to leave a comment to the sysop. AMiX will look into and read the first line. in the first line should be a name of a user in your bbs that you want to also read the messages to the sysop. for example: ----- cut here for BBS:ForwardSysopMail ----- CoSysOp ----- cut here ------------------------------ Now the bbs will forward the mail also to that user you typed here. This is very usefull if you go to holiday. Use it. - when express is searching it searchs now in BBS:UTILS for PARADOOR & REXXDOOR. This will help them quicker by knowing exactly where they are located. NOTE: All References to BBS: is meant to indicate the BBS location, it is not really hardcoded references to BBS: , you may have in your case MYBBS: or something like that. - Obsolete functions are now totally removed. This should reduce the size of the code somewhat. - A new Door Protocol Command have been added called BB_LOGONTYPE, this will allow doors to know if someone logged on locally or remote. - Some new SysCommands have been added to Express. This SysCommands should be added to SYS.CMD like the "FRONTEND" routine. ANSI - This will replace the AnsiGFX Question after Logon EDITOR - This module must be created for message editing and dir editing with the 3 & 4 menu prompt commands. There is a module I created named AUXED version 1.0 which will let you define your own external editor to use for local logins. Remote logins will use the standard emacs interface until some new editors are designed. FILECHECK - This Module will bypass the internal FileChecking for uploaded Files. Keep in mind, if this module is created it will cause express to ignore anything in the FCheck directory. PWFAIL - This Module will be executed everytime someone has an excessive Password Failure problem. - New Door Command have been installed: DT_LANGUAGE This allows you to retrive or change the current language specifictaions. You only can execute this through a door. example: Default Language ".TXT" , ".TXT.GR" English Language ".ENG" , ".ENG.GR" German Language ".GER" , ".GER.GR" a.s.o - Installed new ACP command in the acp.startup called: NODE* MODEM_HARDFLUSH THiS Command will help the guys of you having probs with the Modem Resets. - Changed the calculation of the downloaded & uploaded bytes if you press "U" or "D" and now you seeing the 100% Kilobytes instead of the old 1024 Bytes calculation. - There have been added a Lost Carrier Zoom Mail routine which will check if the user gets a Lost Carrier in the Zoom Mailing routine. Then the computer will make a reset. - The Filechecking routines have been modified to allow the Filecheck door to tell AMiX to check the file with it`s own procedures. - The SySoP Account Sequence has been modified to record CallersLog- divider. - The Logon Sequences has been modified to obtain permission for the callerslog prior to any logons. - The AE.LIBRARY has been removed to due some problem. But don`t delete it.. some Doors could use it in further releases. - The Attach File prompt in the msgbase has been modified, so that the (y/N/goodbye) now has 'N' as the default. - Zoom Mailing has been modified so it will not reset the node during local logins. - Express has been modified to store important Data in MSG type semaphores, that would pertain to info needed in the WHO type Door the goal is to provide the means of getting the needed information without the doors having to view the callerslogs etc. - ACP Menu Colors has been modified, when used on the WB Screen, looks a little more professional now. - Modified ZModem Stats Window to be centered in the NodeWindo for the nodes opening on the WB Screen. - New Info added that is set to ACP when a user is loggin on. Before the user`s account is verified the ACP will show Accounting Sequence, then after that it should show logging on. - The User`s Location has been removed from TiTleBars for Express Nodes - The "K" Node List Commando has been totally removed from the AmiExpress Code because it is not needed in further version because of so many Doors much better than that command. - TitelBars has been modified to refelct AmiEX version & Node Number while the stat bar is on, and while the statbar is off, it will display the last accounts or current user account info. - New Command has been added to ACP: NODE* QUIETNODE This Command will toggle the ability for others to see you are on another node or not, this is only good if the utils such as the WHO Doors and MultiNode Chats, know how to determine the status. - New function implemented in the Enter Message command: Now able to view the whole MCI commands in the entered text before saving it. M)ci List <--- new function in "E" command. - The Search function in the Read command has been tottaly removed from amiex because of some problems caused of this. - The ACP Server has been modified to show files being downloaded or uploaded. - a WHO Door has been installed to the internal AmiEX Commands. with this Command you can view the other users who are online at the other node and what they are doing. - The ACP Server has been modified to show the Baudrate at which a user is online at the moment. - Installed a New ACP Command: NODE* BREAK_CHAT This Command will turn on/off the ability for yar users to break out of the chat by pressing CTRL-C or to stop the displaying fo files with CTRL-C in the chat. - Express has been modified to allow the Infinite Conference handling. The whole documentation for this will provided later if a new Account Editor has been finished. - Found a new function in AmiEX Main Menu Commands: [ 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. - Found a new function in AMiEX Main Menu Commands: [ 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. ============================================================================== - CHANGES TO AMIEXPRESS V2.20 (24 AUG 1992 13:30:32) - ============================================================================== - Fixed some bugs in the older version - All the Further docs will be written by THE BIRD - The Remote Shell has now been totally removed from the system because its not very save against hacking and you can now install your own door for the remote-shell. so look out for great Door. And so the command NODE* REMOTE_SHELL 255 has been removed too. - Included a little new things which will show if the ratio of a user will be counted as BYTES,FILES or BYTES&FILES only. this will be shown in the Account Editing screen. - There is a new Textfile "BBS:NODE{x}/NoTThisNode.TXT" and "BBS:NODE{x}/NoTThisNode.MSG". in the first file with the extend ".TXT" you can insert people who are not allowed to log into the node where this textfile is located. Every Time a user loggs in the bbs checks out the file and if it found a user who is not allowed to insert the node where this textfile is located it will display the "BBS:NODE{x}/NoTThisNode.MSG" file and loggs the user off. This function is very usefull for MultiNodeSystems where you want to prevent a specified user to log in your PRIVAT ELITE Node. - Included some new functions for ACP.STARTUP: ------------------------------------------------------------------------------ IDLENODE0: runback >nil: s:bbs.startup 0 IDLENODE1: runback >nil: s:bbs.startup 1 IDLENODE2: runback >nil: s:bbs.startup 2 This new command is the same as the STARTNODEx: command with the execption that this command will wait for your action on pressing the Nodebutton to activate the specified node. This command is very usefull for your local node, because you don`t need your Local Node very often and so you can activate your local node at every time you want. ------------------------------------------------------------------------------ The ACP Commando NODE* STATBAR is totally removed and replaced with the right mousebutton menu in each node where you can view all the userinformation about the user who is online in the node you are viewing. ------------------------------------------------------------------------------ NODE* PUBLICSCREEN ScreenName This command is similiar to PUBLICSCREEN mentioned above, only this command pertains to each node vs ACP. If the specified Public Screen does not exist it will be created. ------------------------------------------------------------------------------ NODE* STANDARD_COLOR This command tells express to swap the RED/WHITE colors, this option may produce strange visual results, but nothing harmful. Actually I prefer this option. ------------------------------------------------------------------------------ NODE* NO_TIMEOUT This option will disabled the nodes timeout routines. This may be useful for direct line communications. And very useful for local nodes. ------------------------------------------------------------------------------ NODE* MODEM_OFFHOOK ATM0H1 This command allows you to specify which modem commands to send to make the modem go offhook. ------------------------------------------------------------------------------ NODE* NO_MCI_MESSAGE This command will disable MCI capabilities in the BBS. ------------------------------------------------------------------------------ NODE1 TRAPDOOR This Command tells ACP that an external programm will take care of starting the node in question. If this option is used then the external program must start express node with the following command: Express Note: This Option is in the beta stage but if you would like to experiment with it and leave me some feedback it would be appreciated. ------------------------------------------------------------------------------ ============================================================================== - CHANGES TO AMIEXPRESS V2.?? (?? ??? ???? ??:??:??) - ==============================================================================