
GALACTICOMM TECHNICAL NOTE          (C) Copyright 1994 Galacticomm, Inc.
1994, No. 3                                                May 31, 1995
========================================================================

      COMMON ERROR MESSAGES ASSOCIATED WITH THE MAJOR BBS, PART I
      -----------------------------------------------------------
      Galacticomm Technical Support 

Bulletin boards are complex software packages, and to successfully
operate a BBS, it is highly recommended that you have a good
understanding of DOS and topics surrounding personal computer
communications.  As easy to use as The Major BBS is, it is still an
advanced software package.

As such, it is useful to have a familiarity with the internals of the
software so that you can detect problems you may be experiencing and
learn how to correct them.  Technical Support is available free from
Galacticomm, but it is recommended that you become familiar with your
own bulletin board.  This can help you trouble shoot and even possibly
fix problems before having to fall back to Galacticomm's Technical
Support.

This technical note contains a list of some of the common error codes
and problems that may be encountered during the operation of The Major
BBS.  Although some of these errors may occur more than others, this
does not mean you will definitely get any of these errors.  These are
just the more common errors that may occur.

Along with each error code, we have included a short description and
suggested solutions to fix it.  If the solution provided does not solve
the problem please call Galacticomm Technical Support.  We will work
with you to diagnose the problem and provide a solution for you.
Galacticomm Technical Support is available at (305) 321-2404, Monday
thru Friday, from 8:30am to 6:00pm Eastern Time.  Additionally, support
is available via Fax at (305) 583-7846 or Electronic Mail at the
following addresses:

         Internet: support@gcomm.com
         MajorNet: Tech Support@GCM
           Usenet: comp.bbs.majorbbs newsgroup

This technical note is broken up into four parts: Catastrophic
("CATASTRO") Error Messages, Btrieve Error Messages, Phar Lap 286|DOS
Extender error codes, and How to read a GP.OUT file.


I. Catastrophic Error Messages ("CATASTRO")
---------------------------------------------

Catastrophic error messages (or "CATASTRO" for short) are problems that
may occur from time to time for a variety of different reasons.  These
errors occur when the BBS encounters situations it didn't expect.
Usually these errors are the easiest to correct.

A CATASTRO is recognizable because it is surrounded by a red box on your
screen with a flashing border.  However, catastrophic errors are not the
only errors that use this box (see BTRIEVE Error Messages below). Inside
the box is the error message as well as some diagnostic information.

