›        EXTENDED SYSOP COMMANDS››  The extended SysOp commands module is something that you will probably not want to give your SigOps access to. Giving a user access to this command is effectively giving him access to do anything to your system. Only you (and perhaps friends that you can REALLY trust) should have access to this command.››       CREATE/EDIT CONFIGURATION››  This command is used to change your BBS's system configuration. Refer to the section "Configuring Your CARINA II" on previous pages.››         CREATE/EDIT SECTIONS››  This command is used to create additional sections and/or reconfigure (e.h., their physical location, name, or keyword). When this command is executed, there will be displayed a list of existing sections, their respective keywords, and the drive numbers on which the folders within that section reside. "G" stands for Games (i.e., MODSEC), "D" for Databases (DATSEC), "M" for Message Area (MSGSEC), and "F" for File Area (FLESEC). If a drive number listed equals zero, then that folder does not exist (or at least CARINA II sets up as if it doesn't exist). After this is displayed, you will then be shown a list of options that you can perform. Pressing K, G, D, M, F, or N will allow you to change a section's Keyword, Game folder drive, Database folder drive, Message Area folder drive, or Section Name respectively. Pressing "R" will allow you to remove the last section in the section's list. You cannot remove a section in the middle of the list; however, you could rename the section you wanted to get rid of to the name of the section at the end of the end of the list and then copy all of the proper files within the last section's folder to that section's folders and then remove the last section. On that same note, there is another use for this function. There is no function that will restart a message base. If you wanted to do that, you would have to create another section (with only a message base), and then remove the last section and delete all of that section's corresponding folders and files within these folders. It's a slight inconvenience but you probably won't have to this often (if ever). When you make any changes, remember, this will be written to the SECTIONS.DAT file. If this file is located in your section, DON'T FORGET TO COPY IT BACK DOWN TO A DISK!›  Refer to the section "Creating Additional Sections" on previous pages for information on the [C]reate New Section command.››              GLOBAL MASK››  Perfoming a global mask will change an item within EVERYONE'S account. Because this is performed on everyone's account, this function can be rather slow in some cases (especially when masking out commands/sections). The first two things you can make out are messages/files waiting. This is the counter that tells the user how many E-Mail messages/F-Mail files he has waiting. Executing this function will reset the counter to zero.›  Clearing the high message read/file browsed is again a matter of resetting a pointer to zero. You would want to do this if you ever restart a message base or file area (but not the password file). You can peform this operation on the current section's pointer or on all sections' pointers, These pointers are used for the NEW parameter of Read/Browse.›  When masking commands and/or sections, you can either give access or take it away. With masking commands, the commands that you tag will be the ones that the user will either get access to (when giving access) or be denied access to (when taking away access). When masking sections this works a little differently. If you are giving users access, then you can select between the different access levels that you wish to grant users. When taking away access, you must take away all of their access in that section. The section that you specify to have their access taken away will be changed to a SPACE (no access); therefore, when taking away access, you have only two choices (either you bump their access down to "no access" or you don't. You can't, say, bump everyone down to read-only status; however, you could bump everyone down to "no access" and then bump everyone up to read-only access.››         UPLOAD A FILE LOCALLY››  This feature allows you to place a file in a download area yourself. You can think of it as doing a normal upload, but instead of doing a file pointer, CARINA II simple copies the file into the upload area. When you execute this command, CARINA II will proceed just like a normal upload; however, when it comes time to do the file transfer, you will be placed in a copy program. Simply type the source file's filename (e.g., D1:FILENAME.EXT or D1:FOLDER>FILENAME.EXT,etc...). You can also do a directory from the prompt by placing ans asterisk [*] before the filespec. For example, typing "D2:FOLDER> would do a directory of all files within the FOLDER subdirectory on drive 2. Once you've dont this, locally uploaded the file, remember, the file has now been uploaded, but it does not been validated (unless you uploaded in electronic mail). You must now place the file on-line via the validate command.››      RUN/BASIC/SPARTADOS COMMANDS››  To make a short story even shorter, the run command will run a BASIC program, the BASIC command will exit into BASIC, and the SpartaDos command will exit you into SpartaDos. If you want to get back into CARINA II (and the SYSCOM module is no longer in memory), simply type RUN"D7:SYSMOD>SYSCOM" where the "?" is replaced by the drive number on which the SYSMOD folder resides. You can also make it so that these commands can be executed only after a user types in a definite password (for extra safety). Place any password you'd like to see in a file called BASICPW.DAT and place the file on drive 1. You can do this with a text editor.›  While in SpartaDos, you can execute any INTERNAL command you'd like (except batch files while on-line remotely). Only limited external commands will work because most of them load in over top of BASIC.›  Remember, you can enter into BASIC on SpartaDos remotely. You can program on-line, copy files on-line, etc...››       VALIDATING UPLOADED FILES››  After a file has been uploaded to your BBS, you will need to validate it before it will be listed in the download directory. This is done so that you can screen out any uploaded files that you do not want on-line. You'll need to do this for every section that has a file area (except electronic mail...F-Mail is automatically validated).›  When using the Validate command, uploaded files are assigned temporary file numbers so you can skip around to different upload files (just like you can messages). When a file is validated, it is assigned a permanent file number. Uploaded files will be listed one at a time in the order that they were uploaded. At the "Command [?]=Menu" prompt, there are three distinct commands that you should know about:  "V" will validate the file (place it on-line where all who have access to this file's area to see), "K" will kill this file (delete it), and "N" will allow you to type a new description, filename, etc...before validating it.››         MAKE VOTE-POLL COMMAND››  You have the ability to make up to 26 voting-polls within each section (Poll_A through Z), by using the Make-Vote command. Each poll can have up to 26 responses (A through Z). When executing this command, you will be asked if you want to delete the previous polls. If you don't have any previous polls, then it really doesn't matter how you respond (can't delete what isn't there). You will then be placed at a "Cmd." prompt. This should look familiar. This is the text editor command prompt. You'll need to type "C" to continue. Enter your vote-poll questions, exit the editor, and [S]ave it. You'll then be asked to enter up to 26 responses to this question. Enter as many as you want (preferably two or more) and press RETURN on a blank line when finished. You'll then be asked if these responses are correct. After answering "YES" (hopefully), you'll be asked if the entire poll is correct (after displaying it to you for a second look). After answering "YES" to this prompt, it will tell you, "Writing out poll" followed by the poll's letter (A through Z). You can continue entering more polls via the Make-Vote command until you feel you have enough.››      CREATING A BACKUP BATCH FILE››  A batch file can be made to backup your ramdisk to a disk drive or hard disk anywhere from every hour to every 255 hours. This file does not necessarily have to copy files however. It can be used to do just about anything. You could use it to rotate your macro screens every hour, for example. You could have 5 different INTRO.ATA files (named INTRO_1.ATA through INTRO_4.ATA and the INTRO.ATA file (the one used by the BBS [for example], and you could make a batch file that would rename these files every hour. Here's an example of a backup batch file that would do this:››  RENAME SYSTXT>INTRO.ATA TEMP.ATA›  RENAME SYSTXT>INTRO_1.ATA INTRO.ATA›  RENAME SYSTXT>INTRO_2.ATA INTRO.1ATA›  RENAME SYSTXT>INTRO_3.ATA INTRO.2ATA›  RENAME SYSTXT>INTRO_4.ATA INTRO.3ATA›  RENAME SYSTXT>TEMP.ATA INTRO_4.ATA›  CAR›  RUN "D7:MODULE>WAITCALL" *››  * (Your drive # may be different)››  This file (or any backup batch file) would have to be called BACKUP.BAT and would have to reside on drive one of your data disks. The backup batch file must end with CALL followed by a›RUN D7:MODULE>WAITCALL" (your drive number may be different). Although you will most likely want to use this batch file to backup your ramdisk (if you have one), you can use this batch file to do just about anything that batch files can do that is).››     MISCELLANEOUS POINTS/FEATURES››  I you would like to kick someone off of your BBS, bring up the full-page status window, move your cursor over to the [cd] field and press the SPACE bar.›  Pressing the SELECT key (and holding it down until a block has been transferred) will abort a file transfer (since C-Modem blocks are so big, you may find that you will be holding down this key for a LONG time).›  In order for a file to be validated, you need enough space for the file to be duplicated in the download area before it is deleted. For example, if a 5000-byte file was waiting to be validated, you would need another 5000 bytes free on that drive so the file can be duplicated in the download area. The first file will then be deleted and you will have 5000 bytes free again, but that space is necessary for the duplication to take place.›  We've discovered that you can actually create two different BBSs with your CARINA II. You could divide your board in half (allowing each BBS to have 12 sections) and allow users to have two accounts---one that would log them onto the board, and another to log them on to the other. You could create two GENERAL sections (having the exact same name, keyword, etc...), and give users logging onto the first BBS access to the first GENERAL section and then logging onto the second BBS access to the second GENERAL section. This way, you can have two totally separate BBSs where the only common area would be electronic mail. You could set up a board based around role-playing, for example, and another board for say, your local computer club. You would have to create a section spefically for new users so they could request which board they are trying to get access to (and you should, of course, explain that there are two different boards being run here and that the user would need to request one (if not both of them). This has been tried and it does seem to work rather well.›  There are some text files included on disk number 2 side 2 of your CARINA II master disks that together make up a SigOp's help database. If you have the room, you may want to create a section specifically for SigOps and place these text files in the DATSEC folder for that section. These files are MAIN.HLP and A.HLP through J.HLP (11 files total). These files should not be confused with your user's help database located in your SYSTXT folder.›  If you ever forget to backup your INDEX.FLE file along with your PASSWORD.FLE, run the MAKEINDX program. This will recreate your INDEX.FLE file. Users not being able to log on with their name is an indication that your INDEX.FLE file may have a problem. Running the MAKEINDEX program should correct the problem.››        MODIFYING YOUR CARINA II››  MOE (the Modem Operating Environment) has a command built into it that will disable MOE. This command is "EDIT" and can be entered at any prompt; however, it will only work when typed with the computer's keyboard (it will have no effect if someone on-line types it). You will want to use this command anytime you want to modify the BBS, There are also other reasons you would want to use it (any time you would want to use your cursor control keys for example). It's a very handy command. Anytime you want to turn MOE back on, just run one of the command modules (e.g., MAILCOM, USERCOM, FILECOM, SYSCOM). This will turn all of the necessary features back on and place you at the "COMMAND" prompt where you can continue using the BBS.›  If you plan on making your own programs for CARINA II (which I encourage you to do if you know how), then you will need to use an error-trapping routine included on your CARINA II disk 2 side 2 called ERRTRAP.BAS.  This file (if used properly) will trap your program so that an error ocurring will not throw the user into BASIC. It also tells the program what to do if the user's time has expired. Two variables should be used within your program:  ERRGO and BREAK. ERRGO is used to replace all occurrences of TRAP commands that you may be using in your program. Anywhere you would normally put a TRAP statement, replace it with an ERRGO=statement. For example, if you had a TRAP 1000 statement in your program, replace it with an ERRGO=1000. There should only be two TRAP statements in your program---the two in the ERRTRAP.BAS file.  The BREAK key is used to tell your program what line number to go to if someone were to hit the CTRL-C keys together. For simplcity's sake, you can disregard the variable and turn off the ability of a user to hit the CTRL-C key-combination by using the statement POKE 1636,0: All of CARINA II's modules use this routine so you may want to use a module as an example if you are having trouble understanding this routine.›  If your are planning to modify your GATEWAY, XY_TRAN, or CM_TRAN modules, keep in mind that these modules load binary files into upper memory. These files are not recognized by BASIC's FRE(0) command. BASIC will think that this memory is still available. You should subtract about 900 bytes from the value given by the FRE(0) command when modifying any of these modules. Your programs will start to do strange, random things if you start to program into this area of used memory.›  If you plan on modifying any of CARINA II's data files, you should take note of where items within these data files reside.›