Date: Thu, 2 Aug 2001 09:52:00 +0300 (IDT)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: "Mark E." <snowball3 AT bigfoot DOT com>
cc: djgpp-workers AT delorie DOT com
Subject: Re: djgpp: djgpp/src/libc/posix/termios/tmwrite.c
In-Reply-To: <3B6822C8.13288.88DCBE@localhost>
Message-ID: <Pine.SUN.3.91.1010802095129.28510D-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Wed, 1 Aug 2001, Mark E. wrote:

> > The upshot of this is that you need to call a special function (see
> > refreshvirtualscreen on conio.c) to signal DOS/V that it should update
> > the actual screen from its virtual contents at 0xb800 or wherever.
> 
> > OTOH, if only BIOS functions are used to
> > write text and move cursor, this problem is irrelevant to termios.
> 
> Then perhaps DOS/V should use the all-BIOS support (when added) so
> the direct access code doesn't have to deal with this complication.

I'm not sure what do you mean.  Are you suggesting to have two
branches of code in termios, one that uses BIOS for DOS/V, the other
one which uses direct video memory access, for other systems?  If so,
I think it's easier to use direct access on all platforms and to call
the equivalent of refreshvirtualscreen at strategic points: it's not
such a big deal, in practice, as demonstrated by conio.