;
                                TESTERR.COM                                   

             Size (recs) CRC   Version    Author/Latest Issue      Disk
               1k (4)    3B5D  1.3        Howard Goldstein 2/91    Z3COM9

  1- Syntax  2- Assembly  3- Adding Programs  4- Notes                        


   TESTERR is based on FINDERR.COM by  Ted H. Emigh.   The  latter  caused the 
error counts returned by various programs to be stored in the ZCPR3 registers.
TESTERR, instead, uses the program error flag in the ZCPR3 message buffer.

   TESTERR eliminates  the  complex  macros  in FINDERR and provides a program
that will convert to Zilog opcodes  with ZCON and assemble  with ZAS.  
:1
 Syntax   TESTERR PN


...where PN is first letter of name of program to check.

   Programs supported: M80 F80 BASCOM CB80 JETFIND

   TESTERR reads the error count reported by the preceeding program & sets the
flag tested by the "IF ER" command.
:2
 Assembly 

   Since TESTERR uses no external references,  it can be assembled to a HEX or
COM file directly;  just  add the appropriate  ORG  directive and use MAC with
MLOAD instead of M80/L80, e.g.:

   MAC TESTER11 $-SPZ;MLOAD TESTERR=TESTER11
 
   SLRMAC (or even ASM with MLOAD) ought to work, too.   If using M80, comment
out the ORG directive, specifying the load address at link time instead, e.g.:

   M80 =TESTER11.ASM;L80 /P:9800,TESTER11,TESTERR/N/E
:3
 Adding programs 

   Additional programs can be  added  by  including  appropriate  branches and
sections of testing code.   The one  constraint that must be  observed is that
TESTERR itself must be short enough not to overwrite the memory locations that
contain the error counts.   If  that  becomes  a  problem,  the  built-in help
message could be  shortened  considerably.   If it  becomes  essential to test
addresses low in  memory,  then  an  RCP version of this program or of FINDERR
should be made, or it should  be written to run  higher in  memory and invoked
with GET and JUMP commands.

   One word of caution.   The original distribution of SYSFCP.ASM contained an
error in the IF ERROR function  --  the sensing is done in reverse!   IF ERROR
returns TRUE if the program error flag is reset and  FALSE if it is set.   You
must correct that error in your FCP or use the IF testing in reverse.
:4
 TESTERR Notes 

   a. Version 1.3 updates (2/28/91, Howard Goldstein):
      - Modified to work with JetFind Version 1.22, rather than 1.20.  Vs 1.22
        is the version that is currently being sold.
        
   b. Version 1.2 updates (2/21/91, Bruce Morgen):
      - Added support for the "hit count" of JetFind Version 1.20 (Plu*Perfect
        Systems).   If there are no  hits  (strings found),  the program error
        flag is set.  
      - Added safety header as program was already into the fourth record.
     
   c. Version 1.1 updates (09/21/88, Bruce Morgen):
      - Implements Type 3 format.
      - Restores F80 support  (since a  Type 3  version can be used  with F80)
      - Tightened code  (since there is no  need to  use  memory  storage when
        there are unused CPU registers)
      - Restored support  for  BASCOM 5.30  and  CB80 2.0  (addresses  as  per
        FNDERR13.MAC).
