









                          Error Code Listings for
                            WILDMAIL! and WCFF!

                         Online Computer Resources
                  4330-J Clayton Road, Concord, CA 94521


                         Voice: (510) 687-1122  
                           BBS: (510) 687-0236 USR DS   
                                (510) 687-2134 V32bis

                             Revised: 10/22/92







                            ERROR CODE LISTINGS

                             TABLE OF CONTENTS



          INTRODUCTION  . . . . . . . . . . . . . . . . . . . . . . . .   1 

          DOCUMENT LAYOUT . . . . . . . . . . . . . . . . . . . . . . .   1 

          TROUBLESHOOTING . . . . . . . . . . . . . . . . . . . . . . .   1 

          BTREE FILE ERROR CODES. . . . . . . . . . . . . . . . . . . .   2 

          TURBO PASCAL RUN TIME ERRORS. . . . . . . . . . . . . . . . .   4 
               DOS ERRORS . . . . . . . . . . . . . . . . . . . . . . .   4 
               I/O ERRORS . . . . . . . . . . . . . . . . . . . . . . .   5 
               PROGRAM RELATED ERRORS . . . . . . . . . . . . . . . . .   5 
               CRITICAL ERRORS  . . . . . . . . . . . . . . . . . . . .   6 
               FATAL ERRORS . . . . . . . . . . . . . . . . . . . . . .   7 
               CRITICAL PROGRAM RELATED ERRORS  . . . . . . . . . . . .   8 



































                                     i


          ERROR CODE LISTING                                     Page  1
          INTRODUCTION



          INTRODUCTION

          WILDMAIL! and WCFF! (as well as WILDCAT! v3.+) has been written
          with Borland's Turbo Pascal v6.00 along with using Turbo Power
          Software's BTree Filer program to manage the database files. For
          those not familiar with BTree Filer from TurboPower Software, this
          is a special collection of procedures and routines for manipulating
          the database files used within WILDCAT! v3.+.  For programs such
          as WILDMAIL! and WCFF! to properly access these files requires that
          they use these same routines to ensure integrity of the database
          files.  Because this is a separate software package (used only in
          the developmental stages), it produces its own set of error codes
          which are covered here in addition to the regular error messages
          produced by Borland's Turbo Pascal.



          DOCUMENT LAYOUT

          This document has been laid out with 2 basic sections in mind, one
          for when BTree Filer routines produce an error and the other for
          errors generated by Turbo Pascal.  



          TROUBLESHOOTING 

          Because of the various different operating environments a program
          may be executed under, error messages generated at run time may
          require close observation to determine what was happening at the
          point in time the error occurred.  Often times this is necessary
          to get a better understanding of what was going on to help isolate
          possible causes of the error produced.

          The error codes presented here are taken directly out of the
          appropriate manuals and include a brief description of possible
          problem resolutions.  Because of the wide variety of different
          system configurations, often times it's hard to obtain an exact
          "fix" to the error produced.  With that in mind, use this
          information as a reference only and not as a troubleshooting guide.




          BTREE FILER v5.23                                      Page  2
          ERROR CODES



          BTREE FILER ERROR CODES

           9900     INVALID PATH NAME
                    This error generally indicates a configuration error. 
                    Please recheck your setup/configuration and ensure that
                    all subdirectories on the specified drives do in fact
                    exist and conform to DOS character limitations.

           9901     TOO MANY OPEN FILES
                    An attempt has been made to open too many files.  DOS
                    never allows more than 15 open files per process.  If
                    you get this error with less than 15 files, it may
                    indicate that the CONFIG.SYS file FILES=xx entry
                    specifies too few files.  This can commonly happen when
                    operating under a multi-tasking environment such as
                    DESQview.  Simply increase the number to some suitable
                    value, for example, FILES=65.
                    
           9902     CURRENT DIRECTORY IS FULL
                    An attempt has been made to save a file to a directory
                    when there is no more room in the FAT.  This error is
                    rare and can occur when you try and save too many files
                    in the root directory on the specified drive.  Delete
                    unnecessary files and re-execute program.

           9903     FILE NOT FOUND
                    This error is relatively straight forward.  Normally
                    this is a configuration type error.  Recheck your
                    configuration paying close attention to the definitions
                    for your database files.

           9904     INVALID FILE DESCRIPTOR
                    This file name specified in your configuration does not
                    contain valid DOS characters.  Please recheck your
                    configuration/setup.

           9905     READ REQUEST EXCEEDS 64K BYTES
                    This is typically a programming error and should never
                    be encountered.

           9906     WRITE REQUEST EXCEEDS 64K BYTES
                    This is typically a programming error and should never
                    be encountered.

           9907     ERROR RETURNING FILE SIZE

           9908     INVALID FILE ACCESS MODE
                    This is typically a programming error and should never
                    be encountered.



          BTREE FILER v5.23                                      Page  3
          ERROR CODES



          ERROR CODES - continued

          10010     INDEX FILE PROBABLY CORRUPT
                    This error indicates the index file of the database
                    being accessed has somehow been corrupted.  Run WCREPAIR
                    on the appropriate database and re-execute the program.

          10070     FILE READ ERROR
                    This error indicates the program had problems reading
                    the .DIA file for requested message conference.  Deleted
                    the appropriate .DIA (dialog) file or run WCREPAIR on
                    the database and re-execute the program.

          10090     INSUFFICIENT MEMORY
                    The amount of available memory at runtime is not enough
                    to allow proper operation of the program.  Increase
                    memory or increase the DESQview window size.

          10100     INSUFFICIENT MEMORY
                    Similar to 10090, make more memory available to the
                    program.

          10110     DRIVE NOT READY
                    This error indicates a hardware error where the
                    requested drive for some reason is no longer available
                    for access.  Somehow restore drive to a ready state and
                    re-execute the program.

          10140     UNEXPECTED DOS ERROR
                    When the program attempted to access a file, for some
                    reason DOS returned an error message.  This could
                    indicate a SHARE related problem, WRITE PROTECTED files
                    and so on.  Recheck access rights and re-run program.

          10170     FREE RECORD LIST CORRUPT
                    Information maintained inside of the associated database
                    file has become corrupted.  Run WCREPAIR on the affected
                    database and restart program.

          10180     ATTEMPT TO REPAIR FILEBLOCK FAILED
                    Information maintained inside of the associated database
                    file has become corrupted.  Run WCREPAIR on the affected
                    database and restart program.

          10310     NETWORK INITIALIZATION ERROR
                    This error typically indicates a problem accessing the
                    network.  Is there really a network running?

          10356     INSUFFICIENT MEMORY
                    The amount of available memory at runtime is not enough
                    to allow proper operation of the program.  Increase
                    memory or increase the DESQview window size.



          TURBO PASCAL v6.00                                     Page  4
          ERROR CODES



          RUN TIME ERRORS

          Certain errors at run time cause the program to display an error
          message in the following format and then terminate.

                    Run-time error NNN at XXXX:YYYY

          Where NNN is the run-time error and XXXX:YYYY is the run-time error
          address (segment and it's offset).

          The run-time errors are divided into four categories: 

                    DOS errors          1 thru 99
                    I/O errors          100 thru 149
                    CRITICAL errors     150 thru 199
                    FATAL errors        200 thru 255


          DOS ERRORS

          002  FILE NOT FOUND
               Specified file can not be located.  Within the path defined,
               the program cannot locate the needed file.  Please recheck
               your setup/configuration.

          003  PATH NOT FOUND
               Path defined is invalid or specifies a nonexistent
               subdirectory.  This is typically a configuration related
               problem.

          004  TOO MANY FILES OPEN
               An attempt has been made to open too many files.  DOS never
               allows more than 15 open files per process.  If you get this
               error with less than 15 files, it may indicate that the
               CONFIG.SYS file FILES=xx entry specifies too few files.  This
               can commonly happen when operating under a multi-tasking
               environment such as DESQview.  Simply increase the number to
               some suitable value, for example, FILES=65.

          005  FILE ACCESS DENIED
               This error is reported when an attempt has been made to read
               or write to a file that has some form of protection preventing
               the operation from taking place.  Shown below is a list of
               possible causes.

               o    Attempting to add information to a file or sub-directory
                    that is flagged as read only.

               o    Specified sub-directory is full and no files may be
                    added.



          TURBO PASCAL v6.00                                     Page  5
          ERROR CODES



          RUN TIME ERRORS - continued


               o    Attempt has been made to create a previously existing
                    file or sub-directory.

               o    Attempt to remove a sub-directory that isn't empty, a
                    invalid sub-directory or if the path specifies the root
                    directory.

               o    Specified file has not been previously opened for
                    reading or writing.


          017  CANNOT RENAME ACROSS DRIVES
               An attempt has been made to rename a directory which is not
               on the current drive.  Normally, you shouldn't receive this
               error, but if you do, this indicates a problem with the
               executing program.


          I/O ERRORS

          100  DISK READ ERROR
               An attempt has been made to read past the end of file marker. 
               Since the file name is not reported with this error, it can
               be difficult to isolate.  This error requires you to very
               carefully watch the program and see what it was doing
               precisely before the error occurred.  Then you might be able
               to isolate the action being performed and identify the
               problem.

          101  DISK WRITE ERROR
               An attempt has been made to write information to disk without
               having sufficient room to save it in.  This error is
               relatively straight forward.  Depending on what the needs of
               the program are, disk space requirements can vary.  Best thing
               to do is free up as much space as possible and re-execute the
               program.


          PROGRAM RELATED ERRORS

          Shown below is a list of possible error codes that should never
          happen.  These errors are usually found and fixed prior to general
          release of the program.  If you do encounter one of these errors,
          please call tech support.


          102  FILE NOT ASSIGNED
               A variable has not been assigned to a file.




          TURBO PASCAL v6.00                                     Page  6
          ERROR CODES



          PROGRAM RELATED ERRORS - continued

          103  FILE NOT OPEN
               An attempt has been made to access a file that has not been
               previously opened for reading or writing.

          104  FILE NOT OPEN FOR INPUT
               An attempt has been made to access a file that has not been
               previously opened for input. 

          105  FILE NOT OPEN FOR OUTPUT
               An attempt has been made to access a file that has not been
               previously opened for output. 
               

          CRITICAL ERRORS

          Critical errors are general associated with the hardware of your
          PC, specifically, your hard disk.  Sometimes these errors can be
          generated by improperly configured disk caching software.  Since
          it's beyond the scope of this document to tell you how to fix a
          hardware problem, use these error codes for reference only!

          150  DISK IS WRITE PROTECTED

          151  UNKNOWN UNIT

          152  DRIVE NOT READY

          153  UNKNOWN COMMAND

          154  CRC ERROR IN DATA

          155  BAD DRIVE REQUEST STRUCTURE LENGTH

          156  DISK SEEK ERROR

          157  UNKNOWN MEDIA TYPE

          158  SECTOR NOT FOUND

          159  PRINTER OUT OF PAPER

          160  DEVICE WRITE FAULT

          161  DEVICE READ FAULT

          162  HARDWARE FAILURE



          TURBO PASCAL v6.00                                     Page  7
          ERROR CODES



          FATAL ERRORS

          These errors always immediately terminate the program and return
          to DOS.  Depending on the operation that was in progress at the
          moment one of these errors occurred, your database files may not
          have been properly closed and could result in corrupted data. 
          Normally running WCREPAIR (database repair program) will fix most
          any database error.

          200  DIVISION BY ZERO
               An attempt has been made to divide a number by zero. 
               Typically a programming error.

          201  RANGE CHECK ERROR
               The index expression of an array qualifier was out of range. 
               Typically a programming error.

          202  STACK OVERFLOW ERROR
               This error is reported when there is not enough stack space
               to allocate the subprograms local variables.  This error
               indicates insufficient memory has been allocated to the
               executing program.  If you're operating in DESQview, allocate
               more memory to the window or remove (unload) previously
               installed TSR programs and re-execute the program.

          203  HEAP OVERFLOW ERROR
               This error is reported when there is not enough free space in
               the heap to allocate a block of the requested size.  This
               error is similar to #202 in that there is not enough free
               memory available to execute in.  Allocate more memory and re-
               execute.

          204  INVALID POINTER OPERATION
               This error is reported if the pointer is nil or points to a
               location outside of the heap, or if the free list cannot be
               expanded due to a full free list.



          TURBO PASCAL v6.00                                     Page  8
          ERROR CODES



          CRITICAL PROGRAM RELATED ERRORS

          Shown below is a list of errors that should never be encountered
          because these errors are usually found in the developmental stages
          of the program.  If you do encounter one of these errors, please
          contact technical support and report the problem and exactly how
          it happened.


          205  FLOATING POINT OVERFLOW
               A floating-point operation produced a number too large for the
               numeric coprocessor (if any) to handle.

          206  FLOATING POINT UNDERFLOW
               A floating-point operation produced an underflow.  This error
               is only reported if you are using a 8087 numeric coprocessor
               with a control word that unmasks underflow exceptions.  By
               default, an underflow causes a result of zero to be returned.

          207  INVALID FLOATING POINT OPERATION
               The real value passed could not be converted to an integer
               within the Longint range.

          208  OVERLAY MANAGER NOT INSTALLED
               The program is calling an overlaid procedure or function, but
               the overlay manager is not installed.

          209  OVERLAY FILE READ ERROR
               A read error occurred when the overlay manager tried to read
               an overlay from the overlay file.

