0.2 CodeView Error Messages

CodeView displays an error message whenever it detects a command it cannot execute. Most errors terminate the CodeView command in error, but do not terminate the debugger. Start-up errors terminate CodeView.

Depending on the context of the error, CodeView may display only the text of the message without the error number. This section is organized in alphabetical order by message text.

In some cases, CodeView may display the error number by itself. To obtain the error message and an explanation of the error in thoses cases, use online help. Click the right mouse button on the error number or use the Help (H) Command-window command. For example,

H CV1020

displays help for the error Divide by zero.

Error Message  

Access denied (CV0013)  
  A specified file's permission setting does not allow the required access.
  One of the following may have occurred:

An attempt was made to write to a read-only file.

A locking or sharing violation occurred.

An attempt was made to open a directory instead of a file.

Address of register variable cannot be watched (CV1049)  
  An attempt was made to evaluate the address of a register variable. A register variable can be watched but not the address of a register variable.
  One of the following occurred:

The variable was declared as a register variable. Recompile the program with the register declaration removed.

The optimizer converted an ordinary variable into a register variable to speed up execution. Recompile the program using the /Od option to turn optimization off.

The function was defined with _fastcall, causing parameters to be passed in registers. Remove the _fastcall designation and recompile.

All threads blocked (CV3502)  
  The block may be due to a request for a system service semaphore. When the semaphore is cleared, the block will clear.
  The block may also be due to a deadlock situation that will not clear until one or more of the threads are terminated.
Arg list too long (CV0007)  
  CodeView is not able to restart the program being debugged because the number of arguments to the executable program exceeds the limit of 128.
Argument to IMAG/DIMAG must be simple type (CV1121)  
  An invalid argument was specified to IMAG or DIMAG, such as an array with no subscripts.
Array must have subscript (CV1101)  
  An array was specified without any subscripts, such as IARRAY+2. A correct example would be IARRAY(1)+2.
Bad integer or real constant (CV1105)  
  An illegal numeric constant was specified in an expression.
Bad intrinsic function (CV1106)  
  An illegal intrinsic function name was specified in an expression.
Bad subscript (CV1100)  
  An illegal subscript expression was specified for an array.
  For example, IARRAY(3.3) and IARRAY((3,3)) are illegal. The correct expression is IARRAY(3,3).
Badly formed type (CV1009)  
  CodeView detected corrupt information in the symbol table of the file being debugged.
  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.
Breakpoint number or '*' expected (CV1006)  
  A breakpoint was specified without a number or asterisk.
  A Breakpoint Clear (BC), Breakpoint Disable (BD), or Breakpoint Enable (BE) command requires one or more numbers to specify the breakpoints, or an asterisk to specify all breakpoints.
  For example, the following command causes this error:

bc a

Cannot cast complex constant component into REAL (CV1112)  
  Both the real and imaginary components of a COMPLEX constant must be compatible with the type REAL.
Cannot cast IMAG/DIMAG argument to COMPLEX (CV1122)  
  Arguments to IMAG and DIMAG must be simple numeric types.
Cannot create CURRENT.STS (CV1063)  
  CodeView could not find an existing state file (CURRENT.STS), and it tried to create one but failed.
  One of the following may have occurred:

There was not enough space either on the disk containing the program to be debugged or on the disk pointed to by the INIT environment variable.

There were not enough free file handles. In DOS, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=20 is the recommended setting. In OS/2, if multiple processes are running, removing one or more of them may release enough file handles.

The environment variable INIT pointed to a directory that does not exist. If the variable points to more than one directory, the first directory listed does not exist.

Cannot create \QUEUES\CVP (CV3601)  
  One or more of the required queues could not be created.
  When debugging multiprocess programs, CodeView creates multiple copies of itself that intercommunicate through queues.
  The failure to create queues may be due to lack of memory, or to having too many OS/2 processes running at one time.
Cannot create \SEM\CVP (CV3605)  
  The required semaphore could not be assigned.
  When debugging multiprocess programs, CodeView allocates areas of shared memory for interprocess communication.
  The failure to assign a semaphore may be due to lack of memory or to having too many OS/2 processes running at one time.
Cannot create \SHAREMEM\CVP (CV3604)  
  The required shared memory could not be assigned.
  When debugging multiprocess programs, CodeView allocates areas of shared memory for interprocess communication.
  The failure to assign shared memory may be due to lack of memory or to having too many OS/2 processes running at one time.
Cannot open CV.EXE (CV1310)  
  An error occurred while CV.EXE was being opened.
  One of the following may have occurred:

