From: Martynas Kunigelis <martynas AT nm3 DOT ktu DOT lt>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Geting 8x8 text from rom?
Date: Tue, 16 Dec 1997 11:59:24 +0200
Organization: LITNET
Lines: 29
Message-ID: <349650FC.F89BC691@nm3.ktu.lt>
References: <34938c5f DOT 0 AT pusher DOT student DOT adelaide DOT edu DOT au> <34951A01 DOT 5C6864E3 AT nm3 DOT ktu DOT lt> <3495C407 DOT 1562 AT nic DOT smsu DOT edu>
NNTP-Posting-Host: slibinas.nm3.ktu.lt
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Precedence: bulk

Tony O'Bryan wrote:
> 
> Martynas Kunigelis wrote:
> 
[offensive post snipped]

> 
> There is no reason to get hyper on him, especially since he is correct
> for the platform he came from.  Turbo C required far pointers to specify
> a segment:offset address as a single long pointer.  Hence A000:0000 was
> addressed as:
> 
> unsigned char far *Screen = (unsigned char far *)0xa0000000;
> 
> And the font ROM would be addressed as (assuming the address is
> F000:FA6E):
> 
> unsigned char far *Rom = (unsigned char far *)0xf000fa6e;
> 
> You are correct about the protected mode linear address, and he was
> correct about the real mode Borlandism.


I am really sorry if I sounded hyper.. :( Had a bad day... The fact
that I _was_ aware of the Borlandism you mention makes me even more
guilty. Again, sorry, didn't mean it. However, weren't you supposed
to use MK_FP(0xa000,0) under Borland instead of the 0xa0000000 hack? :)

Martynas