Advertisement
SYSTEM DESCRIPTION
24.9 -- MDOS Equate File
are followed
by
another series of self-sequencing definitions
ror the various
lID
function error statuses.
Following
the
error
statuses,
the locations or all
of
the MOOS internal variables are defined.
These
include
the
locations
of
the variables needed
by
the user for accessing
the
command
buffer,
the
memory
sizes
established
at
initialization, and the user-defined interrupt vectors.
After
the variables is a series of equates that defines
the various bit positions of the IOCB,
the offsets
into
the
controller descriptor block (CDB),
bit definitions within the
CDB,
and the offsets
to
the
entry
points
of
the
device
dr
i verso
Lastly,
the diskette controller variables, entry pointsl
and
~rror
statuses are equated to symbols.
These equates are
followed
by
a partial list of the locations
in EXbug
required
b
y
MOOS.
i h
e
EX bug eli u ate 1 i s t i s not c om p
let
e .
Th us,
us eT' s
requiring
other
entry
points
into EXbug must provide them
~ithin
their
progra~s.
If programs are being written thpt use the resident
MDOS
fun c t ion s ,
i t · i s s u
9
g est e d t hat
the
MDOS
e
qua t e f
i1
e
b
e
included as
a
part of
the
assemb
1y
(requires
M6800
Macro
Assembler).
Symbols
within
the
MDOS equate file may have
their values changed
by
Motorola in
subsequent
versions
Or
MDOS;
however,
all
attempts will be made to ensure a minimal
numb e r
0
r
s
u
c h chan g e s .
Th ere
of
0
re,
the
MDOS
e qua t e
f
i
1
e
should
not
be
copied
from one version of
MDOS
to another.
Like the resident system and command files that comprise
the
operating
systeml
the
MDOS
equate file is associated with a
specific version and revision of the operating system.
A
listing of
the
MDOS
equate
file
is
contained
in
Appendix
1.
Page
24-27
Advertisement