The file could be corrupt. Copy CV.EXE from the original disks and retry.

The operating system could not find CV.EXE due to a disk error.

There were not enough free file handles. In DOS, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=20 is the recommended setting. In OS/2, if multiple processes are running, removing one or more of them may release enough file handles.

  If the error recurs, 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.
Cannot open \QUEUES\CVP (CV3602)  
  One or more of the required queues could not be opened.
  When debugging multiprocess programs, CodeView creates multiple copies of itself that intercommunicate through queues.
  The failure to open queues may be due to lack of memory or to having too many OS/2 processes running at one time.
Cannot open \SHAREMEM\CVP (CV3606)  
  The required shared memory could not be opened.
  When debugging multiprocess programs, CodeView tries to access areas of shared memory for interprocess communication.
  The failure to open shared memory may be due to lack of memory or to having too many OS/2 processes running at one time.
Cannot open \SEM\CVP (CV3607)  
  The required semaphore could not be opened.
  When debugging multiprocess programs, CodeView tries to access areas of shared memory for interprocess communication.
  The failure to open a semaphore may be due to lack of memory or to having too many OS/2 processes running at one time.
Cannot read CV.EXE (CV1311)  
  An error occurred while CV.EXE was being read. Possibly the operating system could not find CV.EXE due to a disk error.
  If the error recurs, 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.
Cannot read file (CV5004)  
  A file was selected from a dialog box, and CodeView then opened the file. The read process failed while the file was being read.
  Read the file again. If the second read fails, exit and restart CodeView. If the read process still fails, the file may be corrupt.
Cannot read this version of CURRENT.STS (CV1054)  
  The state file (CURRENT.STS) has a version number that is not recognized by this version of CodeView.
  Check the directories for older copies and delete them.
Cannot restart program, out of system resources (CV3611)  
  The operating system reached its limit of one of the following resources:

Memory

Screen groups

Threads

Cannot select (CV5001)  
  The cursor was not on the same line as an automatically selectable symbol.
Cannot understand entry in TOOLS.INI or CURRENT.STS (CV1056)  
  At least one line in the given file (either the state file or the TOOLS.INI file) could not be interpreted.
  On start-up, CodeView reads the state file (CURRENT.STS) and the TOOLS.INI file (if the latter is available).
  Examine the given file to find the problem.
Cannot use second monitor from VIO window (CV3610)  
  The operating system cannot support a second monitor from a virtual I/O window (Presentation-Manager text window).
Cannot use struct or union as scalar (CV1025)  
  A structure or union was used in an expression, but no element was specified.
  When requesting display of a structure or union variable, the name of the variable may appear by itself, without a field qualifier. If a structure or union is used in an expression, it must be qualified with the specific element desired.
  Specify the element whose value is to be used in the expression.
Character constant too long (CV1109)  
  A character constant was specified that is too long for the FORTRAN expression evaluator (the limit is 126 bytes).
  Use the Radix (N) command to change the radix.
Character too big for current radix (CV1120)  
  A radix was specified in a constant that is larger than the current radix.
Command incompatible with history (CV2202)  
  The command entered is illegal while recording because it changes the state of CodeView and/or the program being debugged.
  For example, the Restart (L) command cannot be used during recording.
  Turn off history to use the command.
Constant too big (CV1028)  
  CodeView cannot accept an unsigned integer constant larger than 4,294,967,295 (0xFFFFFFFF hex), or a floating-point constant whose magnitude is larger than approximately 1.8E+308.
Corrupt debug OMF detected in file, discarding source line information (CV2206)  
  The linker used was not the current version of the Microsoft linker.
  Conditions that require the most current linker include use of the alloc_text pragma in a C program and use of multiple segments in an assembly-language module.
Corrupted CV.EXE (CV1318)  
  The CV.EXE file has been corrupted. Copy CV.EXE from the original disks and retry.
  If the error recurs, 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.
CURRENT.STS not found—creating default (CV1057)  
  The state file (CURRENT.STS) could not be located at start-up, so CodeView created a state file.
Divide by zero (CV1020)  
  The expression contains a divisor of zero, which is illegal. This divisor might be the literal number zero, or it might be an expression that evaluates to zero.
/E: EMM driver not loaded (CV1304)  
  The EMM driver must be installed in order to use expanded memory.
/E: EMM internal error (CV1309)  
  An unexpected error from the EMM driver occurred. The driver may be corrupted or may have malfunctioned.
  If replacing the EMM driver does not correct the problem, 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.
