中国DOS联盟

### Microsoft Quick BASIC Error Messages (V4.5)

/

--------------------------------------------------------------------------------
　　●Boot error ●Link error
　　●Compile error ●Run-time error
　　Each type of error is related to a specific step in the program development process. A boot error may occur when using the QB or BC command to boot into QuickBASIC. A compile error (and warning) may occur during the compilation process. A run-time error may occur when the program is running. A link error may only occur when using the link command to link object files generated by BC or other language compilers.
　　Section 1.2 lists the boot, compile, and run-time error messages and all specified error codes in alphabetical order. Table 1.1 lists the run-time error messages and error codes in numerical order. Section 1.3 lists the Microsoft Overlay Linker error messages, and Section 1.4 lists the Microsoft Library Manager error messages.
　　1.1 Error Message Display
　　When a run-time error occurs in the environment (using the default screen display), the error message appears in the dialog box, and the cursor is placed on the line where the error occurred.
　　In an independent executable program (that is, a program that can be executed by entering the base name of the executable file at the system prompt), the run-time system prints an error message with an address, unless the /D, /E, or /W option is specified on the BC command line. In these cases, the error range is followed by the line number where the error occurred. The standard form of such an error message is as follows:
　　Error n in module module-name at address segment:offset or Error n in line linenumber of module module-name at address segment:offset Some errors have been included in the error code list. If an error occurs when entering the error trapping subroutine, the return value of ERR sets the corresponding code (the error trapping subroutine can be entered using the ON ERROR statement). The ERR value remains unchanged until the RESU
　　ME statement returns control to the main program.
　　Table 1.1 Run-time Error Codes
　　Deseription Code Deseription
　　2 syntax error 53 File not found
　　3 RETURN without GOSUB 54 Bad file mode
　　4 Out of DATA 55 File already open
　　5 Illegal function call 56 FIELD statement active
　　6 Overflow 57 Device I/O error
　　7 Out of memory 58 File already exists
　　9 Subscript out of rang 59 Bad record length
　　10 Duplicate definition 61 Disk full
　　11 Division by zero 62 Input past end of file
　　13 Type mismatch 63 Bad record number
　　14 Out of string space 64 Bad file name
　　16 String formula too complex 67 Too many files
　　19 No RESUME 68 Device unavailable
　　20 RESUME without error 69 Communication-buffer overflow
　　24 Device timeout 70 Permission denied
　　25 Device fault 71 Disk not ready
　　27 Out of paper 72 Disk-media error
　　39 CASE ELSE expected 73 Advanced feature unavailable
　　40 Variable requirted 74 Rename across disks
　　50 FIELD overflow 75 Path/File access error
　　51 Internal error 76 Path not found
　　52 Bad file name or number 
　　(Table 1.1 lists the error codes in numerical order. For the explanation of the errors, please refer to the alphabetical list.)
　　1.2 Call, Compile, Run-time Error Messages
　　Argument-count mismatch
　　A function feature used in QuickBASIC that is applied in other BASIC versions, or this feature can only run under a high version of DOS. (Compile or run-time error) Error code: 73
　　Advanced feature unavailable
　　The number of parameters used in the BASIC subroutine or function is incorrect. (Compile error)
　　Array already dimensioned
　　The error may be caused by the following reasons:
　　●Using multiple DIM statements to define the same static array.
　　●Using the DIM statement after array initialization. Before redefining a dynamic array using DIM, you must use the ERASE statement to reallocate memory units; or redefine it using the REDIM statement.
　　●After the array is defined, the OPTION BASE statement appears (compile or run-time error)
　　Array not defined
　　Using an undefined array. (Compile error)
　　Array not dimensioned
　　Using an undefined array. If compiled with BC, this error is not "fatal", the program will be executed, but the result may be incorrect. (Compile error)
　　Array too big
　　There is not enough user data space to load the defined array. Please reduce the array size or use the $DYNAMIC meta-command. If the array space exceeds 64K, or the array is not dynamic and the /AH option is not used, this error will still occur. Please reduce the array space, or use the /AH command line option to make the array a dynamic array. (Compile error)
　　AS clause required
　　The variable defined with the AS statement has no parameters. If the AS clause is in the first definition of the variable, the AS clause must be in a series of statements related to the variable such as DIM, REDIM, SHARED, and COMMON statements. (Compile error)
　　AS clause required on first declaration
　　A variable that has not been defined with the AS clause uses the AS clause as a parameter. (Compile error)
　　AS missing
　　The compiler requires the keyword AS, such as in the OPEN "FILENAME" FOR INPUT AS#1 statement. (Compile error)
　　Asterisk missing
　　The asterisk (*) is missing in the user-defined string definition. (Compile error)
　　Bad file mode 
　　The reasons for the error are as follows:
　　●The program uses the PUT or GET statement for sequential files, or uses the OPEN statement for non-I, O, or R file modes.
　　●Using the FIELD statement for a file that is not opened in random access mode.
　　●Performing output operations on a file opened in input form.
　　●Performing input operations on a file opened in output or append form.
　　●QuickBASIC attempts to use an include file stored in compressed format. The include file must be stored in text format. Reload the include file, store it in text format, and then run the program.
　　●Attempting to load an incorrect binary program. (Run-time error)
　　Error code: 54
　　Bad file name
　　The file name is illegal when using the LOAD, SAVE, KILL, or OPEN statement (for example, the file name has too many characters). (Run-time error)
　　Error code: 64
　　Bad file name or number
　　The file name or number used in the statement or command is not explained by the OPEN statement, or exceeds the number of files explained in the program. (Run-time error)
　　Error code: 52
　　Bad record length
　　The length of the record variable specified in the GET or PUT statement does not match the record length specified in the corresponding OPEN statement. (Run-time error)
　　Error code: 59
　　Bad record number
　　In the PUT or GET statement, the number of records is less than or equal to zero. (Run-time error)
　　Error code: 63
　　BASE missing
　　The Quick BASIC version requires the keyword BASE to appear here, such as in OPTION BASE. (Compile error)
　　Binary source file
　　The file being compiled is not an ASCII file. All source files stored in BASIC must use the A option. In a binary source file, if the user uses the /Z1 or /ZD CodeView option, QuickBASIC also uses this error message to prompt. (Compile error)
　　Block IF without END IF
　　There is no corresponding ENDIF statement in the IF structure block. (Compile error)
　　Buffer size expected after /C:
　　The buffer size must be defined after the /C option. (BC boot error)
　　BYVAL allowed only with numeric arguments
　　BYVAL does not accept string or record parameters. (Compile error)
　　/C:buffer size too large
　　The maximum capacity of the communication buffer is 32,767 bytes. (BC boot error)
　　Cannot continue
　　During debugging, the user's changes prevent continuous execution. (Run-time error)
　　Cannot find file (filename), Input path;
　　When QuickBASIC cannot find the Quick library or utility (BC.EXE, LINK.EXE, LIB.EXE, or QB.EXE) required by the program, this error message will appear. Please enter the correct path name, or press the CTRL+C key to return to the DOS prompt. (QB boot error)
　　Cannot generate listing for BASIC binary source files
　　Attempting to compile a binary source file with the BC command and the /A option. Please remove the /A option and recompile. (BC boot error)
　　Cannot start with 'FN'
　　Using "FN" as the first two letters of a subroutine or variable name. "FN" can only be used as the first two letters when calling the DEFFN function. (Compile error)
　　CASE ELSE expected
　　There is no matching case in the SELECT CASE statement. (Run-time error)
　　Error code: 39
　　CASE without SELECT
　　The first part of the SELECT CASE statement is missing or misspelled. (Compile error)
　　Colon expected after /C
　　A colon ":" is required between the option and the parameter of the buffer size. (BC boot error)
　　Comma missing
　　A comma "," is needed. (Compile error)
　　COMMON and DECLARE must precede executable statements
　　The position of the COMMON statement or DECLARE statement is incorrect. The COMMON and DECLARE statements must be placed before all executable statements. Except for the following statements, all BASIC statements are executable.
　　▲COMMON
　　▲DEFtype
　　▲DIM (applied to static variables)
　　▲OPTION BASE
　　▲REM
　　▲TYPE
　　▲All meta-commands
　　(Compile error)
　　COMMON in Quick library too small
　　There are more common variables in the module than the common variables currently loaded in the Quick library. (Compile error)
　　COMMON name illegal
　　In the block named COMMON, QuickBASIC encounters an illegal block name /blocknamel (for example, the block name is a BASIC reserved word). (Compile error)
　　Communication-buffer overflow
　　In remote communication, the receive buffer overflows. The size of the receive buffer is defined by the /C option or RB option in the OPEN COM statement. You should often check the buffer space or empty the buffer frequently (using the INPUT function) (Run-time error)
　　Error code: 69
　　CONST/DIM SHARED follows SUB/FUNCTION
　　The CONST and DIM SHARED statements should appear before the definition of all subroutines or FUNCTION procedures. If this program is compiled with BC, this error is not fatal, the program will be executed, but the running result may be incorrect. (Compile warning)
　　Controlstructure in IF...THEN...ELSE incomplete
　　A mismatched NEXT, WEND, ENDIF, END SELECT, or LOOP statement appears in the IF…THEN…ELSE one-line statement. (Compile error)
　　Data-memory overflow
　　There is too much program data in memory. This error is caused by too much data in constants or static arrays. If compiled with BC, or generating an EXE file or a Librory command, close all debugging options. If there is still not enough memory, please divide the user program into several parts and use the CHAIN statement or use the DYNAMIC meta-command. (C compile error)
　　DECLARE required
　　The process is not defined before the implicit call to the SUB or FUNCTION process. All processes must be defined or explained before the implicit call. (Compile error)
　　DEF FN not allowed in control statements
　　Defining a DEF FN function inside a control structure such as IF...THEN...ELSE and SELECT CASE is not allowed. (Compile error)
　　
　　DEF without END DEF 
　　There is no corresponding END DEF statement in the definition of a multi-line function. (Compile error)
　　DEF type character specification illegal
　　There is a mistake in entering the DEF type statement. Only LNG, DBL, INT, SNG, STR or space (for user-defined functions) can follow DEF. (Compile error)
　　Device fault
　　The drive returns a hardware error. If this message appears when data is transmitted to a communication file, it means that the signal tested by the OPEN COM statement was not detected during this period. (Run-time error)
　　Error code: 25
　　Device I/O error
　　An I/O error occurs during I/O operations on the drive, and the operating system cannot recover from the error state. (Run-time error)
　　Error code: 57
　　Device timeout
　　The program did not receive information from the drive within the scheduled time. (Run error)
　　Error code: 24
　　Device unavailable
　　The device that needs to be entered is not online or does not exist. (Run-time error)
　　Error code: 68
　　Disk full
　　When there is not enough disk space to complete the PRINT, WRITE, or CLOSE operation, Quick BASIC also generates this error message when writing the target file or executable file to the peripheral if there is not enough disk space. (Run-time error)
　　Error code: 61
　　Disk-media error
　　The disk drive hardware detected physical damage on the disk (run-time error)
　　Error code: 72
　　Disk not ready
　　The door of the drive is not closed, or there is no disk on the drive. (Run-time error)
　　Error code: 71
　　Division by zero
　　The divisor in the expression is zero, or the result of the exponent operation is a negative power of zero.
　　DO without LOOP
　　The LOOP termination clause is missing in the DO...LOOP statement. (Compile error)
　　Document too large
　　The file exceeds the internal limit of Quick BASIC. This file should be divided into several files.
　　Duplicate definition
　　Using a definition statement for an item that has been defined, for example, using the same name in the LONST statement and the variable definition statement, or the procedure has the same name as the variable.
　　This error also occurs when trying to redefine an array. When redefining a dynamic array, you must use DIM or REDIM (compile error or run-time error)
　　Error code: 10
　　Duplicate label
　　Two lines in the program share a number or mark. All line numbers or marks in a module must be unique.
　　(Compile error)
　　Dynamic array element illegal 
　　Using a dynamic array element in VARPTR is not allowed. (Compile error)
　　Element not defined
　　The element of the user-defined type is not defined. For example, the user-defined type MYTYPE contains elements A, B, and C, and using variable D as an element in MY TYPE will cause this error. (Compile error)
　　ELSE without IF
　　Using the ELSE clause but without the corresponding IF statement. Sometimes this error is caused by incorrect IF statement nesting.
　　(Compile error)
　　ELSEIF without IF
　　Using the ELSE IF statement but without the corresponding IF statement. (Compile error)
　　END DEF without DEF
　　Using the ELSE DEF statement but without the corresponding DEF statement. (Compile error)
　　END IF without block IF
　　The start part of the IF program block is missing. (Compile error)
　　END SELECT without SELECT
　　There is only the END SELECT end statement, but no SELECT CASE start sentence. The SELECT CASE start sentence may be omitted (Compile error)
　　END SUB or END FUNCTION must be last line in window
　　Adding a code after a process must return to the main module or open another module. (Compile error)
　　END SUB/FUNCTION withcut SUB/FUNCTION
　　The user deleted the SUB or FUCTION statement. (Compile error)
　　END TYPE without TYPE
　　The END TYPE statement is missing TYPE. (Compile error)
　　Equal sign missing
　　Quick BASIC requires an equal sign. (Compile error)
　　Error during Quick BASIC initialization
　　There are many reasons for this error. The most common reason is that there is not enough memory space to load Quick BASIC. If the Quick library is loaded, the space occupied by this library should be reduced.
　　This error will also occur when using it on hardware that does not support Quick BASIC. (QB boot error)
　　Error in loading file (filename)-Cannot find file
　　This error will occur when redirecting input from a file to Quick BASIC. The input file is not in the position specified by the command line. (QB boot error)
　　Error in loading file (filename)-Disk I/O errorThis error is caused by physical problems during disk access, such as the drive door not being closed. (QB boot error)
　　Error in loading file (filename)-DOS memory-aera error
　　Writing an assembly language program or POKE statement to the memory area used by DOS. (QB boot error)
　　Error in loading file(filename)-Invalid format
　　Loading the Quick BASIC library in an illegal format. This error will occur when using a library established by a different version of Quick BASIC, or when using the /QU option not processed by the Quick BASIC library building command or LINK, or when loading an independent library with Quick BASIC. (QB boot error)
　　Error in loading file(filename)-Out of memory
　　The required memory space is larger than the available space. For example: there is not enough space to allocate the file buffer. Try reducing the DOS buffer, releasing programs that have terminated and are still in memory, or removing some device drivers. If the array is large, use the meta-command $DYNAMIC at the beginning of the program. If the file has been loaded, clearing these files can release some memory. (Run-time error)
　　EXIT DO not within DO...LOOP
　　The EXIT DO statement is used outside the DO...LOOP statement. (Compile error)
　　EXIT not within FOR...NEXT
　　The EXIT FOR statement is used outside the FOR...NEXT statement. (Compile error)
　　Expected:item
　　This is a syntax error. The cursor appears on an item that should not appear.
　　Expression too complex
　　This error will occur when exceeding a certain internal limit. For example, during the evaluation of an expression, a string irrelevant to the variable is temporarily assigned to the variable. The occurrence of a large number of such strings will cause this error. Please simplify the expression. Re-specify the variable that stores the expression. (Compile error)
　　Extra file name ignored
　　Too many files are specified on the command line; the last file on the line will be lost. (BC boot error)
　　Far heap corrupt
　　The far-heap storage has an error in the following situations:
　　●The QB compiler does not support programs that have terminated and remain in memory in DOS.
　　●The POKE statement modifies the memory area used by Quick BASIC. (This may modify the definition of dynamic arrays for numbers or fixed-length strings)
　　●The program calls a subroutine of another language, and this subroutine modifies the storage area used by Quick BASIC.
　　(This may modify the definition of dynamic arrays for numbers or fixed-length strings)
　　(Compile error)
　　FIELD overflow
　　The number of bytes allocated by the FIELD statement is greater than the record length specified in the random file.
　　(Run-time error)
　　Error code: 50
　　FIELD statement active
　　The space of the record variable used in the file GET or PUT statement has been occupied by the FIELD statement. The GET or PUT statement with the record variable parameter is only applied to files without the FIELD statement. (Run-time error)
　　Error code: 56
　　File already exists
　　The file name defined by the NAME statement is already used in the form of a file name on the disk. (Run-time error)
　　Error code: 58
　　File already open
　　Trying to open an already opened file from the OPEN statement in sequential output mode, or operating on an already opened file with the UNK statement.
　　(Run-time error)
　　Error code: 55
　　File not found
　　Operating on a non-existent file with FILES, KILL, NAME, OPEN, or RUN statements.
　　(Run-time error)
　　Error code: 53
　　File not found in module module-name at address segment:offset
　　The file in the FILE, KILL, NAME, OPEN, or RUN statement does not exist. This error message is equivalent to the File not found message. However, this error occurs when the compiler is executed. The module name is the name of the module being called. The address is the address where the access error code is located. (Run-time error)
　　Error code: 53
　　File previously loaded
　　Attempting to load a file that already exists in memory. (Compile error)
　　Fixed-length string illegal
　　Trying to use a fixed-length string as a standard parameter. (Compile error)
　　FOR index variable already in use
　　This error will occur when the subscript variable is used multiple times in a nested FOR loop. (Compile error)
　　FOR index variable illegal
　　This error will occur when the wrong variable type is used in the FOR loop subscript. The FOR loop subscript variable must be a simple numeric variable. (Compile error)
　　FOR without NEXT
　　Each FOR statement must be accompanied by a NEXT statement. (Compile error)
　　Formal parameter specification illegal
　　There is an error in the parameter list of the function or subroutine. (Compile error)
　　Formal parameters not unique
　　The parameters specified for the function or subroutine appear repeatedly, such as: SUB Get Name(A,B,C,A) STATIC. (Compile error)

