X-Authentication-Warning: delorie.com: mail set sender to djgpp-bounces using -f From: Hans-Bernhard Broeker Newsgroups: comp.os.msdos.djgpp Subject: Re: dosmemput and dosmemget Date: 3 Mar 2005 18:13:13 GMT Lines: 26 Message-ID: <38p2dpF5scat7U5@news.dfncis.de> References: <1109872127 DOT 199181 DOT 31850 AT l41g2000cwc DOT googlegroups DOT com> X-Trace: news.dfncis.de I9KxpZyfQusKqIYrcRprlAzAEoiO6eJneULv08r7LCQMtFY2bmvC2OZOxt X-Orig-Path: not-for-mail To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com arizvi wrote: > My doubt it whether the function actually copies data from one memory > space to another, or if there is no actual copying but some sort of > remapping of address spaces. It's actual copying --- if DOS could be "told" where this memory is, these functions wouldn't be needed at all. But DJGPP program's main memory is way outside the region of memory MS-DOS, being a 16-bit OS, has direct access to. Remapping would be a theoretical possibility, but most DPMI servers don't let a client do that in the region accessible by DOS --- for good reasons, I must assum. > I am writing a program with lots of dosmemput(s) and dosmemget(s). > If I could reduce the number of these function calls by once and for > all telling DOS that I would like to work in DOS memory - there would > be no need for those calls. If you really *need* those many calls, then there's nothing to be done but to make them. This overhead is the price you pay for not having to worry about silly 64K size restrictions all the time, without having to go all the long way to Windows programming. -- Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de) Even if all the snow were burnt, ashes would remain.