/E: EMM not LIM 4.0 or later (CV1305)  
  The EMM driver must be LIM EMS version 4.0 or later in order to contain the calls needed for CodeView to use expanded memory.
/E: no EMM handle available (CV1306)  
  No handle is available for the CodeView overlay code.
  One of the following may be a solution:

If possible, increase the number of EMM handles that are allocated when the EMM driver is loaded.

If multiple applications are running, remove one or more of the applications that use expanded memory. This should free enough handles to permit CodeView to run properly.

Some memory may have become inaccessible due to program error. Reboot in order to free the memory.

/E: not enough free expanded memory (CV1308)  
  There is currently not enough room in expanded memory to load overlays.
  One of the following may be a solution:

Decrease the size of memory allocated to SMARTDRV.SYS or RAMDRIVE.SYS to free expanded memory.

Reconfigure the EMM driver or hardware to allocate more expanded memory.

/E: not enough total expanded memory (CV1307)  
  There is not enough room in all of expanded memory to load overlays. Freeing expanded memory will not help.
  If possible, reconfigure the EMM driver or hardware to allocate more expanded memory.
EMM error (CV3010)  
  An unknown expanded memory error has occurred.
  One of the following may have occurred:

The EMM driver may be corrupted or may have malfunctioned. Reload the driver and retry.

There was a disk error.

  If the error recurs, 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.
EMM hardware error (CV3001)  
  An error has occurred in expanded memory.
  Exit CodeView and reboot the computer. If this does not correct the problem, the expanded memory board may need service.
EMM memory not found (CV3011)  
  CodeView cannot find expanded memory.
  The EMM driver or expanded memory board is not installed, or the board has a malfunction.
EMM software error (CV3000)  
  An error has occurred in the EMM driver.
  Exit CodeView and reboot the computer. If the problem recurs, replace the EMM driver file with a fresh copy from the EMM driver's distribution disk. If this does not correct the problem, the expanded memory board may need service.
Executable file format error (CV0008)  
  The system is not able to load the program to be debugged. The file is not an executable file, or it has an invalid format for this operating system.
  Try to run the program outside of CodeView.
Expression not a memory address (CV1050)  
  The expression entered does not evaluate to an address. An address must be a numeric value.
  An lvalue (so called because it appears on the left side of an assignment statement) is an expression that refers to a memory location.
  For example, buffer[count] is a valid lvalue because it points to a specific memory location. The logical comparison zed != 0 is not a valid lvalue because it evaluates to TRUE or FALSE, not a memory address.
Expression too complex (CV1019)  
  The expression entered was too complex for the amount of storage space available to the expression evaluator.
  Overflow usually occurs because of too many pending calculations. Rearrange the expression so that each component of the expression can be evaluated immediately, rather than having to wait for other parts of the expression to be calculated.
Extra input ignored (CV1003)  
  The first part of the command line was interpreted correctly.
  The remainder of the line could not be interpreted or was unnecessary.
File error (CV1041)  
  CodeView could not write to the disk.
  One of the following may have occurred:

There was not enough space on the disk.

The file was locked by another process.

Flip/Swap option off—application output lost (CV1043)  
  The program being debugged wrote to the display when Flip/Swap was off. The program output was lost.
  When flipping is on, video page 1 is normally reserved for CodeView, while programs by default write to video page 0. Programs that write to video page 1 must be debugged with swapping on.
  Turn Flip/Swap on to be able to view program output.
Floating-point support not loaded (CV1048)  
  An attempt was made to access the math processor registers in a program that does not use floating-point arithmetic.
  Several situations can cause this error:

The math processor registers can only be accessed through the floating-point library code. This code is not loaded if the program does not perform floating-point calculations.

If the program does not use floating-point instructions, this error may occur when attempting to access the math processor before any floating-point instructions have been performed. The C run-time library includes a floating-point instruction near the beginning so that the math processor registers are always accessible.

If a floating-point instruction occurs in an assembly-language routine before such an instruction occurs in the C code that calls the routine, this error occurs.

Function argument may not be byte register (CV4058)  
  The register specified in the function does not accept a byte value. The register must be assigned a word or doubleword value.
Function call before stack frame initialization (CV1026)  
  A function call cannot be executed until after the BP (stack frame) register has been initialized.
  Run the program to a statement that follows initialization of the BP register. This is usually set up as the first statement in the first function of the program.
Function returning struct/union not supported (CV1060)  
  CodeView cannot evaluate a function that returns a structure or union variable.
