| U1000 |
syntax error : ')' missing in macro invocation |
| |
A left parenthesis ( ( ) appeared without a matching right parenthesis ( ) ) in a macro invocation. The correct form is $(name), or $n for one-character names. |
| U1001 |
syntax error : illegal character character in macro |
| |
A nonalphanumeric character other than an underscore (_) appeared in a macro. |
| U1002 |
syntax error : invalid macro invocation '$' |
| |
A single dollar sign ($) appeared without a macro name associated with it. |
| |
The correct form is $(name). To use a dollar sign in the file, type it twice ($$) or precede it with a caret (^). |
| U1003 |
syntax error : '=' missing in macro |
| |
The equal sign (=) was missing in a macro definition. |
| |
The correct form is |
| |
macroname=string |
| U1004 |
syntax error : macro name missing |
| |
A macro invocation appeared without a name. |
| |
The correct form is |
| |
$(name) |
| U1005 |
syntax error : text must follow ':' in macro |
| |
A string substitution was specified for a macro, but the string to be changed in the macro was not specified. |
| U1006 |
syntax error : missing closing double quotation mark |
| |
An opening double quotation mark (") appeared without a closing double quotation mark. |
| U1007 |
double quotation mark not allowed in name |
| |
The specified target name or filename contained a double quotation mark ("). |
| |
Double quotation marks can surround a filename but cannot be contained within it. |
| U1017 |
unknown directive !directive |
| |
The directive specified is not one of the recognized directives. |
| U1018 |
directive and/or expression part missing |
| |
The directive was incompletely specified. |
| |
The expression part of the directive is required. |
| U1019 |
too many nested !IF blocks |
| |
Note the circumstances of the error and notify Microsoft Corporation by following the instructions on the Microsoft Product Assistance Request form at the back of one of your manuals. |
| U1020 |
end-of-file found before next directive |
| |
A directive, such as !ENDIF, was missing. |
| U1021 |
syntax error : !ELSE unexpected |
| |
An !ELSE directive was found that was not preceded by !IF, !IFDEF, or !IFNDEF, or the directive was placed in a syntactically incorrect place. |
| U1022 |
missing terminating character for string/program invocation : char |
| |
The closing double quotation mark (") in a string comparison in a directive was missing, or the closing bracket (]) in a program invocation in a directive was missing. |
| U1023 |
syntax error in expression |
| |
An expression was invalid. |
| |
Check the allowed operators and operator precedence. |
| U1024 |
illegal argument to !CMDSWITCHES |
| |
An unrecognized command switch was specified. |
| U1031 |
filename missing (or macro is null) |
| |
An include directive was found, but the name of the file to be included was missing, or the macro expanded to nothing. |
| U1033 |
syntax error : string unexpected |
| |
The given string is not part of the valid syntax for a description file. |
| U1034 |
syntax error : separator missing |
| |
The colon (:) that separates targets and dependents is missing. |
| U1035 |
syntax error : expected ':' or '=' separator |
| |
Either a colon (:), implying a dependency line, or an equal sign (=), implying a macro definition, was expected. |
| U1036 |
syntax error : too many names to left of '=' |
| |
Only one string is allowed to the left of a macro definition. |
| U1037 |
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 on the Microsoft Product Assistance Request form at the back of one of your manuals. |
| U1039 |
internal error : parser |
| |
Note the circumstances of the error and notify Microsoft Corporation by following the instructions on the Microsoft Product Assistance Request form at the back of one of your manuals. |
| U1040 |
internal error : macro expansion |
| |
Note the circumstances of the error and notify Microsoft Corporation by following the instructions on the Microsoft Product Assistance Request form at the back of one of your manuals. |
| U1041 |
internal error : target building |
| |
Note the circumstances of the error and notify Microsoft Corporation by following the instructions on the Microsoft Product Assistance Request form at the back of one of your manuals. |
| U1042 |
internal error : expression stack overflow |
| |
Note the circumstances of the error and notify Microsoft Corporation by following the instructions on the Microsoft Product Assistance Request form at the back of one of your manuals. |
| U1043 |
internal error : temp file limit exceeded |
| |
Note the circumstances of the error and notify Microsoft Corporation by following the instructions on the Microsoft Product Assistance Request form at the back of one of your manuals. |
| U1044 |
internal error : too many levels of recursion building a target |
| |
Note the circumstances of the error and notify Microsoft Corporation by following the instructions on the Microsoft Product Assistance Request form at the back of one of your manuals. |
| U1045 |
internal error message |
| |
Note the circumstances of the error and notify Microsoft Corporation by following the instructions on the Microsoft Product Assistance Request form at the back of one of your manuals. |
| U1046 |
internal error : out of search handles |
| |
This error occurs under OS/2 when there are not enough search handles for NMAKE to run. |
| U1049 |
macro or inline file too long (maximum 64K) |
| |
An inline file or a macro exceeded the limit of 64K. |
| U1050 |
user-specified text |
| |
The message specified with the !ERROR directive was displayed. |
| U1051 |
out of memory |
| |
The program ran out of space in the far heap. |
| |
Split the description file into smaller and simpler pieces. |
| U1052 |
file filename not found |
| |
The file was not found. |
| |
Check the specification of the filename in the description file. |
| U1053 |
file filename unreadable |
| |
The file cannot be read. |
| |
The following are possible causes of this error:
 The file does not have appropriate attributes for reading.
A bad area exists on disk.
A bad file-allocation table exists.
The file is locked.
|
| U1054 |
cannot create inline file filename |
| |
NMAKE failed in its attempt to create the given file. |
| |
The following are possible causes of this error:
The file already exists with a read-only attribute.
There is insufficient disk space to create the file.
|
| U1055 |
out of environment space |
| |
The environment space limit was reached. |
| |
Restart the program with a larger environment space or with fewer environment variables. |
| U1056 |
cannot find command processor |
| |
The command processor was not found. |
| |
NMAKE uses COMMAND.COM or CMD.EXE as a command processor to execute commands. It looks for the command processor first by the full pathname given by the COMSPEC environment variable. If COMSPEC does not exist, NMAKE searches the directories specified by the PATH environment variable. |
| U1057 |
cannot delete temporary file filename |
| |
NMAKE failed to delete the temporary inline file. |
| U1058 |
terminated by user |
| |
Execution of NMAKE was aborted by CTRL+C or CTRL+BREAK. |
| U1060 |
unable to close file : filename |
| |
NMAKE encountered an error while closing a file. |
| |
One of the following may have occurred:
The file is a read-only file.
There is a locking or sharing violation.
The disk is full.
|
| U1061 |
/F option requires a filename |
| |
The /F command-line option requires the name of the description file to be specified. |
| |
To use standard input, specify '–' as the filename. |
| |
One cause of this error is omitting the space between /F and the filename. |
| U1062 |
missing filename with /X option |
| |
The /X command-line option requires the name of the file to which diagnostic error output should be redirected. |
| |
To use standard output, specify '–' as the output filename. |
| U1063 |
missing macro name before '=' |
| |
NMAKE detected an equal sign (=) without a preceding name. |
| |
This error can occur in a recursive call when the macro corresponding to the macro name expands to nothing. |
| U1064 |
MAKEFILE not found and no target specified |
| |
No description file was found, and no target was specified. |
| |
A description file can be specified either with the /F option or in a file named MAKEFILE. Note that NMAKE can create a target using an inference rule even if no description file is specified. |
| U1065 |
invalid option option |
| |
The option specified is not a valid option for NMAKE. |
| U1066 |
option /N not supported; use NMAKE /N |
| |
NMK does not support the /N option. Run NMAKE with the /N option. |
| U1070 |
cycle in macro definition macroname |
| |
A circular definition was detected in the given macro definition. |
| |
Circular definitions are invalid. |
| U1071 |
cycle in dependency tree for target targetname |
| |
A circular dependency was detected in the dependency tree for the given target. |
| |
Circular dependencies are invalid. |
| U1072 |
cycle in include files : filename |
| |
A circular inclusion was detected in the given include file. This file includes a file which eventually includes this file. |
| U1073 |
don't know how to make targetname |
| |
The specified target does not exist, and there are no commands to execute or inference rules given for it. |
| U1074 |
macro definition too long |
| |
The value of a macro definition overflowed an internal buffer. |
| U1075 |
string too long |
| |
The text string overflowed an internal buffer. |
| U1076 |
name too long |
| |
The macro name, target name, or build-command name overflowed an internal buffer. |
| |
Macro names cannot exceed 128 characters. |
| U1077 |
program : return code value |
| |
The given program invoked from NMAKE failed, returning the given exit code. |
| U1078 |
constant overflow at directive |
| |
A constant in the directive's expression was too big. |
| U1079 |
illegal expression : divide by zero |
| |
An expression tried to divide by zero. |
| U1080 |
operator and/or operand usage illegal |
| |
The expression incorrectly used an operator or operand. |
| |
Check the allowed set of operators and their order of precedence. |
| U1081 |
program : program not found |
| |
NMAKE could not find the given program in order to run it. |
| |
Make sure that the program is in the current path and has the correct extension. |
| U1082 |
command : cannot execute command; out of memory |
| |
NMAKE cannot execute the given command because there is not enough memory. |
| |
Free some memory and run NMAKE again. |
| U1083 |
target macro $(macroname) expands to nothing |
| |
A target was specified as a macro name that has not been defined or has null value. |
| |
NMAKE cannot process a null target. |
| U1084 |
cannot create temporary file filename |
| |
NMAKE was unable to create a temporary file it needed for processing the description file. |
| |
The following are possible causes of this error:
The file already exists with a read-only attribute.
There is insufficient disk space to create the file.
The TMP environment variable was set to an invalid directory or path.
|
| U1085 |
cannot mix implicit and explicit rules |
| |
A regular target was specified along with the target for a rule. |
| |
A rule has the form |
| |
.fromext.toext |
| U1086 |
inference rule cannot have dependents |
| |
Dependents are not allowed when an inference rule is being defined. |
| U1087 |
cannot have : and :: dependents for same target |
| |
A target cannot have both a single-colon (:) and a double-colon (::) dependency. |
| U1088 |
invalid separator '::' on inference rule |
| |
Inference rules can use only a single-colon (:) separator. |
| U1089 |
cannot have build commands for directive targetname |
| |
Directives (for example, .PRECIOUS or .SUFFIXES) cannot have build commands specified. |
| U1090 |
cannot have dependents for directive targetname |
| |
The specified directive (for example, .SILENT or .IGNORE) cannot have a dependent. |
| U1091 |
invalid suffixes in inference rule |
| |
The suffixes being used in the inference rule are not part of the .SUFFIXES list. |
| U1092 |
too many names in rule |
| |
An inference rule cannot have more than one pair of extensions. |
| U1093 |
cannot mix special pseudotargets |
| |
It is illegal to list two or more pseudotargets together. |
| U1094 |
syntax error : only (NO)KEEP allowed here |
| |
Something other than KEEP or NOKEEP appeared at the end of the syntax for creating an inline file. |
| |
The syntax for generating an inline file allows an action to be specified after the second pair of angle brackets. Valid actions are KEEP and NOKEEP. Any other specification is invalid. |
| |
The KEEP option specifies that NMAKE should leave the inline file on disk. The NOKEEP option causes NMAKE to delete the file before exiting. The default is NOKEEP. |
| U1095 |
expanded command line commandline too long |
| |
After macro expansion, the command line shown exceeded the length limit for command lines for the operating system. |
| |
DOS permits up to 128 characters on a command line. |
| |
If the command is for a program that can accept command-line input from a file, change the command and supply input from either a file on disk or an inline file. For example, LINK and LIB accept input from a response file. |
| U1096 |
cannot open file filename |
| |
The given file could not be opened, either because the disk was full or because the file has been set to be read-only. |
| U1097 |
extmake syntax usage error, no dependent |
| |
No dependent was given. |
| |
In extmake syntax, the target under consideration must have either an implicit dependent or an explicit dependent. |
| U1098 |
extmake syntax in string incorrect |
| |
The part of the string shown contains an extmake syntax error. |
| U1099 |
stack overflow |
| |
The description file being processed was too complex for the current stack allocation in NMAKE. |
| |
NMAKE has a default allocation of 0x3000 (12K). |
| |
To increase NMAKE's stack allocation, run the EXEHDR utility with a larger stack option: |
| |
EXEHDR /STACK:stacksize |
| |
where stacksize is a number greater than the current stack allocation in NMAKE. |
| U1450 |
could not execute NMAKE.EXE |
| |
NMK was not able to locate and execute the NMAKE utility. Make sure this file is on your path. |
| U1451 |
out of memory |
| |
There was not enough available memory to complete the operation. |
| |
One of the following may be a cause:
There are too many TSR programs installed. Remove some TSRs.
A previous command did not release memory when it terminated. This can happen if you attempt to run a TSR from within NMK.
There are too many active command shells. Close the current shell by entering EXIT at the operating-system prompt.
|
| U1452 |
COMSPEC not defined |
| |
The COMSPEC environment variable is not defined |
| |
NMK requires COMSPEC to be set to the full pathname of the operating-system command processor. |
| U1453 |
error reading script file |
| |
NMK encountered an error while reading the script file, which contains commands to execute during a shell or build operation. |
| |
This can be caused by a CTRL+BREAK or a disk error while reading the script file. |
| U1454 |
command
could not execute |
| |
NMK was unable to execute the given command. |
| |
One of the following may have occurred:
There was not enough available memory to execute the command. A previous command may not have released memory when it ended. This can happen if you attempt to run a TSR from within NMK.
The operating system denied access to the file: it is in use by another program.
The executable file is corrupt.
|
| U1455 |
bad command or file name |
| |
An operating-system command or executable program could not be executed. |
| |
Either the command was spelled incorrectly, or it does not exist on the paths specified in the PATH environment variable. |