Tandy TRS-80 Owner Manual & Programming Manual page 93

APPENDIX G
ERROR MESSAGES
/O
Division
by
zero.
The Computer was
asked
to
divide
a
number
by
0,
which
is
impossible.
You
could also get this error
message
if
you
do not
enclose
a filename
in quotation
marks.
AE
File
Already
Exists.
You
are trying
to
RENAME
or
COPY
a
file
to
a
filename which Already
Exists.
DS
Direct Statement. There
is
a
direct
statement
in
the data
file.
This could be caused
if
you
load a
program with no
line
numbers.
ER
Write
or
Input past
End
of
Record
(direct access
only).
You
are attempting
to
PUT
more
data in the
record
than
it
can
hold or
INPUT
more data than
it
contains.
AO
Attempt
to
open a data
file
which
is
Already
Open.
BR
Bad
Record
Number. You have
used an
impossible
record
number
in
your
PUT
or
GET
line.
Either
it
is too
low
(less
than
1)
or too
high
(higher
than
the
maximum
number
of records the
Computer
can
fit
on
the
disk).
Use
a different record
number
in
the
PUT
or
GET
line,
or assign a smaller record
length in the
OPEN
line.
BS
Bad
Subscript.
The
subscripts in
an
array
are out
of
range.
Use
DIM
to
dimension
the
array.
For
example,
if
you have
A(12)
in
your program,
with-
out a preceding
DIM
line
which dimensions array
A
for
12 or
more
elements,
you
will
get
this error.
CN
Can't continue.
If
you
use the
command
CONT
and you
are at
the
END
of the
program, you
will
get this
error.
DD
Attempt
to
redimension an
array.
An
array can
only
be dimensioned
once.
For example, you
can-
not
have
DIM
A(12)
and
DIM
A(50)
in the
same
program.
DF
Disk
Full.
The
Disk you
are trying
to
store
your
file
on
is
Full.
Use
another
disk.
DN
This
is
either
a Drive
Number
or
Device
Number
error.
Drive
Number
Error.
You
are using a
drive
num-
ber higher than
3.
You
will also get
this error
if
you
do not specify a drive
number when
using
DSKINI
or
BACKUP.
If
you have
only one
drive
specify drive with these two
commands
(DSKINIO
or
BACKUP
0).
Device
Number
error.
You
are using
more
buffers
than
the
Computer
has
reserved.
Use FILES
to
reserve more.
You might
also get this error
if
you
use a nonexisting buffer
number
(such as buffer
#
-
3)
or
omit the buffer (such as
FIELD
1
AS
A$
rather
than
FIELD
#1,
1
AS
A$).
FC
FD
FM
FN
FO
FS
ID
IE
IO
Illegal
Function
Call.
This
happens
when
you use
a
parameter (number) with
a
BASIC
word
that
is
out of range.
For example
SOUND
(260,260)
or
CLS(IO)
will
cause
this error.
Also RIGHT$(S$,20),
when
there are only 10 characters
in S$,
would
cause
it.
Other examples
are a negative
subscript,
such
as
A(
-
1),
or
a
USR
call
before the address
has been
POKEd
in.
Bad
File
Data. This
error occurs
when
you
PRINT
data
to
a
file,
or
INPUT
data
from
the
file,
using
the
wrong
type
of variable
for
the corresponding
data.
For example,
INPUT #
1,
A,
when
the data
in
the
file is
a
string,
causes
this error.
Bad
File
Mode.
You
have
specified the
wrong
file
mode
("O,"
"I,"
or "D")
in
your
OPEN
line for
what
you
are
attempting
to do.
For example, you
are
attempting
to
GET
a record
from
a
file
OPENed
for "I" (use "D") or
WRITE
data
to
a
file
OPENed
for "I"
(use "O").
Bad
File
Name. You
used
an
unacceptable format
to
name
your
file.
Field Overflow.
The
field
length
is
longer than
the
record length.
Bad
File Structure.
There
is
something wrong
with your
disk
file.
Either the data
was
written
incorrectly or the directory track on the disk
is
bad.
See
IO
for instructions
on
what
to do.
Illegal
Direct statement.
You
can
only use
INPUT
as a line in the program, not as a
command
line.
Input past
End
of
file.
Use
EOF
or
LOF
to
check
to see
when
you've
reached
the
end
of
the
file.
When
you
have,
CLOSE
it.
Input/Output
error.
The Computer
is
having
trou-
ble inputting
or
outputting information
to
the
disk.
83