[comp.windows.ms.programmer] TDW Dual Monitor Problem

kid@hpctdkzcol.hp.com (Kevin Dietz) (05/30/91)

I have a Video 7 VEGA VGA (8-bit) card and an older (bought in 1985)
Sysdyne monochrome adapter card.  I'm trying to use these to do 
dual-monitor debugging with TDW.  The VGA card has a switch to make
it be either the primary or secondary adapter.  The Sysdyne card
doesn't (I don't know if any monochrome cards have a switch to do
this).  Anyways, TDW comes up on the monochrome monitor okay, but
everything on the color screen comes up in black-and-white.  That is,
the program I'm debugging comes up in black-and-white.  If I move the
app's window, the area the window previously covered stays black (the
background is not drawn correctly).  If I iconize and deiconize the
Program Manager, all the icons in it (which were color up until this
point) are now black and white.  Basically anything that has to be
redrawn is redrawn in black and white.

Normally I run the VGA card in 740x520 mode (or something like).  Now
I know TDW says it only supports standard VGA, but it's not clear in
the manual if this means you need standard VGA to do single monitor
debugging only, or if you also need it for dual monitor.  In any
event, I tried it both ways, standard & non-standard, and it does
the exact same thing both times.  I also tried the primary/secondary
adapter setting on the VGA card, and that didn't seem to matter either.

Other than this problem, the debugging process seems to work fine.  I
just don't like everything going to black and white.  Has anybody
else seen this?  Am I doing something wrong?  Do I need a newer
monochrome adapter card (or VGA card)?  Thanks for your help.

Kevin Dietz

bking@ersys.edmonton.ab.ca (Barry King) (06/02/91)

kid@hpctdkzcol.hp.com (Kevin Dietz) writes:

> 
> I have a Video 7 VEGA VGA (8-bit) card and an older (bought in 1985)
> Sysdyne monochrome adapter card.  I'm trying to use these to do 
> dual-monitor debugging with TDW.  The VGA card has a switch to make
> it be either the primary or secondary adapter.  The Sysdyne card
> doesn't (I don't know if any monochrome cards have a switch to do
> this).  Anyways, TDW comes up on the monochrome monitor okay, but
> everything on the color screen comes up in black-and-white.  That is,
> the program I'm debugging comes up in black-and-white.  If I move the
> app's window, the area the window previously covered stays black (the
> background is not drawn correctly).  If I iconize and deiconize the
> Program Manager, all the icons in it (which were color up until this
> point) are now black and white.  Basically anything that has to be
> redrawn is redrawn in black and white.
> 
> Normally I run the VGA card in 740x520 mode (or something like).  Now
> I know TDW says it only supports standard VGA, but it's not clear in
> the manual if this means you need standard VGA to do single monitor
> debugging only, or if you also need it for dual monitor.  In any
> event, I tried it both ways, standard & non-standard, and it does
> the exact same thing both times.  I also tried the primary/secondary
> adapter setting on the VGA card, and that didn't seem to matter either.
> 
> Other than this problem, the debugging process seems to work fine.  I
> just don't like everything going to black and white.  Has anybody
> else seen this?  Am I doing something wrong?  Do I need a newer
> monochrome adapter card (or VGA card)?  Thanks for your help.
> 
> Kevin Dietz

I just went through the same thing with an ATI VGA Wonder/512.  All I had 
to do in the end was put the ATI into an 8 bit slot...that's all.  
Everything works perfectly now although VGA performance is somewhat 
degraded.

Barry King              bking@ersys.edmonton.ab.ca
Edmonton Remote Systems:  Serving Northern Alberta since 1982

kpleas@milton.u.washington.edu (Keith Pleas) (06/03/91)

The "official" answer from Borland as to why TDW doesn't run in other
than normal VGA resolution is that there is a bug in WINDEBUG.DLL, which
they have licensed from Microsoft.  This is the same WINDEBUG.DLL that
comes with the SDK.  It was reported to MS months ago by beta testers.

If I were to speculate (which, in fact, I am going to do), I would say
that there won't be a fix (if any) until Windows 3.1 ships.  FWIW, I dl'd
the updated CVW (CodeView for Windows, for use with single monitors) and
it didn't include any DLLs.