From:	"dima 3141596" <dima AT rts-ukraine DOT com>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: addressing question
Date:	Thu, 13 Sep 2001 17:51:33 +0300
Organization:	Alkar Teleport News Server
Lines:	25
Message-ID:	<9nqhdg$2gnu$1@pandora.alkar.net>
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1010913163428 DOT 3657C-100000 AT is>
NNTP-Posting-Host:	dial-164-91.alkar.net
Mime-Version:	1.0
X-Trace:	pandora.alkar.net 1000392944 82686 195.248.164.91 (13 Sep 2001 14:55:44 GMT)
X-Complaints-To:	abuse AT alkar DOT net
NNTP-Posting-Date:	Thu, 13 Sep 2001 14:55:44 +0000 (UTC)
X-Newsreader:	Microsoft Outlook Express 4.72.3155.0
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3155.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Hi Eli !

>The various ways of accessing the video memory from a DJGPP program are
>described and explained in the DJGPP FAQ, sections 10.2 and 18.4.

tnx for your answer, but I must write own library to direct access to
the video memory.

>> In the Turbo C I can do  it :     char far* scr = MK_FP(segment,
>> offset);
>>  then any instruction like it:       *scr = '1';  will generate asm
code
>>            mov ax,segment
>>            mov es,ax
>>            mov  es:[offset] , '1'   ------> here ES !!!
>
>This won't work in protected mode, even in Turbo C.

 Are you sure ??? :)
 If you want I can send simple program writen on the Turbo C where was
realised such video RAM access.

 --dima

- Raw text -