mirror of
https://github.com/markpmlim/EdAsm.git
synced 2024-11-22 14:33:02 +00:00
Disassembled source code of the ProDOS Assembler Tools package
This commit is contained in:
commit
f6a1b75e84
BIN
EDASM_SRC.2mg
Executable file
BIN
EDASM_SRC.2mg
Executable file
Binary file not shown.
31
README.MD
Normal file
31
README.MD
Normal file
@ -0,0 +1,31 @@
|
||||
The disassembled source code of the programs of the PRODOS ASSEMBLER TOOLS RELEASE 1.1 are
|
||||
distributed in the form of an 800K Universal disk image (.2mg).
|
||||
|
||||
This disassembled source codes are arranged in 5 folders.
|
||||
|
||||
If you wish to assemble any of the 5 programs,
|
||||
1) you should have a copy of the PRODOS Assembler Tools,
|
||||
2) you know how to run EDASM.SYSTEM, and
|
||||
3) you should be have some knowledge using the command line of the EDASM editor.
|
||||
|
||||
To assemble a particular program it’s advisable to change the working directory.
|
||||
|
||||
There is a README.TXT at the root directory of the disk image containing information on how to assemble the source code(s) in a particular folder.
|
||||
|
||||
To understand the source codes, the following are required:
|
||||
|
||||
1) a good knowledge of the instructions of the 6502/65C02 CPU.
|
||||
2) an idea on how to call the Apple ][ Monitor subroutines.
|
||||
3) a working knowledge of the ProDOS 8 filing protocol including its on-disk data structures.
|
||||
4) know what EDASM’s assembly directives do.
|
||||
5) at least some knowledge of the pseudo 16-bit microprocessor SWEET16.
|
||||
|
||||
The following are useful references:
|
||||
|
||||
1) Beneath Apple ProDOS by Quality Software
|
||||
2) Programming the 65816 etc by Eyes and Lichty
|
||||
3) Apple II monitor listings
|
||||
4) EDASM manual
|
||||
5) SWEET16 by Steve Wozniak
|
||||
|
||||
When you peruse through the source codes you will notice that many data areas are filled with what seems to be garbage. These are actually random data created when the assembler encounters a particular form of the DS directive in original source. I had left them as-is so that a byte-to-byte comparison can be made between the new binaries and the original binaries.
|
Loading…
Reference in New Issue
Block a user