From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: _mono... functions don't work
Date: 5 Oct 2000 12:51:29 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 24
Message-ID: <8rhtgh$jah$1@nets3.rz.RWTH-Aachen.DE>
References: <39DBC1FD DOT F9E5AB44 AT polbox DOT com>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 970750289 19793 137.226.32.75 (5 Oct 2000 12:51:29 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 5 Oct 2000 12:51:29 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

Jerzy Klejnowski <dziabol AT polbox DOT com> wrote:
> 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 find it hard to understand how this behaviour lead to a subject line
claiming that these "functions don't work". They most obviously *do*
work, albeit not exactly in the expected way.

> Could anybody confirm (or not) this buggy behaviour?

This buggy behaviour actually exists with a purpose. The _mono_*
functions were mainly used for debugging printout, and DJ seems to
have had other facilities running in the background, at that time,
which constantly used the top and bottom 5 lines of the Mono screen,
so they leave them alone.

If this really bugs you, you can change this by changing two #defines
in src/libc/pc_hw/mono/mono.c from djlsr203.zip, recompiling it and
putting the changed version into your libc.a.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.