Download Print this page

Motorola EXORdisk II User Manual page 192

Advertisement

MERGE COMMAND
19. 1 -
Use
in that case.
19.2
Messages
The following messages can be
displayed
by
the
MERGE
command.
Not all messages are error messages, although error
messages are
included
in
the
list.
The
standard
error
messages that can be displayed
by
all
commands are
not
listed
here.
<name:>
EXISTS.
OVERWRITE?
The specified file name
already
exists
in
the
directory.
The
operator is prompted before the
f
i
l e i
$
overUlr
i
tten.
Any"
resp onse
LIIi
11
cause
the merge to take place.
Any
other response Ulill
cause control be to returned to
MDOS.
**
15 <name> HAS INVALID FILE TYPE
The file indicated
by
<name> is
not of
the proper
format
(i.
e.
I
ASCI I
record!
binary
record,
memory-imagel or user-defined)
J
or the RIB
of
the
file
is
damaged.
·A memory-image file's RIB
is
considered to be
dama~ed
if
the
number of
se~tors
to load is zero,
the number of bytes to load -From
the last sector
is
zero, or if
the
ending
load
address
is
larger than $FFFF.
If a damaged RIB
is suspected, the
REPAIR
command
(Chapter
22)
should be invoked to
co~~ect
tbe
er~or.
**
16 CONFLICTING FILE TYPES
The
riles
specified
by <name
i::>
have
diTfe~ent
file formats.
They must all be the same
format.
Even
if
the
format
(ASCI I
record, etc.)
is
the
same,
the contiguous allocation attribute and the
space
compression
att~ibute
must
also
agree
between all <name i::>.
This error can also
oc~ur
if
<dname> (not the same as <name
1>'
exists and
has a
diffe~ent
file
fo~mat
than <name 1::>.
**
33 TOO MANY SOURCE FILES
More than 38 (decimali file names were
specified
ror <name i::>.
19.3
Examples
The
following
example
combines
the
first Tour files
specified on the command line into a new file (the last
name
on the command line).
The
fi~st
four files all have the same
Page
19-05

Advertisement

loading

This manual is also suitable for:

Exordisk iii