AMOS Errors - AMOS Professional Manual

Editing error messages

While you are editing programs, one of the following messages may appear.

Bottom of text

The text cursor has come to the last line of your current program.

Cannot delete warm-start information!

You've tried to use AMOS Warm-start system on a Write protected disc. AMOS won't reload until the "AMOSPro.LastSession" has been successfully deleted. Remove the protection and try again. If the problem persists, you'll have to delete the file manually. It's in the APSystem folder.

Cannot hide the last window

AMOS Professional always requires at least one window on the screen at any one time. So you can't hide the final window away as an accessory.

Cannot load configuration

If you've tried to load a new configuration using the option in the [Config] menu, and the file you have selected is not valid then this error will be generated. It will also appear in the CLI or Workbench if AMOS Professional cannot load the default configuration when it is being booted or re-loaded after a KILL EDITOR command. A backup copy of the default configuration file can be found in the Extra_Configs folder on the AMOSPro System disc.

Cannot load included file

The INCLUDE command can't find your chosen include file. Check that it's available in one of your drives.

Cannot load included file

The INCLUDE command can't find your chosen include file. Check that it's available in one of your drives.

Cannot save editor set-up: warm start not enabled

AMOS Professional cannot save the AMOSPro.LastSession file or cannot save one of the program files being worked on. This can happen for many reasons - disc protected, no disc in drive, disc full etc. If this happens, the next warm-start procedure is aborted and the next time you boot up you'll have an empty editor.

Disc error

The Editor has been unable to load a configuration file, include file, or library from the current disc. If the file is on a floppy, try re-inserting it a couple of times. If all else fails, use DISCDOCTOR to salvage your data and try again with a fresh disc.

Editor command not runnable

ASK EDITOR and CALL EDITOR can only be used by EDITOR ACCESSORIES. These are normal programs with a SET EDITOR command at the start.

Editor function not found

You've used an incorrect function number in an ASK EDITOR or CALL EDITOR command.

Editor function not found

You've used an incorrect function number in an ASK EDITOR or CALL EDITOR command.

Editor function not found

You've used an incorrect function number in an ASK EDITOR or CALL EDITOR command.

Mark not defined

This error is generated using the [Goto] system mark and [Goto] user mark from the [Editor] menu. You are only allowed to jump to a mark if it's been previously defined from the editor. User marks are created by you, but System marks are generated automatically whenever you move through an AMOS program listing. However, if you call them straight after a program has been loaded, you can still get this error.

Mark not defined

No more Redo

You've run out of things to redo. You can only redo lines which have been previously recalled by the UNDO command. So every REDO matches exactly one UNDO operation.

No more Undo

You've reached the end of the stored key presses used by the undo option. If you've got enough memory, AMOS Professional will happily allow you to undo the entire editing session a character at a time.

No more Undo

Not done

This "error" is generated when you abort from an operation such as [Load], [New], or [Quit] I corn the Editor. It's also produced when the editor is unable to comply with your instructions.

Not done

This "error" is generated when you abort from an operation such as [Load], [New], or [Quit] I corn the Editor. It's also produced when the editor is unable to comply with your instructions.

Out of buffer space

The AMOS Professional Editor stores each program listing in an internal "memory buffer". If you run out of space in this buffer, you'll get an "Out of buffer space" error. The solution is to use the [Set Text Buffer] function from the [Editor] menu to increase the allocation. Each extra byte can hold a single character in your program listing. Note that providing you INCREASE the memory buffer, your current program listing will be perfectly safe. If you reduce it however, it will be erased from memory!

The most common cause of this problem is when you select the "Automatic Adaptation" option after loading a large file. This will reserve just 254 bytes for your editing operations. If you click on [No], AMOS will automatically call [Set Text Buffer] so that you can expand the memory buffer to a more sensible size.

Out of Editor memory

You've tried to load an AMOS program which is too large to fit into the available memory. If you've several windows open, try closing some of them to grab back a little extra space. Don't forget to save any changes first! Also check the amount of available memory with the [Information] option from the [Project] menu. If there seems to be plenty of Ram, you've probably suffered from a memory fragmentation problem. Save your programs, and re-boot your Amiga from scratch.

