delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:3612 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!datalytics!news.ahc.ameritech.com!ddsw1!news.mcs.net!chi-news.cic.net!newsfeed.internetmci.com!news.sesqui.net!rice!news!sandmann |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: DPMI Server |
Date: | Sun, 03 Dec 1995 20:53:07 CST |
Organization: | Rice University, Houston, Texas |
Lines: | 13 |
References: | <49r0p5$77h AT news1 DOT delphi DOT com> |
Reply-To: | sandmann AT clio DOT rice DOT edu |
Nntp-Posting-Host: | clio.rice.edu |
To: | djgpp AT sun DOT soe DOT clarkson DOT edu |
Dj-Gateway: | from newsgroup comp.os.msdos.djgpp |
> I'm having trouble finding a DPMI server. I got CWSDPMI beta 6 from > ftp.idsoftware.com, but it takes up 50K(!!) of memory, and that's WAY too > big for me. It also doesn't support 16 bit apps, ie ED209. Problem 1 - if you run a 16-bit DPMI app you cannot shell out to a 32-bit DPMI app - this is against the DPMI rules. Since nested DPMI apps share the same IDT, you can't mix 16-bit and 32-bit. The only way around this is a DPMI 1.0 server - you could buy 386MAX. Problem 2 - to get a significantly smaller memory footprint you will have to run under Windows (or OS/2 or something else) to decrease the memory footprint (at least until Morten finishes his server ;-)
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |