| Number | MPC Warning Message |
| MP4001interpreter segment not FIXED | ||
| The segment containing the p-code interpreter must be fixed when generating real-mode Windows executable files. | ||
| MPC considered the p-code interpreter segment to be FIXED. | ||
| The following lines in a LINK module-definition (.DEF) file will eliminate this warning:
SEGMENTS $$PCD_INTERP FIXED |
||
| MP4002executable file contains no p-code : filename | ||
| The given .EXE or .DLL file did not contain any p-code. | ||
| MPC copied the given file to the output filename without modification. | ||
| MP4003file already processed by MPC : filename | ||
| The given .EXE or .DLL file has already been processed by MPC. | ||
| MPC copied the given file to the output filename without modification. | ||
| MP4004far data reference to movable segment: source segment:????, target segment:offset | ||
| The source segment contained a far data reference to the target map address, which is in a movable segment. This is illegal when creating a real-mode Windows executable file. | ||
| These references are dangerous when running Windows in real mode because data segments can move, causing the references to be invalid. | ||
| To find the function that caused this warning, 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. | ||
| Relink the executable file using a module-definition (.DEF) file to mark the target segment as FIXED or to mark the executable file as PROTMODE. | ||
| MP4005interpreter debug data segment not FIXED | ||
| The segment containing the p-code interpreter debug data must be FIXED when when creating a real-mode Windows executable file. | ||
| MPC considered the interpreter debug data segment to be FIXED. | ||
| MP4006CVPACK has not been run on this executable file | ||
| The executable file contains Microsoft symbolic debugging information, but CVPACK has not been run. | ||
| MPC requires CVPACK-processed debugging information. | ||
| Run CVPACK on the executable file, then rerun MPC. | ||
| MP4007MAP file parse failed at line number in file filename | ||
| MPC could not read the map (.MAP) file for this executable file. | ||
| The map file was ignored. | ||
| Either relink the executable file to generate a new map file or delete the current corrupt map file. | ||
| MP4008internal optimization error; turn off quoting for segment:offset | ||
| A physical segment used more than 256 global variables and functions or contained more than 256 functions. This can cause problems when using p-code quoting optimization. | ||
| To find the function that caused this warning, 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 turn off the p-code quoting optimization, use #pragma optimize( “f”, off ) or the /Of- command-line option. | ||