| U1500 |
UNKNOWN ERROR
Contact Microsoft Product Support Services |
| |
PWBRMAKE detected an unknown error condition. |
| |
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. |
| U1501 |
unknown character character in option option |
| |
PWBRMAKE did not recognize the given character specified for the given option. |
| U1502 |
incomplete specification for option option |
| |
The given option did not contain the complete specification that PWBRMAKE expected. |
| U1503 |
cannot write to file filename |
| |
PWBRMAKE could not write to the given file. |
| |
One of the following may have occurred:
 The disk was full.
A hardware error occurred.
|
| U1504 |
cannot position in file filename |
| |
PWBRMAKE could not move to a location in the given file. |
| |
One of the following may have occurred:
The disk was full.
A hardware error occurred.
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.
|
| U1505 |
cannot read from file filename |
| |
PWBRMAKE could not read from the given file. |
| |
One of the following may have occurred:
The file was corrupt.
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.
|
| U1506 |
cannot open file filename |
| |
PWBRMAKE could not open the given file. |
| |
One of the following may have occurred:
No more file handles were available. In DOS, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=20 is the recommended setting.
The file was locked by another process.
The disk was full.
A hardware error occurred.
The specified output file had the same name as an existing subdirectory.
|
| U1507 |
cannot open temporary file filename |
| |
PWBRMAKE could not open one of its temporary files. |
| |
One of the following may have occurred:
No more file handles were available. In DOS, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=20 is the recommended setting.
The TMP environment variable was not set to a valid drive and directory.
The disk was full.
|
| U1508 |
cannot delete temporary file filename |
| |
PWBRMAKE could not delete one of its temporary files. |
| |
One of the following may have occurred:
Another process had the file open.
A hardware error occurred.
|
| U1509 |
out of heap space |
| |
PWBRMAKE ran out of memory. |
| |
One of the following may be a solution:
Reduce the memory that PWBRMAKE will require by using one or more options. Use /Ei or /Es to eliminate some input files. Use /Em to eliminate macro bodies.
Free some memory by removing terminate-and-stay-resident (TSR) software.
Reconfigure the EMM driver.
Change CONFIG.SYS to specify a lower number of buffers (the BUFFERS command) and fewer drives (the LASTDRIVE command).
|
| U1510 |
corrupt .SBR file filename |
| |
The given .SBR file is corrupt or does not have the expected format. |
| |
Recompile to regenerate the .SBR file. |
| U1511 |
invalid response file specification |
| |
PWBRMAKE did not understand the command-line specification for the response file. The specification was probably wrong or incomplete. |
| |
For example, the following specification causes this error:
pwbrmake @
|
| U1512 |
database capacity exceeded |
| |
PWBRMAKE could not build a database because the number of definitions, references, modules, or other information exceeded the limit for a database. |
| |
One of the following may be a solution:
Exclude some information using the /Em, /Es, or /Ei option.
Omit the /Iu option if it was used.
Divide the list of .SBR files and build multiple databases.
|
| U1513 |
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 U4502, which will give the name of the .SBR file that caused the error. |
| |
PWBRMAKE can process a truncated, or zero-length, .SBR file only when a database already exists and is being incrementally updated. |
| |
One of the following may be a cause:
The database was deleted.
The wrong database name was specified.
The database file was corrupted, requiring a full build.
|
| U1514 |
all .SBR files truncated and not in database |
| |
None of the .SBR files specified for an update was a part of the original database. This message is always preceded by warning U4502, which will give the name of the .SBR file that caused the error. |
| |
One of the following may be a cause:
The wrong database name was specified.
The database file was corrupted, requiring a full build.
|