From: Lars Damerow Subject: Re: DJGPP To: djgpp AT sun DOT soe DOT clarkson DOT edu Date: Tue, 2 May 1995 18:13:57 -0400 (EDT) From djgpp-bounces AT sun DOT soe DOT clarkson DOT edu Tue May 2 17:06 EDT 1995 Received: from omnigate.clarkson.edu (omnigate.clarkson.edu [128.153.4.2]) by bingnfs1.cc.binghamton.edu (8.6.9/8.6.9) with SMTP id RAA13410 for ; Tue, 2 May 1995 17:06:18 -0400 Received: from sun.soe.clarkson.edu by omnigate.clarkson.edu with SMTP (PP) id <04504-0 AT omnigate DOT clarkson DOT edu>; Tue, 2 May 1995 16:08:47 -0400 Received: by sun.soe.clarkson.edu.soe (4.1/SMI-4.1) id AA03609; Tue, 2 May 95 15:18:42 EDT Received: from Starbase.NeoSoft.COM by sun.soe.clarkson.edu.soe (4.1/SMI-4.1) id AA03577; Tue, 2 May 95 15:17:45 EDT Received: from praline.no.NeoSoft.com (sandmann AT praline DOT no DOT NeoSoft DOT COM [198.64.57.253]) by Starbase.NeoSoft.COM (8.6.10/8.6.10) with ESMTP id OAA05822; Tue, 2 May 1995 14:15:07 -0500 Received: (from sandmann AT localhost) by praline.no.NeoSoft.com (8.6.10/8.6.10) id OAA20024; Tue, 2 May 1995 14:15:06 -0500 X-Provider: NeoSoft, Inc.: Internet Service Provider (713) 684-5969 From: Charles Sandmann Message-Id: <199505021915 DOT OAA20024 AT praline DOT no DOT NeoSoft DOT com> Subject: Re: DJGPP To: b8003054 AT nas05 DOT kpi DOT edu DOT tw Date: Tue, 2 May 1995 14:15:05 -0500 (CDT) Cc: KM5M AT c53000 DOT petrobras DOT anrj DOT br, djgpp AT sun DOT soe DOT clarkson DOT edu In-Reply-To: <9505020841 DOT AA11452 AT nas05 DOT kpi DOT edu DOT tw> from "b8003054 AT nas05 DOT kpi DOT edu DOT tw" at May 2, 95 04:41:45 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Content-Length: 374 Status: RO >> The address of video RAM is re-mapped to the address 0xe0000000. If >you want > to access the video RAM, you can use the pointer 0xe00b8000. > >Don't do this, use dosmem*() routines or > >This method does not work under Dpmi hosts (like qdpmi, windows, os/2, etc) >and won't work at all in a few months when V2 is released. > >Just say NO to 0xe0000000 addressing! Does that mean that direct video graphics will not be allowed? If it is not possible to use a pointer directed to video RAM to put pixels on the screen, can we set up a segment that gives us that kind of access without causing a segmentation fault? My entire optimized graphics library is at stake if we can't! :( ...Lars Damerow bb07779 AT bingsuns DOT cc DOT binghamton DOT edu (try saying THAT ten times fast!)