BUG: CodeView for Windows Displays "Unsupported Video Mode"Last reviewed: July 22, 1997Article ID: Q116490 |
1.00 1.50 4.10
WINDOWS
kbtool kberrmsg kbbuglist
The information in this article applies to:
SYMPTOMSThe Visual Workbench comes with a customizable menu to start different applications such as App Studio and CodeView. These customizations are set up by choosing Options from the Tools menu. If the command line for CodeView for Windows uses the argument line "$(TARGET) /2" to enter CodeView in dual-monitor mode, invoking CodeView for Windows with a project loaded in the Visual Workbench causes the following message box to appear:
Codeview Exiting Unsupported Video Mode. Try CVW.EXEIf the parameters are then changed to "/2 $(TARGET)", another attempt to start CodeView for Windows causes the following message box to appear:
CVW is already runningAt this point, CodeView for Windows is stranded in memory. NOTE: A project must be loaded for this behavior to occur.
CAUSECodeView for Windows is not parsing the command line properly when the $(TARGET) /2 option is used. This same behavior can be reproduced by starting CodeView for Windows from File Manager or Program Manager using the same syntax, but supplying a real .EXE name in place of "$(TARGET)". Because CodeView requires the /2 option to be placed before the target name, CodeView should simply ignore the /2 option. If the $(TARGET) /2 command line is used with CodeView for MS-DOS, it properly ignores the /2, and these error messages do not appear. NOTE: In all cases, if no project has been loaded (that is, no target has been specified), CodeView correctly ignores the $(TARGET) field and starts in dual-monitor mode.
RESOLUTIONAlways put CodeView command-line switches before the target name. If you have already encountered the message boxes listed above, restarting Windows and invoking CodeView using the /2 $(TARGET) command line will properly start CodeView in dual-monitor mode.
STATUSMicrosoft has confirmed this to be a bug in the products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.
MORE INFORMATIONTo reproduce the problem, do the following: NOTE: It is not necessary to have a second monitor to reproduce the error messages using the /2 option.
|
Additional reference words: 1.00 1.50
© 1998 Microsoft Corporation. All rights reserved. Terms of Use. |