PTT Initialization Errors
=============================================================
PTT Initialization errors  are ones that occur during the execution 
of the startup functions of PTT. These  errors are used to inform the
user that while the PTT  program was  attempting to  initialize, an
error has occurred and the program is aborted.

There are two subsystems in which you will get an initialization error: the
virtual memory  subsystem and  the message subsystem.  A listing of all the
potential error  codes, their  descriptions, and ideas for solving them are
listed below.


Loader error (0001): out of memory
-------------------------------------
This message means that there is not enough Extended Memory (XMS) available
for PTT to load. PTT 3.20+ no longer uses EMS (Expanded Memory) and instead
uses XMS memory. 


Virtual Memory Subsystem

When  you  experience  an  error  while  initializing  the  virtual  memory
subsystem, the program will immediately abort with a message stating:

      Error Initializing Virtual Memory Subsystem!!
      Exiting with error code ??

where ??  is the  error code necessary for determining the error.  Here are
all existing error codes for initializing the virtual memory subsystem.

Error 101:

     This is  a memory  allocation error results from a failure during
the allocation of a 64K buffer that is  required to  do memory swapping
to either XMS or disk space.

     You just do not have enough available heap space to initialize the
program and must find a  way to  free up memory by removing a TSR or
virtual disk.

Error 104:

     This error  occurs when  either the EMS or XMS drivers fail when
attempting to do a memory copy. It has never occurred yet.

     This error is usually the result of a hardware or software failure.
You may however try rebooting your system and execute the program again.

Error 110:

     This is another memory allocation error that occurs when there is
not enough memory to run the program. 

     For a quick and easy fix, please see the description above for an
error 101.

Error 112:

     This error occurs when the virtual memory subsystem is unable to
open a temporary file. The most common reason why a temp file is unable
to be created is that the TEMP environmental variable is not set to a
valid directory.  Two other possible causes are that there is not
enough disk space or that your FILES= setting in your CONFIG.SYS is too
low.

     In almost all cases, setting the TEMP directory in your DOS
environment will relieve you of this error. You would most likely place
this setting in your AUTOEXEC.BAT file, and the syntax looks like this:

                      SET TEMP=C:\TEMP

where C:\TEMP is a valid directory on your hard drive.  If this is
not successful, check your hard drive space and your FILES= setting.

Error 113:

     This error occurs when a swap file is created, but is unable to be
read. This error would only be caused by a hardware failure.

     You would need to find the cause of the hardware failure to fix this
error.

Error 114:

     This error also occurs when a swap file is created, but is unable to
be written to.  This error is also the result of a hardware failure, and
you would need to find the cause of the failure to resolve this error.

Error 115:

     This error occurs when a swap file is created but is unable to be
extended. This error is usually the result of running out of disk space.

     The obvious solution to this error is to free up some disk space.

Message Subsystem

When you  experience an error while initializing the message subsystem, the
program will immediately abort with a message stating:

      Error Initializing Message Subsystem!!
      Exiting with error code ??

where ??  is the  error code necessary for determining the error.  Here are
all existing error codes for initializing the message subsystem.

Error -2:

     This error occurs when your program does not have enough heap space to
initialize.

     The simple  solution is to free up heap space.  
     See the description for error 101 for more details.

Error 65:

     This error  occurs when the message data is not in a valid format.
This error usually results because the program file has been corrupted
during a download.

--------------------------------------------------------------------
                QEMM 7.xx users:
--------------------------------------------------------------------
If you are using QDPMI (QEMM's DPMI server), you will need to increase
the SWAP size to 4096 to run PTT. 

If you have a missing hard disk drive ID:, for example you have drives
C:, D:, and F:, but do not have a drive E: defined, you will get a
Drive Not Ready error from DOS when you use the File Selection Dialog
in PTT. This is a conflict between PTT and the QDPMI driver. You can
either remove or comment out the QDPMI loading in your CONFIG.SYS or
you can substitute drive E: for some other directory on your system.
To do this, type 
        SUBST E: C:\
which will make drive E: look like drive C: to DOS.