Function already defined
　　 Redefining a function that has already been defined. (Compile-time error)
　　 Function name illegal
　　 A reserved word in BASIC was used in the name of a user-defined function. (Compile-time error)
　　 Function not defined
　　 A function must be declared or defined before it is used. (Compile-time error)
　　 GOSUB missing
　　 A GOSUB is missing in the ON event statement. (Compile-time error)
　　 GOTO missing
　　 A GOTO is missing in the ON ERROR statement. (Compile-time error)
　　 GOTO or GOSUB expected
　　 Quick BASIC requires a GOTO or GOSUB statement. (Compile-time error)
　　 Help not found
　　 The requested help was not found, and the errors in the program prevented Quick BASIC from generating the variable list. Press F5 to return to the line where the error occurred. Identifier cannot end with %, &, !, # or $
　　 The above suffixes are not allowed in names used in type definitions, subroutine names, or COMMON statements. (Compile-time error)
　　 Identifier cannot include period
　　 Names of user-defined types and record elements cannot contain periods. Periods can only be used as separators for record variables. Additionally, if the part of the name before the period has been used in an AS usertype clause somewhere in the program, the variable name cannot contain a period. If a program uses a period in a variable name, it is recommended to change it to a mixed form. For example, variables ALPHA and BETA can be changed to ALphaBeta. (Compile-time error)
　　 Identifier expected
　　 An identifier, number, or BASIC reserved word was expected.
　　 Identifier too long
　　 The length cannot exceed 40 characters.
　　 Illegal function call
　　 An out-of-bounds parameter was passed to a mathematical or string function. The following reasons can also cause a function call error:
　　 ●Using a negative number or an out-of-bounds subscript.
　　 ●Performing a non-integer exponentiation on a negative number.
　　 ●Using a negative record number when using GET or PUT files.
　　 ●Passing an incorrect or out-of-bounds parameter to a function.
　　 ●Performing BLOAD or BSAVE operations on a non-disk drive.
　　 ●Performing the operation on a drive that does not support I/O functions or statements (such as LOC or LOF).
　　 ●Combining strings to produce a string longer than 32,767. (Run-time error)
　　 Error code: 5
　　 Illegal in direct mode
　　 The statement is only valid in a program.
　　 It cannot be used in the current window. (Compile-time error)
　　 Illegal number
　　 The data format is incorrect. Maybe there is a typo. For example, the number 2p3 will generate this error. (Compile-time error)
　　 Illegal in procedure or DEF FN
　　 Illegal outside of SUB, FUNCTION, or DEFFN
　　 This statement is not allowed in module-level code. (Compile-time error)
　　 Illegal outside of SUB FUNCTION
　　 This statement is not allowed in module-level code or DEF FN functions. (Compile-time error)
　　 Illegal outside of TYPE block
　　 This statement is not allowed in module-level code or DEF FN functions. (Compile-time error)
　　 The element As type clause is only allowed in TYPE…END TYPE. (Compile-time error)
　　 Illegal type character in numeric constant
　　 A mismatched type specifier is present in a numeric constant. (Compile-time error)
　　 $INCLUDE-file access error
　　 The included file in the meta-command could not be loaded. (Compile-time error)
　　 Include file too large
　　 The included file exceeds Quick BASIC's internal limits. The file needs to be divided into several parts. (Compile-time error)
　　 Input file not found
　　 The source file specified in the command line is not in the specified location. (BC boot error)
　　 INPUT missing
　　 The keyword INPUT is missing in the compile program. (Compile-time error)
　　 Input past end of file
　　 Reading an empty file or the end of the file has been reached using the INPUT statement. Use the EOF function to test for the end of the file to avoid this error. (Run-time error)
　　 Error code: 62
　　 Input runtime module path:
　　 This error occurs if the run-time module BRVN45.EXE is not found. The correct path name should be entered. This error is serious and difficult to catch. (Run-time error)
　　 Integer between 1 and 32767 required
　　 An integer parameter is required. (Compile-time error)
　　 Internal error
　　 Quick BASIC has an internal fault. Use the Product Assistance Request form with your file to explain to Microsoft under what conditions which messages appear. (Run-time error)
　　 Error code: 51
　　 Internal error near xxxx
　　 Quick BASIC has an internal fault when loading xxxx. Use the Product Assistance Request form with your file to explain under what conditions which messages appear. (Compile-time error)
　　 Invalid character
　　 Quick BASIC found an invalid character. For example, a control character appears in the source file. (Compile-time error)
　　 Invalid constant
　　 A constant value is specified with an illegal expression. Note that an expression defined as a constant can include numeric constants, symbolic constants, and all arithmetic or logical operators except exponentiation. A string expression defined as a constant can only include simple literal strings. (Compile-time error)
　　 Invalid DECLARE for BASIC procedure
　　 The keywords ALLAS, CDECL, or BYVAL are used in a BASIC procedure with the DECLARE statement. ALLAS, CDECL, and BYVAL can only be used in non-BASIC procedures. (Compile-time error)
　　 Label not defined
　　 The referenced line label (such as in the GO TO statement) does not exist in the program. (Compile-time error)
　　 Left parenthesis missing
　　 Quick BASIC requires a left parenthesis, or the REDIM statement to redefine space for subscript variables. (Compile-time error)
　　 Line invalid, Start again
　　 An invalid file name is used after the path character "\" or ":". (BC boot error)
　　 Line number or label missing
　　 The line number or label is missing in a statement that requires it, such as the GO TO statement. (Compile-time error)
　　 Line too long
　　 Only 255 characters are allowed per line. (Compile-time error)
　　 LOOP without DO
　　 The DO that initiates the DO...LOOP statement is missing or misspelled. (Compile-time error)
　　 Lower bound exceeds upper bound
　　 The lower bound exceeds the upper bound defined by the DIM statement. (Compile-time error)
　　 Math overflow
　　 The calculated result is too large to be represented in the BASIC data format. (Compile-time error)
　　 $Metacommand error
　　 The meta-command is incorrect. If compiling with BC, this error is not fatal, the program will run, but the result may be incorrect. (Compile-time warning)
　　 Minus sign missing
　　 Quick BASIC requires a minus sign. (Compile-time error)
　　 Missing Event Trapping(/W) or Checking Between Statements(/V) option
　　 The program contains an /N event statement that requires one of these options. (Compile-time code)
　　 Missing On Error(/E) option
　　 When using the BC command, the program containing the ON ERROR statement must use the ON ERROR(/E) option. (Compile-time error)
　　 Missing Resume Next(/X) option 
　　 When using the BC command, the program containing RESVME, RESVME NEXT, and RESVME statements must use the RESVME NEXT(/X) option. (Compile-time error)
　　 Module level code too large
　　 The module-level code exceeds Quick BASIC's internal limits. Some code can be moved to SUB or FUNCTION procedures. (Compile-time error)
　　 Module not found. Unload module from program?
　　 When loading the program, Quick BASIC did not find the file containing the specified module. Quick BASIC will generate an empty module instead. The empty module must be deleted before running the program.
　　 Must be first statement on the line
　　 In the IF...THEN...ELSE structure, IF, ELSE, ELSE IF, and END IF can only be preceded by a line number or line label. (Compile-time error)
　　 Name of subprogram illegal
　　 The subprogram name uses a Quick BASIC reserved word or two subprograms have the same name. (Compile-time error)
　　 Nested function definition
　　 A FUNCTION definition appears within another FUNCTION definition, or this occurs in an IF...THEN...ELSE clause. (Compile-time error)
　　 NEXT missing for variable
　　 There is a FOR statement but no corresponding NEXT statement. The variable is the subscript variable of the FOR loop. (Compile-time error)
　　 NEXT without FOR Every NEXT statement should correspond to a FOR statement. (Compile-time error)
　　 No line number in module-name at adress segment:offset
　　 This error occurs when the error address is not found in the line number table during error handling. It also occurs if the line number is not an integer within the range 0_65,527. It also occurs if the user overwrites the line number table. This error is serious and difficult to detect. (Run-time error)
　　 No main module, Choose Set Main Module from the Run menu to select one 
　　 The program tries to run before the main module is loaded. All programs must have a main module. (Compile-time error)
　　 No RESUME
　　 The program encounters the program end flag during error handling. The RESQUME statement needs to be used to correct this situation. (Run-time error)
　　 Error code: 19
　　 Not watchable
　　 This error occurs when a variable is specified in the watch expression. Confirm that the module-level procedure in the currently active window accesses the matching variable. For example, module-level code cannot access variables in SUB or FUNCTION. (Run-time error)
　　 Numeric array illegal
　　 The parameter of VARPTR$ cannot be a numeric array, only simple variables and string array elements. (Compile-time error)
　　 Only simple variables allowed
　　 In the READ and INPUT statements, arrays of user-defined types are not allowed, i.e., non-user-defined type arrays are allowed. (Compile-time error)
　　 Operation requires disk
　　 An attempt is made to perform a take-out or store operation on an external disk drive, such as a printer or keyboard. (Compile-time error)
　　 Option unknown:option
　　 The given option is illegal. (BC boot error)
　　 Out of DATA
　　 The data in the DATA statement has been read up when the READ statement is executed. (Run-time error)
　　 Error code: 4
　　 Out of data space
　　 The data space request should be modified. As follows:
　　 ●Reduce the file buffer in the LEN clause of the OPEN statement.
　　 ●Use meta-commands to generate dynamic arrays. Dynamic arrays require much more data space than static arrays.
　　 ●Use fixed-length string arrays instead of variable-length string arrays.
　　 ●Use the smallest data type that meets the requirements. Try to use integer data as much as possible.
　　 ●Use as few small procedures as possible. Quick BASIC must generate several control information bytes for each procedure.
　　 ●Use the CLEAR statement to modify the stack space. Use enough stack space to meet the requirements.
　　 ●Do not have more than 255 characters per line in the source program. Such long lines require additional text buffer space. (Compile-time or run-time error)
　　 Out of memory
　　 The required memory is greater than the available memory. For example, there is not enough space when allocating a file buffer. The DOS buffer can be reduced, or some terminated and resident programs can be cleared or some device drivers can be removed. If the array is large, add a meta-command at the beginning of the program. If some files are loaded in memory, clearing the files can release some memory space. (BC boot error, compile-time or run-time error)
　　 Error code: 7
　　 Out of paper
　　 The printer has no paper or is not powered on. (Run-time error) Error code: 27
　　 Out of stack space
　　 The recursion function procedure is nested too deeply, too many subroutines are activated, or too many FUNCTION and SUB calls are made. This error will occur. The CLEAR statement should be used to increase the stack space allocated by the program. This error cannot be caught. (Run-time error)
　　 Out of string space
　　 The string variable exceeds the space allocated to the string. (Run-time error)
　　 Error code: 14
　　 Overflow
　　 The result of the operation is out of bounds. Its value exceeds the range of integers and floating-point numbers. (Run-time error)
　　 Error code: 6
　　 Overflow in numeric constant
　　 The constant value is too large. (Compile-time error)
　　 Parameter type mismatch
　　 The type of the subroutine or FUNCTION parameter does not match the type of the parameter in the DECLARE statement or the type of the calling parameter.
　　 (Compile-time error)
　　 Path not found
　　 When performing OPEN, MKDIR, CHDIR, or RMDIR operations, DOS cannot find the specified path. The operation cannot be completed. (Run-time error)
　　 Error code: 16
　　 Path/File access error
　　 When performing OPEN, MKDIR, CHDIR, or RMDIR operations, DOS cannot correctly associate the path name with the file name. This operation cannot be completed. (Compile-time error or run-time error)
　　 Error code: 75
　　 Permisson denied
　　 Writing to a write-protected disk or reading/writing a locked file. (Run-time error)
　　 Error code: 70
　　 Procedure already defined in Quicklibrary
　　 The QuickBASIC procedure has the same name as the procedure in the user program. (Compile-time error)
　　 Procedure too large
　　 The procedure exceeds QuickBASIC's internal limits. This procedure needs to be divided into several procedures to reduce its size. (Compile-time error)
　　 Program-memory overflow
　　 Compiling a program with a code segment exceeding 64K. This program should be divided into several modules or the CHAIN statement should be used. (Compile-time error)
　　 Read error on standard input 
　　 This system error occurs when reading from the keyboard or a redirected input file.
　　 Record/string assignment required
　　 A string or record variable parameter is missing in the LSET statement. (Compile-time error)
　　 Redo from start
　　 Incorrect data or item type is entered at the INPUT prompt. The data needs to be re-entered in the correct form. (Run-time error)
　　 Rename acrossd disks
　　 Attempting to change the file name with a new drive letter is not allowed. (Run-time prompt)
　　 Error code: 74
　　 Requires DOS 2.10 or later
　　 Using QuickBASIC under an incorrect DOS version. (QB boot or run-time error)
　　 RESUME without error
　　 The RESUM statement is encountered before entering the error trapping subroutine. (Run-time error)
　　 Error code: 20
　　 RETURN without GOSUB
　　 No matching GOSUB statement is found before the RETURN statement. (Run-time error)
　　 Error code: 3
　　 Right parenthesis missing
　　 QuickBASIC requires a right (closing) parenthesis. (Compile-time error)
　　 SEG or BYVAL not allowed in CALLS
　　 BYVAL and SEG are only allowed in the CALL statement. (Compile-time error)
　　 SELECT without END SELECT
　　 The end statement is missing or misspelled in the SELECT CASE statement. (Compile-time error)
　　 Semicolon missing
　　 QuickBASIC requires a semicolon ";". (Compile-time error)
　　 Separator illegal
　　 An illegal delimiter appears in the PRINT USING or WRITF statement. Semicolons or commas should be used as delimiters.
　　 (Compile-time error)
　　 Simple or array variable expected
　　 The compile program expects a variable parameter. (Compile-time error)
　　 Skipping forward to END TYPE statement
　　 An error in the TYPE statement causes Quick BASIC to ignore everything between TYPE and END TYPE. (Compile-time error)
　　 Statement cannot occur within $INCLUDE file
　　 SUB..ENDSUB and FUNCTION...END FUNCTION statement blocks are not allowed in included files. Use the Merge command in the file menu to insert the included file into the current module, or load the included file as an independent module into memory. If the included file is loaded as an independent module, it needs to be reorganized because shared variables are only shared within the module. (Compile-time error)

