From: yurick AT oblik DOT dp DOT ua Newsgroups: comp.os.msdos.djgpp Subject: Re: __djgpp_map_physical_memory - some questions Date: Fri, 1 Jun 2001 18:21:23 +0300 Organization: Apex NCC Public InterNet News Server Lines: 16 Message-ID: References: <7458-Thu31May2001062819+0300-eliz AT is DOT elta DOT co DOT il> NNTP-Posting-Host: dialup79.apex.dp.ua X-Trace: main.apex.dp.ua 991436736 58305 195.24.139.79 (1 Jun 2001 23:05:34 GMT) X-Complaints-To: abuse AT apex DOT dp DOT ua NNTP-Posting-Date: 1 Jun 2001 23:05:34 GMT User-Agent: tin/1.5.8-20010221 ("Blue Water") (UNIX) (Linux/2.2.19 (i686)) To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Reply-To: djgpp AT delorie DOT com Thu, 31 May 2001 06:28:19 +0300, Eli Zaretskii wrote: >> 2. I've tried this with djgpp 2.03 under Win95OSR2. Is it supports >> this call (DPMI 0508)? EZ> The docs clearly says that this is DPMI 1.0 function, and that most EZ> DPMI hosts don't support it. Windows doesn't. I has been read docs but I hoped against hope :) Well, what can I do with it? Can I use _farpoke*() with _dos_ds for this? I need to access physical address 0xeb000000 (which is not in 1st meg of course). And will DPMI host allows such access or I must make some other calls for this? And if _farpoke*() is answer, I can't understand, how this works? I hasn't allocated memory at this address so DPMI host must blame me, hasn't it?