Citadel Errors & problems List
 In general, if you get an error and this list does not tell you how to
 correct it, collect as much information as possible and report what
 happended either directly to me or in the Citadel 68k room.  The first
 thing to look for is a file called debug.sys or crash.sys.  These files
 should appear in either your audit area, the home area, or the location
 you started up Citadel.  I usually will want the information in these
 files(even if it is just a cryptic one line message like "dependant variables
 mismatch", sometimes it tells me exactly where the problem is).  The second
 thing I will tell you to do is turn on debug, Here is a general method I
 end up telling people:

     1) go into the Sysop menu, turn on debug "D" option.
     2) Shut down your Citadel, "X" option.
     3) delete debug.sys in the audit area(or save it if it contains
        info I might need.  At the least, edit the file and add some
        markers (like two lines of asterisks) at the end of the file.
     4) Bring up Citadel and attempt to reproduce the problem.  If you
        cannot do it locally, you might even ask a remote user to do it
        for you.  leave debug on.  Note:  If you run confg, debug is
        automatically turned off, repeat the above steps.
     5) archive all the information(using something like lha) and arrange
        to get the information to me.  I may call your BBS to download the
        file so make some arrangements in Citadel 68K so I know where it
        is.


 Error:  [1]IOError = nnnn
 Error:  [2]IOError = nnnn
 Reason:  nnnn is a result code returned from a serial port i/o, usually
          a dropped carrier(small timing window for a race condition could
          cause this).  The error is handled for 99% of the cases in a way
          that will cause Citadel to recover and reset.  [1] is the case
          where i check to see what is in the serial port buffer, and [2]
          is when the actual read is done.

 Error:   Startup Error Code nn
 Reason:  something went wrong during system initialization. The reasons
          are:
          1 - unable to open intuition.library, you must be 1.2 or greater
              to run Citadel.
          2 - unable to open graphics.library, same as 1, or could
              not open req.library, check your libs: for req.library, it
              is required for Citadel operation.
          3 - Insufficient Stack space, Citadel versions 3.42.E19 and
              earlier required a large stack, much larger than needed
              (50K).  Versions 3.42.E20 and later will require a 20K
              stack or less(I am still adjusting the values down).
              3.43 will probably require an 8K stack since all the tests
              I have done show a 3 k stack is enough.  Citadel still
              requires the larger limits.
         11 - Console Open Error.  Catch all for console window errors
              If you are using #WBSCREEN, try without it.
         25 - Open Serial Port Failed, Well, Citadel could not get to
              the serial port(maybe something else has it open, or you
              have Citadel running twice?).
         31 - Could not create a Port for timer communications, Low
              memory?  Trashed system tables?  Try a re-boot.  This is
              one of those, "you should never get here".  If you bug me
              with this type of problem, you had better have a full
              system configuration and alot of details.
         32 - could not create an I/O request. See 31.
         33 - Open timer.device failed.  See 31.

  Note:  In the serial port open errors, and in most cases with debug
  turned on, you will get a text error message of the form:

   1:    Date - Dos Error:nnnn
   2:    (some text as to what happened)
   3:    (some text as to what happened) <-- you may get only one line.
   4:    Reason: <error text>
   5:    Current Directory

   Line 1: is the internal error code(less than 100), or the Dos error
   code.
   Lines 2-3: will either be a command(like in the external protocols) and
   a text line, or just one line of text.  External commands will display
   the text and command, most errors do not have an external command.
   4: is the reason the error occured(from the Exec routine Fault).
   5: is the current directory.  This is important if you are trying to
      setup a door for example and in the wrong directory.

 If the problem is reproducable, do it several times and record all possible
 information, especially your system configuration!  If it happens just
 once and you can not reproduce it, then still record what you can, check
 things like memory in use, what is running.

 Note:  If you have a problem that seems to happen often, realize that I
 rarely have a crash.  Pleae check to see that something else is not causing
 the problem.  Remove commodities, other programs and see if you can cause
 the problem without that super-duper-whiz-bang mouse accelerator/screen
 blanker!  It probably ain't Citadel!