Advertisement
SYSTEM DESCRIPTION
24.2 -- File
St~uctu~e
starting load
add~ess,
number
of
b~tes
in
execution
add~ess.
the number of
sectors
the
last
sector,
and
to
load,
the
the
s
ta
r
tin
9
The memory-image file load information is
described
in
the
following paragraphs.
Both the content and the location
of
each field are described.
The offsets used
to
refer
to
~ne
various bytes are relative to zero
~zero
being the first
byte of the
RIB
sector>.
All
offsets
ar~
given in decimal.
1.
Byte
117,
the numbeT' of bytes
to
load
fT'om
the last sectoT'I must be non-zero, a multiple
of
8, and less than
or equal to
128 (S80).
2.
B~tes
118-119}
the number of sectors to
load,
must
contain a number that is non-zero;
less
than the total number of sectors allocated to
the
r
i 1
e,
and
1
es
5
than
or
equal to
512
($200) .
3.
Bytes
120-1211
the starting load address, are
not
checked.
For
programs
loading
in an
EXDRcisel'
I
system}
in the User Memory Map of
an
EXORcier
II
system with the single memory
map configuredl or in
the
Executive
Memory
Map
of
an EXORciser
II
system with the dual
memory map configured,
this
value
must
be
greater
than hexadecimal location
$lF
if
the
program is to be loaded via the
MOOS
loader.
EXORciser
II
systems can have pT'ograms loaded
into the User Memory Map of the
dual
memory
map configuration starting at location zero.
4.
The
ending
load
addl'ess is calculated from
bytes
117-121
in the following manner:
5.
EL
=
(NSL - 1)
*
128
+
NELS
+
SL - 1
where EL is the ending load address,
NSL
is
the
number
of
sectors
to
load
(bqtes
118-119), NBLS
is the number of bytes in
the
1
a-s
t
sec tOT'
(
b Y
t e l l
7 ) ,
and
SL
i
s
the
starting load address (bytes
120-121>'
The
ending load address must be less than
65536.
Bytes
122-123,
the
starting
execution
address,
must
lie
within
the
range
of
addresses
spanned
by
the rile (greater than
or eQ.ual to the starting
load
ad dress,
and
less
than
aT'
equal
to
the
ending
load
address).
6.
By tes
124-127
are not u sed and must be zero.
Page
24·-08
Advertisement
