Date: Thu, 5 Oct 2000 12:47:05 -0400
Message-Id: <200010051647.MAA12723@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp AT delorie DOT com
In-reply-to: <39DBC1FD.F9E5AB44@polbox.com> (message from Jerzy Klejnowski on
	Thu, 05 Oct 2000 01:49:17 +0200)
Subject: Re: _mono... functions don't work
References:  <39DBC1FD DOT F9E5AB44 AT polbox DOT com>
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


> When I try to use functions from '_mono' family to display something
> on my secondary (mono) monitor, they use only middle part of screen,
> leaving top and bottom lines intact. I've tried to write directly to
> screen memory, and got proper results. Could anybody confirm (or
> not) this buggy behaviour?

It's intentional.  That module was written by me, for me.  At the
time, I had a number of TSRs that also used the mono screen, like a
clock, disk monitor, program tracer, and heartbeat.  They used the
other lines.

Since the _mono routines are intended for debugging, this isn't a big
problem.  If you want to do full-screen stuff, you'd either write
directly to memory (that's faster anyway) or switch to mode 7 so that
stdout goes to the mono screen.

However, if someone wants to modify mono.c to use the whole screen
now, I won't mind.