Statement cannot precede SUB/FUNCTION definition
　　 Statements that can only be REM and DEF type statements are used before the process definition. (Compile - state error)
　　 Statement ignored
　　 When using the BC command to compile a program containing TRON and TROFF statements, the / D option is not used. This error is not fatal. This program will execute, but the result may be wrong. (Compile error)
　　 Statement illegal in TYPE block 
　　 Only REM and element AS typename can appear between TYPE and END TYPE. (Compile - state error)
　　 Statement unrecognizable
　　 A BASIC statement may be input incorrectly. (Compile - state error)
　　 Statements/labels illegal between SELECT CASE and CASE
　　 No other statements and line marks can appear before SELECT CASE and the first CASE statement. But comment statements and statement separators can appear. (Compile - state error)
　　 STOP in module name at address segment:offset
　　 The STOP statement is encountered in the program. (Runtime error)
　　 String assignment required 
　　 The REST statement is missing a string setting. (Compile - state error)
　　 String constant required for ALIAS
　　 The keyword ALIAS in the DECLARE statement should be a string constant parameter. (Compile - state error)
　　 String expression required
　　 The statement requires a string expression as a parameter. (Compile - state error)
　　 String formula too complex
　　 The string is too long or more than 15 string variables are applied for in the INPUT statement. The string formula should be split or the INPUT statement should be divided into several parts to make it execute correctly. (Runtime error)
　　 Error code: 16
　　 String space corrupt
　　 This kind of error will occur when invalid characters in the string space are deleted when compressing the stack. The causes of the error are as follows: inappropriately modifying the string pointer or the string return pointer, this error will occur when the string is modified by an assembly language subroutine.
　　 The subscript of the used array exceeds the limit and the modification of the string space is not sufficient. The process debugging code option can be used to check the array subscript exceeding the limit during compilation.
　　 Incorrect use of POKE and/or DEF SEG statements may inappropriately modify the string space.
　　 Mismatched COMMON statements may appear between two linked programs. (Runtime error)
　　 String variable required
　　 The statement requires a string variable parameter. (Compile - state error)
　　 SUB or FUNCTION missing
　　 There is no corresponding process in the DECLARE statement. (Compile - state error) The process is missing an end statement. (Compile - state error)
　　 Subprogram error
　　 The SUB or FUNCTION definition is wrong. The causes of the error are as follows:
　　 This SUB or FUNCTION statement has been defined
　　 The program contains incorrect FUNCTION or SUB statement nesting.
　　 SUB or FUNCTION does not have an end statement END SUB or END RUNCTION. (Runtime error)
　　 Subprogram not defined
　　 The called subroutine is not defined. (Compile - state error)
　　 Subprograms not allowed in control statements
　　 The definition of the subroutine FUNCTION is not allowed in control structures such as IF...THEN...ELSE and SELECT CASE. (Compile - state error)
　　 Subscript out of range
　　 The subscript of the array element exceeds the limit defined by the array, or an element of a dynamic array without dimensions is accessed. If the / D option is used for debugging during compilation, this message will be generated. If the array space exceeds 64K, the array is not dynamic, and the / AH option is not used, this error will also occur. The array space should be reduced, the array should be made dynamic, or the / AH command line option should be used. (Runtime error)
　　 Error code: 9
　　 Subscript syntax illegal
　　 There is a syntax error in the array definition. For example, the array definition contains both string data type and integer data type. (Compile - state error)
　　 Syntax error
　　 There are many causes of this error. The most common cause is that the BASIC keyword or parameter entered is wrong during compilation. During operation, it is often that the DATA statement format is incorrect. (Compile - state or runtime error)
　　 Error code: 2
　　 Syntax error in numeric constant
　　 The format of the numeric constant is incorrect.
　　 (Compile - state error)
　　 THEN missing
　　 QuickBASIC is missing the keyword THEN
　　 (Compile - state error)
　　 TO missing
　　 QuickBASIC needs the keyword TO.
　　 (Compile - state error)
　　 Too many arguments in function call
　　 The parameter limit in the function call is 60. (Compile - state error)
　　 Too many dimensions
　　 The number of array dimensions shall not exceed 60. (Compile - state error)
　　 Too many files
　　 This kind of error will occur when the nesting level of included files is greater than 5 during compilation. During operation, this kind of error will also occur when trying to use the SAVE or OPEN statement to create a new file, so that the number of file directories exceeds 255. (Runtime error or compile - state error)
　　 Error code: 67
　　 Too many labels
　　 The number of line numbers in the line table of the ON...GOTO or ON...GOSUB statement exceeds 255 (compile - state error) or 59 (runtime error of compile application)Too many named COMMON bldoks
　　 The maximum number allowed in the block of name COMMON is 126. (Compile - state error)
　　 Too many TYPE definitions
　　 The maximum number of user - defined types is 240.
　　 (Compile - state error)
　　 Too many variables for INPUT
　　 The maximum number of variables in the INPUT statement is 60. (Compile - state error)
　　 Too many variables for LINE INPUT
　　 Only one variable is allowed in the LINE INPUT statement. (Compile - state error)
　　 Type mismatch
　　 The type of the variable does not match the requirement. For example, SWAP is used with string variables and numeric variables. (Compile - state or runtime error)
　　 Error code: 13
　　 TYPE missing
　　 The keyword TYPE is missing in the END...TYPE statement. (Compile - state error)
　　 Type more than 65535 bytes
　　 User - defined types are not allowed to exceed 64K. (Compile - state error)
　　 Type not defined
　　 The user type parameter is not defined in the TYPE statement. (Compile - state error)
　　 TYPE statement improperly nested
　　 User - defined types are not allowed to be defined in the process. (Compile - state error)
　　 TYPE without END TYPE
　　 The END TYPE statement associated with the TYPE statement is missing. (Compile - state error)
　　 Typed variable not allowed in expression
　　 User - defined type variables are not allowed in the expression. For example, in CALL ALPHA(x), x is a user - defined type. (Compile - state error)
　　 Unexpected end of file in TYPE declaration
　　 The file end character appears in the TYPE...EDN TYPE block
　　 Unprintable error
　　 The error message does not match the existing error condition. This may be generated by the ERROR statement for which the error code has not been defined. (Runtime error)
　　 Unrecognized switch error:“QU”
　　 It is established by an incorrect version of Microsoft Overlay Lind r. The EXE file or Quick library. The connection program in the QuickBASIC distribution disk must be used to establish the EXE file or Quick library. (Compile - state error)
　　 Valid options:［/RUN］ file/AH/B/C:buf/G/NOHI/H/L［lib］/MBF/CMD stringThis kind of error will occur when an invalid option of QuickBASIC is used. (QB boot error)
　　 Variable - length string required
　　 Only variable - length strings are allowed in the FIELD statement. (Compile - state error)
　　 Variable name not unique
　　 After using variables X and Y, trying to define X as a user - defined type. (Compile - state error)
　　 Variable required
　　 QuickBASIC encounters INPUT, LET, READ, or SHARED statements without variable parameters. (Compile - state error)
　　 Variable required
　　 When operating on a file opened in BINARY mode, the GET or PUT statement cannot define a variable. (Runtime error)
　　 WHILE without WEND
　　 This error will be generated when the WHILE statement has no corresponding WEND statement. (Compile - state error)
　　 WEND without WHILE
　　 This error will be generated when the WEND statement has no corresponding WHILE statement. (Compile - state error)
　　 Wrong number of dimensions
　　 The array dimension is wrong. (Compile - state error)
　　 1.3 Error messages in linking
　　 This section lists and describes the error messages generated by Microsoft Over lay Linker, LINK.
　　 A fatal error will cause the linker to stop running. The information form of these fatal errors is as follows:
　　 location fatal error L1xxx:messagetext
　　 A non - fatal error refers to a problem in the executable file, and LINK will generate the executable file. The form of non - fatal error messages is as follows:
　　 location:error L2xxx:messagetext
　　 A warning refers to a problem in the executable file: LINK generates the executable file, and the warning form is as follows:
　　 Location: warning L4xxx:messagetext In these messages, Location refers to the input file related to the error. If there is no input file, it refers to LINK.
　　 When using LINK to connect the target file, the following error messages will appear:
　　 Number LINK Error Message
　　 L1001 option:option name ambiguous
　　 The option name after the option indicator is not unique. For example:
　　 LINK /N main;
　　 The cause of this error is that LINK cannot distinguish which of the three options starting with the letter N is needed.
　　 L1002 option:unrecognized option name
　　 The character after the option indicator (/) is uncertain. For example:
　　 LINK/ABCDEF main:
　　 L1003 /QUICKLIB,/EXEPACK incompatible
　　 Two options that cannot be used at the same time are defined:
　　 /QUICKLIB and/EXEPACK.
　　 L1004 option:invalid numeric value
　　 An invalid value appears in an option of LINK. For example, a value required for a string is assigned to a numeric option.
　　 L1006 option:stack size exceeds 65535 bytes
　　 The parameter value assigned to the / STACKSIZE option exceeds the maximum allowed value:
　　 L1007 option:interrupt number exceeds 255
　　 The parameter value assigned to the / OVERLAYINTERRUPT option exceeds 255.
　　 L1008 option:segment limit set too high
　　 The number limit of segments set by using the / SEGMENTS option exceeds 3072.
　　 L1009 number:CPARMALLOC:illegal value
　　 The value specified in the CPARMAXALLOC option is not between 1_65,535.
　　 L1020 no object modules specified
　　 LINK does not find the target file name.
　　 L1021 Cannot nest response files
　　 A response file is generated in the response file.
　　 L1022 response line too long
　　 The number of characters in a line in the response file exceeds 127.
　　 L1023 terminated by user
　　 The user has entered CTRL+C or CRTL+BREAK.
　　 L1024 nested right parentheses
　　 There is an error in entering the segment content repeatedly in the command line.
　　 L1025 nested left parentheses
　　 There is an error in entering the segment content repeatedly in the command line.
　　 L1026 unmatched right parenthesis
　　 The right parenthesis described in the segment content repeatedly in the command line is missing.
　　 L1027 unmatched left parenthesis
　　 The left parenthesis described in the segment content repeatedly in the command line is missing.
　　 L1043 relocation table overflow
　　 There are long - distance calls, long - distance transfers or other long pointers exceeding 32,768 in the program.
　　 If possible, replace the long pointer with a short pointer. Then re - generate the target module.
　　 L1045 too many TYPDEF records
　　 The target module contains more than 255 TYPDEF records. These records define public variables. This error only occurs in programs generated by the Microsoft FORTRAN compiler or other compilers supporting public variables. TYPDEF is a term in DOS. It is explained in the Microsoft MS DOS Pprogrammer's Reference and other DOS references.
　　 L1046 too many external symbols in one module ,
　　 More than 1023 external symbols are described in the target module. Divide this module into several small modules.
　　 L1047 too many group ,segment,and class names in one module
　　 There are too many group names, segment names and classification names in the program. The number of group names, segment names and classification names must be reduced, and the target file must be re - generated.
　　 L1048 too many segments in one module
　　 The target module contains more than 255 segments. The module should be separated or the segments should be combined.
　　 L1049 too many segments
　　 The number of segments contained in the program exceeds the maximum value. Use the / SEG MENTS option with the default value of 128 to specify the legal maximum number of segments. The default value in the / SEGMENTS selection is 128. It specifies the legal maximum number of segments.
　　 Re - link using the / SEGMENTS option and an appropriate number of segments.
　　 L1050 too many groups in one module
　　 In one module, LINK encounters more than 21 group definitions ((GRPDEF)).
　　 Reduce the number of defined groups or separate modules (for the definition of groups, refer to the Microsoft MS-DOS
　　 Programmer's Reference or other DOS reference books.
　　 L1041 too many groups
　　 The number of groups defined in the program is more than 20, but it is not counted in the DGROUP statement. The number of groups needs to be reduced.
　　 L1052 too many libraries
　　 More than 32 libraries are attempted to be connected.
　　 The libraries should be combined, or modules requiring fewer libraries should be used.
　　 L1053 out of memery for symbol table
　　 There is no fixed limit on the size of the symbol table, but it is limited by the available memory space.
　　 The modules or segments should be combined, and then the target file should be re - generated to reduce public symbols as much as possible.
　　 L1054 requested segment too high
　　 LINK does not have enough space to allocate to the required segment number description table. (The default value is 128 or its value is specified by the / SEGMENTS option).
　　 Re - connect using the / SEGMENTS option to select a smaller number of segments (for example, if the default value has been used, its value is 64), or eliminate the program or shell residing in the memory to release some memory space.
　　 L1056 too many overlays
　　 There are more than 63 definitions of overlays in the program.
　　 L1057 data record too large
　　 The LEDATA record (in the target module) contains more than 1024 bytes of data. This is a compile error. (LEDATA is a term in DOS. It is explained in the Microsoft MS-DOS Programmer's Reference and other DOS reference books.)
　　 Note which translator (compile or assembly) generates the error target module and environment. Report this error to Microsoft using the Product Assistance Request form attached to the document.
　　 L1063 out memory for Code View information
　　 There are too many connected target (.OBJ) files containing debugging information. Turn off the Produce Debug Code option in the Generate EXE file dialog box.L1070 segment size exceeds 64K
　　 The number of codes or data contained in a segment is greater than 64K.
　　 It should be compiled and connected in large mode.
　　 L1071 segment TEXT larger than 65520 bytes
　　 This kind of error usually only occurs in C programs in small mode. But this kind of error will also occur when a program with the segment name _TEXT is connected using the / DOSSEG option. C programs in small mode must reserve code addresses 0 and 1; if for calibration, this range can be increased to 16.
　　 L1072 common area longer than 65536 bytes 
　　 There are more than 64K public variables in the program. This kind of error only occurs in programs generated by compilers supporting public variables.
　　 L1080 cannot open list fileThe disk or root directory is full.
　　 Delete or move out some files to release space.L1081 out of space for run file
　　 The disk where the executable file is located is full.
　　 Release more disk space and restart the LINK program.
　　 L1083 cannot open run file
　　 The disk or root directory is full.
　　 Delete or move out some files to release space.
　　 L1084 cannot open temporary file
　　 The disk or root directory is full.
　　 Release more directory space and restart the LINK program.
　　 L1085 cannot open temporary file 
　　 The disk or root directory is full.
　　 Delete or move out some files to release space.
　　 L1086 scratch file missing
　　 An internal error has occurred
　　 Note the environment of the problem and contact Microsoft using the Product Assistance Reguest form attached to the document.
　　 L1087 unexected end -of-file on scratch file
　　 The disk storing the LINK temporary output file has been removed.
　　 L1088 out space for file
　　 The space for writing the list file on the disk is full.
　　 Release more disk space and restart the LINK program.
　　 L1076 filename:cannot open response file
　　 LINK cannot find the specified response file.
　　 Usually it indicates an input error.

L1090 cannot reopen list file
No original disk is placed under the prompt. Restart the LINK program.
L1091 unexpected end-of-file on library
The disk containing the library may have been erased. Put the disk containing the library back and run the LINK program again.
L1093 object not found
The target file specified for linking in the input was not found. Restart the LINK program and specify the target file.
L1101 invalid object module
An object module is invalid. If this error still occurs after recompilation, contact Microsoft Corporation using the Product Assistance Request form attached to the documentation.
L1102 unexpected end-of-file
Incorrect formatting of the library.
L1103 attempt to access data outside segment bounds
The data defined by the data record in the object module exceeds the end of the segment. This is a translation error. Note the translation program (compiler or assembler) and environment that generated the erroneous object module. Report this error to Microsoft Corporation using the Product Assistance Request form attached to the documentation.
L1104 filename: not valid library
The specified file is not a valid library file. This error interrupts the LINK program.
L1113 unresolved COMDEF: internal error
Note the error environment and contact Microsoft Corporation using the Product Assistance Request form attached to the documentation.
L1114 file not suitable for /EXEPACK; relink without 
For the linked program, the size of the packed image plus the packing overhead space is larger than the unpacked image. Relink without using the /EXEPACK option.
L1115 /QUICKLIB, overlays incompatible
Overlays are specified and the /QUICKLIB option is used. These two cannot be used simultaneously.
L2001 fixup(s) without data
A FIXUPP record with a missing preceding data record occurs. This may be a compilation error. (Refer to the detailed information about FIXUPP.)
L2002 fixup overflow near number in frame segname target seg segname target offset number
The following conditions can cause this error:
·A group is larger than 64K.
·The program contains segments, short-distance jumps or calls.
·The data name in the program conflicts with the name of a library function in the linker.
An EXTRN statement in an assembly language source file within a segment, for example:
code SEGMEMT public'CODE
EXTRNmian:far
startPROCfar
callmain
ret
start ENDP
code ENDS
It should be changed to the following structure:
EXTRN main:far
codeSEGMENT public,CODE.
startPROC far
call main 
ret
start ENDP 
code ENDS
Modify the source code file and regenerate the object file. (Refer to the information about frames and target segments in the Microsoft MS-DOS Programmer's Reference.)
03
Attempt to use a near call or jump to an entry at offset offet in a far segment segname. It needs to be a far call or jump, or make the entry near.
04
LOBYTE fixup address overflow. (Detailed information is in the Microsoft MS-DOS Programmer's Reference Manual.)
05
An assembly type not supported by the Microsoft linker occurs. This may be a compilation error. Note the error environment and contact Microsoft Corporation using the Product Assistance Request form attached to the documentation.
06
Conflict between NEAR and HUGE attributes of public variables. This error only occurs in programs generated by compilers that support public variables.L2012 name: array-element size mismatch
Define a remote public array with a different array element space. (For example, define an array in one pass.) This error can only occur in compilers that support remote public arrays.
L2013 LIDATA record too large
The LIDATA record contains more than 512 bytes. This is usually caused by a compilation error.
L2024 name: symbol already defined
The linker finds a redefinition of a public symbol. Eliminate the redundant definition.
L2025 name: symbol defined more than once
Eliminate redundant symbol definitions in the object file.
L2029 unresolved externals
Define one or more external symbols in one or more modules, but do not define them as public symbols in any module or library. The table of undefinable external parameters will be listed after the error message. For example:
unresolved externals
EXIT in file(s):
MAIN.OBJ(main.for)
OPEN in file(s):
MAIN.OBJ(main.for)
The name before in file(s) is the undefinable external symbol. The next line is the table of target modules that generate these symbols. If the map file exists, this information and table are also written into the map file.
L2041 stack plus data exceed 64K
The sum of the near data and stack space exceeds 64K. Reduce the stack space to avoid this error.
The linker only tests this condition when the /DOSSEG option is enabled. The library startup automatically selects this option.
L2043 Quick library support module missing
The user did not specify, or the linker cannot find the target module or library needed to build the Quick library.
The library provided in the QuickBASIC environment is called BQLB45.LIB.
L2044 name: symbol multiply defined, use/NOE
The linker finds a possible redefinition of a public symbol. This error is usually caused by redefining a symbol that is already defined in the library. Reconnect using the /NOEXTDICTIONARY option.
This error in the merge and the description of the L2025 error for the same symbol are indeed redefinition errors.
L4011 PACKCODE value exceeding 65500 unreliable
The segment space for packing code longer than 65,500 bytes in the Intel 80286 processor may be unreliable.
L4012 load-high disables EXEPACK
The /HIGH and /EXEPACK options cannot be used simultaneously.
L4015 /CODEVIEW disablesl/DSALLOCATE
The /CODEVIEW and /DSALLOCATE options cannot be used simultaneously
L4016/CODVIEW disables/EXEPACK
The /CODEVIEW and /EXEPACK options cannot be used simultaneously
L4020 name code-segment size exceeds 65500
A code segment of 65,501-65,536 bytes in the Intel 80286 processor may be unreliable.
L4021 nostack segment
This program does not contain a stack segment defined with the STACK combination type. This information does not appear when using modules compiled with Microsoft QuickBASIC, but may appear when using assembly language modules.
Normally, every program should define a stack segment with the STACK combination type. This error message can be ignored when there is a special reason for not defining a stack or not defining a stack with the STACK combination type. Using a LINK version before 2.4 to link may cause this error because these linkers only search the library once.
L4031 name: segment declared in more than one groupA segment is defined as a member of two different groups.
Modify the source file and regenerate the object file.
L4034 more than 239 overlay segments: extra put in rootThere are more than 239 segments for overlays in the program. When this error occurs, segments from 234 onwards are placed in the root, that is, the resident part.
L4045 name of output file is name
The default value for the prompt of the running file field is inaccurate because the /QUICKLIB option was not used in time. The name of the Quick library will be given in the error message.
L4050 too many public symbols for sorting
The number of public symbols exceeds the space available for symbol sorting required by the /MAP option. These symbols are not sorted.
L4051 fiename: cannot find library
The linker cannot find the specified file.
Enter a new file name, new path name, or path plus file name.
L4053 VM.TMP: illegal file name: ignored
VN.TMP appears as the target file name. Change the file name and relink.
L4045 fiename: cannot find file
The linker cannot find the specified file. Enter a new file name, new path name, or path plus file name.
1.4 Library error messages
The error message format generated by the Microsoft library management system, LIB, is as follows:
{filename |LIB}: fatal error U1xxx: messagetext
{filename |LIB}: error U2xxx: messagetxt
{filename |LIB}: warning U4xx: messagetext
If the input file name (filename) exists, the message starts with that name; otherwise, it starts with the name of the application system. If possible, LIB displays a warning and continues running. When a fatal error occurs, LIB stops running.
LIB can display the following error messages:
Number LIB Error Message
U1150 page size too small
The page size of the input library is too small. This indicates that the input library file is invalid.
U1151 syntax error: illegal file specification
There is no module name after the command operator such as a minus sign (_).
U1152 syntax error: option name missing
There is no option after the slash (/).
U1153 syntax error: option value missing
There is no value after the /PAGESIZE option.
U1154 option unknown
The option is not recognized. Currently, .LIB only recognizes the /PAGESIZE option.
U1155 syntax error: illegal input
The command does not conform to the correct library syntax described in "DOS Compilation and Linking".
U1156 synuax error
The command does not conform to the correct library syntax described in Appendix G "DOS Compilation and Linking".
U1157 comma or new line missing
A comma or carriage return is missing in the command line. This means that the position of the comma in the command line may be incorrect.
For example:
LIB math.lib,mod1+mod2;
The correct format is as follows:
LIB math.lib,mod1+mod2;
U1158 terminator missing
The response to the "Output Library" prompt or the last line of the response file starting the library LIB has no carriage return end mark.
U1161 cannot rename old library
LIB cannot change the extension of the old library name to .BAK because the .BAK form already exists in write-protected mode. Change the protection mode of the old .BAK.
U1162 cannot reopen library
The old library cannot be opened after changing to the .BAK extension.
U1163 error writing to cross-reference file
The disk or root directory is full.
Delete or move files to free up space.
U1170 too many symbols
The number of symbols in the library file exceeds 4096.
U1171 insufficient memory
There is not enough memory to run the library.
Delete some shell or resident programs, or increase memory space, then run again.
U1172 no more virtual memory
Note the error environment and notify Microsoft Corporation using the Produce Assistance Request form attached to the documentation.
U1173 internal failure
Note the error environment and notify Microsoft Corporation using the Produce Assistance Request form attached to the documentation.
U1174 mark: not allocated
Note the error environment and notify Mircosoft Corporation using the Produce Assistance Request form attached to the documentation.
U1175 free: not allocated
Note the error environment and notify Mircosoft Corporation using the produce Assistance Request form attached to the documentation.
U1180 write to extract file failed
The disk or root directory is full
Delete or move files to free up space.
U1181 Write to library file failed
Delete or move files to free up space.U1182 filename: cannot create extract file
The disk or root directory is full, or the specified file to be read already exists in write-protected mode.
Free up disk space or change the protection of the read file.
U1183 cannot open response file
The response file was not found.
U1184 unexpected end-of-file on command input
The end-of-file character appears too early in the response to the prompt.
U1185 cannot create new library
The disk or root directory is full, or the library file already exists in write-protected mode.
Free up disk space or change the protection of the library file.
U1186 error writing to new library
The disk or root directory is full.
Delete or move files to free up space.
U1187 cannot open VW.TMP
Delete or move files to free up space.
U1188 cannot write to VM
Note the error environment and notify Microsoft Corporation using the Produce Assistance Request form attached to the documentation.
U1189 cannot read from VM
Note the error environment and notify Microsoft Corporation using the Prpduce Assistance Request form attached to the documentation.
U1190 interrupted by user
The user used the CTRL+C or CTRL+BREAK key.
U1200 name: invalid library header
The format of the input library file is incorrect. This file is not a library file, or the file is damaged.
U1203 name: invalid object module near location
The module indicated by the name is not a valid object module.
U2152 fileme: cannot create listing
The disk or directory is full, or the cross-reference table file already exists in write-protected mode.
U2155 modulenme: module not in library; ignored
The specified module was not found in the input library.
U2157 filename: cannot access file
The library cannot open the file used.
U2158 libraryname: invalid
libray header; file ignored
The format of the input library is incorrect
U2159 filename:invalideformat hexnumber;ignored
The feature byte or hexnumber word of the file is not one of the following recognizable types:
Microsoft library, Intel library, Microsoft object, or XENIX archive
U4150 modulename: module redefinition ignored
The module added to the library has the same name as an existing module in the library. Or, multiple modules with the same name are found in the library.
U4151 symbol: symbol redefined in module modulename, redefinition ignored
The specified symbol is described in multiple modules.
U4153 number: page size too small; ignored
The value specified in the /PAGE option is less than 16.
U4155 modulename: module not in library
The updated module is not in the library. .LIB adds this module to the library.
U4156 libraryname: output-library specification ignored
Add a new library name to the specified output library. For example:
LIB new.lib+one.obj,new.lst.lib
This error will occur if new lib does not exist.
U4157 Insufficient memory, extended dictionary not created.
LIB cannot create an extended directory, and this library is still valid. However, the LINK program cannot use the advantages of the extended library to speed up linking.
U4158 Internal error, extended dictionary not created.
LIB cannot create an extended directory, and this library is still valid. However, the LINK program cannot use the advantages of the extended library to speed up linking.