Article ID: 116489
Article Last Modified on 9/30/2003
APPLIES TO
- Microsoft CodeView 4.0
- Microsoft CodeView 4.01
- Microsoft CodeView 4.1
This article was previously published under Q116489
SYMPTOMS
Screen corruption occurs when printing to stdout from a DOS application,
while using CV /2 to start CodeView in a DOS session under Windows.
Portions of the screen may get blanked out and restored from old buffered
screens, the mouse position may move to the middle of the screen, or
existing text may get overwritten. Note that these problems do not occur
when running outside of Windows under native DOS.
RESOLUTION
To work around the problem, you can debug under native DOS or switch
to single monitor mode.
Depending on your application, the following may also work while
debugging under Windows:
- Clear the screen before starting CV at the DOS session prompt.
- If you have Visual C++, start CodeView for DOS from the Workbench
Tools menu.
STATUS
Microsoft has confirmed this to be a problem with the interaction
between Windows and CodeView for DOS while running in a Windows DOS
session. We will post more information here in the Knowledge Base as
it becomes available.
Additional query words: 4.00 4.10
Keywords: kb16bitonly KB116489