Chapter 4 The meeting system ================================== 4.1 To create meetings -------------------------- You create meets with the command CREATE MEETING. As soon as you have filled in the relevant information about the characteristics of the meeting, it will be available for the users. When you wish to delete a meeting you use the command DELETE MEETING. You must be alone in the BBS when you are deleting meetings. NT will tell you about this if you're not alone. 4.2 The meetflags functions ------------------------------- When you are creating a meeting, or editing an old one, you will set its characteristics in the form of flags. The SysOp does always have access to all the meetings and can of course do whatever he feels like. The same applies for persons with the same status as the CHMEETSTAT value in NT.CFG. That way you can have a companion with responsibilities for a meeting. * WRITEPROTECTED SysOp-status or CHMEETSTAT is required to write new texts in the meeting. Anyone may read texts though. * COMMENT-PROTECTED SysOp-status or CHMEETSTAT is required to comment texts in the meeting. If the meeting isn't WRITEPROTECTED you may write new texts though. * CLOSED The meeting is only available for a certain group of people. The creator, SysOp and those with CHMEETSTAT are the only ones that may decide who's allowed in the meeting. This is done with the commands ADD RIGHTS and SUBTRACT RIGHTS. * SECRET This flag has no effect unless the meeting is CLOSED. If both flags are set the meeting wont be seen when users, who doesn't have the right to be a member of the meeting, lists meetings. There is no way, for those without rights to do anything with the meeting, to even see that there is a meeting. * ANONYMOUS If this flag is set all the names in the meeting will be changed into "Anonymous", except your own name of course! The SysOp may choose to see the real names of the users if he so wishes, by editing the appropriate value in NT.CFG. * ALIAS When this flag is set the users' aliases will be shown instead of their real names. The SysOp may choose to see the real names instead. 4.3 How texts and meetings are stored on disk ------------------------------------------------- Each meeting has its own TEXTx and HEADx file, where x is the meeting number. TEXTx contains the texts, and just the texts, stuffed after each other without any mark that separates the texts. HEADx contains the information about where each text begins and how long it is. That way NT Pro knows where in TEXTx it shall look when someone reads a text. HEADx also contains all the information about who the author of the text is, the subject, and any comments etc. All these files are in the TEXTS directory in your system. You don't normally have to care about them. If anything goes wrong, use the SERVICE command to correct the error.