This is an example of a CATASTRO:

         -----------------------------------------------------
         | 29-JUN-94 16:03:04                                |
         | ERROR IN HARDWARE CONFIGURATION OPTION "LANTYP5"  |
         | LAN TYPE NOT OPERATIVE                            |
         -----------------------------------------------------

  This error box tells you that the error occurred at 16:03:04 on June
  29, 1994, and that there is an error in hardware configuration option
  "LANTYP5".

  In addition to appearing on screen, a copy of a CATASTRO error message
  will be written to the file CATASTRO.TXT in your \BBSV6 directory.
  The entry in your CATASTRO.TXT file for the above error would look
  like this:

  29-JUN-94 16:03:04 ERROR IN HARDWARE CONFIGURATION OPTION "LANTYP5"
  LAN TYPE NOT OPERATIVE

  This CATASTRO will occur when you have defined a channel group to be
  IPXV or SPX and have not installed the Advanced LAN Option.  To
  correct this problem, either install your Advanced LAN Option
  Connectivity diskette (if you have purchased the option), redefine the
  offending channel group to IPXD (if you were attempting to get LAN
  access), or select some other channel group type.

  Here are some other common CATASTRO messages.  It is impossible to
  list all of the possible messages, so if you receive one that is not
  listed below, please contact Galacticomm Technical Support for help.


         -----------------------------------------------------
         | 22-DEC-93 16:09:18                                |
         | There is not enough memory to continue.           |
         | Please either reduce your memory requirements     |
         | or install more memory, and try again.            |
         |    << Press any key to proceed >>                 |
         -----------------------------------------------------

  With this error, The Major BBS could not locate enough free memory to
  proceed.  This error could occur for one of the following reasons:

  A.  You do not have enough memory to continue.  You should remove any
      TSR's from your CONFIG.SYS and AUTOEXEC.BAT that are not necessary
      to run the BBS.  At a minimum your CONFIG.SYS should contain the
      following lines:

        FILES=127
        BUFFERS=30

       Don't remove drivers for devices like CD-ROMs, Network Interface
       Cards, or other SCSI devices, if your BBS accesses them.

  B.  You are trying to load the BBS from a directory other than its
      home directory.  If you have the BBSV6 directory in your path, and
      you try to run the BBS from your root directory, you might
      encounter this message.  To resolve this problem, first switch to
      your BBSV6 directory and then run the BBS.


         -----------------------------------------------------
         | 28-FEB-94 09:34:08                                |
         | ERROR IN YES/NO OPTION 7 IN galfxm.mcv            |
         | ,MSG:galfxm.mcv/7                                 |
         -----------------------------------------------------

  This can occur when the BBS is expecting a certain configuration
  option to have a YES/NO value but the corresponding .MSG file had some
  other value.  We can examine the files to see what appears to be
  happening.

  First, some background information.  Every .MSG file has a
  corresponding .MCV and .H file.  The .MCV and .H files are generated
  each time there is a change made to the .MSG file.  For instance, you
  have a BBSMAJOR.MSG, BBSMAJOR.MCV, and BBSMAJOR.H file in your \BBSV6
  directory.  The .H file is the message-number definitions file --
  essentially an index of all of the configuration settings and text
  blocks within the .MSG file.

  In the above example, the problem occurred with the file GALFXM.MSG
  With any standard text editor (you can use the DOS EDIT command with
  MS-DOS 5 or 6) look at the contents of the file GALFXM.H. For this
  error, you would bring up the file GALFXM.H in a text editor (such as
  EDIT, included with DOS 5 and 6).  While in the text editor, search
  for the number 7.  The results will look something like:

                    #define LEVEL4      7  <--------
                    #define AUDSUC      8
                    #define AUDABT      9

  Remember the name of the option that corresponded to the number 7.
  Next, you will have to go into GALFXM.MSG and search for LEVEL4.
  Looking at LEVEL4, it is obvious that configuration number 7 is not
  meant to be a YES/NO option.  In this particular case, the error has
  occurred because the .MSG file is out of sync with the Fax/Online
  module.  This may have occurred because an incorrect file was copied
  into the BBS directory, or the installation procedure did not complete
  properly or the file has been corrupted.  If the .MSG file is outright
  corrupted, restoring a backup may solve the problem.  Alternatively
  reinstalling the add-on option would correct the situation.

  If number 7 in the GALFXM.H file was AUDSUC, and looking at GALFXM.MSG
  presented you with the following:

        AUDSUC {Record successful fax attempts to Audit Trail? FOO} B

  It appears as though the option was edited by hand incorrectly.  The
  solution to this version of the problem is to replace the "FOO" text
  with either a YES or NO response.  This form of the error will only
  occur when the file is hand edited.  The configuration editor utility
  will not permit anything other than a YES/NO response for this option.

  Occasionally a .MSG file will change but the associated .MCV file will
  not be updated.  To correct this error, delete all your .MCV files at
  the DOS prompt and then typing "BBS" by itself.  The BBS will then
  regenerate all of your .MCV files.


         -----------------------------------------------------
         | 04-MAY-93 10:11:51                                |
         | SUMAMS ERROR                                      |
         | CH01=John:11/143,MSG:galms.mcv/160                |
         -----------------------------------------------------

  This error is encountered when there is mail in a users mailbox that
  is neither addressed to them nor sent from them.  This error is
  generally caused by a corruption between the index used to look up a
  record in the GALMSG.DAT file, and the data that it points to.   This
  can be fixed by doing a re-index of the GALMSG data file.  To re-index
  the GALMSG.DAT file, type in the following commands from your \BBSV6
  directory:

     BBSBTR         <Enter>
     BBSRIDX GALMSG <Enter>
     BBSRMB         <Enter>

  When re-indexing any Btrieve data files, you need to make sure that
  you have twice as much free space as the size of the file you are
  fixing.  For instance, if your GALMSG.DAT file is 70 megabytes, you
  will need to have at least 140 megabytes free in order for the system
  to re-index your file properly.


         -----------------------------------------------------
         | 01-NOV-93 15:22:49                                |
         | INISIG: BAD HDR #5                                |
         | ,MSG:galms.mcv/46                                 |
         -----------------------------------------------------

  Bad header errors can be caused by two separate circumstances.  The
  first case can occur if you lower the value of NSIGS below the highest
  number forum in your system.  Unfortunately, forum numbers are not
  listed anywhere in the BBS online.  If you lowered the value of NSIGS
  to save memory and you receive this error message try the follow
  procedure:

  1.  Go into configuration Level 4 (Configuration Options) and search
      for the option "NSIGS".  Note the number that it is currently set
      to, and increase it to 3500.

  2.  Go to Level 7 (Basic Utilities) and select the option GALSORT.

  3.  Go back into configuration level 4 (Configuration options) and
      change the NSIGS option back to the number it was set to
      originally.

  4.  Bring your BBS back online.  If you still receive the Bad Header
      message, you will need to increase the NSIGS option.  Try
      incrementing by 10 at a time.  If you reach 3500, then the problem
      is not related to the number of forums you are running.  You will
      need to contact Galacticomm Technical Support.  However, if you
      increase the number and the error no longer occurs, you are set.

  If you have not been adjusting your NSIGS option, and suddenly receive
  a Bad Header message, this indicates that an illegal message is
  located in your GALMSG.DAT file.  You can attempt to correct the
  problem by typing the following at the DOS prompt:

     BBSBTR     <Enter>
     BBSRIDX    <Enter>
     BBSRMB     <Enter>

  If you still encounter the above error message, please call
  Galacticomm Technical Support for further assistance.


         -----------------------------------------------------
         | 07-FEB-94 19:04:12                                |
         | GMDNAM: CAN'T OPEN "GALFIL.MDF"                   |
         | ,MSG:bbsrip.mcv/8                                 |
         -----------------------------------------------------

  Each module of The Major BBS requires a file with the extension of
  .MDF.  This file tells the BBS the name of the executable for that
  module, or .DLL file, as well as the name of the .MSG file that holds
  the configuration, and text blocks for that module.

  During the loading of the BBS, many DLLs will attempt to open related
  .MDF files.  If the BBS is unable to open the associated .MDF file,
  the above CATASTRO will occur.

  In the above error, the BBS had located GALFIL.DLL, and then attempted
  to search for its associating GALFIL.MDF file.  It was unable to
  locate GALFIL.MDF, so it produced the CATASTRO message shown above.

  To correct this situation verify that the correct .MDF file exists in
  the BBSV6 directory.  If it doesn't, extract it from the appropriate
  archive file.  You can locate which file it is located in by typing
  the following commands at the DOS prompt:

     PKUNZIP -V *.ZIP <FILENAME>.MDF
     PKUNZIP <ZIPNAME> <FILENAME>.MDF


         -----------------------------------------------------
         | 15-MAR-94 14:23:04                                |
         | GMDNAM: NO MODULE NAME IN "GALFIL.MDF"            |
         | CH01=:0/0,MSG: bbssup.mcv/121                     |
         -----------------------------------------------------

  Similar to the above error, the BBS is having trouble with a .MDF
  file.  In this instance, the BBS has located the .MDF file, but was
  unable to locate the "Module Name:" line in the file.

  Shown below is an excerpt from a valid GALFIL.MDF file:

               ; GALFIL.MDF

               Module Name: File Libraries

               Developer: Galacticomm


  The second line of this file tells the BBS what the name of this
  module is.  In this case, it is given the name of "File Libraries". If
  there is no text after the ':' the BBS will assign a blank name for
  the module.  This is not considered an error condition but you may
  wish to assign a name yourself.