Out of memory

There is no more memory available to hold the current programs. Using the CLOSE WORKBENCH instruction can restore 40k of memory used by the Workbench screen.

Out of memory: Cannot load program

This error is generated when there isn't enough memory to hold an accessory program assigned to one of the Editor options. It's also produced by the PRUN command. The solution is to free up as much memory as possible by closing any unused windows. If you still can't call the program, save any changes and re-boot AMOS Professional from scratch. This re-initialises the Amiga's memory system and provides the maximum storage space your AMOS programs.

Please choose a RELOCATABLE PROGRAM!

The [Insert Program] option from the [Editor/Procedures] menu only works with 68000 machine code programs in PC relative (relocatable) format. If you've included instructions which move directly to a fixed memory location, your assembler will have placed extra relocation information at the end of your machine code. This cannot be used by AMOS Professional, so your program will be rejected out of hand.

Program already running

This will occur if a program trys to PRUN itself.

Program already running

This will occur if a program trys to PRUN itself.

Sorry! Editor configuration not recoverable!

AMOS Professional has attempted a Warm-start. In order to work it needs to be able to find the "AMOSPro.LastSession" file from the APSystem folder. If this is corrupted, or write-protected, you'll get an error when you try to load AMOS Professional. If you've write-protected the disc, remove the protection, and try again. If it still fails to load, delete the "AMOSPro.LastSession" file from the CLI and re-boot. AMOS Professional should now load correctly.

Sorry! Editor configuration not recoverable!

Text buffer too small

The SET TEXT BUFFER command from the Editor menu will not allow you to set the text buffer smaller than 1024 bytes. Try a higher value.

Too many direct mode variables

Normally, you are allowed to create up to 64 new variables while in direct mode. If your program is using too much memory, space in the variable table may become restricted.

Too many direct mode variables

Normally, you are allowed to create up to 64 new variables while in direct mode. If your program is using too much memory, space in the variable table may become restricted.

Too many direct mode variables

Normally, you are allowed to create up to 64 new variables while in direct mode. If your program is using too much memory, space in the variable table may become restricted.

This function cannot be used in a macro!

When you're creating a Macro, you're not allowed to call up any existing Macro definitions from the keyboard. If you try, you'll get a dialogue box with this error, and your Macro definition will be aborted.

This function cannot be used in a macro!

This is not a 'User' menu option!

The Delete Option command can only be used to delete entries from the User Menu. If you try to wipe out any other item, you'll get an error.

This line can't be modified

You've tried to edit a line containing a closed procedure. This is not allowed! If the procedure contains normal AMOS instructions you can use F9 to expand the definition onto the screen. Machine code procedures can't be listed in this way.

This line can't be modified

This menu option is already assigned to a program!

You've tried to assign a new program to a menu item which has already been set up. Click on [Cancel] to abort, or [Replace] to assign your new program.

This menu option is already assigned to a program!

You've tried to assign a new program to a menu item which has already been set up. Click on [Cancel] to abort, or [Replace] to assign your new program.

Variable name buffer too small

You have used too many overlong names for your variables. Variable names are held in a buffer, and its default size may be changed from the [Set Interpreter] option in the [Config] menu.

Warm-Start Error

AMOS Professional has attempted to re-start using the session data held in the "AMOSPro.LastSession" file from the APSystem folder. This can happen if you attempt to warm-start AMOS Professional from a Write-Protected disc. Remove the protection and try again. If AMOS still fails to load, there's probably been a disc error of some sort. So delete the "AMOSPro.LastSession" file from the CLI and re- boot. AMOS should now load as normal.

What block?

You've tried to use the Block commands without defining a block on the screen. This can be accomplished with the Ctrl + B or [Block On/Off] option from the [Block] menu. You'll also get this error if you try to [Print] or [Save] a block. These operations first require you to grab the block into memory with [Store] or [Cut]. Highlighting the block is not enough!

What block?

Program errors

There is no need to wait until your programs are executed before any errors become obvious. By making use of the [Test] option, an automatic check is made of all the instructions in your current program while you are still editing. The following messages may also appear when a program is [Run].

