Advertisement
OTHER SYSTEM FUNCTIONS
27.4 -- Diskette File Functions
INDEX
NUMBER
ERROR MESSAGE
29
**
22 BUFFER OVERFLOW
2A
**
23 CHECKSUM ERROR
2B
**
26 FILE IS WRITE PROTECTED
2C
**
43 INVALID DIRECTORY ENTRY NO. AT \8
2D
**
44 CANNOT DEALLOCATE ALL SPACE,
DIRECTORY
ENTRY
EXISTS AT \8
2E
**
45 RECORD
LENGTH
TOO LARGE
2F
**
48 CHAIN
OVERLAY
DOES NOT
EXIST
30
**
08 CHAIN ABORTED BY BREAK
KEY
31
**
09 CHAIN ABORTED BY SYSTEM ERROR
STATUS
WORD
32
**
49 CHAIN ABORTED BY
ILLEGAL
OPERATOR
33
**
50 CHAIN
ABORTED
BY
UNDEFINED LABEL
34
**
51 CHAIN ABORTED BY PREMATURE
END OF
FILE
35
**
52 SECTOR BUFFER SIZE ERROR
36
**
53
INSUFFICIENT MEMORY
In
addition,
two
error messages have
speci~ic
calling
sequences.
These two messages have the following format when
display~d:
INDEX
NUMBER
00
01
ERROR
MESSAGE
**UNIF.
I/O
ERROR -- STATUS
~
\3 AT \8
**PROM I/O ERROR -- STATUS
=
\3
AT h
DRIVE
i
- PSN
J
.
The
First
case
<index
number
DO)
should
be
used
for
displaying standard
erro~
messages as a result
or
the
device
independent I/O functions.
The
.MDERR
function expects the
X
register to contain the address or an IOCB.
The status
byte
of
the
IOCB
will be decoded into one of the standard system
error messages shown above.
In the
event
that
an
illegal
status
code is contained in the IOCB,
the error message will
take on the fOl'm as shown above.
The
"\3
U
parameter
will
contain
the value of the status byte, and the
"\8
11
parameter
will contain the address of the call
to
the
error
message
function.
The
second
case
(index
number 01> should be used for
displaying standard diskette contl'oller
error
messages
(as
returned
by
.EREAD,
.
EWRIT,
.
MERED,
.MEWRT).
The
.MDERR
function expects the
X
register to contain the address
of
a
three-byte packet.
The format of the packet is shown below:
Page
27-33
Advertisement
