Thank you for your interest in EDTASM6309 V3.03.03 .
This is a major patch to Tandy's Disk EDTASM (editor/assembler) and offers
many improvements over the original version and earlier patch versions. The
program comes in two versions, one for the Coco 1 or 2 and the second for the
Coco 3. The only user noticable difference is that the Coco3 version uses
40/80 column screens and runs in the fast 2MHz mode. Use RGBCNFIG.BAS to
select whether the 40 or 80 column screen will be used.

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

EDTASM6309 $35
Robert Gault
832 N.Renaud
Grosse Pointe Woods, MI 48236
USA
(313)-881-0335
e-mail:	robert.gault@att.net

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= \.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) While in the Editor, the U key will backup one screen in your source file.
23) DOS.BAS can be used to program the F1 and F2 keys on a Coco3. See below.
24) Coco3 WIDTH80 now uses 28 lines of text.



Coco 1&2 versions do require 64K RAM, the Coco 3 version will work with 128K
of RAM. You can assemble 6309 code even if your Coco has a 6809 cpu.

NEW COMMANDS

V - obtains a directory from either Editor or ZBUG modes.
U - scrolls backwards through source code.
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 format
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

SUPPORT FOR 6309 OPCODES

   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.

GENERAL INSTRUCTIONS AND CAVEATS

   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.

INSTALLATION

   With Tandy out of business, your EDTASM is ready to use. Just select the
appropriate version from the zip directories and mount it in an emulator. With
a hardware Coco, you will need to either mount your disk on Drivewire to use
or for transfer to a real Coco disk.

   Please "three hole punch" and insert this doc 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.
   If you don't own Tandy's Disk EDTASM, you can download the manual from
http://www.colorcomputerarchive.com
under the Documents/Manuals/Programming directory
DiskEDTASM(Tandy).pdf

IF HELP IS NEEDED

   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.
robert.gault@att.net

*******RGBDOS USERS ONLY******

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

!!!!!WARNING!!!!!

   There is an unavoidable problem with hard drive use. There is only room for
4 FAT buffers. To access multiple drives, DOS now uses modulo 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.

USEFUL HINTS

   Coco3 users now have a line in DOS.BAS: 0 WIDTH32. If you didn't do this
and started DOS.BAS from a high res. text screen, you wouldn'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) with the line:
1 REMEDTASM      IS NOW LOADING
That also has been added to the DOS.BAS program.

Coco3 users can set the F keys to perform often repeated tasks. Check DOS.BAS
after installation for examples of Assembly and Write. You will need to use
the file name of your project and change lines 3 & 4.