delorie.com/archives/browse.cgi | search |
Xref: | news-dnh.mv.net comp.os.msdos.djgpp:1695 |
Path: | news-dnh.mv.net!mv!news.sprintlink.net!in2.uu.net!mercury.near.net!noc.near.net!das-news2.harvard.edu!oitnews.harvard.edu!newsfeed.rice.edu!rice!news!sandmann |
From: | Charles Sandmann <sandmann AT clio DOT rice DOT edu> |
Newsgroups: | comp.os.msdos.djgpp |
Subject: | Re: Please define "locking" |
Date: | Mon, 21 Aug 1995 16:12:30 CDT |
Organization: | Rice University, Houston, Texas |
Lines: | 12 |
References: | <41ajf9$ogg AT sulawesi DOT lerc DOT nasa DOT gov> |
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 |
> However, the machines I develop and test upon DO have hard drives, so how > would I disable virtual memory on them so that I don't have to deal with this? It is DPMI provider dependent. Under QDPMI, you use NOVM, under Windows you tinker with the swap file size/location/existence. Under the current beta of cwsdpmi (or GO32...) you point GO32TMP environment variable to a non-existent drive (ie v:\) > Do you have a favorite example you could point me to? The easiest to get is in the V2 source in go32/dpmiexcp.c & exceptn.S - V2 hooks the keyboard, timer, and coprocessor interrupts.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |