| delorie.com/archives/browse.cgi | search |
| From: | "Charles Sandmann" <sandmann AT clio DOT rice DOT edu> |
| Newsgroups: | comp.os.msdos.djgpp |
| Subject: | Re: CWSDPMI Error? |
| Date: | Wed, 22 Oct 1997 9:35:56 |
| Organization: | Aspen Technology, Inc. |
| Lines: | 7 |
| Message-ID: | <344dc8fc.sandmann@clio.rice.edu> |
| References: | <Pine DOT GSO DOT 3 DOT 96 DOT 971020202746 DOT 26137A-100000 AT ural2> |
| Reply-To: | sandmann AT clio DOT rice DOT edu |
| NNTP-Posting-Host: | nboal2.dmccorp.com |
| To: | djgpp AT delorie DOT com |
| DJ-Gateway: | from newsgroup comp.os.msdos.djgpp |
> but error is error... So, there is a function 0x0801 of DPMI. > CWSDPMI is returning the value of 0x0801 always, so the > __dpmi_free_physical_mapping is ALWAYS returning -1. As it should - since dpmi_free_physical_mapping (0x801) is a dpmi 1.0 feature which CWSDPMI doesn't support. Don't use this call. I can't think of a real good reason to support it.
| webmaster | delorie software privacy |
| Copyright © 2019 by DJ Delorie | Updated Jul 2019 |