| CK1000unknown error; contact Microsoft Product Support Services |
|
| |
CVPACK detected an unknown error condition. |
| |
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. |
| CK1001out of memory |
|
| |
The executable file is too big for the available memory. This error can occur under DOS when there is little extra memory. Even though CVPACK uses virtual memory, which involves swapping to disk, some information can be stored only in real memory. |
| |
One of the following may be a solution:
 Recompile one or more of the object files without debugging information. If the file was compiled using the /Zi option, use either /Zd or no option.
Add more memory to your computer.
|
| CK1002out of virtual memory |
|
| |
There was not enough virtual memory for CVPACK to pack the executable file. Virtual memory can be any of the following:
Conventional memory. Remove TSR (terminate-and-stay-resident) programs or run CVPACK outside of a shell or a makefile.
Extended or expanded memory. Run CVPACK under a DPMI server, such as MSDPMI.EXE or the server provided in a DOS session under Windows enhanced mode.
Disk space. Free some disk storage.
|
| CK1003cannot open file |
|
| |
CVPACK could not open the specified executable file. |
| |
One of the following may be a cause:
The specified file does not exist. Check the spelling of the filename and path.
The executable file was opened or deleted by another process.
|
| CK1004file is read-only |
|
| |
CVPACK cannot pack a read-only file. Change the read attribute on the executable file and run CVPACK again. |
| CK1005invalid executable file |
|
| |
CVPACK could not process the executable file. One of the following may be a cause:
The debugging information in the executable file is corrupt.
The executable file is a zero-length file.
|
| CK1006invalid module module |
|
| |
The given object file did not have a valid format. |
| |
Check the linker version. |
| CK1007invalid table table in module module |
|
| |
The given table in the given object file was not valid. |
| |
Check the compiler and linker versions. |
| CK1008cannot write packed information |
|
| |
There was not enough space on disk for CVPACK to write the packed executable file. This leaves a corrupt file on disk. |
| |
Make more space available on disk and relink the program. |
| CK1009module module unknown type index number; contact Microsoft Product Support Services |
|
| |
The debugging information in the executable file is corrupt. This is due to an internal error in either the compiler or CVPACK. Recompile the program. 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. |
| CK1010symbol error in module module; contact Microsoft Product Support Services |
|
| |
The debugging information in the executable file is corrupt. This is due to an internal error in either the compiler or CVPACK. Recompile the program. 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. |
| CK1011error in type number for module module; contact Microsoft Product Support Services |
|
| |
The debugging information in the executable file is corrupt. This is due to an internal error in either the compiler or CVPACK. Recompile the program. 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. |
| CK1012no Symbol and Type Information |
|
| |
The executable file does not contain debugging information. |
| |
Link the program using the /CO option to put at least minimal debugging information in the executable file. To include full debugging information in an object file, compile or assemble using the /Zi option. To include minimal information and line numbers, compile or assemble using the /Zd option. |
| CK1013debugging information missing or unknown format |
|
| |
One of the following has occurred:
The program did not contain debugging information. Recompile using /Zi or /Zd, then link using /CO.
The executable file was linked using an obsolete or unsupported linker. Use Microsoft LINK version 5.3x or later.
The executable file was already packed using a previous version of CVPACK.
|
| CK1014module module type number refers to skipped type index; contact Microsoft Product Support Services |
|
| |
The debugging information in the executable file is corrupt. This is due to an internal error in the compiler. Recompile the program. 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. |
| CK1015too many segments in module module |
|
| |
The alloc_text pragma was used more than 20 times in an object file that was compiled with Microsoft C version 6.x or earlier. |
| |
One of the following may be a solution:
Recompile using Microsoft C/C++ version 7.0 or later.
Split the object file into multiple files.
Group the pragma statements according to segment.
|
| CK1016unable to execute MPC for CVPACK /PCODE |
|
| |
CVPACK could not find MPC.EXE on the path. |
| CK1017precompiled types file filename not found |
|
| |
The program used a precompiled header, but the program was linked without the object file that was created when the header was precompiled. |
| CK1018precompiled types object file filename inconsistent with precompiled header used to compile object file filename |
|
| |
The program used a precompiled header, but the object file linked to the program was not the object file that was created when the header was precompiled. Either the user or the creator changed since the last compilation. |
| |
Recompile and relink. If a makefile is used, check the makefile dependencies. |
| CK1020packed type index exceeds 65535 in module module |
|
| |
The debugging information exceeded a CVPACK limit. |
| |
This error may occur when precompiled headers are used. |
| |
One of the following may be a solution:
Eliminate unused type strings.
Compile some object files without debugging information.
|
| CK1021error in precompiled types signature in module module |
|
| |
The program was compiled with an out-of-date precompiled header. |
| |
Delete the object file and recompile. |