Mail Archives: djgpp/1996/08/12/05:45:24
Xref: | news2.mv.net comp.os.msdos.djgpp:7096
|
From: | Luke Steele <luke AT jags DOT co DOT uk>
|
Newsgroups: | comp.os.msdos.djgpp
|
Subject: | __dpmi_physical_address_mapping problems.
|
Date: | Sun, 11 Aug 1996 10:36:28 GMT
|
Organization: | INTERact BBS UK (01753) 775533
|
Lines: | 30
|
Message-ID: | <Dvz18E.6wH@ftp.jags.co.uk>
|
To: | djgpp AT delorie DOT com
|
DJ-Gateway: | from newsgroup comp.os.msdos.djgpp
|
Hi,
I'm having difficulty with the __dpmi_physical_address_mapping
function. I'm trying to use it to convert the physical address of the
linear frame buffer returned by the VESA driver, but whenever I use
the function I get an invalid opcode error. I've simplefied the code
to this:
#include "dpmi.h"
void main(void)
{
__dpmi_meminfo meminf;
meminf.size = 640*480;
meminf.address = 256*1024*1024;
__dpmi_physical_address_mapping(&meminf);
}
But this still generates the same error. I've also tried writing a
similar function myself, but this too generates the same error. Has
anyone any idea how I can solve this problem? If there's an
alternative way of accessing the VESA linear frame buffer, that would
also be great.
Thanks!
--
Luke Steele
(luke AT jags DOT co DOT uk)
- Raw text -