I/O error (CV0005)  
  An attempt was made to access an address that is not accessible to the program being debugged.
  Check the previous command for numeric constants used as addresses and for pointers used for indirection.
Illegal instruction (CV4001)  
  An assembler instruction was not recognized.
  The instruction may have been mistyped.
Illegal operand (CV4003)  
  The specified operand is not permitted with this instruction.
  The operand name may have been mistyped.
Illegal size for item (CV4036)  
  The wrong size was specified for the data item.
Illegal usage of CS register (CV4059)  
  The CS (code segment) register cannot be addressed in the function specified.
Index out of bound (CV1102)  
  A subscript value was specified that is outside the bounds declared for the array.
Insufficient EMM memory (CV3007)  
  CodeView tried to allocate expanded memory, but there was not enough space.
  Possible solutions include the following:

Run CVPACK on the executable file to reduce the demand on memory for symbolic information.

Recompile without symbolic information in some of the modules. CodeView requires memory to hold information about the program being debugged. Compile some modules with the /Zd option instead of /Zi, or don't use either option.

If multiple applications are running, remove one or more of the applications that use expanded memory. This may free enough memory to permit CodeView to run properly.

Allocate more expanded memory in the system configuration.

Internal debugger error: n (CV0100)  
  CodeView has encountered an internal error. Quit and restart.
  If the error recurs, 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.
Internal error—unrecoverable fault (CV1319)  
  The DOS extender encountered a general protection fault.
  The CodeView file may be corrupt. Reboot and copy CV.EXE from the original disks and retry.
  If the error recurs, 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.
Invalid address (CV0014)  
  The View (V) command was followed by an argument that could not be interpreted as a valid address.
  A name or constant may have been specified without the period (.) that indicates a filename or line number.
Invalid argument (CV0022)  
  An invalid value was given as an argument in the most recent command.
  One of the following may have occurred:

An invalid argument was passed to the Go (G) command.

An invalid argument was passed to the Delete Watch Expression (Y) command.

Invalid breakpoint command (CV1001)  
  CodeView could not interpret the breakpoint command.
  The command probably used an invalid symbol or the incorrect command format.
Invalid executable file—please relink (CV1046)  
  The executable file did not have a valid format.
  One of the following may have occurred:

The executable file was not created with the linker released with this version of CodeView. Relink the object code using the current version of LINK.EXE.

The .EXE file may have been corrupted. Recompile and relink the program.

Invalid flag (CV1022)  
  An attempt was made to examine or change a flag, but the flag name was not valid.
  Any flags preceding the invalid name were changed to the values specified. Any flags after the invalid name were not changed.
  Use the flag mnemonics displayed after entering the R FL command.
Invalid format in CV.EXE (CV1313)  
  The CV.EXE file has been corrupted. Copy CV.EXE from the original disks and retry.
  If the error recurs, 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.
Invalid format specifier (use one of ABDILSTUW) (CV1021)  
  A Dump (D), Enter (E), or View Memory (VM) command included a format specifier that is not recognized by CodeView.
  The valid format specifiers are

Specifier Display Format

A ASCII
B Byte
I Integer
U Unsigned integer
W Word
D Doubleword
S Short real
L Long real
T 10-byte real

Invalid format string (CV1038)  
  An invalid format specifier followed an expression.
Invalid operation (CV1062)  
  An attempt was made to set the IP register to a line or address in a different segment.
Invalid process ID (CV3603)  
  An attempt was made to run a process using an ID that does not exist.
  The ID may have been mistyped.
Invalid radix (use 8, 10, or 16) (CV1027)  
  The Radix (N) command takes three radixes: 8 (octal), 10 (decimal), and 16 (hexadecimal). Other radixes are not permitted. The new radix is always entered as a decimal number, regardless of the current radix.
Invalid register (CV1004)  
  The Register (R) command named a register that does not exist or cannot be displayed. CodeView can display the following registers:

AX SP DS IP

BX BP ES FL

CX SI SS

DX DI CS

  When running under DOS or Windows on an 80386/486 machine, the 386 option can be selected to display the following registers:

EAX ESP DS GS

EBX EBP ES SS

ECX ESI FS EIP

EDX EDI CS EFL

Invalid tab setting—assumed 8 (CV2210)  
  The value for tabs cannot be less than 0 or greater than 19. If you supply a value that is not in this range, CodeView defaults to a tab value of 8.
