Home Page The Club Computers News Links Glossary EYAWTK
Before Amiga Background ICS OCS ECS AGA ??? PPC
U-Boot SLB Linux Amiga OS Dual Boot Motherboards Peripherals Other
Initialisation Installation OS4 Updates About OS4 Networking Printing SFS Other
Introduction File System Workbench Preferences Commands Error Msgs Miscellaneous

AmigaOS 4.0 - About OS4 - Error Messages

This section attempts to list all of the possible AmigaDOS errors, along with probable causes and suggestions for recovery. Programmer errors are boxed.

Error Probable Cause Recovery Suggestion

101: Invalid message in dos packet

102: Wrong dos packet returned

103: Not enough memory available Not enough memory in your Amiga to carry out the operation. Close an unnecessary windows and aplications, then re-issue the command. If it still doesn't work, reboot. Memory may be sufficient, but fragmented. It is possible that you may need to add more RAM to your system.

105: Process table full There is a limit to the number of possible processes. Stop one or more tasks.

114: Bad template Incorrect command line. Verify the correct command format.

115: Bad number The program was expecting a numerical argument. Verify the correct command format.

116: Required argument missing Incorrect command line. Verify the correct command format.

117: Value after keyword missing Incorrect command line. Verify the correct command format.

118: Wrong number of arguments Incorrect command line. Verify the correct command format.

119: Unmatched quotes Incorrect command line. Verify the correct command format.

120: Argument line invalid or too long Your command line is incorrect or contains too many arguments. Verify the correct command format.

121: File is not executable You misspelled the command name, or the file may not be a loadable (program or script) file. Retype the filename and make sure that the file is a program file. In order to execute a script, either the s bit must be set or the EXECUTE command must be used.

122: Invalid resident library You are trying to use commands with a previous version. Reboot with the current version of AmigaDOS.

202: Object is in use The specified file or directory is already being used by another application. If an application is reading a file, no other program can write to it, and vice versa. Stop the other application that is using the file or directory, and re-issue the command.

203: Object already exists The name that you specified already belongs to another file or directory. Use another name, or delete the existing file or directory, and replace it.

204: Directory not found AmigaDOS cannot find the directory you specified. You have made a typing or spelling error. Check the directory name (use DIR if necessary). Re-issue the command.

205: Object not found AmigaDOS cannot find the file or device you specified. You may have made a typing or spelling error. Check the filename (use DIR) or the device name (use INFO). Re-issue the command.

206: Invalid window description This occurs when specifying a window size for a Shell, ED, or ICONX window. You may have made the window too big or too small, or may have omitted an argument. This error also occurs with the NEWSHELL command if you supply a device name that is not a window. Re-issue the window specification.

207: Object too large

209: Packet request type unknown You have asked a device handler to attempt an operation it cannot do. For example, the console handler cannot rename anything. Check the request code passed to device handlers for the appropriate request.

210: Object name invalid There is an invalid character in the filename or the filneame is too long. Re-type the name, taking care not to use any invalid characters or exceed the maximum length.

211: Invalid object lock You have used something that is not a valid lock. Check that your code only passes valid locks to AmigaDOS calls that expect locks.

212: Object is not of required type You may have specified a filename for an operation that requires a directory name, or vice versa. Verify the correct command format.

213: Disk not validated If you have just inserted a disk, the disk validation process may be in progress. It is also possible that the disk is corrupt. If you have just inserted the disk, wait for the validation process to finish. This may take less than a minute for a floppy disk, or up to several minutes for a hard disk. If the disk is corrupt, it cannot be validated. In this case retrieve the disk's files and copy them to another disk.

214: Disk is write protected The plastic tab is in the write-protect position. Remove the disk, move the tab to the writeable position, and re-insert the disk, or use a different disk.

215: Rename across devices attempted RENAME only changes a filename on the same volume. You can use RENAME to move a file from one directory to another, but you cannot move files from one volume to another. Use COPY to copy the file to the destination volume. Delete it from the source volum, if desired. Then use RENAME.

