Renegade Bbs Manual 1

DOC 1.1 documentation file ----------------------------------------------------------------------Please note - this is a plain ASCII text file containing multiple documents. You may find it most convenient to view or print this file using the DOC.EXE program supplied. ----------------------------------------------------------------------Title1:Renegade Start-up Title2:Volume 1 Copyright:(C)1992 Cott Lang Enterprises @@Installation INSTALLING RENEGADE ___________________ To install Renegade, follow these steps, and it will be basically setup. 1) Type "MD [BBSPATH]" where [BBSPATH] is the path on the drive where the BBS will be located (like C:\BBS). 2) Change directory to BBS Path by typing "CD [BBSPATH]", then change to the drive where [BBSPATH] is located (like C:). 3) Unpack the Renegade Archive by typing "[PATH] Renegade", where [PATH] is the path to where the Renegade.Exe archive is. 4) Type "INSTALL". a) Install will ask for the directory to install Renegade to. Enter "[BBSPATH]" as above. b) Install will now do some disk access, then ask for the directory where the external protocols are to be stored. The external protocols are the files such as DSZ.EXE and GSZ.EXE, etc. Most setups have "[BBSPATH]\PROT". (You might want to grab the file RGPROT10.ZIP. It has a bunch of protocols and the Data file for Renegade to use them all.) c) Install will now ask where the external archivers are to be stored. These files are the files Pkzip, ARJ, etc... Most setups have "[BBSPATH]\ARCS". 5) Run the batch file "INST" which should be in the Renegade archive. This will delete unneeded files, and then instruct you to delete it. 6) You should now be at the Waiting for Call screen. Press "S" and go through the System Configuration, setting the BBS up as you want. 7) If you haven't already, get ahold of a Fossil Driver (such as X00 or BNU), and install it.

Renegade needs one to run. That should be all you need to do to install Renegade. If you didn't get the INST.BAT file in the Renegade Archive, or off the BBS you got the original archive from, the files you can delete after installation are "INSTALL.EXE, README.NOW, RGMAIN.DAT, RGMISC.DAT, RGMENU.DAT and RGDATA.DAT". These files were only needed by the install program, and aren't needed by Renegade again. OTHER INFORMATION _________________ Renegade 06-11 now has RIP graphic emulation support, which is a advanced grahpics emulation language. RIP isn't a creation of Cott Lang's, so I can't include the documentation as a creation of mine. The docs are in the archive file from a file I found on a local bulletin board explaining the commands to use. Renegade is still in Beta testing which anyone running Renegade is doing. Even though it says to Register the program, there is currently no way to do so. As soon as the program is in a way that is mostly bug-free, and is good enough to be released, it will be out of Beta testing and be released to the general public. @@System Startup SYSTEM STARTUP ______________ To start the BBS, change to the main BBS directory and execute the "RENEGADE" program. Renegade requires that you have at least 285K of available memory, have at least a 80186 processor, and a fossil driver. Common fossil drivers are X00 and BNU, which are both found on most local BBS's. The Command Line Parameters are as follows: -Bnnnnn This command tells the BBS program a user is on the modem at nnnnn baud. This skips the WFC screen and goes directly to the BBS. -EEnnn If a critical error occurs during the operation of the BBS, it aborts to DOS with an ERRORLEVEL value of 254. -ENnnn Normally, when you perform a normal exit back to DOS, the program returns an ERRORLEVEL value of 0. -L Operate the BBS in local mode only (don't send anything out to the modem, and don't respond to incoming calls). -Mn Will create a QWK mail packet for user n then return to DOS.

-Nn If you're running in a multi-node environment, use this to execute the BBS on node n. -P

Pack the message bases and return to DOS.

-S Sort the File areas and return to DOS. Same as Pack Message Bases, except it will sort the file bases. -Q

Quit to DOS after the next user logs off.

-Un Will upload a REP mail packet for user n then return to DOS. -Xnnnn External event start time in minutes. @@WFC Statistics WFC STATISTICS -------------Time/Date: The current time and date. Today's Stats: Calls - # of calls today Posts - # of public postings today Email - # of Electronic Mail parcels that was sent today Newusers - # of new users today Feedback - # of feedbacks that were sent to you today # UL - # of Uploads today Kb UL - How many K was uploaded today # DL - # of Downloads today Kb DL - How many K was downloaded today Minutes - # of minutes the board was used today System Averages: Calls - The average Posts - The average # UL - The average # DL - The average Activity - The average System Totals: Calls - Total Posts - Total # UL - Total # DL - Total Days - Total Hours - Total

# # # # # #

of of of of of of

# of calls per day # of posts per day # of U/Loads per day # of D/Loads per day activity (in %) per day

calls the BBS has had posts the BBS has had Uploads the BBS has had D/Loads the BBS has had Days the BBS has been online Hours the BBS has been online

Other Info: Node - Which node is currently on screen Errors- How many fatal errors occurred today Megs - Megabytes left free on the current Drive Mail - How many pieces of E-Mail you currently have in your mailbox Users - Total # of Users the BBS currently has Overlays - Where the BBS loads itself into System Activity: % of use the BBS has had today @@WFC Commands

WFC COMMANDS -----------A Sends the "modem answer" command to the modem. It is normally not used, but for testing the connections and when you have an error, this is helpful. In most cases though, the BBS will automatically answer the phone by itself. B Enters the message base editor, where you can insert and modify the bases used to store public messages. C

Displays a list of callers for the day.

D Shells to DOS, allowing you to perform maintenance and other functions that aren't available through Mini-DOS. To return to the WFC menu, use the "EXIT" command. E Enters the schedule event editor, where you can insert and modify the different scheduled events used to perform different functions to maintain the system & other things. F Enters the file base editor, where you can insert and modify the bases used to store files for uploading and downloading by users. H Sends the "modem hangup" command to the modem, which hangs up the modem if it is offhook. WFC command "O".

See

I Sends the "initialization" command to the modem, used to initialize the modem. L Displays the SysOp logs. You can display today's log, or the logs of previous days (up to the number of days specified in the system configuration). M Allows viewing of ALL Email messages that have been posted. It does not specify for the viewing of a certain individual's Email. See WFC command "R". N nodes.

Lists the current users that are on your Useful only on multi-node systems.