Invalid thread ID (CV3500)  
  An attempt was made to run a thread using an ID that does not exist.
  The ID may have been mistyped.
Invalid type cast (CV1008)  
  An attempt was made to cast a variable to an undefined or user-defined type.
  A cast can be made only to fundamental C types.
Library module not loaded (CV1042)  
  The program being debugged uses load-on-demand DLLs. At least one of these libraries is needed but does not currently exist on the path specified by the LIBPATH environment variable.
LIM 4.0 function not supported (CV3013)  
  CodeView required a function that is not supported in the EMM driver present on the system.
  Either of the following must be done:

Run CodeView without using expanded memory.

Obtain an EMM driver that fully supports LIM EMS version 4.0 or later.

LIM 4.0 subfunction not supported (CV3014)  
  CodeView required a subfunction that is not supported in the EMM driver present on the system.
  Either of the following must be done:

Run CodeView without using expanded memory.

Obtain an EMM driver that fully supports LIM EMS version 4.0 or later.

Loaded symbols for module module (CV2207)  
  CodeView automatically loaded the symbols for the given DLL. The DLL can now be debugged.
Losing History (CV5010)  
  When you restarted the program, CodeView was not able to maintain debug history.
Match not found (CV1016)  
  No string was found that matched the search pattern.
Missing ')' (CV1000)  
  The command contained a left parenthesis (() that lacked a matching right parenthesis ()).
Missing ']' (CV1014)  
  The command contained a left bracket ([) that lacked a matching right bracket (]).
