








                                   OverVue

OverVue  is  a  machine language monitor for the TRS-80  Model  4/4P/4D  using 
TRSDOS 6.2 or newer operating system.   TRSDOS 6.1.0 is no longer supported by 
either Radio Shack nor the author of OverVue.

This program is distributed by the Freeware concept.   In other words, you may 
try  before you buy.   Because of the method of supporting Freeware,  I  would 
encourage  you to make copies of this program and freely distribute it in  any 
way, shape or form to your friends, local bulletin boards, or whatever. 

If  you have any questions regarding the operation of OverVue which are either 
unclear to you, or not fully explained in this manual, please write the author 
at the address shown in the OverVue program or on the last page of this manual 
with  your  question(s).   Enclose a self-addressed envelope  (no  stamps  are 
required), for a speedy reply.

For  faster replies,  the author maintains a Fast80 BBS system which  operates 
from 9:00 PM to 9:00 AM,  seven days a week.   The BBS number is 604-594-7398.  
Leaving  a  message at that number will result in a reply being made  in  less 
that 24 hours.



Your support is fully appreciated.


Mel Patrick, Author   











OverVue Copyright 1986 by Mel Patrick











                                1








                                 Conventions

Throughout  this  entire manual,  all numbers shown will be in BASE  16,  i.e. 
HEXIDECIMAL.   This  is  obviously the most popular base for  programmers  and 
should  be learned by anyone who wishes to effectively debug programs  with  a 
machine language monitor such as OverVue.

Commands  in OverVue are invoked by using the two letters which reside  within 
the "<>" signs which appear on the main menu.  These two letters correspond to 
the command text description immediately following them.  These letters may be 
in either upper case or lower case,  or a combination of either.  OverVue will 
interpret the commands correctly.

In  many commands in OverVue,   particularily with addresses,   a comma "," is 
used as a separator or delimiter.  In addition, most commands allow a space(s) 
after the initial 2 letter command.

If  you are using an address or number which has leading zero's,  they may  be 
omitted.   i.e.  0A00  would  be exactly the same to  OverVue  as  A00.   This 
convention is used completely in OverVue.

Whenever any [ ] signs appear within the syntax line, it indicates an optional 
parameter which may be entered.   This could be as simple as a drive specifier 
in  a  filename,  or have a more complex usage depending on the command  being 
processed.

Any  variations  from  the  above syntax will be  covered  in  the  respective 
sections throughout this manual.

When  you are at the main menu in OverVue,  the address at which  the  program 
(OverVue)  resides at will be shown at the top left side of the video display. 
i.e. [C000]. 

I suggest you read this manual very carefully since many OverVue commands  are 
interactive with each other.






















                                2








DV - Disassemble to Video

