
 Error Listing for Bre / Fe / Tal


2 - File not found
    Check the Resource.dat and other configuration files to make sure
    that all the files exist (check for misspelled directory names too).

3 - Path not found
    Make sure (in the configuration files) that all the directory names
    are right.  This is reported when BRE tries to write a file to a
    directory that does not exist, or if the filename is invalid.

4 - Too many open files
    Try increasing the FILES= statement in your CONFIG.SYS file.  If this
    problem persists, it may be a bug.  (BRE Betas 1, 2, and 3 had a bug
    of this nature.)

5 - File access denied
    Be sure none of your BRE data files are marked "read only".  Also,
    when specifying score and news files in Resource.dat, be sure you
    put a file NAME, not just a directory.

6 - Invalid file handle
    This should never occur.  It means DOS is badly corrupted; check
    for viruses and run CHKDSK on your hard disk.

100-Disk read error
    This usually indicates either a bug in the game or a bad inbound
    IP game packet.

101-Disk write error
    This usually means the disk is full.

102-File not assigned
    This should not occur -- please report it as a bug.

103-File not open
    This should not occur -- please report it as a bug.

104-File not open for input
    This should not occur -- please report it as a bug.

105-File not open for output
    This should not occur -- please report it as a bug.

106-Invalid numeric format.
    This usually means that in one of your configuation files, you have
    put text instead of a number.  The most common place this occurs is
    in the node list -- if you have an extra blank line somewhere, BRE
    will read the blank line as the BBS name and then the BBS name as
    the BBS number, and the name is not a number, so this error occurs.
    Check all the configuration text files to make sure it matches the
    format required by BRE.

=============================================================================

The following errors indicate a problem with your hardware, and not with BRE.
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

=============================================================================

200-Division by zero
    Please report this as a bug.

201-Range check error
    This can happen when your players' empires get larger than what BRE
    can handle.  It can also occur when corrupt IP packets arrive.  This
    is the main "the numbers are too big" error.  If you have run BRE
    PLANETARY, and this occurs, to salvage your game, delete the inbound
    packets. 

202-Stack overflow error
    Please report this as a bug.

203-Heap overflow error
    This indicates that the system has run out of conventional memory.
    BRE does not use EMS or XMS for data; it _can_ use EMS for swapping
    the program out, but empire data is stored in conventional memory.
    Try removing some device drivers or TSRs; also, check your BBS software
    to see if it can swap itself out before running door games.

204-Invalid pointer operation
    This should never occur - please report it as a bug.

205-Floating point overflow
    This rarely occurs, but if it does, it means numbers are too big
    for the game (or the math chip) to handle.

206-Floating point underflow
    This should never occur.

207-Invalid floating point operation
    This means that the numbers are too big for the game (or the math
    chip) to handle.
