| MP1001cannot open file : filename |
|
| |
The given file either did not exist, could not be opened, or was not found. |
| |
One or more of the following can cause this error:
 The file was read-only or was being used by another process.
An invalid filename or path was specified.
MPC ran out of file handles. To increase the number of available file handles, change the FILES setting in CONFIG.SYS. FILES=50 is the recommended setting.
The environment settings were invalid.
There was a disk media error or an open floppy disk drive door.
|
| MP1002file I/O error : filename |
|
| |
There was an error when working with the given file. |
| |
One or more of the following can cause this error:
There was a disk media error or an open floppy disk drive door.
The file was read-only or was being used by another process.
There was insufficient space on the specified drive.
The file was corrupt.
|
| MP1010filename is not a segmented executable file |
|
| |
The given file was not a valid segmented executable file. MPC can only operate on segmented executable files. |
| |
Make sure that the given filename was compiled and linked with the correct command-line options to generate a segmented executable file. |
| |
P-code object modules contain special-purpose records that force the generation of a segmented executable file. When building an MS-DOS p-code program, MPC converts the segmented executable file to an unsegmented executable file. |
| MP1040out of memory |
|
| |
The MPC program ran out of memory and was unable to recover. |
| |
One of the following may be a solution:
Remove other programs or drivers running in the system, which could be consuming significant amounts of memory.
Recompile some of the p-code functions as native code and relink.
Run MPC directly from the command line, instead of from CL, LINK, NMAKE, or PWB.
|
| MP1041unsupported fixup; source type type flags flags |
|
| |
MPC has encountered an unsupported relocation fixup in the executable file. |
| |
This warning can be generated by dynamic-link library (DLL) fixups in an MS-DOS executable file. This warning can also be caused by using 32-bit code in a p-code executable file. P-code supports only 16-bit programs. |
| MP1042too many p-code segments |
|
| |
The p-code limit of 255 segments was exceeded. |
| |
Each physical segment containing p-code functions or functions referenced by p-code routines is divided into one or more p-code logical segments. There is a limit of 255 p-code logical segments per executable file. |
| |
To reduce the number of physical p-code segments, select segments that reference or are referenced by many functions and compile them into native code by using #pragma optimize( “q”, off ). The number of p-code segments can also be reduced by combining physical segments. |
| MP1043too many DLL functions referenced |
|
| |
The maximum number of dynamic-link library (DLL) functions referenced from p-code was exceeded. A maximum of 255 DLL entry points can be referenced from p-code in each executable file. |
| |
To eliminate this error, reduce the DLL reference count by recompiling some p-code functions that call DLL functions into native code. |
| MP1044too many functions referenced by p-code function at address |
|
| |
The maximum number of unique functions referenced by a p-code function was exceeded. A maximum of 255 unique functions can be referenced by a p-code function. |
| |
To find the function that caused this error, look up the given map address in the .MAP file generated from the executable file. To generate a .MAP file, use the CL /Fm command-line option or the LINK /MAP command-line option. |
| |
To correct this error, either recompile the routine at the specified map address to native code or split the function into subfunctions that call fewer functions. |
| MP1045too many globals referenced by p-code function at address |
|
| |
The maximum number of unique global variables referenced by a p-code function was exceeded. A maximum of 255 unique global variables can be referenced by a p-code function. |
| |
To find the function that caused this error, look up the given map address in the .MAP file generated from the executable file. To generate a .MAP file, use the CL /Fm command-line option or the LINK /MAP command-line option. |
| |
To correct this error, either recompile the routine at the specified map address to native code or split the function into subfunctions that reference fewer global variables. |
| MP1046unused entry number |
|
| |
MPC has detected an unused entry in the module entry table. Unused entries are not currently supported by MPC. |
| MP1047entry table overflow; attempted to extend segment table to number |
|
| |
The 64K limit of the segment table was exceeded. |
| |
MPC adds an entry to the segment table for each movable p-code segment and dynamic-link library (DLL) entry point. |
| |
To correct this situation, either reduce the number of p-code segments or mark some of the p-code segments as FIXED. |
| MP1048too many imported functions : number |
|
| |
Too many imported functions were referenced by p-code functions. The limit is 4680 imported functions. |
| |
Reduce the number of imported functions referenced by p-code functions by recompiling p-code functions into native code or by moving references to imported function to native code. |
| MP1049invalid executable file : filename |
|
| |
The given executable file contains errors. MPC will not process invalid executable files. |
| |
Relink the program so that no errors are generated. |
| MP1051imported names table overflow |
|
| |
There were too many imported names in the executable file, causing the MPC buffer to overflow. The buffer is 64K bytes. |
| |
Reduce the number of imported names in the executable file. |
| MP1080p-code interpreter not found : filename |
|
| |
MPC could not find the p-code interpreter in the given file. |
| |
Relink the executable file, making sure that no link errors occur. This error can also be caused by adding information to the reserved p-code interpreter segment. |
| MP1081MPC fixup segment not found: filename |
|
| |
MPC could not find any p-code fixup segments in the given executable file. |
| |
The compiler emits special p-code fixup data to reserved data segments. These segments could not be found. |
| MP1082invalid data found in executable file at segment:offset |
|
| |
MPC detected corrupted code or data in the executable file at the given address. |
| |
Recompile the source files containing p-code and relink the executable file. If the error persists, compile the function at the given address into native code. |
| MP1083segment overflow writing p-code tables in segment segment |
|
| |
The writing of p-code tables at the end of the given segment caused the segment to exceed 64K. This segment contains or is referenced by p-code functions. |
| |
Reduce the size of the given segment and relink. If the LINK /PACKC option is being used, specify an amount to reserve for the p-code tables (512 bytes is the recommended amount.) |
| MP1084nonsegmented executable file cannot contain imported routines |
|
| |
MPC attempted to generate a nonsegmented executable file, but encountered references to imported functions. This indicates a protected-mode executable file. |
| |
Relink the executable file using real-mode libraries. |
| MP1085Windows application does not reference module KERNEL |
|
| |
When generating a real-mode Windows executable file, MPC requires a reference to the Windows KERNEL module in the executable file. This allows MPC to add the appropriate memory-management information to the p-code executable file. |
| |
This error is usually caused by a corrupted library. |
| |
Relink the executable file, making sure that no errors occur in the linking process. |