Computers Overview
Commodore PET
        PET ROMs
            IEC (for C64)
            Parts List
            User's Guide
                Error Codes
Sinclair ZX80
Sinclair ZX81
BBC Micro
Commodore 64
Sinclair ZXSpectrum
Memotech MTX
Memotech CP/M
Tatung Einstein
Atari ST
Commodore Amiga
DEC 3000 AXP
Raspberry Pi



Commodore PET Projects - petSD+

petSD+ - User Guide



Error Messages

Error messages displayed on the PET or petSD+ LCD screen are a subset of the Commodore DOS and CMD error messages with some additions to support petSD+

Errors are returned over the command channel in the format: ee, estring,tv,sv, where :
ee = a two digit error number
estring = an ASCII string describing the error
tv = the track variable (the logical track where the error took place)
sv = the sector variable (the logical sector where the error took place)
note :   Some errors define special meanings for the track and sector variables - see table

ee estring Meaning
00 OK 1 This code is present when no other error condition exists.
01 FILES SCRATCHED 1 Occurs after using the DOS or BASIC scratch commands. The number of files scratched will be indicated in the track variable, anm the sector variable will contain a zero.
02 (not used) CMD Partition support
20 READ ERROR NODISKEMU Generic Read Error
20 READ ERROR Header block not found (Commodore DOS)
21 READ ERROR No sync character (Commodore DOS)
22 READ ERROR Data block not present (Commodore DOS)
23 READ ERROR Checksum error in data block (Commodore DOS)
24 READ ERROR Undefined
25 WRITE ERROR NODISKEMU Generic Write Error
25 WRITE ERROR Write-verify error (Commodore DOS)
26 WRITE PROTECT ON Indicates that an attempt was made to write to the SD Card while the card Write Protect function was activated.
27 READ ERROR Checksum error in header block (Commodore DOS)
28 WRITE ERROR Undefined
29 READ ERROR Disk ID mismatch (Commodore DOS)
30 SYNTAX ERROR Indicates that the petSD+ command interpreter was unable to identify the last command sent via the command channel. This is usually caused by incorrect characters being present in the disk command.
31 SYNTAX ERROR Usually indicates that the first character of the last command string was not recognized as part of a legal DOS command.
32 SYNTAX ERROR Occurs when a disk command string contains over 254 characters. Due to the large size of the command channel input buffer in petSD+, this error should rarely be encountered.
33 SYNTAX ERROR Usually indicates that an attempt was made to use wildcards or pattern matching within a file name or disk command that does not accept wildcards.
34 SYNTAX ERROR The last disk command failed due to a missing file name or the file name should have been preceded by a colon (:).
39 FILE NOT FOUND (Commodore DOS)
40 (not used) CMD SCSI controller support
41 (not used) CMD SCSI controller support
42 (not used) CMD SCSI controller support
43 (not used) CMD SCSI controller support
44 (not used) CMD SCSI controller support
45 (not used) CMD SCSI controller support
46 (not used) CMD SCSI controller support
47 (not used) CMD SCSI controller support
49 (not used) CMD SCSI controller support
50 RECORD NOT PRESENT The last attempt to access a relative (REL) file record specified a record number which does not yet exisL This condition will result even when attempting to create or expand a relative file, and under those conditions should be ignored.
51 OVERFLOW IN RECORD The last attempted write to a relative record contained more data than could be stored in the record. When this occurs, as much data as can fit is stored into the record.
52 FILE TOO LARGE The last attempt to access a relative record would have exceeded the amount of storage space remaining in the partition specified. Under this condition, no additional records were added to the file, and if this was an attempt to create a new relative file, the file was not created
60 WRITE FILE OPEN The last attempt to open a file was made to a file which was already open for writing.
61 FILE NOT OPEN Indicates that the last attempt to access data was made to a file which was not properly opened. Under some circumstances, this error is not generated and the attempt to access the file is simply ignored.
62 FILE NOT FOUND During the last attempt to open a file, the DOS could not find the file specified by the path and filename given. This error will also occur if the filetype of the file does not match the allowed flletypes.
63 FILE EXISTS While attempting to open a new file, another file with the same name was found in the specified partition or sub-directory.
64 FILE TYPE MISMATCH The last disk operation specified a file which did not match the filetypes allowed for that operation. 
65 NO BLOCK Indicates that an attempt was made to allocate a block which was already allocated using the BLOCK-ALLOCATE (B-A) command. The track and sector variables will contain the next available block when this condition occurs. If the track variable contains a zero, there are no blocks available.
66 ILLEGAL BLOCK Occurs when an attempt is made to access a track or sector which does not exist. This may occur if one of the track and sector links within a file have become corrupted.
67 ILLEGAL BLOCK Usually caused by a corrupt disk. This error shows up when the block parameters for a partition do not exist
70 NO CHANNEL This indicates that the specified channel within a disk command is already in use, or that all buffers in the drive are currently in use. This may be an indication that too many files are currently opened.
71 DIRECTORY ERROR Indicates that the BAM (Block Availability Map) on the diskette is invalid. To correct the problem, Validate the disk.
72 DISK FULL2 Occurs when the targeted SD Card or its directory are full. When this message is sent, there are still two blocks free, allowing the current file to be closed.
An attempt was made to write to a diskette with a non-compatible format. The DOS version stored at location $0101 was not a $41. This memory address is normally updated during initialization by reading byte 2 from track 18, sector 0.
74 DRIVE NOT READY Occurs after an attempt was made to access an illegal drive or an SD Card that has not been properly formatted.
75 (not used) CMD SCSI controller support
76 (not used) CMD SCSI controller support
77 (not used) CMD Partition support
78 BUFFER TOO SMALL 3 petSD+ Image file support
79 IMAGE FILE INVALID 3 petSD+ Image file support
99 CLOCK UNSTABLE 3 petSD+ Real Time Clock support
1 These strings are expected status returns and are not errors
2 NODISKEMU version of CBM/CMD Error String
3 NODISMEMU Addition



petSD+ Commands  <  Previous Page   Goto   Next Page  >  




mailto: Webmaster

 Terms & Conditions