II. Btrieve Error Messages
--------------------------

Btrieve is the name of the database engine that Galacticomm uses for the
data files of The Major BBS.  Btrieve files use a B-tree for locating
records quickly.  The actual file format is proprietary.

Btrieve Errors are a class of CATASTRO errors, except that they are
related to problems surrounding the data files of The Major BBS, while
other CATASTROs relate to different aspects of the BBS.  Btrieve errors
are displayed in a red box with a flashing border.

  Here's an example of a Btrieve error message:

         -----------------------------------------------------
         | 22-DEC-93 16:03:04                                |
         | BTRIEVE OPEN ERROR 12 ON FILE "bbsvbl.dat"        |
         | CHFFF=:0/0,MSG:bbsacct.mcv/6                      |
         -----------------------------------------------------

  This message will also be written to a file in your \BBSV6 directory
  named CATASTRO.TXT.  The entry in your CATASTRO.TXT file for the above
  error would look like this:

  22-DEC-93 16:03:04 BTRIEVE OPEN ERROR 12 ON FILE "bbsvbl.dat"
  CHFFF=:0/0,MSG:bbsacct.mcv/6

  Another error message would look like:

         -----------------------------------------------------
         | 22-DEC-93 16:06:18                                |
         | BTRIEVE DELETE ERROR 4 ON FILE "galmsg.dat"       |
         | ,MSG:bbsmajor.mcv/-1                              |
         -----------------------------------------------------

  The following is a partial list of the more common Btrieve error
  messages, that occur while operating The Major BBS.  If you do
  encounter any of the following errors, and the solution doesn't work,
  please call Galacticomm Technical Support for assistance.

  The following Btrieve errors will be listed in order by error code:

  ERROR
  CODE    ERROR MESSAGE
  =====   ================================================================

  2       BTRIEVE <function> ERROR 2 - I/O Error

          This error is encountered during a read or write of the disk.
          This error usually means that the file is corrupt, or that
          there is a bad sector on the disk.  You should run a disk
          repair utility such as DiskFix (part of PC Tools from Central
          Point Software), Norton Disk Doctor (part of the Norton
          Utilities from Symantec) or ScanDisk (included with MS-DOS 6.0
          and above), which will scan your hard disk for any problems,
          and repair them if possible.  After this, you should try a
          re-index of the file that the error was encountered on.  This
          can be done by typing the following at the DOS prompt:

                  BBSBTR                  <Enter>
                  BBSRIDX <filename>      <Enter>

          Replace "<filename>" with the actual name of the file that was
          reported in the Btrieve error message, *but* leave off the
          extension of that filename.  For example, if you receive a
          "BTRIEVE ERROR 2 ON FILE "galmsg.dat", you would type:

                  BBSBTR                  <Enter>
                  BBSRIDX GALMSG          <Enter>


  5       BTRIEVE INSERT ERROR 5 - Duplicate Key Value

          The BBS attempted to insert a record into one of the data
          files which does not permit duplicate key values.

          In its most common form, this error will generally occur on
          the GALMSG.DAT file.  This error is likely to occur when the
          BBS crashes and the message counters for the GALMSG.DAT file
          are not reset (in normal usage the BBS will automatically try
          to correct the counters on its own).  To reset the counters
          manually, type the following at the DOS prompt:

            BBSBTR      <Enter>
            BBSRIDX     <Enter>
            BBSRMB      <Enter>

         If this error occurs on some file other than GALMSG.DAT please
         contact the appropriate vendor for technical support.


  12      BTRIEVE OPEN ERROR 12 - File Not Found

          The BBS was looking for a certain file, but could not find it,
          and will not be able to continue without that file.  You
          should use the "DIR" command in DOS to search for that file,
          or a File Find-type program (such as Norton File Find) and
          search for that file.  You may find that file does not exist.
          If you have a backup, you should restore that file from the
          backup.  If you do not have a backup, you will need to copy
          the appropriate .VIR file to a file with a .DAT extension. For
          example:

            COPY GALREG.VIR GALREG.DAT  <Enter>

          If your BBS is located on a network drive, make sure that the
          BBS has read/write access to that file.

  18      BTRIEVE INSERT/UPDATE ERROR 18 - Disk Full

          There is no free disk space available on the hard disk to
          write this file.  You will need to erase any unneeded files
          from your hard disk.  Otherwise, a larger hard disk will be
          needed.  Additionally, although The Major BBS itself can't
          make use of additional hard drives for storing its own files,
          it does allow you store your files for your File Libraries on
          additional drives.  Consult the System Operations Manual for
          information about "Alternate File Path" (for Version 6.2 and
          above) or "Alternate Path Prefix" (for earlier versions).

          One alternative to stay away from: disk compression software.
          Galacticomm does not recommend the use of any type of disk
          compression utilities such as DoubleSpace or Stacker with The
          Major BBS.  The drawbacks to disk compression is decreased
          speed and possible serious data loss.


  43      BTRIEVE ABSOLUTE ERROR 43 - Invalid Record Address

          The BBS attempted to read a data record from a direct offset
          that was invalid for the specified Btrieve File.  This error
          can be the result of a corruption between the file index and
          the data records.  The solution is to re-index the offending
          data file.  This can be accomplished with the following set of
          commands:

            BBSBTR              <Enter>
            BBSRIDX <filename>  <Enter>

          If the error persists, the problem is code related and should
          be reported to the appropriate vendor.


  86      BTRIEVE OPEN ERROR 86 - File Table Full

          Btrieve maintains a table of all the files it has opened.
          Normally the BBS can calculate the number of files that will
          be opened.  However, if the BBS does not properly close files,
          you may receive this error the next time the BBS comes up. You
          can manually adjust the /F parameter contained in the
          BBSBTR.BAT as a temporary fix.  You should contact all vendors
          that have supplied you with add-ons for the BBS to notify them
          that you are encountering this error.

          This error may also occur if a vendor does not properly supply
          the BBS with the number of Btrieve files it needs to open.
          Once again you should contain all your vendors to attempt to
          get a permanent solution.

          The default BBSBTR.BAT file consists of the following:

                  BTRIEVE >NUL /P:2048 /F:35 /M:64 /E

          The /F switch controls the file table, which in this case,
          sets it at 35.  If you receive this error message, increase
          the amount of files by ten.  If you still receive the message,
          increase it by another ten.

          Be aware that this file is changed every time you install an
          add-on, remove an add-on, or change your configuration.
          Because of this, you should put a read-only attribute on the
          file so that it is not changed by the BBS when you change
          something in your configuration.  It is recommended, however,
          that you remove the read-only parameter if you are going to be
          installing an add-on or removing an add-on.  You can always go
          back into the BBSBTR.BAT file and change the /F parameter when
          it is done.


  94      BTRIEVE ERROR 94 - Permission Error

          The BBS was unable to access the named file due to it either
          being read-only, or hidden.  If the BBS is on a network, make
          sure that it has read/write access to the directory.  If it is
          not on a network, make sure that there are not any read-only
          or hidden attributes on the file.

  The above list does not contain all of the Btrieve errors.  They are
  only the errors that have been encountered the most often.  If you do
  encounter an error that is not in the above list, please call
  Galacticomm Technical Support.  We will be able to tell you what the
  error entails and how to go about solving it.


