50: RECORD NOT PRESENT
Result of disk reading past the last record through INPUT#, or GET#
commands. This message will also occur after positioning to a record
beyond end of file in a relative file. If the intent is to expand the file by
adding the new record (with a PRINT# command), the error message may
be ignored. INPUT or GET should not be attempted after this error is
detected without first repositioning.
51: OVERFLOW IN RECORD
PRINT# statement exceeds record boundary. Information is truncated.
Since the carriage return which is sent as a record terminator is counted to
the record size, this message will occur if the total characters in the
record (including the final carriage return) exceeds the defined size.
52: FILE TOO LARGE
Record position within a relative indicates that disk overflow will result.
60: WRITE FILE OPEN
This message is generated within a write file that has not been closed is
being opened for reading.
61: FILE NOT OPEN
This message is generated when a file is being accessed that has not been
opened in the DOS. Sometimes, in this case, a message is not generated;
the request is simply ignored.
62: FILE NOT FOUND
The requested file does not exist on the indicated drive.
63: FILE EXISTS
The file name of the file being created already exists on the diskette.
64: FILE TYPE MISMATCH
The file type does not match the file type in the directory entry for the
requested file.
65: NO BLOCK
This message occurs in conjunction with the B-A command. It indicates
that the block to the allocated has been previously allocated. The parame-
ters indicate the track and sector available with the next highest number.
If the parameters are zero (0), then all blocks higher in number are in use.
79
To Next Page
Loading...
