

                              Memory issues:

Do  not use any 'front end' program that branches to this program and  then 
returns  back once this program is finished.   This type of program resides 
in memory.  It may conflict with this program and it will reduce the amount 
of memory available for this program.   An example of a 'front end' program 
is AUTOMENU [TM].

If  you use any kind of front end menu,  this program will  be  unable,  in 
time, to read its files.  Go into \ARCHITEC.ACS and execute this utility:  

                     CD \ARCHITEC.ACS
                     MEMORY    <========= you enter this
program responds  
with this  =====>   Machine is 14 % full.  555 bytes are free.
            
 
Observe  the '% full' number.   It should be between 8 and 16%.   If higher 
than that,  you have something loaded into memory that is conflicting  with 
the  program.   Remove it until the '% full' number is reduced to between 8 
and 16.


            Alternate methodology to check memory availability:

Look for the presence of 'MEMTEST.BAT' in \ARCHITEC.ACS.  If you observe this 
'BAT' file, then enter this command in the subdirectory:

                    MEMTEST    <======== you enter this 

The test that follows will display a memory usage and a memory map.

                       To rebuild corrupted indexes:

Let's  say that you are entering data and your power circuit has a  voltage 
surge,  thereby locking up your computer.   When you power up  again,  your 
indexes may have become corrupted and either you cannot go into the program 
or the data files become unreadable.   If that happens,  use this procedure 
in \ARCHITEC.ACS:
            
                               DEL *.MEM    <===== you enter these
                               DEL *.NTX    <======
                               GO           <====== 'GO' invokes PROGRAM.EXE

At this point,  the Installation menu will appear, indicate that you are on 
a  hard drive and follow the instructions.   The program will then recreate 
all the old indexes and attempt to read the old registration files. 


            Alternate methodology to rebuild corrupted indexes:

Look in \ARCHITEC.ACS and execute this command:

                                 DIR *.BAT

If you see a file named "CRISIS.BAT",  then invoke this file instead of the 
prior procedure.  It accomplishes the same thing.


                    CRISIS   <========= you enter this