Array already dimensioned: You are trying to dimension an array that has already been dimensioned in the current program.
Array not dimensioned: You must first give an array a dimension before it can be specified in an expression.
Array not dimensioned: You must first give an array a dimension before it can be specified in an expression.
Array not dimensioned: You must first give an array a dimension before it can be specified in an expression.
Array not dimensioned: You must first give an array a dimension before it can be specified in an expression.
ELSE without ENDIF: You have forgotten to end an IF test with its ENDIF command.
ELSE without ENDIF: You have forgotten to end an IF test with its ENDIF command.
ELSE without ENDIF: You have forgotten to end an IF test with its ENDIF command.
ELSE without ENDIF: You have forgotten to end an IF test with its ENDIF command.
FOR without matching NEXT: You are trying to use a FOR command, but have forgotten to follow it with a NEXT statement.
IF without ENDIF: A structured IF test must be ended by a single ENDIF statement. This sort of IF test is totally different from an IF ... THEN command.
IF without ENDIF: A structured IF test must be ended by a single ENDIF statement. This sort of IF test is totally different from an IF ... THEN command.
Illegal number of parameters: You've entered the wrong number of values in one of your AMOS Professional instructions. You can find the correct syntax using the HELP system. Just position the cursor over the start of the offending instruction, and hit the HELP key from the keyboard.
Included file is not an AMOS program!: The AMOS INCLUDE system is only capable of including runnable .AMOS format programs. You've probably typed the filename wrong.
Included file is not an AMOS program!: The AMOS INCLUDE system is only capable of including runnable .AMOS format programs. You've probably typed the filename wrong.
Included file is not an AMOS program!: The AMOS INCLUDE system is only capable of including runnable .AMOS format programs. You've probably typed the filename wrong.
Included file is not an AMOS program!: The AMOS INCLUDE system is only capable of including runnable .AMOS format programs. You've probably typed the filename wrong.
Music bank not found: There is no music bank.
Music bank not found: There is no music bank.
Music bank not found: There is no music bank.
Music bank not found: There is no music bank.
No jumps allowed in the middle of a loop!: You can only jump out from a loop once you are inside of it. You cannot jump into a loop using a GOTO or GOSUB statement.
Not enough loops to exit: You have specified a larger count of loops than the number of active loops available in your EXIT or EXIT IF command.
Not enough loops to exit: You have specified a larger count of loops than the number of active loops available in your EXIT or EXIT IF command.
Not enough loops to exit: You have specified a larger count of loops than the number of active loops available in your EXIT or EXIT IF command.
Procedure not closed: You have forgotten to end one of your procedures with an END PROC statement.
Procedure not closed: You have forgotten to end one of your procedures with an END PROC statement.
Procedure not closed: You have forgotten to end one of your procedures with an END PROC statement.
Procedure not closed: You have forgotten to end one of your procedures with an END PROC statement.
Shared must be alone on a line: The SHARED command must be the only statement on the current line.
Structure too long: Loops in AMOS Professional have a maximum span of 65,536 bytes. So if you have lines between a FOR.. .NEXT loop that exceed this limit you'll receive this error. The same applies to IF...ENDIF and all other loops.
Structure too long: Loops in AMOS Professional have a maximum span of 65,536 bytes. So if you have lines between a FOR.. .NEXT loop that exceed this limit you'll receive this error. The same applies to IF...ENDIF and all other loops.
Structure too long: Loops in AMOS Professional have a maximum span of 65,536 bytes. So if you have lines between a FOR.. .NEXT loop that exceed this limit you'll receive this error. The same applies to IF...ENDIF and all other loops.
This instruction must be used within a procedure: You are trying to use the SHARED command outside of a procedure definition.
This instruction must be used within a procedure: You are trying to use the SHARED command outside of a procedure definition.
This instruction must be used within a procedure: You are trying to use the SHARED command outside of a procedure definition.
This instruction must be used within a procedure: You are trying to use the SHARED command outside of a procedure definition.
Undefined label: Your program is trying to find a label that you have forgotten to specify.
Undefined procedure: You are trying to call up a procedure that does not exist in your program.
Undefined procedure: You are trying to call up a procedure that does not exist in your program.
Undefined procedure: You are trying to call up a procedure that does not exist in your program.
Variable buffer can't be changed in the middle of a program!: Apart from a REM statement, the SET BUFFER command must always be used as the very first line of your program.
Variable buffer can't be changed in the middle of a program!: Apart from a REM statement, the SET BUFFER command must always be used as the very first line of your program.
Variable buffer can't be changed in the middle of a program!: Apart from a REM statement, the SET BUFFER command must always be used as the very first line of your program.
Variable buffer can't be changed in the middle of a program!: Apart from a REM statement, the SET BUFFER command must always be used as the very first line of your program.

