This section lists error messages generated by the Microsoft EXE File Header Utility (EXEHDR). EXEHDR errors (U11xx) are always fatal.
U1100 |
invalid magic number number |
|
EXEHDR discovered an unknown signature in the header for the file. |
|
The signature in the header for a file gives the operating system under which the executable file will run. EXEHDR recognizes signatures for DOS and OS/2 only. |
U1101 |
automatic data segment greater than 64K; correcting heap size |
|
There was not enough space in the automatic, or default, data segment (DGROUP) to accommodate the requested new heap size. EXEHDR adjusted the heap size to the maximum available space. |
|
This error applies only to OS/2 programs. |
U1102 |
automatic data segment greater than 64K; correcting stack size |
|
There was not enough space in the automatic, or default, data segment (DGROUP) to accommodate the requested new stack size. EXEHDR adjusted the stack size to the maximum available space. |
|
This error applies only to OS/2 programs. |
U1103 |
invalid .EXE file : actual length less than reported |
|
The second and third fields in the input-file header indicate a file size greater than the actual size. |
U1104 |
cannot change load-high program |
|
When the minimum allocation value and the maximum allocation value are both 0, the file cannot be modified. |
U1105 |
minimum allocation less than stack; correcting minimum |
|
If the minimum allocation is not enough to accommodate the stack (either the original stack request or the modified request), the minimum allocation value is adjusted. |
|
This error applies only to DOS programs. |
U1106 |
minimum allocation greater than maximum; correcting maximum |
|
If the minimum allocation is greater than the maximum allocation, the maximum allocation value is adjusted. |
|
If a display of DOS header values is requested, the values shown will be the values after the packed file is expanded. |
|
This error applies only to DOS programs. |
U1107 |
unexpected end of resident/nonresident name table |
|
While decoding run-time relocation records, EXEHDR found the end of either the resident names table or the nonresident names table. The executable file is probably corrupted. |
|
This error applies only to OS/2 and Windows programs. |
U1108 |
cannot display compressed relocation records |
|
EXEHDR cannot decode the information in the file header because the header is not in a standard format. |
U1109 |
illegal value argument |
|
The given argument was invalid for the EXEHDR option it was specified with. |
U1110 |
malformed number number |
|
A command-line option for EXEHDR required a value, but the specified 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. |
U1112 |
value out of legal range lower–upper |
|
A command-line option for EXEHDR required a value, but the specified number did not fall in the required decimal range. |
U1113 |
value out of legal range lower–upper |
|
A command-line option for EXEHDR required a value, but the specified number did not fall in the required hexadecimal range. |
U1114 |
missing option value; option option ignored |
|
A command-line option for EXEHDR required a value, but nothing was specified. EXEHDR ignored the option. |
U1115 |
option option ignored |
|
A command-line option for EXEHDR was ignored. This error usually occurs with error U1116, unrecognized option. |
U1116 |
unrecognized option: option |
|
A command-line option for EXEHDR was not recognized. This error usually occurs with either U1115, option ignored, or U1111, option requires value. |
U1120 |
input file missing |
|
No input file was specified on the EXEHDR command line. |
U1121 |
command line too long: commandline |
|
The given EXEHDR command line exceeded the limit of 512 characters. |
U1130 |
cannot read filename |
|
EXEHDR could not read the input file. Either the file is missing or the file attribute is set to prevent reading. |
U1131 |
invalid .EXE file |
|
The input file specified on the EXEHDR command line was not a valid executable file. |
U1132 |
unexpected end-of-file |
|
EXEHDR found an unexpected end-of-file condition while reading the executable file. The file is probably corrupt. |
U1140 |
out of memory |
|
There was not enough memory for EXEHDR to decode the header of the executable file. |