Advertisement
ERROR
MESSAGES
28. 1 -- Oi s k etta Contl'o 11 er Errors
is
a
value
returned
by
the diskette controller.
The errors
are of the same
type that
cause the initialization process to
give
cont~ol
to
EXbugi
however,
instead
of beginning with the
letter liE
II ,
the status (nn) begins with the
digit
"3
1
' .
The
second
digit
or
the
status
corresponds
directly
to the
diskette controller error number discussed
in
the
previous
section.
The
"E't
has been replaced
by
the
"3".
Thus,
status
31
is the same as
El
32
is the same as
E2
39
is the same as
E9.
A
memory address (only meaningful ror system diagnostiCS) is
substituted for the
lette~
Uh";
the logical
unit
number
is
substituted
ror
the
letter
"i";
and
the physical sector
number
(PSNl
at which the error occurred is
substituted
ror
the let tel'
II
J
II •
For
errors
that
are retryable (status
311
34,
38, and
39 )
J
the roll ow in g act ion s h a v e
b
e en t a ken ina n a t temp
t
to
bypass
the
errol'.
Firstl
the
ROM
firmware tried to re-access
the sector Five ·times.
The
head
was
then
positioned
a
maximum.
of
rive cylinders outward Tram the sector in error,
repositioned back over the sector,
and another five
accesses
attempted.
Lastly,
the head
was
positioned a maximum
oT
rive
cylinders inward from the sector in error} repositioned
back
over the sector, and another five accesses attempted.
Occassionally,
if
the diskette in drive zero
was
changed
without properly reinitializing the system,
or
if
an
MDOS
sq~tem
Tile is
moved,
r1!lnam@dl
or
deleted
from
the
directorql
the error messages
EII ERI EU,
or
EV
can
be
displayed
and
control given to the debug monitoT'.
These error messages are
explained in the previQus section.
28.2 Standard Command Errors
The Following list contains all of
the
standard
error
messages
than
can
be displayed
by
the
MDOS
commands.
They
are listed in order of their two-digit reference
number
ror
easy
location.
This
number is not to be confused with the
error
message
index
number
that
is
loaded
into
the
B
accumulator
when
the system error message function
L MDERR,
section 27.4) is accessed.
In
some
cases,
the
error
message
applies
also
to
user-written
programs
using
the
device
independent
I/O
fun c t ion
5 .
The n i t h e e
l' l' 0 l'
con d
i
t ion
l'
e
t urn e d . i n t h e
I DC B
entry
IOCSTA (section 25.3.1. 20) llIill contain a value, which
when decoded by the
.MDERR
function,
would
result
in
the
"
Advertisement