Run-time errors

When AMOS Professional comes across a mistake while your program is running, it will automatically halt the program, pinpoint the offending instruction and display the relevant error message. As soon as you continue editing your program, the cursor will go to the line in your program where the error is lurking. These run time errors each have a special code number, which is displayed in brackets immediately after the error message, and these code numbers can be used in the process of error trapping. For example, you may want to find the error message that goes with a particular code number, by using a line such as:

Error Errornumber

256 characters for a wave (181)

Audio waves can only be created by a list of 256 bytes.

256 characters for a wave (181)

Audio waves can only be created by a list of 256 bytes.

256 characters for a wave (181)

Audio waves can only be created by a list of 256 bytes.

Animation string too long (113)

Your current AMAL program is too long, the maximum number of bytes is 65536. You may split your program into several smaller sections, and it is possible to animate the same object using several AMAL channels.

AREXX device not interactive (199)

This error is reported back by AREXX. We don't know what it means so write to Commodore!

Arexx library not found (194)

You've attempted to use the AREXX commands on a system on which it hasn't been installed. The AREXX library is held in the "rexxsyslib.library" and should be normally available from the LIBS directory of your Workbench disc. Note; AREXX is provided free with Workbench 2, but other users will need to purchase it separately.

Arexx message not answered (198)

You've received a message from an external AREXX program and you haven't answered back. You must answer all messages at once otherwise the sending program will be hanging around waiting for your answer.

Arexx message not answered (198)

Autotest already opened (111)

An illegal AMAL autotest has been defined inside an existing autotest command.

Bad IFF format (30)

You are attempting to use LOAD I FF to load a file in the wrong format. LOAD I FF can only load IFF screens into memory and not general purpose IFF files.

Bad parameter (149)

You've made a mistake when setting up the serial port with SERIAL SPEED, SERIAL BITS, SERIAL PARITY, or SERIAL X. Check your current set up.

Bank already reserved (35)

You have tried to create a memory bank that already exists.

Bank not reserved (36)

The bank that you are trying to select has not been created using RESERVE. This error message can also result from certain commands trying to use data from a specific memory bank automatically, such as SAMPLAY.

Bank not reserved (36)

Bordered windows not on edge of screen (59)

You are not allowed to position a window at the edge of a screen, but must leave at least eight pixels between them, to allow space for the border.

Break detected (159)

The device you are communicating with has aborted the present serial operation.

Buffer overflow (156)

The SERIAL SEND or SERIAL INPUT commands have run out of buffer space. Increase the amount of memory with SERIAL BUFFER and try again.

Cannot load med.library (187)

You've tried to use the MED PLAYER commands without installing the med.library file in the LIBS folder of your current start-up disc. A copy can be found on the AMOSPro System disc.

Cannot open Arexx port (195)

You've tried to open a busy AREXX port with AREXX OPEN. Check that you've entered it in the correct format. The name should be in UPPER CASE. You should find a usable port with the =AREXX EXIST function.

Cannot open Arexx port (195)

Can't fit picture in current screen (32)

You have tried to use LOAD I FF to load a picture into an existing screen of a different type. AMOS Professional will automatically create a screen of the right type if you specify a screen number in the correct range of 0 to 7.

You should tag the number of the destination screen to the LOAD IFF command like this:

Load Iff "filename", number

Can't open narrator (185)

AMOS Professional is unable to find "narrator.device" in the current "devs:" directory, so the narrator program cannot be loaded.

Can't resume to a label (4)

You cannot use RESUME label inside an error procedure.

Can't resume to a label (4)

You cannot use RESUME label inside an error procedure.

Can't resume to a label (4)

You cannot use RESUME label inside an error procedure.

