Xref: news-dnh.mv.net comp.os.msdos.djgpp:1087
Path: news-dnh.mv.net!mv!news.NH.Destek.Net!news2.net99.net!uunet!in2.uu.net!newshost.marcam.com!news.mathworks.com!newsfeed.internetmci.com!ncar!noao!CS.Arizona.EDU!news.Arizona.EDU!usenet
From: fitz AT argus DOT lpl DOT arizona DOT edu (Mike Fitzgibbon)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: running with 2 monitors
Date: 20 Jul 1995 17:39:31 GMT
Organization: University of Arizona, LPL
Lines: 18
References: <DC09Eu DOT L1J AT jade DOT mv DOT net>
Nntp-Posting-Host: babel.lpl.arizona.edu
To: djgpp AT sun DOT soe DOT clarkson DOT edu
Dj-Gateway: from newsgroup comp.os.msdos.djgpp

In article <DC09Eu DOT L1J AT jade DOT mv DOT net>, A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk says...
>
>  If I am not debugging but running an ordinary program e.g. with the main
>graphical display on the color monitor and the control and system replies on
>the mono monitor: how can the program switch between monitors when desired?

It depends on the graphics library that you are using.  We are doing a similar 
thing here for instrument control using Genus's libraries.  The method we use 
is to initialize the graphics, setting display type, mode, etc. for the data 
display, and then set the BIOS equipment flag to mono (bits 4 & 5 set at 
40:10).  Then call INT 10 with AX=7 to reset the BIOS mode to mono text for 
the I/O screen.  It's not perfect, but it will work with many cards.

Note that if the graphics does a mode detect within its calls they must be 
disabled or this will not work.  In this case just do the graphics normally 
and the I/O screen must be handled with direct screen writes to B000:0-7FFF.