Advertisement
ERROR MESSAGES
28.2 --
Standa~d
Command
Erro~s
**
13 INVALID LOAD ADDRESS
This message indicates that an attempt
was
made
to load a
prog~am
into memory which,
depending on
the method of loading:
1) loads outside
of
the
range
of
contiguous
memory
established
at
initialization;
2)
loads
over
the
T'~sident
operating
system;
3)
loads
below
hexadecimal
location
$20i
O'r
4)
loads be'Jond location
$FFFF.
The
latter
case implies that the ¥ile's
RIB
may
be damaged.
If
this is the suspected cause,
the
REP A I R
comma n d
( Chap t er
22)
s h
0 U
1 d be
use
d
to
correct the errol'.
P~ogT'ams
~hich
load into
the
highest
memor'J address ($FFFF) which do not have
a
starting load address that
is
a
multiple
o~
eighti can also cause this erT'or.
**
14 INVAL1D FILE TYPE
The
rile
name
entered on the command line as a
parameter has the wrong file ¥ormat (the
numeric
portion
o~
a
displa'Jed
directory
entry's
attribute field) for the intended operation.
No
file
name
is displayed since only one
paramete~
is required by the command.
This error can also
occur
if
a
binary
recoro
transrer is being requested to a device that does
not support binary
transfersj
ir
a
nan-record
ro~mat
(e. g.
1
memory-imag e r01'mat) is
5p
ec i
r
i ed
when opening
a
non-diskette
device;
or
if
a
non-ASCII
record
f01'mat is specified when using
the non-rile rormat mode.
**
15 <name/ HAS INVALID FILE TYPE
The displayed
fil~
name has the w1'ong file f01'mat
(the
nume1'ic
portion
o~
a displayed directory
entry's
attribute
¥ield)
for
the
intended
operation.
The <name> is displayed to show which
file name of
the
mul~iple
names
specified
as
parameters
caused
the
e~~or_
The
MERGE
command (Chapter 19) can display this
message if a memory-image
file
has
an
invalid
RIB.
The
REPAIR
command (Chapte1' 22) should be
used to correct the e1'ror.
**
16 CONFLICTING FILE TYPES
A command was expecting files of the same format.
The
riles
speciried have different rile formats
and/or attributes.
I
/
Advertisement