Can't resume to a label (4)

You cannot use RESUME label inside an error procedure.

Copper not disabled (76)

You are not allowed to use the COP MOVE or COP SWAP commands before disabling the normal copper list with COPPER OFF.

Device already opened (140)

You've tried to open the same device twice. The PRINTER and PARALLEL devices can only be opened once in any particular session. If you're using multi-tasking, check that another application hasn't grabbed the device first. If so, you'll have to quit from the application before running your AMOS program.

Device already opened (140)

Device error (144)

A device has reported a device specific error. AMOS Professional cannot keep all possible errors in memory so check with Commodore documentation for the correct error meaning.

Device error (144)

A device has reported a device specific error. AMOS Professional cannot keep all possible errors in memory so check with Commodore documentation for the correct error meaning.

Dir$="Df0:"

Device error (144)

A device has reported a device specific error. AMOS Professional cannot keep all possible errors in memory so check with Commodore documentation for the correct error meaning.

Directory not empty (85)

You can only erase directories when all the files held within them have been deleted by the KILL command.

Directory not empty (85)

You can only erase directories when all the files held within them have been deleted by the KILL command.

Disc error (101)

There's a problem with a disc you're trying to access from one of your disc operations, or with the AMOS Professional file selector. Try removing the disc and re-inserting it. This clears up most problems. If you still can't get the disc to work after a couple of attempts, there may be a problem with your disc. You may need to use the DISCDOCTOR program on your Workbench disc. DISCDOCTOR should only be used as a last resort, but it's quite good at salvaging dead discs.

Disc full (88)

There is not enough space on your current disc to hold your data.

Disc full (88)

There is not enough space on your current disc to hold your data.

Disc full (88)

There is not enough space on your current disc to hold your data.

Division by zero (20)

You are trying to divide a number by zero, and this is impossible.

Division by zero (20)

You are trying to divide a number by zero, and this is impossible.

Division by zero (20)

You are trying to divide a number by zero, and this is impossible.

Error not resumed (3)

You have come out of an error-handling routine, but forgotten to reset the error using RESUME.

Error procedure must RESUME to end (8)

You may not exit from an error-handling procedure using END PROC. Use one of the special RESUME commands instead.

Error procedure must RESUME to end (8)

You may not exit from an error-handling procedure using END PROC. Use one of the special RESUME commands instead.

Error procedure must RESUME to end (8)

You may not exit from an error-handling procedure using END PROC. Use one of the special RESUME commands instead.

File format not recognised (95)

The LOAD command can only be used to load AMOS Professional program and bank files from disc. Use BLOAD for files stored in standard Amiga format. Use LOAD IFF for Iff screens.

File format not recognised (95)

The LOAD command can only be used to load AMOS Professional program and bank files from disc. Use BLOAD for files stored in standard Amiga format. Use LOAD IFF for Iff screens.

File is protected against reading (91)

You have requested a file that has been protected from unauthorised examination. The PROTECT command is available from the CLI or Workbench, and is explained in the Amiga User's Guide that you ignored when you unpacked your computer!

File is protected against reading (91)

File not found (81)

You have tried to call up a file or directory that does not exist.

File not found (81)

You have tried to call up a file or directory that does not exist.

File not found (81)

You have tried to call up a file or directory that does not exist.

File not found (81)

You have tried to call up a file or directory that does not exist.

Font not available (44)

SET FONT couldn't find the font number you've specified in the instruction. These fonts should be available from the FONTS: directory of your current start-up disc.

Font not available (44)

SET FONT couldn't find the font number you've specified in the instruction. These fonts should be available from the FONTS: directory of your current start-up disc.

Hardware data overrun (150)

This error can be generated if you wait too long before loading your data from the serial port using SERIAL INPUTS. If there's too much waiting in the wings the serial port can be overloaded, and the system collapses. Possible solutions include reducing the transfer rate with SERIAL SPEED, or reading the information a character at a time with SERIAL GET.

I/O error (94)

The Input/Output error message implies that there is a corrupted file that cannot be accessed properly. Try again, checking any disc drive connections. If necessary, you may have to resort to the DISC DOCTOR program, supplied on your original Workbench disc.

I/O error (94)

