From:	derek AT algonet DOT se (Christian Granström)
Newsgroups:	comp.os.msdos.djgpp
Subject:	VBE2 InfoBlock problems (Please help)!!!
Date:	Mon, 26 May 1997 21:49:43 GMT
Organization:	RAGE
Lines:	42
Message-ID:	<338a030e.9979792@news.algonet.se>
NNTP-Posting-Host:	du115-2.ppp.algonet.se
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

Hi guys!!

Ive got a problem refering to pointers inside the VBEinfoBlock. I have
tried both the near and the far way to reach the strings pointed to by
the pointers inside the struct.

None of them seem to work, im kind of new using djgpp so I don't realy
know what to do. I used the near version to reach the videomemory with
linearframebuffer and that worked just fine.

What the hell am I doing wrong???

And which one is best to use far or near???
Whats the advantages/disadvantages with the two methods???
Anyone out there got a sourcecode that gets the  VbeInfoblock in
djgpp???


// near version this one goes without errors but the string is just
shit
mem.size=256;
mem.address=VbeContrlInfo->OemStringPtr;
__dpmi_physical_address_mapping(&mem);
addr=mem.address;                 
test=(char *)(addr + __djgpp_conventional_base);                 



// far version   this one fucks up when I use the _farnspeekb
    pagefaults and stuff like that
unsigned long test;
char test1;
 test =(unsigned long)VbeContrlInfo->OemStringPtr;
_farsetsel(_dos_ds);                 
test1 = _farnspeekb(test);


------------------------------------------------------------------------
      Christian Granström, Bryggerigatan 4A, 733 34 Sala, Sweden
    derek AT algonet DOT se, christiang AT pasdata DOT se, www.algonet.se/~derek
                 +46(0)22477312, +46(0)704961587
------------------------------------------------------------------------

- Raw text -