III. Phar Lap 286|DOS Extender Error Codes
------------------------------------------

The Major BBS uses the Phar Lap 286|DOS Extender to take advantage of
Extended Mode Memory.  Phar Lap puts any 80286 or better computer into
"Protected Mode", where Extended Memory can be accessed.  Here are some
of the more common error codes generated by Phar Lap while running The
Major BBS.


  Fatal Error 286.2170 - Out of memory
  Fatal Error 286.2230 - Out of memory

  Phar Lap has run out of memory while loading the BBS.  The BBS
  requires approximately 3 free megabytes of Extended Mode Memory.  Go
  through your CONFIG.SYS file, removing any statements that are not
  necessary for the operation of your BBS.  We recommend that you simply
  comment out the lines by putting REM in front of the line you wish to
  disable.  If you are running EMM386, you should disable it.  If you
  are running QEMM, be sure Stealth mode is not enabled.  Do not use the
  LOADHIGH (or LH) statement.  Also, disable any STACKS or FCBS
  statements that are present.  The CONFIG.SYS file that we recommend
  is:

        FILES=127
        BUFFERS=30

  Do not disable any statements that pertain to CD-ROMs, Network
  Interface Cards or other devices that your BBS accesses.  Also be sure
  to remove any unnecessary TSRs (Terminate-Stay-Resident) from your
  AUTOEXEC.BAT file.  TSRs may include mouse drivers, virus checkers,
  etc.  If you need to take a command out of your AUTOEXEC.BAT file, it
  is recommended that you REM it out.  For example, if you have the
  following AUTOEXEC.BAT file:

        @echo off
        path=c:\;c:\dos;c:\bbsv6
        prompt $p$g
        c:\mouse\mouse.com
        cd\bbsv6
        bbs go

  In this AUTOEXEC.BAT file, you are loading the mouse driver in line 4.
  Change the AUTOEXEC.BAT file so that line 4 is REM'd out.  The results
  are:

        @echo off
        path=c:\;c:\dos;c:\bbsv6
        prompt $p$g
        REM c:\mouse\mouse.com
        cd\bbsv6
        bbs go

  If cleaning out your CONFIG.SYS and AUTOEXEC.BAT does not solve the
  problem, then you will need to increase the memory in your computer by
  adding more RAM.


  Fatal Error 286.2360 - Out of Interrupt Stacks

  The BBS has exhausted its interrupt stacks.  This is generally caused
  by overtaxing your system.  For example, if you are running 32 14.4K
  lines on a 386SX/16, you probably would get this error message.  Try
  reducing the number of channels.  If you have serial channels that are
  not being used, remove them.  If your polling rate is set to 38400,
  try lowering it to 9600, or if it is at 9600, change it back to AUTO.
  If this has already been done, contact Galacticomm Technical Support.


  Fatal Error 286.3330 - <exception> detected

  This is an exception error.  Phar Lap had problems trying to execute a
  computer instruction.  There are 17 separate classes of this type of
  error.  The most common is called a General Protection Fault, or GP
  for short.  If the BBS errors with a General Protection Fault
  detected, in most cases the system will not display the above message
  but instead notify you that such an error occurred and then
  automatically reboot.  Whenever possible, the BBS will create a GP.OUT
  file in your \BBSV6 directory.  This file can be helpful in
  determining what the computer didn't like.  This file will list what
  modules were loading, and what the computer was doing at the time of
  the error.  If you do have a GP.OUT file, you should either fax it to
  technical support or upload it to the Galacticomm Demo System BBS to
  the User-ID "Tech Support".  In most cases, we will be able to tell
  you what occurred and what the solution is, if one exists.