Invalid baud rate (147)

The SERIAL SPEED command only permits you to set the speed to certain values. If the current serial device doesn't support your value, you'll get this error.

Invalid baud rate (147)

The SERIAL SPEED command only permits you to set the speed to certain values. If the current serial device doesn't support your value, you'll get this error.

Invalid baud rate (147)

The SERIAL SPEED command only permits you to set the speed to certain values. If the current serial device doesn't support your value, you'll get this error.

Illegal direct mode (17)

Direct mode only permits you to run certain types of instructions from the command line. All program control instructions such as FOR. .NEXT, IF. .THEN, GOSUB, and GOTO are forbidden. In addition, you are NOT allowed to call any AMOS Professional procedures from direct mode.

Illegal file name (82)

You are trying to use a non-standard file name.

Illegal file name (82)

You are trying to use a non-standard file name.

Illegal file name (82)

You are trying to use a non-standard file name.

Illegal number of colours (49)

You are trying to use the wrong number of colours on screen at once. Check the syntax of your SCREEN OPEN commands, or check this User Guide for a full list of available screen colour options.

Illegal number of colours (49)

You are trying to use the wrong number of colours on screen at once. Check the syntax of your SCREEN OPEN commands, or check this User Guide for a full list of available screen colour options.

Illegal number of colours (49)

You are trying to use the wrong number of colours on screen at once. Check the syntax of your SCREEN OPEN commands, or check this User Guide for a full list of available screen colour options.

Illegal user function call (16)

You've made an error in either a user defined function, as created by the DEF FN command. The most likely mistake is that you've entered the wrong number of variables in your FN statement.

Illegal user function call (16)

You've made an error in either a user defined function, as created by the DEF FN command. The most likely mistake is that you've entered the wrong number of variables in your FN statement.

Illegal user function call (16)

You've made an error in either a user defined function, as created by the DEF FN command. The most likely mistake is that you've entered the wrong number of variables in your FN statement.

Illegal user function call (16)

You've made an error in either a user defined function, as created by the DEF FN command. The most likely mistake is that you've entered the wrong number of variables in your FN statement.

Interface Error: Bad syntax (120)

There's a syntax or typing error in one of your AMOS Interface programs. Use the EDIALOG function to find the position of your error in the command string.

Interface Error: Bad syntax (120)

There's a syntax or typing error in one of your AMOS Interface programs. Use the EDIALOG function to find the position of your error in the command string.

Interface Error: Channel not defined (125)

There's a problem with a DIALOG RUN command in your program. The channel number you've attempted to execute does not exist. It needs to have been previously assigned to an AMOS Interface command sequence with a call to DIALOG OPEN.

Interface Error: Illegal function call (128)

You've entered the wrong sort of values in one of your AMOS INTERFACE commands. Use EDIALOG to find the offending command. A full list of all the parameter options can be found directly from the HELP menu.

Interface Error: Illegal number of parameters (131)

You've typed too few, or too many values into one of your AMOS Interface functions. Use EDIALOG to located the mistake, and the AMOS HELP menu to find the correct number of parameters for your instruction.

Interface Error: Illegal number of parameters (131)

Interface Error: Label not defined (123)

A JUmp or JS command has been entered in your AMOS Interface program with a non-existent label number. Labels are defined using the LA command. Unlike AMOS Professional or AMAL, you're only allowed to use numbers from 1 to 65536. Names are not permitted.

Interface Error: Screen modified (126)

After an Interface channel has been opened to a particular screen, the screen has been altered or closed. Interface stores information about the screen from the start, so you must keep the screen in the same format.

Interface Error: Type mismatch (129)

One of the values in an Interface function is of the wrong type. If you're using a variable, check that it contains the right sort of data. An Interface variable can be used to store both strings or numbers. So it's easy to get confused.

Interface Error: Variable not defined (127)

You've called the VA function with a no existent variable number. Permissible numbers range from 0 to 65535. However, the system defaults to just 17. You can increase this limit with a simple option from the DIALOG OPEN command.

Interface Error: Variable not defined (127)

Label already defined in animation string (114)

Two versions of the same label definition have been discovered in an AMAL program. All labels must consist of a single upper case letter.

