Table of Contents
Advertisement
5.
Main program from 4200 to
4FFF
begins to execute and will
continue to do so
until
a RETURN (RTS) is executed, or a
I
System
Reset
I
or
I
B'"eak
I
occurs.
tn the
case
of compound fifes
,
the
result is more complicated
,
depending on how the
now
appended
files
were
created.
The
next section illustrates
several
cases where files have been ap·
pended.
Structure of a Compound Binary File
Before
considering
the
next
example,
look
at the
structure 01 a
compound file.
A compound file
is constructed of
various
binary
files that have been appended together. You
can create
com-
pound files in
one of
two ways. One way
is to
use the COPY FILE
option with its
append
option
.
A compound file created with this
command is
not
compatible
with
the
Assembler Editor
loader,
although it can be
loaded using the BINARY LOAD
option of
DOS
.
If
compatibility
with the Assembler Editor
cartridge is
de-
sired
,
an
alternate
way to
create
a
compound
file
is
to use
the
BINARY
SAVE
option
.
(To
do this
,
you
must tell DOS the name
of
the file
you are
appending
to,
followed by the
fA
option-see
Example
5.)
The
two
types
of files
are
illustrated in
Appendix I.
The
only
real difference is that the FFFF
(Hex) identification code
is included
with every
segment
when
a compound
file
is created
using COPY
FILE.
When BINARY SAVE
is
used, the additional identification
codes
for each segment
(after
the first one) are
not
included in the final
file. This is the only form of
compound file
that is compatible with
the LOAD
command of
the
Assembler
Editor
cartridge
.
The BI-
NARY LOAD
option
of DOS, however,
is
compatible
with
both
types
of
compound
files.
Now
consider
what happens when a compound file like this
is
loaded-supposing various INIT and RUN addresses were
spec·
ified for each
of
these files before they were appended.
(It
will
help
you
to think of the
INIT
and
RUN
addresses as being part
of
the data
in
each segment, which they essentially are.)
50
Advertisement
Table of Contents
