Advertisement
LOAD
COMMAND
18. 1 -- Use
18.
1.
1 Command-i nterpreter-l oadab 1 e programs
Prog~ams
that
can
be
loaded
by
the
MOOS
command
interpreter
are usually loaded for testing
by
not specifying
anything in the <options> field.
The "G" option can be
used
to
load
and
execute
the program in one stepi
however,
Tor
such programs this is awkward.
They are usually
loaded
and
executed directly
by
the MDOS command interpreter
by entering
their file names as the first rile name
speci~ication
on
an
MDOS command line.
The command line
LOAD TESTPROG
would
attempt to load the file TESTPROG.LO from logical unit
zero above the resident operating system
(the
program
must
have
already
been
assembled atl
or link/loaded and assigned
memory locations at the proper addresses so
l~
loads
above
MDOS)'
After
the
file
was
loaded,
control would be given to
the debug monitor.
The following command lines
TESTPROG. LO
or
'LOAD TESTPROG;G
would load the program from
TESTPROG. LO
from
logical
unit
zero
and execute the program.
It should be noted that these
two command lines will accomplish the same
function.
Since
the
first
~orm
of the command line is shorter,
especially
if
the suffix were change to "eMil, the second form
is
seldomly
used.
Command-interpreter-loadable
follo~ing
requirements:
programs
must
meet
the
1.
The
program
must
load
above
the
resident
operating
system;
it
must
be origined to load
above hexadecimal location
$lFFF.
The
prog~am
can
access
the
direct
addreSSing
area
below
hexadecimal address $100 (BSCT) during executioni
howeverl that area of the memory cannot be loaded
into.
Thus,
variables
in
BSCT
cannot
be
initialized
during
loading.
In addition,
if
a
program is going to use diskette
lID,
none of the
locations
below
address
$20
can be used
by
the
program for its own variables.
The· program
must
load
within
the
range
of
contiguous
memory
that
was
establiShed during
MDOS initialization.
Such
programs
require
an
Page
18-03
Advertisement
