Pegasus Graphics Universe 1

home *** CD-ROM | disk | FTP | other *** search

/ Pegasus Graphics Universe 1 / Pegasus_Graphics_Universe.iso / p11 / system / help / errors.doc < prev next >

Wrap

Text File | 1992-10-15 | 59.2 KB | 1,291 lines

ERROR CODE DESCRIPTIONS FOR: VERSION 7.32 (October 15th, 1992) OF P11 A GRAPHICS PROGRAM WRITTEN BY: RUSSELL D. HOFFMAN P.O. Box 188006 CARLSBAD, CA 92009 (800) 551-2726 (619) 720-7261 America Online:RUSSELL DH CompuServe:70743,1226 THE AUTHOR ASSUMES NO RESPONSIBILITIES AS TO THE APPLICABILITY OF THIS PROGRAM TO YOUR NEEDS OR THE ACCURACY OF ITS FUNCTIONS. PLEASE NOTIFY THE AUTHOR OF ANY INACCURACIES FOUND AND OF ANY DESIRED NEW FEATURES. CONCEIVED, DESIGNED, WRITTEN AND PRODUCED BY RUSSELL D. HOFFMAN IN THE UNITED STATES OF AMERICA. PROGRAM COPYRIGHT (c) 1984 to 1992, DOCUMENTATION COPYRIGHT (c) 1985 to 1992 by RUSSELL D. HOFFMAN. ALL WORLDWIDE RIGHTS RESERVED. This error code descriptions list is for P11.EXE, P11RUN.EXE, SHOWER.EXE, SCRNSAVE.COM, SHOW_PCX.EXE, and HPRASTER.EXE, all from THE ANIMATED SOFTWARE COMPANY. Not all codes apply to all programs. This document is intended mainly to aid users of the P11 authoring system, but may be needed by others who use applications created with our products. This document may be freely distributed in electronic or printed or any other form. There are hundreds of error codes for quick elimination of problems. Some error codes reflect possible programming errors in the product; they are listed here for completeness but should never come up. If they do some of them suggest a reboot. Please contact THE ANIMATED SOFTWARE COMPANY if you get any such errors. If an error comes up that is not listed it is probably a documentation error and indicates some problem that can be worked around. Again, PLEASE contact us if this occurs! YOUR HELP IS APPRECIATED! In normal editing/creating/testing, you will probably get many errors. Text processing can SOMETIMES be continued by simply correcting the line in error and restarting the program from the current location. This will not always be entirely correct. For example, all nesting within \IF and \CALL statements will be lost and variable "B" will be zero. All sprint frames will be lost and all sprite values reset. \ON KEY specifications will be voided. Still, you might use this option during testing. When you run a text file from the beginning of the file within the editor all current colors, text speeds, wait limits, scaling values (for \DRAW), the current text location, and so on are reset. It is best to set these values as you want them for each text file rather than to rely on defaults. Most text files will be called by other text files which will have set these values themselves. In a few instances errors will cause automatic deletion of the current frame. These error codes should only occur if the picture/font file that was read in was already damaged. It should NOT happen during regular processing. Unless you have issued \ON ERROR any error stops processing of a text or macro file. If you were using the picture editor you will return to drawing mode. Remember, any syntax error could, somehow, generate very misleading errors. Always review the proper syntax (in the manual and other help facilities) when the error code does not seem to make any sense. When you give up, call us! When an error occurs the following message will be displayed near the bottom of the screen: *** CAN'T PROCEED! *** ERROR #: # LINE: # OFFSET: # Press F1... In the editor, the line # and offset # are only displayed if the error occurred while running a text file. Any print, data, or disk-based animation file that was open will be automatically closed. You will be placed on the line where processing stopped. Usually this is the line where the error is, but not always (explained below.) <F9> will probably put you near the actual point of error. With <F2> you can display the last two (2) errors. Sometimes an error in one part of a text file will cause processing to halt later on. In this case you will have to figure out the problem "logically". Take for example, creating a sprite that is supposed to track another image. If the path is NOT a vector image this is an error, but it will not be discovered until \SPRINT assigns a frame to track the image. The real error would be the \SPRITE PATH= command and option. When possible, this guide offers suggestions about these things. Occasionally multiple errors will occur before processing stops. This may happen because one error causes subsequent parts of the same command to fail. Note the error codes and their sequence: it may be an aid in debugging the problem. Error codes chime out the code in tones. (Or rather, BEEP the code in time.) The # is in sharps starting at Lower C Sharp (leading zero's included--total five tones.) Two special key codes are used by THE ANIMATED SOFTWARE COMPANY for debugging internal P11 problems, but you may find a use for them yourself, especially Alt-123: Alt-147 (Hold the alt key and press 1, 4, 7 on the numeric keypad) will display the CPU registers as close to the time of the error as possible. This is of little or no use to you unless you expect to be contact us about the error. Alt-123 (Hold the alt key and press 1, 2, 3 on the numeric keypad) will display the names of the current files the program is using. ERROR CODE LISTING: 0001: Command error while in "instant" mode. Some commands are not allowed in this mode, including \READ, \JUMP, \CALL and others. See documentation on F10, instant commands, for more information. 0002: \RETURN encountered without a corresponding \CALL having occurred. \CALL's and \RETURNs should have a one-to-one relationship with the first \RETURN being matched with the last \CALL, the next \RETURN with the next- to-last \CALL, etc. Note that \ON commands eliminate \CALL nesting. 0003: \CALL's and \CALLM's nested more than thirty- two (32) deep. Often this error occurs because a \JUMP somewhere causes a \CALL to be repeated without it's corresponding \RETURN being used. 0004: \CALL, \CALLM, \JUMP or \ON cannot find the \X paragraph name that is specified in the command. The names must be EXACTLY the same including case. Coding in all upper-case is preferred. This error cannot be overridden with \ON ERROR. 0005: The program will not read in a new text file if changes exist to the current one in RAM. Save the file and rerun, or read in the new text file manually using function key 6. 0007: Same as 5 above but for picture files in RAM, EMM, or on disk if doing disk-based editing. The program will not read in a new picture file if changes exist to the current one being edited 0011: \READ. File not found on the current disk or unable to open for some other reason. 0012: A failure occurred during a read of a file. You probably also got an error that was more specific just prior to this one. 0020: There was a failure to open an aux file prior to writing it. This would be a DOS error such as: Invalid name, no room in the directory, hardware failure, etc. Try a different diskette, drive, etc. 0021: There was a failure when writing an aux file. Similar to error 20 above but for a close. In this case the aux file is probably closed not any good and may not be readable. You should be able to write it out again to a different media. The disk directory may be damaged if you get this error, so it would be a good idea to run the DOS function CHKDSK on the disk used after this error, when you return to DOS. This error may be called by bad sectors and other hardware problems. 0022: DOS could not close an aux file after a write. Disk is probably damaged. See error 21 for additional information. 0023: Invalid auxbox specification. Possibly you have created too many and used up the space available for auxboxes. 0024: Auxbox storage area error. You should not be able to get this error at all. 0025: Auxbox error. Can't fit a new or enlarged auxbox because the aux area is full. You can eliminate unused boxes with \ELIMINATE to make more room. 0026: Trying to store data in the TIME&DATE auxbox (#32767). This is not allowed. #32767 is a "read only" auxbox--you cannot write to it. 0027: Trying to store data in auxbox zero (0). The first box is #1. 0029: TIME&DATE auxbox not valid. You probably read in an invalid aux file. If not this may be a programming error. 0031: \WRITE NNNNNNNN.AUX error. The full auxfile was NOT written. (Note: This was ignored as an error prior to version 7.) 0048: A macro file has "run out". The last statement was executed and nothing followed it. The last statement in a text or macro file should be either \READ (a text file), \RETURN, \JUMP or \END. All other statements will cause this error if processing gets past them in the macro area. 0049: Same as 48 above but you were in a text file. 0050: Command word was not recognized. Probably misspelled or not capitalized. 0060: \+ command not the last command on the line. 0061: \+ cannot be the first command on a line. It cannot immediately follow a \CALL or \CALLM command on the same line, but if another command comes between them, that's okay. 0071: Missing close parenthesis in a math equation. An uneven number of parenthesis could produce this too. 0072: Extra close parenthesis in a math statement. More information about parenthesis can be found in error 71 above, and in the section on commands and syntax. 0073: \SHOW. Top frame is greater than the number of frames in the picture area. 0074: DOS reports "access denied" error during an attempt to read or write to a disk. 0075: \READ. Extension not valid. Program can only read certain types of files, whose extensions are AUX, DAT, FON, HUE, MAC, PIC or TXT. 0076: DOS returned an "invalid handle" error code during an attempt to read or write to disk. This means it doesn't "know" about the file the program is requesting activity with. May indicate a programming error in this program. 0077: DOS returned an unspecified error code when reading or writing to a disk (see error codes 74 and 76 for valid DOS error codes). 0078: DOS did not write all the bytes for a font, hue, text or auxiliary file. Try saving to another disk--the file has NOT been saved properly. 0101: More than 32 nested \IF statements. Remember to code \ENDIF statements to end nesting of \IF statements. 0104: A paragraph name while in the midst of an \IF statement (paragraphs are named with the \X command). End the \IF statement first with \ENDIF. 0110: A command looks sort of like \END or \ELSE or \ENDIF but is none of these. Probably a syntax or spelling error of some sort. 0111: \ELSE encountered while not in an IF-THEN-ELSE statement. You are only "in" the statement while within the sequential area of text-- \CALL's effectively exit the statement until they \RETURN to the line under the \CALL. 0112: Unmated \ELSE statement. \ELSE must follow an \IF (after any \THEN statements). It can immediately follow the \IF statement, in which case \THEN processing would drop down to the \ENDIF statement. It may be left off in which case \ELSE processing (\IF evaluated as FALSE) would simply skip to \ENDIF. 0113: \ELSE more than 32 deep. You should not be able to get this error because you will get either 101 or 112 first. 0114: Unmatched \ENDIF statement (\ENDIF encountered while not inside an \IF statement). 0121: \IF operator(s) not >, = or < (greater than, equal or less than). 0122: "AND" or "OR" not spelled correctly in an \IF statement. 0124: Attempt to compare apples to oranges. Both sides of each operator in an \IF statement must be either numeric or alphanumeric (except a single ASCII character in quotes can be compared to a number.) 0201: DOS command (F10 twice). Invalid option letter. 0221: \QUESTION command specifies a length for the question greater than 80 characters. The maximum is 80. 0231: Invalid auxbox name. The only legitimate characters are capital letters, numbers, the ampersand (&) and the underscore (_). The name must begin with three letters, end with a letter, and be at least three characters long. You can also get this error if you try to move an alphanumeric auxbox to a variable. 0232: Auxbox destination # connot be 0 or invalid. (Same as error 27 but caught in a different way.) 0303: DOS rename command. DOS was not able to perform the rename operation. Perhaps the name(s) are invalid or the file does not exist on the named drive. 0304: DOS returned an error during attempt to rename a file to *.BAK. 0310: \ON error. Second command word not KEY or ERROR. See \ON KEY or \ON ERROR for proper syntax. 0313: \ON KEY error. Paragraph name must be capitalized. 0315: \ON KEY programming error. You should never get this error. 0316: \ON KEY reset programming error. You should never get this error. 0317: Too many (more than 15) individual \ON KEY keys specified (besides global and the function keys). Turn some of them off. (See \ON KEY.) 0318: \ON KEY function key value must be 1 thru 10 inclusive. 0319: \ON KEY error. This key code represents a function key and must be coded as such (F1, F2, etc., NOT a number). 0400: DOS error trying to delete a file. Perhaps the name is wrong or the disk is bad. 0441: Missing " TO " as in \ADD # TO # or \MOVE # TO #. The word " TO " must be in capitals and have at least one space on either side of it. 0443: Missing equals (=) sign. The equals sign does not need to have spaces around it, but can if you want. 0500: Drive specification invalid. Must be 1, 2, 3 etc. 0525: You tried to save a picture element in memory using the SAVE option of \SHOW but changes exist to the current picture file. To use this option the file must be unchanged. Save the file to disk first or read in a new one. This check is to prevent you from accidentally overlaying new artwork. 0566: \WAIT RETURN # "NNNNN". The phrase inside the quote marks is more than 78 characters. 0587: \PASSWORD. TIME= value must be at least 117. 0588: \PASSWORD. Auxbox is not an alphanumeric literal. 0589: \PASSWORD. Parameter not recognized. 0702: \MULTIPLY syntax error. This follows a more specific error. 0750: \ADD syntax error. This follows a more specific error. 0760: " FROM " incorrectly spelled or missing in \SUBTRACT statement. FROM must have at least one space on either side of it and be all capitals. 0761: Attempt to divide by zero. You can't divide by zero and neither can the program. 0763: \DIVIDE syntax error. The BY portion of the command not spelled right or not separated by spaces. 0770: Intermediate result in a math calculation contains a divide by zero. Dividing by zero is impossible. You have to be sure your calculations won't do that. 0779: Attempt to put a literal (alphanumeric) into a variable. You can only do this with a single ASCII character in single or double quotes. The numeric value of that character will be put in the variable in that case. 0780: Error in the "TO" part of a \MOVE statement. The receiving area is invalid for some reason, perhaps for the type of move you are doing, or perhaps you are using a symbolic name for an auxbox, and the box has not been \NAMEd yet. 0792: DOS failed in writing a print record. This program actually writes print records only when 512 bytes of print data (including all cr/lf's (carriage return/line feeds)) are accumulated. Perhaps the diskette is faulty or removed. 0885: DOS returned an error during a read of a file. 0887: Too many macro names. Macro names are stored so that the program will not automatically reread macros it has already read. Although you can read as many macros as will fit in the macro area you can only store nine (9) names. Use \DELETE to remove extra names. 0892: Nothing read (file on disk is empty). 0893: Programming error during read of a file (FON, AUX, MAC or TXT only). This error should never occur. 0896: File size larger than specified, or just too large for the program too handle. Possibly the file is damaged. Possibly, you have set the maximum picture size down with the P11FLAGS= environment parameters or startup command variables, or the default size is too small for the image you are trying to read. 0897: Unrecoverable critical error occurred during a \READ. 0899: Programming error after reading in a macro that was too big. You should not be able to get this error. 0900: Attempt to do math with an operand that is not numeric. You are using an auxbox that is non-existent or non-numeric. 0902: Math evaluation error. A "destination" cannot be a math expression. It must be an auxbox or variable. 0904: Math evaluation error inside brackets when using a partial alphanumeric auxbox. The numbers inside the brackets can be other auxboxes, or variables, or numeric literals. 0905: Attempt to \CONVERT an auxbox that does not exist or an attempt to \CONVERT the TIME&DATE auxbox, #32767. 0906: Attempt to use an auxbox that does not exist. 0907: Same as 902 above but specifically during \ADD. 0912: Rotate of a frame. Raster frames can only be rotated by 90-degree or 180-degree amounts. 0914: \ROTATE. Unrecognized parameter. Check spelling or refer to command for valid options. 0916: \ROTATE. You cannot execute this command if changes exist to the picture file. Save the file to disk first. 0917: Location specified in \ROTATE is out of range. Must be from -2000 to +2000 inclusive on each axis. 0918: \ROTATE FRAME=#. The frame specified must be a vector frame in version 6.00. 0919: \ROTATE. Angle not 0 to 90 degrees, inclusive. 0920: Radius too great in \CIRCLE. The largest value on either axis is 2000. 0928: Unrecognized parameter in \CIRCLE. 0933: Tried to display the zero (0) auxbox, or a negative auxbox. The first auxbox is #1. 0953: An error occured getting memory to save a raster temporary rectangle. (You probably got an Out Of Memory error first.) 0954: When saving screen boxes with the "R" option in the picture editor the points must form a box. If you try to save a single dot you will get this error. 0956: Divide error. The dividend cannot be more that 32K times the divisor or less than 1/32K of it. Intermediate calculations are signed 31 bit values so this error is possible during math evaluation. 0980: I/O error on printer. Operation halted. (Printer is not ready.) (If you use Alt- 147, you can see that the LPT# (0,1,2) is in DX and AX has DOS STATES code.) 1199: You cannot execute disk-based animation or \LOAD-based animation while doing disk-based editing. 1221: \CLOCK invalid parameter, or speed option number not valid. Must be from 1 to 6. (Default is 5.) 1443: SCRNSAVE only. Error writing picture header. File is bad, or directory \P11\TEMP does not exist on the specified drive. 1444: SCRNSAVE only. Could not open a filename. Perhaps it already exists. You may try again, it will try the next name/number combination. 1445: SCRNSAVE only. Error creating the file for a screen save. You may try again if you like. 1454: SCRNSAVE only. HUES error. Same as 1444. 1455: SCRNSAVE only. HUES error. Same as 1445. 1615: \BUILD. Trying to create too big an auxbox (maximum is 82 bytes). 1616: A number in the text file is >32767 or <-32768. 1874: Mirror option of draw mode. The number of mirror images must be 0 or 1 (which both mean none) or 2, or 4. If two then you must choose H (horizontal) or V (vertical). 1986: Maximum auxbox number is 32767 (which is TIME&DATE). 0 or below and 32768 or above are not allowed. 2001: Ran out of room for symbolic names for auxboxes. Perhaps a shorter one than this would fit. You have slightly more than 1000 bytes for names. The program uses three bytes of that area plus the length of the name itself for each name. 2002: Symbolic name is more than 30 characters. Use a shorter name. 2003: Symbolic name is less than 3 characters long. Use a longer name. 2004: Invalid character in a symbolic name. Valid characters are capital letters, numbers, underscore (_) and ampersand (&). The first two and the last character must be letters. 2006: Symbolic naming error. The pound sign (#) must be used for the auxbox to be named. For example \NAME #43=SUCH_AND_SUCH is valid but \NAME 43=WHATEVER is not because "43" needs a # sign. 2007: Symbolic naming error. You attempted to use the same name for two different auxboxes or you attempted to give two names to the same auxbox. 2008: Symbolic naming error. Same as error 2007 above. 2010: Symbolic name error. There is no auxbox with this name. Establish the existence of the auxbox by, for example, moving a value to it. Naming an auxbox does NOT establish its existence. It is possible to get this error if you have a syntax error such as extra commas, etc. 2011: This named auxbox is not numeric but you are attempting to do math with it. 2112: DOS copy. The file you said to copy from does not exist on the current disk. 2113: DOS copy. DOS was unable to open the file you said to copy "to". (Files, whether new or pre-existing, are always opened before they are used. This is usually automatic in this program.) 2114: DOS copy. The copy "to" name was the same, on the same drive and path, as the copy "from" name. You can only copy to a different name! 2115: DOS copy. The copy "to" name contained question marks (?) or asterisks (*) in bad combinations. These are legitimate only if they fill the file name or the extension. (Example: *.??? is legal but *?.* is not.) 2116: DOS copy. Copy could not be written properly. Diskette may be full or bad. A partial file was possibly written and closed. 2117: DOS copy. The copy "to" file could not be closed properly. Possibly the diskette is bad. 2119: DOS copy. Could not properly read the input file. 2121: Not enough RAM to execute the COPY option of the F10 DOS functions. The program needs at least 4K free to copy files. 2122: After a DOS copy the program could not return memory to DOS pool. You shouldn't be able to get this error. 2123: Could not close the input file during a copy command. 2131: After a DOS copy the attempt to set the attribute to HIDDEN, SYSTEM, or READ ONLY failed. The file was copied successfully, but without the attribute. 2141: After a DOS rename the attempt to set the attribute to HIDDEN, SYSTEM, or READ ONLY failed. The file was renamed successfully, but without the attribute. 2552: No graphics interface picture exists for the picture editor icons for this screen mode, in the directory \P11. Copy P11MOD??.PIC from your P11 master disks to \P11\*.* on the drive you plan to edit from. It looks on the drive you edit in first, then it looks in the original drive. This error comes only after BOTH searches have failed to turn up the files. 2553: The graphics interface picture is not in the correct screen mode. File P11MOD??.PIC in \P11\ has been damaged or renamed. Reload your P11MOD??.PIC files to \P11 from your P11 master disks. 2624: Attempt to \DELETE frames from a picture file that has edit changes while running a text file. Save the picture file or manually read in a new one first. 2625: \DELETE FRAME error. The frame to delete is greater than the total number of frames in the picture file. 3000: \DELETE MACRO error. The name was not stored so it could not be deleted. 3002: \ROUNDS. Number of rounds cannot be zero. 3011: Frame to use for timing control is not vector, or there are no frames in RAM. 3012: Ran out of RAM, specifically during setting of a speed-control vector frame. When setting a vector frame as a speed control (see the SPEED option of the \ROUNDS command) the frame is copied into RAM if you are using EMM. 3421: "Merge" option of vector drawing mode. This frame is too small to merge (less than 3 dots). 3422: "Merge" option. This frame does not exist in the file (greater than the top frame). 3423: "Merge" option. Frame to be merged is not vector. 3424: "Scale" option in the picture editor cannot have "multiply" or "divide" values of zero, <0 or >255. 3513: During picture editing you refused to save edit changes in RAM, so P11 cannot use the temporary frame area to \APPEND pictures. 3514: \OPEN or \LOAD of a picture file in the wrong screen mode. The screen mode must match the mode of the picture file for disk-based animation. 3515: Frame headers are too small. You cannot do disk-based animation with fonts or proportional fonts. (Frame headers must be 16 bytes or more.) 3516: Read error during disk-based animation. Either the file was bad (cropped, perhaps) or bad data in the file. Did not read the number of bytes it expected based on file header information. 3517: Could not set disk pointers properly for a disk-based animation file read. Either the file has bad data or the disk is unreadable for some reason. 3518: Critical disk error occurred on a disk-based animation read. You should have gotten another error message before this one. 3527: DOS returned an error when trying to set the spot on the diskette to read from for \APPEND or \READ. File is probably damaged. 3532: Your last frame to \APPEND is missing or less than your first frame to append. 3534: DOS read error of an \APPEND or \READ picture file. 3535: See note below. Your header record is too small. 3536: See note below. Picture size is >64K. 3537: See note below. Dos returned an error code trying to read the file during \APPEND or \READ of a picture file. NOTE: These \APPEND and \READ errors generally indicate that the file is damaged. Possibly some frames can be appended, depending on the problem. 3539: \APPEND frame specifications missing or invalid (non-numeric, 0, etc.). 3542: \APPEND or \READ of a picture file. File is not valid, specifically the decimal point is missing from the file header release code. This should never occur because the release code is included in all picture files that are written out. File is bad. 3543: \APPEND or \READ of a picture file couldn't get enough RAM space from DOS. 3545: \ELIMINATE. Math evaluation error or you tried to eliminate the TIME&DATE auxbox (#32767), the zero (0) auxbox, or a negative auxbox. 3547: \APPEND. The top frame requested does not exist in the picture file named. 3548: \APPEND or \READ. The total number of frames would exceed the maximum allowed in a picture file if this command were executed. The maximum is over 8000, but may be set by the default (1000) or by the Environment or command-line startup parameters. 3551: \OPEN or \LOAD error. Same as 3548 above but for these commands. 3555: No room to \APPEND or \READ a picture file. You will probably also get an 8431 or similar memory error. 3562: Incompatible screen mode for this picture. Change screen mode first, then execute the picture file \APPEND or \READ. This error cannot be overridden with \ON ERROR. 3563: Same as 3562. This error cannot be overridden with \ON ERROR. 3564: Bad data in picture file or picture file too big You may get this error if the file is bad, or, if you have set the size to less than the maximum with the P11FLAGS= environment variable or the command-line startup parameters. 3568: Same as 3564, above. 3599: Same as 3564, above. 3583: \JOYSTICK. The first joystick command must be with the initialize option unless you have already initialized the joystick manually. 3585: Joystick is (probably) being inititalized at a 90 degree angle from where it should be. (Note: 180 degree (completely inverted) works.) 3609: /PATH/ parameter invalid: path name not valid or not found. 3639: \DELETE. The option word was not recognized. 3640: \BUILD. The string you are creating is too long (greater than 82 bytes). 3740: \CURSOR. You cannot place the cursor at the lowest, rightmost position on the screen or off the screen. 3742: \QUESTION error. You did not specify a place for the response to go. (A variable or auxbox.) 4004: \JUMP or \CALL within a macro or \CALLM to a macro cannot find the paragraph name in the macro area. Similar to error code 4 but for the macro area. This error cannot be overridden with \ON ERROR. 4204: \TEXT error. Unrecognized parameter. 4205: \TEXT PLANES=NNNNNNNN. Format is "binary" (1's and 0's) at least 1 must be a 1. (One of the first four if there are four planes.) 4206: \TEXT WIDTH= option. This option has not been implemented yet. 4303: \KEY. Code not valid. 4304: \KEY. The END= key value cannot be the return key, 7181. 4444: \X command. The paragraph name is greater than thirty-two (32) characters long. Use a shorter name. 4501: \ZING error. Only raster images can be \ZING'ed, not vector frames. 4503: \ZING error. You must specify a frame to zing with the FRAME=# option. 4508: \BUTTON number is less than zero (0) or greater than 7. 4519: Too many END= parameters in \MOUSE. Maximum is ten (10). These are cleared with \CLEAR MOUSE. 4521: \MOUSE. Invalid parameter keyword. 4522: \MOUSE initialization can only be done if the current files in RAM do not have changes to them. Either your TXT, PIC, or HUE file has edit changes. See \MOUSE and other documentation on I/O devices for why this precaution is necessary. 4523: \MOUSE WINDOWS= option. Values are no good. Be sure X-low <= (less than or equal to) X-high and Y-low <= Y-high 4524: \MOUSE FRAME= option. The picture frame requested cannot be greater than the number of frames in the file (Use zero (0) for no frame.) 4525: \MOUSE INITIALIZE option. Software for the mouse is definitely not installed yet, initialization is impossible. 4543: \SPRITE starting WPATH= dot cannot be zero. Must be one or greater. One (1) represents the first active dot (the second actual dot) of the vector image. 4553: \SPRITE starting PATH= dot cannot be zero. Must be one or greater. One (1) represents the first active dot (the second actual dot) of the vector image. 4554: \SPRITE STRING= error. Neither value can be zero. 4555: \SPRITE. Parameter not recognized. See \SPRITE for valid parameters and their syntax. 4556: \SPRITE WINDOWS= option. Window values not logical. Be sure X-low < X-high and Y-low < Y-high, and X-high < screen width and Y-high < screen height, and X-low >= 0 and Y-low >= 0. 4558: \SPRITE ZING=#,#,#. Frame to zing is not a raster image. 4653: \SHOW PATH= parameter. The starting dot cannot be 0. 4655: \SHOW. Parameter not recognized. 4656: \SHOW WINDOW= values are not valid. Be sure X-low is <= X-high and Y-low is <= Y-high. 4741: Copy function of a frame in the picture editor would exceed the maximum allowable number of frames during the operation (it uses one extra frame to perform the copy.) 4848: Program error calculating the width of a picture in words from the size you specified. You should not be able to get this error. 4849: Program error in setting the address for displaying a picture. You should not be able to get this error. 4876: \SPRINT. Too many sprites. (Greater than about 120.) 4879: \CLEAR SPRITE # option. Number too great. You can't have this many sprites, so you can't CLEAR this sprite. Maximum is about 120. 4894: \WIDTH. A width of 0 is not allowed. 4902: \HEIGHT value, when added to the \LOCATE value, goes off the screen (at the bottom). Error is only found when using \SCROLL. \OVERLAY resets itself. 4903: Text width too large. A full screen is the maximum text width, although this can wrap from the right edge to the left edge (it will be lower (two dots lower in CGA mode) and is not recommended.) 4904: Text width value is too small or too big. Number of dots too great or text width too big when font width is converted internally to screen dots. May be caused by a bad font in the font area or, if the file SHOULD fit, perhaps the current line width is too great. Set it to a smaller value with \WIDTH. You can also get this error if the # of dots is <2 bytes width (Example: 16 dots in mode 16.) 4905: Font height plus location would put part of the font off the screen at the bottom. 4907: Picture file has bad data in the file header. The file is probably bad or not in the program's format, or your P11FLAGS= C:# value may be < than when you wrote the file, and the frame won't fit. 4923: \SPRITE WPATH=. The first dot specified is greater than the number of dots in the drawing. 4924: \SPRITE WPATH=. Path must be vector. 4933: Starting dot for a PATH= tracking pattern is greater than the number of dots in the picture (not including the first and the last dots). 4934: Only vector drawings can be used as tracking patterns (paths). This error is not "caught" until \SPRINT creates sprite data for a frame. Go back to \SPRITE PATH= and set a vector frame for a path. 4944: Same as 4934 (above) but during \SHOW animation. Disk-based animation uses frames in RAM or EMM (not on disk) for paths. 5004: Height calculation invalid. You should not be able to get this error or any up to 5007 unless your file has been damaged or none has been read in. If the file is good they indicate a programming error during raster sprite animation. 5005: Height calculation invalid. See error code 5004. 5006: Width calculation invalid. See error code 5004. 5007: Offscreen width calculation error. See error code 5004. 5058: Math receiving field must not be an expression or number. It must be an auxbox or a variable. 5060: Math evaluation error. Operand not an auxbox, variable or number, or not capitalized. 5321: Math evaluation programming error. You should not be able to get this error. 5440: Can't save a macro file. Macro files are created as text files, and then the extension is renamed. 5853: An error occurred while trying to \SAVE the entire screen to disk, or during the save part of a \EXCHANGE SCREEN command. Disk may be full, or the path \P11\TEMP does not exist on the current drive. 5854: Similar to 5853, but during a \RESTORE SCREEN or the restore part of \EXCHANGE. Of course, since this only reads and does not write to the disk, this would not be caused by a disk full DOS error. 5870: \SCREEN LINE=#,#. #'s are invalid. The first must be 0 or greater, and the second must be greater or equal to the first and not greater than the number of screen lines for the current mode. 6000: Attempt to use an auxbox that does not exist. 6001: Attempt to do math with an auxbox that does not have a numeric value in it. Presumably it has alphanumeric data instead. 6002: Attempt to do math with an auxbox that does not exist. 6003: Attempt to do math with an auxbox that does not have a numeric value in it. Same as error 6001. 7121: Invalid value for \JRCOLOR. Five values may be listed, all must be between 0 and 15 inclusive. 7199: When displaying a raster picture the frame was too tall (too high on the Y-axis.) File is probably damaged. 7320: When displaying a raster picture the frame width was too wide. You should only be able to get this error if the file was bad. 7653: \CLEAR MACROS encountered within a macro. To do this here would clear the macro itself, so this command can only be executed from within a text file. 7654: \CLEAR. Invalid option. 7657: \CLEAR PICTURES command and option. This option isn't valid while you are editing a picture file. 7658: \CLEAR PICTURES command and option. When picture changes exist in the editor this option is NOT permitted, so that edit changes are not overwritten. 7709: Screen mode failure. You should have gotten another error before this one. It resets to the previous mode if this error occurs. 7715: EGA is not supported on this machine. 7716: You only have 64K video memory available and you are trying to go into mode 16 (EGA). Requires 128K Video RAM minimum. 7718: Screen mode not properly entered. After changing the screen mode it is "tested" with a call to the BIOS. It was NOT in the mode requested. Resets to previous mode. 7719: Screen mode invalid in either the \SCREEN command or in the P11 environment variable, or in the command-line startup parameters. 7726: You cannot change screen modes if editor changes to your HUE file exists. Save the whole hue file or read a full one in for the current mode. 7728: Screen mode changes to incompatible modes are not valid while changes exist to a picture file in the editor. 7729: Screen mode changes to incompatible modes are not valid while editing a picture file. 8017: Replacing a picture in RAM from the screen, the program could not find the proper place. You should not be able to get this error. 8106 A picture could not be returned to it's area in RAM or EMM because it would not fit. This represents an internal programming error and should not be able to occur. 8107: During a screen mode adjustment for a picture file, either the program could not find enough RAM for a screen mode change, or the maximum number of frames would be exceeded by this operation. The maximum number of frames is set by the F:# value in the environment variable or command-line startup paramters. Depending on what modes you go from and to, the picture size may change up or down The old area is not necessarily returned to DOS, depending on whether it is the only frame in the area (if it is, it can be returned to the available pool of RAM.) 8108 During a screen mode adjustmet for a picture file, could not get a work area from RAM to do the screen mode change. 8201: DOS returned an error code when an attempt was made to return memory used by pictures that have been deleted. Probably a programming error which should never occur. If editing, you should save your files (to temporary new names) and exit if you get this error. You probably will have to reboot. We suggest you do so anyway. 8344: \EXECUTE DOS> syntax error. After the command word (EXECUTE) you need at least one space and then either DOS> or just a > greater than) sign. The > is followed (in both cases) by the program to be executed or the command line (if any) to be passed to DOS. Check spelling/syntax. Or, maybe a command looks sort of like \EXEC but isn't. 8346: \EXECUTE error. The command line is too long (maximum 76 characters). 8348: \EXECUTE > error. You cannot execute batch files this way. Use \EXECUTE DOS> instead. 8351: \EXECUTE > error. Same as 8344 but not executing a second copy of DOS. 8352: \EXECUTE > error. The command to execute is missing. 8403: \APPEND or \OPEN error. Could not find the file. Perhaps it is not on the current drive. 8414: Error closing a print file (extension PRN) or data file (extension DAT). Can occur during \CLOSE or when exiting from a running text file. Also after some other error, since when an error occurs the program attempts to close any file which was left open. Indicates an error returned from DOS (perhaps the diskette was removed or damaged.) You probably should run the DOS function CHKDSK on the disk if this occurs. 8423: \OPEN of a print file failed. 8424: You issued a command to open a print file but a print file was already open. You can only have one print file open at a time. 8426: \OPEN with ADD option for updating an existing print file failed. Either the file does not exist, or some other DOS error occurred. 8428: \OPEN file extension not valid. Must be .PIC, .PRN, or .DAT. 8431: DOS would not give the program space for pictures. Possibly your space has become "fragmented", in which case writing out all of your picture files and then reading them in again may free up space. Otherwise, you have used up all available space. 8432: Same as 8431. 8434: Box too big to save (>64K dots.) 8435: Out of RAM memory during picture file memory acquisition operation. See the Guide and the Technical Reference for ways to reduce this program's RAM needs and/or to increase available RAM. 8436: Out of EMM memory (or at least out of the amount you allocated in your Environment parameter or startup command-line parameter.) Similar to 8431 but for EMM, not RAM. 8438: When reading in a font the expansion of the frame headers would create too big a file (greater than approximately 20K unless you set the font area to a different size in the Environment or command-line startup parameter.) Solution: Rename as a picture file and read in that way, then adjust to a smaller size. This error may also indicate the font frame headers are greater than the maximum permissible size which means the file is bad. 8440: \RESTORE of a screen is not valid because no screen has been saved. (Screens saved in a running tutorial are no longer saved while you are editing.) 8441: \EXCHANGE. You cannot exchange the active screen and the stored screen until you have issued \SAVE SCREEN so that a screen is stored. 8445: EMM memory usage error. EMM driver returned an error while mapping an EMM memory page, specifically after first trying to reuse EMM space and not finding enough pre-used space. You should not be able to get this error if all programs (including this one) are handling EMM correctly. 8476: Bad read of data in the \DATA command. The file is apparently bad. 8485: Bad picture or font file--Total frames is zero (0) so you can't use the draw mode yet. No action is necessary, the program will request that you name a file. 8502: Not enough space in the area assigned for this picture to return it there from the "work area" while drawing. This indicates a programming error and should never occur. 8503: Cannot find proper place to return this picture to it's RAM area. This is a programming error and should never occur. 8504: The picture has not had RAM space assigned to it yet. A programming error, this should never occur. 8507: The picture size is listed as zero, discovered while attempting to place the image in RAM. This is a programming error and should never a occur. 8512: DOS did not write a picture file properly. The error may have been due to the disk being full, but not necessarily. File is not properly saved yet. 8536: DOS indicated a bad close of a file. All files that are written out must be closed by DOS. Try to re-save the file, then exit and run the DOS CHKDSK utility. 8546: You attempted to close a .PRN print file or .DAT data file when none was open. 8547: \CLOSE syntax error. The EXT of the file to close was not valid. 8611: Could not find the COMSPEC= parameter in the environment during setup of \EXECUTE DOS>. This is a technical error that should never occur with a standard DOS. 8612: COMSPEC= parameter too long. Cannot process the \EXECUTE command. This error MIGHT be similar to error 8611, but not always. 80 bytes are allowed by DOS for the COMSPEC= parameter. 8664: You can't use the "Assembler type" command \OUT unless: 1) No changes exist to any files or pictures. 2) You have enabled "high level authority" (done with the \AUTHORITY command.) 8665: For byte \OUT commands, the value to be \OUTed must be 0 to 255. 8694: When specifying a frame for a pattern you chose one that is not a raster image. Must be raster to use as a pattern. 8720: \ACTIVATE SCREEN (<1) but no 2nd or 3rd (or more) screen is active. 8722: \ACTIVATE SCREEN is the only valid option in Version 6. 8723: Invalid compress amount during save of a file. You should not be able to get this error. 8727: You tried to change the extension of a font (FON) to a picture extension (PIC) or vice- versa when naming the file for saving to disk. This error can also occur if the extension is invalid or not attached to the filename. Program will reset the extension and save the file. 8728: Issued \PRINT without a print file open. \OPEN a print file or LPT# before you use \PRINT. 8729: You attempted to save a font but the file could not be made into a font. To be a font all frames must be the same height, all frames must be raster, and except for proportional fonts, all frames must be the same width. 8734: Too many (or too few) font characters. Maximum is 100 characters. (Minimum is 1.) 8735: Bad data in a font file, or the font file will not fit in the font area. (The size of the font area is adjustable with the FONT=# parameter of the P11FLAGS= environment variable or the command-line startup parameters.) 8741: Picture header size invalid. Header contains bad data and file is probably damaged, or you tried to move a bitplane font to the picture edit area. You can't do this. Fonts are created in bitmap mode only. 8742: Error expanding a picture header from 0 or 10 bytes to full size for picture files. File is probably damaged. 8743: Error occurred during picture or font file decompression. Either the file is bad, or you do not have a large enough area for the frame if you have set the maximum frame or font size to less than 64K using the P11FLAGS= environment variable or the command-line startup parameters. 8744: Same as 8743, above, but during a picture file decompression. 8745: Header size for frame (font or picture) is wrong--file is probably bad. 8746: Decompressed picture or font wouldn't fit in assigned area. Environment or command line startup parameter C:# may be too small, or file is damaged. 8753: Bad parameter in the \HUE command. 8754: Hues. Values out of range (0 to 63 or, for EGA, 0 to 16.) If using INC=, you have to "know your numbers" and not let this happen... 8755: Hue color value too great (must be < maximum # of colors for that mode.) 8759: \HUE. A hue file cannot be read in if changes to the current hue file in RAM exist. 8776: \RETURN inside an \IF statement. Not allowed. \ENDIF must come first. 8980: Beyond the last dot in a vector drawing. You cannot draw this dot if doing so would make the picture size larger than the original size specified when new or when saved to or read from the disk. To make a frame larger copy to a pre-defined larger frame which you have inserted in front of the current frame, then delete the old frame. 8983: Attempt to delete the only dot in a vector picture. Instead you must delete the frame at that point. 8985: Attempt to delete after the last dot in a vector image. This dot doesn't exist. 8996: Attempt to \DELETE a frame when there are no frames in RAM to delete. 8997: An attempt to delete frame zero (0). There is no frame zero. This error would occur if you code \DELETE with a zero value. 9023: Block move/copy error. The text block has not been properly marked somehow. 9024: Block move/copy error. The current cursor position is within the block to be moved/copied. It must be outside that area for this function. 9025: Block move/copy error. To move/copy a block the full size of the block must be available in the text area of RAM. The program first copies the block, inserting it at the current cursor location. If doing a Move option the old block is deleted. Since it first copies the block, it needs the total text size--with two copies of the block-- available to accomplish this option. 9026: Block move error. Can be the same as 9027 but strictly for the Move option, or some other block error. You will probably also have gotten a previous block error. 9027: Block copy error. Same as 9028 below but for the Copy option of F2. 9028: Block move or delete error. You have not defined the endpoints of the block yet or you have since made changes to the text file. Move/Copy must be done after setting endpoints for the block and before making any additional changes. If you have defined NO block and hit <F2>, D, then you will delete a line. You only get this error if you defined one block point. 9100: \FRAME error. Size is too big. Maximum vector frame is about 4000 dots, and the maximum raster size is about 64,016 bytes. 9101: \FRAME error. There is no room in RAM for this picture. Solutions would be to make a smaller frame, have less frames in RAM, or buy more RAM for your machine if possible. If you have been deleting frames, space may also be fragmented. (See additional information on SPACE CONSIDERATIONS.) 9102: \FRAME error. The maximum # of frames would be exceeded if the command were executed. You can increase the maximum number of frames (to the limit of over 8,000) with the f:# option of the Environment or command- line startup parameter. 9104: \FRAME cannot be executed in "instant" command mode if you are editing a vector picture at the time. It can only be executed from a text file, from the text editor, or while drawing a raster image. 9214: \SET. Parameter not recognized. 9215: \SET. Frame number is negative or 0. 9216: \SET. Frame not vector. 9217: \SET. DOT= number greater than the number of dots in the vector frame. Dots cannot be added with this command. 9218: \SET. This command can only be executed if there are no editing changes to the current picture file. 9303: Raster picture height invalid during a save. You should not be able to get this error unless you had read a bad picture file. 9304: Vector picture size is invalid when saving it in memory. You should not be able to get this error unless you read a bad picture file. 9305: Attempt to save a vector picture with the SAVE option of \SHOW. Only pre-existing raster pictures can be saved with this command. Use \FRAME to create and save a new image. 9931: Missing close-brackets (]). 9997: \DRAW cannot end with a comma. \DRAW stops evaluating when an invalid parameter is found. You could get this error if an invalid parameter comes after a comma. In that case you should also get another error first. 9998: Syntax of the Scale option within \DRAW is not valid. S must be immediately followed by A, X or Y (see \DRAW). 9999: Color specification in \DRAW evaluates to a negative number or a number greater than the maximum for this mode. See \DRAW. 32765: DOS version major version number is less than two (2). You need at least DOS 2.0 to run this program. 32767: Program failed to return all excess memory at the start of running. Program probably cannot allocate area for pictures after this error. You should never get this error.