Date:	Mon, 22 Nov 1999 09:14:47 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Marius Myburg <iti06469 AT mweb DOT co DOT za>
cc:	djgpp AT delorie DOT com
Subject:	Re: fprintf() and using under graphic modes
In-Reply-To:	<0FLK003UZO9RIJ@cpt-proxy1.mweb.co.za>
Message-ID:	<Pine.SUN.3.91.991122091431.3829K-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Mon, 22 Nov 1999, Marius Myburg wrote:

> If you really want to do things yourself from the bottom up, then you can
> access the ROM character set directly.
> 
> char *rom_char_set = (char *)0xffa6e;

Caveat emptor: this is not always true!  Some configurations load
non-default fonts into memory and use that instead of the font burnt
into the BIOS.  One notable case like this is if your CONFIG.SYS loads
DISPLAY.SYS or use the "MODE CON" command in AUTOEXEC.BAT to load some
.cpi file to support non-default codepage or font.

There are special subfunctions of function 11 of the BIOS interrupt
10h that return the pointer to the font tables.  You should use that
instead of hard-wired values like FFA6Eh.  The module conio.c in the
DJGPP library sources (djlsr202.zip) includes working code that
accesses the system font (and even changes it).

- Raw text -