
   
                                                   The Vulcan Embassy BBS
                                                              version 2.0
                                         Copyright 1990, Timothy M. Garay

   
                                GENERAL.TXT
                               =============

   
          This file will explain the general usage of The Vulcan Embassy 
   BBS version 2.0.  It will explain some of the various things about the 
   program, some of which a user will never see.
   
          First thing to talk about is the BLACKLIST function.  If you 
   have a troublesome user (and we all do!) just turn this function to 
   'YES' on their password record.  When next they call the system and 
   log on it will display the BLACK.SCR file to them.  This file should read 
   something like "you are not welcome here anymore" or "you really 
   botched things up this time!  don't come back!!".  It is your 
   discretion.  Once the file has been displayed the system will log them 
   off immediately, not allowing them to do anything.  Nice huh?  Don't 
   forget about the SHIFT-F5 function too, it can be used to log somebody 
   off immediately!!  (without them knowing that you did it on 
   purpose...)
   
          Next thing is the Main Menu.  It is the pivot point of the 
   whole program.  If any error occurs (if it doesn't lock the system up 
   or is a fatal error that cannot be trapped) a user will be returned 
   immediately to this point.  You are always told how much time remains 
   here.  You can re-print the main menu by pressing the [RETURN] key.  
   Also, pressing [?] will print the HELP.SCR file you created (or at 
   least should have!).  Anytime something is being printed to the 
   screen/modem it can be paused by pressing ^S and resumed by pressing 
   [RETURN].  If a user has not pressed [RETURN] within about 3 minutes 
   then the system will log them off.  This goes for any input-waiting.  
   If it does not get any input for approximately 3 minutes it will log 
   the user off.  Neat huh?  Also, when something is being displayed to 
   the screen/printer it can be aborted by pressing ^C.  There are also 
   "defaults" throughout the system.  Like in the reading of a msg base, 
   pressing [RETURN] will automatically default to reading any new msgs 
   in the base.  At the end of each msg [RETURN] causes it to go on to 
   the next msg.  They are pretty obvious, they are usually for the most 
   used functions.
   
          A user cannot "break" the system.  The only time this may not 
   be true is with transfer shells and on-line game programs.  That all 
   depends on the programmers.  If a user hangs up anywhere the system 
   will detect it and log them off and wait for the next caller.  No 
   problem!!
   
          Read all the documentation files so you know what is going on 
   and what you need before trying to run this program.  There is alot of 
   work involved in getting it all set up correctly but once finished it 
   pretty much runs itself.
   
          The status line at the bottom of the screen tells a great deal 
   of information.  It will tell you the handle and real name of the 
   person on-line, what baud rate they are calling at, how much time they 
   have remaining, and what computer they have.  It also tells you where 
   they are in the program, how many times they have called the system, 
   how many people have called the system total, how many credits the 
   person has, what time and date it is, and a short history of their 
   functions.  A full history of the user's keypresses appears in either 
   the printout on the printer or the USERLOG.DAT file.  It will be a 
   conglomerate of the characters the user pressed (whether or not they 
   were the correct ones).  This will give you an idea of that the user 
   did or tried to do.  These keypresses will usually correspond to your 
   menu item selections.  Each section is grouped in []'s to give you an 
   easier time in following what a user did.
   
          Because TOS has a problem recognizing when a floppy disk has 
   been changed during the boot-up process it was necessary to have the 
   program do a free space check on Drives A and B the first time the 
   program is run.  This is to force TOS to recognize the current 
   (system) floppy disks, otherwise it still thinks the boot-up disks are 
   in the drives.  It only does this once the first time the program is 
   run so it is not of any inconvenience.  EXCEPT, if you do not have a 
   floppy drive B!!  Sorry, there is no way around it.  TOS always says 
   you have a drive B even when you don't and have removed the drive B 
   icon from the desktop.  Until someone can tell me a quick way of 
   telling if Drive B is really there or not you are just stuck.  All 
   this means is when it checks free space on Drive B TOS will tell you 
   to swap disks and then you will have to swap them back or whatever.  
   Minor inconvenience, all else will work ok.
   
             When you want to put files of your own up for users to 
   download you need to copy the file into the directory before 
   "uploading" it.  When you log on in local mode you are asked all the 
   same questions that any user would be asked, except when it comes to 
   the actual file transfer; that part is skipped.  Instead it checks to 
   make sure the file is there and if so, tells you it was a successful 
   transfer.  When you use the UDKILL sysop command it only marks the 
   file data record as being deleted, it does not actually delete the 
   file itself.  You must "upload" a file you have placed in the 
   directory in order for it to be available to a user to download.  This 
   program does not scan the directories at all, it only goes by what's in 
   the data file as what is available.  For this reason, you can have all 
   the files in one directory if you wish and a user can still list out 
   or only see those in particular categories (ie. ST UTILITIES or IBM 
   SOFTWARE) even though all the files are in the same directory.
   
          Remember that the text screens and menus must be less than 32K 
   in length (32767 bytes) or else the system will crash or display an 
   error when it tries to load the screen or menu.
   
          You should at least take the time to make a good help screen 
   for new users.  The help screen can be displayed from the main menu by 
   pressing [?].
   
          Even if you have a clock card (like I do) you must pause when 
   the program asks for the time and date at boot-up.  It is this way 
   because it is at this point that you must take out the boot disks and 
   insert the system disks, or at least make sure the disk with 
   A:\CONFIG.DAT is in Drive A.  If you have a clock card or the time 
   and date is already correct then just press [RETURN] at each question 
   and the time and date will not be changed.
   
          A sure sign of a bum user is one who does not give correct 
   information in the new user application; especially if they give 
   totally crazy information.  Don't be so humble that you think that 
   you must stay friends with everyone and keep all users even those that 
   give incorrect information.  There are enough good people out there 
   that you don't need to ruin your board with users like that.  Just 
   delete their password.  If they persist to cause more trouble then 
   blacklist them.  Usually, people don't just randomly pick a BBS to 
   call and annoy, it will most likely be someone you know; especially if 
   they persist.
   
          The time limit you give a user is good for one day.  When that 
   user logs off the time he has remaining is saved along with the date.  
   When that user calls back, if the date is the same as his last call 
   date then he is given only the time that was remaining on that last 
   call date.  If the date is different then he will be given the full 
   amount of time.
   
   
   
          For the latest information on THE VULCAN EMBASSY BBS version 
   2.0 program call the original Vulcan Embassy BBS.  The number is     
   216-365-7702.  It runs 24 hours a day and 7 days a week.  The baud 
   rates it currently handles are 300, 1200, and 2400 baud.  It is open 
   to everyone with any computer.  Or you can write to me at TIMOTHY M. 
   GARAY  /  729 THORNWOOD BLVD.  /  ELYRIA, OH  44035  /  U.S.A.  I 
   welcome any comments or questions you might have.  Remember to read 
   all the doc files that came with the archive.  Thank you for your 
   attention and I hope this program will be of use to you!
   
   

