| CODE (in hex) |
MEANING |
EXPLANATION |
| 00 |
All is well |
The last command was successfully processed |
| 08 |
Clock Error |
Can be caused by a protected disk or Bad Disk or Bad Drive. A clock bit
was found missing when reading the disk. The disk may have been exposed to strong
magnetic fields or permanently damaged. Try overwriting the offending sector.
The disk controller chip may be faulty. |
| 0C |
Sector ID CRC Error |
One sector of the disk is damaged and reformatting may cure the problem.
This may have been due to strong magnetic fields or permanent damage. You might
have a hardware fault. |
| 0E |
Data CRC Error |
See 0C above. Overwriting may cure the problem instead of reformatting |
| 10 |
Drive Not Ready |
Either there is no power to the drive, no disk in it, an attempt to read
a non-existant drive or the drive went NOT READY while a read/write operation
was in effect. Check the disk cable or try a hard rest. |
| &11 |
Escape |
The ESCape key has been pressed |
| 12 |
Write Protect |
Disk is read only |
| 14 |
Track 0 Not Found |
Indicates a hardware fault. Most likely the microswitch that that detects
track 0 in the drive is faulty. |
| 16 |
Write Fault |
Your drive has detected a fault whilst trying to write data on the disk.
Almost certainly a hardware fault. Check the cable first. |
| 18 |
|
An attempt was made to read or write a sector that does not exist or to
read a protected sector and the DFS was unable to decode the data correctly. Is
the disk formatted? |
| 73 |
The disk controller was not found |
Check the physical connection between the controller chip and the circuit
board/socket |
| &92 |
Aborted |
You have not replied YES to the question "Destroy?" when using *DESTROY |
| &93 |
Won't |
You have tried to *RUN a file whose load address is FFFFFFFF. This address
is reserved for text files which are *EXECed (ie read as if typed at the keyboard)
whereas files that are *RUN are usually machine code. |
| &94 |
Bad Params |
Invalid address parameters were supplied when specifying the memory area
to be used by *COMPACT |
| &95 |
Too Many Defects |
During formatting too many media defects were found for the disk to be
useable |
| &96 |
Can't Delete CSD |
You cannot delete the CSD. Therefore you must set another directory as
the CSD |
| &97 |
Can't Delete Library |
You cannot delete the current library. Therefore you must set another
before deleting this one. |
| &98 |
Compaction Required |
The free space is too fragmented. There is no space large enough for your
data. |
| &99 |
Map Full |
The free space map is full (contains 80 entries). Use *COMPACT to allow
further information to be saved. |
| &A |
Data was not written/read in the alloted time |
Caused by disk or drive or possibly false interrupts inside the computer. |
| &A7 |
No Directory |
|
| &A8 |
Broken Directory |
This should be a rare occurrence. The directory has become corrupted.
You may have to reformat the disk and copy your backup files on it. Sometimes
this is only the copy in memory that is affected and a resut cures the problem.
If you know what you are doing this can be also be rectified using a disk sector
editor. |
| &A9 |
Bad FS Map |
Either the computer memory or secotrs 1 and 1 of your disk are corrupted.
Try resetting the computer with CTRL-BREAK |
| &AA |
Bad Checksum |
The computer memory has become corrupted preventing ADFS to read, write
or close a file. Reset the computer with CTRL-BREAK |
| &B0 |
Bad Rename |
A directory cannot be renamed in this way |
| &B3 |
Dir Full |
You can only have 47 objects in an ADFS directory. You may be able to
put some machine code files into the library or create another directory. |
| &B4 |
Dir Not Empty |
You must delete all the objects in a directory before deleting the directory
itself. |
| &B7 |
Outside File |
An attempt has been made to set the pointer of a file (which is only open
for reading) to a value beyond the end of a file. |
| BD |
Not Enabled |
You need to use the *ENABLE command before you can *BACKUP or *DESTROY
(DFS 1.0 or earlier) |
| &BD |
Access Violation |
You have tried to read or load a file which has not got the R attribute
set or write a file where the W attribute is not set. |
| BE |
Cat Full/Catalogue Full |
The DFS only allows 31 files per disk side. You have tried to exceed that
number. Use a different disk. |
| BF |
Can't Extend |
The file you are tring to write/save is larger than the original and cannot
be squeezed into its existing slot. Try saving with a new name then delete the
original and rename it. You may need to *COMPACT the disk. |
| &C0 |
Too many open files |
You have tried to open more files than there are channels open. To set
channels use the *SET command with a maximum of 10 channels (STL ADFS) |
| &C1 |
Not open for update |
An attempt has been made to write to a random access file that is only
open for reading. Instead of using OPENOUT use OPENUP (or its assemblylanguage
equivalemt). Also (File) Read Only |
| &C2 |
Already Open |
You are opening a file that has already been opened, or you are deleting
an open file or overwriting one with a new version. In the latter case you need
to close the file. |
| &C3 |
Locked |
The object is locked and cannot be deleted, renamed or overwritten. To
perform one of these operations you need to unlock the file. |
| &C4 |
Already Exists |
You have tried to create an object with the same name as an existing object.
You have tried to rename a file for which there is already a file with the new
name on the disk. Choose a new name or delete the offending item. |
| C5 |
Drive Fault |
See &C7 |
| &C6 |
Disk Full |
|
| &C7 |
Disk Error |
The controller found a fault on the disk during the last disk operation.
See 00, 08, 0C, 0E, 11, 12, 14, 16, 18. Are you using the correct filing system
for the disks/controller chip you are using? |
| &C8 |
Disk Changed |
Issue *MOUNT to read in the free map space |
| &C9 |
Disk Protected |
|
| &CB |
Bad Opt |
You have use the *OPT command with an invalid argument |
| &CC |
Bad Name |
An illegal filename was used. The characters : and $ and special characters
such as @ cannot be used in filenames. |
| CD |
Bad Drive |
Drive parameter must be 0-3. If part of a filename the drive must be preceded
by a colon (eg 0:myfile) |
| &CD |
Drive Not Ready |
The drive is not yet up to speed. If this persists the drive may be faulty. |
| CE |
Bad Directory (Bad Dir) |
You have specified a bad directory parameter with *DIR or *LIB. You have
probably typed too many characters. |
| CF |
Bad Attribute |
*ACCESS command used with wrong parameters |
| &D6 |
Not Found |
Object referred to has not been found |
| DB |
Syntax |
You have completely misused a DFS command. Check the parameters and the
rules for them. *HELP DFS or *HELP UTILS may be of assistance. |
| DD |
Channel |
See below |
| &DE |
Channel |
A sequential file operation has been attempted with an invalid file handle
or incorrect command |
| DE |
EOF |
End Of File |
| &DF |
EOF |
2 attempts have been made to read beyone the end of a file. The failure
of the first is shown by the contents of the C flag following an OSBGET or OSGBPB
command |
| &FD |
Wildcards |
A wildcard character has been found where a full object spec is required. |
| FC |
Bad Address |
All addresses should be im hexadecimal (hex) but should not be prefixed
with "&". The command you have used expects an address parameter |
| &FE |
Bad Command |
The last command was not recognised by the ADFS or any other ROM nor was
it found (as a machine code file) on the disk. Possibly you have mistyped it.
Or you have inserted the wrong disk or you have the wrong settings in *LIB. Or
you may have omitted the drive/directory from the command (the computer otherwise
looks at the default). |