O Sends the "offhook" command to the modem, which makes the line busy to all remote callers. Use the "H" command to hang up the phone. P Allows you to pack all of your message bases in case you need to do so. Q Exits the BBS and returns to DOS with the "normal exit" ERRORLEVEL value. R

Allows you to read a specific individual's

Email messages. S Enters the system configuration, where you can perform most of the major changes and modifications to the BBS. U Enters the user editor, where you can modify the modify the information for each user of the BBS. V Enters the voting editor, where you can enter and modify the voting booth questions, as well as view information on the different topics. W Allows you to send Email messages to other users, either individually or via various mass mail criteria. X Enters the protocol editor, where you can enter and modify the definitions of the file transfer protocols used to transfer files. Z Displays the usage log information contained in the HISTORY.DAT file, which contains a record of all general system activity. Just to note, the percent activity is roughly the number of minutes used that day divided by 1440 minutes (24 hours). # Enters the menu editor, where you can create and modify the BBS menus. ! Validate files - If you set files to not be auto-validated in the System Config, this will allow you to validate the files manually or automatically. [SPACE] Allows you to log on to the BBS locally. You can log on normally (by pressing "Y"), log on quickly (by pressing "F"), or not log on at all (by pressing "N"). $ Takes you into the conference editor. to keep message bases or file bases separate in sub-groups.

Useful

If local security is set to on, there are only 2 commands that become available on the keyboard. (This is useful if the BBS is in a space where many people pass by and can cause great damage to the BBS.) The only two commands which are allowed are [SPACE] and "Q". [SPACE] brings up a prompt for the system password. Entering the correct password will allow the use of all WFC menu commands. @@Sysop Function Keys SYSOP FUNCTION KEYS ------------------The following function keys are available only when a user is online:

(Key: A:x = Alt key+x key together.) [A:B] Toggles "beep-after-end" on and off. This feature will take the phone offhook and sound an alarm when the user logs off, letting you know that the system is available for use. [A:C]

Toggles chat mode on and off.

[A:E] Allows modification of the user's security information (SL, DSL, AR & AC flags, file points). Prints the "SysOp working" message to the user while this window is displayed. [A:F]

Prints fake line noise to the user.

[A:G] Allows enabling and disabling of activity trapping and chat capturing for a user. [A:H] menu.

Hang up on a user and return to the WFC

[A:I]

Toggles the user input on and off.

[A:K] Allows you to select a hangup message to display (HANGUPnn.*) before hanging up on the user and returning to the WFC menu. [A:L]

Toggles the local screen on and off.

[A:M] Toggles temporary SysOp access for a user. If temporary SysOp access is still active when the user logs off, the user's statistics are returned to normal. [A:N]*16 order.

Switches you to the next SysOp window in

[A:O]

Conference System toggle.

[A:P]

Prints a file from disk to the user.

[A:Q] alarm.

Turns off the "user attempted to chat"

[A:R]*16 window.

Displays the chat reason in the Sysop

[A:S]

Toggles the SysOp window on and off.

[A:T] Toggles the SysOp window display between the top and bottom of the local screen. [A:U] and off.

Toggles the user's input and output on

[A:V] Asks the Sysop for the Subscription Security Level to give to the user.

[A:W] Same as [A:E] except that the "SysOp working" message is not displayed. [A:Z] Sends a continuous stream of beeps until the user presses a key or hangs up. [A:+] time left.

Adds five minutes to a user's total

[A:-] Subtracts five minutes from a user's total time left. [A:F1-F5]*16 Changes to SysOp Window 1-5 depending on which Function key you hit (F1-F5) [F1-F10] Hitting one of these keys will activate the Sysop Defined Macro that was defined in System Variables. [Ctrl:Home] Shows a help screen with all of the SysOp function keys and a brief description. The following function keys are available anywhere in the system, whether or not a user is online: [A:n] Executes a batch file called "GLOBATx.BAT", where "n" is a number from 1 to 9. [A:D] Dump screen to file - Puts a copy of the current screen into a certain file (definable). [A:J] Performs a local shell to DOS. Prints the "SysOp has shelled to DOS" message before entering DOS, and the "thank you for waiting" message after returning. [Scroll Lock] Toggles the "SysOp available for chat" flag on and off. [Ctrl:SysRq] Allows the SysOp to choose to generate a run time error. @@ACS System ACS SYSTEM ---------Most of the ACS functions have the same basic syntax: A letter followed by the parameter of the function (not case sensitive). Function : Description: Access req.:

"Annn" Age of user Must be at least "nnn" years old.

Function : Description: Access req.:

"Bnnn" Baud rate without last two zeros Must be connected at "nnn"00 baud.

Function : Description: Access req.:

"Cx" Conference Must be in Conference x (@-Z).

Function : Description: Access req.:

"Dnnn" DSL Must have DSL of "nnn" or higher.

Function : Description: Access req.:

"Ex" Emulation Must be in x emulation. (A=ANSI,V=AVATAR,N=NONE)

Function : Description: Access req.:

"Fx" AR flag Must have AR flag "x" (A-Z).

Function : Description: Access req.:

"Gx" Gender Must have gender "x" (M/F).

Function : Description: Access req.:

"JJ" Novice Mode Must not be in Expert Mode.

Function : Description: Access req.:

"Knn" Message Base Must be in Message Base #nn.

Function : Description: Access req.:

"Lnn" File Base Must be in File Base #nn.

Function : Description: Access req.:

"MM" Voting Must have voted on all of the voting topics.

Function : Description: Access req.:

"Nnn" Node Number Must be on node #nn.

Function : Description: Access req.:

"OO" Sysop Status True if Sysop is available.

Function : Description: Access req.:

"Pnnn" File points Must have at least "nnn" file points.

Function : Description: Access req.:

"Rx" AC flag Must have AC flag "x" (LCVBA*PEKM1234).

Function : Description: Access req.:

"Snnn" SL level Must have an SL level of "nnn" or higher.

Function : Description: Access req.:

"Tnnn" Time left Must have at least "nnn" minutes of time left online.

Function : Description: Access req.:

"Unnn" User number Must be user number "nnn".

Function : Description: Access req.:

"VV" Validation Must be a validated user.

Function : Description: Access req.:

