For what it is worth, here is the documentation on how to install and set up a sig............. Please NO flames!!!! For clarity, I will be referring to a term called ORGPATH. ORGPATH is nothing more than the directory that contains the bbs software. ... The following steps are REQUIRED to set up a sig: 1) From ORGPATH, make a directory with the SAME name as the SIG. 2) Be sure the permissions are such so that the bbs user has rwx permission. 3) From that directory, make two new directories called files and msgs. The files directory will be the file section for that SIG. You guessed it, the msgs directory will be the message base for that SIG. 4) Same as step 2 but for the two new directories. 5) The files directory must contain a file called files.bbs. This is exactly the same as the GENERAL file directories. Guess what, it uses the same code! Actually, the message section for the SIG is controlled by the same code as for the GENERAL message bases. 6) In ORGPATH, generate a file called sigs.bbs. This file is the listing of the sigs on your system. The distribution contains an example sigs.bbs that you can use as a guide. 7) Sigs.bbs is basically in the same format as features.bbs etc. The IMPORTANT difference is that a SIG can either be "private" or "public". If you wish to make the SIG private, put an asterisk is column 78. You will notice that the distribution sigs.bbs has two SIGS, one is private and one is public. The first field is the SIG name and MUST be the SAME name as the SIG directory that you made in step 1!!!! The second field is the description and the third field is the privilege level assigned to that SIG. 8) Each SIG MUST have a file in ORGPATH using the SAME name as the directory but with an extension of .bbs. If the SIG is private, you will have to make a list of each allowable user in the form of Firstname Lastname. Remember, on user per line and CAPITALIZE the first character of the first and last names. A string compare is performed. If the SIG is "public", you must still make each file by simply typing "touch signame.bbs" where signame is that of your SIG. REMEMBER, make sure that the file has rwx permission for the bbs user. This is very important since a public SIG is dynamically updated by the user. 9) This is optional but nice! In the directory that you made in step one, you can have a file called sigwelcome.bbs. This file will be displayed, if it exists, to the SIG user once he has successfully logged into the SIG. It is nothing more than an ASCII file an can be generated by "vi". A) This ALSO an optional but nice feature. In the directory that you made in step one and if it is a private sig, you can have a file called sigentry,bbs. This file is displayed to the user, if he tries to login to the sig, and entry is not permitted because he/she is not listed in the sig users file. It can be used to describe the way he/she can be registered, by you, into the sig. Once you have performed the above steps, you are ready to login yourself into each SIG. Go into each SIGS message section and leave a message. This will make all the necessary msgs files. REMEMBER, a "private" SIG can only be entered if the user's name is present within the appropriate .bbs file. This is ALSO true for you. You MUST enter your name too to gain access. Enjoy, Sandy