Date: Thu, 21 Oct 1999 19:22:17 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Tom Fjellstrom <tomcf AT connect DOT ab DOT ca>
cc: djgpp AT delorie DOT com
Subject: Re: Plague of the slow 'blit' routine :)
In-Reply-To: <380EF520.C2FAE759@connect.ab.ca>
Message-ID: <Pine.SUN.3.91.991021191954.4851E-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On Thu, 21 Oct 1999, Tom Fjellstrom wrote:

> But I can't be completely sure if the 'bitmap' i'm blitting
> to or from is in video memory. If I could then it would make sense
> to call the dosmemput or farptr functions only for those 'bitmaps'.
> I may be wrong but I don't think 'regular' memory can (or should?) be
> accessed with dosmemput or those farptr functions.

For ``normal'' memory, simply use memcpy or whatever C functions are 
appropriate.  There's no need neither for farptr nor for 
__djgpp_nearptr_enable stuff.

> The only way I have thought of determining that a bitmap is in video memory
> is too add a variable to the bitmap struct when creating it to indicate
> whether or not it is in video memory.

I'm not sure I follow.  How come you don't know where's the bitmap in a 
program that you yourself wrote?