From:	tmurez AT nospam DOT planete DOT net (Thibaut Murez)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: VESA and more generally using dpmi to access VIDEO Memory
Date:	Sun, 29 Nov 1998 15:47:44 +0100
Organization:	Planete.net, France
Lines:	18
Message-ID:	<MPG.10ca0e2bd9949e4e98969d@news>
References:	<MPG DOT 10c7c628d7c67f2898969b AT news> <73mqsq$t5f$1 AT idy05 DOT tfh-berlin DOT de>
NNTP-Posting-Host:	numeris-bdx-12.planete.net
X-Newsreader:	Anawave Gravity v2.00
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

In article <73mqsq$t5f$1 AT idy05 DOT tfh-berlin DOT de>, pitti AT tfh-berlin DOT de 
says...
> The physical address of the video memory should not be hardcoded,
> but rather obtained from VESA >= 2.0 or something, or else this
> will indeed only run on YOUR computer - but I guess this is only
> supposed to be an example...
Exactly it was just a try to find what didn't work. As LFB is bigger than 
one segment i used 0xa000 instead...
> The only difference I can see to code I have written is the
> call for the segment limit:
> 
> __dpmi_set_segment_limit(VideoSelector, LFB.size-1);
Great it works !!! just one question...Why must the size be 1 byte less ?
i guess that it's because offset start from 0 so last offset i size-1..Is 
that right ?
> 
> The size must be 1 less. Then it should work.
Thanks a lot :)

- Raw text -