"Funny" problem with MSVC6 and flatscreen
-
Hi, I just got a new monitor, a Samsung SyncMaster 151BM flatscreen (nice!). But I also go myself a spurious problem. Whenever I compile something with VC++ 6.0 the screen goes black, showing a caret in the upper left corner (reminds me of the ol' DOS days, but no prompt :-) ) and a white box as the mouse cursor. When compilation ends the screen goes back to normal, and all the little messages from the compilation is present in the Build box. I have fumbled around with both a generic MS driver for the monitor and with the Samsung driver included with the monitor (no updated one present), but to no avail. Has anybody seen this phenomenon before? My box is a HP Vectra 800MHz with 256 MB RAM and running Win2K Pro (corporate setup). Cheers Steen. "To claim that computer games influence children is rediculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"
-
Hi, I just got a new monitor, a Samsung SyncMaster 151BM flatscreen (nice!). But I also go myself a spurious problem. Whenever I compile something with VC++ 6.0 the screen goes black, showing a caret in the upper left corner (reminds me of the ol' DOS days, but no prompt :-) ) and a white box as the mouse cursor. When compilation ends the screen goes back to normal, and all the little messages from the compilation is present in the Build box. I have fumbled around with both a generic MS driver for the monitor and with the Samsung driver included with the monitor (no updated one present), but to no avail. Has anybody seen this phenomenon before? My box is a HP Vectra 800MHz with 256 MB RAM and running Win2K Pro (corporate setup). Cheers Steen. "To claim that computer games influence children is rediculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"
At a guess this is VC making a call to the command prompt to run a tool of some kind. Try changing the background colour of your command prompt and see if the same background colour appears in the compiler. Michael :-)
-
At a guess this is VC making a call to the command prompt to run a tool of some kind. Try changing the background colour of your command prompt and see if the same background colour appears in the compiler. Michael :-)
You're right, of course. I found out that during a long compile I could switch away from the black screen using alt-esc, and briefly see a command prompt icon flicker on the task bar. Now the question is, why doesn't the focus return to the IDE window during the compilation, but stays on the command prompt window until the compile is finished? I have checked a number of flatscreen monitors as well as normal CRT ones, and they all displayed this phenomenon. So it has nothing to do with the monitor, perhaps my updated Intel Graphics Technology driver is to blame? Or did I inadvertently set some default parameters for command prompts in a special way to get this? I, for one, am completely lost here. Cheers Steen. "To claim that computer games influence children is rediculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"
-
You're right, of course. I found out that during a long compile I could switch away from the black screen using alt-esc, and briefly see a command prompt icon flicker on the task bar. Now the question is, why doesn't the focus return to the IDE window during the compilation, but stays on the command prompt window until the compile is finished? I have checked a number of flatscreen monitors as well as normal CRT ones, and they all displayed this phenomenon. So it has nothing to do with the monitor, perhaps my updated Intel Graphics Technology driver is to blame? Or did I inadvertently set some default parameters for command prompts in a special way to get this? I, for one, am completely lost here. Cheers Steen. "To claim that computer games influence children is rediculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"
How does a normal command prompt open? I've never seen this problem before, but it is probably some screwed setting on the command prompt? Are you upto date with all the service packs, both VC and Windows? Michael :-)
-
Hi, I just got a new monitor, a Samsung SyncMaster 151BM flatscreen (nice!). But I also go myself a spurious problem. Whenever I compile something with VC++ 6.0 the screen goes black, showing a caret in the upper left corner (reminds me of the ol' DOS days, but no prompt :-) ) and a white box as the mouse cursor. When compilation ends the screen goes back to normal, and all the little messages from the compilation is present in the Build box. I have fumbled around with both a generic MS driver for the monitor and with the Samsung driver included with the monitor (no updated one present), but to no avail. Has anybody seen this phenomenon before? My box is a HP Vectra 800MHz with 256 MB RAM and running Win2K Pro (corporate setup). Cheers Steen. "To claim that computer games influence children is rediculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"
What happens is the IDE launches cl to do the compiling. cl is a console app, so you're seeing the console window. I know I've seen a KB article on this, give a search of MSDN on "cl console" and you should find it. --Mike-- http://home.inreach.com/mdunn/ #include "witty_sig.h" :love: your :bob: with :vegemite: and :beer:
-
Hi, I just got a new monitor, a Samsung SyncMaster 151BM flatscreen (nice!). But I also go myself a spurious problem. Whenever I compile something with VC++ 6.0 the screen goes black, showing a caret in the upper left corner (reminds me of the ol' DOS days, but no prompt :-) ) and a white box as the mouse cursor. When compilation ends the screen goes back to normal, and all the little messages from the compilation is present in the Build box. I have fumbled around with both a generic MS driver for the monitor and with the Samsung driver included with the monitor (no updated one present), but to no avail. Has anybody seen this phenomenon before? My box is a HP Vectra 800MHz with 256 MB RAM and running Win2K Pro (corporate setup). Cheers Steen. "To claim that computer games influence children is rediculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"
-
How does a normal command prompt open? I've never seen this problem before, but it is probably some screwed setting on the command prompt? Are you upto date with all the service packs, both VC and Windows? Michael :-)
Hi Michael apparently my Win2K has been set to open all console apps in fullscreen mode by default, hence the black screen (this was pointer out to me by Michael Dunn). It's described in Q126031 in MSDN KB. I simply removed this default fullscreen mode in the registry and the problem evaporated! Thanks for all your help :-) Cheers Steen. "To claim that computer games influence children is rediculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"
-
What happens is the IDE launches cl to do the compiling. cl is a console app, so you're seeing the console window. I know I've seen a KB article on this, give a search of MSDN on "cl console" and you should find it. --Mike-- http://home.inreach.com/mdunn/ #include "witty_sig.h" :love: your :bob: with :vegemite: and :beer:
Wow! You're absolutely right. The KB article is Q126031. The problem was that my Win2K was set to start console apps in default fullscreen mode. When I remobed this setting in the registry the problem evaporated! Thanks 1M times! :) Cheers Steen. "To claim that computer games influence children is rediculous. If Pacman had influenced children born in the 80'ies we would see a lot of youngsters running around in dark rooms eating pills while listening to monotonous music"