IV. Reading a GP.OUT File
-------------------------

When the BBS encounters a General Protection Fault, it may try to
recover from it a configurable number of times.  If the BBS is unable to
recover from the error, it will create a GP.OUT file in the \BBSV6
directory. This GP.OUT file is a listing of where the error occurred,
the time and date it occurred, the DLL's that were loaded, and a
routines section.

There are three options in level 1 (hardware setup) configuration that
affect the way the General Protection Fault recovery acts.  These three
options are:

        GPHDLR  Continue operation after "GP" errors?
        GPSLMT  Number of attempts to recover from a "GP"?
        GPBOOT  Reboot computer after unrecoverable "GP"?

The first option, GPHDLR, tells the system whether or not you want it to
attempt to recover from a General Protection Fault.  This option relies
on the option below it, GPSLMT, as to how many times it will attempt to
recover.  The default number of attempts is 2000, which means that the
BBS will try to recover 2000 times from a General Protection Fault
before shutting down.  If the BBS is unable to recover from a General
Protection Fault, GPBOOT tells it whether or not it should reboot, if it
is capable of it.

If you have the system set to try to recover from a general protection
error, and it is unable to, it will try to create a GP.OUT file.  This
GP.OUT file will also contain the amount of times it tried to recover
from the error.  The more times you try to recover from the fault, the
less useful the GP.OUT file is.

