Specifications

Error! Style not defined. 691
Filename: LMAETAPA.DOC Project: MASM Environment and Tools
Template: MSGRIDA1.DOT Author: Nobody Last Saved By: Mike Eddy
Revision #: 136 Page: 691 of 7 Printed: 10/09/00 02:49 PM
BK1513 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.
One of the following may be a cause:
u The database file was missing.
u The wrong database name was specified.
u The database was corrupted, and a full build was required.
BK1514 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 BK4502, which will give the name of the .SBR
file that caused the error.
One of the following may be a cause:
u The wrong database name was specified.
u The database was corrupted, and a full build was required.
BK1515 bscfile : incompatible version; cannot incrementally update
The given database (.BSC file) was not created with this version of BSCMAKE.
A database can be incrementally built only by the same version of BSCMAKE as the
one used to fully build the database.
BSCMAKE Warning Messages
BK4500 UNKNOWN WARNING
Contact Microsoft Product Support Services
An unknown error condition was detected by BSCMAKE.
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.
BK4501 ignoring unknown option option
BSCMAKE did not recognize the given option and ignored it.
If the given option is /r, it must be specified first on the BSCMAKE command line.