delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/1997/07/27/19:49:02

From: lonniem AT cs DOT utexas DOT edu (Lonnie McCullough)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: __dpmi_int
Date: Sun, 27 Jul 1997 05:55:58 GMT
Message-ID: <33dae229.1242808@news.nol.net>
References: <Pine DOT UW2 DOT 3 DOT 95 DOT 970726184003 DOT 4492A-100000 AT bryggen DOT bgnett DOT no>
NNTP-Posting-Host: ip38-57.nol.net
Lines: 23
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

On Sat, 26 Jul 1997 16:40:29 GMT, Gisle Vanem <giva AT bryggen DOT bgnett DOT no>
wrote:

> 
>George Foot (mert0407 AT sable DOT ox DOT ac DOT uk) wrote:
>> If you will be calling this routine a lot you could more efficiently
>> allocate the block of low memory on initialisation, use it over and over
>> again later on, and free the block on shutdown. Or you could use the
>> transfer buffer, which is already allocated for you, doesn't need 
>> freeing, and can normally be stomped on without causing any problems.
> 
>Are you sure about that? I tought the __tb was  used for all dos I/O.
> 
>Gisle V.
DJGPP uses it for comunticating with BIOS routines that need pointers
to areas of memory in conventional memory but none of the routines
that use the transfer buffer assume it's contents to be preserved
across function calls so it is safe to use for any conventional memory
buffer (unless a call is made to the bios and the tranfer buffer is
required: you're data will be overwritten)

Lonnie McCullough
lonniem AT cs DOT utexas DOT edu

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019