Number | LIB Error Message |
U1150 | page size too small |
The page size of an input library was too small, indicating an invalid input .LIB file. | |
U1151 | syntax error : illegal file specification |
A command operator was not followed by a module name or filename. | |
One possible cause of this error is an option specified with a dash (–) instead of a forward slash (/). | |
U1152 | syntax error : option name missing |
A forward slash (/) appeared on the command line without an option name after it. | |
U1153 | syntax error : option value missing |
The /PAGE option was given without a value following it. | |
U1154 | unrecognized option |
An unrecognized name followed the option indicator. | |
An option is specified by a forward slash (/) and a name. The name can be specified by a legal abbreviation of the full name. | |
U1155 | syntax error : illegal input |
A specified command did not follow correct LIB syntax. | |
U1156 | syntax error |
A specified command did not follow correct LIB syntax. | |
U1157 | comma or newline missing |
A comma or carriage return was expected in the command line but did not appear. | |
This may indicate 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 used to start LIB did not end with a carriage return. | |
U1159 | option argument missing |
An expected argument to an option or command was missing from the command line. | |
U1160 | invalid page size |
The argument specified with the /PAGE option was not valid for that option. The value must be an integer power of 2 between 16 and 32,768. | |
U1161 | cannot rename old library |
LIB could not rename the old library with a .BAK extension because the .BAK version already existed with read-only protection. | |
Change the protection on the old .BAK version. | |
U1162 | cannot reopen library |
The old library could not be reopened after it was renamed with a .BAK extension. | |
One of the following may have occurred:
Another process deleted the file or changed it to read-only. The floppy disk containing the file was removed. A hard-disk error occurred. |
|
U1163 | error writing to cross-reference file |
The disk or root directory was full. | |
Delete or move files to make space. | |
U1164 | name length exceeds 255 characters |
A filename specified on the command line exceeded the LIB limit of 255 characters. Reduce the number of characters in the name. | |
U1170 | too many symbols |
The number of symbols in all object files and libraries exceeded the capacity of the dictionary created by LIB. | |
Create two or more smaller libraries. | |
U1171 | insufficient memory |
LIB did not have enough memory to run. | |
Remove any shells or resident programs and try again, or add more memory. | |
U1172 | no more virtual memory |
The LIB session required more memory than the one-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 on the Microsoft Product Assistance Request form at the back of one of your manuals. | |
U1174 | mark : not allocated |
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. | |
U1175 | free : not allocated |
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. | |
U1180 | write to extract file failed |
The disk or root directory was full. | |
Delete or move files to make space. | |
U1181 | write to library file failed |
The disk or root directory was full. | |
Delete or move files to make space. | |
U1182 | filename : cannot create extract file |
The disk or root directory was full, or the given extract file already existed with read-only protection. | |
Make space on the disk or change the protection of the extract file. | |
U1183 | cannot open response file |
The response file was not found. | |
U1184 | unexpected end-of-file on command input |
An end-of-file character was received prematurely in response to a prompt. | |
U1185 | cannot create new library |
The disk or root directory was full, or the library file already existed with read-only protection. | |
Make space on the disk or change the protection of the library file. | |
U1186 | error writing to new library |
The disk or root directory was full. | |
Delete or move files to make space. | |
U1187 | 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 on the Microsoft Product Assistance Request form at the back of one of your manuals. | |
U1189 | cannot read from temporary file |
The library manager cannot read the virtual memory. | |
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. | |
U1190 | interrupted by user |
LIB was interrupted during its operation, with either CTRL+C or CTRL+BREAK. | |
U1200 | filename : invalid library header |
The input library file had an invalid format. | |
Either it was not a library file, or it had been corrupted. | |
U1203 | filename : invalid object file near location |
The given file was not a valid object file or was corrupted at the given location. |