"Xnn" Subscription expiration "nn" must be greater than or equal to the number of days remaining before the user's subscription expires.

Function : Description: Access req.:

"Ynnn" Time of day Must be at least "nnn" minutes after midnight.

Function : Description: Access req.:

"ZZ" Within Post/Call Ratio Must have enough posts per call for their SL.

Some examples: "A21" "B96" "FS" "T20" "Y360" "N1"

-

Must Must Must Must Must Must

be 21 years old. be connected at 9600 baud or higher. have AR flag "S". have at least 20 minutes time left. be later than 6:00 am. be logged onto node 1.

For added ACS control, there are five logical operators that can be used. For access to happen: ~~~~~~~~~~~~~~~~~~~~ "&" - Logical AND - both must be true "|" - Logical OR - either can be true "!" - Logical NOT - first is true second isn't These are the all on/off settings: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ "^" - Logical TRUE - everything is true "%" - Logical FALSE - everything is false Examples: ~~~~~~~~ AND - "S20D50" requires the user has an SL of 20 *AND* a DSL of 50. OR - "S20|FA" requires that the user have either SL 20

NOT - "!FA"

*OR* AR flag "A". requires that the user *NOT* have AR flag "A".

The TRUE and FALSE operators are used to give everyone access, or to not give anyone access. "^" means ALL users have access, and "%" means NO users at all have access. For even more complex ACS's, parentheses are allowed to group ACS settings together to be compared to another set: "(S20FA)|(D255)" means that the user must have SL 20 *AND* AR flag "A" *OR* DSL 255. A few more examples: S50 !S50 VV|U1 A21FAS50

User User User User flag !(A21FAS50) User flag !N234 User @@MCI Codes MCI CODES _________

must have SL 50 or higher (50-255). must *NOT* have SL 50 (0-49). must be validated *OR* be user #1. must be 21 years old *AND* have AR "A" *AND* have SL 50. must *NOT* be 21 years old, have AR "A", or have SL 50. must *NOT* be logged onto node 234.

Renegade has a system for displaying system information in all locations on the board. This is done using a set of codes called MCI (Message Command Interpreter). These codes are entered with the character "@" followed by a specific character. All the valid MCI codes are listed below. NOTE!: MCI commands are CASE SENSITIVE! ~~~~ @A @B @C @D @E @F @G @H @I @J @K @L @M @N @O @P @Q

Displays the current user's user name minus the user number. Displays the current user's entire real name. Displays the current user's real first name. Displays the current user's real last name. User's phone number User's street address User's City/State User's Zip Code User's Security Level User's Download Security Level User's last call date User's total number of calls Displays a carriage return/linefeed. User's number of files downloaded User's number of files uploaded User's kbytes downloaded User's kbytes uploaded

@R @S @T @U @V @W @X @Y @Z @0 @1 @2 @3 @4 @5 @6 @7 @8 @9 @# @! @~ @& @a @b @c @d @e @f @g @h @i @j @k @l @m @n @o

User's number of posts User's number of downloads today User's kbytes of downloads today Displays the number of file points remaining to the current user. Displays the amount of time online remaining to the current user in the format "HH:MM:SS". Displays the current message board name. Displays the current message board number in the format "#xxx". Displays the current file board name. Displays the current file board number in the format "#xxx". Node Number Current Conference Tag Current Conference Name Displays the number of kilobytes (K) available on the drive of the current file board's upload path. Displays the message number that the current user is reading. Displays the number of messages in the current message board. Displays the maximum number of lines allowed for a message in the current message board. Clear screen Delay Pause Pausing off Aborting off System Caller Number Mr. or Ms. by gender Date Time BBS Name BBS Phone SysOp Name Post/Call Ratio Account balance Baud rate Time left in minutes Max number of files downloadable in one day Max number of kbytes " " " " Credits Debits Days left until expiration Number of messages left to read

NOTE: This next section is made up of new MCI codes from version 03-26a. These are normally used in the Doors, Archives, or Protocol sections, check the whatdone file to convert from 03-05 and earlier versions if you have upgraded. %A %B %C %D

Actual Baud Rate Baud Rate reported (Locked, if active.) Archive Comment Download File List

%F %G %I %K %L %M %N %P %R %T %U %1 %2 @@Color COLOR _____

File to be processed Graphics (0=Off, 1=On) Internal files (Filenames) Complete name and path of the current file bases's *.DIR file. Log file (Protocol) Main RG Directory Node Number Port Number Current User's Real Name Time Left Current User's Handle Current User's Real First Name Current User's Real Last Name

There are 2 easy ways of changing colors in Renegade. The first method is usable everywhere in Renegade. When you're where you want to change to another color, press [Ctrl-P] and then enter a number from 0-9. From then on, the color will be the one you set with the last command. It will stay the same color until the color is changed again by either the system or by another color code sequence. (In certain areas (like F/S Editor) entering a carat "^" then the number 0-9 that you want set.) PIPE COLOR SYSTEM _________________ A other way which can be used is called the PipeSystem. Where you want to change the color, enter a "|nn" (w/out quotes). The nn is a number between 00 and 23. (2 digits MUST be used.). The first 16 colors (00-15) affect the foreground color, and the last 8 (16-23) affect the background color. The colors are as follows: (B. = Bright, D. = Dark) 00: 01: 02: 03: 04: 05: 06: 07:

Black Blue Green Cyan Red Purple Brown Grey

08: 09: 10: 11: 12: 13: 14: 15:

D. Grey B. Blue B. Green B. Cyan B. Red B. Purple Yellow B. White

16: 17: 18: 19: 20: 21: 22: 23:

Black Blue Green Cyan Red Purple Brown White

@@Mini-DOS MINI-DOS ENVIRONMENT ____________________ Mini-DOS is a small, compact version of the DOS commandline. When you enter this area, you will see something like:

E:\RENEGADE> where E:\RENEGADE is your BBS Home directory. commands available here are:

The

CD

Normal DOS Change Directory Command

CLS

Normal DOS Clear Screen Command

CONVERT *8*

This command will convert an archived file to another archive format. The proper format for the command is: CONVERT FILENAME.EXT XTN where FILENAME.EXT is the full drive:\path\filename with the correct archive extention of the archive you want to convert (ie: RENEGADE.ZIP). XTN is the archive extention that you want to convert the original file to (ie: ARJ).

