Advertisement
EXBIN COMMAND
14. 1 -- Use
null
records
from
<name
1>.
Null
records
consist OT a
--'.
carriage return only.
The content of the
51
records will
be
converted to its binary equivalent and written into <name
2>.
Since
the
EXbug-loadable
riles can contain
51
records
that would be loaded into non-adjacent blocks of
memor~
based
on
their address fields,
the resulting memory-image file
may
be larg@r
(occup~
mere diskette space) than <name
1>.
This
r~sults
from
the fact that <name 2> is a memory-image file.
All parts or memory which are not directly referenced by
the
51
records,
but which are included between the lowest and the
highest address contained in all
Sl
records,
will be
a
paT't
of
the
memory-image
in
the
file
<name2> (initialized to
binar1.j zeroes).
The EXbug-loadable
~ile~
<name 1>,
is unaffected
by
the
entire
EXBIN
conversion process.
The output
rilEib
<name
2/1
can then be loaded into
memor1.j
directly
~rom
diskette
using
the
LOAD
command (see Chapter
18).
14.2
Execution Address Specification
A
starting
execution address for the
memor~-image
file
can be specified by entering a valid
hexadecimal
number
in
the
<options~
rield.
The
number
must
be
in
the range
$OOOO-FFFF (entered in the
<options~
rield without the dollar
sign>.
In
addition, the
e~ecution
address must
fal~
l.Dithin
the range of addresses spanned
bq
the
file.
That
is,
the
starting
execution
address
cannot
be less than the lowest
addr~ss
found in an
Sl
record, and it cannot be greater
than
the highest address.
If an execution address is specified
in
the <options> field,
it will override any value contained
in
the S9
recor~
of <name
1~.
14.3
Error Messages
The
following
error
messages
can be displayed by the
EXBIN command.
The
standard
error
messages
that
can
be
displayed
b~
all commands are not listed here.
CHECKSUM ERROR
On~
of
the Srecords From <name
1~
contained an
invalid checksum.
Page
14-02
Advertisement