In order to determine the exact location the error occurred, you would
set the option GPHDLR to NO, and the option GPBOOT to YES.  This will
cause the BBS to immediately halt after it encounters a General
Protection Fault, create a GP.OUT file, and attempt to reboot the
system.  If the BBS is unable to reboot the system, you will need to do
so yourself, after all hard disk activity has ceased.

The following is a GP.OUT file that was created with the system set not
to try to recover from the fault:

        BBS GP @ 307F:4823 EC 0000 (recorded 02/19/94 03:06:34)
        GP'ed between 307f:23b1 _VALNAME and 307f:e5d5 _TAGOFF
        AX=06ff BX=060b CX=0000 DX=06ff SI=0000 DI=ffff BP=0f44 ES=5254
        DS=3097 Flags=3246
        Current CS:IP==>26 83 3f 01 74 16 b8 ff 06 8e c0 26 c4 1e d5 05

        BBS Version: 6.20a
        User 41 channel 2A User-ID "Evil Current" status 240
        Online level 6, state 8, substate 118
        MSG:galfil.mcv/-1
        Module "File Libraries"
        Input """"```````"

        0177=C:\BBSV6\MAJORBBS.EXE
        089f=C:\BBSV6\GALGSBL.DLL
        08c7=C:\BBSV6\BBSBTU.DLL
        08e7=C:\BBSV6\DOSCALLS
        0907=C:\BBSV6\GALMSG.DLL
        2f77=C:\BBSV6\MR_MJRCD.DLL
        2fb7=C:\BBSV6\TTICCM.DLL
        2fef=C:\BBSV6\FW_OTHEL.DLL
        301f=C:\BBSV6\GALGLO.DLL
        3047=C:\BBSV6\GALGWI.DLL
        306f=C:\BBSV6\GALFIL.DLL
        30bf=C:\BBSV6\FW_TRIV.DLL
        3117=C:\BBSV6\FW_ACT.DLL
        315f=C:\BBSV6\GALBJ.DLL
        3187=C:\BBSV6\GALETL.DLL
        3207=C:\BBSV6\GALREG.DLL
        322f=C:\BBSV6\GALRSY.DLL
        326f=C:\BBSV6\GALUIE.DLL
        3297=C:\BBSV6\GSSTFEDT.DLL
        32c7=C:\BBSV6\MJSMAS.DLL
        32ef=C:\BBSV6\MJWMUT.DLL
        33a7=C:\BBSV6\MJSWHL.DLL
        33df=C:\BBSV6\PROCC.DLL
        340f=C:\BBSV6\GALNOTE.DLL
        3437=C:\BBSV6\ESCWARN.DLL
        3467=C:\BBSV6\GALQWK.DLL
        349f=C:\BBSV6\GALTXV.DLL
        34c7=C:\BBSV6\GALXIT.DLL
        34ef=C:\BBSV6\GALHNG.DLL
        3517=C:\BBSV6\GALPOK.DLL
        3547=C:\BBSV6\HVSAUTOV.DLL
        3577=C:\BBSV6\GALAND.DLL
        35a7=C:\BBSV6\HVSTW.DLL
        3777=C:\BBSV6\GALLOT.DLL
        37a7=C:\BBSV6\ETICONF.386
        37d7=C:\BBSV6\PROML.DLL
        380f=C:\BBSV6\ESCFCM.DLL
        384f=C:\BBSV6\GALFAZ.DLL
        38ff=C:\BBSV6\GALSNV.DLL
        3937=C:\BBSV6\GALTNG.DLL

The first part of the file is the header.  The first line of the header
is what is used to locate the address causing the problem.

        BBS GP @ 307f:4823 EC 0000 (recorded 02/19/94 03:06:34)

Above is the first line of the header for this GP.OUT file.  This header
shows that the GP occurred at address 307f:4823 at 03:06:34 on 02/19/94.

The second part of the GP.OUT file tells who was online when the system
encountered the General Protection Fault, and what the last input was.
The third part of the GP.OUT file is a list of all the modules that were
loaded in the system at the time.  Each module name, or DLL, is preceded
by an address.  For instance, the address of MAJORBBS.EXE is 0177.

While looking at the third section of the GP.OUT, you will notice that
there is no address 307f.  Because of this, you will have to locate the
first address lower than 307f.  In this case, the address is 306f, which
is GALFIL.DLL.  GALFIL.DLL is the File Library module, so you know that
the error occurred somewhere in the File Libraries.

Once you locate the address and module that the fault occurred in, you
will be able to tell which company the module belongs to.  Each company
has its own developer ID.  For instance, if you look at the module
GALFIL.DLL, the first three letters are Galacticomm's developer ID, GAL.
At this point you can contact the appropriate vendor about the General
Protection Fault.

Not all GP.OUT files are as easy to read as the one above.  If you
encounter a GP.OUT file that you cannot interpret, please call Technical
Support, and we will be happy to assist you in determining where the
General Protection Fault occurred.

                               #  #  #  #

Galacticomm Technical Support is available Monday through Friday, from
8:30am - 6:00pm ET by calling (305) 321-2404.  Support is also available
via the Internet by sending electronic mail to 'support@gcomm.com' or by
calling the Galacticomm Demo System BBS at (305) 583-7808 and writing a
message to 'Tech Support'.

Galacticomm, Inc.                          Tech Support: (305) 321-2404
4101 SW 47th Ave., Suite 101                      Sales: (800) 328-1128
Fort Lauderdale, FL 33314                           Fax: (305) 583-7846

All product names are trademarks or registered trademarks of their
respective suppliers.  These technical notes are freely distributable.