COPY

Normal DOS Copy Command.

DEL

Normal DOS Delete Command.

DIR

This command will provide a short DOS directory. The use is the same as the normal DOS Directory Command.

DIRSIZE

This command will provide the amount of space that a given filetype takes up. The usage is: DIRSIZE FILETYPE[.EXT] FILETYPE is a valid DOS filename, EXT is an optional extention. Wildcards are allowed. "DIRSIZE *.ZIP" shows the total size of all the ZIP files, while "DIRSIZE *" will show the total size of all the files that don't have an extention.

DISKFREE

This command will show the amount of space free on the current drive.

EDIT

This command will pop up the old Renegade Editor, which is not unlike the DOS command EDLIN. If no file is specified, the file is then asked for.

EXIT

Normal DOS EXIT Command which will return you to Renegade.

HELP or ?

This command will pup up the DOSHELP.* file as a Help me file.

IFL *8*

This command will use the Renegade internal File lister and will list the files inside an archive. The proper use for this command is: IFL FILENAME IFL will search for a wildcards extention.

MD

Normal DOS Make Directory Command.

MOVE

This command will copy a file or a group of files and then will delete the original files. The proper format for this command is: MOVE FILESPEC.EXT DESTINATION

RD

Normal DOS Remove Directory Command.

RECEIVE

This command will tell Renegade to receive a file from the remote computer. The full command is just "RECEIVE". After pressing enter, Renegade will prompt for a protocol, and if the protocol is a non-batch protocol, Renegade will prompt for a filename.

REN

Normal DOS Rename File Command.

SEND

This command is the opposite of receive, as it will allow the remote computer to receive a file that is sent from Renegade. No filespecs are required for the command. The filename is asked for and then the protocol.

TYPE

Normal DOS Type Command. (If in Renegade, you have a page pause, the file you are typing will be paused.)

UNZIP *8*

This command will extract the files from an archive file. The proper format for this command is: UNZIP FILENAME.EXT [OPTIONAL] FILENAME.EXE is the FULL path and filename with extention of the archive. [OPTIONAL] is any optional information that should be passed to the Un-Archiver, such as destination, file to extract, etc.

VER

This command will just notify you that you are in the Renegade DOS Emulator.

ZIP *8*

This command is the opposite of the UNZIP command. It has the same format however: ZIP FILENAME.EXT FILE1.EXT [FILE2.EXT ...] FILENAME.EXT is the full path and filename with extention, FILE1.EXT is the full path and filename for the first file to be archived. [FILE2.EXT ...] is any other files you want to stick in the archive.

X: Normal DOS Change to Drive Command. @@Infoform INFOFORM QUESTIONNAIRE SYSTEM _____________________________ InfoForm questionnaires are text files with certain commands that only have meaning to the BBS. The questionnaire is stored in the MISC directory, in a file with the extension .INF, .INA or .INV (No Emulation, ANSI Emulation, or Avatar Emulation, respectively.) When users answer the question(s), their answers are also stored in the MISC directory, in a file with the extension ".ASW". Answers from other users are appended to the end of the answer file. A special InfoForm questionnaire called NEWUSER is always given to a new user during the new user logon process. An example is listed below: ______________________________________________________ Alright! Only a few more questions to go before you can logon. Please answer the questions, as they are essential for Validation and just as a security measure. Don't worry though.... It's not a test. (it's a quiz..) ;YAre you the Sysop of a BBS (Y/N)? : * ;INO,NOSYSOP What is the Phone # of the BBS? ###-###-#### ;A ? * ;AWhat BBS software do you run? * ;AHow long has it been running for? * ;GNOSYSOP1 :NOSYSOP Oh well!

Someone's gotta do it, eh?

:NOSYSOP1 Do you know of any of the current users on this BBS, or any other good users that could recommend you? (2 lines)

;A 1) * ;A 2) * Ok! Thanks for answering the questions, and I'm sure you'll be validated very soon! _______________________________________________________ Below are listed all the InfoForm questionnaire commands currently supported by Renegade. All commands must start on a separate line, beginning with a ";" character. Labels also start on a separate line, but beginning with a ":" character, and are followed by a string of characters which define the label name. Everything else is treated as straight text. A "; <string>" line is treated as a comment. Command: A<string>* Function: Displays <string> then inputs the string at the "*" character. Command: B<string>* Function: Similar to the "A" command, except input is uppercase only. Command: C"chars"<string>* Function: Displays string, then inputs a single character at the "*" character. Only accepted answers are the characters between the quote marks (""). Command: Dx<string> Function: Outputs a doorfile (See Door in Menu Commands for x) then executes <string>. All rules for standard door commands apply. Command: F Function: Will toggle the AR flags. Refer to the Commandkey "OF" in Chapter 11-D-12 for information on the . Command: G Function: Goes to label . If doesn't exist, the questionnaire will terminate. Command: H Function: Terminates questionnaire and hangs up on user. Command: I<string>, Function: Branches to if <string> was the the last input value from a "A", "B", "C", or "Y" command. Command: K Function: Terminate questionnaire without saving answers.

Command: L<string> Function: Outputs <string> to the questionnaire answer file only. Command: N<String>* Function: Displays <string>, then accepts either a "Y", or "N" at the "*" character. Defaults to Yes. Command: Q Function: Terminates questionnaire and saves answers in answer file. Command: R Function: Will toggle the AC flags. Refer to the Commandkey "OG" in Chapter 11-D-12 for information on the . Command: T Function: Displays the file . Command: V Function: Will validate a user up to level . Command: Y<string>* Function: Same as N<String>, but defaults to Yes instead of No. @@Errors RUN-TIME ERRORS _______________ Certain errors while Renegade is online cause it to exit back to DOS. Whenever this occurs, the screen image is sent to a file called ERROR.LOG in your main BBS directory, along with certain pieces of information such as the time, date, error number, BBS version, the user who was on and what baud rate they were on at. A message is also sent to the SysOp log, and the user's screen when a error occurs. If a error does occur in Renegade, please report it to either your local support hub, or one of the Renegade Alpha sites. Please send along the information at the top of the section where the error is in the ERROR.LOG file. 0 No error 1 Critical error 2 New echomail entered 2 File not found. 3 Path not found. 4 Too many open files. 5 File access denied. 6 Invalid file handle. 12 Invalid file access code. 15 Invalid drive number. 16 Cannot remove current directory. 17 Cannot rename across drives.