Syntax - DV nnnn,[####]      <ENTER>

Where  the "nnnn" is the starting address for disassembly,  and the [####]  is 
the address (optional) where disassembly is to stop. 

<SPACE BAR>     - scroll ahead one page on the screen
<DOWN ARROW>    - step ahead 1 instruction only
<LEFT ARROW>    - step back 1 byte from start address then display
<RIGHT ARROW>   - step ahead 1 byte from start address then display
<BREAK> - abort the disassembly and return to the main menu

Display Format

0000    F3      DI              ;s
0001    3E 01   LD     A,01H    ;>.
0003    D3 9C   OUT  (9CH),A    ;S.
0005    3E 0F   LD     A,0FH    ;..
0007    EF      RST   28H       ;..     @VDCTL

The first column is the address in memory, the second column is the data which 
is found there, and may consist of from 1 to 4 bytes.  The third column is the 
disassembled  code  for  that  address  and  the  last  column  is  the  ASCII 
representation of those bytes.   The last column,  @VDCTL,  is shown only on a 
RST 28H, with the command code value found in the A register.

The ASCII section is provided so that DATA, or text areas within a program are 
easily located.


Disassembly to Printer

Syntax - DP nnnn,[####]         <ENTER>

Where  'nnnn' is the address to start disassembly at,  and the [####] is where 
disassembly is to stop.  

OverVue will allow single pages, a variable left margin, and page length to be 
set before using this command option.   Refer to the <FL> Find Program  Labels
for further information on how to change these.

In  its default state,  OverVue will use 65 lines per page with a left  margin 
indent  of 5.   It also assumes that you are using continous sheet paper.   If 
you require a different setup, refer to the <FL> section for details.

<BREAK> - will abort printing after the current op code is printed and  return 
to the main menu.

OverVue uses a CHR$(12) as a form feed to advance to the top of the next page.  
Fortunately the majority of printers will respond to this command correctly.






                                3








DM - Display Memory

Syntax - DM nnnn      <ENTER>

Where 'nnnn' is the address to start the display at.

This  command option will display a full 256 byte block of RAM at a time.   It 
may be scrolled in either direction one block at a time,  or 1 byte at a time.
This block of RAM may be referred to later in this manual as a page.



3000  40 41 42 43 44 45 46 47 48 49 4A 4B 4C 4D 4E 4F :@ABCDEFGHIJKLMNO
3010  61 62 63 64 65 66 67 68 69 6A 6B 6C 6D 6E 6F 70 :abcdefghijklmnop
        ...................etc. to 30FF


Scrolling is controlled by one of the following keys.

<UP ARROW>      - will display the previous 256 byte block
<DOWN ARROW>    - will display the next 256 byte block
<LEFT ARROW>    - will step back 1 byte, then re-display 256 byte block
<RIGHT ARROW>   - will step ahead 1 byte, then re-display 256 byte block
<SPACE BAR>     - will step ahead 16 bytes, then re-display 256 byte block
<BREAK>         - will abort the mode and return to the main menu
<M>             - will enter the MODIFY mode
<ENTER>         - will terminate the Modify mode,  and return to the  display 
                  mode

HEX Modify

When the hex mode is active,  the left most cursor will indicate the  position 
of the byte which may be changed.   Any valid HEX character (0-9,  A-F) may be 
entered  directly from the keyboard,  and will change the byte at the location 
shown.

Pressing  the <ENTER> key will exit the modify mode and return to the  display 
mode.

ASCII Modify

When the ASCII mode is active the right most cursor will indicate the position 
of  the byte which maybe changed.   Any valid ASCII character may  be  entered 
from  the  keyboard and will replace the character highlighted by the  cursor.
At the same time the HEX representation will change to show the new value.

Pressing  the <ENTER> key will exit the modify mode and return to the  display 
mode.


Selecting the  Mode

To  toggle from HEX to ASCII modify mode,  and vice-versa,  press the F1  key.  
The active mode will always be shown at the top left corner of the display.



                                4








CB - Clearing Breakpoints

Syntax - CB[#]

Where  CB stands for CLEAR BREAKPOINT,  and the optional # sign would  be  the 
selected  breakpoint to clear.   If no # is specified  ALL breakpoints will be 
cleared.


DB - Display Breakpoints

Syntax - DB

Will display all 9 breakpoints in the following format :

1 - 0000        2 - 0000    3 - 0000
4 - 0000        5 - 0000    6 - 0000
7 - 0000        8 - 0000    9 - 0000

The first number represents the breakpoint, while the 4 digit number following 
it is the address where the breakpoint is set.   Any which are set to  address 
0, indicate that they are currently not in use. 


SB - Setting Breakpoints

Syntax - SB#,nnnn

Where # is the number of the breakpoint to be set (0-9) and the 'nnnn', is the 
address to set the breakpoint at. 


Breakpoints must be set at least 3 bytes apart.  If not, they will overlap and 
not work.

JP - Jump to an Address

Syntax - JP 3000
Syntax - JP *

Where  the first example is an address to start execution at.   Registers  may 
contain any random data when entering a program to test in this way.

The  second example is where you have specified the register contents by using 
the SR command (see the next section).   The address to execute will be  taken 
from the PC (program counter) register.  All registers will be loaded, and the 
program executed.  


CR - Clear Registers

Syntax - CR

This will clear any previous values set for any/all registers.  If you want to 
clear only 1 register, use the SR and set the register to 0000.


                                5








DR - Display Registers

Syntax - DR

This will display the following map :

AF - 0000   BC - 0000     DE - 0000
HL - 0000   IX - 0000     IY - 0000
SP - 0000   PC - 0000     Flags........................

Any value shown as 0000,  indicates that register has not been set.  The flags 
will  indicate  the status of the second part of the AF register  (F).   Flags 
available will be Z,NZ,C,NC,PE,PO,M,+.



SR - Set Registers

Syntax - SRrr,nnnn

Where 'rr' is the register to set and the 'nnnn' is the hex number to set them 
to.   Leading 0's may be omitted from the hex number for the register.   Valid 
registers  are  AF,BC,DE,HL,IX,IY,SP,PC.   If  you are going to  use  the  JP* 
command,  the  PC register MUST be set,  since this is where OverVue gets  the 
execution point from.


IM - Initialize  Memory

Syntax - IM ssss,eeee,[bb]

Where 'ssss' is the address to start at,  'eeee' is the ending address of  the 
block,  and 'bb' is the byte to use to set that block to.   Note that the 'bb' 
is optional and if not specified, the value 0 will be used.


FB - Find Byte

Syntax - FB ssss,eeee,nn

Where  'ssss' is the address to start the search at,  'eeee' is the address to 
end the search at,  and 'nn' is the byte to find.    The space between the  FB 
and the starting address is optional.

For example,  in TRSDOS 6.2 you could do this,  FB 0,1500,3E   <ENTER>.   This 
would  search from address 0 to address 1500 for the occurance of the byte 3E.  
Note  all  addresses and data bytes are in HEX.   Your display  should  be  as 
follows :

Match : 0001    : <N>ext / <M>enu
Match : 03BA    : <N>ext / <M>enu
etc.





                                6








FW - Find Word

Syntax - FW ssss,eeee,nnnn

Where  'ssss' is the address to start the search at,  'eeee' is the address to 
end the search at and 'nnnn' is the word in MSB,LSB order to search for.   The 
word  to  search for will be turned around into standard Z80  storage  format, 
i.e.  LSB first then MSB.  So that if you specified a word like 1234, it would 
have to appear in memory as 3412.   Therefore by changing the LSB/MSB you  can 
obtain a more versatile search.

When  a  match  is found,  it will be reported in the same method  as  the  FB 
command option does.


FS - Find String

Syntax - FS ssss,eeee,ASCII STRING

Where  'ssss' is the address to start the search at,  'eeee' is the address to 
end the search at, and the string can be any ASCII characters.  For example in 
TRSDOS 6.2, you could use the following example:

FS 0,1500,TRSDOS62


<N>ext / <M>enu - Search Options

Whenever  a match is found,  it is possible to return to the main menu in  the 
OverVue program.   If this is done,  by using DV, or DM without any arguements 
will take you directly to the address which the match was found at.   You  may 
then proceed with those commands to work on the memory locations.


FN - Find Next

Syntax - FN

When you have chosen the <M>enu option when a match is found, you may elect to 
disassemble the code from that point on.   However, if that is not the section 
of  code  you are searching for (there may be more than one reference  point), 
you  may continue the search from where the last match was found by using  the 
FN command.   This command will only work as long as at least 1 match has been 
found  and the ending address for the search has not be reached.   If  it  has 
this command will become invalid and will not work.












                                7








FB/FW Special Applications

It  may become necessary to search for a combination of words and/or bytes  in 
memory.  With OverVue this is possible.  Some of the formats for searching are 
as follows :

FW 0,1500,0005,001E     - would find a double word in memory (LSB/MSB order)
FW 0,1500,1BF2,28       - find a word and a byte (IBF2 in reverse order)
FB 0,1500,F2,1B         - find a word the way it will appear in memory
FB 0,1500,C3,1BFF       - Find a byte, then word in reverse order

Note  some  of the codes must be in reverse order because of the way they  are 
stored in memory (LSB,  MSB).   If you can not locate a byte(s) which you know 
appear within a program, try reversing the order.


VD - View Addresses of /CMD File

Syntax - VD filespec[.pw][:d]

Where  the  filespec may have the access password and  drive  included.   This 
command will proceed to VIEW the addresses at which the file loads at, as well 
as  any  ASCII header blocks.   Once the file has been  completely  read,  the 
addresses will be displayed for your reference.   This command is used  mainly 
to  ensure that the /CMD file which you are going to load into memory will not 
conflict with the addresses occupied by OverVue.


LD - Load a /CMD file from Disk

Syntax - LD [nnnn,] filespec[.pw][:d]

Where 'nnnn', is the optional address to use for an offset load, followed by a 
valid filename, optional password and drive identifier.

The addresses which the file loads at are contained within the disk file being 
read.  If the optional offset value is entered, OverVue will add this value to 
the  block  load  address and store it at the new  location,  instead  of  its 
original location.

Once  a file have finished loading,  all data retaining to that file  will  be 
displayed on the screen.

If  header comments are indicated,  refer to the section dealing with them for 
further details.












                                8








WD - Write /CMD file to Disk

Syntax - SD *,filespec[.pw][:d]
Syntax - SD ssss,eeee,xxxx,filespec[.pw][:d]

Where in the first example, the '*' indicates that the addresses or any offset 
loads which has been done,  will be again used to write the file back to disk.
The filename must still be used.

In the second example,  'ssss' is the start address for saving,  'eeee' is the 
end address,  and 'xxxx' is the execution address for the program.   Again the 
filename  must  be  entered  along  with  any  optional  passwords,  or  drive 
identifiers.


LF - Load a File from Disk

Syntax - LF filespec[.pw][:d]

This command will load ANY file from disk and start storing it in memory  from 
hex address 3000 on.   This file can be a CMD file, a SYS file or a TEXT file.
The  file can be modified in memory where it sits and then written back out to 
disk.

The  addresses  that  it loads from and to will be  display  when  loading  is 
completed.


SF - Save a File to Disk

Syntax - SF filespec[.pw][:d]

This  command  will save any file which has been loaded with the  LF  command.
Only  the filename is needed.  OverVue will keep track of the addresses  which 
were used when the disk file was loaded.


PA - Program Addresses Display

Syntax - PA

This command will re-display the addresses used by the most recent LF,  VD, or 
LD commands.  This serves as a quick reminder in case you forgot the addresses 
which  the program loads at.   It will also display any offset used in loading 
and whether the /CMD file contains a header block.


WD Special Option

If  a  file which has been loaded contains a header block,  when the  file  is 
saved back to disk by using the '*" identifier, it will write the header block 
back  as well.   If you don't want this to happen,  use the RC to  remove  any 
comments, before writing the file back to disk.




                                9








ASCII Header Blocks

It  is  possible to have a sort of comment block attached to the beginning  of 
any type of SYS or CMD type files.   This block serves many purposes,  but  is 
mainly  used for simple copyright comments.   Whenever a /CMD file type format 
is loading, any comment blocks will be displayed as a capitol letter C.  i.e.

Loading .CC................................................

Where the two C's indicate two comment blocks,  and each of the periods  after 
that indicate another 256 bytes have been read/and or loaded into memory.

If you want to see one of these header blocks, try the following :

VD SYS4/SYS.LSIDOS

You will be informed of the comment block,  and may use the VC command to look 
at the comments.


VC - View Header Comments

Syntax - VC

If  any  CMD format file was loaded which contains a comment block,  use  this 
command to view it.


EC - Enter Header Comments

Syntax - EC

If  you  want to change the comments (I suggest that you use a Backup copy  of 
the  program in case of problems),  use this command.   There is no prompt  to 
follow,  just type in the information as you want it stored.  A maximum of 250 
characters  are available for use.    If you need a linefeed,  use  the  <DOWN 
ARROW> to get to the next line.

Pressing the <ENTER> key will terminate the input mode, and return to the main 
menu. 

RC - Remove Header Comments

Syntax - RC

This  command  will  remove any header comments and shorten the  file  by  the 
length of header comments.  Since the smallest block the TRSDOS system uses is 
1.5K, this usually won't save any disk space, but will remove unwanted comment 
blocks.








                               10








MA - Math Operation

Syntax - MA nnnn,xxxx

Where  'nnnn' is the first number to use,  and 'xxxx' is the second number  to 
use.   In  OverVue,  A  will  equal 'nnnn' and B  will  equal  'xxxx'.   Three 
operations are performed, A+B, A-B, B-A.  


MV - Move Memory Block

Syntax - MV ssss,eeee,wwww

Where  'ssss'  is the start address of the block to move,  'eeee' is  the  end 
address of the block to move and 'wwww' is where you want the block moved to. 


DC - TRSDOS Library Command

Syntax - DC cmd

Where the 'cmd' is the library command you want to execute.   Commands such as 
CAT,  DIR, FREE etc are all library commands.  In the TRSDOS manual there is a 
more  complete list of library commands,  or you may type in LIB using the  DC 
command to find them.

FL - Find Labels

Syntax - FL

There  are four labels and addresses which will display after this command  is 
issued.  They are as follows:

SHEET   : nnnn  - 00    PAGE   : nnnn - 42    LRL   : nnnn - 00
INDENT  : nnnn  - 05    Video  : nnnn - 10   CMDTAB : nnnn
Lead 0  : nnnn  - 00    RSTCMD : nnnn - 01

Each  of the 'nnnn' addresses refer to a location within OverVue which can  be 
changed and the 2 digit values after the address are the present values.  


Sheet

This is a 1 byte value which is used during the DP (disassembly to printer) to 
indicate  whether  single  sheet  or fanfold paper is  being  used.   Use  the 
following for a guide :

                        0 = FanFold / 1 = Single Sheet

Page

This  1 byte hexidecimal value is the maximum number of lines per page  +1  to 
use when in the disassembly to printer command.   OverVue will use 1 less than 
this value when formatting to the printer. 



                               11









LRL

This 1 byte code affects the LF and SF (load file/save file) commands.  It may 
happen  that  you  have a file which you want to modify,  but  are  unable  to 
because  of the Logical Record Length not being 256.   In this case,  set this 
byte to the LRL as shown in the DIRectory for that file.   You may then  load, 
modify and save this file without any problems.   Remember to reset it back to 
0 (LRL=256) when you are done.


Indent

This  1 byte value is the indent used during the formatting of the disassembly 
to the line printer.   The idea of it being there is so that you can obtain  a 
listing, and then punch holes in it to save in a binder or duotang.


Video

This  one  byte  value  indicates which line on the display will  be  used  to 
display the contents of the registers and other information during the  single 
stepping  option.   The  display will always start from the left side  of  the 
video,  but  may  be positioned higher or lower depending on the value of  the 
digit.

The number shown is in HEX,  i.e. if a 10 where displayed, that would indicate 
line 16.   If you specifiy a line greater than this,  the display will  scroll 
and  the  top  portion of the screen will be destroyed (due to  the  scrolling 
effect).   However,  you  may specify any value less 10H to move  the  display 
higher.


CMDTAB

This address is the start of the RST command lookup table in OverVue.   If you 
want  to change a command,  use the DM command to start looking through memory 
at this address.   Alternatively,  use the FS (find string) command to  locate 
the ASCII portion of the RST command word.

Each  entry in the table is 7 bytes in length.   All commands are in numerical 
order according to the TRSDOS Technical Information Manual.   The seventh byte 
of  each entry is a 03H terminator byte.   This must be always be the  seventh 
byte.  A typical entry would be :

49  50 4C 20 20 20 03,  which is the first entry in the table and  stands  for 
IPL.

You  may add or change this list to suit your requirements.   Note that the  @ 
symbol which is printed along with the RST command,  is not in this table.  It 
resides within a different area of code in OverVue.






                               12








Lead 0

This  single  byte  value at the address shown determines whether or  not  any 
leading  0's are surpressed or printed during a disassembly in  OverVue.   For 
example,  if  an  address such as AFDE was used,  there may or may  not  be  a 
leading 0 used ( 0AFDE).

A  0  at the lable address will surpress any leading 0's.   A value of 1  will 
display all leading zero's.


RSTCMD

This  single  byte value determines whether OverVue will display  the  RSTCMDs 
during  a disassembly.   This may be needed if you were working on  a  program 
which used RST 28H but was a Model IV program.

A  zero value at this address will supress the RSTCMD from being displayed.  A 
non-zero value will display the RSTCMD as needed.


XS - Execute Single Step

Syntax - XS nnnn

Where 'nnnn' is the address to start single stepping at,  i.e.  this sets  the 
program counter.   If 'nnnn' is not specified the program counter address will 
be taken from the register which can be set using the SR command.


Register Usage

The  single  step  command uses the registers which can be set  using  the  SR 
command.   If  if PC register is not set,  one must be specified using the  XS 
nnnn command.   If a PC register has been set, just use the XS command with no 
address.  The PC register may contain any valid address except 0000.

The SP or stack pointer,  may be set, or if it is not set using the SR command 
(it is still 0000),  the normal TRSDOS stack pointer will be used.

All  other  registers,  AF/BC/DE/HL will be loaded before starting the  single 
step routine.















                               13








Single Step Display Format

When single stepping,  the information will appear at the bottom left side  of 
the display.   You may re-position to a higher position (refer to FL command), 
or  leave it where it is.   Regardless,  it will always display from the  left 
hand side of the display.  A typical display would look like this :

AF : 0000       BC : 0000       DE : 0000          HL : 0000
IX : 0000       IY : 0000       SP : 037E          PC : C000
Flags : +,NZ,PE,NC

(BC) F3,.       (DE) F3,.       (HL) F3,.       (IX)F3,.      (IY) F3,.

C000    18  14          JR      C016H           ;..

The  information  in  the  middle section ( the  (BC)  etc),  is  a  HEX,ASCII 
representation of the data byte found from the address where the registers are 
pointing.   This  feature is most helpful where a line text is being sent to a 
device and you can see the characters are they are pointed to and loaded  into 
another register.   In this case usually HL points to the line of information, 
and  the A register is the one which reads it from the HL  register,  i.e.  LD
A,(HL).  Beside the (HL) register would be the hex value of the byte, followed 
by a comma, and then, if possible, the ASCII itself.

There are four keys which control single stepping.  These are as follows :

<DOWN ARROW> - will single step to the next instruction and execute  it.   The 
registers will be immediately shown thereafter.
<BREAK> - will abort the single step mode and return to the main menu.
<C> - will allow single stepping of a CALL instruction.
<R> - will allow single stepping of a RST instruction.


Single Stepping with RST and CALL

It  is possible to be single stepping through a program and find a CALL or RST 
being displayed.  At this time OverVue offers you two options.  You may branch 
to  the CALL or RST and continue single stepping through the routine,  or  you 
may  simply elect to bypass the CALL or RST and resume single  stepping  after 
it.

The  R  or  the  C keys will allow this.   You may select one  of  these  keys 
accordingly  whenever a CALL or RST is to be single stepped.   If you use  the 
<DOWN  ARROW>  single  stepping will resume AFTER the call  or  RST  has  been 
executed.

These  command  options allow quick processing of routines which are known  to 
work, such as many of the TRSDOS command functions.


Display of SVC's

During single stepping,  where ever possible,  and SVC codes will be displayed 
on the screen for the disassembly of the instruction.



                               14









Single Step Special Notes

When  single stepping a section of code it is important to keep in  mind  that 
all  of the code is actually executed so that you can see what is happening to 
the  registers.   In the same manner it is entirely possible to unbalance  the 
stack pointer, or change a part of memory accidently thereby rendering OverVue 
helpless to recover.

If you are executing code and it has a section to save all the registers, make 
sure  you  exit after the section which restores all the  registers.   If  you 
don't  the stack will not quite be where it is supposed to be and the  program 
could fail to work.












































                               15








OverVue Concept

OverVue is supplied as a Freeware,  or ShareWare product.   This means you get 
to  try before you buy which in itself is fairly unusual  today.   While  this 
program  could  have  been  commerically marketed for  more  than  the  $15.00 
requested  here,  that was not the authors intention.   I am trying to provide 
good  software  at  a price where even the most  limited  budget  can  readily 
justify the small outlay.

If you like the OverVue program and plan to make use of it,  I would encourage 
you to take a few minutes and fill out the form below.   When I receive it,  I 
will  mail  you  a printed manual along with any updates,  or patches  to  the 
program.

If,  with  your  application  a diskette is included,  you  may  also  request  
OverVue's which reside at different memory locations.   Just check beside  the 
locations  you  require  and they will be included on the disk  you  sent  and 
returned  with  the  documentation.   In addition,  a special  memory  address 
version may be requested.  The limits here are above 2800H and below D000H.

If you would like the source code to the OverVue program,   please send $30.00 
to  the address shown below.   You will receive the commented source code  and 
documentation.    There is no need to send any diskettes,  but please  specify 
the  format  for the source code you require.  Standard EDTASM code,  or  ZEUS 
format can be supplied.   The documentation will be supplied in standard ASCII 
format on the disk(s).
______________________________________________________________________________

                           OverVue Application Form


      Name : ______________________________________________________________
    Address: _____________________________________________________________
       City: ______________________________________________________________
 State/Prov: ______________________________________________________________
Postal Code: ______________________________________________________________


                        OverVue Memory Version Request

OverVue 1 - 3000H__          OverVue 2 - 5000H__        OverVue 3 - 8000H__
OverVue 4 - 9000H__          OverVue 5 - B000H__        OverVue 6 - C000H__
OverVue 7 - D000H__          OverVue 8 - ____H, your choice

                Source Code Formats : EDTASM__    /   ZEUS___

   Comments : __________________________________________________________
Suggestions : __________________________________________________


Send to..........................Mel Patrick
                                13699 70A Ave.
                                 Surrey, B.C.
                               Canada  V3W 2J8



                               16





FYI: this file is c/o Guy Omer of 8/N/1 #1 at 904/377-1200 in Gainesville, FL.


   