0.1 BIND Error Messages

This section lists error messages generated by the Microsoft Bind Utility (BIND). BIND errors (U12xx) are always fatal.

Number

BIND Error Message

U1250	invalid executable file
	The executable file cannot be bound. Either the header is invalid, or the executable file has an invalid magic number.
	Repeat with a backup version of the executable file, or rebuild the file and repeat.
U1251	cannot create file : filename
	BIND was unable to create a temporary file or the map file, probably because the disk was full.
U1252	unrecoverable I/O error
	The system returned an I/O error when reading the executable file.
U1253	cannot open file : filename
	The given file could not be opened.
	The following are possible causes of this error: The file does not exist. The file is in use by another process. The disk is full.
U1254	structure error in .EXE file
	The executable file has an invalid structure.
	Rebuild the file.
U1255	structure error in .LIB file : filename
	The given library file has an invalid structure. Library files must conform to Microsoft object module format.
	Repeat with a backup version of the library file, or rebuild the library and repeat.
U1256	out of memory
	There was insufficient memory for BIND to run.
U1257	too many libraries specified, number allowed
	The BIND command line contained more than the given number of libraries.
	Combine some libraries.
U1258	resource tables not supported
	Protected-mode executable files that use resource tables cannot be bound because when the bound executable file runs in DOS mode the resources would be unknown.
U1259	internal error — Lname not found : lname
	BIND encountered an internal error.
	Repeat the attempt with a new copy of BIND. If the problem persists, 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.
U1260	import by ordinal not defined : dllname.ordinal
	The given DLL does not contain a function with the given ordinal value. As a result, fixups from function calls to this function cannot be made.
U1261	system call syscall return error
	BIND encountered an internal error.
	Repeat the attempt with a new copy of BIND. If the problem persists, note the circumstances of the error and notify Microsoft Corporation by following the instructions in the Microsoft Product Assistance Request form at the back of one of your manuals.
U1262	cannot find LINK.EXE in path
	BIND could not find LINK.EXE in any directory specified by the PATH environment variable.
	BIND needs the linker to complete the binding operation.
U1263	error during link of file, link error status : status
	A linking error occurred during the LINK session invoked by BIND.
	The following are possible causes of this error: Unresolved references exist in the files. BIND could not resolve references with API.LIB or other support libraries. APILMR.OBJ was used when the executable file was created, and LINK gave error L2044, symbol multiply defined, use /NOE. Relink using the LINK option /NOE, then rebind. There was not enough memory. A disk I/O error occurred.
U1264	unrecognized option : option
	The BIND command line contained the given unrecognized option.
U1265	unrecognized argument : string
	The given string is not a valid argument for the option it was specified with.
U1266	no infile specified
	No executable file to be bound was named on the BIND command line.
U1267	no outfile specified
	The option for naming an outfile, /o, was given on the command line, but no file was named.
U1268	duplicate infile name given : filename
	The given file was named in more than one place on the BIND command line.
U1269	duplicate global name : name
	The given global name was defined in more than one place in the specified libraries, making a unique fixup impossible.
	This error can be caused by specifying both OS2.LIB and DOSCALLS.LIB. To correct the error, specify only OS2.LIB.
U1270	terminated by user
	BIND was halted by CTRL+C or CTRL+BREAK.
U1271	insufficient disk space
	There was not enough room on the disk. BIND creates temporary files that take up disk space.
	Make some room on the disk and repeat.
U1272	cannot bind a PROTMODE executable
	The module-definition file used to create the executable file contained a PROTMODE statement. This statement creates an executable file that cannot be run under DOS and prevents the file from being bound.