Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!caen!ox.com!math.fu-berlin.de!unido!rwthinf!slcdec!hippo!f1.n6000.z2.fidonet.org!f50.n347.z1.fidonet.org!Kent_Stewart
From: Kent_Stewart@f50.n347.z1.fidonet.org (Kent Stewart)
Newsgroups: comp.windows.ms.programmer
Subject: Dual Monitor debugging?
Message-ID: <1410700260@f50.n347.z1.fidonet.org>
Date: 8 May 91 20:40:00 GMT
References: <5532@p1.f6.n242.z2.fidonet.org>
Reply-To: Kent_Stewart%f50.n347.z1@hippo.dfv.rwth-aachen.de (Kent Stewart)
Organization: The Traveler's Mail BBS Richland, WA. 1:347/50
Lines: 20
Comment-To: fred_welland@f1.n6000.z2.fidonet.org (Fred Welland)


 > Dual monitor debugging with TP for Windows and
 > BC++.  The debugger for these package claim
 > that they support dual monitor debugging.
 > I want to setup the 3d as my primary monitor
 > and the LE mono monitor to "run" the debugger.
That's the only choice.
 > I realize that I will need another display adapter
 > to run the 2nd monitor (as well as fiddle around
 > with the IRQ settings).
The hercules clone that I am using has a jumper to make it the secondary 
monitor and that is all you have to do.  If you are lucky, you won't have to 
protect any memory.  I don't remember using bc++ in this mode, but I have used 
codeview, td and tdw in the dual monitor mode.  The vga
bcomes the program's display and the mono is the debugger's
display.  The great part of it all is no more switching
screens when you move through the code.

Kent