685 A P P E N D I X A Error Messages The error messages generated by MASM components fall into three categories: u u u Fatal errors. These indicate a severe problem that prevents the utility from completing its normal process. Nonfatal errors. The utility may complete its process. If it does, its result is not likely to be the one you want. Warnings. These messages indicate conditions that may prevent you from getting the results you want.
686 Environment and Tools Table A.
Appendix A Error Messages Table A.
688 BSCMAKE Error Messages BSCMAKE Error Messages Microsoft Browser Database Maintenance Utility (BSCMAKE) generates the following error messages: u Fatal errors (BK1xxx) cause BSCMAKE to stop execution. u Warnings (BK4xxx) indicate possible problems in the database-building process. BSCMAKE Fatal Error Messages BK1500 UNKNOWN ERROR Contact Microsoft Product Support Services BSCMAKE detected an unknown error condition.
Error! Style not defined. BK1505 689 cannot read from file filename BSCMAKE could not read from the given file. One of the following may have occurred: BK1506 u The file was corrupt. u The file was truncated. Truncation can occur if the compiler runs out of disk space or is interrupted when it is creating the .SBR file. cannot open file filename BSCMAKE could not open the given file. One of the following may have occurred: u u u u u BK1507 No more file handles were available.
90 BSCMAKE Error Messages BK1509 out of heap space BSCMAKE ran out of memory. One of the following may be a solution: u Reduce the memory that BSCMAKE will require by using one or more options. Use /Ei or /Es to eliminate some input files. Use /Em to eliminate macro bodies. u Run BSCMAKE (or PWB if you are building a database in PWB) in an MS-DOS session within Windows to use virtual memory provided under the Windows operating system.
Error! Style not defined. BK1513 691 nonincremental update requires all .SBR files An attempt was made to build a new database, but one or more of the specified .SBR files was truncated. This message is always preceded by warning BK4502, which will give the name of the .SBR file that caused the error. BSCMAKE can process a truncated, or zero-length, .SBR file only when a database already exists and is being incrementally updated.
692 CodeView C/C++ Expression Evaluator Errors BK4502 truncated .SBR file filename not in database The given zero-length .SBR file, specified during a database update, was not originally part of the database. If a zero-length file that is not part of the original build of the database is specified during a rebuild of that database, BSCMAKE issues this warning. One of the following may be a cause: BK4503 u The wrong database name was specified. u The database was deleted (error BK1513 will result).
Error! Style not defined. CAN0005 693 operator not supported An unsupported C operator was specified in an expression. You can usually write an equivalent expression using the supported C operators. CAN0006 missing left parenthesis Unbalanced parentheses were found in the expression. Retype the expression with balanced parentheses. CAN0007 missing right parenthesis Unbalanced parentheses were found in the expression. Retype the expression with balanced parentheses.
694 CodeView C/C++ Expression Evaluator Errors CAN0015 expression too complex (stack overflow) The expression entered was too complex or nested too deeply for the amount of storage available to the C expression evaluator. Overflow usually occurs because of too many pending calculations. Rearrange the expression so that each component of the expression can be evaluated as it is encountered, rather than having to wait for other parts of the expression to be calculated.
Error! Style not defined. CAN0020 695 operand types bad for this operation An operator was applied to an expression with an invalid type for that operator. For example, it is not valid to take the address of a register, or subscript an array with a floating-point expression. CAN0021 struct or union used as scalar A structure or union was used in an expression, but no element was specified.
696 CodeView C/C++ Expression Evaluator Errors CAN0028 not struct/union element An expression of the form Struct.Member or pStruct->Member was specified, but member is not an element of the structure. The expression may not be parenthesized correctly. CAN0029 not struct pointer The member-selection operator (->) was applied to an expression that is not a pointer to a structure.
Error! Style not defined. CAN0034 697 types incompatible with operator The operand types specified are not legal for the operation. For example, a pointer cannot be multiplied by any value. You may need to type cast the operands to a type compatible with the operator. CAN0035 overlay not resident An attempt was made to access an overlay that is not currently resident in RAM. Execute the program until the overlay is loaded. CAN0036 bad context {...
698 CodeView C/C++ Expression Evaluator Errors CAN0039 symbol is ambiguous The CodeView C expression evaluator cannot determine which instance of a symbol to use in an expression. The symbol occurs more than once in the inheritance tree. You must use the scope resolution operator (::) to explicitly specify the instance to use in the expression. CAN0040 function requires implicit conversion Implicit conversions involving constructor calls are not supported by the CodeView C expression evaluator.
Error! Style not defined. CAN0048 calling sequence not supported A function specified in the expression uses a calling sequence not supported by the CodeView C expression evaluator. You cannot call this function in a CodeView expression. CAN0049 obsolete OMF - please relink program The program used an old OMF (Object Module Format). 699 The program must be linked with LINK version 5.30 or later, and packed with CVPACK version 4.0 or later.
700 CodeView Error Messages CAN0059 left operand is class not a function name The left operand of a function call was a class name and could not be resolved to a function call. This error can be caused by omitting the name of a member function in an expression. CAN0060 register is not available An expression specified a register that cannot be used.
Error! Style not defined. CV0002 701 no such file or directory The specified file does not exist or a path does not specify an existing directory. Check the file or directory name in the most recent command. One of the following may have occurred: CV0003 u The View Source (VS) command or the Open Source command from the File menu was used to view a nonexistent file. u An attempt was made to print to a nonexistent file or directory.
702 CodeView Error Messages CV0012 out of memory CodeView was unable to allocate or reallocate the memory that it required because not enough memory was available. Possible solutions include the following: CV0013 u Recompile without symbolic information in some of the modules. CodeView requires memory to hold information about the program being debugged. Compile some modules with the /Zd option instead of /Zi, or don’t use either option.
Error! Style not defined. CV0024 703 too many open files CodeView could not open a file it needed because a file handle was not available. Increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=50 is the recommended setting. The program being debugged may have so many files open that all available handles are exhausted. Check that the program has not left files open unnecessarily.
704 CodeView Error Messages CV0104 CodeView information for filename is newer than this version of CodeView The executable file was compiled or linked with a version of a Microsoft compiler that is newer than the version of CodeView you are using. Try one of the following: CV1001 u Reinstall CodeView that came with the new compiler. u Remove older versions of CodeView that may be present on your hard disk. u Recompile the program with an older version of a Microsoft compiler.
Error! Style not defined. CV1007 705 unable to open file The specified file cannot be opened. One of the following may have occurred: u The file may not exist in the specified directory. u The filename was misspelled. u The file’s attributes are set so that it cannot be opened. u A locking or sharing violation occurred. CV1011 no previous regular expression The Repeat Last Find command was executed, but a regular expression (search string) was not previously specified.
706 CodeView Error Messages CV1021 unknown format specifier; specify one of A,B,I,IU,IX,L,LU,LX,R,RL,RT An unknown format specifier was given to a View Memory (VM), Memory Dump (MD), or Memory Enter (ME) command.
Error! Style not defined. CV1031 707 no source lines at this address An attempt was made to view an address that does not have source code. This error can be caused by debugging a program whose source has been modified after it was compiled. Recompile the file before debugging it with CodeView. CV1039 not a text file An attempt was made to load a file that is not a text file. The file may be binary data.
708 CodeView Error Messages CV1046 invalid executable file: relink The executable file did not have a valid format. One of the following may have occurred: CV1047 u The executable file was not created with the linker released with this version of CodeView. Relink the object code using the current version of LINK.EXE. u The .EXE file may have been corrupted. Recompile and relink the program.
Error! Style not defined. CV1053 709 TOOLS.INI not found The directory listed in the INIT environment variable did not contain a TOOLS.INI file. Check the INIT variable to be sure that it points to the correct directory. CV1054 cannot read this version of CURRENT.STS The state file (CURRENT.STS) has a version number that is not recognized by this version of CodeView. The old CURRENT.STS was ignored, and a new one will be created when CodeView exits.
710 CodeView Error Messages CV1063 cannot create CURRENT.STS CodeView could not find an existing state file (CURRENT.STS), and CodeView tried to create one but failed. One of the following may have occurred: CV1064 u There was not enough space either on the disk containing the program to be debugged or on the disk pointed to by the INIT environment variable. u There were not enough free file handles. Increase the number of file handles by changing the FILES setting in CONFIG.
Error! Style not defined. CV1250 711 general expression-evaluator error An error occurred in a CodeView expression evaluator. This error is probably caused by a lack of memory available to the expression evaluator. You can free memory by doing one or more of the following: u Close windows that are not needed. The Memory window should be closed if possible. u Delete breakpoints that are not needed. u Disable options that are not needed.
712 CodeView Error Messages CV2209 cannot restart; current process is not the process being debugged The debugging session was halted, and a different process was started. Return to the debugged program’s process by setting a breakpoint in it and issue a Go command. CV2210 invalid tab setting; using 8 The value for tabs cannot be less than 0 or greater than 19. If you supply a value that is not in this range, the default tab value is 8.
Error! Style not defined. CV3608 713 out of memory CodeView needed additional memory, but insufficient memory was available. Possible solutions include the following: u Remove some drivers or applications that have been loaded in high memory. u Recompile without symbolic information in some of the modules. CodeView requires memory to hold information about the program being debugged. Compile some modules with the /Zd option instead of /Zi, or don’t use either option.
714 CodeView Error Messages CV3625 no transport layer; exiting CodeView needs a transport layer to make appropriate calls to the operating system in local debugging and to a remote computer in remote debugging. Check your TOOLS.INI file, and make sure there is a Transport entry in the [cv] or [cvw] CodeView section. CV3626 no execution model; exiting CodeView needs an execution model in order to function. Check your TOOLS.INI file, and make sure there is a Native entry specified.
Error! Style not defined. CV4003 715 assembler: illegal range The size of a specified value exceeds the size expected by the instruction. The instruction was rejected and the address was not advanced. CV4004 assembler: overflow Numeric overflow occurred while assembling the current instruction. The instruction was rejected and the address was not advanced. CV4005 assembler: syntax error The syntax for the instruction is incorrect. The instruction was rejected and the address was not advanced.
716 CodeView Error Messages CV4011 assembler: divide by zero CodeView encountered a divide-by-zero error while assembling the current instruction. The instruction was rejected and the address was not advanced. CV4012 cannot assemble code with current execution model This error can be caused by trying to assemble p-code in CodeView. CV4500 bad fixed format length: using variable length In invalid length was specified for the Memory window.
Error! Style not defined. CV5013 717 no expression evaluators found; exiting CodeView needs at least one expression evaluator in order to operate. Check the [cv] or [cvw] section of your TOOLS.INI file and specify at least one Eval entry. CV5014 cannot execute function in watch expression A watch expression cannot specify a function to be executed.
718 CVPACK Error Messages CK1001 out of memory The executable file is too big for the available memory. This error can occur with MSDOS when there is little extra memory. Even though CVPACK uses virtual memory, which involves swapping to disk, some information can be stored only in real memory. One of the following may be a solution: CK1002 u Assemble and link in separate steps (that is, use NMAKE). u Recompile one or more of the object files without debugging information.
Error! Style not defined. CK1007 719 invalid table table in module module The given table in the given object file was not valid. Check the compiler and linker versions. CK1008 cannot write packed information There was not enough space on disk for CVPACK to write the packed executable file. This leaves a corrupt file on disk. Make more space available on disk and relink the program.
720 CVPACK Error Messages CK1013 debugging information missing or unknown format One of the following has occurred: u The program did not contain debugging information. Recompile using /Zi or /Zd, then link using /CO. u The executable file was linked using an obsolete or unsupported linker. Use Microsoft LINK version 5.3x or later. u The executable file was already packed using a previous version of CVPACK.
Error! Style not defined. CK1020 721 packed type index exceeds 65535 in module module The debugging information exceeded a CVPACK limit. This error may occur when precompiled headers are used. One of the following may be a solution: CK1021 u Eliminate unused type strings. u Compile some object files without debugging information. error in precompiled types signature in module module The program was compiled with an out-of-date precompiled header. Delete the object file and recompile.
722 EXEHDR Error Messages EXEHDR Fatal Error Messages U1110 malformed number number A command-line option for EXEHDR required a value, but the given number was mistyped. U1111 option requires value A command-line option for EXEHDR required a value, but no value was specified or the specified value was in an illegal format for the given option.
Error! Style not defined. U1140 723 out of memory There was not enough memory for EXEHDR to decode the header of the executable file. Math Coprocessor Error Messages The error messages listed below correspond to exceptions generated by the math coprocessor hardware. Refer to the manufacturer’s documentation for your processor for a detailed discussion of hardware exceptions. These errors may also be detected by the floating-point emulator or alternate math library.
724 Math Coprocessor Error Messages M6107 unemulated An attempt was made to execute a coprocessor instruction that is invalid or is not supported by the emulator. This error terminates the program with exit code 135. M6108 square root The operand in a square-root operation was negative. This error terminates the program with exit code 136. The sqrt function in the C run-time library and the FORTRAN intrinsic function SQRT do not generate this error.
Error! Style not defined. M6203 725 function : _OVERFLOW error The given function result was too large to be represented. This error calls the _matherr function with the function name, its arguments, and the error type. You can rewrite the _matherr function to customize the handling of certain run-time floating-point math errors. M6205 function : _TLOSS error A total loss of significance (precision) occurred.
726 H2INC Error Messages HI1012 unmatched parenthesis nesting - missing character The parentheses in a preprocessor directive were not matched. The missing character is either a left, (, or right, ), parenthesis. HI1016 #if[n]def expected an identifier An identifier must be specified with the #ifdef and #ifndef directives. HI1017 invalid integer constant expression The expression in an #if directive either did not exist or did not evaluate to a constant.
Error! Style not defined. HI1026 727 parser stack overflow, please simplify your program The program cannot be processed because the space required to parse the program causes a stack overflow in the compiler. Simplify the program by decreasing the complexity of expressions. Decrease the level of nesting in for and switch statements by putting some of the more deeply nested statements in separate functions. Break up very long expressions involving ',' operators or function calls.
728 H2INC Error Messages HI1048 This error existed in previous versions of H2INC as “unknown option character in option.” This condition now generates warning HI4799. HI1049 This error existed in previous versions of H2INC as “invalid numerical argument string.” This condition now generates warning HI4052. HI1050 segment : code segment too large A code segment grew to within 36 bytes of 64K during compilation.
Error! Style not defined. HI2001 729 newline in constant A string constant was continued onto a second line without either a backslash or closing and opening quotes. To break a string constant onto two lines in the source file, do one of the following: u End the first line with the line-continuation character, a backslash, \ . u Close the string on the first line with a double quotation mark, and open the string on the next line with another quotation mark.
730 H2INC Error Messages printf("Hello,\ \nworld"); or printf("Hello,\n" "world"); or printf("Hello," "\nworld"); HI2003 expected defined id An identifier was expected after the preprocessing keyword defined. HI2004 expected defined(id) An identifier was expected after the left parenthesis, (, following the preprocessing keyword defined. HI2005 #line expected a line number, found token A #line directive lacked the required line-number specification.
Error! Style not defined. HI2014 preprocessor command must start as first non-white-space Non-white-space characters appeared before the number sign (#) of a preprocessor directive on the same line. HI2015 too many characters in constant A character constant contained more than one character. 731 Note that an escape sequence (for example, \ t for tab) is converted to a single character.
732 H2INC Error Messages HI2028 struct/union member needs to be inside a struct/union Structure and union members must be declared within the structure or union. This error may be caused by an enumeration declaration containing a declaration of a structure member, as in the following example: enum a { january, february, int march; /* Illegal structure declaration */ }; HI2030 identifier : struct/union member redefinition The identifier was used for more than one member of the same structure or union.
Error! Style not defined. HI2042 733 signed/unsigned keywords mutually exclusive The keywords signed and unsigned were both used in a single declaration, as in the following example: unsigned signed int i; HI2056 illegal expression An expression was illegal because of a previous error, which may not have produced an error message. HI2057 expected constant expression The context requires a constant expression.
734 H2INC Error Messages HI2065 identifier : undefined An attempt was made to use an identifier that was not defined. HI2066 cast to function type is illegal An object was cast to a function type, which is illegal. However, it is legal to cast an object to a function pointer. HI2067 cast to array type is illegal An object was cast to an array type. HI2068 illegal cast A type used in a cast operation was not legal for this expression.
Error! Style not defined. HI2050 nonintegral switch expression A switch expression did not evaluate to an integral value. HI2051 case expression not constant Case expressions must be integral constants. HI2052 case expression not integral Case expressions must be integral constants. HI2054 expected '(' to follow identifier The context requires parentheses after the function identifier.
736 H2INC Error Messages HI2084 function function already has a body The function has already been defined. HI2086 identifier : redefinition The given identifier was defined more than once, or a subsequent declaration differed from a previous one.
Error! Style not defined. 737 HI2092 array element type cannot be function Arrays of functions are not allowed. Arrays of pointers to functions are allowed. HI2095 function : actual has type void : parameter number An attempt was made to pass a void argument to a function. The given number indicates which argument was in error. Formal parameters and arguments to functions cannot have type void. They can, however, have type void * (pointer to void).
738 H2INC Error Messages HI2113 pointer subtracted from nonpointer The right operand in a subtraction operation using the minus (-) operator was a pointer, but the left operand was not. HI2114 operator : pointer on left; needs integral right The left operand of the given operator was a pointer; so the right operand must be an integral value. HI2115 identifier : incompatible types An expression contained incompatible types.
Error! Style not defined. HI2132 syntax error : unexpected identifier An identifier appeared in a syntactically illegal context. HI2133 identifier : unknown size An attempt was made to declare an unsized array as a local variable. HI2134 identifier : struct/union too large The size of a structure or union exceeded the 64K compiler limit. HI2136 function : prototype must have parameter types A function prototype declarator had formal-parameter names, but no types were provided for the parameters.
740 H2INC Error Messages HI2146 syntax error : missing token before identifier identifier The compiler expected the given token to appear before the given identifier. HI2147 unknown size An attempt was made to increment an index or pointer to an array whose base type has not yet been declared. HI2148 array too large An array exceeded the maximum legal size of 64K. Either reduce the size of the array, or declare it with _huge.
Error! Style not defined. 741 HI2157 function : must be declared before use in pragma list The function name in the list of functions for an alloc_text pragma has not been declared prior to being referenced in the list. HI2158 identifier : is a function The given identifier was specified in the list of variables in a same_seg pragma but was previously declared as a function.
742 H2INC Error Messages HI2171 operator : illegal operand The given unary operator was used with an illegal operand type, as in the following example: int (*fp)(); double d,d1; fp++; d = ~d1; HI2172 function : actual is not a pointer : parameter number An attempt was made to pass an argument that was not a pointer to a function that expected a pointer. The given number indicates which argument was in error.
Error! Style not defined. HI2185 743 identifier : illegal _based allocation A _based-allocated variable that explicitly has extern storage class and is uninitialized may not have a base of any of the following: (_segment) & var _segname("_STACK") (_segment)_self void If the variable does not explicitly have extern storage class or it is uninitialized, then its base must use _segname("string") where string is any segment name or reserved segment name except "_STACK".
744 H2INC Error Messages HI2208 no members defined using this type An enum, struct, or union was defined without any members. This is an error only when compiling with /Za; otherwise, it is a warning. HI2209 type cast in _based construct must be (_segment) The only type allowed within a cast in a _based declarator is (_segment). HI2210 identifier : must be near/far data pointer The base in a _based declarator must not be an array, a function, or a _based pointer.
Error! Style not defined. HI2217 745 attribute1 must be used with attribute2 The first function attribute requires the second attribute to be used. Some causes for this error include u An interrupt function explicitly declared as near. Interrupt functions must be far. u An interrupt function or a function with a variable number of arguments, when that function is declared with the _fortran, _ pascal, or _fastcall attribute.
746 H2INC Error Messages HI2224 left of .member must have struct/union type The left operand of the '.' operator is not a struct/union type. This error can occur when the left operand is an undefined variable. Undefined variables have type int. HI2225 tagname : first member of struct is unnamed The struct with the given tag started with an unnamed member (an alignment member). Struct definitions must start with a named member.
Error! Style not defined. HI4004 (level 1) 747 missing ')' after defined The closing parenthesis was missing from an #if defined phrase. The compiler assumes a right parenthesis, ), after the first identifier it finds. It then attempts to compile the remainder of the line, which may result in another warning or error.
748 H2INC Error Messages HI4010 (level 1) identifier is a MASM keyword This warning is issued if the .h include file tries to redefine a MASM keyword. H2INC will give a warning whenever such conflicts take place. This includes #define, typedef, structures, and other variables. If you want to redefine a MASM keyword, use #define instead. A #define in the .INC file will not try to redefine the MASM keyword unless the /Ht option is set.
Error! Style not defined. HI4022 (level 1) 749 function : pointer mismatch : parameter number The pointer type of the given parameter was different from the pointer type specified in the argument-type list or function definition. The parameter will be passed without change. Its value will be interpreted as a pointer within the called function.
750 H2INC Error Messages HI4042 (level 1) identifier : has bad storage class The storage class specified for identifier cannot be used in this context. The default storage class for this context was used in place of the illegal class: u If identifier was a function, the compiler assumed extern class. u If identifier was a formal parameter or local variable, the compiler assumed auto class. u If identifier was a global variable, the compiler assumed the variable was declared with no storage class.
Error! Style not defined. HI4050 (level 4) 751 operator : different code attributes The function-pointer expressions used with operator had different code attributes. The attribute involved is either _export or _loadds. This is a warning and not an error, because _export and _loadds affect only entry sequences and not calling conventions. HI4051 (level 2) type conversion, possible loss of data Two data items in an expression had different base types, causing the type of one item to be converted.
752 H2INC Error Messages HI4072 (level 1) function : no function prototype on _fastcall function A _fastcall function was called without first being prototyped. Functions that are _fastcall should be prototyped to guarantee that the registers assigned at each point of call are the same as the registers assumed when the function is defined. A function defined in the new ANSI style is a prototype.
Error! Style not defined. HI4085 (level 1) 753 expected [on | off] The pragma expected an on or off parameter, but the specified parameter was unrecognized or missing. The pragma was ignored. HI4086 (level 1) expected [1 | 2 | 4] The pragma expected a parameter of either 1, 2, or 4, but the specified parameter was unrecognized or missing.
754 H2INC Error Messages HI4091 (level 2) no symbols were declared The compiler detected an empty declaration, as in the following example: int ; The declaration was ignored. HI4092 (level 2) untagged enum/struct/union declared no symbols The compiler detected an empty declaration using an untagged structure, union, or enumerated variable. The declaration was ignored. For example, the following code causes this warning: struct { . . .
Error! Style not defined. HI4105 (level 1) 755 identifier : code modifiers only on function or pointer to function The given identifier was declared with a code modifier that can be used only with a function or function pointer. The code modifier was ignored. HI4109 (level 1) unexpected identifier identifier The pragma contained an unexpected token. The pragma was ignored. HI4110 (level 1) unexpected token int constant The pragma contained an unexpected integer constant. The pragma was ignored.
756 H2INC Error Messages HI4119 (level 1) different bases name1 and name2 specified The _based pointers in the expression have different symbolic bases. There may be truncation or loss in the code generated. HI4120 (level 1) _based/unbased mismatch The expression contains a conversion between a _based pointer and another pointer that is unbased. Some information may have been truncated. This warning commonly occurs when a _based pointer is passed to a function that accepts a near or far pointer.
Error! Style not defined. HI4130 (level 4) 757 operator : logical operation on address of string constant The operator was used with the address of a string literal. Unexpected code was generated. For example, the following code causes this warning: char *pc; pc = "Hello"; if (pc == "Hello") ... The if statement compares the value stored in the pointer pc to the address of the string “Hello” which is separately allocated each time it occurs in the code.
758 H2INC Error Messages HI4136 (level 4) conversion between different floating types Information was lost or truncated between two floating types. For example, the following code causes this warning: double doublevar; float floatvar; floatvar = doublevar; Note that unsuffixed floating-point constants have type double, so the following code causes this warning: floatvar = 1.
Error! Style not defined. HI4139 (level 1) 759 hexnumber : hex escape sequence is out of range A hex escape sequence appearing in a character or string constant was too large to be converted to a character. If in a string constant, the compiler cast the low byte of the hexadecimal number to a char. If in a char constant, the compiler made the cast and then sign extended the result. If in a char constant and compiled with /J, the compiler cast the value to an unsigned char.
0 H2INC Error Messages HI4204 (level 3) function : in-line assembler precludes global optimizations The use of in-line assembler in the named function prevented the specified global optimizations (/Oe, /Og, or /Ol) from being performed. HI4205 (level 4) statement has no effect The indicated statement will have no effect on the program execution.
Error! Style not defined. HI4323 (level 3) 761 potential divide by 0 The second operand in a divide operation evaluated to zero at compile time, giving undefined results. The 0 operand may have been generated by the compiler, as in the following example: func1() { int i,j,k; i /= j && k; } HI4324 (level 3) potential mod by 0 The second operand in a remainder operation evaluated to zero at compile time, giving undefined results.
762 HELPMAKE Error Messages HI4812 (level 1) static variable declaration not accepted with /Mn switch H2INC does not translate static items, as they are not visible outside the C source file. HI4815 (level 1) string : EQU string truncated to 254 characters A #define statement exceeded 254 characters, the maximum length of a MASM EQU statement. The string was truncated.
Error! Style not defined. H1001 763 /E compression level must be numeric The /E option requires either no argument or a numeric value in the range 0–15. The correct form is: /En where n specifies the amount of compression requested. H1002 multiple /O parameters specified Only one output file can be specified with the /O option. H1003 invalid /S file-type identifier The /S option was given an argument other than 1, 2, or 3. The /S option requires specification of the type of input file.
764 HELPMAKE Error Messages H1052 encode requires /O option Database encoding was requested without a specified output-file name for the operation. H1053 compression level exceeds 15 A value greater than 15 was specified with the /E option. The /E option requires either no argument or a numeric value in the range 0–15. The correct form is: /En where n specifies the amount of compression requested.
Error! Style not defined. H1107 765 cannot overwrite input file The /DS option for splitting a concatenated Help file was specified, but the Help file contained a database with the same name as the Help file. It may be that the Help file is not a concatenated file and contains only one database, and the database has the same name as its physical Help file. One of the following may be a solution: H1200 u Rename the Help file so that the filename does not match any of the database names.
766 HELPMAKE Error Messages H1303 unknown RTF attribute An unknown RTF formatting command was found. One of the following may have occurred: H1304 u A new RTF attribute was used. HELPMAKE recognizes a set of attributes that were current at the time this version of HELPMAKE was created. It interprets some of the attributes and knows to ignore the others. Any RTF attribute defined after HELPMAKE was created is not known by HELPMAKE and will cause this error. u The RTF file is corrupted.
Error! Style not defined. H1990 767 internal compression error This message indicates an internal HELPMAKE error. Note the circumstances of the error and notify Microsoft Corporation by following the instructions in the “Microsoft Support Services” section of the introduction to this book. HELPMAKE Error Messages H2000 line too long, truncated A line exceeded the fixed width specified by the /W option or the default of 76 characters. HELPMAKE truncated the extra characters.
768 IMPLIB Error Messages H4003 negative left indent Topic text in an RTF file was formatted with a left indent to a position to the left of column 1. HELPMAKE deleted all text preceding column 1. IMPLIB Error Messages Microsoft Import Library Manager (IMPLIB) generates the following error messages: u Fatal errors (IM16xx) cause IMPLIB to stop execution. u Errors (IM26xx) prevent IMPLIB from creating an import library. Warnings (IM46xx) indicate possible problems in the output file being created.
Error! Style not defined. 769 IM1604 filename : cannot open file—message IMPLIB could not find the specified module-definition (.DEF) file or dynamic-link library (DLL) for the given reason. IM1605 too many nested include files in module-definition file A module-definition (.DEF) file contained an INCLUDE statement specifying a nested set of include files that exceeded the limit for nesting. The limit is 10 levels.
770 LIB Error Messages LIB Error Messages This section lists error messages generated by the LIB utility. Microsoft Library Manager (LIB) generates the following error messages: u Fatal errors (U1150 through U1203) cause LIB to stop execution. u Errors (U2152 through U2159) do not stop execution but prevent LIB from creating a library. u Warnings (U4150 through U4158) indicate possible problems in the library being created.
Error! Style not defined. U1157 771 comma or newline missing A comma or newline character was expected in the command line but did not appear. One cause of this error is an incorrectly placed comma, as in the following command line: LIB math.lib, -mod1 +mod2; The line must be entered as follows: LIB math.lib -mod1 +mod2; U1158 terminator missing The last line of the response file supplied to LIB did not end with a newline character.
772 LIB Error Messages U1172 no more virtual memory The LIB session required more memory than the 1-megabyte limit imposed by LIB. Try using the /NOE option or reducing the number of object modules. U1173 internal failure Note the circumstances of the error and notify Microsoft Corporation by following the instructions in the “Microsoft Support Services” section of the introduction to this book.
Error! Style not defined. U1187 773 cannot open temporary file VM.TMP The disk or root directory was full. Delete or move files to make space. U1188 insufficient disk space for temporary file The library manager cannot write to the virtual memory. Note the circumstances of the error and notify Microsoft Corporation by following the instructions in the “Microsoft Support Services” section of the introduction to this book.
774 LIB Error Messages U2155 module : module not in library; ignored The specified module was not found in the input library. One cause of this error is a filename or directory containing a a hyphen or dash (–). LIB interprets the dash as the operator for the delete command. This error occurs if you install a Microsoft language product in a directory that has a dash in its path, such as C:\MS-C.
Error! Style not defined. U4156 775 library : output-library specification ignored A new library was created because the filename specified in the oldlibrary field did not exist. However, a filename was also specified in the newlibrary field. LIB ignored the newlibrary specification. For example, both of the following command lines cause this error if PROJECT.LIB does not already exist: LIB project.lib +one.obj, new.lst, project.lib LIB project.lib +one.obj, new.lst, new.
776 LINK Error Messages L1003 /Q and /EXEPACK incompatible LINK cannot be given both the /Q option and the /EXEPACK option. L1004 value : invalid numeric value An incorrect value was specified with a LINK option. For example, this error occurs if a nonnumeric string is specified with an option that requires a number. L1005 option : packing limit exceeds 64K The value specified with the /PACKC or /PACKD option exceeded the limit of 65,536 bytes.
Error! Style not defined. L1020 777 no object files specified The object-files field was empty. LINK requires the name of at least one object file. L1021 cannot nest response files A response file was specified in a response file. L1022 response line too long A line in a response file was longer than 255 characters. To extend a field to another line, put a plus sign (+) at the end of the current line. L1023 terminated by user The LINK session was halted by CTRL+C or CTRL+BREAK.
778 LINK Error Messages L1034 name truncated to string A name specified either on the LINK command line or in a module-definition (.DEF) file exceeded 255 characters. The name was truncated to the given string. This is a warning, not a fatal error. However, it indicates a serious problem. This message may be followed by another error as LINK tries to use the specified name. For example, if the string is a filename, LINK issues an error when it cannot open the file.
Error! Style not defined. L1045 779 too many TYPDEF records An object file contained more than 255 TYPDEF records. TYPDEF records describe communal variables. (TYPDEF is an MS-DOS term. It is explained in the Microsoft MS-DOS Programmer’s Reference and in other reference books on MS-DOS.) This error appears only with programs created by the Microsoft FORTRAN Compiler or other compilers that support communal variables.
780 LINK Error Messages L1053 out of memory for symbol table The program had more symbolic information than could fit in available memory. Symbolic information includes public, external, segment, group, class, and file names. One of the following may be a solution: L1054 u Eliminate as many public symbols as possible. u Combine object files or segments. u Link from the command line instead of from a makefile or PWB. u Remove terminate-and-stay-resident programs or otherwise free some memory.
Error! Style not defined. L1064 781 out of memory—near/far heap exhausted LINK was not able to allocate enough memory for the given heap. One of the following may be a solution: L1065 u Reduce the size of code, data, and symbols in the program. u If the program is a segmented executable file, put some code into a dynamic-link library. too many interoverlay calls use /DYNAMIC:nnn; current limit is number The program had more than the given limit of interoverlay calls.
782 LINK Error Messages L1072 common area exceeds 64K The program had more than 65,536 bytes of communal variables. This error occurs only with programs produced by the Microsoft FORTRAN optimizing compiler or other compilers that support communal variables. L1073 file-segment limit exceeded The number of physical or file segments exceeded the limit of 255 imposed by the Windows operating system for each application or dynamic-link library.
Error! Style not defined. L1083 L1084 cannot open run file One of the following may have occurred: u The disk or the root directory was full. u Another process opened or deleted the file. u A read-only file existed with the same name. u The floppy disk containing the file was removed. u A hard-disk error occurred. cannot create temporary file One of the following may have occurred: u u L1085 783 The disk or the root directory was full.
784 LINK Error Messages L1089 filename : cannot open response file LINK could not find the given response file. One of the following may have occurred: L1090 u The response file does not exist. u The name of the response file was incorrectly specified. u An old version of LINK was used. Check your path. To see the version number of LINK, run LINK with the /? option. cannot reopen list file The original floppy disk was not replaced at the prompt. Restart the LINK session.
Error! Style not defined. L1098 785 cannot open include file filename—message LINK could not open the given include file for the given reason. An include file is specified in an INCLUDE statement in the module-definition (.DEF) file. L1100 stub .EXE file invalid The file specified in the STUB statement in the module-definition (.DEF) file is not a valid MS-DOS executable file. L1101 invalid object module LINK could not link one of the object files.
786 LINK Error Messages L1107 unknown COMDAT selection type for symbol; record ignored This is a translator error. The given symbol is either a routine or a data item. Note which translator (compiler or assembler) produced the incorrect object module and the circumstances in which it was produced. Please report this error to Microsoft Corporation by following the instructions in the “Microsoft Support Services” section of the introduction to this book.
Error! Style not defined. L1127 787 far segment references not allowed with /TINY The /TINY option for producing a .COM file was used in a program that has a far segment reference. Far segment references are not compatible with the .COM file format. High-levellanguage programs cause this error unless the language supports the tiny memory model. An assembly-language program that references a segment address also causes this error.
788 LINK Error Messages L2005 fixup type unsupported at number in segment segment A fixup type occurred that is not supported by LINK. This is probably a translator error. Note which translator (compiler or assembler) produced the incorrect object module and the circumstances in which it was produced. Please report this error to Microsoft Corporation by following the instructions in the “Microsoft Support Services” section of the introduction to this book.
Error! Style not defined. L2024 789 symbol : special symbol already defined The program defined a symbol name already used by LINK for one of its own low-level symbols. For example, LINK generates special symbols used in overlay support and other operations. Choose another name for the symbol to avoid conflict. L2025 symbol : symbol defined more than once The same symbol has been found in two different object files.
790 LINK Error Messages L2030 starting address not code (use class 'CODE') The program starting address, as specified in the END statement of an .ASM file, should be in a code segment. Code segments are recognized if their class name ends in “CODE”. This is an error in a segmented-executable file. The error message can be disabled by including the REALMODE statement in the module-definition (.DEF) file.
Error! Style not defined. L2048 791 Microsoft Overlay Manager module not found Overlays were designated, but an overlay manager was missing. By default, the overlay manager is the Microsoft Overlay Virtual Environment (MOVE). This is provided in MOVE.LIB, which is a component library of the default combined libraries provided with Microsoft C/C++ version 7.0. The error occurs when LINK cannot find the _moveinit routine.
792 LINK Error Messages L2062 continuation of COMDAT function has conflicting attributes; record ignored This is a translator error. Note which translator (compiler or assembler) produced the incorrect object module and the circumstances in which it was produced. Please report this error to Microsoft Corporation by following the instructions in the “Microsoft Support Services” section of the introduction to this book.
Error! Style not defined. 793 L4011 /PACKC value exceeding 64K–36 unreliable The packing limit specified with the /PACKC option was in the range 65,501–65,536 bytes. Code segments with a size in this range are unreliable on some versions of the 80286 processor. L4012 /HIGH disables /EXEPACK The /HIGH and /EXEPACK options cannot be used at the same time. L4013 option : option ignored for segmented executable file The given option is not allowed for segmented-executable programs.
794 LINK Error Messages L4021 no stack segment The program did not contain a stack segment defined with the STACK combine type. Normally, every program should have a stack segment with the combine type specified as STACK. You can ignore this message if you have a specific reason for not defining a stack or for defining one without the STACK combine type. Linking with versions of LINK earlier than version 2.40 might cause this message since these linkers search libraries only once.
Error! Style not defined. L4030 795 segment : segment attributes changed to conform with automatic data segment The given logical segment in the group DGROUP was given sharing attributes (SHARED/NONSHARED) that differed from the automatic data attributes as declared by the DATA instance specification (SINGLE/MULTIPLE). The attributes are converted to conform to those of DGROUP. The name DGROUP is predefined as the automatic (or default) data segment.
796 LINK Error Messages L4038 program has no starting address The segmented-executable application had no starting address. A missing starting address will usually cause the program to fail. High-level languages automatically specify a starting address. In a C-language program, this is provided by the main function. If you are writing an assembly-language program, specify a starting address with the END statement.
Error! Style not defined. L4051 797 filename : cannot find library LINK could not find the given library file. One of the following may be a cause: L4053 u The specified file does not exist. Enter the name or full path specification of a library file. u The LIB environment variable is not set correctly. Check for incorrect directory specifications, mistyping, or a space, semicolon, or hidden character at the end of the line. u An earlier version of LINK is being run.
798 LINK Error Messages L4067 changing default resolution for weak external symbol from oldresolution to newresolution LINK found conflicting default resolutions for a weak external. It ignored the first resolution and used the second. L4068 ignoring stack size greater than 64K A stack was defined with an invalid size. LINK assumed 64K. L4069 filename truncated to filename A filename specification exceeded the length allowed. LINK assumed the given filename.
Error! Style not defined. L4083 799 changing overlay assignment for symbol symbol from oldnumber to newnumber The given symbol was assigned to two overlays, represented by oldnumber and newnumber. LINK assumed the newnumber overlay. Probably a command-line overlay specification with parentheses conflicted with an overlay specification in the module-definition (.DEF) file. L4084 option : argument missing; option ignored The given option requires an argument, but none was specified.
800 ML Error Messages A1000 cannot open file: filename The assembler was unable to open a source, include, or output file. One of the following may be a cause: u The file does not exist. u The file is in use by another process. u The filename is not valid. u A read-only file with the output filename already exists. u Not enough file handles exist. In MS-DOS, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files.
Error! Style not defined. A1005 801 assembler limit : macro parameter name table full Too many parameters, locals, or macro labels were defined for a macro. There was no more room in the macro name table. Define shorter or fewer names, or remove unnecessary macros. A1006 invalid command-line option: option ML did not recognize the given parameter as an option. This error is generally caused when there is a syntax error on the command line.
802 ML Error Messages A1010 A1011 unmatched block nesting : A block beginning did not have a matching end, or a block end did not have a matching beginning. One of the following may be involved: u A high-level directive such as .IF, .REPEAT, or .
Error! Style not defined. A1015 803 statement too complex The assembler ran out of stack space while trying to parse the specified statement. One or more of the following changes may eliminate this error: A1017 u Break the statement into several shorter statements. u Reorganize the statement to reduce the amount of parenthetical nesting. u If the statement is part of a macro, break the macro into several shorter macros.
804 ML Error Messages A2004 symbol type conflict : identifier The EXTERNDEF or LABEL directive was used on a variable, symbol, data structure, or label that was defined in the same module but with a different type. A2005 symbol redefinition : identifier The given nonredefinable symbol was defined in two places. A2006 undefined symbol : identifier An attempt was made to use a symbol that was not defined. One of the following may have occurred: u u u u u u A2007 A symbol was not defined.
Error! Style not defined. 805 A2009 syntax error in expression An expression on the current line contained a syntax error. This error message may also be a side-effect of a preceding program error. A2010 invalid type expression The operand to THIS or PTR was not a valid type expression. A2011 distance invalid for word size of current segment A procedure definition or a code label defined with LABEL specified an address size that was incompatible with the current segment size.
806 ML Error Messages A2017 operator expected An expression operator was expected at the current location. One possible cause of this error is a missing comma between expressions in an expression list. A2018 invalid use of external symbol : identifier An attempt was made to compare the given external symbol using a relational operator. The comparison cannot be made because the value or address of an external symbol is not known at assembly time.
Error! Style not defined. A2028 807 expression must be a code address An expression evaluating to a code address was expected. One of the following occurred: A2029 u SHORT was not followed by a code address. u NEAR PTR or FAR PTR was applied to something that was not a code address. multiple base registers not allowed An attempt was made to combine two base registers in a memory expression.
808 ML Error Messages A2032 invalid use of register An attempt was made to use a register that was not valid for the intended use. One of the following occurred: u OFFSET was applied to a register. (OFFSET can be applied to a register under the M510 option.) u A special 386 register was used in an invalid context. u A register was cast with PTR to a type of invalid size. u A register was specified as the right operand of a segment override operator (:).
Error! Style not defined. A2038 missing operand for macro operator The assembler found the end of a macro’s parameter list immediately after the ! or % operator. A2039 line too long A source-file line exceeded the limit of 512 characters. 809 If multiple physical lines are concatenated with the line-continuation character ( \ ), the resulting logical line is still limited to 512 characters.
810 ML Error Messages A2046 missing single or double quotation mark in string An unmatched quotation mark (either ' or ") was found in a string. One of the following may have occurred: A2047 u A pair of quotation marks around a string was not complete. u A pair of quotation marks around a string was formed of one single and one double quotation mark. u A single or double quotation mark was intended to be literal, but the surrounding quotation marks were the same kind as the literal one.
Error! Style not defined. 811 A2052 forced error The conditional-error directive .ERR or .ERR1 was used to generate this error. A2053 forced error : value equal to 0 The conditional-error directive .ERRE was used to generate this error. A2054 forced error : value not equal to 0 The conditional-error directive .ERRNZ was used to generate this error. A2055 forced error : symbol not defined The conditional-error directive .ERRNDEF was used to generate this error.
812 ML Error Messages A2064 structure alignment must be 1, 2, or 4 The alignment specified in a structure definition was invalid. A2065 expected : token The assembler expected the given token. A2066 incompatible CPU mode and segment size An attempt was made to open a segment with a USE16, USE32, or FLAT attribute that was not compatible with the specified CPU, or to change to a 16-bit CPU while in a 32bit segment.
Error! Style not defined. A2075 813 jump destination too far [: by 'n' bytes] The destination specified with a jump instruction was too far from the instruction. One of the following may be a solution: u Enable the LJMP option. u Remove the SHORT operator. If SHORT has forced a jump that is too far, n is the number of bytes out of range. u Rearrange code so that the jump is no longer out of range.
814 ML Error Messages A2085 instruction or register not accepted in current CPU mode An attempt was made to use an instruction, register, or keyword that was not valid for the current processor mode. For example, 32-bit registers require .386 or above. Control registers such as CR0 require privileged mode .386P or above. This error will also be generated for the NEAR32, FAR32, and FLAT keywords, which require .386 or above.
Error! Style not defined. A2093 count value too large The length argument specified for SUBSTR or @SubStr exceeded the length of the specified string. A2094 operand must be relocatable An operand was not relative to a label. 815 One of the following occurred: u An operand specified with the END directive was not relative to a label. u An operand to the SEG operator was not relative to a label. u The right operand to the minus operator was relative to a label, but the left operand was not.
816 ML Error Messages A2100 segment or group not allowed An attempt was made to use a segment or group in a way that was not valid. Segments or groups cannot be added. A2101 cannot add two relocatable labels An attempt was made to add two expressions that were both relative to a label. A2102 cannot add memory expression and code label An attempt was made to add a code label to a memory expression. A2103 segment exceeds 64K limit A 16-bit segment exceeded the size limit of 64K.
Error! Style not defined. 817 A2113 invalid radix tag The specified radix was not a number in the range 2–16. A2114 INVOKE argument type mismatch : argument number The type of the arguments passed using the INVOKE directive did not match the type of the parameters in the prototype of the procedure being invoked. A2115 invalid coprocessor register The coprocessor index specified was negative or greater than 7.
818 ML Error Messages A2122 alternate identifier not allowed with EXTERNDEF An attempt was made to specify an alternate identifier with an EXTERNDEF directive. You can specify an optional alternate identifier with the EXTERN directive but not with EXTERNDEF. A2123 text macro nesting level too deep A text macro was nested too deeply. The nesting limit for text macros is 40. A2125 missing macro argument A required argument to @InStr, @SubStr, or a user-defined macro was not specified.
Error! Style not defined. A2134 819 structure too large to pass with INVOKE : argument number An attempt was made with INVOKE to pass a structure that exceeded 255 bytes. Pass structures by reference if they are larger than 255 bytes. A2136 too many arguments to INVOKE The number of arguments passed using the INVOKE directive exceeded the number of parameters in the prototype for the procedure being invoked.
820 ML Error Messages A2147 macro label not defined : macrolabel The given macro label was not found. A macro label is defined with :macrolabel. A2148 invalid symbol type in expression : identifier The given identifier was used in an expression in which it was not valid. For example, a macro procedure name is not allowed in an expression. A2149 byte register cannot be first operand A byte register was specified to an instruction that cannot take it as the first operand.
Error! Style not defined. A2157 821 missing right parenthesis A right parenthesis, ), was missing from a macro function call. Be sure that parentheses are in pairs if nested. A2158 type is wrong size for register An attempt was made to assume a general-purpose register to a type with a different size than the register.
822 ML Error Messages A2166 structure field expected The righthand side of a dot operator (.) is not a structure field. This error may occur with some code acceptable to previous versions of the assembler. To enable the old behavior, use OPTION OLDSTRUCTS, which is automatically enabled by OPTION M510 or the /Zm command-line option. A2167 unexpected literal found in expression A literal was found where an expression was expected.
Error! Style not defined. A2178 823 invalid use of FLAT There was an ambiguous reference to FLAT as a group. This error is generated when there is a reference to FLAT instead of a FLAT subgroup. For example, mov mov A2179 ax, FLAT ax, SEG FLAT:_data ; Generates A2178 ; Correct structure improperly initialized There was an error in a structure initializer. One of the following occurred: u u The initializer is not a valid expression. The initializer is an invalid DUP statement.
824 ML Error Messages A2186 extra characters in literal initialization A literal structure initializer was not properly delimited. One of the following may have occurred: A2187 u There were missing or mismatched angle brackets (< >) or braces ({ }) around an initializer. u There were extra characters after the end of an initializer. u There was a syntax error in the structure initialization.
Error! Style not defined. A2195 825 parameter or local cannot have void type The assembler attempted to create an argument or create a local without a type. This error can be caused by declaring or passing a symbol followed by a colon without specifying a type or by using a user-defined type defined as void. A2196 cannot use TINY model with OS_OS2 A .MODEL statement specified the TINY memory model and the OS_OS2 operating system. The tiny memory model is not allowed under OS/2.
826 ML Error Messages A2205 ESC instruction is obsolete : ignored The ESC (Escape) instruction is no longer supported. All numeric coprocessor instructions are now supported directly by the assembler. A2206 missing operator in expression An expression cannot be evaluated because it is missing an operator. This error message may also be a side-effect of a preceding program error.
Error! Style not defined. A4002 827 non-unique STRUCT/UNION field used without qualification A STRUCT or UNION field can be referenced without qualification only if it has a unique identifier. This conflict can be resolved either by renaming one of the structure fields to make it unique or by fully specifying both field references. The NONUNIQUE keyword requires that all references to the elements of a STRUCT or UNION be fully specified. A4003 start address on END directive ignored with .STARTUP Both .
828 ML Error Messages A4011 multiple .MODEL directives found : .MODEL ignored More than one .MODEL directive was found in the current module. Only the first .MODEL statement is used. A4012 line number information for segment without class 'CODE' There were instructions in a segment that did not have a class name that ends with “CODE.” The assembler did not generate CodeView information for these instructions.
Error! Style not defined. A5005 types are different The type given by an INVOKE statement differed from that given in the procedure prototype. The assembler performed the appropriate type conversion. A6001 no return from procedure A PROC statement generated a prologue, but there was no RET or IRET instruction found inside the procedure block. A6003 conditional jump lengthened A conditional jump was encoded as a reverse conditional jump around a near unconditional jump.
830 NMAKE Error Messages U1001 syntax error : illegal character character in macro The given character appeared in a macro but was not a letter, number, or underscore (_). If the colon (:) is omitted in a macro expansion, the following error occurs: syntax error : illegal character '=' in macro U1002 syntax error : invalid macro invocation '$' A single dollar sign ($) appeared without a macro name associated with it. The correct form is $(name).
Error! Style not defined. U1017 unknown directive !directive The specified directive is not one of the recognized directives. U1018 directive and/or expression part missing The directive was incompletely specified. 831 The expression part of the directive is required. U1019 too many nested !IF blocks The limit on nesting of !IF directives was exceeded. The !IF preprocessing directives include !IF, !IFDEF, !IFNDEF, !ELSE IF, !ELSE IFDEF, and !ELSE IFNDEF.
832 NMAKE Error Messages U1033 syntax error : string unexpected The given string is not part of the valid syntax for a makefile.
Error! Style not defined. U1037 833 syntax error : target name missing A colon (:) was found before a target name was found. At least one target is required. U1038 internal error : lexer Note the circumstances of the error and notify Microsoft Corporation by following the instructions in the “Microsoft Support Services” section of the introduction to this book.
834 NMAKE Error Messages U1051 out of memory The makefile was too large or complex for available memory. U1052 file filename not found NMAKE could not find the given file, which was specified with one of the following: u The /F option u The !INCLUDE preprocessing directive u The at sign (@) specifier for a response file Check that the file exists and the filename is spelled correctly. U1053 file filename unreadable The file cannot be read.
Error! Style not defined. 835 U1058 terminated by user NMAKE was halted by CTRL+C or CTRL+BREAK. U1059 syntax error: '}' missing in dependent A search path for a dependent was incorrectly specified. Either a space existed in the path or the closing brace (}) was omitted. The syntax for a directory specification for a dependent is: {directories}dependent where directories specifies one or more paths, each separated by a semicolon (;). No spaces are allowed.
836 NMAKE Error Messages U1064 MAKEFILE not found and no target specified The NMAKE command line did not specify a makefile or a target, and the current directory did not contain a file named MAKEFILE. NMAKE requires either a makefile or a command-line target. To make a makefile available to NMAKE, either specify the /F option or place a file named MAKEFILE in the current directory. NMAKE can create a command-line target by using an inference rule if a makefile is not provided.
Error! Style not defined. U1076 U1077 837 name too long A string exceeded one of the following limits: u A macro name cannot exceed 1024 characters. u A target name (including path) cannot exceed 256 characters. u A command cannot exceed 2048 characters. program : return code value The given command or program called by NMAKE failed and returned the given exit code. To suppress this error and continue the NMAKE session, use the /I option, the .
838 NMAKE Error Messages U1084 cannot create temporary file filename NMAKE was unable to create the temporary file it needs when it processes the makefile. One of the following may be a cause: u The file already exists with a read-only attribute. u There is insufficient disk space to create the file. u The directory specified in the TMP environment variable does not exist. U1085 cannot mix implicit and explicit rules A target and a pair of inference-rule extensions were specified on the same line.
Error! Style not defined. U1094 839 syntax error : only (NO)KEEP allowed here Something other than KEEP or NOKEEP appeared after the closing set of angle brackets (<<) specifying an inline file. Only KEEP, NOKEEP, or a newline character may follow the angle brackets. No spaces, tabs, or other characters may appear. KEEP preserves the inline file on disk. NOKEEP deletes the file after the NMAKE session. The default is NOKEEP.
840 NMAKE Error Messages U2001 no more file handles (too many files open) NMAKE could not find a free file handle. One of the following may be a solution: u Reduce recursion in the build procedures. u In MS-DOS, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=50 is the recommended setting.
Error! Style not defined. U4004 841 too many rules for target targetname More than one description block was specified for the given target using single colons (:) as separators. NMAKE executed the commands in the first description block and ignored later blocks. To specify the same target in multiple dependencies, use double colons (::) as the separator in each dependency line. U4005 ignoring rule rule (extension not in .SUFFIXES) The given rule contained a suffix that is not specified in the .
842 PWB Error Messages PWB Error Messages PWB displays an error message whenever it detects a command it cannot execute. Most errors terminate the command that is in error, but do not terminate PWB. For most errors, PWB displays a message box with only the text of the message. The error number does not appear. With these messages, press F1 or click Help when the message box is displayed for Help on the error. Some errors terminate PWB.
Error! Style not defined. PWB3178 843 Cannot start: unable to open swapping file PWB is unable to create its virtual-memory file on disk. PWB creates this file in the directory pointed to by the TMP environment variable. If no TMP environment variable is set, PWB creates the file in the current directory. Check that the disk has at least 2 free megabytes and that the directory can be accessed with permission to create a file. Check that the TMP environment variable lists a single existing directory.
844 SBRPACK Error Messages This section lists error messages generated by the Microsoft Browse Information Compactor (SBRPACK). SBRPACK errors (SB xxx) are always fatal. SB1000 UNKNOWN ERROR Contact Microsoft Product Support Services SBRPACK detected an unknown error condition. Note the circumstances of the error and notify Microsoft Corporation by following the instructions in the “Microsoft Support Services” section of the introduction to this book. This error ends SBRPACK with exit code 1.
Error! Style not defined. SB1004 845 sbrfile : incompatible .SBR version The given .SBR file cannot be packed by this version of SBRPACK. One of the following may be a cause: u The .SBR file was created by a compiler that is not compatible with this version of SBRPACK. u The .SBR file is corrupt. This error ends SBRPACK with exit code 2. SB1005 sbrfile : cannot open file SBRPACK cannot open the given .SBR file. One of the following may be a cause: u u The .SBR file does not exist.
846 Environment and Tools Filename: LMAETAPA.DOC Project: MASM Environment and Tools Template: MSGRIDA1.