Label already defined in animation string (114)

Two versions of the same label definition have been discovered in an AMAL program. All labels must consist of a single upper case letter.

Label not defined in animation string (109)

You are attempting to jump to a non-existent label in an AMAL animation string.

Library already opened (168)

You've tried to open the same library twice with LIB OPEN.

Library not opened (169)

LIB CALL has been used with a non-existent channel number. You'll need to open this channel first using LIB OPEN.

Menu item not defined (39)

The item specified in a MENU command has not been previously defined using MENU$.

Menu item not defined (39)

The item specified in a MENU command has not been previously defined using MENU$.

Menu item not defined (39)

The item specified in a MENU command has not been previously defined using MENU$.

Menu item not defined (39)

The item specified in a MENU command has not been previously defined using MENU$.

Next without For in animation string (108)

In an AMAL animation string, each Next command must be associated with a single For statement. Also check the upper and lower case of any comments in your AMAL program.

No data set ready (157)

A strange error message generated by Commodore's Serial device. We think it may happen when the serial device just cannot handle the incoming data. Let us know if you know better!

No ON ERROR PROC before this instruction (5)

You can only use RESUME LABEL after an ON ERROR PROC command.

No ON ERROR PROC before this instruction (5)

You can only use RESUME LABEL after an ON ERROR PROC command.

No disc in drive (93)

Your Amiga does not believe that there is a disc in the drive you want to access. Try again.

No disc in drive (93)

Your Amiga does not believe that there is a disc in the drive you want to access. Try again.

No disc in drive (93)

Your Amiga does not believe that there is a disc in the drive you want to access. Try again.

No zones defined (73)

This is an error generated by the RESET ZONE command. RESET ZONE erases all the zone definitions you've created using SET ZONE. It can only be called after you've reserved some memory for your zones with RESERVE ZONE.

No zones defined (73)

Not an AmigaDOS disc (92)

AMOS Professional can only read discs created on an Amiga. If you want to use discs that are of compatible size but originate from another sort of computer, you will first have to use specialised software to translate the data.

Not a med module (189)

The MED LOAD command is only capable of loading music modules which are compatible with the MED music format. So check that the music is in the correct format.

Not a packed bitmap (200)

You have attempted to unpack a data bank which is not in bitmap format.

Not a packed bitmap (200)

You have attempted to unpack a data bank which is not in bitmap format.

Not a packed bitmap (200)

You have attempted to unpack a data bank which is not in bitmap format.

Out of data (33)

You may have left out some information from one of your DATA lines, because a READ command has gone past the last item of data in the current program. Alternatively, there may be a typing error in a RESTORE command.

Out of data (33)

Out of memory (24)

Your Amiga thinks that it has run out of available memory storage space. If the information line assures you that there is plenty of spare memory, simply save your program, re-boot and load the program back in. There are commands which will free up memory when you start reaching the Amiga's limits. These are: CLOSE EDITOR, KILL EDITOR and CLOSE WORKBENCH.

Out of memory (parallel device 172), (printer device 166), ( serial device 148)

If a device requires memory and finds that there's no more left, one of the above will be reported back. Try adding the CLOSE WORKBENCH or CLOSE EDITOR commands at the start of your program to free up some additional memory.

Out of stack space (0)

There are too many procedure calls nested inside one another. Although AMOS Professional procedures can call themselves up, this error may be reported after about 50 loops. The same can happen with the GOSUB command. See the SET STACK command if you need to extend this limit.

Out of stack space (0)

Overflow (29)

The result of a calculation has exceeded the maximum size of a variable.

Overflow (29)

The result of a calculation has exceeded the maximum size of a variable.

Parallel device already used (171)

The PARALLEL OPEN command can only be used ONCE in your program. If you've already opened the printer port with PRINTER OPEN, the parallel device may not be available for your use. Alternatively, if your Amiga has several of these parallel ports you might need to access the devices directly using the DEV OPEN command.

Parallel initialisation error (177)

The parallel device has refused to open probably because another program is using it.

Parallel line error (174)

The PARALLEL SEND, PARALLEL INPUT$ or PRINTER SEND commands have been unable to access the parallel port. Check than the cables are plugged firmly into the connectors, and try again.

