Mail Archives: djgpp/1996/12/04/05:56:28
From: | mert0407 AT sable DOT ox DOT ac DOT uk (George Foot)
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | Re: unsigned char *far : problems
|
Date: | Wed, 04 Dec 1996 06:48:05 GMT
|
Organization: | Oxford University
|
Lines: | 15
|
Message-ID: | <32a51cf9.46054839@news.ox.ac.uk>
|
References: | <01bbe146$95359e20$582449c2 AT default>
|
NNTP-Posting-Host: | mc31.merton.ox.ac.uk
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
On 3 Dec 1996 18:26:44 GMT, "Thomas Harte" <T DOT Harte AT btinternet DOT com>
wrote:
>unsigned char far *videobuf = (char far *)0xA0000000L;
>unsigned int far *videobufw = (int far *)0xA0000000L;
I take it you haven't read the FAQ... Go read it. It is extremely
helpful, and has a great deal of information on this problem.
I'll say briefly that the concepts of 'near' and 'far' pointers do not
exist under DJGPP; they are DOS-specific. Go and read the FAQ; this is
dealt with in section 17.7, I think. Accessing video memory is dealt
with specifically in section 10.2.
George Foot
- Raw text -