100 101 102 103 104 105 106

Disk read error. Disk write error. File not assigned. File not open. File not open for input. File not open for output. Invalid numeric format.

150 151 152 153 154 155 156 157 158 159 160 161 162

Disk is write-protected. Unknown unit. Drive not ready. Unknown command. CRC error in data. Bad drive request structure length. Disk seek error. Unknown media type. Sector not found. Printer out of paper. Device write fault. Device read fault. Hardware failure.

200 Division by zero. 201 Range check error. 202 Stack overflow error. 203 Heap overflow error. 204 Invalid pointer operation. 205 Floating point overflow. 206 Floating point underflow. 207 Invalid floating point operation. 208 Overlay manager not installed. 209 Overlay file read error. @@Optional Files OPTIONAL FILES ______________ SYSOPIN.* SYSOPOUT.* REQFILE.* DLHOURS.* UPLOAD.* WELCOME#.* PRHELP.* COLOR.* BDYS.* BDAY.* LOGONx.* SL###.* DSL###.*

Displayed when sysop chat availability command is used and is available. Displayed when sysop is not available. Displayed when an offline file is requested for download. Displayed during hours when downloading isn't allowed. Displayed before uploading a file. All welcome files are displayed in sequence. Message Editor help file. Color help file for inside the message editor. Displayed if the user has had a birthday since their last call. Displayed on the user's birthday. Displayed after the user logs on in sequence. Displayed to users who have Security Level ###. Displayed to users who have Download Security Level ###.

ARLEVEL#.* USER###.* SYSTEM.* NEWUSER.* NONEWUSR.* NEWAPP.* NOSYSOP.* GOAWAY.* AUTOVAL.* LOGOFF.* PRESHUTL.* ACSEA#.* ACSEB#.* NOBAUD.* NOBAUDH.* YESBAUDH.* 2MANYCAL.* NOTLEFTA.* PROTRES.* PROTBUL.* PROTBDL.* PROTSUL.* PROTSDL.* BATCHUL0.* BATCHUL.* CHATINIT.* CHATEND.* REVENT#.* TIMEDOUT.* HANGUP##.* NOTLEFT.* PWCHANGE.* NONODE.* TELEHELP.* TELECONF.* MULTILOG.* READHLP1.*

Displayed to users who have AR flag # set. Displayed to user number ###. Displayed to new users and at the (I)nformation command. Displayed to new users. Displayed when system is refusing new users. Displayed before new user application is sent. Displayed when the sysop didn't answer chat call. Displayed when user attempts to chat more than times allowed. Displayed when users validate themselves with password. Displayed when the user is logged off. Displayed before the Shuttle menu. Displayed to users during ACS event number #. Displayed to users refused during ACS event number #. Displayed to low baud callers when low baud isn't allowed. Displayed to low baud callers who call outside of low baud time. Displayed when low baud caller calls during low baud times. Displayed when a user attempts to logon more times than allowed. Displayed when user attempts to logon with no time left. Protocols Listing - Resume protocols. Protocols Listing - Batch Upload. Protocols Listing - Batch Download. Protocols Listing - Single Upload. Protocols Listing - Single Download. Displayed when batch upload is selected with 0 files in queue. Displayed before batch upload protocol is selected. Displayed when breaking into chat. Displayed when exiting chat. Displayed when system event number # is approaching. Displayed when the user times out. Displayed when you hangup with the HANGUPxx option. Displayed when the user runs out of time. Displayed when forcing a password change. Displayed when user doesn't have the ACS to log on to node. Displayed as help file in Teleconferencing Displayed when users first enter Teleconferencing. Displayed if a user tries logging in while on another node. Display when user hits ? at the message read prompt.

READHLP2.*

Displayed in place of READHLP1 when user is message sysop. CONFLIST.* Displayed in place of internal conference listing. PRELOGON.* Displayed after Copyright notice, before login prompt. CONF@.* Displayed after joining conference @. CHATOVR.* Displayed when paging if sysop is NOT available but user has chat hour override ACS. DOSHELP.* Mini-DOS help file. WRNGBDAY.* Displayed to a user that fails the birthdate check. ONCEONLY.* Displayed to a user at logon only if it's NEW since last logon. NETMHELP.* Displayed right after a user selects to send NETMAIL. DLOAD.* Displayed before downloading a file. YOURINFO.* Displayed by the OY (your info) command keys in place of default screen if it exists. NOACCESS.* Displayed if a user doesn't have access to a menu. ACTIONS.LST The Teleconference Action File. Must be in the Data Directory. ACTIONS.* Displayed when the user lists the actions in ACTIONS.LST. @@Logon Order ORDER OF LOGONS The Codes: A I T P

= = = =

Always displayed. If Available. Toggleable. If Applicable.

The following is the order in which events and files occur when a user logs on to the BBS, starting right after he successfully enters his password and phone number. Event or File (CAPS) called: Codes: ------------------------------------------------------1. Renegade Logo and "Registered to.." A 2. PRELOGON.* I 3. Enter Name, User #, etc A 4. WELCOME.* I WELCOME#.* where # = 1-9, in sequence. I 5. LOGON.* I LOGON#.* where # = 1-9, in sequence. I 6. Last Few Callers T 7. SL###.* P 8. DSL###.* P 9. ARLEVEL#.* P 10. USER###.* P 11. ONCEONLY.* P 12. BDAY.* or BDYS.* P 13. Automessage T 14. User Information Screen T

15. 16. 17. 18. 19. 20.

"System Bulletins have been updated..." "You have not voted..." " replied to <subject> on " "You Received XXX file points..." "You have Email waiting..." BULLETIN.* If nothing specified in startout menu: 21. MAIN.*

P P P P P T A