Parallel line error (174)

The PARALLEL SEND, PARALLEL INPUT$ or PRINTER SEND commands have been unable to access the parallel port. Check than the cables are plugged firmly into the connectors, and try again.

Parallel line error (174)

The PARALLEL SEND, PARALLEL INPUT$ or PRINTER SEND commands have been unable to access the parallel port. Check than the cables are plugged firmly into the connectors, and try again.

Printer cannot output graphics (162)

The PRINTER DUMP command can only dump your screens onto printers which support some sort of graphics mode. This applies to the vast majority of printers currently on the market, and includes ANY normal dot-matrix or laser printer. However, if you're using a daisy wheel printer, you'll be unable to make use of this feature. Sorry!

RETURN without GOSUB (1)

RETURN can only be used to exit from a subroutine that was originally entered with a GOSUB.

Rainbow not defined (75)

You must define your rainbow effect using SET RAINBOW before you can call it up.

Rainbow not defined (75)

You must define your rainbow effect using SET RAINBOW before you can call it up.

Resume without error (7)

The RESUME command cannot be executed unless an error has been discovered in your program.

Resume without error (7)

The RESUME command cannot be executed unless an error has been discovered in your program.

Resume without error (7)

The RESUME command cannot be executed unless an error has been discovered in your program.

Resume without error (7)

The RESUME command cannot be executed unless an error has been discovered in your program.

Screen not in dual playfield mode (71)

You may only use DUAL PRIORITY after creating a dual playfield.

Screen not opened (47)

You must open a screen with the SCREEN OPEN command before it can be accessed.

Screens can't be ANIMated (67)

AMAL can only move or scroll screens. It is impossible to animate screens using the built in Anim command.

Scrolling zone not defined (72)

Before using the SCROLL command, the direction and size of the scrolling area must be defined with SET SCROLL.

Selected unit already in use (160)

The unit number can be specified for Serial communications and this error will occur if the requested unit is in use. You'll need to have a special multi-serial board though!

Selected unit already in use (160)

The unit number can be specified for Serial communications and this error will occur if the requested unit is in use. You'll need to have a special multi-serial board though!

Selected unit already in use (160)

The unit number can be specified for Serial communications and this error will occur if the requested unit is in use. You'll need to have a special multi-serial board though!

Selected unit already in use (160)

The unit number can be specified for Serial communications and this error will occur if the requested unit is in use. You'll need to have a special multi-serial board though!

String too long (21)

AMOS Professional allows a maximum of 65000 characters in any string.

Syntax error in animation string (107)

There is an error in the animation sequence specified by an Anim command. Check for typing errors, especially for full stops instead of commas.

Text window 0 can't be closed (62)

The WIND CLOSE command can only close windows which have been defined using WIND OPEN. So it won't close the original text window.

This window has no border (63)

A BORDER command has been used on a window which has no border.

Time-out error (155)

The SERIAL INPUTS command or SERIAL GET command have waited in vain for information over the serial channel. They've finally aborted with an error. Check that everything is connected correctly, and that the other end of the communications line is actually sending you some data. This time-out limit can be set from the Workbench Preferences.

Time-out error (155)

A$=23 : B="A string into an integer?"

User cancelled request (161)

The printer was not available to the printer device, a system requester appeared and you clicked on Cancel and then this error occurred.

User function not defined (15)

There's a problem with a user defined function created with DEF FN. AMOS can't find the function you are referring to. Check that you've defined your function earlier in your program with DEF FN. This line must occur BEFORE your FN function actually appears in the listing! You can't create your function as part of a procedure, or a subroutine.

Valid screen numbers range from 0 to 7 (50)

There is a maximum of eight screens that can be opened at any one time.

Wave 0 and 1 are reserved (182)

Waves 0 and 1 are automatically reserved for white noise and pure tones respectively. So you can't redefine them using the SET WAVE command.

Window already opened (55)

It is impossible to open a window that is already open.

Window already opened (55)

It is impossible to open a window that is already open.

Window already opened (55)

It is impossible to open a window that is already open.

Window too small (56)

The requested window is smaller than the minimum permitted size. Please see WIND OPEN and WIND SIZE for a full explanation.