AVAILABILITY & HELP: Refer to your version/serial number when requesting help.

CHANGES TO EDTASM (Tandy Version)

1) Tape is no longer supported; code has been removed.
2) Buffer size increased to over 42K bytes.
3) Directory obtainable from both Editor and ZBUG; V command.
4) Multiple FCB and FDB data per line.
5) FCS supported.
6) SET command now works properly.
7) Screen colors remain as set from Basic before starting EDTASM.
8) Symbol table printed in five names per line on Coco3.
9) On assembly with /NL option, actual errors are printed.
10) Warning error on long branch where short is possible.
11) ZBUG now defaults to numeric instead of symbolic mode.
12) RGB DOS users now have support for drive numbers higher than 3.
13) Hitachi 6309 opcodes are now supported for both assembly and
disassembly including latest discoveries.
14) HD6309 detection is included and if present incorporates a ZBUG
error trap for illegal opcodes and enables monitoring and changing
the E,F,V registers from ZBUG.
15) Coco 3 users can now safely exit to Basic and use their RESET
button from EDTASM.
16) Keyboard now has auto repeat keys when keys are held down.
17) Lower case is now supported for commands, opcodes, options,
and symbols. Take care when loading or saving files or using
symbols, ex. NAME does not equal name,  \.A not equal \.a, etc.
 18) Local names are now supported. Format is A@-Z@ and a@-z@ for 52 local
symbols. New sets of locals are started after each blank line in the
source code. Local symbols do not appear in or clutter symbol table.
19) Local symbols can only be accessed from ZBUG in expanded form: ex.
A@00023  not A@.
20) Now reads source code files that don't have line numbers. Writes
normal source files with line numbers ( W filename ) or without line
numbers ( W# filename ).
21) Macro parameters now function correctly from INCLUDEd files.
22) In the Editor, a new command U scrolls backwards through the source code.

    There is a PATCHER program on the product disk which will automatically convert your program for use. Selection of Coco 1&2 vrs. Coco3 version is automatic. Coco 1&2 versions do require 64K RAM, the Coco 3 version will work with 128K of RAM.

V - obtains a directory from either Editor or ZBUG modes.
FCS - is used exactly like FCC but automatically add $80 to the last
character in the string.
FCB, FDB - for multiple entries per line entries should be seperated
by a comma. Make sure that the comment field for that line DOES
NOT CONTAIN ANY COMMAS or an error will result.
6309 OPCODES - since there is no endorsed memnonic convention for
these code, the syntax of the Hirotsugo Kakugawa paper "A Memo
on the Secret Features of the 6309" has been followed with one
exception.
TFM (transfer block) have the following format:

H.K format                EDTASM formmat

TFR r1+,r2+              TFRP r1,r2  ie. plus
TFR r1-,r2-                TFRM r1,r2  ie. minus
TFR r1+,r2                 TFRS r1,r2  ie. send
TFR r1, r2+                TFRR r1,r2  ie. receive

    The product disk contains several text files describing the 6309 and the new opcodes. These can be accessed with any word processing program or may be printed by a simple READER program also included on the disk.

    The version of DOS which is used with EDTASM6309 is patched specifically for the new program. Do not use it as a general purpose DOS as explained in the EDTASM manual, instead use the old version.
    Do not attempt to test any HSCREEN functions from ZBUG as changes made to the system MMU will cause program failure. For the same reason do not change bytes in the region of $400-$600. Stand alone programs may do whatever they like.
    If you are testing a routine from ZBUG which accesses the ROMs you must conform to the following practices. Make sure that your stack register points below $8000 and execute your routine as shown below:
 

Coco3 users            Coco 1&2 users

PSHS A,CC              STA $FFDE
ORCC #$50
CLR $FF91
go do the routine      go do the routine
LDA #1                 STA $FFDF
STA $FF91
PULS A,CC

    This is required because the extended buffer may cause your code to extend over and corrupt the RAM image of the ROMS.

    Simply place a copy of the product disk in your main drive and run PATCHER. PATCHER is self prompting and very simple to follow. After PATCHER finishes running, you will then be able to run DOS from that disk and use EDTASM6309.
    Remember you MUST own the Tandy version of Disk EDTASM and have a copy of the disk available.

    Please "three hole punch" and insert these sheets into your EDTASM binder for future reference. Also be sure to punch and include the sheets from the disk support TXT files in your binder. These can be printed using the READER program or any wordprocessor program.
    Set your WP program for an 80 width, 66 row page with NO margins.

    Every effort has been made to create an error free program but errors can happen. If you have problems, please contact the author for assistance. Be sure to include your version and serial number and a valid email address with all correspondence.
 

    You may now boot EDTASM6309 from any hard drive excluding 255. To use this option, you must first run PATCHER, then copy DOS.BAS, DOS.BIN, and EDTASM to the selected drive number. Run RGBCNFIG (RGB-Config) to patch DOS.BIN for a boot from the selected drive.

    There is an unavoidable problem with hard drive use. There is only room for 4 FAT buffers. To access multiple drives, DOS now uses modulo3 math. However, there is no way to check for a drive in use under this system without a major rewrite of DOS.BIN. If this situation occurs during assembly through the use of INCLUDE, you can and will damage the directory track. It is left to the user to avoid "overlapping" drive numbers.

    The use of "overlapping" is explained below. This situation is easily avoided by limiting the range of any one assembly to 4, ex. 3,4,5,6  37,38,39,40 etc. If you must use a wider range of drive numbers, YOU MUST PRECALCULATE TO AVOID OVERLAP.
 

0  1  2  3     FAT BUFFER NUMBER

0  1  2  3     ACTUAL DRIVE IN USE
4  5  6  7
8  9 10 11
12 13 14 15
etc.

FAT BUFFER FORMULA: FAT = 4 * ((drive number / 4) - INT(drive number / 4))

!!!DO NOT USE OVERLAPPING DRIVE NUMBERS DURING ASSEMBLY!!!

    There is also a bug in DOS.BIN for which a correction has not been found. Files with 256 bytes in the last sector can not be written or loaded correctly.
    If you get strange errors related to bad line number or line too long, add or subtract a one byte character from the file; the error will probably vanish.
 

    Coco3 users should add a line to DOS.BAS   0 WIDTH32. If you don't do this and start DOS.BAS from a high res. text screen, you won't be able to read any of the DOS.BAS instructions.

    You can make DOS.BAS autostart EDTASM (that's what EDTASM6309 is called on the disk) by adding the following line:
1 REMEDTASM      IS NOW LOADING
    Be sure to include at least 3 spaces between EDTASM and any following message but DO NOT put any spaces between REM and EDTASM.  The filename plus spaces must total to at least 8 characters.