The following is the order in which certain events and files occur when a new user is in the process of applying for an account on the BBS, starting right after they choose to logon as new. Event or File (CAPS) called: Codes: ------------------------------------------------------1. Renegade Logo and "Registered to.." A 2. PRELOGON.* I 3. Enter Name, User #, etc A NEW is entered 4. New user password is asked for P 5. NONEWUSR.* is displayed and the user is I logged off, if they enter the new user password incorrectly or if new users aren't allowed (if not allowed, 4 is skipped.) If password is correct or there is no password: 6. SYSTEM.* I 7. NEWUSER.* I 8. Question Sequence (18 new-user questions) A 1. User name or alias 2. Real name 3. Country Calling From 4. Street address 5. City 6. State 7. Zip code 8. Voice phone number 9. Gender 10. Birthdate 11. SysOp Defined Question #1 12. SysOp Defined Question #2 13. SysOp Defined Question #3 14. Screen Width 15. Screen Length 16. Screen Clearing 17. Screen Pausing 18. Password 9. New User question responses displayed. A 10. "Saving your information..." A 11. NEWUSER.INF I 12. NEWAPP.* I 13. LOGON.* I LOGON#.* where # = 1-9, in sequence. I 14. Last Few Callers T 15. SL###.* P 16. DSL###.* P 17. ARLEVEL.* P 18. USER###.* P

19. 20. 21. 22. 23. 24. 25. 26. 27. 28.

ONCEONLY.* BDAY.* or BDYS.* Automessage User Information Screen "System Bulletins have been updated..." "You did not Vote..." " replied to <subject> on " "You received XXX file points..." "You have Email waiting..." BULLETIN.* If nothing specified in startout menu: 29. MAIN.* @@AC Flag Def. AC FLAG DEFINITIONS ___________________

P P T T P A P P A T A

PENALTY FLAGS _____________ L

Can logon ONLY once/day -- Does not allow a given caller to have more than one BBS logon in a given day.

C

Can't page SysOp -- Does not allow the caller to use the chat command throughout the BBS.

V

Posts marked unvalidated -- Marks all public messages as "unvalidated" until the SysOp decides to either validate or delete them.

B

The strange unknown Restriction Flag.

A

Can't write a automessage. This command will not allow the user to replace the current automessage with one of their own.

*

Can't post/send anon. -- This flag prevents the caller from being able to post public or Email messages anonymously.

P

Can't post at all -- This flag prevents a user from posting any messages in any message base.

E

Can't send Email -- This flag prevents the caller from sending any Email to another user.

K

Can't vote -- Does not allow the caller to have access to the voting booth.

M

Mandatory Reply or Deletion of E-Mail. User must either read and reply to his/her mail, or delete it.

REWARD FLAGS 1

No UL/DL ratio check -- This flag will suppress the upload/download ratio check.

2

No post/call ratio check -- This flag will suppress the post/call ratio check.

3

No file points check -- This flag will suppress the checking of a user's file points when requesting a download of a file.

4

Protection from deletion -- This flag will prevent a user's account from being deleted. @@File Base Flag Def. FILE BASE FLAG DEFINITIONS __________________________ N

Sets the file base to not have UL/DL ratio or file points checks.

U

If active, it will display a file base in an area listing regardless of whether or not the user has access to that base. If the user lacks access, it will show in the directory list, but no base number will be shown.

C

This feature toggles whether of not the file base is kept on a CD-ROM or not. If toggled on, it will disallow the file base to be newscanned. (Set the Upload ACS to s300 to not allow uploads from anyone (including you)).

I

If toggled on, the *.DIR file for the particular file base will be stored in the download path instead of the DATA directory.

G