216: Directory not empty This error occurs if you attempt to delete a directory that contains files or sub-directories. If you are sure that you want to delete the complete directory, and all of the file and sub-directories within it, use the ALL option of DELETE.

217: Too many levels You have exceeded the limit of 15 soft links. Reduce the number of soft links.

218: Device (or volume) is not mounted If the device is a floppy disk, it has not been inserted in a drive, If it is another type of device, it has not been mounted with MOUNT, or the name is mispelled. Insert the correct floppy disk, mount the device, check the spelling of the device name, or revise your Mountlist file.

219: Seek failure You have attempted to call SEEK with invalid arguments. Make sure that you only SEEK within the file. You cannot SEEK outside the bounds of the file.

220: Comment is too long Your filenote has exceeded the maximum number of characters (79). Use a shorter filenote.

221: Disk is full There is not enough room on the disk to perform the requested operation. Delete some unnecessary files or directories, or use a different disk.

222: Object is protected from deletion The d (deleteable) protection bit of the file or directory is clear. If you are certain that you want to delete the file or directory, use PROTECT to set the d protection bit or use the FORCE option of DELETE.

223: File is write protected The w (writeable) protection bit of the file is clear. If you are certain that you want to overwrite the file, use PROTECT to set the w protection bit of the file.

224: File is read protected The r (readable) protection bit of the file is clear. Use PROTECT to set the r protection bit of the file.

225: Not a valid DOS disk The disk in the drive is not an AmigaDOS disk, it has not been formatted, or it is corrupt. Check to make sure you are using the correct disk. If you know the disk worked before, use a disk recovery program such as ??????? to salvage its files. If the disk has not been formatted, use FORMAT to do so.

226: No disk in drive The disk is not properly inserted in the specified drive. Insert the appropriate disk in the specified drive.

232: No more entries in directory This indicates that the AmigaDOS call EXNEXT has no more entries in the directory you are examining. Stop calling EXNEXT.

233: Object is soft link You tried to perform an operation on a soft link that should only be performed on a file or directory. AmigaDOS uses Action/Read/Link to resolve the soft link and retries the operation.

234: Object is linked

235: Bad loadfile hunk The loaded program is corrupted Load a new or original copy of the program.

236: Function not implemented You have attempted to execute a function that is not yet active. Wait until the next release of the software.

240: Record not locked

241: Record lock collision Another application is accessing the database Try accessing the database again.

242: Record lock timeout Another application has the database entry locked. Try again or quit the other application and retry.

243: Record unlock error

303: Buffer overflow Ocurs if pattern matching string is too long. Make pattern matching string shorter.

304: ***Break Occurs if program stopped via Ctrl+C. No recovery

305: File not executable The e (executable) protection bit of the file is clear. Use PROTECT to set the e protection bit of the file.

306: Operation not permitted on a pipe

307: Pipe connection is broken

308: Requested operation would block

309: Supplied signal bit number was invalid

401: Attempt to mount a device that is not a handler nor file system

402: Invalid device name construction, wrong number of colon characters

403: Invalid device name, longer than 255 characters

404: Invalid sector size, not a multiple of four

405: Invalid control string for device, longer than 255 characters

406: Invalid exec device driver name, longer than 255 characters

407: Invalid handler name, longer than 255 characters

408: Invalid startup string for device, longer than 255 characters

409: Invalid number of surfaces, sector size, number of sectors per block or number of sectors per track

410: No exec device driver name was supplied

411: Invalid number of cylinders, value out of range

412: No handler name, segment list or port address was supplied

413: Invalid global vector value, must be -2 or -1

414: Invalid task priority, must be in the range of

Disclaimer: Amiga Auckland have prepared the above information for the use of its members based on our experiences and as such is subject to revision at any time. Amiga Auckland cannot guarantee any of the information and cannot be held accountable for any issues that may result from using it.

Copyright 2006 Amiga Auckland Inc. All rights reserved.
Revised: February 9, 2006.