Explanation: A
disk error occurred while seeking either the message file or the .EXE file.
Action: Run CHKDSK on the drive containing the file and restart MSGBIND.
MSGBIND: I/O error writing file
Explanation: A
disk error occurred while writing messages to the .EXE file.
Action: Run CHKDSK on the drive containing the .EXE file, and restart
MSGBIND.
MSGBIND: Must specify .EXE file before
message file
Explanation: The input file
was in error.
Action: Correct input file.
MSGBIND: Must
specify message file before message number
Explanation: The
input file was in error.
Action: Correct the input file.
MSGBIND:
Out of memory, needed xxxx bytes
Explanation: There
was not enough memory available to run MSGBIND.
Action: Reduce the number of programs presently running in your system
and restart MSGBIND.
MSGBIND: Premature EOF during
copy
Explanation: The .EXE file was not
built correctly.
Action: Rebuild the .EXE file and restart MSGBIND.
MSGBIND:
Unable to create temp file-MSGBIND.TMP
Explanation: An
error occurred while creating the intermediary file MSGBIND.TMP.
Action: Delete or move files to make disk space available. If MSGBIND.TMP
is present as a read-only file, it must first be deleted. Restart MSGBIND.
MSGBIND: Unable to open xxxxxxxx
Explanation: The
input file specified was not found or an error occurred when opening the
message file.
Action: Restart MSGBIND using the correct input file name or a backup
copy of the message file.
Number of Message Files
exceeded. Only nnn allowed
Explanation: The
number of message files specified in the input file exceeds the maximum
number of files that MSGBIND can process at one time.
Action: Correct the input file or combine message files, and then
restart MSGBIND.
Reading messages from xxxxxxxx
Explanation: Messages from the displayed
message file are being read into memory.
Action: None. This message is for information only.
Reading
messages from xxxxxxxx -file not found
Explanation: The
message file was not found in the path specified in the input file.
Action: Edit the input file, correcting the path or file name, or
both. Restart MSGBIND.
Reading messages from xxxxxxxx
-not created with MKMSGF program
Explanation: The
message file displayed was not created using the MKMSGF program.
Action: Convert the source message file to a formatted message file
using the MKMSGF program, and restart MSGBIND. See the Make
Message File (MKMSGF).
Reading messages from
xxxxxxxx -not enough memory
Explanation: There
was not enough memory available to store the messages.
Action: Reduce the number of programs running in your system, and
restart MSGBIND.
The object that would contain the
bound messages would be too large. Refer to the Toolkit Documentation for
more information.
Explanation: (self explanatory)
Action: Do one or more, of the following:
Modify the module definition file to isolate
the message object, and then relink the application.
Reduce the number of messages to be bound to
the application as specified in the input file.
Reduce the size of the messages and rebuild
the message file with MKMSGF.
Then restart MSGBIND.
Unable
to bind message nnnn, message segment would exceed 64K. The remaining messages
will NOT be bound.
Explanation: (self explanatory)
Action: Do one or more, of the following:
Modify the module definition file to isolate
the message object, and then relink the application.
Reduce the number of messages to be bound to
the application as specified in the input file.
Reduce the size of the messages and rebuild
the message file with MKMSGF.
Then restart MSGBIND.
Unable
to locate call to Dos32GetMessage, messages will not be bound.
Explanation:
The executable file to be modified makes no function calls to the message
retriever, or was not linked with the correct library file.
Action: If the application does use the message retriever function,
such as DosGetMessage, relink the application using the correct library
file, and then restart MSGBIND.
If not, messages cannot be bound to the application.
Updating
xxxxxxxx
Explanation: The .EXE file
name displayed is being updated with the requested messages.
Action: None. This message is for information only.
Updating
xxxxxxxx -file not found
Explanation: The
.EXE file name was not found in the path specified in the input file.
Action: Edit the input file, correcting the path or file name, or
both. Restart MSGBIND.
Updating xxxxxxxx -not
linked with MSGSEG.OBJ
Explanation: The
.EXE file name displayed made no DosGetMessage functions, or the .EXE file
was not linked with the correct library. Messages can only be bound to applications
that call message retriever functions, such as DosGetMessage.
Action: If the .EXE file does make calls to message retriever functions,
relink the application using the correct library, and restart MSGBIND.
usage:
MSGBIND scriptfile
Explanation: The command
was entered incorrectly.
Action: Restart MSGBIND. Refer to Syntax
for the correct syntax.
Warning: No msgseg data
found in new executable
Explanation: The
executable file to be modified makes no function calls to the message retriever,
or was not linked with the correct library file.
Action: If the application does use the message retriever function,
such as DosGetMessage, relink the application using the correct library
file, and then restart MSGBIND.
If not, messages cannot be bound to the application.
WARNING:
Skipping messages for this file
Explanation: The
.EXE file was in error, so the messages were not bound to it. Either the
.EXE file does not exist, or it has not been linked with the correct library.
Action: If the .EXE file name is correct, relink the application
using the correct library, and restart MSGBIND.
WARNING:
Skipping message numbers for this file
Explanation: The
message file was in error, so all messages from this message file were ignored.
The message file might not exist, might not be formatted correctly, or there
might not be enough memory to store all the messages.
Action: If the message file name is correct and has been correctly
formatted, check the memory available for the file. Restart MSGBIND.
WARNING:
xxxx is an invalid message number
Explanation: The
message number specified was not found in the message file.
Action: Edit the input file and correct any message numbers that
are in error. Restart MSGBIND.
Writing messages
Explanation: The .EXE file is being updated
with the messages requested.
Action: None. This message is for information only.