Table of Contents
Advertisement
If your
LOAD
file overlays any part of the
DUPSYS
file
,
you must
have a
MEM
.SAV file on the diskette in Drive 1 if the
load
is to be
successful
.
If
you do have
MEM.SAV,
the
following
actions take
place after you execute
LOAD BINARY FILE
option
:
1.
You use
the LOAD BINARY FILE
selection
to
load your
file
.
2.
Your original
MEM.SAV
is loaded
from
disk into memory, over-
laying
and invalidating
DUP.SYS.
3. Your file is loaded on
top
of the
original
MEM.SAV,
modifying
part or
all
of the
original MEM.SAV file
,
4. Your new MEM ,SAV file
in
RAM is saved in the MEM.SAV
area
on
the
diskette.
5.
OUPSYS is
reloaded from diskette into memory.
6.
You remain in
DOS
until you choose to:
RUN
CARTRIDGE
at which time your file is loaded into
memory from MEM .SAV and you
come
up
under
the
control of your
BASIC
or Assembly
Language
cartridge
;
RUN
AT ADDRESS
at which time your
file
is loaded into
memory from
MEM
.SAV and you
begin execution of whatever code is
at the address you specified; or
LOAD
BINARY
FILE
where you wish
to load
a load-and-go
file
,
In
this instance
,
if
the new file
also overlays a part of
DUPSYS
,
but
not the
original
file,
then
both
MEM
.SAV and your
new
file will
now
be
in memory when the load is
com-
plete. If
the
new
file
does
not
overlay
DUPSVS at all
,
then the load will
complete with only the new file
loaded into
RAM
,
Since the new file is
a
load-and-go
and loaded whether
DUP,SYS is overlaid or not
,
you will
come
up
under
the
control of
this file
until
a
RETURN
(RTS) is executed.
58
~
~
~
~
~
~
~
-
~
~
~
-
-
~
~
~
-
~
~
~
~
Advertisement
Table of Contents