Missing '(' (CV1034)  
  The command contained a right parenthesis ()) that lacked a matching left parenthesis (().
Missing '(' in complex constant (CV1110)  
  CodeView expected an opening parenthesis of a complex constant in an expression, but it was missing.
Missing ')' in complex constant (CV1111)  
  CodeView expected a closing parenthesis of a complex constant, but it was missing.
Missing '(' to intrinsic (CV1113)  
  CodeView expected an opening parenthesis for an intrinsic function, but it was missing.
Missing ')' to intrinsic (CV1114)  
  CodeView expected a closing parenthesis for an intrinsic function, but it was missing.
Missing ')' in substring (CV1119)  
  CodeView expected a closing parenthesis for a substring expression, but it was missing.
Missing or corrupt emulator info (CV1051)  
  Status information about the floating-point emulator is missing or corrupt.
  The program probably wrote to this area of memory. Check all pointers to confirm that they refer to their intended objects.
No closing double quotation mark (CV1029)  
  The double quotation mark (") expected at the end of the string was missing.
No closing single quotation mark (CV1030)  
  The single quotation mark (') expected at the end of the character constant was missing.
No code at this line number (CV1023)  
  An attempt was made to set a breakpoint at a line that does not correspond to machine code. Such a line could be a blank line, a comment line, a line with program declarations, or a line moved or removed by compiler optimization.
  To set a breakpoint at a line deleted by the optimizer, recompile the program with the /Od option to turn optimization off.
  Note that in a multiline statement the code is associated only with one line of the statement.
No CodeView source information (CV1059)  
  There is no CodeView symbol listing for the source file or module being debugged.
  Be sure the file was compiled with the /Zi option or the /Zd option. If linking in a separate step, be sure to use the /CO option.
No debugging information (CV5003)  
  The program file did not contain the debugging information needed.
  Recompile the program using the /Zi option to include CodeView symbolic information. If linking in a separate step, use the LINK /CO option.
No file selected (CV5005)  
  A module must be selected before OK is chosen.
  To exit the dialog box without selecting a module, choose Cancel.
No free EMM memory handles (CV3005)  
  No expanded memory handle is available for the symbolic information.
  One of the following may be a solution:

If multiple applications are running, remove one or more of the applications that use expanded memory. This should free enough handles to permit CodeView to run properly.

Reconfigure the EMM driver to allow more handles.

No immediate mode (CV4056)  
  The instruction does not take an immediate-mode operand.
No match found (CV5008)  
  There was no match for the specified string in the file.
No previous regular expression (CV1011)  
  The Repeat Last Find command was executed, but no previous regular expression (search string) has been specified.
No process status, /O not specified (CV5002)  
  CodeView must be started with the /O option in order to debug multiprocess programs.
  Exit and restart CodeView with the /O option.
No second monitor connected to system (CV1061)  
  CodeView was invoked with the /2 option, but there was no second monitor for CodeView to use.
No source lines at this address (CV1031)  
  An attempt was made to view an address which has no source code.
No Source window open (CV1058)  
  A command was entered to manipulate the contents of the Source window, but no Source window is open.
No space left on device (CV0028)  
  No more space for writing is available on the disk.
  One of the following may have occurred:

CodeView could not find room for writing a temporary file.

An attempt was made to write to a disk that was full.

No such file or directory (CV0002)  
  The specified file does not exist or a pathname does not specify an existing directory.
  Check the file or directory name in the most recent command.
  One of the following may have occurred:

The View (V) command or the Open Source command from the File menu was used to view a nonexistent file.

An attempt was made to print to a nonexistent file or directory.

No symbolic information for filename (CV0101)  
  The executable file (or DLL if in OS/2) did not contain the symbols needed by CodeView.
  Be sure to compile the program or DLL using the /Zi option. If linking in a separate step, be sure to use the /CO option. Use the most current version of LINK.
No watch variables to delete (CV5009)  
  An attempt was made to delete one or more watch variables (watch expressions), but no watch expressions are currently selected.
Not a text file (CV1039)  
  An attempt was made to load a file that is not a text file, possibly a binary-data file or an executable program file. This error can also occur if the first line of a file includes characters that are not in the range of ASCII 9 to 13 or ASCII 32 to 126.
  The Source window only works with text files.
Not DOS 3.0 or later (CV1315)  
  CodeView requires DOS version 3.0 or later. CodeView does not support DOS versions 1.x and 2.x.
Not enough memory to load CV.EXE (CV1314)  
  There was not enough conventional memory to load CodeView.
  Possible solutions include the following:

Free memory by removing terminate-and-stay-resident software.

Reduce the settings in CONFIG.SYS for FILES, BUFFERS, and LASTDRIVE.

Operand expected (CV4027)  
  The operation or instruction requires an operand, but none was specified.
Operand must be register (CV4018)  
  The operand for this instruction must be a register, not a label or variable.
Operand must have size (CV4035)  
  No variable size was specified for the operand.
  Specify the size of the variable being accessed by using the BY, WO, or DW operator.
Operand types incorrect for this operation (CV1010)  
  The operand types specified are not legal for the operation.
  For example, a pointer cannot be multiplied by any value.
Operand types must match (CV4031)  
  The command or instruction takes two or more operands, all of the same type.
Operator must have a struct/union type (CV1033)  
  Components of structure variables or unions must be fully qualified. Components cannot be entered without full specification.
Operator needs lvalue (CV1032)  
  An expression that does not evaluate to an lvalue was specified for an operation that requires an lvalue.
  An lvalue (so called because it appears on the left side of an assignment statement) is an expression that refers to a memory location.
  For example, buffer[count] is a valid lvalue because it points to a specific memory location. The logical comparison zed != 0 is not a valid lvalue because it evaluates to TRUE or FALSE, not a memory address.
Outdated EMM software (LIM 4.0 required) (CV3012)  
  The EMM driver must be LIM EMS version 4.0 or later in order to contain the calls needed for CodeView to use expanded memory.
Out of memory (CV0012)  
  CodeView was unable to allocate or reallocate the memory that it required because not enough memory was available.
  Possible solutions include the following:

Run CVPACK on the executable file to reduce the demand on memory for symbolic information.

Recompile without symbolic information in some of the modules. CodeView requires memory to hold information about the program being debugged. Compile some modules with the /Zd option instead of /Zi, or don't use either option.

Remove other programs or drivers running in the system that could be consuming significant amounts of memory.

Decrease the settings in CONFIG.SYS for FILES and BUFFERS.

Out of memory (CV3608)  
  CodeView needed additional conventional memory, but insufficient memory was available.
  Possible solutions include the following:

Run CVPACK on the executable file to reduce the demand on memory for symbolic information.

Recompile without symbolic information in some of the modules. CodeView requires memory to hold information about the program being debugged. Compile some modules with the /Zd option instead of /Zi, or don't use either option.

Remove other programs or drivers running in the system that could be consuming significant amounts of memory.

Free some memory by removing terminate-and-stay-resident software.

Remove unneeded watches or breakpoints.

Compile some modules with optimizations enabled to reduce the demand on memory made by the program being debugged.

Overlay Manager stack overflow (CV1317)  
  The CodeView file may be corrupt. Copy CV.EXE from the original disks and retry.
  If the error recurs, 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.
Overlay not resident (CV1047)  
  An attempt was made to disassemble machine code from an overlay section of code that is not currently resident in memory.
  Execute the program until the overlay is loaded.
Packed file (CV5012)  
  (DOS only)
  CodeView cannot debug files in DOS that are linked with the /EXEPACK option. Relink without this option to debug the file and then switch back to linking with /EXEPACK for the release version of your program.
Path of execution different from history (CV5006)  
  The code executed during dynamic replay differed from the recorded history.
  This may be normal if the program being debugged responds to asynchronous events.
Radix must be between 2 and 36 inclusive (CV1107)  
  A radix outside the allowable range was specified.
Register must be AX or AL (CV4060)  
  The destination register for the instruction must be AX or AL.
Register variable out of scope (CV1024)  
  An attempt was made to display a register variable outside the scope of the function containing it.
  One of the following occurred:

The variable was declared as a register variable. Recompile the program with the register declaration removed.

The optimizer converted an ordinary variable into a register variable to speed up execution. Recompile the program using the /Od option to turn optimization off.

The function was defined with _fastcall, causing parameters to be passed in registers. Remove the _fastcall designation and recompile.

Regular expression too long (CV1012)  
  The regular expression entered was too long or complex for CodeView to handle.
  Use a simpler regular expression.
Relative jump out of range (CV4053)  
  An address jump was specified that is greater than permitted.
  A jump may be forward no more than 127 bytes and backward no more than 128 bytes relative to the next instruction.
Restart illegal in child CodeView (CV3612)  
  A request was made to restart the program within a child copy of CodeView.
  The Restart command cannot be used on a child process in a child CodeView. It is necessary to restart the parent program to begin the child process again.
Restart program to edit options (CV2204)  
  The program must be restarted before the recording or playback options can be modified.
Restart program to record (CV5007)  
  Recording cannot begin while the program is executing.
  Restart the program before recording.
Resynchronizing the user tape (CV2205)  
  The command history and user input tapes are out of synchronization. CodeView automatically adjusted the user tape to be synchronized with the command tape.
Screen session ended—application output lost (CV1044)  
  Under OS/2, each screen display is handled by a different session. When CodeView tried to switch from one display to the other, the other display's session had ended and the output was gone.
  Exit CodeView and restart it.
Simple variable can not have arguments (CV1115)  
  In an expression, an argument was specified to a simple variable.
  For example, given the declaration INTEGER NUM, the expression NUM(I) is not allowed.
Specified number of lines not supported, using default (CV1052)  
  A display mode was selected that is not supported by either the monitor's hardware or the driver routines.
  Exit CodeView, then restart it with an appropriate command-line option for the display mode, either /25, /43, or /50.
Substring range out of bound (CV1118)  
  A character expression exceeded the length specified in the CHARACTER statement.
Symbol not defined (CV4009)  
  The symbol specified has not been previously defined.
  The symbol name may have been mistyped.
Syntax error (CV1017)  
  The command contained a syntax error.
  The most likely cause is an invalid command or expression.
The program has terminated, restart to continue (CV0003)  
  CodeView has detected a termination request by the program being debugged.
  The program cannot be executed because it has terminated and has not been restarted. Program memory remains allocated and may still be examined at this point.
  To run the program again, reload it using the Restart command.
Thread blocked (CV3501)  
  The requested thread will not run because it is blocked by another thread.
  If this is not expected behavior for the program being debugged, it may be necessary to terminate the threads that are blocking the requested thread.
Too few array bounds given (CV1103)  
  The bounds specified in an array subscript do not match the array declaration.
  For example, given the array declaration INTEGER IARRAY(3,4), the expression IARRAY(I) would produce this message.
Too many array bounds given (CV1104)  
  Too many subscripts were specified for the array.
  For example, given the array declaration INTEGER IARRAY(3,4), the expression IARRAY(I,3,J) would produce this error message.
Too many open files (CV0024)  
  CodeView could not open a file it needed because no more file handles are available.
  In DOS, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=20 is the recommended setting. In OS/2, if multiple processes are running, removing one or more of them may release enough file handles.
  The program being debugged may have so many files open that all available handles are exhausted. Check that the program has not left files open unnecessarily. The first four handles are reserved by the operating system.
Too many watch objects (CV1036)  
  More watch objects were specified than CodeView can handle.
  The number of watch expressions that can be specified varies with the demands made upon CodeView's internal memory resources.
  Remove one or more of the watch expressions, or remove some breakpoints.
TOOLS.INI not found (CV1053)  
  The directory listed in the INIT environment variable did not contain a TOOLS.INI file.
  Check the INIT variable to be sure it points to the correct directory.
Type clash in function argument (CV1117)  
  The type of an actual parameter did not match the corresponding formal parameter.
  This message also appears when a routine that uses alternate returns is called and the values of the return labels in the actual parameter list are not 0.
Type conversion too complex (CV1037)  
  Too many levels of type casting were specified.
  Type casting is limited to two levels, as in

(char) ((int) (floatvar))

Unable to create tape (CV2200)  
  CodeView could not open a disk file (tape) to record commands and data for later replay.
  Choosing the History On option from the Run menu causes CodeView to open disk files program.CVH and program.CVI to record all commands and data for a debugging session.
  One of the following situations may have caused the error:

There was not enough space on the disk containing the program to be debugged.

There were not enough free file handles. In DOS, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=20 is the recommended setting. In OS/2, if multiple processes are running, removing one or more of them may release enough file handles to permit creating the tape.

Unable to open file (CV1007)  
  The file specified cannot be opened.
  One of the following may have occurred:

The file may not exist in the specified directory.

The filename was misspelled.

The file's attributes are set so that it cannot be opened.

A locking or sharing violation occurred.

Unable to open tape (CV2201)  
  CodeView could not open the history file (tape) for replay.
  Choosing the History On option from the Run menu causes CodeView to open disk files program.CVH and program.CVI to record all commands and data for a debugging session.
  There probably were not enough free file handles. In DOS, increase the number of file handles by changing the FILES setting in CONFIG.SYS to allow a larger number of open files. FILES=20 is the recommended setting. In OS/2, if multiple processes are running, removing one or more of them may release enough file handles to permit opening the tape.
Unexpected EMM error (CV1316)  
  An unexpected error occurred when reading overlays into expanded memory.
  One of the following has probably occurred:

The EMM driver may be corrupted or may have malfunctioned. Reload the driver and retry.

Expanded memory has been corrupted.

  If the error recurs, 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.
Unexpected end-of-file in CV.EXE (CV1312)  
  An unexpected end-of-file occurred while CV.EXE was being read.
  The CodeView file may be corrupt. Copy CV.EXE from the original disks and retry.
  If the error recurs, 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.
Unknown queue request—ignored (CV3609)  
  One of the CodeView processes sent a command or data to another CodeView process that the latter process did not recognize. This is not a fatal error.
  If this is a recurring error, please 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.
Unknown symbol (CV1018)  
  The symbolic name specified could not be found.
  One of the following may have occurred:

The specified name was misspelled.

The wrong case was used when case sensitivity was on. Case sensitivity is toggled by the Case Sensitivity command from the Options menu, or set by the Option (O) Command-window command.

The module containing the specified symbol may not have been compiled with the /Zi option to include symbolic information.

User Tape Disabled (CV2208)  
  The current CodeView session was invoked with the /K option to disable the keyboard. CodeView issues this warning as a reminder that the recording ability is limited when /K is used. You can record CodeView commands made during a debugging session, but not user keystrokes.
User tape may be truncated (CV2203)  
  A request was made to start recording again without completely rerunning the original history tape. Any unexecuted commands will be discarded.
Value out of range (CV4050)  
  The value specified was out of range for the data item.
Video mode changed without /S option (CV1040)  
  The program being debugged changed screen modes, and CodeView was not set for swapping. The program output is now damaged or unrecoverable.
  To be able to view program output, exit CodeView and restart it with the Swap (/S) option.
Wrong number of function arguments (CV1116)  
  An incorrect number of arguments was specified in a function call.
Wrong type of register (CV4019)  
  The register specified is not permitted for this operation or instruction.
  The mnemonic for the register may have been mistyped.
/X: CPU in protected or virtual mode (CV1301)  
  The DOS extender was unable to switch to protected mode.
  One of the following may have occurred:

OS/2 is running.

An EMM driver is running in protected mode.

A protected-mode application is running.

/X: CPU not 80286 or later (CV1300)  
  The DOS extender runs in protected mode, which is supported only on the 80286 and later processors.
/X: HIMEM.SYS not loaded (CV1302)  
  HIMEM.SYS is used by the DOS extender to allocate extended memory and must be installed.
/X: not enough extended memory (CV1303)  
  There was not enough space in extended memory to load the DOS extender.
  One of the following may be a solution:

Remove programs that are using extended memory.

Run CodeView without the /X option.

/X: Unexpected initialization error (CV1320)  
  The DOS extender encountered a general protection fault.
  The CodeView file may be corrupt. Copy CV.EXE from the original disks and retry.
  If the error recurs, 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.