This flag is used for directories containing GIF pictures, and active, the BBS will insert in the description the size and color information about the file. It is written in the following format: (Width,Height,# of colors) Width and Height are in pixels.

D

This flag will make the date that the file was uploaded in the file listings.

S

This flag will make the name of the uploaded appear in the file listings. @@Message Base Flag Def. MESSAGE BASE FLAG DEFINITIONS _____________________________ R

If active, real names are stored in the "From:" and "To:" fields of each message.

U

If active, it will display a message base in an area listing regardless if the user has access to that

base. A

If active, ANSI codes and 8-bit ASCII characters (127-255) are removed from messages before they are posted.

P

If active, this allows private posts to be allowed in the message bases.

F

If active, this will disable the Q command, making the base a "Mandatory Reading" base to read every message. @@Menu Flag Def. MENU FLAG DEFINITIONS _____________________ (C)lear screen before menu - This tells Renegade to clear the screen every time the normal menu is displayed. (D)on't center the menu titles - This tells Renegade to leave the menu titles uncentered. This only affects the titles at the top. (N)o menu prompt toggle - This can be used if you want to put the menu prompt for the menu in the .ASC or .ANS file. (P)Force pause before menu display - The screen will be paused before the menu is displayed. (T)Auto-time display toggle - If this is set to on, a "time-left" string will be inserted right before the menu prompt. (Most use the @V MCI command to insert a HH:MM:SS type format time left string in their menu-prompt.) @@File Extentions FILE EXTENSIONS _______________ Renegade has a complex way of displaying files (Normally the menus.) Here is a list of possible file extensions, and what they mean. ASC

Can contain color codes which are displayed to users who are in an emulation mode.

ANS

Displayed to those users who have ANSI.

AN1-AN9

If a file with an extension of AN1 exists, Renegade will pick and display a random file. (ANS, AN1-AN9).

A0S-A6S

These files are displayed on different days of the week, ranging from 0:Sunday to 6:Saturday. They can be used in conjunction

with the random files, too. (WELCOME.A01 for example, means the first (1) random ANSI displayed on Sundays). AVT

These files follow the same guidelines as the ANSI files, except they are displayed to AVATAR emulation users. (If this file isn't found, Renegade will try the ANS file.)

@@Flags FLAGS _____ *1* =

is the command required to execute the door. If the command begins with "R;", then the user's real name is written to the file instead of the user's handle (the "R;" is stripped before being passed to DOS).

*2* =

is the command required to execute the door.

*3* =

command will only work in file base menu

*4* =

command will only work in message base menu

*5* =

* - Recommended for higher access only. $ - Not recommended for use at all. Use types 16 and 17 for ANSI type modification this command is the one used during a new user logon.

*6* =

! - These commands are recommended for SysOp use only. Each of these commands prompt for the SysOp password and will not execute if it is incorrectly entered. Some of these commands are dangerous and could destroy your board if used improperly. * - These commands are somewhat dangerous in certain cases, and are recommended for users with high or SysOp access only.

*7* =

Refer to the following instructions. ___________________________ Colors: 0. 1. 2. 3. 4. 5. 6. 7.

Black Blue Green Cyan Red Magenta Yellow White

8. 9. 10. 11. 12. 13. 14. 15.

Foreground (0-15):

Black! Blue! Green! Cyan! Red! Magenta! Yellow! White!

Background (0-7): Blinking? No Example: Black on Black ___________________________ The available colors are displayed, then you are asked which color will be your foreground, and which will be your background. You are then asked if you want the foreground to be blinking. After you have entered your answers, you are displayed with what your selection looks like, and you're asked if it is what you wanted. *8* =

Archive Extensions must be specified in the Archive Configuration.

*9* =

Most be Moderator or have Co-Sysop ACS level.

*10* =

ANSI type actually asks if user wants ANSI or AVATAR emulation, if the user has a color monitor, and if they want the Full Screen Editor.

*11* =

SDQ means Sysop Definable Question.

*12* =

Maxperday and Size of bank are in minutes.

*13* =

If "U" is entered, the upload batch queue is used. Otherwise the download queue is used.

*14* =

Sysop level users are excluded from this option.

*15* =

Normally found in File Menu.

*16* =

Must have Sysop Window active.

*17* =

Password must be in uppercase.

*18* =

Shuttle Logon Only.

*19* =

Hard Upgrades will copy the flag set directly from the Subscription Level Editor into the User's Account. Soft Upgrades however will just toggle on any flag that isn't already on in the User's Account. ie:

With a Subscription Level AR Flag setting of A-C-E-------M-----S------Z, a Hard upgrade will make the User's AR Flags an exact duplicate. A Soft upgrade will just turn the A, C, E, M, S and Z flags on, and leave the rest of the flags alone. @@Modem Init Strings MODEM INIT STRINGS __________________

[ SupraFax 14.4k v.32bis ] Modem/Node Configuration 1. Maximum baud rate : 19200 2. COM port number : 2 3. Modem init string : at&f2v&c1&d2x4s0=0h0e0w2| 4. Modem answer string : ata| 5. Modem hangup string : ath0| 6. Modem offhook string : atm0h1| 7. Inactivity init time : 30 8. COM port locking : On 9. Locked baud rate : 19200 baud A. CTS/RTS flow control : On B. XON/XOFF flow control: Off ___________________________________________________ Modem configuration - Result Codes Normal Alternate A. No carrier : 3 B. CONNECT 300 : 1 40 C. CONNECT 1200 : 5 46 D. CONNECT 2400 : 10 47 E. CONNECT 4800 : 11 11 F. CONNECT 7200 : 49 49 G. CONNECT 9600 : 12 50 H. CONNECT 12000 : 51 51 I. CONNECT 14400 : 15 14 J. CONNECT 16800 : 52 52 K. CONNECT 19200 : 16 16 ___________________________________________________ [ Generic 2400 baud ] ___________________________________________________ Modem/Node Configuration 1. Maximum baud rate : 2400 2. COM port number : 1 3. Modem init string : ATV0S0=0&C1&D2M0E0| 4. Modem answer string : ATA| 5. Modem hangup string : ATH0| 6. Modem offhook string : ATH1| 7. Inactivity init time : 30 8. COM port locking : Off 9. Locked baud rate : 38400 baud A. CTS/RTS flow control : On B. XON/XOFF flow control: Off ___________________________________________________ On the 2400 baud modem, port locking is off, so the locked baud rate doesn't matter. For CTS/RTS, make sure the modem is internal, or the cable supports it. ___________________________________________________

Modem configuration - Result Codes Normal Alternate A. No carrier : 3 B. CONNECT 300 : 1 1 C. CONNECT 1200 : 5 5 D. CONNECT 2400 : 10 10 ___________________________________________________ All other result codes should be set to 255. [ Generic 14.4k / 9600 baud ] ___________________________________________________ Modem/Node Configuration 1. Maximum baud rate : 19200 2. COM port number : 2 3. Modem init : at\n3&k3&q5v&c1&d2x4s0=0h0e0w2| 4. Modem answer string : ata| 5. Modem hangup string : ath0| 6. Modem offhook string : atm0h1| 7. Inactivity init time : 30 8. COM port locking : On 9. Locked baud rate : 19200 baud A. CTS/RTS flow control : On B. XON/XOFF flow control: Off ___________________________________________________ Modem configuration - Result Codes Normal Alternate A. No carrier : 3 B. CONNECT 300 : 1 40 C. CONNECT 1200 : 5 46 D. CONNECT 2400 : 10 47 E. CONNECT 4800 : 11 11 F. CONNECT 7200 : 49 49 G. CONNECT 9600 : 12 50 H. CONNECT 12000 : 51 51 I. CONNECT 14400 : 15 52 J. CONNECT 16800 : 52 52 K. CONNECT 19200 : 14 16 ___________________________________________________ If the modem is only 9600, set everything from 12k up to 255. @@Teleconferencing TELECONFERENCING COMMANDS _________________________ /A [ACTION]

This command will perform an action where [ACTION] is the thing you want to do. /A kills himself.

will send: Username kills himself. *9* /ANON

This command will toggle the current room between anonymous and nonanonymous mode.

/ECHO

This command will toggle the local echo on. Instead of typing something, and having what you type be sent back to you as it looks on the other nodes, /E shuts the echo back to you off.

*9* /EJECT [USER] This command will eject a user from the current room. *14* [USER] is the username of the person to kick out. /G

This command will let the user hangup from the teleconference.

/GLOBAL [CHAN]

This command will assign a channel (000-999) which is accessable by all who are in that channel, no matter which room they are in. The user then can send a message to only the people in that channel by typing a "'" (single quotation, no double quotes) and then the line of text he wishes to send.

*9* /I <[USER]> This command, if by itself, will toggle the current room between private and public mode. If the room is private, any user who wants to get in must be invited by the moderator or Co-Sysop. To invite a user, type the username that you want to invite in the [USER] space. /INTERRUPT

This command will toggle whether or not the user's typing will be interrupted by lines from other nodes or not.

/J [ROOM]

This command will bring the user into room # [ROOM].

/LIST

This command will list the possible actions from the ACTIONS.LST file.

/M [TOPIC]

This command will make the user a moderator of the current room, and will set the topic.

/P [USER] [MSG] This command will send a private message [MSG] to the user with the username [USER], on any node and in any area, as long as they are available.

/Q <[ACTION]>

This command will quit the teleconferencing area. If [ACTION] is specified, it will be put at the end of the username. Ie: /Q leaves in a puff of smoke. will send to all the users in conference: Username leaves in a puff of smoke.

/S

This command will show the users in every conference room.

/U

This command will show the users in the current conference.

/W

This command will show the users who are currently online.

/?

This command will display the TELEHELP.* file.

/[ACTION]

Will perform [ACTION] if it's listed in the ACTIONS.LST file.

@@CD ROM HOOKING UP A CD-ROM ___________________ Having a CD-ROM as a file directory is a good plan, as most CD's will hold in excess of 600 Megabytes of information. In Renegade, the CD-ROM drive is accessed as a straight DOS disk, so you can set-up the CD-ROM directories in the same fashion as your other directories. People have come to think that you must have an interface program (such as RomBrain) to allow users to transfer files from the CD-ROM, which on some BBS Programs might be needed, but Renegade is not one of them. The typical CD-ROM drive setup is to have the local Hard Drive directories be 1 Conference, and each individual CD-ROM has it's own conference (ie: Local Stuff is Conference @, and the other CD's are conferences A-Z). For example: ________________________________________ 1. 2. 3. 4. 5. 6. 7. 8.

Name : Communications 1 Filename : 05A DL/UL path : H:\TS\05A\ / H:\TS\05A\ ACS req'd : vvcc UL/DL ACS : % / s30 Max files : 2000 Password : Arc/cmt type: ZIP/1 Flags : ----C________________________________________

This is a typical setup for a CD-ROM directory. Filename is setup to be the prefix of the *.BBS file found in the CD directory specified in #3. (Not all CD's will have the *.BBS file, which is a file that normally has the descriptions of all the files so an external program can import the directories into your board without much hassle.) The Download and Upload path is the same, but it doesn't have to be since uploading won't work anyway. ACS is set to Validated User in Conference C. The Upload ACS is % to stop everyone from being able to upload, and the Download ACS is set to s30. Max Files usually won't matter here, but for those large CD's, you might have to set this number to something higher. (Most CD's though don't have more then 700 files in 1 directory.) Password can be set to your choice. Archiver type and Comment number doesn't matter as no uploads are going to be converted, and you can't convert the ones already on the disc. Flags are set as normal flags are, except the C flag is set to let Renegade know the directory is on CD-ROM. @@Door Set-up SETTING UP A DOOR _________________ Doors are one of the easiest things to setup. Since most doors are online games, let's use Tradewars 2002 for an example. First thing to do is to find a place on the disk to put the game, then make the directory, put the files in there, and then go back into your main BBS directory. For the door, the Option in the menu editor is the batch file that is run to get to the door and run it. A batch file for Tradewars can be something like: 1> 2> 3> 4> 5> 6> 7>

@echo off copy chain.txt \renegade\games\tradewar del chain.txt cd \renegade\games\tradewar tw2002 -wwiv %1 %2 %3 %4 %5 %6 del chain.txt cd \renegade

Well, to explain it fast, line 1 shuts the DOS command echo off, line 2 copies the door dropfile CHAIN.TXT to my Tradewars directory, line 3 deletes the original file just to save space. Line 4 changes to the Tradewars directory, line 5 actually runs the game and tells Tradewars to look for the WWIV BBS type door file (CHAIN.TXT). The %1 %2 ... %6 just tells the program whatever else you might want to pass to it. When the program is finished, line 6 deletes the copy of the door file, and line 7 returns to the main BBS directory. Normally if a batch file has no more commands, it will drop back to DOS, but since the file

was executed by Renegade, it will return to where it was when it left. REMEMBER! NEVER put something like "RENEGADE -N1" at the end of the batch file that you are running as a door. This has a negative effect on the user, memory, and a bunch of other things. In Renegade, the menu entry is something like: 1. 2. 3. 4. 5. 6.

Long descript :(T)radewars 2002 Short descript:(T)radewars 2002 Menu keys :T ACS required :"" Cmdkeys :DC Options :tw2002 Flags :None

The option is the batch file you want to run. If no path or directory is specified, the board scans for it in the main BBS directory. @@Telecon Action File TELECONFERENCING ACTION FILE ____________________________ The Teleconferencing Action File is a file which will have pre-defined actions like the "/a" command, but without the "/a" use. The format is: [KEYWORD] [STRING SHOWN [STRING SHOWN [STRING SHOWS [STRING SHOWN

TO TO TO TO

USER] ALL BUT RECEIVER] ALL IF THERE IS NO RECEIVER] RECEIVER]

The 2 MCI codes that are for this file only are %S and %R, which stand for Sender and Receiver, respectively. A sample file: ---------------------kick ... and the kick is good! %S just kicked %R square in the butt! %S is kicking blindly! %S just kicked you square in the butt! laugh Hahahahahahahahhahah!!! %S is laughing at %R! %S just burst out laughing! %S is pointing at you and laughing! punch Ouch! That's smarts! %S just punched %R right in the face! %S is punching blindly! %S just punched you right in the face! ---------------------If you enter "kick slammin" for example, %S is replaced

with your handle, and %R is replaced with "slammin". @@Credits CREDITS _______ This documentation (even in the form it's in) has some key people to mention: Theo Van Dinter - Sysop: GS Connection BBS running on a 486DX/33 w/ 8 Megs memory, 213 megs and online CD-ROM, Suprafax v.32bis 14.4k modem, running Renegade 06-11a. (207) 799-9080, Cape Elizabeth, ME. P. Hartman - Gave me CORRECT Logon sequences (with a few minor adjustments)... J. Bonner - Gave me the information on the ACTIONS.LST file... Other parts were written by Cott Lang in the "Whatdone" file that is released with the new versions of Renegade. The main parts of this manual were written by Theo Van Dinter - December 27, 1992 through January 1, 1993, and the other various dates that Renegade comes out..